RCP Counters

FUNCTIONAL SPECIFICATION
not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this
document, use and communication of its contents
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
GLOSSARY / TERMINOLOGY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.1 General Principle about Application Counters Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.1.2 Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.2 General Principle about Application Counters Exploitation . . . . . . . . . . . . . . . . . . . . . . . 26
1.2.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.2.2 Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.3 Activation of synchronized sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.4 Functional options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2 DETAILED DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.1 Detailed description in the RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.1 The functional environment of the function in the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.2 List of RCF observations to be sent to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.2 Detailed description in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.2.1 Functional environment of the function in the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.2.2 List of VLR observations to be sent to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.3 Detailed description in the RCP station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.3.2 List of RCP station observations to be sent to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.4 Detailed description in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.4.2 List of HLR observations to be sent to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.5 Detailed description in the HLR station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2.5.2 List of HLR station observations to be sent to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3 INTERFACE MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
01 020122 DP4 SYS/DFB
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

1AA 00014 0004 (9007) A4 – ALICE 04.10
OBSERVATION
ED 01
AAC020023800DS En 1 / 260
260
4 INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.1 I20y interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.1.1 J Interface definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.1.2 Filter mechanism and Transfer of observation data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.1.3 Ticket format (sent by the ASP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4.1.4 Detail about rank in the family identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

4.1.5 Maximum number of counters sent per family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4.2 I30y interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4.3 I40y interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
APPENDIX A – RCF COUNTER IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

A.1 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
A.2 –––––––––––––––––––– CA counters (357) ––––––––––––––––––––––––– . . . . . . . . . . . 115
A.2.1 OB–FCA–APPCHGREP (19) – Number of Apply Charging successful . . . . . . . . . . . . . . 115
A.2.2 OB–FCA–APPCHGREQ (18) – Number of Apply Charging . . . . . . . . . . . . . . . . . . . . . . . 115
A.2.3 OB–FCA–CALLGAPREJ (35) Number of calls rejected by call gapping . . . . . . . . . . . . . 115
A.2.4 OB–FCA–CALLGAPREQ (34) Number of received call gap requests . . . . . . . . . . . . . . . 115
A.2.5 OB–FCA–CALLINFOREP (21) – Number of Call Information successful . . . . . . . . . . . . 115
A.2.6 OB–FCA–CALLINFOREQ (20) – Number of Call Information Request . . . . . . . . . . . . . . 115
A.2.7 OB–FCA–CANCEL (33) Number of Cancel Call successful . . . . . . . . . . . . . . . . . . . . . . . 115
A.2.8 OB–FCA–CANCELREQ (32) Number of Cancel Call Request . . . . . . . . . . . . . . . . . . . . 115
A.2.9 OB–FCA–DFC (25) – Number of Disconnect Forward Connection successful . . . . . . . 116
A.2.10 OB–FCA–DFCREQ (24) – Number of Disconnect Forward Connection Request . . . . 116
A.2.11 OB–FCA–DISCONLEG (37) – Number of Disconnect Leg successful . . . . . . . . . . . . . 116
A.2.12 OB–FCA–DISCONLEGREQ (36) – Number of Disconnect Leg Request . . . . . . . . . . . 116
A.2.13 OB–FCA–ETC (23) – Number of Establish Temporary Connection successful . . . . . . 116
A.2.14 OB–FCA–ETCREQ (22) – Number of Establish Temporary Connection request . . . . 116
A.2.15 OB–FCA–EVRPBCSMDP04 (09) – Number of Event Report BCSM at DP4 . . . . . . . . 116
A.2.18 OB–FCA–EVRPBCSMDP07 (05) – Number of Event Report BCSM sent at DP07 . . 116
A.2.20 OB–FCA–EVRPBCSMDP10 (12) – Number of Event Report BCSM at DP10 . . . . . . . 117
A.2.26 OB–FCA–FCI (29) – Number of Furnish Charging Information successful . . . . . . . . . . 117
A.2.27 OB–FCA–FCIREQ (28) – Number of Furnish Charging Information Request . . . . . . . 117
A.2.28 OB–FCA–INDPIDP02 (01) – Number of InitialDP sent at DP02 . . . . . . . . . . . . . . . . . . 117
A.2.29 OB–FCA–INDPIDP12 (03) – Number of InitialDP sent at DP12 . . . . . . . . . . . . . . . . . . 117
A.2.30 OB–FCA–INDPRDP02 (02) – Number of response to InitialDP sent at DP02 . . . . . . 117
A.2.31 OB–FCA–INDPRDP12 (04) – Number of response to InitialDP sent at DP12 . . . . . . 118
A.2.32 OB–FCA–REQBCSM (38) – Number of Request Report BSCM Event . . . . . . . . . . . . . 118
A.2.33 OB–FCA–RESETTIM (27) – Number of Reset Timer successful . . . . . . . . . . . . . . . . . 118
A.2.34 OB–FCA–RESETTIMREQ (26) – Number of Reset Timer request . . . . . . . . . . . . . . . . 118
A.2.35 OB–FCA–SCI (31) – Number of Send Charging Information successful . . . . . . . . . . . 118
A.2.36 OB–FCA–SCIREQ (30) – Number of Send Charging Information Request . . . . . . . . . 118
A.2.37 OB–FCA–SMINIDP1 – Number of initial–DP–SMS at DP1 . . . . . . . . . . . . . . . . . . . . . . 118
A.2.38 OB–FCA–SMINRDP1 – Number of response to Initial–DP–SMS at DP1 . . . . . . . . . . 118
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.2.39 OB–FCA–SMRQRPSMSEVT– Number of Request Event Report SMS Event . . . . . 118

A.2.40 OB–FCA–SMRQRPSMSDP2 – Number of Event Report SMS at DP2 . . . . . . . . . . . 118
A.2.41 OB–FCA–SMRQRPSMSDP3 – Number of Event Report SMS at DP3 . . . . . . . . . . . 118
ED 01
AAC020023800DS En 2 / 260
260
A.2.42 OB–FCA–SMRESETREQ – Number of Reset Timer SMS Request received from the
SCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
A.2.43 OB–FCA–SMRESETSUC – Number of Reset Timer SMS successful . . . . . . . . . . . . . 119
A.2.44 OB–FCA–SMFCIREC – Number of Furnish Charging Information SMS received . . . 119
A.2.45 OB–FCA–SMFCISUC – Number of Furnish Charging Information SMS successful . 119

A.3 ––––––––––––––––––– CCB counters (350) –––––––––––––––––––––––––– . . . . . . . . . 119

A.3.1 OB–FCCB–CALL–A (02) – Number of successful CCBS calls on the A side . . . . . . . . . 119
A.3.2 OB–FCCB–CALL–B (03) – Number of successful CCBS calls on the B side . . . . . . . . . 119
A.3.3 OB–FCCB–REC–CALLB (04) – Number of CCBS calls received on the B side . . . . . . 119
A.3.4 OB–FCCB–RQ (01) – Number of CCBS requests received from the MS . . . . . . . . . . . . 119
A.4 –––––––––––––––––––– CS counters (351) ––––––––––––––––––––––––– . . . . . . . . . . . 119
A.4.1 OB–FCS–ACFPC (02) – Number of forwarded call attempts per carrier . . . . . . . . . . . . 119
A.4.2 OB–FCS–AOCPC (01) – Number of outgoing call attempts per carrier . . . . . . . . . . . . . 119
A.4.3 OB–FCS–ARRPC (03) – Number of rerouted call attempts per carrier . . . . . . . . . . . . . 119
A.4.4 OB–FCS–IGWPC (04) – Number of incoming gateway calls per carrier . . . . . . . . . . . . 120
A.4.5 OB–FCS–ITCPC (05) – Number of terminating calls per carrier . . . . . . . . . . . . . . . . . . . 120
A.5 –––––––––––––––––––– CT counters (349) ––––––––––––––––––––––––– . . . . . . . . . . . 120
A.5.1 OB–FCT–INVTR (01) – Number of Activate Trace mode sent . . . . . . . . . . . . . . . . . . . . . 120
A.5.2 OB–FCT–INVTRHO (02) – Number of Activate Trace mode forwarded through Prepare
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
A.6 –––––––––––––––––––– DA counters (348) ––––––––––––––––––––––––– . . . . . . . . . . . 120
A.6.1 OB–FDA–CMMCONF (10) – Number of channel mode modify success . . . . . . . . . . . . 120
A.6.2 OB–FDA–CMMREQ (9) – Number of channel mode modify procedures . . . . . . . . . . . . 120
A.6.3 OB–FDA–COMPOC (21) – Outgoing data calls with compression. . . . . . . . . . . . . . . . . . 120
A.6.4 OB–FDA–COMPTC (22) – Terminated data calls with compression. . . . . . . . . . . . . . . . . 120
A.6.5 OB–FDA–EACK–OC (03) – IWF connection ack. unsuccessful for Outgoing data calls 121
A.6.6 OB–FDA–EACK–TC (04) – IWF connection ack. unsuccessful for Incoming data calls 121
A.6.7 OB–FDA–ESIMP (05) – IMPULSE error signalled by SMIM on data calls . . . . . . . . . . . 121
A.6.8 OB–FDA–ESON (06) – Error signalled by SMIM on data calls . . . . . . . . . . . . . . . . . . . . . 121
A.6.9 OB–FDA–FORCERL (11) – Data call release forced by SMIM . . . . . . . . . . . . . . . . . . . . . 121
A.6.10 OB–FDA–FRBUF (20) – Data call release forced by SMIM due to buffer overflow . . . 121
A.6.11 OB–FDA–FRFAX (18) – Data call release forced by SMIM due to FAX protocol problems .
121
A.6.12 OB–FDA–FRINT (19) – Data call release forced by SMIM due to internal failure . . . . 121
A.6.13 OB–FDA–FRRLP (15) – Data call release forced by SMIM due to RLP problems . . . 121
A.6.14 OB–FDA–FRSYNC (14)– Data call release forced by SMIM due to synchronisation prob-
lems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
A.6.15 OB–FDA–FRV42 (16) – Data call release forced by SMIM due to V.42 problems . . . . 122
A.6.16 OB–FDA–FRX25 (17) – Data call release forced by SMIM due to X.25 problems . . . 122
A.6.17 OB–FDA–MODREQ (12) – Number of In–Call Modification procedure request . . . . 122
A.6.18 OB–FDA–MODRES (13) – Number of In–Call Modification procedure result . . . . . . 122
A.6.19 OB–FDA–OCDATANS (33) – Number of answered originating fax/data calls. . . . . . . 122
A.6.20 OB–FDA–OCDATATT (31) – Number of originating fax/data call attempts. . . . . . . . . . 122
A.6.21 OB–FDA–OFBACK (27) – Number of HSCSD (multislot and 14.4 singleslot) outgoing
request leading to use of fallback GSM–BC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
A.6.22 OB–FDA–OHSCSD–REQ (25) – Number of HSCSD (multislot and 14.4 singleslot) outgo-
ing request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
A.6.23 OB–FDA–S14–4 (30) – Number of successful 14.4kbit/s singleslot call . . . . . . . . . . . 123
A.6.24 OB–FDA–SHSCSD (29) – Number of successful multislot call . . . . . . . . . . . . . . . . . . 123
A.6.25 OB–FDA–SIWF–OC (01) – IWF connection successful for Outgoing data calls . . . . . 123
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.6.26 OB–FDA–SIWF–TC (02) – IWF connection successful for Incoming data calls . . . . . 123
A.6.27 OB–FDA–SIWFOCREQ (07)– IWF connection request for Outgoing data calls . . . . . 123
A.6.28 OB–FDA–SIWFTCREQ (08)– IWF connection request for Incoming data calls . . . . . 123
A.6.29 OB–FDA–TCDATANS (34) – Number of answered terminated fax/data calls. . . . . . . 123
ED 01
AAC020023800DS En 3 / 260
260
A.6.30 OB–FDA–TCDATATT (32) – Number of terminated fax/data call attempts. . . . . . . . . . 123
A.6.31 OB–FDA–TFBACK (28) – Number of HSCSD (multislot and 14.4 singleslot) terminating
request leading to use of fallback GSM–BC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
A.6.32 OB–FDA–THSCSD–REQ(26) – Number of HSCSD (multislot and 14.4 singleslot) termi-
nating request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

A.6.33 OB–FDA–UIMREQ (23) – Number of User Initiated Modification procedure request . 124
A.6.34 OB–FDA–UIMRES (24) – Number of User Initiated Modification procedure result . . 124
A.6.35 OB–FDA–UMMOC (25) – Number of UMTS Multimedia OC calls. . . . . . . . . . . . . . . . . 124
A.6.36 OB–FDA–UMMTC (26) – Number of UMTS Multimedia TC calls. . . . . . . . . . . . . . . . . . 124
A.6.37 OB–FDA–UBS20OC (27) – Number of UMTS BS20 OC calls. . . . . . . . . . . . . . . . . . . . . 124
A.6.38 OB–FDA–UBS20TC (28) – Number of UMTS BS20 TC calls. . . . . . . . . . . . . . . . . . . . . 124
A.7 –––––––––––––––––––– DN counters (331) ––––––––––––––––––––––––– . . . . . . . . . . . 124
A.7.1 OB–FDN–CONFUSION (01) – confusion messages emitted toward a BSC . . . . . . . . . 124
A.8 –––––––––––––––––––– GP counters (335) ––––––––––––––––––––––––– . . . . . . . . . . . 125
A.8.1 OB–FGP–ERP–CGS (02) – Paging failures (calls only) on Gs–interface . . . . . . . . . . . 125
A.8.2 OB–FGP–ERP–UGS (03) – Paging failures for call unrelated services on Gs–interface 125
A.8.3 OB–FGP–SRP–GS (01) – Paging repetitions on Gs–interface . . . . . . . . . . . . . . . . . . . . . 125
A.9 –––––––––––––––––––– HO counters (307) ––––––––––––––––––––––––– . . . . . . . . . . . 125
A.9.1 OB–FHO–S3GCOMA (74) – Number of handover command (2G –> 3G intra–MSC hand-
over) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
A.9.2 OB–FHO–S3GCOME (78) – Number of handover command at controlling MSC (2G –> 3G
inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
A.9.3 OB–FHO–S3GCOMS (82) – Number of handover command at serving MSC (2G –> 3G
subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
A.9.4 OB–FHO–S3GCOMPA (75) – Number of handover complete (2G –> 3G intra–MSC hand-
over) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.5 OB–FHO–S3GCOMPE (79) – Number of handover complete at controlling MSC (2G –> 3G
inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.6 OB–FHO–S3GCOMPCS (86) – Number of handover complete at controlling MSC (2G –>
3G subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.7 OB–FHO–S3GCOMPS (83) – Number of handover complete at serving MSC (2G –> 3G
subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.8 OB–FHO–S3GHORQA (73) – Number of handover required (2G –> 3G intra–MSC hand-
over) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.9 OB–FHO–S3GPREPE (77) – Number of handover preparation request at controlling MSC
(2G –> 3G inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.10 OB–FHO–S3GPREPCS (85) – Number of handover preparation request at controlling
MSC (2G –> 3G subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.11 OB–FHO–S3GPREPSS (81) – Number of handover preparation request at serving MSC
(2G –> 3G subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.9.12 OB–FHO–S3GRERA (76) – Number of handover process released (2G –> 3G intra–MSC
handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
A.9.13 OB–FHO–S3GRERE (80) – Number of handover process released at controlling MSC
A.9.14 OB–FHO–S3GRERCS (87) – Number of handover process released at controlling MSC
(2G –> 3G subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
A.9.15 OB–FHO–S3GRERSS (84) – Number of handover process released at serving MSC (2G
–> 3G subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
A.9.16 OB–FHO–EHOFFM (07) – HO failures signalled by the mobile stations . . . . . . . . . . . . 127
A.9.17 OB–FHO–EHOFFM–2 (51) – HO failures signalled by the mobile stations . . . . . . . . . 127
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.9.18 OB–FHO–EHOFFMA (28) – HO failures signalled by the mobile stations . . . . . . . . . . 127

A.9.19 OB–FHO–EHOFFMA–2 (54) – HO failures signalled by the mobile stations . . . . . . . . 127
A.9.20 OB–FHO–EHOFFMAGLO (68) – HO failures signalled by the mobile stations (global) 128
A.9.21 OB–FHO–EHOFFMB (29) – HO failures signalled by the mobile stations . . . . . . . . . . 128
ED 01
AAC020023800DS En 4 / 260
260
A.9.22 OB–FHO–EHOFFMB–2 (55) – HO failures signalled by the mobile stations . . . . . . . . 128
A.9.23 OB–FHO–EHOFFMBGLO (69) – HO failures signalled by the mobile stations (global) 128
A.9.24 OB–FHO–EHOIAMSC (04) – Intra–MSC HO failures signalled by the network . . . . . . 128
A.9.25 OB–FHO–EHOIAMSC–2 (49) – Intra–MSC HO failures signalled by the network . . . 128
A.9.26 OB–FHO–EHOIRMSC (03) – Inter–MSC HO failures signalled by the network . . . . . 128

A.9.27 OB–FHO–EHOIRMSC–2 (48) – Inter–MSC HO failures signalled by the network . . . 128

A.9.28 OB–FHO–EHOIRMSCGLO (65) – Inter–MSC HO failures signalled by the network
(global) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
A.9.29 OB–FHO–EHOSMSCB (25) – HO failures detected by network . . . . . . . . . . . . . . . . . . 129
A.9.30 OB–FHO–EHOSMSCB–2 (53) – HO failures detected by network . . . . . . . . . . . . . . . . 129
A.9.31 OB–FHO–EHOSMSCBGLO (67) – HO failures detected by network (global) . . . . . . . 129
A.9.32 OB–FHO–REJ (58) – Incoming HO rejected for regulation cause . . . . . . . . . . . . . . . . . 129
A.9.33 OB–FHO–SDTR1 (05) – HO required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
A.9.34 OB–FHO–SDTR2 (09) – HO started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
A.9.35 OB–FHO–SDTR3 (10) – HO updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
A.9.36 OB–FHO–SDTR4 (11) – Repeated HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
A.9.37 OB–FHO–SDTR5 (12) – HO required on signalling channel . . . . . . . . . . . . . . . . . . . . . . 129
A.9.38 OB–FHO–SDTR6 (72) – HO required with cause ’switch circuit pool’ . . . . . . . . . . . . . 130
A.9.39 OB–FHO–SHOACMB (26) – HO reception in target MSC . . . . . . . . . . . . . . . . . . . . . . . . 130
A.9.40 OB–FHO–SHOACOMP (17) – Efficient intra–MSC HO . . . . . . . . . . . . . . . . . . . . . . . . . . 130
A.9.41 OB–FHO–SHOAREQ (16) – Attempted intra–MSC HO . . . . . . . . . . . . . . . . . . . . . . . . . . 130
A.9.42 OB–FHO–SHOAREQACK (27) – Efficient intra–MSC HO resource assignment . . . . . 130
A.9.43 OB–FHO–SHOBREQ (30) – Attempted inter–MSC HO resource assignment . . . . . . . 130
A.9.44 OB–FHO–SHOBREQACK (31) – Efficient inter–MSC HO resource assignment . . . . . 130
A.9.45 OB–FHO–SHOC (06) – HO commands (intra–MSC HO) . . . . . . . . . . . . . . . . . . . . . . . . 130
A.9.46 OB–FHO–SHOC–2 (50) – HO commands (intra–MSC HO) . . . . . . . . . . . . . . . . . . . . . . 130
A.9.47 OB–FHO–SHOCIR (32) – HO commands (inter–MSC HO) . . . . . . . . . . . . . . . . . . . . . . 130
A.9.48 OB–FHO–SHOCIR–2 (56) – HO commands (inter–MSC HO) . . . . . . . . . . . . . . . . . . . . 131
A.9.49 OB–FHO–SHOCIRGLO (70) – HO commands (inter–MSC HO) (global) . . . . . . . . . . . 131
A.9.50 OB–FHO–SHOCS (33) – HO commands (subsequent HO) . . . . . . . . . . . . . . . . . . . . . . 131
A.9.51 OB–FHO–SHOCS–2 (57) – HO commands (subsequent HO) . . . . . . . . . . . . . . . . . . . . 131
A.9.52 OB–FHO–SHOCSGLO (71) – HO commands (subsequent HO) . . . . . . . . . . . . . . . . . . 131
A.9.53 OB–FHO–SHOIAMSC (01) – Efficient intra–MSC handovers . . . . . . . . . . . . . . . . . . . . . 131
A.9.54 OB–FHO–SHOIAMSC–2 (46) – Efficient intra–MSC handovers . . . . . . . . . . . . . . . . . . . 131
A.9.55 OB–FHO–SHOIMSCA (02) – Efficient outgoing inter–MSC HO . . . . . . . . . . . . . . . . . . 131
A.9.56 OB–FHO–SHOIMSCA–2 (47) – Efficient outgoing inter–MSC HO . . . . . . . . . . . . . . . . 131
A.9.57 OB–FHO–SHOIMSCAGLO (64) – Efficient outgoing inter–MSC HO (global) . . . . . . 131
A.9.58 OB–FHO–SHOIMSCB (08) – Efficient incoming inter–MSC and subsequent HO (target) .
132
A.9.59 OB–FHO–SHOIPHORA (34) – Efficient outgoing inter–MSC HO . . . . . . . . . . . . . . . . . . 132
A.9.60 OB–FHO–SHOIPHORAGLO (63) – Efficient outgoing inter–MSC HO (global) . . . . . . 132
A.9.61 OB–FHO–SHOIPIVA (13) – Attempted outgoing inter–MSC HO . . . . . . . . . . . . . . . . . . 132
A.9.62 OB–FHO–SHOIPIVAGLO (59) – Attempted outgoing inter–MSC HO (global) . . . . . . . 132
A.9.63 OB–FHO–SHOIPIVB (15) – Attempted incoming inter–MSC HO . . . . . . . . . . . . . . . . . . 132
A.9.64 OB–FHO–SHOIRIABSC (35) – Inter–BSC HO interruption by intra BSC HO . . . . . . . 132
A.9.65 OB–FHO–SHOISESA (14) – Efficient outgoing inter–MSC HO . . . . . . . . . . . . . . . . . . . 132
A.9.66 OB–FHO–SHOISESAGLO (60) – Efficient outgoing inter–MSC HO (global) . . . . . . . . 132
A.9.67 OB–FHO–SHOREL (36) – intra–MSC HO process release . . . . . . . . . . . . . . . . . . . . . . 132
A.9.68 OB–FHO–SHORELA (37) – inter–MSC HO process release in controlling . . . . . . . . . 133
A.9.69 OB–FHO–SHORELB (38) – HO process release in Target MSC . . . . . . . . . . . . . . . . . . 133
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.9.70 OB–FHO–SHORMSCA (19) – Efficient incoming return subsequent HO . . . . . . . . . . . 133

A.9.71 OB–FHO–SHORPSIA (18) – Attempted incoming return subsequent HO . . . . . . . . . . 133
A.9.72 OB–FHO–SHORSEL (41) – HO resource reselections . . . . . . . . . . . . . . . . . . . . . . . . . . 133
A.9.73 OB–FHO–SHOSAREQ (42) – Attempted return subseq HO resource assignment . . 133
ED 01
AAC020023800DS En 5 / 260
260
A.9.74 OB–FHO–SHOSAREQACK (43)– Efficient return subs HO resource assignment . . . 133
A.9.75 OB–FHO–SHOSMSCA (21) – Efficient incoming subsequent HO . . . . . . . . . . . . . . . . . 133
A.9.76 OB–FHO–SHOSMSCB (24) – Efficient outgoing subsequent HO . . . . . . . . . . . . . . . . . 133
A.9.77 OB–FHO–SHOSMSCB–2 (52) – Efficient outgoing subsequent HO . . . . . . . . . . . . . . . 134
A.9.78 OB–FHO–SHOSPHORA (44) – Efficient subsequent HO resource assignment . . . . . 134

A.9.79 OB–FHO–SHOSPSHORA (45) – Efficient return subs HO in controlling MSC . . . . . . 134

A.9.80 OB–FHO–SHOSPSIA (20) – Attempted incoming subsequent HO . . . . . . . . . . . . . . . . 134
A.9.81 OB–FHO–SHOSPSIB (22) – Attempted outgoing subsequent HO . . . . . . . . . . . . . . . . 134
A.9.82 OB–FHO–SHOSPSIBGLO (61) – Attempted outgoing subsequent HO (global) . . . . . 134
A.9.83 OB–FHO–SHOSRELA (39) – SUBS return HO process release . . . . . . . . . . . . . . . . . . 134
A.9.84 OB–FHO–SHOSRELB (40) – SUBS HO process release in Serving MSC . . . . . . . . . 134
A.9.85 OB–FHO–SHOSSERB (23) – Efficient outgoing subsequent HO . . . . . . . . . . . . . . . . . . 134
A.9.86 OB–FHO–SHOSSERBGLO (62) – Efficient outgoing subsequent HO (global) . . . . . . 135
A.10 ––––––––––––––––––––– IN counters (399) –––––––––––––––––––––––– . . . . . . . . . . 135
A.10.1 OB–FIN–CONNECT (04) – Number of Connect at the IN interface . . . . . . . . . . . . . . . 135
A.10.2 OB–FIN–CONTINUE (05) – Number of Continue at the IN interface . . . . . . . . . . . . . . 135
A.10.3 OB–FIN–INDPE (02) – Number of InitialDP errors at the IN interface . . . . . . . . . . . . . 135
A.10.4 OB–FIN–INDPI (01) – Number of InitialDP invoke at the IN interface . . . . . . . . . . . . . 135
A.10.5 OB–FIN–NETWORK (06) – Number of originating calls routed by a network server . 135
A.10.6 OB–FIN–RELCALL (03) – Number of release call at the IN interface . . . . . . . . . . . . . . 135
A.11 –––––––––––––––––––– LCS counters (362) ––––––––––––––––––––––––– . . . . . . . . . 135
A.11.1 OB–FLCS–MTLRREQ (03) Global number of Mobile terminating location request MT_LR
received from GMLC for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
A.11.2 OB–FLCS–CURMTLRREQ (04) Number of Call unrelated Mobile terminating location
request MT_LR received from GMLC for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
A.11.3 OB–FLCS–CURMTLRRES (05) Number of Call unrelated Mobile terminating location
request MT_LR result sent to GMLC for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.4 OB–FLCS–CRMTLRREQ (06) Number of Call related Mobile terminating location request
MT_LR received from GMLC for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.5 OB–FLCS–CRMTLRRES (07) Number of Call related Mobile terminating location request
MT_LR result sent to GMLC for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.6 OB–FLCS–LOCREQ (01) Number of location request messages sent for LCS services . . .
136
A.11.7 OB–FLCS–LOCRES (02) Number of location response messages received for LCS ser-
vices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.8 OB–FLCS–LOCNOTS (10) Number of Location Notification sent to the MS for Mobile Ter-
minating location request MT_LR LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.9 OB–FLCS–LOCNOTR (11) Number of Location Notification result received from the MS
for Mobile Terminating location request MT_LR LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.10 OB–FLCS–MOLRREL (19) Number of Mobile Originating location request MO_LR proce-
dure release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.11.11 OB–FLCS–MOLRREQ (12) Number of Mobile Originating location request MO_LR
received from MS for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
A.11.12 OB–FLCS–MOLRRES (13) Number of Mobile Originating location request MO_LR result
sent to MS for LCS services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
A.11.13 OB–FLCS–LOCREPIMO (14) Number of Subscriber Location report invoke sent to the
GMLC for Mobile Originating location request MO_LR LCS services . . . . . . . . . . . . . . . . . . . . . 137
A.11.14 OB–FLCS–LOCREPRMO (15) Number of Subscriber Location report result received
from the GMLC for Mobile Originating location request MO_LR LCS services . . . . . . . . . . . . . 137
A.11.15 OB–FLCS–LOCREPINI (16) Number of Subscriber Location report invoke sent to the
1AA 00014 0004 (9007) A4 – ALICE 04.10
GMLC for Network Initiated location request NI_LR LCS services . . . . . . . . . . . . . . . . . . . . . . . 137
A.11.16 OB–FLCS–LOCREPRNI (17) Number of Subscriber Location report result received from
the GMLC for Network Initiated location request NI_LR LCS services . . . . . . . . . . . . . . . . . . . . 137
ED 01
AAC020023800DS En 6 / 260
260
A.11.17 OB–FLCS–MTLRREL (18) Number of Mobile Terminating location request MT_LR proce-
dure release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
A.12 –––––––––––––––––––– LD counters (327) ––––––––––––––––––––––––– . . . . . . . . . . 137
A.12.1 OB–FLD–OVL (01) – OVERLOAD message from BSC/RNC . . . . . . . . . . . . . . . . . . . . . 137
A.13 –––––––––––––––––––– LR counters (304) ––––––––––––––––––––––––– . . . . . . . . . . 138

A.13.1 OB–FLR–ATT (02) – IMSI attach received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

A.13.2 OB–FLR–DET (03) – IMSI detach indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
A.13.3 OB–FLR–LOC–CTRL (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
A.13.4 OB–FLR–LOC–REP (11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
A.13.5 OB–FLR–LR–REJ (09) – Rejected non periodic LR for regulation cause . . . . . . . . . . . 138
A.13.6 OB–FLR–LRP–REJ (08) – Rejected periodic LR for regulation cause . . . . . . . . . . . . . 138
A.13.7 OB–FLR–REL (07) – Location registration process release . . . . . . . . . . . . . . . . . . . . . . 138
A.13.8 OB–FLR–SLU (05) – Registration requests for normal LR . . . . . . . . . . . . . . . . . . . . . . . 138
A.13.9 OB–FLR–SLUA (01) – Registration requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
A.13.10 OB–FLR–SLUP (06) – Registration requests for periodic LR . . . . . . . . . . . . . . . . . . . . 139
A.13.11 OB–FLR–SLUR (04) – Accepted registration requests . . . . . . . . . . . . . . . . . . . . . . . . . . 139
A.14 –––––––––––––––––––– LSA counters (359) ––––––––––––––––––––––––– . . . . . . . . 139
A.14.1 OB–FLSA–MMINF (01) – Number of MM information messages due to SoLSA feature
sent to the MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
A.14.2 OB–FLSA–LSAINF (02) – Number of LSA information messages . . . . . . . . . . . . . . . . . 139
A.15 –––––––––––––––––––– MLP counters (361) ––––––––––––––––––––––––– . . . . . . . . 139
A.15.1 OB–FMLP–MOPROC (01) – Number of authorized MO calls . . . . . . . . . . . . . . . . . . . . . 139
A.15.2 OB–FMLP–MOALERT (02) – Number of delivered MO calls . . . . . . . . . . . . . . . . . . . . . 139
A.15.3 OB–FMLP–MTSETUP (03) – Number of authorized MT calls . . . . . . . . . . . . . . . . . . . . 139
A.15.4 OB–FMLP–MTALERT (04) – Number of delivered MT calls . . . . . . . . . . . . . . . . . . . . . . 139
A.16 –––––––––––––––––––– MO (Short Message Originating) counters (346) . . . . . . . . . . 140
A.16.1 OB–FMO–IFSMREQ (07) – Incoming forward SM request (SMS–IWMSC) . . . . . . . . . 140
A.16.2 OB–FMO–MSALREQ (02) – Reception of RP–SMMA . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
A.16.3 OB–FMO–MSTRREQ (01) – Reception of RP–DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
A.16.4 OB–FMO–OFSMREQ (05) – Outgoing forward SM request (VMSC) . . . . . . . . . . . . . . 140
A.16.5 OB–FMO–REL (11) – SMO procedure release (VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . 140
A.16.6 OB–FMO–SALERT (04) – Acknowledgment of an RP–SMMA . . . . . . . . . . . . . . . . . . . . 140
A.16.7 OB–FMO–SCACK (10) – Successful transfer to the SC (SMS–IWMSC) . . . . . . . . . . . 140
A.16.8 OB–FMO–SCREQ (09) – Transfer of a SM to the SC (SMS–IWMSC) . . . . . . . . . . . . . 140
A.16.9 OB–FMO–SIFSM (06) – Incoming succesful forward (VMSC) . . . . . . . . . . . . . . . . . . . . 140
A.16.10 OB–FMO–SOFSM (08) – Outgoing successful forward (SMS–IWMSC) . . . . . . . . . . 140
A.16.11 OB–FMO–SSMTR (03) – Acknowledgment of an RP–DATA . . . . . . . . . . . . . . . . . . . . 140
A.17 –––––––––––––––––––– MP counters (323) –––––––––––––––––––––––– . . . . . . . . . . . 141
A.17.1 OB–FMP–START (01) – Request to start a multi–party call . . . . . . . . . . . . . . . . . . . . . . 141
A.17.2 OB–FMP–SUCCESS (02) – Successful multiparty calls . . . . . . . . . . . . . . . . . . . . . . . . . 141
A.18 –––––––––––––––––––– NP counters (358) –––––––––––––––––––––––– . . . . . . . . . . . 141
A.18.1 OB–FNP–FQOD (07) – Call forwarding NPDB query on digits analysis (OQoD) . . . . 141
A.18.2 OB–FNP–FROD (08) – Calls forwarded to a ported MS – OQoD – . . . . . . . . . . . . . . . 141
A.18.3 OB–FNP–NPDBF (09) – NPDB query failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
A.18.4 OB–FNP–OQOD (05) – Originating NPDB query on digits analysis (OQoD) . . . . . . . 141
A.18.5 OB–FNP–OROD (06) – Originating calls to a ported MS – OQoD – . . . . . . . . . . . . . . . 141
A.18.6 OB–FNP–QOHR (01) – Terminating NPDB query on HLR release (QoHR) . . . . . . . . . 141
A.18.7 OB–FNP–ROHR (02) – Terminating calls to a ported MS – QoHR – . . . . . . . . . . . . . . 142
A.18.8 OB–FNP–RRPLMN (09) – Calls rerouted to a ported subscriber toward a given PLMN . . .
142
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.18.9 OB–FNP–TQOD (03) – Terminating NPDB query on digits analysis (TQoD) . . . . . . . . 142
A.18.10 OB–FNP–TROD (04) – Terminating calls to a ported MS – TQoD – . . . . . . . . . . . . . 142
A.19 –––––––––––––––––––– OC counters (305) –––––––––––––––––––––––– . . . . . . . . . . . 142
A.19.1 OB–FOC–ALERT (09) – MS originating calls with alerting . . . . . . . . . . . . . . . . . . . . . . . 142
ED 01
AAC020023800DS En 7 / 260
260
A.19.2 OB–FOC–C–REL (29) – OC releases during conversation phase . . . . . . . . . . . . . . . . . 142
A.19.3 OB–FOC–CALPROC (08) – Authorized MS originating calls . . . . . . . . . . . . . . . . . . . . . 142
A.19.4 OB–FOC–CGAP (30) – Rejected OC for call rate control cause . . . . . . . . . . . . . . . . . . 142
A.19.5 OB–FOC–CONNACK (13) – Established MS originating calls . . . . . . . . . . . . . . . . . . . . 142
A.19.6 OB–FOC–CONNECT (11) – MS originating calls with called response . . . . . . . . . . . . . 143

A.19.7 OB–FOC–DIRCONNECT (12) – Established MS originating calls . . . . . . . . . . . . . . . . . 143

A.19.8 OB–FOC–DTMFCAL (07) – Calls requesting DTMF transmission. . . . . . . . . . . . . . . . . 143
A.19.9 OB–FOC–DTMFREQ (06) – START DTMF received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
A.19.10 OB–FOC–DURC–BS (27) – Conversation phase duration for originating calls . . . . 143
A.19.11 OB–FOC–DURE–BS (23) – Establishment phase duration for originating calls . . . . 143
A.19.12 OB–FOC–DURS–BS (25) – Ringing phase duration for originating calls . . . . . . . . . . 143
A.19.13 OB–FOC–EAEMOB (04) – Failures on call attempts from the MS . . . . . . . . . . . . . . . . 143
A.19.14 OB–FOC–EMIMEI (17) – Number of emergency call on IMEI . . . . . . . . . . . . . . . . . . . 143
A.19.15 OB–FOC–NBRC–BS (28) – Number of calls taken into account in OB–FOC–DURC–BS
counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.16 OB–FOC–NBRE–BS (24) – Number of calls taken into account in OB–FOC–DURE–BS
counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.17 OB–FOC–NBRS–BS (26) – Number of calls taken into account in OB–FOC–DURS–BS
counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.18 OB–FOC–PROGRESS (10) – MS originating calls with progress . . . . . . . . . . . . . . . . 144
A.19.19 OB–FOC–REJ (16) – Rejected OC for regulation cause . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.20 OB–FOC–REL (14) – OC releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.21 OB–FOC–REQ–BS (15) – Outgoing call request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.22 OB–FOC–SAEMOB (03) – Call attempts from the MS. . . . . . . . . . . . . . . . . . . . . . . . . . 144
A.19.23 OB–FOC–SETUP (05) – Call setup requests from the MS . . . . . . . . . . . . . . . . . . . . . . 144
A.19.24 OB–FOC–SHOP–SETUP (21) – Single Hop telephony Call setup requests from the MS .
144
A.19.25 OB–FOC–SODBOC (18) – Number of OC refused due to ODB of outgoing calls . . 145
A.19.26 OB–FOC–SODBPR (19) – Number of OC refused due to ODB of premium rate calls . . . .
145
A.19.27 OB–FOC–SODBSH (20) – Number of CH invocations refused due to ODB of SS man-
agement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
A.19.28 OB–FOC–SRSU (01) – Emergency service requests . . . . . . . . . . . . . . . . . . . . . . . . . . 145
A.20 –––––––––––––––––––– OR counters (347) –––––––––––––––––––––––– . . . . . . . . . . . 145
A.20.1 OB–FOR–BASICOR (02) – Optimal routeing for basic MS to MS calls . . . . . . . . . . . . . 145
A.20.2 OB–FOR–EARLYCF (03) – Number of early calls forwarding . . . . . . . . . . . . . . . . . . . . . 145
A.20.3 OB–FOR–LATECF (05) – Number of late calls forwarding in the GMSC . . . . . . . . . . . 145
A.20.4 OB–FOR–RCHINV–GMSC (04) – Number of RCH invoke received in the GMSC . . . 145
A.20.5 OB–FOR–RCHINV–VMSC (06) – Number of RCH invoke sent by the VMSC . . . . . . . 145
A.20.6 OB–FOR–RCHRES (07) – Number of RCH result received in the VMSC . . . . . . . . . . 146
A.20.7 OB–FOR–SRI–FOR (08) – Number of ’send routing info’ invoke with interrogation type
’forwarding’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
A.20.8 OB–FOR–SRIINV (01) – Number of SRI invoke with OR interrogation . . . . . . . . . . . . . 146
A.21 –––––––––––––––––––– PG counters (303) ––––––––––––––––––––––––– . . . . . . . . . . 146
A.21.1 OB–FPG–BUSY–C (13) – Terminating calls towards busy MS (calls only) . . . . . . . . . . 146
A.21.2 OB–FPG–BUSY–SM (15) – Terminating short messages towards busy MS . . . . . . . . 146
A.21.3 OB–FPG–BUSYMS (03) – Terminating calls towards busy MS. . . . . . . . . . . . . . . . . . . . 146
A.21.4 OB–FPG–ERP (02) – Paging failures on A–interface or Iu interface . . . . . . . . . . . . . . . 146
A.21.5 OB–FPG–ERP–C (12) – Paging failures (calls only) on A–interface or Iu interface . . 146
A.21.6 OB–FPG–ERP–SM (14) – Paging failures (short messages) on A–interface or Iu interface
1AA 00014 0004 (9007) A4 – ALICE 04.10
147
A.21.7 OB–FPG–FBDCELL (07) – Number of paging on the forbidden cells of the VMSC. . . 147
A.21.8 OB–FPG–HPA (09) – Paging with Alerting Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
A.21.9 OB–FPG–NACK (11) – Paging Nack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
ED 01
AAC020023800DS En 8 / 260
260
A.21.10 OB–FPG–OPINTA (06) – Operator calls with intervention allowed . . . . . . . . . . . . . . . 147
A.21.11 OB–FPG–OPNDUB (05) – Operator calls toward busy MS . . . . . . . . . . . . . . . . . . . . . . 147
A.21.12 OB–FPG–OTC (08) – Number of successful paging for Optimized Terminating Call 147
A.21.13 OB–FPG–PAGEIMSI (04) – Page with IMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
A.21.14 OB–FPG–SHPA (10) – Successful Paging with Alerting Required. . . . . . . . . . . . . . . . 147

A.21.15 OB–FPG–SRP (01) – Paging repetitions on A–interface or Iu interface . . . . . . . . . . . 147

A.22 –––––––––––––––––––– ALR counters (360) ––––––––––––––––––––––––– . . . . . . . . 148
A.22.1 OB–FALR–PAGING (01) – Paging sent on A–interface or Iu interface for ALR Automatic
location retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.23 –––––––––––––––––––– RE counters (308) ––––––––––––––––––––––––– . . . . . . . . . . 148
A.23.1 OB–FRE–S2GPREPE (37) – Number of relocation preparation request at controlling MSC
(3G –> 2G inter–MSC handover) (intra–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.23.2 OB–FRE–S2GPREPEE (47) – Number of relocation preparation request at controlling
MSC (3G –> 2G inter–MSC handover) (inter–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.23.3 OB–FRE–S2GPREPSS (42) – Number of relocation preparation request at serving MSC
(subsequent 3G –> 2G inter–MSC handover) (intra–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.23.4 OB–FRE–S2GPREPSSE (51) – Number of relocation preparation request at serving MSC
(subsequent 3G –> 2G inter–MSC handover) (inter–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
A.23.5 OB–FRE–S2GRECANA (33) – Number of relocation cancelled (3G –> 2G intra–MSC
handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.6 OB–FRE–S2GRECANE (38) – Number of relocation cancelled at controlling MSC (3G –>
2G inter–MSC handover) (intra–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.7 OB–FRE–S2GRECANEE (48) – Number of relocation cancelled at controlling MSC (3G
–> 2G inter–MSC handover) (inter–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.8 OB–FRE–S2GRECANS (43) – Number of relocation cancelled at serving MSC (3G –>
2G subsequent inter–MSC handover) (intra–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.9 OB–FRE–S2GRECANSE (52) – Number of relocation cancelled at serving MSC (3G –>
2G subsequent inter–MSC handover) (inter–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.10 OB–FRE–S2GRECOMA (34) – Number of relocation command (3G –> 2G intra–MSC
handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.11 OB–FRE–S2GRECOME (39) – Number of relocation command at controlling MSC (3G
–> 2G inter–MSC handover) (intra–PLMN ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.12 OB–FRE–S2GRECOMEE (49) – Number of relocation command at controlling MSC (3G
–> 2G inter–MSC handover) (inter–PLMN ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
A.23.13 OB–FRE–S2GRECOMS (44) – Number of relocation command at serving MSC (3G –>
2G subsequent inter–MSC handover) (intra–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.23.14 OB–FRE–S2GRECOMSE (53) – Number of relocation command at serving MSC (3G –>
2G subsequent inter–MSC handover) (inter–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.23.15 OB–FRE–S2GRECOMPA (35) – Number of relocation complete (3G –> 2G intra–MSC
handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.23.16 OB–FRE–S2GRECOMPE (40) – Number of relocation complete at controlling MSC (3G
–> 2G inter–MSC handover) (intra–PLMN ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.23.17 OB–FRE–S2GRECOMPEE (50) – Number of relocation complete at controlling MSC
(3G –> 2G inter–MSC handover) (inter–PLMN ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.23.18 OB–FRE–S2GRECOMPS (45) – Number of relocation complete at serving MSC (3G –>
2G subsequent inter–MSC handover) (intra–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A.23.19 OB–FRE–S2GRECOMPSE (54) – Number of relocation complete at serving MSC (3G
–> 2G subsequent inter–MSC handover) (inter–PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
A.23.20 OB–FRE–S2GRERA (36) – Number of relocation process released (3G –> 2G intra–
MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.23.21 OB–FRE–S2GRERE (41) – Number of relocation process released at controlling MSC

A.23.22 OB–FRE–S2GRERSS (46) – Number of relocation process released at serving MSC (3G
–> 2G subsequent inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
ED 01
AAC020023800DS En 9 / 260
260
A.23.23 OB–FRE–S2GRERQA (32) – Number of relocation required (3G –> 2G intra–MSC hand-
over) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
A.23.24 OB–FRE–SACMTE (18) – Number of successful relocation preparation at target MSC
(inter–MSC and subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
A.23.25 OB–FRE–SPREPE (10) – Number of relocation preparation request at controlling MSC

(inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

A.23.26 OB–FRE–SPREPCS (21) – Number of relocation preparation request at controlling MSC
(subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.23.27 OB–FRE–SPREPSS (24) – Number of relocation preparation request at serving MSC
A.23.28 OB–FRE–SPREPTE (15) – Number of relocation preparation request at target MSC
(inter–MSC and subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.23.29 OB–FRE–SRECANA (06) – Number of relocation cancelled (intra–MSC relocation) 152
A.23.30 OB–FRE–SRECANE (11) – Number of relocation cancelled at controlling MSC (inter–
MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.23.31 OB–FRE–SRECANS (25) – Number of relocation cancelled at serving MSC (subsequent
inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.23.32 OB–FRE–SRECOM (02) – Number of relocation command (all type of relocation) . 152
A.23.33 OB–FRE–SRECOMA (07) – Number of relocation command (intra–MSC relocation) 152
A.23.34 OB–FRE–SRECOME (12) – Number of relocation command at controlling MSC (inter–
MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
A.23.35 OB–FRE–SRECOMS (26) – Number of relocation command at serving MSC (subse-
quent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
A.23.36 OB–FRE–SRECOMPA (08) – Number of relocation complete (intra–MSC relocation) . . .
153
A.23.37 OB–FRE–SRECOMPE (13) – Number of relocation complete at controlling MSC (inter–
MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
A.23.38 OB–FRE–SRECOMPCS (22) – Number of relocation complete at controlling MSC (sub-
sequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
A.23.39 OB–FRE–SRECOMPS (27) – Number of relocation complete at serving MSC (subse-
quent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
A.23.40 OB–FRE–SRECOMPR (31) – Number of relocation complete at target MSC (subsequent
return inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
A.23.41 OB–FRE–SRECOMPTE (19) – Number of relocation complete at target MSC (inter–
MSC and subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
A.23.42 OB–FRE–SRERA (09) – Number of relocation process released (intra–MSC relocation) .
153
A.23.43 OB–FRE–SRERCE (14) – Number of relocation process released at controlling MSC
(inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
A.23.44 OB–FRE–SRERCS (23) – Number of relocation process released at controlling MSC
A.23.45 OB–FRE–SRERSS (28) – Number of relocation process released at serving MSC (sub-
sequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
A.23.46 OB–FRE–SRERTE (20) – Number of relocation process released at target MSC (inter–
MSC and inter–MSC subsequent relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
A.23.47 OB–FRE–SRERQ (01) – Number of relocation required (all type of relocation) . . . . 154
A.23.48 OB–FRE–SRERQA (05) – Number of relocation required (intra–MSC relocation) . . 154
A.23.49 OB–FRE–SREREQA (03) – Number of relocation resource allocation request (intra–
MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
A.23.50 OB–FRE–SREREQE (16) – Number of relocation resource allocation request at target
1AA 00014 0004 (9007) A4 – ALICE 04.10
MSC (inter–MSC and subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

A.23.51 OB–FRE–SREREQR (29) – Number of relocation resource allocation request at target
MSC (subsequent return inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
ED 01
AAC020023800DS En 10 / 260
260
A.23.52 OB–FRE–SREREQKA (04) – Number of relocation resource allocation acknowledge
(intra–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
A.23.53 OB–FRE–SREREQKE (17) – Number of relocation resource allocation acknowledge at
target MSC (inter–MSC and subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . 155
A.23.54 OB–FRE–SREREQKR (30) – Number of relocation resource allocation acknowledge at

target MSC (subsequent return inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

A.24 –––––––––––––––––––– RM counters (315) –––––––––––––––––––––––– . . . . . . . . . . 155
A.24.1 OB–FRM–EASR (02) – traffic channel assignment failures . . . . . . . . . . . . . . . . . . . . . . . 155
A.24.2 OB–FRM–EASR–2 (12) – traffic channel assignment failures for pool related causes 155
A.24.3 OB–FRM–ESVUNVL (11) – Speech version requested unavailable . . . . . . . . . . . . . . . 156
A.24.4 OB–FRM–FAXDOWN (15) – Forced downgrading for fax calls . . . . . . . . . . . . . . . . . . . 156
A.24.5 OB–FRM–LSANA (17) – traffic channel assignment failures for SoLSA related causes . . .
156
A.24.6 OB–FRM–OCASCOM (06) – Successful radio resource assignments for OC . . . . . . . 156
A.24.7 OB–FRM–OCASREQ (05) – Radio resource assignment requests for OC . . . . . . . . . 156
A.24.8 OB–FRM–POOL (13) – traffic channel assignment success with pool indication mismatch
156
A.24.9 OB–FRM–RETRYACK (10) – Number of directed retry handover success . . . . . . . . . 156
A.24.10 OB–FRM–RETRYREQ (09) – Number of directed retry handover request . . . . . . . . 156
A.24.11 OB–FRM–SASR (01) – Radio resource (traffic channel) assignments . . . . . . . . . . . . 157
A.24.12 OB–FRM–SDLIB (04) – Release requests ”BSC” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
A.24.13 OB–FRM–SHOIABSC (03) – Successful intra–BSC handovers . . . . . . . . . . . . . . . . . . 157
A.24.14 OB–FRM–SHOP–REASS (16) – TCH re–assignment requests due to Single Hop denial
157
A.24.15 OB–FRM–SHOPERF (14) – Receipt of Handover performed with change in multislot
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
A.24.16 OB–FRM–TCASCOM (08) – Successful radio resource assignments for TC . . . . . . 157
A.24.17 OB–FRM–TCASREQ (07) – Radio resource assignment requests for TC . . . . . . . . . 157
A.25 –––––––––––––––––––– SC counters (310) –––––––––––––––––––––––– . . . . . . . . . . . 158
A.25.1 OB–FSC–IMEIBLACK (04) – EIR answers with black IMEI . . . . . . . . . . . . . . . . . . . . . . . 158
A.25.2 OB–FSC–IMEIGREY (03) – EIR answers with grey IMEI . . . . . . . . . . . . . . . . . . . . . . . . 158
A.25.3 OB–FSC–IMEIINT (01) – EIR interrogation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
A.25.4 OB–FSC–IMEIUNKNOWN (05) – EIR answers with unknown IMEI . . . . . . . . . . . . . . . 158
A.25.5 OB–FSC–IMEIWHITE (02) – EIR answers with white IMEI . . . . . . . . . . . . . . . . . . . . . . . 158
A.26 –––––––––––––––––––– SH counters (330) –––––––––––––––––––––– . . . . . . . . . . . . . 158
A.27 –––––––––––––––––––– SM counters (398) –––––––––––––––––––––– . . . . . . . . . . . . . 158
A.27.1 OB–FSM–ALSC (09) – Alert service center (IWMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
A.27.2 OB–FSM–GTWREL (18) – Short message gateway procedure release (GMSC) . . . . 158
A.27.3 OB–FSM–IEFW (17) – Incoming unsuccessful forward (GMSC) . . . . . . . . . . . . . . . . . . 158
A.27.4 OB–FSM–IEFWS (21) – Incoming unsuccessful forward from SGSN (GMSC) . . . . . . 158
A.27.5 OB–FSM–IFWREQ (10) – Incoming forward request (VMSC) . . . . . . . . . . . . . . . . . . . . 159
A.27.6 OB–FSM–ISFW (04) – Incoming successful forward (GMSC) . . . . . . . . . . . . . . . . . . . . 159
A.27.7 OB–FSM–ISFWS (20) – Incoming successful forward from SGSN (GMSC) . . . . . . . . 159
A.27.8 OB–FSM–MWDREQ (07) – Message waiting data/Report SM delivery status request
(GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
A.27.9 OB–FSM–OEFW (12) – Outgoing unssuccessful forward (VMSC) . . . . . . . . . . . . . . . . 159
A.27.10 OB–FSM–OFWREQ (03) – Outgoing forward request (GMSC) . . . . . . . . . . . . . . . . . . 159
A.27.11 OB–FSM–OFWREQS (19) – Outgoing forward request to SGSN (GMSC) . . . . . . . . 159
A.27.12 OB–FSM–OSFW (11) – Outgoing successful forward (VMSC) . . . . . . . . . . . . . . . . . . 159
A.27.13 OB–FSM–RCFREQ (13) – RCF request (VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.27.14 OB–FSM–REL (15) – SMT procedure release (VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . 159

A.27.15 OB–FSM–RGREQ (05) – routing request (GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
A.27.16 OB–FSM–SCREQ (01) – Service center request (GMSC) . . . . . . . . . . . . . . . . . . . . . . 160
ED 01
AAC020023800DS En 11 / 260
260
A.27.17 OB–FSM–SMWD (08) – Successful message waiting data/Report SM delivery status
(GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
A.27.18 OB–FSM–SODBSMOC (16) – Number of SMSMO refused due to ODB of outgoing calls.
160
A.27.19 OB–FSM–SRG (06) – Successful routing (GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

A.27.20 OB–FSM–SSMRX (14) – successful short message reception (VMSC) . . . . . . . . . . . 160

A.27.21 OB–FSM–SSMTX (02) – Successful short message transmission (GMSC) . . . . . . . 160
A.28 –––––––––––––––––––– SW counters (311)–––––––––––––––––––––––––– . . . . . . . . . 160
A.28.1 OB–FSW–ACMGTW (21) – Reception of ACM event . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
A.28.2 OB–FSW–ANMGTW (26) – Reception of ANM event . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
A.28.3 OB–FSW–EAEVRF (02) – Outgoing call establishment failures . . . . . . . . . . . . . . . . . . . 160
A.28.4 OB–FSW–EARGMSC (09) – Call forwarding refusals (GMSC) . . . . . . . . . . . . . . . . . . . 160
A.28.5 OB–FSW–EIRAGMSC (07) – Failures of interrogation for rerouting call excepted Forward-
ing Violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
A.28.6 OB–FSW–ENAEMSC (05) – Incoming call failures in VMSC . . . . . . . . . . . . . . . . . . . . . 161
A.28.7 OB–FSW–FILMCF (27) – Number of routing on announcement . . . . . . . . . . . . . . . . . . 161
A.28.8 OB–FSW–GTWREL (22) – Gateway procedure release . . . . . . . . . . . . . . . . . . . . . . . . . 161
A.28.9 OB–FSW–IWFINSREQ (30) – Number of IWF insertion request . . . . . . . . . . . . . . . . . . 161
A.28.10 OB–FSW–IWFINSRES (31) – Number of IWF insertion success . . . . . . . . . . . . . . . . 161
A.28.11 OB–FSW–IWFINS–MOD–REQ (43) – Number of IWF insertion requests for MODIFY
using the SSP generic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
A.28.12 OB–FSW–IWFINS–MOD–RES(44) – Number of IWF insertion results for MODIFY using
the SSP generic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
A.28.13 OB–FSW–IWFINS–OC–REQ (39) – Number of IWF insertion requests in OC call using
A.28.14 OB–FSW–IWFINS–OC–RES (40) – Number of IWF insertion results in OC call using the
SSP generic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
A.28.15 OB–FSW–IWFINS–TC–REQ (41) – Number of IWF insertion requests in TC call using
A.28.16 OB–FSW–IWFINS–TC–RES (42) – Number of IWF insertion results in TC call using the
SSP generic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
A.28.17 OB–FSW–ODBECT (37) – Number of ECT refused due to ODB of call transfer calls 162
A.28.18 OB–FSW–OPCALL (28) – Terminating operator calls in VMSC . . . . . . . . . . . . . . . . . . 162
A.28.19 OB–FSW–OPINTR (29) – Interventions requested by operator . . . . . . . . . . . . . . . . . . 162
A.28.20 OB–FSW–OTC–SRI (35) – Number of received SRI result with VlrContainer . . . . . . 162
A.28.21 OB–FSW–OTC–MSRN (36) – Number of local MSRN request . . . . . . . . . . . . . . . . . . 162
A.28.22 OB–FSW–SAEGVRF (10) – Calls outgoing from GMSC . . . . . . . . . . . . . . . . . . . . . . . . 162
A.28.23 OB–FSW–SAEVRF (01) – Calls outgoing from MSC. . . . . . . . . . . . . . . . . . . . . . . . . . . 163
A.28.24 OB–FSW–SARGMSC (08) – Calls forwarded (GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . 163
A.28.25 OB–FSW–SARVRF (20) – Conditionally Forwarded calls outgoing from MSC . . . . . 163
A.28.26 OB–FSW–SHOP–DENIED (38) – Single Hop denials on originating side . . . . . . . . . 163
A.28.27 OB–FSW–SIRAGMSC (06) – Interrogations for call rerouting . . . . . . . . . . . . . . . . . . . 163
A.28.28 OB–FSW–SNAEGMSC (03) – Calls from fixed network (GMSC). . . . . . . . . . . . . . . . . 163
A.28.29 OB–FSW–SNAEMSC (04) – Incoming calls (VMSC). . . . . . . . . . . . . . . . . . . . . . . . . . . 163
A.28.30 OB–FSW–SRIABSSUB (24) – Failures of interrogation for rerouting call because of
Absent Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
A.28.31 OB–FSW–SRICFMSC (18) – Interrogations for call rerouting (CF MSC) . . . . . . . . . . 164
A.28.32 OB–FSW–SRICFRES (19) – Results of interrogation for rerouting calls . . . . . . . . . . 164
A.28.33 OB–FSW–SRIFWDVIOL (14) – Call forwarding violation . . . . . . . . . . . . . . . . . . . . . . . 164
A.28.34 OB–FSW–SRIGTW (11) – Interrogations for call rerouting (GTW) . . . . . . . . . . . . . . . 164
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.28.35 OB–FSW–SRIGTW2 (32) – Interrogations for call rerouting (GTW) . . . . . . . . . . . . . . 164

A.28.36 OB–FSW–SRIGTWCAM (45) – Results of first interrogation without FTN nor MSRN 164
A.28.37 OB–FSW–SRIGTWCF (13) – Results of interrogation for rerouting calls (with CFU) 164
A.28.38 OB–FSW–SRIGTWRES (12) – Results of interrogation for rerouting calls . . . . . . . . 164
ED 01
AAC020023800DS En 12 / 260
260
A.28.39 OB–FSW–SRIOC (15) – Interrogations for call rerouting (OC) . . . . . . . . . . . . . . . . . . . 164
A.28.40 OB–FSW–SRIOC2 (33) – Interrogations for call rerouting (OC) . . . . . . . . . . . . . . . . . . 165
A.28.41 OB–FSW–SRIOCCAM (46) – Results of first interrogation without FTN nor MSRN . 165
A.28.42 OB–FSW–SRIOCCF (17) – Results of interrogation for rerouting calls (with CFU) . 165
A.28.43 OB–FSW–SRIOCRES (16) – Results of interrogation for rerouting calls . . . . . . . . . . 165

A.28.44 OB–FSW–SRISNOTSU (25) – Failures of interrogation for rerouting call because of ser-
vice not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
A.28.45 OB–FSW–SRIUNKSUB (23) – Failures of interrogation for rerouting call because of
Unknown Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
A.28.46 OB–FSW–TONECF (34) – Number of routing on tone . . . . . . . . . . . . . . . . . . . . . . . . . . 165
A.29 –––––––––––––––––––– TC counters (306) –––––––––––––––––––––––– . . . . . . . . . . . 165
A.29.1 OB–FTC–ALERT (05) – MS terminating calls with Alerting . . . . . . . . . . . . . . . . . . . . . . . 165
A.29.2 OB–FTC–C–FORREL (19) – VMSC–forwarded TC during conversation phase . . . . . 165
A.29.3 OB–FTC–C–REL (18) – TC releases during conversation phase . . . . . . . . . . . . . . . . . 166
A.29.4 OB–FTC–CALCONF (04) – Confirmed MS terminating calls . . . . . . . . . . . . . . . . . . . . . 166
A.29.5 OB–FTC–CALCONF–BS (10) – Confirmed MS terminating calls per basic service . . 166
A.29.6 OB–FTC–CONNECT (06) – Successful MS terminating calls . . . . . . . . . . . . . . . . . . . . . 166
A.29.7 OB–FTC–DURC–BS (16) – Conversation phase duration for terminating calls . . . . . 166
A.29.8 OB–FTC–DURE–BS (12) – Establishment phase duration for terminating calls . . . . 166
A.29.9 OB–FTC–DURS–BS (14) – Ringing phase duration for terminating calls . . . . . . . . . . 166
A.29.10 OB–FTC–EARMSC (02) – Refusal of call forwarding (MSC) . . . . . . . . . . . . . . . . . . . . 166
A.29.11 OB–FTC–FORREL (09) – TC forwarded in VMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
A.29.12 OB–FTC–NBRC–BS (17) – Number of calls taken into account in OB–FTC–DURC–BS
counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
A.29.13 OB–FTC–NBRE–BS (13) – Number of calls taken into account in OB–FTC–DURE–BS
counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
A.29.14 OB–FTC–NBRS–BS (15) – Number of calls taken into account in OB–FTC–DURS–BS
counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
A.29.15 OB–FTC–REJ (08) – Rejected TC for regulation cause . . . . . . . . . . . . . . . . . . . . . . . . . 167
A.29.16 OB–FTC–REL (07) – TC releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
A.29.17 OB–FTC–SARMSC (01) – Forwarded calls (MSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
A.29.18 OB–FTC–SNGWTC (03) – Incoming and MS terminating calls . . . . . . . . . . . . . . . . . . 167
A.29.19 OB–FTC–SODBSH (11) – Number of CH invocations due to ODB of SS management . .
167
A.30 ––––––––––––––––––––– TR counters (316) –––––––––––––––––––––– . . . . . . . . . . . . 167
A.30.1 OB–FTR–ANARES (01) – Number of translation analysis results observed . . . . . . . . 167
A.31 ––––––––––––––––––––– UU counters (395) –––––––––––––––––––––– . . . . . . . . . . . . 167
A.31.1 OB–FUU–PUUSOC (01) – Number of OC with PUUS activated . . . . . . . . . . . . . . . . . . 167
A.31.2 OB–FUU–PUUSTC (02) – Number of TC with PUUS activated . . . . . . . . . . . . . . . . . . . 168
A.31.3 OB–FUU–UUIMSN (03) – Number of UUI transferred from MS to network . . . . . . . . . 168
A.31.4 OB–FUU–UUINMS (04) – Number of UUI transferred form network to MS . . . . . . . . . 168
A.32 ––––––––––––––––––––– VH counters (354) –––––––––––––––––––––– . . . . . . . . . . . . 168
A.32.1 OB–FVH–FALLBACK (01) – Number of MAP version fallbacks . . . . . . . . . . . . . . . . . . 168
A.32.2 OB–FVH–FALLBACKUN (02) – Number of unexpected MAP version fallbacks . . . . . 168
A.32.3 OB–FVH–PHASE1–TRANS (05) – Call independant SS with MS handled in phase 1 168
A.32.4 OB–FVH–PHASE1CNX (03) – Connection with MS phase 1 . . . . . . . . . . . . . . . . . . . . . 168
A.32.5 OB–FVH–PHASE2–TRANS (06) – Call independent SS with MS handled in phase 2 168
A.32.6 OB–FVH–PHASE2CNX (04) – Connection with MS phase 2 . . . . . . . . . . . . . . . . . . . . . 168
A.32.7 OB–FVH–R99CNX (07) – Connection with MS Release 99 at least . . . . . . . . . . . . . . . 169
A.33 –––––––––––––––––––– XX/SH counters (330) ––––––––––––––––––––– . . . . . . . . . . . 169
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.33.1 OB–FSH–REL (03) – Supplementary service operation release . . . . . . . . . . . . . . . . . . 169

A.33.2 OB–FXX–ASS (02) – Supplementary service acceptance . . . . . . . . . . . . . . . . . . . . . . . . 169
A.33.3 OB–FXX–SISS (01) – Supplementary service invocations . . . . . . . . . . . . . . . . . . . . . . . 170
A.34 ––––––––––––––––––––– XX/SLI counters (300) –––––––––––––––– . . . . . . . . . . . . . . . 171
ED 01
AAC020023800DS En 13 / 260
260
A.34.1 OB–FXX–SEMN3 (02) – Level 3 messages from MSC to BSC/RNC . . . . . . . . . . . . . . 171
A.34.2 OB–FXX–SRMN3 (03) – Level 3 messages received by MSC from BSC/RNC . . . . . . 171
APPENDIX B – VLR COUNTER IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

B.1 Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

B.2 –––––––––––––––––––– CA counters (257) –––––––––––––––––––––– . . . . . . . . . . . . . 172

B.2.1 OB–VCA–MMEVENTN (01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
B.3 –––––––––––––––––––– CCP counters (252) –––––––––––––––––––––– . . . . . . . . . . . . . 172
B.3.1 OB–VCCP–ERA (3) – Erase CC entry received per supplementary service related to call
completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
B.3.2 OB–VCCP–ERA–F (4) – Erase CC entry failure per supplementary service related to call
completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
B.3.3 OB–VCCP–REG (1) – Register CC entry received per supplementary service related to call
completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
B.3.4 OB–VCCP–REG–F (2) – Register CC entry failure per supplementary service related to call
completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
B.4 –––––––––––––––––––– CT counters (249) –––––––––––––––––––––– . . . . . . . . . . . . . . 173
B.4.1 OB–VCT–ACTRMOD (1) – Activate trace mode received . . . . . . . . . . . . . . . . . . . . . . . . . 173
B.4.2 OB–VCT–ACTRMODR (2) – Activate trace mode sent . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
B.5 –––––––––––––––––––– GP counters (235)––––––––––––––––––––––––– . . . . . . . . . . . 173
B.5.1 OB–VGP–ALRTACK (11) – Alert Ack message received from a SGSN . . . . . . . . . . . . . 173
B.5.2 OB–VGP–ALRTREQ (10) – Alert Request message sent to a SGSN . . . . . . . . . . . . . . . 173
B.5.3 OB–VGP–GPDETACK (14) – GPRS_Detach_Ack message sent to a SGSN . . . . . . . . 173
B.5.4 OB–VGP–GPDETIND (13) – GPRS_Detach_Indication message received from a SGSN . .
173
B.5.5 OB–VGP–IMDETACK (16) – IMSI_Detach_Ack message sent to a SGSN . . . . . . . . . . 173
B.5.6 OB–VGP–IMDETIND (15) – IMSI_Detach_Indication message received from a SGSN 173
B.5.7 OB–VGP–LOCUPACP (08) – Location Update Accept message sent to a SGSN . . . . 173
B.5.8 OB–VGP–LOCUPREQ (07) – Location Update Request message received from a SGSN .
173
B.5.9 OB–VGP–MMINFREQ (23) – MM_information Request message sent to a SGSN . . . 173
B.5.10 OB–VGP–MOBMMR (24) – Mobile Status message received from a SGSN containing a
MM Information Request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
B.5.11 OB–VGP–MOBSTR (26) – Mobile Status message received from a SGSN . . . . . . . . . 174
B.5.12 OB–VGP–MOBSTS (25) – Mobile Status message sent to a SGSN . . . . . . . . . . . . . . . 174
B.5.13 OB–VGP–MSACTIV (12) – MS_Activity_Indication message received from a SGSN 174
B.5.14 OB–VGP–MSINFREQ (21) – MS_information Request message sent to a SGSN . . . 174
B.5.15 OB–VGP–MSINFRES (22) – MS_information Response message received from a SGSN
174
B.5.16 OB–VGP–PAGREJ (02) – Paging Reject message received from a SGSN . . . . . . . . . 174
B.5.17 OB–VGP–PAGREQ (01) – Paging Request message sent to a SGSN . . . . . . . . . . . . . 174
B.5.18 OB–VGP–PASMRJ (05) – Paging Reject message for SMT received from a SGSN 174
B.5.19 OB–VGP–PASMRQ (04) – Paging Request message for SMT sent to a SGSN . . . . . 174
B.5.20 OB–VGP–RESTACKR (20) – Reset_Ack message received from a SGSN . . . . . . . . . 174
B.5.21 OB–VGP–RESTACKS (18) – Reset_Ack message sent to a SGSN . . . . . . . . . . . . . . . 175
B.5.22 OB–VGP–RESTINDR (17) – Reset_Indication message received from a SGSN . . . . 175
B.5.23 OB–VGP–RESTINDS (19) – Reset_Indication message sent to a SGSN . . . . . . . . . . 175
B.5.24 OB–VGP–TMSIREAL (09) – TMSI_Reallocation_Complete message received from a
SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
B.5.25 OB–VGP–UNREACH (03) – MS_Unreachable message received from a SGSN . . . . 175
B.5.26 OB–VGP–UNREASM (06) – MS_Unreachable message for SMT received from a SGSN
1AA 00014 0004 (9007) A4 – ALICE 04.10
175
B.6 –––––––––––––––––––– LR counters (204) ––––––––––––––––––––––––– . . . . . . . . . . . 175
B.6.1 OB–VLR–AUTHVISIT (12) – Authorized other PLMN MS registrations . . . . . . . . . . . . . . 175
ED 01
AAC020023800DS En 14 / 260
260
B.6.2 OB–VLR–CANLOC–HOM (05) – home PLMN HLR registration cancellations . . . . . . . 175
B.6.3 OB–VLR–CANLOC–OTH (06) – Other HLR registration cancellations . . . . . . . . . . . . . . 175
B.6.4 OB–VLR–DSDREQ (25) – Delete subscriber data request . . . . . . . . . . . . . . . . . . . . . . . . 175
B.6.5 OB–VLR–DSDRES (26) – Delete subscriber data success . . . . . . . . . . . . . . . . . . . . . . . . 175
B.6.6 OB–VLR–ENI (04) – Registration failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

B.6.7 OB–VLR–EXTORI–LAC (14) – Registration request from external originating LAC . . . 176
B.6.8 OB–VLR–HLRCONF–FLAG (16) – Location update requests to HLR due to set of HLR
conf flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
B.6.9 OB–VLR–HLRLOCREQ (09) – Location update requests to HLR . . . . . . . . . . . . . . . . . . 176
B.6.10 OB–VLR–HLRLOCRES (10) – Location update result from HLR . . . . . . . . . . . . . . . . . . 176
B.6.11 OB–VLR–IMPDET (24) – Number or implicit detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
B.6.12 OB–VLR–ISDREQ (29) – Number of framed Insert Subscriber data procedure request
received from HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
B.6.13 OB–VLR–ISDRES (30) – Number of framed Insert Subscriber data procedure success
sent to HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
B.6.14 OB–VLR–MS–UNKN (15) – Registration request from internal originating LAC, not regis-
tered in VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
B.6.15 OB–VLR–NOHLRUPD (31) – Number of intra VLR location registration without HLR
updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
B.6.16 OB–VLR–NWVLRSPREQ (22) – Send parameters request number in new VLR . . . . 177
B.6.17 OB–VLR–NWVLRSPRES (23) – Send parameters result number in new VLR . . . . . . 177
B.6.18 OB–VLR–OLVLRSPREQ (08) – Send parameters request number in old VLR . . . . . . 177
B.6.19 OB–VLR–OLVLRSPRES (21) – Send parameters result number in old VLR . . . . . . . . 177
B.6.20 OB–VLR–OLVLRUKN (07) – Registration requests from unknown VLRs . . . . . . . . . . . 177
B.6.21 OB–VLR–PSIREQ (32) – Number of PSI requests from HLR . . . . . . . . . . . . . . . . . . . . . 177
B.6.22 OB–VLR–PSIRES (33) – Number of PSI results to HLR . . . . . . . . . . . . . . . . . . . . . . . . . 177
B.6.23 OB–VLR–PURGEREQ (17) – Number of PurgeMS requests to HLR . . . . . . . . . . . . . . 177
B.6.24 OB–VLR–PURGERES (18) – Number of PurgeMS responses from HLR . . . . . . . . . . 177
B.6.25 OB–VLR–RESTOREQ (19) – Number of restoreData requests to HLR . . . . . . . . . . . . 177
B.6.26 OB–VLR–RESTORES (20) – Number of restoreData responses from HLR . . . . . . . . 177
B.6.27 OB–VLR–ROAMNALL (13) – Unallowed roaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
B.6.28 OB–VLR–SAISDREQ (27) – Number of stand–alone Insert Subscriber data request
received from HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
B.6.29 OB–VLR–SAISDRES (28) – Number of stand–alone Insert Subscriber data success sent
to HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
B.6.30 OB–VLR–SANL (01) – Location cancellations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
B.6.31 OB–VLR–SANLGLO (51) – Location cancellations (global) . . . . . . . . . . . . . . . . . . . . . . 178
B.6.32 OB–VLR–SATTGSAS (56) – Subscribers currently registered in the VLR with status ”IMSI
attach” and ”GPRS attach”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
B.6.33 OB–VLR–SATTGSASP (58) – Subscribers currently registered in the VLR with status
”IMSI attach” and ”GPRS attach”for each PLMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
B.6.34 OB–VLR–SATTGSNA (55) – Subscribers currently registered in the VLR with status ”IMSI
attach” and not ”GPRS detach”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
B.6.35 OB–VLR–SATTGSNAP (57) – Subscribers currently registered in the VLR with status
”IMSI attach” and not ”GPRS detach” for each PLMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
B.6.36 OB–VLR–SNI (03) – Number of Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
B.6.37 OB–VLR–SNIA (02) – Subscribers currently registered in the VLR . . . . . . . . . . . . . . . . 179
B.6.38 OB–VLR–SNIAP (54) – Subscribers registered in the VLR in each PLMN . . . . . . . . . . 179
B.6.39 OB–VLR–SNIGLO (53) – Registrations number (global) . . . . . . . . . . . . . . . . . . . . . . . . . 179
B.6.40 OB–VLR–UNAUTHVISIT (11) – MS registrations from unauthorized PLMN . . . . . . . . 179
1AA 00014 0004 (9007) A4 – ALICE 04.10
B.7 –––––––––––––––––––– NR counters (278) –––––––––––––––––––––––– . . . . . . . . . . . . 180

B.7.1 OB–VNR–UPLACREQ (01) – LAC updating requests through national roaming . . . . . 180
B.7.2 OB–VNR–UPLACRES (02) – LAC updating success through national roaming . . . . . . 180
B.8 –––––––––––––––––––– PG counters (203) –––––––––––––––––––––––– . . . . . . . . . . . . 180
ED 01
AAC020023800DS En 15 / 260
260
B.8.1 OB–VPG–ENPAG (02) – Paging request failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
B.8.2 OB–VPG–PAGING (03) – Paging requests for calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
B.8.3 OB–VPG–PAGING–SM (06) – Paging requests for SM . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
B.8.4 OB–VPG–PAGSRCHRES (05) – Paging /Search responses for calls . . . . . . . . . . . . . . . 180
B.8.5 OB–VPG–PAGSRCHRES–SM (08) – Paging /Search responses for SM . . . . . . . . . . . . 180

B.8.6 OB–VPG–SEARCH (04) – Search requests for calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

B.8.7 OB–VPG–SEARCH–SM (07) – Search requests for SM . . . . . . . . . . . . . . . . . . . . . . . . . . 180
B.8.8 OB–VPG–SNPAG (01) – Paging requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
B.9 –––––––––––––––––––– SC counters (210) –––––––––––––––––––––––– . . . . . . . . . . . . 181
B.9.1 OB–VSC–EALGO (09) – Key reallocation failures due to A5–X algo. uncompatibility (GSM/
BSS coverage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
B.9.2 OB–VSC–ERALG (11) – Key reallocation failures due to algorithm uncompatibility (UTRAN
coverage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
B.9.3 OB–VSC–EDAUT (04) – Unsuccessful Authentications with triplets . . . . . . . . . . . . . . . . 181
B.9.4 OB–VSC–EAUTH (12) – Unsuccessful Authentications with quintuplets . . . . . . . . . . . . 181
B.9.5 OB–VSC–EDTRH (02)– Failures of authentication vectors requests to HLR . . . . . . . . 181
B.9.6 OB–VSC–ERESYN (16)– Authentication Failure with Synchro Failure cause (UMTS only) .
181
B.9.7 OB–VSC–EAFAIL (17)– Authentication Failure with MAC Failure cause (UMTS only) 181
B.9.8 OB–VSC–ENREAC (06) – Ciphering command failures with triplets . . . . . . . . . . . . . . . . 181
B.9.9 OB–VSC–ECIPH (13) – Ciphering command failures with quintuplets . . . . . . . . . . . . . . 181
B.9.10 OB–VSC–ENREAT (08) – TMSI reallocation failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
B.9.11 OB–VSC–SDAUT (03) – Authentication requests with triplets . . . . . . . . . . . . . . . . . . . . 182
B.9.12 OB–VSC–URAUT (14) – Authentication requests with quintuplets . . . . . . . . . . . . . . . . 182
B.9.13 OB–VSC–SDTRH (01) – Authentication vectors requests to the HLR . . . . . . . . . . . . . 182
B.9.14 OB–VSC–SNREAC (05) – Ciphering commands with triplets . . . . . . . . . . . . . . . . . . . . . 182
B.9.15 OB–VSC–NBCIPH (15) – Ciphering commands with quintuplets . . . . . . . . . . . . . . . . . . 182
B.9.16 OB–VSC–SNREAT (07) – TMSI reallocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
B.9.17 OB–VSC–TRREUSED (10) – Triplet reused . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
B.10 –––––––––––––––––––– SH counters (230)––––––––––––––––––––––––– . . . . . . . . . . 182
B.10.1 OB–VSH–AR (05) – Unstructured SS operations related to AR function request . . . . 182
B.10.2 OB–VSH–ENOSS (02) – Supplementary service operation failures . . . . . . . . . . . . . . . 182
B.10.3 OB–VSH–NIUN (12) – Network initiated unstructured supplementary service notification
invoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
B.10.4 OB–VSH–NIUR (10) – Network initiated unstructured supplementary service request
invoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
B.10.5 OB–VSH–REGPWREQ (07) – Register password request sent . . . . . . . . . . . . . . . . . . 183
B.10.6 OB–VSH–REGPWRES (08) – Register password result received . . . . . . . . . . . . . . . . . 183
B.10.7 OB–VSH–SAR (06) – Unstructured SS operations related to AR function success . . 183
B.10.8 OB–VSH–SNIUN (13) – Network initiated unstructured supplementary service notification
success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
B.10.9 OB–VSH–SNIUR (11) – Network initiated unstructured supplementary service request
success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
B.10.10 OB–VSH–SNOSS (01) – Supplementary service operations . . . . . . . . . . . . . . . . . . . . 183
B.10.11 OB–VSH–SODBSH (09) – Number of operations refused due to ODB of SS manage-
ment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
B.10.12 OB–VSH–SUSS (04) – Unstructured supplementary service operation success . . . 184
B.10.13 OB–VSH–USS (03) – Unstructured supplementary service operation requests . . . . 184
B.11 ––––––––––––––––––––– SM (Short Message Terminating) counters (298) – . . . . . . . 184
B.11.1 OB–VSM–MAREQ (04) – Ready for SM request (Memory available) . . . . . . . . . . . . . . 184
1AA 00014 0004 (9007) A4 – ALICE 04.10
B.11.2 OB–VSM–MSABS (01) – MS present (VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

B.11.3 OB–VSM–MSPRESREQ (02) – Ready for SM request (MS present) . . . . . . . . . . . . . . 184
B.11.4 OB–VSM–SMA (05) – Successful Ready for SM (Memory available) . . . . . . . . . . . . . . 184
B.11.5 OB–VSM–SMSPRES (03) – Successful Ready for SM (MS present) . . . . . . . . . . . . . . 184
ED 01
AAC020023800DS En 16 / 260
260
B.12 –––––––––––––––––––– TC counters (206) –––––––––––––––––––––––– . . . . . . . . . . . 185
B.12.1 OB–VTC–EMSRN–ABSSUB (04) – Failures for Roaming number Requests because of
Absent Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
B.12.2 OB–VTC–EMSRN–FNOTSU (05) – Failures for Roaming number Requests because of
Facility Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

B.12.3 OB–VTC–EMSRN–FNOTSU2 (06) – Failures for Roaming number Requests because of

Facility Not Supported (per E.164 PLMN address) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
B.12.4 OB–VTC–MSRN–REJ (07) – Roaming number request reject for regulation cause . . 185
B.12.5 OB–VTC–REQ–BS (02) – Terminating call request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
B.12.6 OB–VTC–REQ–MSRN (03) – Roaming number Requests . . . . . . . . . . . . . . . . . . . . . . . 185
B.12.7 OB–VTC–RES–BS–MSRN (01) – Roaming Number Request Results . . . . . . . . . . . . . 185
APPENDIX C – HLR COUNTER IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

C.1 Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
C.2 –––––––––––––––––––– CA counters (157) –––––––––––––––––––– . . . . . . . . . . . . . . . . 186
C.2.1 OB–HCA–USSN (03) – Number of Unstructured SS Notify messages . . . . . . . . . . . . . 186
C.2.2 OB–HCA–USSNOK (04) – Number of Unstructured SS Notify . . . . . . . . . . . . . . . . . . . . 186
C.2.3 OB–HCA–USSR (01) – Number of Unstructured SS Request messages . . . . . . . . . . . 186
C.2.4 OB–HCA–USSROK (02) – Number of Unstructured SS Request . . . . . . . . . . . . . . . . . . 186
C.2.5 OB–HCA–ATSI (05) – Number of ATSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
C.2.6 OB–HCA–ATSIACK (06) – Number of ATSI Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
C.2.7 OB–HCA–ATM (07) – Number of ATM Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
C.2.8 OB–HCA–ATMACK (05) – Number of ATM Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
C.3 –––––––––––––––––––– CC counters (197) –––––––––––––––––––– . . . . . . . . . . . . . . . . 187
C.3.1 OB–HCC–PCCBSMES (01) – Number of PCCBS related messages . . . . . . . . . . . . . . . 187
C.3.2 OB–HCC–PCCBSREQ (02) Number of PCCBS Request messages . . . . . . . . . . . . . . . 187
C.4 –––––––––––––––––––– CCB counters (150) –––––––––––––––––––– . . . . . . . . . . . . . . . 187
C.4.1 OB–HCCB–INVA (01) – Number of automatic invocations of CCBS on the A side . . . . 187
C.4.2 OB–HCCB–INVB (02) – Number of automatic invocations of CCBS on the B side . . . . 187
C.4.3 OB–HCCB–RQA (03) – Number of successful CCBS calls on the A side . . . . . . . . . . . 187
C.4.4 OB–HCCB–RQB (04) – Number of successful CCBS calls on the B side . . . . . . . . . . . 187
C.5 –––––––––––––––––––– CCP counters (152) –––––––––––––––––––––– . . . . . . . . . . . . . 187
C.5.1 OB–HCCP–ERA (03) – Erase CC entry received per supplementary service related to call
completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
C.5.2 OB–HCCP–ERA–F (04) – Erase CC entry failure per supplementary service related to call
completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
C.5.3 OB–HCCP–REG (01) – Register CC entry received per supplementary service related to
call completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
C.5.4 OB–HCCP–REG–F (02) – Register CC entry failure per supplementary service related to
call completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
C.6 –––––––––––––––––––– CF counters (196) –––––––––––––––––––– . . . . . . . . . . . . . . . . 188
C.6.1 OB–HCF–SODBFTN (01) – Number of operations refused due to ODB of FTN registration,
OC or TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
C.7 –––––––––––––––––––– CT counters (149) –––––––––––––––––––– . . . . . . . . . . . . . . . . 188
C.7.1 OB–HCT–ACTRMOD (01) – Number of Activate trace mode . . . . . . . . . . . . . . . . . . . . . . 188
C.7.2 OB–HCT–ACTRMODR (02) – Number of Activate trace mode results . . . . . . . . . . . . . . 188
C.8 ––––––––––––––––––––– GP counters (135) ––––––––––––––––––– . . . . . . . . . . . . . . . . 188
C.8.1 OB–HGP–CANLOCREQ (05) – Number of Cancel Location requests sent to SGSN . 188
C.8.2 OB–HGP–CANLOCRES (06) – Number of Cancel Location results sent from SGSN 188
C.8.3 OB–HGP–DSDREQ (07) – Delete subscriber data request sent to SGSN . . . . . . . . . . . 188
C.8.4 OB–HGP–DSDRES (08) – Delete subscriber data result from SGSN . . . . . . . . . . . . . . . 188
1AA 00014 0004 (9007) A4 – ALICE 04.10
C.8.5 OB–HGP–ISDREQ (03) – Number of attempted framed Insert Subscriber data procedures
towards an SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
ED 01
AAC020023800DS En 17 / 260
260
C.8.6 OB–HGP–ISDRES (04) – Number of successful framed Insert Subscriber data procedures
towards an SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
C.8.7 OB–HGP–MAREQ (20) – Ready for SM request from SGSN (Memory available) . . . . 189
C.8.8 OB–HGP–MSPRESREQ (18) – Ready for SM request from SGSN (MS present) . . . . 189
C.8.9 OB–HGP–PDPRGREQ (22) – Send Routing Info for GPRS Invoke received from GGSN . .
189
C.8.10 OB–HGP–PDPRGRES (23) – Send Routing Info for GPRS Result sent to GGSN . . . 189
C.8.11 OB–HGP–PDPFRREQ (24) –Failure Report Invoke received from GGSN . . . . . . . . . 189
C.8.12 OB–HGP–PDPFRRES (25) –Failure Report Result sent to GGSN . . . . . . . . . . . . . . . . 189
C.8.13 OB–HGP–PDPMSPRESREQ (26) –Note MS Present for GPRS Invoke sent to GGSN . . .
189
C.8.14 OB–HGP–PDPMSPRESRES (27) –Note MS Present for GPRS Result from GGSN 189
C.8.15 OB–HGP–PURGEMS (11) – Number of PurgeMS requests from SGSN . . . . . . . . . . 189
C.8.16 OB–HGP–PURGEMSRES (12) – Number of PurgeMS result to SGSN . . . . . . . . . . . 190
C.8.17 OB–HGP–RGREQ (13) – Routing request from a SMS–GMSC supporting MT SMS over
GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.18 OB–HGP–RGRES (14) – Successful routing sent to a SMS–GMSC supporting MT SMS
over GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.19 OB–HGP–RGSGSN (15) – Successful routing with SGSN number . . . . . . . . . . . . . . . 190
C.8.20 OB–HGP–RSMDREQ (16) – Report SM delivery status request from a SMS–GMSC sup-
porting MT SMS over GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.21 OB–HGP–RSMDRES (17) – Report SM delivery status result sent to a SMS–GMSC sup-
porting MT SMS over GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.22 OB–HGP–SAISDREQ (09) – Number of stand–alone Insert Subscriber data request sent
to SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.23 OB–HGP–SAISDRES (10) – Number of stand–alone Insert Subscriber data success
received from SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.24 OB–HGP–SGSNLOCREQ (01) – Number of Update GPRS Location requests received
from SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.8.25 OB–HGP–SGSNLOCRES (02) – Number of Update GPRS Location results sent to
SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
C.8.26 OB–HGP–SMA (21) – Successful Ready for SM sent to SGSN (Memory available) . 191
C.8.27 OB–HGP–SMSPRES (19) – Successful Ready for SM sent to SGSN (MS present) . 191
C.9 –––––––––––––––––––––– LCS counters (162) ––––––––––––––––––––––––– . . . . . . . 191
C.10 ––––––––––––––––––––– LR counters (104) ––––––––––––––––––– . . . . . . . . . . . . . . . 191
C.10.1 OB–HLR–ATIREQ (18) – Number of ATI requests from the SCP . . . . . . . . . . . . . . . . . . 191
C.10.2 OB–HLR–ATIRES (19) – Number of ATI results sent to the SCP . . . . . . . . . . . . . . . . . . 191
C.10.3 OB–HLR–CANLOCREQ (08) – Number of Cancel Location requests sent to VLR . . 191
C.10.4 OB–HLR–CANLOCRES (09) – Number of Cancel Location results sent from VLR . 191
C.10.5 OB–HLR–DSDREQ (10) – Delete subscriber data request . . . . . . . . . . . . . . . . . . . . . . . 191
C.10.6 OB–HLR–DSDRES (11) – Delete subscriber data success . . . . . . . . . . . . . . . . . . . . . . . 191
C.10.7 OB–HLR–ISDREQ (06) – Number of framed Insert Subscriber data procedure request
sent to VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
C.10.8 OB–HLR–ISDRES (07) – Number of framed Insert Subscriber data procedure success
received from VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
C.10.9 OB–HLR–PSIREQ (16) – Number of PSI requests to the VLR . . . . . . . . . . . . . . . . . . . . 192
C.10.10 OB–HLR–PSIRES (17) – Number of PSI results from VLR . . . . . . . . . . . . . . . . . . . . . 192
C.10.11 OB–HLR–PURGEMS (01) – Number of PurgeMS requests from VLR . . . . . . . . . . . 192
C.10.12 OB–HLR–RESTORE (02) – Number of RestoreData requests from VLR . . . . . . . . . 192
C.10.13 OB–HLR–RESTORERES (14) – Number of RestoreData success to VLR . . . . . . . . 192
1AA 00014 0004 (9007) A4 – ALICE 04.10
C.10.14 OB–HLR–SAISDREQ (12) – Number of stand–alone Insert Subscriber data request

sent to VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
C.10.15 OB–HLR–SAISDRES (13) – Number of stand–alone Insert Subscriber data success
received from VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
ED 01
AAC020023800DS En 18 / 260
260
C.10.16 OB–HLR–SENDIMSI (03) – Number of IMSI requests from VLR . . . . . . . . . . . . . . . . 192
C.10.17 OB–HLR–SODBROAM (15) – Number of operations refused due to ODB of roaming . . .
193
C.10.18 OB–HLR–VLRLOCREQ (04) – Number of Update Location requests received from VLR
193
C.10.19 OB–HLR–VLRLOCRES (05) – Number of Update Location results sent to VLR . . . 193
C.11 –––––––––––––––––––– OR counters (147) –––––––––––––––––––––––– . . . . . . . . . . . 193
C.11.1 OB–HOR–SRIINV (01) – Number of SRI invoke with OR interrogation . . . . . . . . . . . . . 193
C.11.2 OB–HOR–SRIRES (02) – Number of SRI result optimized . . . . . . . . . . . . . . . . . . . . . . . 193
C.12 ––––––––––––––––––––– SA counters (188) ––––––––––––––––––– . . . . . . . . . . . . . . . 193
C.12.1 OB–HSA–SN (01) – Number of subscriber in the HLR database (globally) . . . . . . . . 193
C.12.2 OB–HSA–SNC (02) – Number of subscribers in the HLR database with access to the cir-
cuit domain at least . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
C.12.3 OB–HSA–SNP (03) – Number of subscribers in the HLR database with access to the
packet domain at least . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
C.13 ––––––––––––––––––––– SC counters (110) ––––––––––––––––––– . . . . . . . . . . . . . . . 194
C.13.1 OB–HSC–ENDTR (02) – Authentication Vectors request failures . . . . . . . . . . . . . . . . . 194
C.13.2 OB–HSC–SNDTR (01) – Authentication Vectors requests received . . . . . . . . . . . . . . . 194
C.13.3 OB–HSC–RAUREP (03) – Authentication_Failure_report received (UMTS only) . . . . 194
C.14 ––––––––––––––––––––– SH counters (130) ––––––––––––––––––– . . . . . . . . . . . . . . . 194
C.14.1 OB–HSH–AR (03) – Unstructured SS operations related to AR function request . . . . 194
C.14.2 OB–HSH–ENOSS (02) – Supplementary service operation failures . . . . . . . . . . . . . . . 194
C.14.3 OB–HSH–NIUN (10) – Network initiated unstructured supplementary service notification
invoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
C.14.4 OB–HSH–NIUR (08) – Network initiated unstructured supplementary service request
invoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
C.14.5 OB–HSH–REGPWREQ (05) – Register password request received . . . . . . . . . . . . . . 195
C.14.6 OB–HSH–REGPWRES (06) – Register password result sent . . . . . . . . . . . . . . . . . . . . 195
C.14.7 OB–HSH–SAR (04) – Unstructured SS operations related to AR function success . . 195
C.14.8 OB–HSH–SNIUN (11) – Network initiated unstructured supplementary service notification
success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
C.14.9 OB–HSH–SNIUR (09) – Network initiated unstructured supplementary service request
success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
C.14.10 OB–HSH–SNOSS (01) – Supplementary service operations . . . . . . . . . . . . . . . . . . . . 195
C.14.11 OB–HSH–SODBSH (07) – Number of operation refused due to ODB of SS management
195
C.15 ––––––––––––––––––––– SM counters (198) ––––––––––––––––––– . . . . . . . . . . . . . . . 195
C.15.1 OB–HSM–ALMSC (05) – Alert MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
C.15.2 OB–HSM–ALREQ (08) – Alert MSC phase 2 request . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
C.15.3 OB–HSM–ISC (14) – Inform service center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
C.15.4 OB–HSM–MAREQ (12) – Ready for SM request (Memory available) . . . . . . . . . . . . . . 196
C.15.5 OB–HSM–MSPRES (06) – MS present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
C.15.6 OB–HSM–MSPRESREQ (10) – Ready for SM request (MS present) . . . . . . . . . . . . . . 196
C.15.7 OB–HSM–MWDREQ (03) – Message waiting data/Report SM delivery status request 196
C.15.8 OB–HSM–REJ (07) – Number of Send Routing Info for SM requests not handled due to
HLR overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
C.15.9 OB–HSM–RGFNUMENQ (15) – Number of Send Routing Info for SM requests used as a
MSC number enquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
C.15.10 OB–HSM–RGREQ (01) – Routing request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
C.15.11 OB–HSM–SAL (09) – Alert MSC phase 2 successful . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
1AA 00014 0004 (9007) A4 – ALICE 04.10
C.15.12 OB–HSM–SMA (13) – Successful Ready for SM (Memory available) . . . . . . . . . . . . . 196

C.15.13 OB–HSM–SMSPRES (11) – Successful Ready for SM (MS present) . . . . . . . . . . . . . 197
C.15.14 OB–HSM–SMWD (04) – successful message waiting data/report SM delivery status 197
ED 01
AAC020023800DS En 19 / 260
260
C.15.15 OB–HSM–SODBSMTC (16) – Number of SMSMT refused due to ODB of incoming calls.
197
C.15.16 OB–HSM–SRG (02) – successful routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
C.16 ––––––––––––––––––––– SS counters (140) –––––––––––––––––––– . . . . . . . . . . . . . . 197
C.16.1 OB–HSS–SRETRI (01) – Number of reused triplets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

C.16.2 OB–HSS–SRESYN (02) – Number of resynchronisations . . . . . . . . . . . . . . . . . . . . . . . . 197

C.17 ––––––––––––––––––––– TC counters (106) ––––––––––––––––––– . . . . . . . . . . . . . . . 197
C.17.1 OB–HTC–EMSRN–ABSSUB (05) – Number of MSRN provision request failures because
of absent subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
C.17.2 OB–HTC–EMSRN–BUSSUB (08) – Number of MSRN provision request failures because
of MS busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
C.17.3 OB–HTC–EMSRN–FNOTSU (06) – Number of MSRN provision request failures because
of Facility not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
C.17.4 OB–HTC–ENIREA (02) – Failures of interrogation for call rerouting . . . . . . . . . . . . . . . 198
C.17.5 OB–HTC–REJ (07) – Number of routing requests for TC not handled due to overload . . .
198
C.17.6 OB–HTC–REQ–MSRN (03) – Number of MSRN provision request . . . . . . . . . . . . . . . 198
C.17.7 OB–HTC–RES–MSRN (04) – Number of MSRN provision request result . . . . . . . . . . 198
C.17.8 OB–HTC–SNIREA (01) – Interrogations for call rerouting . . . . . . . . . . . . . . . . . . . . . . . . 198
C.17.9 OB–HTC–SNIREA2 (10) – Interrogations for call rerouting . . . . . . . . . . . . . . . . . . . . . . . 198
C.17.10 OB–HTC–SODBIC (09) – Number of TC refused due to ODB of incoming calls . . . 198
C.18 ––––––––––––––––––––– TR counters (116) ––––––––––––––––––– . . . . . . . . . . . . . . . 198
C.18.1 OB–HTR–ANARES (01) – Number of translation analysis result observed . . . . . . . . . 198
C.19 ––––––––––––––––––––– VH counters (154) ––––––––––––––––––– . . . . . . . . . . . . . . . 198
C.19.1 OB–HVH–FALLBACK (01) – Number of MAP version fallbacks . . . . . . . . . . . . . . . . . . 198
C.19.2 OB–HVH–FALLBACKUN (02) – Number of unexpected MAP version fallbacks . . . . 199
C.19.3 OB–HVH–SRGI–REJ (03) – Number of Send routing informations reject for optimal rout-
ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
C.19.4 OB–HVH–SRGISM–REJ (04) – Number of Send routing informations for SM reject for
optimal routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
APPENDIX D OBSERVATION SCENARIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

D.1 LR INTRA VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
D.2 LR INTER VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
D.3 OC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
D.4 PURE GATEWAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
D.5 GATEWAY + TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
D.6 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
D.7 GATEWAY + TC TO MS CONDITIONALY FORWARDED (no paging response) . . . . . . . 212
D.8 GATEWAY + TC TO MS CONDITIONALY FORWARDED (subs not reachable) . . . . . . . . 213
D.9 GSM to GSM HANDOVER (GSM only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
D.9.1 INTRA–MSC HANDOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
D.9.2 INTER–MSC HANDOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
D.9.3 SUBSEQUENT HANDOVER (A –> B –> C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
D.9.4 RETURN SUBSEQUENT HANDOVER (A–>B, B–>A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
D.10 SRNS relocation (UMTS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
D.10.1 Name of counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
D.10.2 Intra MSC SRNS relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
D.10.3 Inter MSC (A –> B) SRNS relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
D.10.4 Subsequent inter MSC SRNS relocation – three MSC involved (A–> B –> C) . . . . . . . 229
D.10.5 Return subsequent inter MSC SRNS relocation – two MSC involved (A–> B –> A) . . 232
1AA 00014 0004 (9007) A4 – ALICE 04.10
D.11 UMTS to GSM handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

D.11.1 Intra MSC UTRAN to GSM handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
D.11.2 Inter MSC UTRAN to GSM handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
ED 01
AAC020023800DS En 20 / 260
260
D.11.3 Subsequent inter MSC UTRAN to GSM handover – three MSC involved . . . . . . . . . . . 238
D.11.4 Return subsequent inter MSC UTRAN to GSM handover – two MSC involved . . . . . 241
D.12 GSM to UMTS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
D.12.1 Intra MSC GSM to UTRAN handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
D.12.2 Inter MSC GSM to UTRAN handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

D.12.3 Subsequent inter MSC GSM to UTRAN handover – three MSC involved . . . . . . . . . . 247
D.12.4 Return subsequent inter MSC GSM to UTRAN handover – two MSC involved . . . . . 250
D.13 IN SERVICES INVOCATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
D.14 SMIM INSERTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
D.15 SHORT MESSAGE TERMINATING (phase 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
D.16 SHORT MESSAGE ORIGINATING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
D.17 CAMEL CONTROL AND INTERROGATION OF SUBSCRIPTION DATA : ANY TIME
INFORMATION HANDLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
D.18 Mobile Terminating Location Request (MT_LR) LCS procedure . . . . . . . . . . . . . . . . . . . 260
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 21 / 260
260
LIST OF FIGURES AND TABLES
Figure 1. General description of Observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 2. Unit and Function numbers in the Counter number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 3. Functional description of Observation in the RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 4. Functional description of Observation in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 5. Functional description of Observation in the RCP station . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 6. Functional description of Observation in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 7. Functional description of Observation in the HLR station . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 22 / 260
260
HISTORY
01 on 02–01–22
Creation from document AAC020023700DS Ed.03
Review: 04/02/02 (MND/MC/R&D/CASYSM/EV/02.035.004/MB)

REFERENCED DOCUMENTS
[1] AAC020023800DT – Observation Feature Description
[2] See note 1 – Functional Option List
[3] AAC020416700DT – Basic Services and Supplementary Services applicability
[4] AAC033528000DS – Error classification
N.B. (1) The documents referenced by < [2] page 23> and < [3] page 23> are related to several docu-
ments, one per customer.
GLOSSARY / TERMINOLOGY
GBR Guaranteed Bit Rate.

FNUR Fixed Network User Rate.
ITC Information Transfer Capability
IWF InterWorking Function.
QoS Quality of Service.
RAB Radio Access Bearer.
RDI Restricted Digital Information.
UDI Unrestricted Digital Information.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 23 / 260
260
1 INTRODUCTION
The general description of observation is given in document [1] page 23.

The observation function describes the actions to be taken in the NSS so that its composite units can send
bulk observation data to the OMC.
The OMC shall process this data, store it and make it available for consultation.
N.B. The ”OMC processing” part is not covered in this document.
The general organization is shown in figure 1.
OMC
OBS.
APPLI.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ COLLECT
(4)
ACQUISITION
GENERIC
I20y
OBS.
I10y
I40y I30y
APPLI.
TCAP
HLR (AUC,HLR) RTOS APPLI.
or
RCP (RFC, VLR)
Figure 1. General description of Observation

1AA 00014 0004 (9007) A4 – ALICE 04.10
(I10y): reading of application counters by an observation function at the rate of a system period.
ED 01
AAC020023800DS En 24 / 260
260
The values of ”y” are:
– 0 : RCF
– 1 : VLR
– 2 : HLR
(I20y): sending of raw values of the counters in the form of tickets (formatting by the Application (OBS)).
– In the RCP :
• 0 : RCF – fast polling : a set of counters is transmitted every ”Tf” mn (”Tf” is managed by MOD-
PER MMC)
• 1 : VLR – fast polling : a set of counters is transmitted every ”Tf” mn (”Tf” is managed by MOD-
PER MMC)
• 5 : RCF – slow polling : a set of counters is transmitted every ”Ts” mn (”Ts” is managed by MOD-
PER MMC)
• 6 : VLR – slow polling : a set of counters is transmitted every ”Ts” mn (”Ts” is managed by MOD-
PER MMC)
• 3 : RCP station : a set of counter is transmitted every ”T1” mn
– If the option F–OBS–006 is not active T1 is a system parameter (5mn).
– If the option F–OBS–006 is active T1 is equal to Tf.
If option F–OBS–006 is not active, typical values could be:

Tf = 5 mn
Ts = 30 mn
T1 = 5 mn
If option F–OBS–006 is active, values could be:

Tf = 15 mn or 30 mn
Ts = 30 mn or 60 mn
– In the HLR :
• 2 : HLR : a set of counter is transmitted every ”T2” mn (”T2” is managed by MODPER MMC)
• 4 : HLR station : a set of counter is transmitted every ”T2” mn (”T2” is managed by MODPER
MMC)
If option F–OBS–006 is not active, typical values could be T2 = 5 mn.
If option F–OBS–006 is active, values could be T2 = 15 mn, 30mn or 60mn .
(I30y): reading of RTOS counters by an observation function at the rate of a system period.
– 2 : HLR
– 3 : RCP
(I40y): reading of TCAP counters by an observation function at the rate of a system period.
– 0 : RCF
– 1 : VLR
– 2 : HLR
(4): transmission of tickets file in ”on line transfer mode”.

The initialization message for the session, sent from COLLECT to ACQUISITION, is included in the data
stream (4).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 25 / 260
260
1.1 General Principle about Application Counters Definition
1.1.1 Definition
– Procedure type:
It can be for instance an originating call, a gateway call, a terminating call, an intra–MSC handover,
a subsequent handover...,
– Release domain:
The procedure release causes should be classified by domain, for instance:
• User cause,
• network cause,
• local cause...
1.1.2 Principle
The defined counters have to allow to count, per procedure type:

– The submitted traffic,
– The processed traffic,
– The procedure release, per release domain (see note 1)
N.B. (1 ) The release counters are used to count the success or the failure of processed procedures.
In case of failure, the incremented release domain allows to know the entity at the origin of the
failure (user, mobile station, BSS, RNS, HLR, ...), or some characterized cause (service not sup-
plied, no answer from called party, ...). See the definition on chapter <4.1.4 page105 >.
The knowing of release domain to be incremented is realized by means of translation of internal
(generated) or external (received) error into release domain. This translation is described in
document [4].
1.2 General Principle about Application Counters Exploitation
1.2.1 Definition
– family: set of counters having the same meaning.

It is identified by a family number. Numbering rules are defined on chapter < 2 page 30>.
– counter rank: ASCII string.

It identifies a counter in a given family. For the families which include only one counter, no rank is
defined (the string is void).
– polling class: attribute of each family (RCF and VLR counters only)
• FAST: the families with this class are transmitted in the fast polling
• SLOW: the families with this class are transmitted in the slow polling
• NONE: the families with this class are not transmitted to the OMC
This is the default value for each family not having yet been assigned a polling class with MOD-
CLA MMC.
– synchronized sending : depending on the functional option F–OBS–006, the counters can be sent,
• without synchronization : the counters are sent according to the polling class period,
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
with synchronization : the values of the period associated to a polling class may be 60 min-
utes, 30 minutes or 15 minutes and the sending is synchronized on the exact hour:
– H.00 for a period of 60 minutes,
– H.00 and H.30 for a period of 30 minutes,
ED 01
AAC020023800DS En 26 / 260
260
– H.00, H.15, H.30 and H.45 for a period of 15 minutes.
1.2.2 Principle
1.2.2.1 Affectation of a polling class to a family
The MMC MODCLA modifies the polling class of a family.
N.B. This MMC is only applicable to the RCP
MODCLA: CPTNAME =.....,CLASS =.....;
CPTNAME : family number, in decimal mode: one or a list

CLASS : SLOW => the family is sent by the slow polling
FAST => the family is sent by the fast polling
BOTH => the family is sent by the two polling
NONE => the family is not sent to the OMC
Both parameters are mandatory.
1.2.2.2 Interrogation of the class
The MMC INTCLA displays the polling class for one or several families.
N.B. This MMC is only applicable to the RCP
INTCLA: CPTNAME =.....,CLASS =.....;
CPTNAME : family number, in decimal mode: one or a list

CLASS : SLOW => the family sent by the slow polling are listed
FAST => the family sent by the fast polling are listed
BOTH => the family sent by the two polling are listed
NONE => the family not send to the OMC are listed
Only one parameter can be given:

– if the parameter CPTNAME is given, the MMC gives the polling classes of the given families.
– if the parameter CLASS is given, the MMC lists the families that fit the parameter.
In the report, the families must be sorted by increasing number.
1.2.2.3 Modification and Interrogation of the polling period if F–OBS–006 is not active
1.2.2.3.1 MMC MODPER at the RCP
The MMC MODPER at the RCP allows the modification and the interrogation of the polling class period.
MODPER: CLASS = ....., PERIOD = .....;
CLASS : FAST => fast polling

SLOW => slow polling
PERIOD : output period of the polling (number of minutes).
minimal value for the fast polling: TfMin = 5 mn (maximal value: Tfmax = 65535 mn)
1AA 00014 0004 (9007) A4 – ALICE 04.10
minimal value for the slow polling: TsMin = 30 mn (maximal value: Tsmax = 65535 mn)
Parameters CLASS and PERIOD are mandatory for the modification.
Parameter CLASS is optional for interrogation :
ED 01
AAC020023800DS En 27 / 260
260
– when this parameter is omitted, both periodicities specified by PERIOD parameter are displayed,
– when this parameter is present, the specified PERIOD parameter for the given CLASS parameter
is displayed.
1.2.2.3.2 MMC MODPER at the HLR

MODPER is not available in the applicable releases, the sending period is defined by a system parameter.
The MMC MODPER at the HLR allows the modification and the interrogation of the polling class period.

minimal value for the polling: Tmin = 5 mn (maximal value: Tmax = 65535 mn)
MODPER: PERIOD = .....;
Parameter PERIOD is mandatory for the modification, when this parameter is omitted, the period is dis-
played. The period is applicable to station and application counters.
1.2.2.4 Modification and Interrogation of the polling period if F–OBS–006 is active
1.2.2.4.1 MMC MODPER at the RCP
The MMC MODPER at the RCP allows the modification and the interrogation of the polling class period.
MODPER: CLASS = ....., PERIOD = .....;
CLASS : FAST => fast polling

SLOW => slow polling

possible values for the fast polling: 15 mn or 30 mn.
possible values for the slow polling: 30 mn or 60 mn.
Parameters CLASS and PERIOD are mandatory for the modification.
Parameter CLASS is optional for interrogation :
– when this parameter is omitted, both periods specified by the PERIOD parameter are displayed,
– when this parameter is present, the specified PERIOD parameter for the given CLASS parameter
is displayed. The period defined for the fast polling is also applied to the station counters.
1.2.2.4.2 MMC MODPER at the HLR
The MMC MODPER at the HLR allows the modification and the interrogation of the polling class period.

possible values for the polling: 15 mn , 30 mn or 60 mn.
MODPER: PERIOD = .....;
Parameter PERIOD is mandatory for the modification, when this parameter is omitted,the periodicity is
displayed. The period is applicable to station and application counters.
1.3 Activation of synchronized sending
The following procedure must be applied :

1AA 00014 0004 (9007) A4 – ALICE 04.10
a) First the functional option F–OBS–006 is set to active.
b) Then the operator updates the collection period(s).
ED 01
AAC020023800DS En 28 / 260
260
At the HLR, the synchronized sending becomes effective after the modification of the period collection.
At the RCP, the synchronized sending becomes effective after the modification of the two collection peri-
ods.
1.4 Functional options
The following functional options are used:
F–OBS–001 : RCP in charge of sending SCCP gateway observation counters
F–OBS–002 : No RTOS observation counters for the HLR part
F–OBS–003 : Observation counters related to LAC not sent to the OMC
F–OBS–004 : Global LR observation counters instead of per LAC counters
F–OBS–005 : VLR subscribers per PLMN
F–OBS–006 : Synchronized sending
F–OBS–007 : Measurements of fax/data call attempts and answered calls
F–OBS–008 : Attach VLR subscribers

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 29 / 260
260
2 DETAILED DESCRIPTION
The different interfaces are listed in this chapter for each unit as follows:
– RCF
– VLR
– RCP station
– HLR
– HLR station
Each section relating to a unit describes:

– the functional environment of the function in the unit,
– the list of data to be sent to the OMC.
N.B. Counters available or not according to a functional option are only sent if this option is active.
The following definitions are used in the tables listing the data to be sent to the OMC:
a) name of the counter family
The following naming rules apply:

OB–yzz–qnnnnnnnn
• the values of ”y” are V (for VLR), H (for HLR) , R (for RCP) ,F (for RCF), corresponding to the
name of the unit,
• ”zz” corresponds to the name of the function and takes the values allocated to the generating
function (OC, TC, SW, etc.),
”zz” may be given the ”XX” value if a number of functions are impacted.
• ”q” is optional and takes the values S (for success) and E (for failure),
• ”nnnnnnnn” is an area for counter identification.
b) family counter number
This number is included in the observation ticket transmitted to OMC for identification.
the following numbering rules apply:
• 1 digit for the functional unit
• 2 digits for the function which increments the counter (see Figure 2. page 31)
• 2 digits for the counter number within the function
The counter number 0 is reserved for use by the applications in the OMC–M. It is never used by the
network elements.
c) type
• P for peg counter (event cumulative counter)
• L for load counter
• Pl for peg counter with long identifier in the family, and which are filtered (see chapter 4.1.2 page
101)
• Ll for load counter with long identifier in the family, and which are filtered (see chapter 4.1.2 page
101)
d) coding mode
• B for binary.
e) identifier if family concerned
see chapter 4.1.4 page 105

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 30 / 260
260
y Unit number Unit name
A 0 STATION (RTOS)
H 1 HLR
V 2 VLR/RCP
F 3 RCF/RCP
zz Function number Function name
SL 00 SLI
XX 00 SLI
TH 00 STATION (RTOS)
TH 01 STATION (RTOS)
PG 03 Paging
LR 04 Location Registration
OC 05 Originating Call
TC 06 Terminating Call
HO 07 HandOver
RE 08 Relocation
SC 10 SeCurity
SW 11 SWitching interface
RM 15 Radio resource Management
TR 16 Translation
MP 23 Multi Party
LD 27 Traffic Load Management
SH 30 Supplementary Service Handling
XX 30 Supplementary Service Handling
DN 31 Defence
GP 35 General Packet Radio Service
SS 40 Subscriber Security
MO 46 Short message originating
OR 47 Support of Optimal Routeing
DA 48 Data transmission
CT 49 Call tracing
CCB 50 Call completion on busy subscriber
CS 51 Carrier selection
CCP 52 Call completion services
VH 54 Version Handling
CA 57 CAMEL
NP 58 Mobile Number Portability
LSA 59 Support of localised service area
ALR 60 Active Location Retrieval
MLP 61 enhanced Multi–level Precedence & Pre–emption
LCS 62 LoCation Services
NR 78 National Roaming
SA 88 Subscriber administration
UU 95 User to user signalling
CF 96 Call Forwarding
CC 97 Preliminary Completion of Calls to Busy Subscribers
SM 98 Short message terminating
IN 99 Intelligent Network
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 2. Unit and Function numbers in the Counter number
ED 01
AAC020023800DS En 31 / 260
260
2.1 Detailed description in the RCF
2.1.1 The functional environment of the function in the unit

Appli. functional modules

ALR Active Location Retrieval
CA CAMEL
CCB Calllcompletion on busy subs
CS Carrier selection
CT Call Tracing
DA Data transmission
DN Defence
GP GPRS
HO Handover
IN(1) Intelligent Network
LCS Location services I 200
LD Traffic Load Management or
LR Location Registration I 205
LSA Support of LSA ACQ. OMC
MO Short Message Originating OBS.
MLP eMLPP
MP Multi party
NP Mobile Number Portability
OC Originating call
OR Support of optimal routeing
PG Paging
RE Relocation
RM Radio Resource Management
SC Security
SM Short Message Terminating
SW Switching Interface
TC Terminating Call
TCAP(1)
RCF
TR Translation
UU User to user
VH(1) Version Handling
XX/SH Suppl. services Handling
XX/SLI
”XX” means ”several functions”
(1) VLR and RCF TCAP VH and IN counters are merged in RCP counters and transmitted in RCF ticket.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 3. Functional description of Observation in the RCF
ED 01
AAC020023800DS En 32 / 260
260
2.1.2 List of RCF observations to be sent to the OMC
Meaning of the column titles :

Name = Name of the Observation Counter Family
Nb. = Number of the Observation Counter Family

Doc. = related Documentation

T = Type of the Observation Counter Family
C = Coding mode
Identifier = Identifier (rank) (filled if family concerned, ”///” otherwise)
Rel. = Release of appearance (this does not take into account possible counter handling evolu-
tions introduced in further releases): if the release is not specified, the counter is not available
Name Nb. Description T C Identifier Rel.
OB–FXX–SEMN3 30002 Number of level 3 messages P B BSC/RNC R2

transmitted from MSC to BSC name
(resp. RNC), per BSC (resp.
RNC)
OB–FXX–SRMN3 30003 Number of level 3 messages P B BSC/RNC R2

received by MSC from BSC name
(resp. RNC), per BSC (resp.
RNC)
OB–FSL–STTCAPE 30011 Number of TCAP P B /// R2

transactions input to RCP
OB–FSL–STTCAPS 30012 Number of TCAP P B /// R2

transactions output from RCP
OB–FSL–ETTCAPE 30013 Number of TCAP transactions P B /// R2

input to RCP terminated with
ABORT
OB–FSL–ETTCAPS 30014 Number of TCAP transactions P B /// R2

output from RCP terminated
with ABORT
OB–FPG–SRP 30301 Number of PAGING repetitions P B /// R2

on A–Interface or Iu interface
OB–FPG–ERP 30302 Number of PAGING failures on P B /// R2

A–Interface or Iu interface for
calls and short messages termi-
nating
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FPG–BUSYMS 30303 Number of MS terminating P B /// R2

calls and short messages termi-
nating with busy MS
ED 01
AAC020023800DS En 33 / 260
260
OB–FPG–PAGEIMSI 30304 Number of page response P B /// R2

with TMSI after page request
with IMSI
OB–FPG–OPNDUB 30305 Number of operator calls P B /// R3+

toward a busy subscriber
OB–FPG–OPINTA 30306 Number of operator calls P B /// R3+

with intervention allowed
OB–FPG–FBDCELL 30307 Number of paging on the forbid- P B ///

den cells of the VMSC
OB–FPG–OTC 30308 Number of successful paging P B ///

for optimized terminating call
OB–FPG–HPA 30309 Number of Paging message P B ///

sent with IE Alerting Required
OB–FPG–SHPA 30310 Number of Paging result P B ///

received after sending of Pag-
ing message with IE Alerting
Required
OB–FPG–NACK 30311 Number of Paging Nack P B ///
OB–FPG–ERP–C 30312 Number of PAGING failures on P B /// R5

calls
OB–FPG–BUSY–C 30313 Number of terminating calls with P B /// R5

busy MS
OB–FPG–ERP–SM 30314 Number of PAGING failures on P B /// R5

short messages
OB–FPG–BUSY–SM 30315 Number of short messages ter- P B /// R5

minating with busy MS
OB–FLR–SLUA 30401 Number of registration P B BSC/RNC R2

(27) requests per BSC/RNC name
OB–FLR–ATT 30402 Number of IMSI attach P B BSC/RNC R2

requests per BSC/RNC name
OB–FLR–DET 30403 Number of IMSI detach P B BSC/RNC R2

requests per BSC/RNC name
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FLR–SLUR 30404 Number of accepted registra- P B BSC/RNC R2

tion requests, per originating name
BSC/RNC
ED 01
AAC020023800DS En 34 / 260
260
OB–FLR–SLU 30405 Number of normal registration P B BSC/RNC R2

request per BSC/RNC name
OB–FLR–SLUP 30406 Number of periodical registra- P B BSC/RNC R2

tion request per BSC/RNC name
OB–FLR–REL 30407 Number of LR releases P B release R2

per release domain domain
OB–FLR–LRP–REJ 30408 Number of periodic LR rejected P B /// R2

for regulation cause
OB–FLR–LR–REJ 30409 Number of non periodic LR P B /// R2

rejected for regulation cause
OB–FLR–LOC–CTRL 30410 Number of Location Reporting P B RNC

Control messages sent with name
direct response requested per
RNC (excluding messages for
LCS services)
OB–FLR–LOC–REP 30411 Number of Location Report P B RNC

messages per RNC, received in name
direct response with the
information requested (exclud-
ing messages for LCS services)
OB–FOC–SRSU 30501 Number of requests per P B emer- R2

emergency service gency
service
identifier
OB–FOC–SAEMOB 30503 Number of call attempts from P B BSC/RNC R2

(27) mobile stations per originating name
BSC/RNC
OB–FOC–EAEMOB 30504 Number of failures on call P B /// R2

(2) attempts from mobile stations
OB–FOC–SETUP 30505 Number of Call SetUP P B BSC/RNC R2

received messages, per name
originating BSC/RNC
OB–FOC–DTMFREQ 30506 Number of START DTMF P B /// R2

(3) received
OB–FOC–DTMFCAL 30507 Number of calls requesting P B /// R2

1AA 00014 0004 (9007) A4 – ALICE 04.10
(3) DTMF transmission
ED 01
AAC020023800DS En 35 / 260
260
OB–FOC–CALPROC 30508 Number of authorized P B BSC/RNC R2

originating calls, per BSC/RNC name
OB–FOC–ALERT 30509 Number of mobile originating P B BSC/RNC R2

calls with alerting, name
per originating BSC/RNC
OB–FOC–PROGRESS 30510 Number of mobile originating P B BSC/RNC R2

calls with progress, name
OB–FOC–CONNECT 30511 Number of mobile originating P B BSC/RNC R2

calls with called response name
OB–FOC–DIRCON- 30512 Number of mobile originating P B BSC/RNC R2

NECT calls with direct connect name
OB–FOC–CONNACK 30513 Number of established P B BSC/RNC R2

mobile originating calls, name
OB–FOC–REL 30514 Number of mobile originating P B release R2

calls releases, domain
per release domain
OB–FOC–REQ–BS 30515 Number of outgoing call P B basic R2

requests service
OB–FOC–REJ 30516 Number of OC rejected P B /// R2

OB–FOC–EMIMEI 30517 Number of emergency call P B /// R4.1

on IMEI
OB–FOC–SODBOC 30518 Number of outgoing calls P B /// R4.1

refused due to ODB of
outgoing calls
OB–FOC–SODBPR 30519 Number of outgoing calls P B /// R4.1

premium rate calls
OB–FOC–SODBSH 30520 Number of CH invocations P B /// R4.1

refused during an OC due
to ODB of SS management
OB–FOC–SHOP– 30521 Number of Call SetUP received P B BSC

SETUP messages with ”telephony” for a name
1AA 00014 0004 (9007) A4 – ALICE 04.10
single hop call
ED 01
AAC020023800DS En 36 / 260
260
OB–FOC–DURE–BS 30523 Establishment phase cumula- P B basic ser- R5

(25) tive durations for outgoing calls, vice
per basic service
OB–FOC–NBRE–BS 30524 Number of calls taken into P B basic ser- R5

account in counter 30523, per vice
basic service
OB–FOC–DURS–BS 30525 Ringing phase cumulative dura- P B basic ser- R5

(25) tions for outgoing calls, per vice
basic service
OB–FOC–NBRS–BS 30526 Number of calls taken into P B basic ser- R5

basic service
OB–FOC–DURC–BS 30527 Conversation phase cumulative P B basic ser- R5

(25) durations for outgoing calls, per vice
basic service
OB–FOC–NBRC–BS 30528 Number of calls taken into P B basic ser- R5

basic service
OB–FOC–C–REL 30529 Number of OC releases during P B release R5

(25) conversation phase, per domain
release domain
OB–FOC–CGAP 30530 Number of OC rejected due to P B /// R5

call rate control
OB–FTC–SARMSC 30601 Number of forwarded calls P B /// R2

(4) (MSC)
OB–FTC–EARMSC 30602 Refusal of call forwarding P B /// R2

(MSC)
OB–FTC–SNGWTC 30603 Number of incoming calls from P B /// R2

fixed network towards a MS
controlled by the MSC
OB–FTC–CALCONF 30604 Number of confirmed MS P B BSC/RNC R2

(27) terminating calls name
OB–FTC–ALERT 30605 Number of MS terminating P B BSC/RNC R2

calls with alerting name
OB–FTC–CONNECT 30606 Number of successful MS P B BSC/RNC R2

1AA 00014 0004 (9007) A4 – ALICE 04.10
terminating calls name
ED 01
AAC020023800DS En 37 / 260
260
OB–FTC–REL 30607 Number of mobile terminating P B release R2

calls releases, per release domain
domain
OB–FTC–REJ 30608 Number of TC rejected P B /// R2

OB–FTC–FORREL 30609 Number of TC forwarded in P B release R3

VMSC domain
OB–FTC–CALCONF–BS 30610 Number of confirmed MS P B basic R4.1

terminating calls service
OB–FTC–SODBSH 30611 Number of CH invocations P B /// R4.1

refused during a TC due
OB–FTC–DURE–BS 30612 Establishment phase cumula- P B basic ser- R5

(25) tive durations for terminating vice
calls in VMSC, per basic service
OB–FTC–NBRE–BS 30613 Number of calls taken into P B basic ser- R5

basic service
OB–FTC–DURS–BS 30614 Ringing phase cumulative dura- P B basic ser- R5

(25) tions for terminating calls, per vice
basic service
OB–FTC–NBRS–BS 30615 Number of calls taken into P B basic ser- R5

basic service
OB–FTC–DURC–BS 30616 Conversation phase cumulative P B basic ser- R5

(25) durations for terminating calls, vice
per basic service
OB–FTC–NBRC–BS 30617 Number of calls taken into P B basic ser- R5

basic service
OB–FTC–C–REL 30618 Number of TC releases (not for- P B release R5

(25) warded in VMSC or in GMSC) domain
during conversation phase, per
release domain
OB–FTC–C–FORREL 30619 Number of TC releases (for- P B release R5

(25) warded in VMSC) during con- domain
versation phase, per release
domain
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 38 / 260
260
OB–FHO–SHOIAMSC 30701 Number of successful P B BSC R2

(5) intra–MSC handovers per name
originating BSC
OB–FHO–SHOIMSCA 30702 Number of successful P B BSC R2

(6) inter–MSC (MSCA) handovers name
per originating BSC
OB–FHO–EHOIRMSC 30703 Number of inter–MSC P B BSC R2

(6) handover failures name
signalled by the network
per originating BSC
OB–FHO–EHOIAMSC 30704 Number of intra–MSC P B BSC R2

(5) handover failures name
signalled by the network
per originating BSC
OB–FHO–SDTR1 30705 Number of handover required P B BSC R2

received per originating BSC name
OB–FHO–SHOC 30706 Number of handover com- P B BSC R2

(5) mands per originating BSC name
(intra MSC handover)
OB–FHO–EHOFFM 30707 Number of handover failures P B BSC R2

(5) signalled by the mobile stations name
per originating BSC
(intra MSC handover)
OB–FHO–SHOIMSCB 30708 Number of successful inter– P B BSC R2

MSC (MSCB) handovers or name
subsequent handover

having started handover pro- name
cesses per originating BSC

having led to the updating of the name
handover processes per origi-
nating BSC
OB–FHO–SDTR4 30711 Number of repeated P B BSC R2

HO_ReQuireD messages name
OB–FHO–SDTR5 30712 Number of HO_ReQuireD mes- P B BSC R2

sages on signalling channels name
OB–FHO–SHOIPIVA 30713 Number of attempted outgoing P B LAC R2

1AA 00014 0004 (9007) A4 – ALICE 04.10
(19) inter–VMSC handovers
ED 01
AAC020023800DS En 39 / 260
260
OB–FHO–SHOISESA 30714 Number of efficient outgoing P B LAC R2

(6) (19) inter–VMSC handovers
OB–FHO–SHOIPIVB 30715 Number of attempted incoming P B MSC R2

inter–VMSC handovers Id.
OB–FHO–SHOAREQ 30716 Number of attempted P B BSC R2

intra–MSC handover (/targ) name
OB–FHO–SHOACOMP 30717 Number of succesful P B BSC R2

(5) intra–MSC handover (/targ) name
OB–FHO–SHORPSIA 30718 Number of attempted incoming P B MSC R2

return subsequent handovers Id.
OB–FHO–SHORMSCA 30719 Number of efficient incoming P B MSC R2

return subsequent handovers Id.
OB–FHO–SHOSPSIA 30720 Number of attempted incoming P B /// R2

subsequent handovers
OB–FHO–SHOSMSCA 30721 Number of efficient incoming P B /// R2

subsequent handovers
OB–FHO–SHOSPSIB 30722 Number of attempted P B LAC R2

(19) outgoing subsequent
handovers (return or not)
OB–FHO–SHOSSERB 30723 Number of efficient P B LAC R2

(6) (19) outgoing subsequent
OB–FHO–SHOSMSCB 30724 Number of efficient P B BSC R2

(6) outgoing subsequent HOs name
(per originating BSC)
OB–FHO–EHOSMSCB 30725 Number of outgoing P B BSC R2

(6) subsequent HO failures name
(detected by network)
OB–FHO–SHOACMB 30726 Number of HO reception P B MSC R2

in target MSC Id.
OB–FHO–SHOARE- 30727 Number of efficient intra VMSC P B BSC R2

QACK HO resource assignment name
OB–FHO–EHOFFMA 30728 Number of outgoing P B BSC R2

(6) inter MSC HO failures name
(detected by MS)
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FHO–EHOFFMB 30729 Number of outgoing subse- P B BSC R2

(6) quent HO failures name
(detected by MS)
ED 01
AAC020023800DS En 40 / 260
260
OB–FHO–SHOBREQ 30730 Number of incoming inter P B BSC R2

VMSC HO resource assign- name
ment attempt
OB–FHO–SHOBRE- 30731 Number of efficient inter VMSC P B BSC R2

QACK HO resource assignment name
OB–FHO–SHOCIR 30732 Number of handover P B BSC R2

(6) commands per originating name
BSC (inter MSC)
OB–FHO–SHOCS 30733 Number of handover P B BSC R2

(6) commands per originating name
BSC (subsequent)
OB–FHO–SHOIPHORA 30734 Number of efficient outgoing P B LAC R2

(19) inter VMSC HO assignment
OB–FHO–SHOIRIABSC 30735 Number of inter BSC HO P B BSC R2

interrupted by intra BSC HO name
OB–FHO–SHOREL 30736 Intra MSC P B release R2

HO process interruptions domain
OB–FHO–SHORELA 30737 Inter MSC P B release R2

(serving/controlling MSC)
OB–FHO–SHORELB 30738 Inter MSC and subsequent P B release R2

(target MSC)
OB–FHO–SHOSRELA 30739 Subsequent return P B release R2

(controlling/target MSC)
OB–FHO–SHOSRELB 30740 Subsequent and subs return P B release R2

(serving MSC)
OB–FHO–SHORSEL 30741 HO resource reselection P B BSC R2

(target MSC) name
OB–FHO–SHOSAREQ 30742 Number of attempted P B BSC R2

return subsequent HO name
resource assignment
OB–FHO–SHOSARE- 30743 Number of efficient P B BSC R2

QACK return subsequent HO name
resource assignment
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FHO–SHOSPHORA 30744 Number of efficient subsequent P B /// R2

HO resource assignment
ED 01
AAC020023800DS En 41 / 260
260
OB–FHO–SHOSPSHORA 30745 Number of efficient P B /// R2

subsequent HO processing
in controlling MSC
OB–FHO–SHOIAMSC–2 30746 Number of successful Pl B (BSC, R2

intra–MSC handovers per BSC)
originating BSC, target BSC
OB–FHO–SHOIMSCA–2 30747 Number of successful Pl B (BSC, R2

(19) inter–MSC (MSCA) handovers LAC)
per originating BSC, target LAC
OB–FHO–EHOIRMSC–2 30748 Number of inter–MSC hand- Pl B (BSC, R2

(19) over failures signalled by the LAC)
network per originating BSC,
target LAC
OB–FHO–EHOIAMSC–2 30749 Number of intra–MSC hand- Pl B (BSC, R2

over failures signalled by the BSC)
network per originating BSC,
target BSC
OB–FHO–SHOC–2 30750 Number of handover com- Pl B (BSC, R2

mands per originating BSC, tar- BSC)
get BSC
OB–FHO–EHOFFM–2 30751 Number of handover failures Pl B (BSC, R2

signalled by the mobile stations BSC)
per originating BSC, target
BSC
OB–FHO–SHOSMSCB–2 30752 Number of efficient Pl B (BSC, R2

(19) outgoing subsequent HOs LAC)
OB–FHO–EHOSMSCB–2 30753 Number of outgoing subse- Pl B (BSC, R2

(19) quent HO failures LAC)
(detected by network)
OB–FHO–EHOFFMA–2 30754 Number of outgoing Pl B (BSC, R2

(19) inter MSC HO failures LAC)
(detected by MS)
OB–FHO–EHOFFMB–2 30755 Number of outgoing Pl B (BSC, R2

(19) subsequent HO failures LAC)
(detected by MS)
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FHO–SHOCIR–2 30756 Number of handover Pl B (BSC, R2

(19) commands (inter MSC) LAC)
ED 01
AAC020023800DS En 42 / 260
260
OB–FHO–SHOCS–2 30757 Number of handover Pl B (BSC, R2

(19) commands (subsequent) LAC)
OB–FHO–REJ 30758 Number of incoming HO P B /// R4.1

rejected for regulation cause
OB–FHO–SHOIPIVA- 30759 Total number of attempted out- P B /// R4.2

GLO going inter–VMSC handovers
(21)
OB–FHO–SHOISESA- 30760 Total number of efficient outgo- P B /// R4.2

GLO ing inter–VMSC handovers
(6) (21)
OB–FHO–SHOSPSIB 30761 Total number of attempted P B /// R4.2

GLO (21) outgoing subsequent
OB–FHO–SHOSSERB- 30762 Total number of efficient P B /// R4.2

GLO outgoing subsequent
(6) (21) handovers (return or not)
OB–FHO–SHOIPHORA- 30763 Total number of efficient outgo- P B /// R4.2

GLO ing inter VMSC HO assignment
(21)
OB–FHO–SHOIMSCA- 30764 Total number of successful P B /// R4.2

GLO inter–MSC (MSCA) handovers
(21)
OB–FHO–EHOIRMSC- 30765 Total number of inter–MSC P B /// R4.2

GLO handover failures signalled by
(21) the network
OB–FHO– 30767 Total number of outgoing P B /// R4.2

EHOSMSCBGLO subsequent HO failures
(21) (detected by network)
OB–FHO–EHOFFMA- 30768 Total number of outgoing P B /// R4.2

GLO inter MSC HO failures
(21) (detected by MS)
OB–FHO–EHOFFMB- 30769 Total number of outgoing P B /// R4.2

GLO subsequent HO failures
(21) (detected by MS)
OB–FHO–SHOCIRGLO 30770 Total number of handover P B /// R4.2

(21) commands (inter MSC)
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FHO–SHOCSGLO 30771 Number of handover P B /// R4.2

(21) commands (subsequent)
ED 01
AAC020023800DS En 43 / 260
260
OB–FHO–SDTR6 30772 Number of handover required P B BSC R4.2

with cause ’switch circuit pool’ name
received per originating BSC
OB–FHO–S3GHORQA 30773 Number of handover required P B (BSC,

(2G –> 3G intra–MSC hand- local
over) RNC)
OB–FHO–S3GCOMA 30774 Number of handover command P B (BSC,

over) RNC)
OB–FHO–S3GCOMPA 30775 Number of handover complete P B (BSC,

over) RNC)
OB–FHO–S3GRERA 30776 Number of handover released P B release

(2G –> 3G intra–MSC hand- domain
over)
OB–FHO–S3GPREPE 30777 Number of handover prepara- P B (BSC,

tion request at controlling MSC adjacent
(2G –> 3G inter–MSC hand- RNC)
over)
OB–FHO–S3GCOME 30778 Number of handover command P B (BSC,

at controlling MSC (2G –> 3G adjacent
inter–MSC handover) RNC)
OB–FHO–S3GCOMPE 30779 Number of handover complete P B (BSC,

at controlling MSC (2G –> 3G adjacent
inter–MSC handover) RNC)
OB–FHO–S3GRERE 30780 Number of handover released P B release

at controlling MSC (2G –> 3G domain
inter–MSC handover)
OB–FHO–S3GPREPSS 30781 Number of handover prepara- P B (BSC,

tion request at serving MSC adjacent
(2G –> 3G subsequent inter– RNC)
MSC handover)
OB–FHO–S3GCOMS 30782 Number of handover command P B (BSC,

at serving MSC (2G –> 3G sub- adjacent
sequent inter–MSC handover) RNC)
OB–FHO–S3GCOMPS 30783 Number of handover complete P B (BSC,

at serving MSC (2G –> 3G sub- adjacent
sequent inter–MSC handover) RNC)
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FHO–S3GRERSS 30784 Number of handover released P B release

at serving MSC (2G –> 3G sub- domain
sequent inter–MSC handover)
ED 01
AAC020023800DS En 44 / 260
260
OB–FHO–S3GPREPCS 30785 Number of handover prepara- P B ///

tion request at controlling MSC
(2G –> 3G subsequent inter–

MSC handover)
OB–FHO–S3GCOMPCS 30786 Number of handover complete P B ///

at controlling MSC (2G –> 3G
subsequent inter–MSC hand-
over)
OB–FHO–S3GRERCS 30787 Number of handover released P B release

at controlling MSC (2G –> 3G domain
subsequent inter–MSC hand-
over)
OB–FRE–SRERQ 30801 Number of relocation required P B RNC R7

(all type of relocation) name
(source)
OB–FRE–SRECOM 30802 Number of relocation command P B RNC R7

(all type of relocation) name
(source)
OB–FRE–SREREQA 30803 Number of relocation resource P B RNC R8

allocation request (intra–MSC name
relocation) (target)
OB–FRE–SREREQKA 30804 Number of relocation resource P B RNC R8

allocation acknowledge (intra– name
MSC relocation) (target)
OB–FRE–SRERQA 30805 Number of relocation required P B (RNC, R8

(intra–MSC relocation) local
RNC)
OB–FRE–SRECANA 30806 Number of relocation cancelled P B (RNC, R8

by the source RNC (intra–MSC local
relocation) RNC)
OB–FRE–SRECOMA 30807 Number of relocation command P B (RNC, R8

RNC)
OB–FRE–SRECOMPA 30808 Number of relocation complete P B (RNC, R8

RNC)
OB–FRE–SRERA 30809 Number of relocation released P B release R8

1AA 00014 0004 (9007) A4 – ALICE 04.10
(intra–MSC relocation) domain
ED 01
AAC020023800DS En 45 / 260
260
OB–FRE–SPREPE 30810 Number of relocation prepara- P B (RNC, R8

(inter–MSC relocation) RNC)
OB–FRE–SRECANE 30811 Number of relocation cancelled P B (RNC, R8

by the source RNC at control- adjacent
ling MSC (inter–MSC reloca- RNC)
tion)
OB–FRE–SRECOME 30812 Number of relocation command P B (RNC, R8

at controlling MSC (inter–MSC adjacent
relocation) RNC)
OB–FRE–SRECOMPE 30813 Number of relocation complete P B (RNC, R8

at controlling MSC (inter–MSC adjacent
relocation) RNC)
OB–FRE–SRERCE 30814 Number of relocation released P B release R8

at controlling MSC (inter–MSC domain
relocation)
OB–FRE–SPREPTE 30815 Number of relocation prepara- P B MSC R8

tion request at target MSC name
(inter–MSC and subsequent (control-
inter–MSC relocation) ling)
OB–FRE–SREREQE 30816 Number of relocation resource P B RNC R8

allocation request at target name
MSC (inter–MSC and subse- (target)
quent inter–MSC relocation)
OB–FRE–SREREQKE 30817 Number of relocation resource P B RNC R8

allocation acknowledge at tar- name
get MSC (inter–MSC and sub- (target)
sequent inter–MSC relocation)
OB–FRE–SACMTE 30818 Number of successful reloca- P B MSC R8

tion preparation at target MSC name
(inter–MSC and subsequent (control-
inter–MSC relocation) ling)
OB–FRE–SRECOMPTE 30819 Number of relocation complete P B MSC R8

at target MSC (inter–MSC and name
subsequent inter–MSC reloca- (control-
tion) ling)
OB–FRE–SRERTE 30820 Number of relocation released P B release R8

at target MSC (inter–MSC and domain
subsequent inter–MSC reloca-
tion)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 46 / 260
260
OB–FRE–SPREPCS 30821 Number of relocation prepara- P B /// R8

tion request at controlling MSC
(subsequent inter–MSC reloca-

tion)
OB–FRE–SRECOMPCS 30822 Number of relocation complete P B /// R8

at controlling MSC (subsequent
inter–MSC relocation)
OB–FRE–SRERCS 30823 Number of relocation released P B release R8

at controlling MSC (subsequent domain
OB–FRE–SPREPSS 30824 Number of relocation prepara- P B (RNC, R8

(subsequent inter–MSC reloca- RNC)
tion)
OB–FRE–SRECANS 30825 Number of relocation cancelled P B (RNC, R8

by the source RNC at serving adjacent
MSC (subsequent inter–MSC RNC)
relocation)
OB–FRE–SRECOMS 30826 Number of relocation command P B (RNC, R8

at serving MSC (subsequent adjacent
inter–MSC relocation) RNC)
OB–FRE–SRECOMPS 30827 Number of relocation complete P B (RNC, R8

at serving MSC (subsequent adjacent
inter–MSC relocation) RNC)
OB–FRE–SRERSS 30828 Number of relocation released P B release R8

at serving MSC (subsequent domain
OB–FRE–SREREQR 30829 Number of relocation resource P B RNC R8

allocation request at controlling/ name
target MSC (subsequent return (target)
OB–FRE–SREREQKR 30830 Number of relocation resource P B RNC R8

allocation acknowledge at con- name
trolling/target MSC (subse- (target)
quent return inter–MSC reloca-
tion)
OB–FRE–SRECOMPR 30831 Number of relocation complete P B RNC R8

at controlling/target MSC (sub- name
sequent return inter–MSC (target)
relocation)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 47 / 260
260
OB–FRE–S2GRERQA 30832 Number of relocation required P B (RNC, R7

(3G–>2G intra–MSC handover) local
BSC)
OB–FRE–S2GRECANA 30833 Number of relocation cancelled P B (RNC, R7

by the source RNC (3G–>2G local
intra–MSC handover) BSC)
OB–FRE–S2GRECOMA 30834 Number of relocation command P B (RNC, R7

(3G–>2G intra–MSC hand- local
over) BSC)
OB–FRE–S2GRE- 30835 Number of relocation complete P B (RNC, R7

COMPA (3G–>2G intra–MSC hand- local
over) BSC)
OB–FRE–S2GRERA 30836 Number of relocation released P B release R7

(3G–>2G intra–MSC hand- domain
over)
OB–FRE–S2GPREPE 30837 Number of relocation prepara- P B (RNC, R7

(3G–>2G inter–MSC handover) LAC)
(intra–PLMN case)
OB–FRE–S2GRECANE 30838 Number of relocation cancelled P B (RNC, R7

by the source RNC at control- adjacent
ling MSC (3G–>2G inter–MSC LAC)
handover)
(intra–PLMN case)
OB–FRE–S2GRECOME 30839 Number of relocation command P B (RNC, R7

at controlling MSC (3G–>2G adjacent
inter–MSC handover) LAC)
(intra–PLMN case)

COMPE at controlling MSC (3G–>2G adjacent
inter–MSC handover) LAC)
(intra–PLMN case)
OB–FRE–S2GRERE 30841 Number of relocation released P B release R7

at controlling MSC (3G–>2G domain
OB–FRE–S2GPREPSS 30842 Number of relocation prepara- P B (RNC, R8

(3G–>2G subsequent inter– LAC)
MSC handover)
1AA 00014 0004 (9007) A4 – ALICE 04.10
(intra–PLMN case)
ED 01
AAC020023800DS En 48 / 260
260
OB–FRE–S2GRECANS 30843 Number of relocation cancelled P B (RNC, R8

by the source RNC at serving adjacent
MSC (3G–>2G subsequent LAC)

(intra–PLMN case)
OB–FRE–S2GRECOMS 30844 Number of relocation command P B (RNC, R8

at serving MSC (3G–>2G sub- adjacent
sequent inter–MSC handover) LAC)
(intra–PLMN case)

COMPS at serving MSC (3G–>2G sub- adjacent
sequent inter–MSC handover) LAC)
(intra–PLMN case)
OB–FRE–S2GRERSS 30846 Number of relocation released P B release R8

at serving MSC (3G–>2G sub- domain
OB–FRE–S2GPREPEE 30847 Number of relocation prepara- P B (RNC, R7

tion request at controlling MSC MSC)
(3G–>2G inter–MSC handover)
(inter–PLMN case)
OB–FRE–S2GRECA- 30848 Number of relocation cancelled P B (RNC, R7

NEE by the source RNC at control- MSC)
ling MSC (3G–>2G inter–MSC
handover)
(inter–PLMN case)
OB–FRE–S2GRECO- 30849 Number of relocation command P B (RNC, R7

MEE at controlling MSC (3G–>2G MSC)
(inter–PLMN case)
OB–FRE–S2GRECOM- 30850 Number of relocation complete P B (RNC, R7

PEE at controlling MSC (3G–>2G MSC)
(inter–PLMN case)
OB–FRE– 30851 Number of relocation prepara- P B (RNC, R8

S2GPREPSSE tion request at serving MSC MSC)
(3G–>2G subsequent inter–
MSC handover)
(inter–PLMN case)
OB–FRE–S2GRE- 30852 Number of relocation cancelled P B (RNC, R8

CANSE by the source RNC at serving MSC)
1AA 00014 0004 (9007) A4 – ALICE 04.10
MSC (3G–>2G subsequent

(inter–PLMN case)
ED 01
AAC020023800DS En 49 / 260
260
OB–FRE–S2GRE- 30853 Number of relocation command P B (RNC, R8

COMSE at serving MSC (3G–>2G sub- MSC)

(inter–PLMN case)

COMPSE at serving MSC (3G–>2G sub- MSC)
(inter–PLMN case)
OB–FSC–IMEIINT 31001 Number of EIR interrogations P B /// R3
OB–FSC–IMEIWHITE 31002 Number of EIR answers P B /// R3

with white IMEI
OB–FSC–IMEIGREY 31003 Number of EIR answers P B /// R3

with grey IMEI
OB–FSC–IMEIBLACK 31004 Number of EIR answers P B /// R3

with black IMEI
OB–FSC–IMEIUNK- 31005 Number of EIR answers P B /// R3

NOWN with unknown IMEI
OB–FSW–SAEVRF 31101 Number of calls outgoing P B /// R2

from MSC
OB–FSW–EAEVRF 31102 Number outgoing calls from P B /// R2

(7) MSC and GMSC failures
OB–FSW–SNAEGMSC 31103 Number of incoming calls P B /// R2

from fixed network (GMSC)
OB–FSW–SNAEMSC 31104 Number of incoming calls P B /// R2

(VMSC)
OB–FSW–ENAEMSC 31105 Number of incoming call P B /// R2

(8) failures (VMSC)
OB–FSW–SIRAGMSC 31106 Number of interrogations P B /// R2

(9) for call rerouting (GMSC)
OB–FSW–EIRAGMSC 31107 Number of failures of P B /// R2

(10) interrogation for call
rerouting (GMSC) except
Forwarding Violation
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FSW–SARGMSC 31108 Number of forwarded calls P B /// R2

(GMSC)
ED 01
AAC020023800DS En 50 / 260
260
OB–FSW–EARGMSC 31109 Number of call forwarding P B /// R2

(12) refusals (GMSC)
OB–FSW–SAEGVRF 31110 Number of calls outgoing P B /// R2

from GMSC
OB–FSW–SRIGTW 31111 Number of interrogations P B /// R2

for call rerouting (GTW)
(This does not concern the
second interrogation in CAMEL
case)
OB–FSW–SRIGTWRES 31112 Number of interrogation P B /// R2

responses for call rerouting
with MSRN (GMSC)
OB–FSW–SRIGTWCF 31113 Number of interrogation P B /// R2

response for call rerouting
with forwarding
OB–FSW–SRIFWDVIOL 31114 Number of call forwarding P B /// R2

refusal for forwarding violation
(forwarded call uncond)
OB–FSW–SRIOC 31115 Number of interrogations P B /// R2

for call rerouting (MS OC)
(This does not concern the
second interrogation in CAMEL
case)
OB–FSW–SRIOCRES 31116 Number of responses for P B /// R2

interrogation for call
rerouting (MS OC) with MSRN
OB–FSW–SRIOCCF 31117 Number of responses for P B /// R2

rerouting (MS OC)
with forwarding
OB–FSW–SRICFMSC 31118 Number of interrogations P B /// R2

(26) for call rerouting
(forwarded calls)
OB–FSW–SRICFRES 31119 Number of responses for P B /// R2

(26) interrogation for call rerouting
(forwarded call) with MSRN
OB–FSW–SARVRF 31120 Number of forwarded calls P B /// R2

outgoing from MSC
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FSW–ACMGTW 31121 Number of successful P B /// R2

gateway procedures
ED 01
AAC020023800DS En 51 / 260
260
OB–FSW–GTWREL 31122 Number of gateway procedure P B release R2

release, per release domain domain
OB–FSW–SRIUNKSUB 31123 Number of failures of P B /// R2

interrogation for call rerouting
(GMSC) because of Unknown
Subscriber
OB–FSW–SRIABSSUB 31124 Number of failures of P B /// R2

(GMSC) because of Absent
Subscriber
OB–FSW–SRISNOTSU 31125 Number of failures of P B /// R2

rerouting (GMSC) because
of service not supported
OB–FSW–ANMGTW 31126 Number of efficient rerouted P B /// R4.1

calls
OB–FSW–FILMCF 31127 Number of routing on P B film R4.1

announcement number
OB–FSW–OPCALL 31128 Number of terminating operator P B /// R3+

calls received (RCF)
OB–FSW–OPINTR 31129 Number of interventions P B /// R3+

requested by operator
OB–FSW–IWFINSREQ 31130 Number of IWF insertion P B /// R4.1

request
OB–FSW–IWFINSRES 31131 Number of IWF insertion P B /// R4.1

result
OB–FSW–SRIGTW2 31132 Number of second Camel P B /// R4.2

(GTW)
OB–FSW–SRIOC2 31133 Number of second Camel P B /// R4.2

(MS OC)
OB–FSW–TONECF 31134 Number of routing on tone P B tone num- R4.1

ber
OB–FSW–OTC–SRI 31135 Number of received SRI result P B ///

with VlrContainer
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FSW–OTC–MSRN 31136 Number of local MSRN request P B ///
ED 01
AAC020023800DS En 52 / 260
260
OB–FSW–ODBECT 31137 Number of Explicit Call Transfer P B /// R5

refused due to ODB of Call
Transfer
OB–FSW–SHOP– 31138 Number of originating calls P B BSC

DENIED which cannot be continued as name
single hop calls, per originating
BSC
OB–FSW–IWFINS–OC– 31139 Number of IWF insertion P B ///

REQ requests in OC call using the
SSP generic function.
OB–FSW–IWFINS–OC– 31140 Number of IWF insertion P B ///

RES results in OC call using the SSP
generic function.
OB–FSW–IWFINS–TC– 31141 Number of IWF insertion P B ///

REQ requests in TC call using the
OB–FSW–IWFINS–TC– 31142 Number of IWF insertion P B ///

RES results in TC call using the SSP
generic function.
OB–FSW–IWFINS– 31143 Number of IWF insertion P B ///

MOD–REQ requests for MODIFY using the
OB–FSW–IWFINS– 31144 Number of IWF insertion P B ///

MOD–RES results for MODIFY using the
OB–FSW–SRIGTWCAM 31145 Number of first interrogation P B /// R5

response for CAMEL, without
FTN nor MSRN
OB–FSW–SRIOCCAM 31146 Number of first interrogation P B /// R5

responses for CAMEL (MS
OC), without FTN nor MSRN
OB–FRM–SASR 31501 Number of assignments of P B BSC R2

(13) radio resources (traffic channel) name
OB–FRM–EASR 31502 Number of radio resource P B /// R2

(14) (traffic channel)
assignment failures
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FRM–SHOIABSC 31503 Number of successful P B BSC R2

intra–BSC handovers name
per originating BSC
ED 01
AAC020023800DS En 53 / 260
260
OB–FRM–SDLIB 31504 Number of release requests P B BSC R2

(15) per originating BSC name
OB–FRM–OCASREQ 31505 Number of Radio Resource P B BSC/RNC R2

assignment requests for OC name
OB–FRM–OCASCOM 31506 Number of successful radio P B BSC/RNC R2

resource assignments for name
originating calls, per BSC/RNC
OB–FRM–TCASREQ 31507 Number of Radio Resource P B BSC/RNC R2

assignment requests for TC name
per destination BSC/RNC
OB–FRM–TCASCOM 31508 Number of successful radio P B BSC/RNC R2

resource assignments for name
terminating calls, per BSC/RNC
OB–FRM–RETRYREQ 31509 Number of directed retry P B BSC R3

handover request name
OB–FRM–RETRYACK 31510 Number of directed retry P B BSC R3

handover success name
OB–FRM–ESVUNVL 31511 Number of failures due to P B BSC R4.2

speech version unavailability name
OB–FRM–EASR–2 31512 Number of assignment failures P B BSC R4.2

with cause ’switch circuit pool’ name
or ’circuit pool mismatch’
per BSC
OB–FRM–POOL 31513 Number of assignment success P B BSC R4.2

with pool indication mismatch name
per BSC
OB–FRM–SHOPERF 31514 Number of Handover Per- P B ///

formed messages
with change in multislot configu-
ration
OB–FRM–FAXDOWN 31515 Number of Assignment Com- P B ///

plete messages with forced
downgrading for fax calls
OB–FRM–SHOP– 31516 Number of traffic channel re– P B BSC

REASS assignments requests due to name
single hop denial, per originat-
ing BSC
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 54 / 260
260
OB–FRM–LSANA 31517 Number of assignment failures P B BSC

with cause ’LSA not allowed’ name
per BSC
OB–FTR–ANARES 31601 Number of translations P B transla- R3

analysis results observed tion result
OB–FMP–START 32301 Number of requests to start a P B /// R4.2

multi–party call
OB–FMP–SUCCESS 32302 Number of successful multi– P B /// R4.2

party calls
OB–FLD–OVL 32701 Number of Overload message P B BSC/RNC R3+

received from BSC/RNC name
OB–FXX–SISS 33001 Number of invocations per P B Suppl. R2

supplementary services : Service (20)
Invocation of CALL BARRING, code
CALL WAITING,CALL HOLD, (16)
CALL FORWARDED,
MALICIOUS CALL IDENTIF,
CLOSED USER GROUP,
ADVICE OF CHARGE,
CLIP/CLIR, CALL BARRING,
COLP/COLR,
EXPLICIT CALL TRANSFER,
MULTIPARTY, CCBS, eMLPP
OB–FXX–ASS 33002 Number of acceptances per P B Suppl. R2

supplementary services : Service (20)
acceptance of code
CALL WAITING,CALL HOLD, (17)
CLOSED USER GROUP,
ADVICE OF CHARGE CHARG-
ING, COLP,
EXPLICIT CALL TRANSFER,
MULTIPARTY, CCBS, eMLPP
OB–FSH–REL 33003 Number of Supplementary P B release R2

service handling operation domain
releases, per release domain
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 55 / 260
260
OB–FDN–CONFUSION 33101 Number of Confusion mes- P B BSC R3

sages emitted toward a BSC
OB–FGP–SRP–GS 33501 Number of Paging repetitions P B /// R6

via Gs interface
OB–FGP–ERP–CGS 33502 Number of Paging failures on P B /// R6

Gs–Interface due to Absent
subscriber for calls
OB–FGP–ERP–UGS 33503 Number of Paging failures on P B /// R6

Gs–Interface due to Absent
subscriber for call unrelated
services (including Location
services LCS)
OB–FMO–MSTRREQ 34601 Number of RP–DATA sent P B /// R3+

by the MS
OB–FMO–MSALREQ 34602 Number of RP_SMMA sent by P B /// R3+

the MS
OB–FMO–SSMTR 34603 Number of successful short P B /// R3+

message transfer
OB–FMO–SALERT 34604 Number of successful P B /// R3+

memory available alerting
OB–FMO–OFSMREQ 34605 Number of Forward Short P B /// R3+

message request sent
OB–FMO–SIFSM 34606 Number of Forward Short P B /// R3+

message result received
OB–FMO–IFSMREQ 34607 Number of Forward Short P B /// R3+

message request received
OB–FMO–SOFSM 34608 Number of Forward Short P B /// R3+

message result sent
OB–FMO–SCREQ 34609 Number of RP–DATA sent P B /// R3+

to the SC
OB–FMO–SCACK 34610 Number of RP–ACK received P B /// R3+

from the SC
OB–FMO–REL 34611 Number of SMO procedure P B release R3+

1AA 00014 0004 (9007) A4 – ALICE 04.10
release, per release domain domain
ED 01
AAC020023800DS En 56 / 260
260
OB–FOR–SRIINV 34701 Number of ’send routeing info’ P B /// R5

invoke with OR interrogation
OB–FOR–BASICOR 34702 Number of calls optimally P B /// R5

routed with basic OR (the calls
are routed with an MSRN).
OB–FOR–EARLYCF 34703 Number of calls optimally P B /// R5

routed with an FTN (early call
forwarding case).
OB–FOR– 34704 Number of Resume Call Han- P B /// R5

RCHINVGMSC dling requests received at
GMSC.
OB–FOR–LATECF 34705 Number of calls optimally P B /// R5

routed with an FTN (late call for-
warding case).
OB–FOR– 34706 Number of Resume Call Han- P B /// R5

RCHINVVMSC dling requests sent by a VMSC.
OB–FOR–RCHRES 34707 Number of Resume Call Han- P B /// R5

dling results (positive response)
received at VMSC
OB–FOR–SRI–FOR 34708 Number of ’send routeing info’ P B /// R5

invoke with interrogation type
’forwarding’
OB–FDA–SIWF–OC 34801 Number of successful P B basic R2

IWF connection service
for outgoing data calls
OB–FDA–SIWF–TC 34802 Number of successful P B basic R2

IWF connection service
for incoming data calls
OB–FDA–EACK–OC 34803 Number of IWF connection fail- P B basic R2

ure for outgoing data calls : service
connection acknowledge
is not successful
OB–FDA–EACK–TC 34804 Number of IWF connection fail- P B basic R2

ure for incoming data calls : service
connection acknowledge
is not successful
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FDA–ESIMP 34805 Number of IMPULSE error P B SMIM R2

signalled by SMIM on data calls name
ED 01
AAC020023800DS En 57 / 260
260
OB–FDA–ESON 34806 Number of error signalled by P B SMIM R2

SMIM on data calls name
OB–FDA–SIWFOCREQ 34807 Number of IWF connection P B basic R2

request for outgoing call service
OB–FDA–SIWFTCREQ 34808 Number of IWF connection P B basic R2

request for incoming call service
OB–FDA–CMMREQ 34809 Number of channel mode Pl B (data R3

modify procedures speed,
data
speed)
OB–FDA–CMMCONF 34810 Number of channel mode Pl B (data R3

modify success speed,
data
speed)
OB–FDA–FORCERL 34811 Number of data call release P B basic R3+

forced by SMIM service
OB–FDA–MODREQ 34812 Number of In–call modification P B /// R4.1

procedure request
OB–FDA–MODRES 34813 Number of In–call modification P B /// R4.1

procedure result
OB–FDA–FRSYNC 34814 Number of data call release P B /// R4.2

forced by SMIM due to synchro-
nisation problems
OB–FDA–FRRLP 34815 Number of data call release P B /// R4.2

forced by SMIM due to RLP
problems
OB–FDA–FRV42 34816 Number of data call release P B /// R4.2

forced by SMIM due to V.42
problems
OB–FDA–FRX25 34817 Number of data call release P B /// R4.2

forced by SMIM due to X.25
problems
OB–FDA–FRFAX 34818 Number of data call release P B /// R4.2

forced by SMIM due to FAX pro-
tocol problems
OB–FDA–FRINT 34819 Number of data call release P B /// R4.2

forced by SMIM due to internal
1AA 00014 0004 (9007) A4 – ALICE 04.10
failure
ED 01
AAC020023800DS En 58 / 260
260
OB–FDA–FRBUF 34820 Number of data call release P B /// R4.2

forced by SMIM due to buffer
overflow
OB–FDA–COMPOC 34821 Number of outgoing data calls P B basic R5

performed with compression. service
(22) (24)
OB–FDA–COMPTC 34822 Number of terminated data calls P B basic R5

performed with compression. service
(22) (24)
OB–FDA–UIMREQ 34823 Number of user initiated P B ///

modification procedure request
OB–FDA–UIMRES 34824 Number of user initiated P B ///

modification procedure result
OB–FDA–OHSCSD– 34825 Number of HSCSD (multislot P B (Nb TCH,

REQ and 14.4 singleslot) outgoing basic ser-
request vice) (23)
OB–FDA–THSCSD– 34826 Number of HSCSD (multislot P B (Nb TCH,

REQ and 14.4 singleslot) terminating basic ser-
request vice) (23)
OB–FDA–OFBACK 34827 Number of HSCSD (multislot P B basic

and 14.4 singleslot) outgoing service
request leading to use of fall- (23) (24)
back GSM–BC
OB–FDA–TFBACK 34828 Number of HSCSD (multislot P B basic

and 14.4 singleslot) terminating service
request leading to use of fall- (23) (24)
back GSM–BC
OB–FDA–SHSCSD 34829 Number of successful multislot P B (Nb of

call requested
TCH,Nb
of allo-
cated
TCH)
OB–FDA–S14–4 34830 Number of successful 14.4 P B Nb of

singleslot call requested
TCH
OB–FDA–OCDATATT 34831 Number of originating fax/data P B ITC

call attempts.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 59 / 260
260
OB–FDA–TCDATATT 34832 Number of terminated fax/data P B ITC

call attempts.
OB–FDA–OCDATANS 34833 Number of answered originat- P B ITC

ing fax/data calls.
OB–FDA–TCDATANS 34834 Number of answered termi- P B ITC

nated fax/data calls.
OB–FDA–UMMOC 34835 Number of UMTS Multimedia P B ITC/ R7

outgoing calls. FNUR
OB–FDA–UMMTC 34836 Number of UMTS Multimedia P B ITC/ R7

terminated calls. FNUR
OB–FDA–UBS20OC 34837 Number of UMTS BS20 origi- P B ITC/GBR R7

nating calls.
OB–FDA–UBS20TC 34838 Number of UMTS BS20 termi- P B ITC/GBR R7

nated calls.
OB–FCT–INVTR 34901 Number of Invoke Trace sent to P B BSC/RNC R3

the BSC/RNC name
OB–FCT–INVTRHO 34902 Number of Invoke Trace P B /// R3

forwarded through Prepare
Handover
OB–FCCB–RQ 35001 Number of CCBS requests P B ///

received from the MS
OB–FCCB–CALL–A 35002 Number of successful CCBS P B ///

calls on the A side
OB–FCCB–CALL–B 35003 Number of successful CCBS P B ///

calls on the B side
OB–FCCB–REC–CALLB 35004 Number of CCBS calls received P B ///

on the B side
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 60 / 260
260
OB–FCS–AOCPC 35101 Number of outgoing calls P B Carrier R5

attempts per carrier identity
OB–FCS–ACFPC 35102 Number of forwarded calls P B Carrier R5

attempts per carrier identity
OB–FCS–ARRPC 35103 Number of rerouted or transit P B Carrier R5

calls attempts per carrier identity
OB–FCS–IGWPC 35104 Number of incoming gateway or P B Carrier R5

transit calls per carrier identity
OB–FCS–ITCPC 35105 Number of terminating calls per P B Carrier R5

carrier identity
OB–FVH–FALLBACK 35401 Number of MAP version P B /// R3

fallbacks
OB–FVH–FALLBACKUN 35402 Number of unexpected P B /// R3

MAP version fallbacks
OB–FVH–PHASE1CNX 35403 Number of connections P B /// R3

with MS phase 1
OB–FVH–PHASE2CNX 35404 Number of connections P B /// R3

with MS phase 2
OB–FVH– 35405 Number of call independant P B /// R3

PHASE1–TRANS SS transactions
with MS handled in phase 1
OB–FVH– 35406 Number of call independant P B /// R3

PHASE2–TRANS SS transactions
with MS handled in phase 2
OB–FVH–R99CNX 35407 Number of connections P B /// R7

with MS Release 99 at least
OB–FCA–INDPIDP02 35701 Number of Initial DP Invoke at P B E.164 R4.2

DP02 CA interface PLMN
address
OB–FCA–INDPRDP02 35702 Number of Response to Initial P B E.164 R4.2

DP Invoke at DP02 CA interface PLMN
(Connect or Continue or Conti- address
nueWithArgument or Release
1AA 00014 0004 (9007) A4 – ALICE 04.10
Call)
ED 01
AAC020023800DS En 61 / 260
260
OB–FCA–INDPIDP12 35703 Number of Initial DP Invoke at P B E.164 R4.2

DP12 CA interface PLMN
address
OB–FCA–INDPRDP12 35704 Number of Response to Initial P B E.164 R4.2

DP Invoke at DP12 CA interface PLMN
(Connect or Continue or Conti- address
nueWithArgument or Release
Call)
OB–FCA– 35705 Number of Event Report BCSM P B E.164 R4.2

EVRPBCSMDP07 at DP07 CA interface PLMN
address

address

address

address
OB–FCA– 35709 Number of Event Report BCSM P B E.164 R5

address

address

address

address

address

address
1AA 00014 0004 (9007) A4 – ALICE 04.10

address
ED 01
AAC020023800DS En 62 / 260
260
OB–FCA–APPCHGREQ 35718 Number of Apply Charging P B E.164 R5

request received at CA inter- PLMN
face address
OB–FCA–APPCHGREP 35719 Number of Apply Charging suc- P B E.164 R5

cessful PLMN
address
OB–FCA–CALLINFO- 35720 Number of Call Information P B E.164 R5

REQ request received at CA inter- PLMN
face address
OB–FCA–CALLIINFO- 35721 Number of Call Information suc- P B E.164 R5

REP cessful PLMN
address
OB–FCA–ETCREQ 35722 Number of Establish Temporary P B E.164 R5

Connection request received at PLMN
CA interface address
OB–FCA–ETC 35723 Number of Establish Temporary P B E.164 R5

Connection successful PLMN
address
OB–FCA–DFCREQ 35724 Number of Disconnect Forward P B E.164 R5

Connection request received at PLMN
OB–FCA–DFC 35725 Number of Disconnect Forward P B E.164 R5

Connection successful PLMN
address
OB–FCA–RESETTIM- 35726 Number of Reset Timer request P B E.164 R5

REQ received at CA interface PLMN
address
OB–FCA–RESETTIM 35727 Number of Reset Timer suc- P B E.164 R5

cessful PLMN
address
OB–FCA–FCIREQ 35728 Number of Furnish Charging P B E.164 R5

Information request received at PLMN
OB–FCA–FCI 35729 Number of Furnish Charging P B E.164 R5

Information successful PLMN
address
OB–FCA–SCIREQ 35730 Number of Send Charging P B E.164 R5

Information request received at PLMN
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 63 / 260
260
OB–FCA–SCI 35731 Number of Send Charging P B E.164 R5

Information successful PLMN
address
OB–FCA–CANCELREQ 35732 Number of Cancel request P B E.164 R5

received at CA interface PLMN
address
OB–FCA–CANCEL 35733 Number of Cancel successful P B E.164 R5

PLMN
address
OB–FCA–CALLGA- 35734 Number of Call Gap requests P B ///

PREQ received from the SCPs and
accepted.
OB–FCA–CALLGAPREJ 35735 Number of calls rejected by call P B E.164

gapping per SCP SCP
address
OB–FCA–DISCONLE- 35736 Number of Disconnect Leg P B E.164

GREQ requests received from the PLMN
SCPs and accepted. address
OB–FCA–DISCONLEG 35737 Number of Disconnect Leg suc- P B E.164

cessful PLMN
address
OB–FCA–REQBSCM 35738 Number of Request Report P B E.164 R5

BCSM Event message PLMN
address
OB–FCA–SMINIDP1 35739 Number of initial–DP–SMS at P B E.164 R8

DP1 PLMN
Address
OB–FCA–SMINRDP1 35740 Number of response to Initial– P B E.164 R8

DP–SMS at DP1 PLMN
Address
OB–FCA– 35741 Number of Request Report P B E.164 R8

SMRQRPSMSEVT SMS Event PLMN
Address
OB–FCA– 35742 Number of Event Report SMS at P B E.164 R8

SMRQRPSMSDP2 DP2 PLMN
Address
OB–FCA– 35743 Number of Event Report SMS at P B E.164 R8

SMRQRPSMSDP3 DP3 PLMN
1AA 00014 0004 (9007) A4 – ALICE 04.10
Address
ED 01
AAC020023800DS En 64 / 260
260
OB–FCA–SMRESE- 35744 Number of Reset Timer SMS P B E.164 R8

TREQ Request received from the SCP PLMN
Address
OB–FCA–SMRESET- 35745 Number of Reset Timer SMS P B E.164 R8

SUC successful PLMN
Address
OB–FCA–SMFCIREC 35746 Number of Furnish Charging P B E.164 R8

Information SMS received PLMN
Address
OB–FCA–SMFCISUC 35747 Number of Furnish Charging P B E.164 R8

Information SMS successful PLMN
Address
OB–FNP–QOHR 35801 Number of NPDB query on HLR P B ///

release (QoHR).
OB–FNP–ROHR 35802 Number of NPDB response with P B ///

CONNECT further to QoHR.
OB–FNP–TQOD 35803 Number of NPDB query for TC P B ///

on digits analysis (TQoD)
OB–FNP–TROD 35804 Number of NPDB response with P B ///

CONNECT for TC (TQoD)
OB–FNP–OQOD 35805 Number of NPDB query for OC P B ///

on digits analysis (OQoD)
OB–FNP–OROD 35806 Number of NPDB response with P B ///

CONNECT for OC (OQoD)
OB–FNP–FQOD 35807 Number of NPDB query for CF P B ///

on digits analysis (OQoD)
OB–FNP–FROD 35808 Number of NPDB response with P B ///

CONNECT for CF (OQoD)
OB–FNP–RRPLMN 35809 Number of calls rerouted to a P B PLMN R6

ported subsciber per destina- name
tion PLMN
OB–FNP–NPDBF 35810 Number of NPDB querry failure P B ///
OB–FLSA–MMINF 35901 Number of MM information P B ///

1AA 00014 0004 (9007) A4 – ALICE 04.10
messages due to SoLSA fea-

ture sent to MS
ED 01
AAC020023800DS En 65 / 260
260
OB–FLSA–LSAINF 35902 Number of LSA information P B BSC

messages per BSC name
OB–FALR–PAGING 36001 Number of Paging sent on A–In- P B ///

terface or Iu interface for Active
location retrieval ALR
OB–FMLP–MOPROC 36101 Number of authorized MO calls P B Priority,

per priority level, per BSC/RNC BSC/RNC
name
OB–FMLP–MOALERT 36102 Number of delivered MO calls P B Priority,

name
OB–FMLP–MTSETUP 36103 Number of authorized MT calls P B Priority,

name
OB–FMLP–MTALERT 36104 Number of delivered MT calls P B Priority,

name
OB–FLCS–LOCREQ 36201 Number of Location Reporting P B BSC/RNC R8

Control (Iu interface) or Perform
Location Request (A interface)
messages sent for LCS ser-
vices
OB–FLCS–LOCRES 36202 Number of Location Report (Iu P B BSC/RNC R8

interface) or Perform Location
Response (A interface) mes-
sages received for LCS ser-
vices
OB–FLCS–MTLRREQ 36203 Global number of Mobile termi- P B R8

nating location request MT_LR ///
received from GMLC for LCS
services
OB–FLCS–CURMTLR- 36204 Number of Call unrelated P B R8

REQ Mobile terminating location ///
request MT_LR received from
GMLC for LCS services
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 66 / 260
260
OB–FLCS– 36205 Number of Call unrelated P B R8

CURMTLRRES Mobile terminating location ///
request MT_LR result sent to

GMLC for LCS services
OB–FLCS– 36206 Number of Call related Mobile P B R8

CRMTLRREQ terminating location request ///
MT_LR received from GMLC
for LCS services
OB–FLCS– 36207 Number of Call related Mobile P B R8

CRMTLRRES terminating location request ///
MT_LR result sent to GMLC for
LCS services
OB–FLCS–LOCNOTS 36210 Number of Location Notification P B R8

sent to the MS for Mobile Termi- ///
nating location request MT_LR
LCS services
OB–FLCS–LOCNOTR 36211 Number of Location Notification P B R8

result received from the MS for ///
Mobile Terminating location
request MT_LR LCS services
OB–FLCS–MOLRREQ 36212 Number of Mobile Originating P B

location request MO_LR ///
received from MS for LCS ser-
vices
OB–FLCS–MOLRRES 36213 Number of Mobile Originating P B

location request MO_LR result ///
sent to MS for LCS services
OB–FLCS–LOCREPIMO 36214 Number of Subscriber Location P B

report invoke sent to the GMLC ///
for Mobile Originating location
request MO_LR LCS services
OB–FLCS– 36215 Number of Subscriber Location P B

LOCREPRMO report result received from the ///
GMLC for Mobile Originating
location request MO_LR LCS
services
OB–FLCS–LOCREPINI 36216 Number of Subscriber Location P B

report invoke sent to the GMLC ///
for Network Initiated location
request NI_LR LCS services
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 67 / 260
260
OB–FLCS–LOCREPRNI 36217 Number of Subscriber Location P B

report result received from the ///
GMLC for Network Initiated

location request NI_LR LCS
services
OB–FLCS–MTLRREL 36218 Number of Mobile Terminating P B Release R8

LCS MT_LR procedure release domain
OB–FLCS–MOLRREL 36219 Number of Mobile Originating P B Release

LCS MO_LR procedure release domain
OB–FUU–PUUSOC 39501 Number of mobile originating P B ///

calls with PUUS service acti-
vated implicitly
OB–FUU–PUUSTC 39502 Number of mobile terminating P B ///

calls with PUUS service acti-
vated implicitly
OB–FUU–UUIMSN 39503 Number of UUI transferred from P B ///

MS to network during originat-
ing call and terminating call
OB–FUU–UUINMS 39504 Number of UUI transferred from P B ///

network to MS during originat-
ing call and terminating call
OB–FSM–SCREQ 39801 Number of request for P B /// R2

Short Message connection
OB–FSM–SSMTX 39802 Number of Short Message P B /// R2

transfer successful
OB–FSM–OFWREQ 39803 Number of Forward Short P B /// R2

message (invoke) request
OB–FSM–ISFW 39804 Number of Forward Short P B /// R2

message successful
OB–FSM–RGREQ 39805 Number of Send Routing Info P B /// R2

for Short Message request
OB–FSM–SRG 39806 Number of Send Routing Info P B /// R2

1AA 00014 0004 (9007) A4 – ALICE 04.10
for Short Message result
ED 01
AAC020023800DS En 68 / 260
260
OB–FSM–MWDREQ 39807 Number of Message Waiting P B /// R2

(18) Data / report SM delivery
status request
OB–FSM–SMWD 39808 Number of Message Waiting P B /// R2

(18) Data / report SM delivery
status success
OB–FSM–ALSC 39809 Number of Alert message P B /// R2
OB–FSM–IFWREQ 39810 Number of Forward Short P B /// R2

message (invoke) request
OB–FSM–OSFW 39811 Number of Forward Short P B /// R2

message successful
OB–FSM–OEFW 39812 Number of Forward Short P B /// R2

message unsuccessful due
to ”absent Subscriber” or
”absent subscriber SM” (MAP
v3)
OB–FSM–RCFREQ 39813 Number of Short message P B /// R2

sent to the MS
OB–FSM–SSMRX 39814 Number of Short message P B /// R2

correctly received by MS
OB–FSM–REL 39815 Number of Short message P B release R2

terminating calls releases domain
per release domain
OB–FSM–SODBSMOC 39816 Number of Short message P B /// R4.1

outgoing calls refused due to
ODB of outgoing calls
OB–FSM–IEFW 39817 Number of received Forward P B /// R4.3

Short message unsuccessful
due to ”absent Subscriber” or
v3)
OB–FSM–GTWREL 39818 Number of Short message P B release R5

gateway procedures released, domain
per release domain
OB–FSM–OFWREQS 39819 Number of Forward Short P B /// R5.2

message (invoke) request sent
to SGSN
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–FSM–ISFWS 39820 Number of Forward Short P B /// R5.2

message successful from
SGSN
ED 01
AAC020023800DS En 69 / 260
260
OB–FSM–IEFWS 39821 Number of received Forward P B /// R5.2

Short message unsuccessful
due to ”absent Subscriber” or

v3) from SGSN
Reserved counter 39822 P B ///
Reserved counter 39823 P B ///
OB–FIN–INDPI 39901 Number of InitialDP invoke P B Service R3

at the IN interface Key
OB–FIN–INDPE 39902 Number of InitialDP errors P B Service R3

OB–FIN–RELCALL 39903 Number of Release Call P B Service R3

OB–FIN–CONNECT 39904 Number of Connect P B Service R3

OB–FIN–CONTINUE 39905 Number of Continue P B Service R3

OB–FIN–NETWORK 39906 Number of routing towards a P B Service R3

network server (OC case, TC Key
case and IN invocation after a
forwarding case)
Note :
(2) This counter is included in FOC–REL but is kept for compatibility reason.
(3) This counter is also incremented by TC function.
(4) This counter is identical to FXX–SISS(CFxxINV) but is kept for compatibility reason.
(5) These events are also counted per couple (origin BSC,target BSC). The counter is kept for compatibility
reason.
(6) These events are also counted per couple (origin BSC,target LAC). The counter is kept for compatibility
reason.
(7) This counter is included in FTC–REL and FSW–GTWREL counters but is kept for compatibility reason.
(8) This counter is included in FTC–REL counters but is kept for compatibility reason.
1AA 00014 0004 (9007) A4 – ALICE 04.10
(9) This counter is identical to FSW–SRIOC + FSW–SRIGTW +FSW–SRICFMSC but is kept for compati-
bility reason.
ED 01
AAC020023800DS En 70 / 260
260
(10) Results are counted but this counter is kept for compatibility reason.
(12) This counter is identical to FSW–SRIWDVIOL but is kept for compatibility reason.
(13) This counter is replaced by counters per BSC and per procedure type:FRM–OCASCOM, FRM–
TCASCOM, FHO–SHOAREQACK, FHO–SHOBREQACK, FHO–SHOSAREQACK but it is kept for com-

patibility reason.
(14) Success are counted but this counter is kept in for compatibility reason.
(15) This counter is included in release counters but it is kept in for compatibility reason.
(16) The list of Supplementary Service codes for the counter OB–FXX–SISS is given in 4.1.4 page 105
by the ”List of SupplementaryService codes for invocations counters”.
(17) The list of Supplementary Service codes for the counter OB–FXX–ASS is given in 4.1.4 page 105
by the ”List of SupplementaryService codes for acceptance counters”.
(18) Since R4.1, these counters are incremented for MAP phase 1 and MAP phase 2 messages.
(19) If option F–OBS–003 is active, these counters are not sent to the OMC (they are not got by the func-
tional module OBS from Application functional modules and, so, are not sent by OBS to the functional mod-
ule ACQUISITION, see chapter 1).
(20) counter availability depends on SS availability according to release contents.
(21)These counters are got by the functional module OBS from the Application and sent to the OMC only
if option F–OBS–004 is active. Nevertheless, these counters are increased by the Application whatever
the value of F–OBS–004 is.
(22) The possible basic services when data compression is used are GBS20, BS25 or BS26.
(23) The possible basic services when HSCSD is requested are GBS20, GBS30, GBS40, TS61, TS62,
BS61A, BS61S, BS81A , BS81S.
(24) The counters sent to the OMC are those which are different from zero
(25) In case of quick release, these counters are not incremented.
(26) Since R4, these counters are not incremented.
(27) not incremented when rejected for regulation cause.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 71 / 260
260
2.2 Detailed description in the VLR
2.2.1 Functional environment of the function in the unit
CCP Call Completion Services

CT Call Tracing
IN (1) Intelligent Network
LR Location Registration
I 201
NR National Roaming or
PG Paging I 206
LCS Location services OBS. ACQ. OMC
SC Security
SH Suppl. Services Handling
TC Terminating Call
TCAP (1)
VH (1) Version Handling
GP General Packet Radio Service
VLR
(1) VLR and RCF TCAP IN and VH counters are merged in RCP counters and trans-
mitted in RCF ticket
Figure 4. Functional description of Observation in the VLR

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 72 / 260
260
2.2.2 List of VLR observations to be sent to the OMC



C = Coding mode
Rel. = Release of appearance (starting as from R2): if the release is not specified, the counter
is not available
OB–VPG–SNPAG 20301 Number of paging requests P B /// R2

(1)
OB–VPG–ENPAG 20302 Number of paging request P B /// R2

(2) failures
OB–VPG–PAGING 20303 Number of paging requests for ter- P B /// R2

minating calls
OB–VPG–SEARCH 20304 Number of search requests for ter- P B /// R2

minating calls
OB–VPG– 20305 Number of successful P B /// R2

PAGSRCHRES paging/search for terminating calls
OB–VPG–PAGING–SM 20306 Number of paging requests for P B /// R5

short messages terminating
OB–VPG–SEARCH–SM 20307 Number of search requests for P B /// R5

short messages terminating
OB–VPG– 20308 Number of successful paging/ P B /// R5

PAGSRCHRES–SM search for short messages termi-
nating
OB–VLR–SANL 20401 Number of registration P B LAC R2

(3) (7) cancellations, per location area
OB–VLR–SNIA 20402 Number of subscribers L B //// R2

currently registered in the VLR
OB–VLR–SNI 20403 Number of registrations, per loca- P B LAC R2

(7) tion area
OB–VLR–ENI 20404 Registration failures P B /// R2
OB–VLR–CANLOC– 20405 Number of registration P B /// R2

1AA 00014 0004 (9007) A4 – ALICE 04.10
HOM cancellation from home HLR
ED 01
AAC020023800DS En 73 / 260
260
OB–VLR–CANLOC– 20406 Number of registration P B /// R2

OTH cancellation from other HLR
OB–VLR–OLVLRUKN 20407 Number of registration P B /// R2

requests from unknown VLRs
OB–VLR–OLVLRSP 20408 Number of send parameter P B /// R2

REQ requests received in VLR
(4)
OB–VLR–HLRLOCREQ 20409 Number of location updates P B /// R2

towards HLRs
OB–VLR–HLRLOCRES 20410 Number of location update P B /// R2

responses from HLRs
OB–VLR–UNAUTHVISIT 20411 Number of MS registrations P B /// R2

request from unauthorized
PLMNs
OB–VLR–AUTHVISIT 20412 Number of authorized other PLMN P B /// R2

mobile registrations
OB–VLR–ROAMNALL 20413 Number of unauthorized mobile P B /// R2

location updating requests
OB–VLR–EXTORI–LAC 20414 Number of registrations request P B /// R2

from external originating lac
OB–VLR–MS–UNKN 20415 Number of registrations request P B /// R2

from internal originating lac but
unknown in VLR
OB–VLR–HLRCONF– 20416 Number of location updates P B /// R2

FLAG to HLRs due to the set of
HLR conf flag
OB–VLR–PURGEREQ 20417 Number of PurgeMS P B /// R3

requests to HLR
OB–VLR–PURGERES 20418 Number of PurgeMS P B /// R3

responses from HLR
OB–VLR–RESTOREQ 20419 Number of RestoreData P B /// R3

requests to HLR
OB–VLR–RESTORES 20420 Number of RestoreData P B /// R3

responses from HLR
OB–VLR–OLVLRSPRES 20421 Number of send parameter re– P B /// R4.1

1AA 00014 0004 (9007) A4 – ALICE 04.10
sult sent for old VLR
OB–VLR– 20422 Number of send parameter P B /// R4.1

NWVLRSPREQ request sent for new VLR
ED 01
AAC020023800DS En 74 / 260
260
OB–VLR– 20423 Number of send parameter re– P B /// R4.1

NWVLRSPRES sult received in new VLR
OB–VLR–IMPDET 20424 Number of implicit detach P B /// R4.1
OB–VLR–DSDREQ 20425 Number of delete subscriber P B /// R4.1

data request received
OB–VLR–DSDRES 20426 Number of delete subscriber P B /// R4.1

data success sent
OB–VLR–SAISDREQ 20427 Number of stand–alone ISD P B /// R4.1

request from HLR
OB–VLR–SAISDRES 20428 Number of stand–alone ISD P B /// R4.1

result to HLR
OB–VLR–ISDREQ 20429 Number of framed ISD pro– P B nb of msgs R4.1

cedure request from HLR
OB–VLR–ISDRES 20430 Number of framed ISD pro– P B nb of msgs R4.1

cedure result to HLR
OB–VLR–NOHLRUPD 20431 Number of successful P B /// R4.1

intra VLR location updating
OB–VLR–PSIREQ 20432 Number of Provide Subscriber P B /// R4.2

Information Request message
received
OB–VLR–PSIRES 20433 Number of Provide Subscriber P B /// R4.2

Information Result message sent
OB–VLR–SANLGLO 20451 Total number of registration P B /// R4.1

(8) cancellations
OB–VLR–SNIGLO 20453 Total number of registrations P B /// R4.1

(8)
OB–VLR–SNIAP 20454 Number of subscribers currently L B E.212 R5

(9) (10) registered in the VLR per PLMN PLMN
address
OB–VLR–SATTGSNA 20455 Number of subscribers currently L B ///

(11) registered in the VLR with status
”IMSI attach” and ”GPRS detach”
(including non GPRS MS).
OB–VLR–SATTGSAS 20456 Number of subscribers currently L B ///

(11) registered in the VLR with status
1AA 00014 0004 (9007) A4 – ALICE 04.10
”IMSI attach” and ”GPRS attach”.
ED 01
AAC020023800DS En 75 / 260
260
OB–VLR–SATTGSNAP 20457 Number of subscribers currently L B E.212

(9) (10) (11) registered in the VLR with status PLMN
”IMSI attach” and ”GPRS detach” address

(including non GPRS MS). One
counter per PLMN
OB–VLR–SATTGSASP 20458 Number of subscribers currently L B E.212

(9) (10) (11) registered in the VLR with status PLMN
”IMSI attach” and ”GPRS attach”. address
One counter per PLMN
OB–VTC–RES–BS– 20601 Number of MSRN provision P B basic R2

MSRN request results service
OB–VTC–REQ–BS 20602 Number of terminating P B basic R2

call requests ( to VMSC) service
OB–VTC–REQ–MSRN 20603 Number of MSRN provision P B /// R2

(12) requests
OB–VTC–EMSRN–ABS- 20604 Number of MSRN provision P B /// R2

SUB request failures because
of Absent Subscriber
OB–VTC–EMSRN– 20605 Number of MSRN provision P B /// R2

FNOTSU request failures because
of Facility not supported
OB–VTC–EMSRN– 20606 Number of MSRN provision P B E.164 R3

FNOTSU2 request failures because PLMN
of Facility not supported address
(per E.164 PLMN address)
OB–VTC–MSRN–REJ 20607 Number of Roaming Number P B /// R4.1

request reject for regulation cause
OB–VSC–SDTRH 21001 Number of Authentication vectors P B /// R2

(4) requests
OB–VSC–EDTRH 21002 Number of Authentication vectors P B /// R2

(4) request failures
OB–VSC–SDAUT 21003 Number of authentication P B /// R2

requests with triplets
OB–VSC–EDAUT 21004 Number of unsuccessful authenti- P B /// R2

1AA 00014 0004 (9007) A4 – ALICE 04.10
cation with triplets
OB–VSC–SNREAC 21005 Number of ciphering commands P B /// R2

under GSM/BSS coverage
ED 01
AAC020023800DS En 76 / 260
260
OB–VSC–ENREAC 21006 Number of unsuccessful ciphering P B /// R2

commands under GSM/BSS cov-
erage
OB–VSC–SNREAT 21007 Number of TMSI reallocation P B /// R2
OB–VSC–ENREAT 21008 Number of TMSI reallocation fail- P B /// R2

ures
OB–VSC–EALGO 21009 Number of key reallocation P B /// R2

failures due to A5–X algo.
incompatibility under GSM/BSS
coverage
OB–VSC–TRREUSED 21010 Number of Triplet reused P B /// R4.1
OB–VSC–ERALG 21011 Number of Key reallocation fail- P B /// R7

ures due to algorithm incompatibil-
ity under UTRAN coverage
OB–VSC–EAUTH 21012 Number of Authentication request P B /// R7

failures with quintuplets
OB–VSC–ECIPH 21013 Number of unsuccessful ciphering P B /// R7

commands under UTRAN cover-
age
OB–VSC–URAUT 21014 Number of authentication request P B /// R7

with quintuplets
OB–VSC–NBCIPH 21015 Number of ciphering request P B /// R7

under UTRAN coverage
OB–VSC–ERESYN 21016 Number of Authentication Failure P B /// R7

with ”Synchro failure” cause
(Authentication with quintuplets
only)
OB–VSC–EAFAIL 21017 Number of Authentication Failure P B /// R7

with ”MAC failure” cause (Authen-
tication with quintuplets only)
OB–VSH–SNOSS 23001 Number of supplementary P B Suppl. R2

(5) service operations per SS Service
(interrogations) code
OB–VSH–ENOSS 23002 Number of supplementary P B Suppl. R2

(6) service operation failures Service
1AA 00014 0004 (9007) A4 – ALICE 04.10
per SS code
ED 01
AAC020023800DS En 77 / 260
260
OB–VSH–USS 23003 Number of unstructured P B /// R3

supplementary services
operation requests
OB–VSH–SUSS 23004 Number of unstructured P B /// R3

supplementary services
operation success
OB–VSH–AR 23005 Number of USSD request for P B /// R3+

automatic relocation
OB–VSH–SAR 23006 Number of USSD success for P B /// R3+

OB–VSH–REGPWREQ 23007 Number of register password P B /// R4.1

request sent
OB–VSH–REGPWRES 23008 Number of register password P B /// R4.1

result received
OB–VSH–SODBSH 23009 Number of operations refused due P B /// R4.1

OB–VSH–NIUR 23010 Number of received NI USSD P B /// R5

requests without
OB–VSH–SNIUR 23011 Number of successful NI USSD P B /// R5

requests without
OB–VSH–NIUN 23012 Number of received NI USSD noti- P B /// R5

fications
OB–VSH–SNIUN 23013 Number of successful NI USSD P B /// R5

notifications
OB–VGP–PAGREQ 23501 Number of Paging Request sent to P B /// R6

a SGSN, including Paging
Request message for SMT,LCS,..
OB–VGP–PAGREJ 23502 Number of Paging Reject P B /// R6

received from a SGSN, including
Paging Reject message for SMT,
LCS,..
OB–VGP–UNREACH 23503 Number of MS_Unreachable P B /// R6

received from a SGSN, including
1AA 00014 0004 (9007) A4 – ALICE 04.10
MS_Unreachable message for

SMT
ED 01
AAC020023800DS En 78 / 260
260
OB–VGP–PASMRQ 23504 Number of Paging request for P B /// R6

SMT sent to a SGSN
OB–VGP–PASMRJ 23505 Number of Paging reject for SMT P B /// R6

received from a SGSN
OB–VGP–UNREASM 23506 Number of MS_Unreachable P B /// R6

received for SMT from a SGSN
OB–VGP–LOCUPREQ 23507 Number of Location Update P B /// R6

Request received from a SGSN
OB–VGP–LOCUPACP 23508 Number of Location Update P B /// R6

Accept sent to a SGSN
OB–VGP–TMSIREAL 23509 Number of TMSI Reallocation P B /// R6

Complete received from a SGSN
OB–VGP–ALRTREQ 23510 Number of Alert Request sent to a P B /// R6

SGSN
OB–VGP–ALRTACK 23511 Number of Alert Ack received from P B /// R6

a SGSN
OB–VGP–MSACTIV 23512 Number of MS Activity Indication P B /// R6

OB–VGP–GPDETIND 23513 Number of GPRS Detach Indica- P B /// R6

tion received from a SGSN
OB–VGP–GPDETACK 23514 Number of GPRS Detach Ack sent P B /// R6

to a SGSN
OB–VGP–IMDETIND 23515 Number of IMSI Detach Indication P B /// R6

OB–VGP–IMDETACK 23516 Number of IMSI Detach Ack sent P B /// R6

to a SGSN
OB–VGP–RESTINDR 23517 Number of RESET Indication P B /// R6

OB–VGP–RESTACKS 23518 Number of RESET Ack sent to a P B /// R6

SGSN
OB–VGP–RESTINDS 23519 Number of RESET Indication sent P B /// R6

to a SGSN
OB–VGP–RESTACKR 23520 Number of RESET Ack received P B /// R6

from a SGSN
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–VGP–MSINFREQ 23521 Number of MS Information P B /// R6

Request sent to a SGSN
ED 01
AAC020023800DS En 79 / 260
260
OB–VGP–MSINFRES 23522 Number of MS information P B /// R6

Response received from a SGSN
OB–VGP–MMINFREQ 23523 Number of MM Information P B /// R6

Request sent to a SGSN
OB–VGP–MOBMMR 23524 Number of Mobile Status contain- P B /// R6

ing a MM Information Request,
OB–VGP–MOBSTS 23525 Number of Mobile Status sent to a P B /// R6

SGSN
OB–VGP–MOBSTR 23526 Number of Mobile Status received P B /// R6

from a SGSN
OB–VCT–ACTRMOD 24901 Number of Activate trace mode P B /// R3

received
OB–VCT–ACTRMODR 24902 Number of Activate trace mode P B /// R3

result sent
OB–VCCP–REG 25201 Number of Register CC Entry P B SS codes

received per supplementary ser- for Call
vice Completion
operations
in VLR
OB–VCCP–REG–F 25202 Number of Register CC Entry fail- P B SS codes

ure per supplementary service for Call
Completion
operations
in VLR
OB–VCCP–ERA 25203 Number of Erase CC Entry P B SS codes

vice Completion
operations
in VLR
OB–VCCP–ERA–F 25204 Number of Erase CC Entry failure P B SS codes

per supplementary service for Call
Completion
operations
in VLR
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 80 / 260
260
OB–VCA–MMEVENTN 25701 Number of MM–Event–Notifica- P B E.164

tion messages sent by VLR to SCP PLMN
address
OB–VNR–UPLACREQ 27801 Number of LAC updating P B /// R3

requests through national
roaming
OB–VNR–UPLACRES 27802 Number of LAC updating P B /// R3

success through national
roaming
OB–VSM–MSABS 29801 Number of MS PRESENT phase 1 P B /// R2

message
OB–VSM–MSPRESREQ 29802 Number of Ready for SM P B /// R4.1

phase 2 request with alert
reason = MS present
OB–VSM–SMSPRES 29803 Number of successful Ready P B /// R4.1

for SM phase 2 with alert
reason = MS present
OB–VSM–MAREQ 29804 Number of Ready for SM P B /// R4.1

reason = memory available
OB–VSM–SMA 29805 Number of successful Ready P B /// R4.1

(1) This counter is identical to VPG–PAGING + VPG–SEARCH but it is kept for compatibility reason.
(2) Success are counted but this counter is kept for compatibility reason.
(3) This counter is identical to VLR–CANLOC–HOM + VLR–CANLOC–OTH but it is kept for compatibility
reason.
(5) The list of Supplementary Service codes for the counter OB–VSH–SNOSS is given in 4.1.4 page 105
by the ”List of SupplementaryService codes for operation counters”.
(6) The list of Supplementary Service codes for the counter OB–VSH–ENOSS is given in 4.1.4 page 105
1AA 00014 0004 (9007) A4 – ALICE 04.10
(7) If option F–OBS–003 is active, these counters are not sent to the OMC (they are not got by the func-
tional module OBS from Application functional modules and, so, are not sent by OBS to the functional mod-
ule ACQUISITION, see chapter 1).
ED 01
AAC020023800DS En 81 / 260
260
7(8) These counters are got by the functional module OBS from the Application and sent to the OMC only
if option F–OBS–004 is active. Nevertheless, these counters are increased by the Application whatever
the value of F–OBS–004 is.
(9) Applicable only if option F–OBS–005 is active

(10) The counters sent to the OMC are those which are different from zero
In order to allow the OMC to reset the OB–VLR–SNIAP counters, they have to be sent after the OB–VLR–
SNIA counter. Therefore, when the OMC receives the OB–VLR–SNIA counter, it must reset all the OB–
VLR–SNIAP counters.
(11) Applicable only if option F–OBS–008 is active
(12) not incremented when rejected for regulation cause.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 82 / 260
260
2.3 Detailed description in the RCP station

I 203
I 303
OBS. ACQ. OMC
RTOS
RCP
For applicability, see counters definition
Figure 5. Functional description of Observation in the RCP station
2.3.2 List of RCP station observations to be sent to the OMC

C = Coding mode
is not available
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 83 / 260
260
OB–ATH–SL–OTR 00001 Sum of numbers of bytes in the P B signalling R2

”service information octet” and link id.
”signalling information field” of sig-

nalling frames transmitted for the
first time on line during a measur-
ing period
per signalling link (before ININEF)
OB–ATH–SL–OREC 00002 Sum of numbers of bytes in the P B signalling R2

nalling frames received for the first
time on line during a measuring
period
OB–ATH–SL–MTR 00003 Number of signalling frames with P B signalling R2

”signalling information field” trans-
mitted for the first time on line dur-
ing a measuring period per signal-
ling link (before ININEF)
OB–ATH–SL–MREC 00004 Number of signalling frames with P B signalling R2

”signalling information field”
received for the first time on line
during a measuring period per sig-
nalling link (before ININEF)
OB–ATH–CP–OUT 00007 Number of messages sent by the P B MTP net- R4.1

(1) SCCP Gateway work
OB–ATH–CP–IN 00008 Number of messages received by P B MTP net- R4.1

(1) the SCCP Gateway work
OB–ATH–SL–OTR2 00011 Sum of numbers of bytes in the Pl B (NFSC, R3

”service information octet” and COC)
ing period
per signalling link
(after ININEF)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 84 / 260
260
OB–ATH–SL–OREC2 00012 Sum of numbers of bytes in the Pl B (NFSC, R3


period
per signalling link
(after ININEF)
OB–ATH–SL–MTR2 00013 Number of signalling frames with Pl B (NFSC, R3

ling link
(after ININEF)
OB–ATH–SL–MREC2 00014 Number of signalling frames with Pl B (NFSC, R3

nalling link (after ININEF)
OB–ATH–SY–CPUO 00101 CPU average occupancy L B processor R2

identifier
OB–ATH–SP–BUFA 00102 Logical Buffer availability L B processor R2

identifier
OB–ATH–SY–PMA 00103 Private memory availability L B processor R2

identifier
OB–ATH–SP–LMA 00104 Local memory availability L B processor R2

identifier
on (1) These Observation counters related to the SCCP Gateway function are sent to the OMC only if
F–OBS–001 is active.
”MTP network” is the SCCP network identification, with possible values :

• local
• national
• international
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 85 / 260
260
2.4 Detailed description in the HLR

CA CAMEL
CC preliminary Completion of Calls
to busy subscriber
CCB Call completion on busy subscr
CCP Call completion Servsces
CF Call Forwarding
CT Call Tracing
GP General Packet Radio Service
LCS Location services OBS. ACQ. OMC
I 202
LR Location Registration
OR Support of optimal routeing
SA Subscriber Administration
SC Security
SH Suppl. Services Handling
SS Subscriber Security
TC Terminating Call
TCAP (I 402)
TR Translation HLR
VH Version Handling
Figure 6. Functional description of Observation in the HLR

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 86 / 260
260
2.4.2 List of HLR observations to be sent to the OMC



C = Coding mode
is not available
OB–HSL–STTCAPE 10011 Number of TCAP P B /// R2

transactions input to HLR
OB–HSL–STTCAPS 10012 Number of TCAP P B /// R2

transactions output from HLR
OB–HSL–ETTCAPE 10013 Number of TCAP transactions P B /// R2

input to HLR terminated with
ABORT
OB–HSL–ETTCAPS 10014 Number of TCAP transactions out- P B /// R2

put from HLR terminated with
ABORT
OB–HLR–PURGEMS 10401 Number of PurgeMS P B /// R3

requests from VLR
OB–HLR–RESTORE 10402 Number of RestoreData P B /// R3

requests from VLR
OB–HLR–SENDIMSI 10403 Number of IMSI requests P B /// R3

from VLR
OB–HLR–VLRLOCREQ 10404 Number of Update location P B /// R3

requests from VLR
OB–HLR–VLRLOCRES 10405 Number of Update location P B /// R3

result to VLR
OB–HLR–ISDREQ 10406 Number of framed Insert P B nb of R3

Subscriber Data to VLR messages
OB–HLR–ISDRES 10407 Number of framed Insert P B nb of R3

Subscriber Data result from VLR messages
OB–HLR–CANLOCREQ 10408 Number of Cancel location P B /// R4.1

requests to VLR
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–HLR–CANLOCRES 10409 Number of Cancel location P B /// R4.1

result from VLR
ED 01
AAC020023800DS En 87 / 260
260
OB–HLR–DSDREQ 10410 Number of delete subscriber P B /// R4.1

data request sent
OB–HLR–DSDRES 10411 Number of delete subscriber P B /// R4.1

data success received
OB–HLR–SAISDREQ 10412 Number of stand–alone P B /// R4.1

Insert Subscriber data
request to VLR
OB–HLR–SAISDRES 10413 Number of stand–alone P B /// R4.1

success from VLR
OB–HLR–RESTORE- 10414 Number of RestoreData P B /// R4.1

RES success to VLR
OB–HLR–SODBROAM 10415 Number of Operations refusals P B /// R4.1

due to ODB of roaming
OB–HLR–PSIREQ 10416 Number of Provide Subscriber P B /// R4.2

Information Request message
sent
OB–HLR–PSIRES 10417 Number of Provide Subscriber P B /// R4.2

Information Result message
received
OB–HLR–ATIREQ 10418 Number of Any Time Interrogation P B /// R4.2

Request message received
OB–HLR–ATIRES 10419 Number of Any Time Interrogation P B /// R4.2

Result message sent
OB–HTC–SNIREA 10601 Number of interrogations P B /// R2

for call rerouting (this does not
concern the second Camel
interrogation)
OB–HTC–ENIREA 10602 Number of failed interrogations for P B /// R2

call rerouting
OB–HTC–REQ–MSRN 10603 Number of MSRN provision P B E.164 R3

requests PLMN
address
OB–HTC–RES–MSRN 10604 Number of MSRN provision P B E.164 R3

requests results PLMN
1AA 00014 0004 (9007) A4 – ALICE 04.10
address
ED 01
AAC020023800DS En 88 / 260
260
OB–HTC–EMSRN–ABS- 10605 Number of MSRN provision P B E.164 R3

SUB requests failures because PLMN
of absent subscriber address
OB–HTC–EMSRN– 10606 Number of MSRN provision P B E.164 R3

FNOTSU requests failures because PLMN
of Facility not supported address
OB–HTC–REJ 10607 Number of routing requests for TC P B /// R3

not handled due to overload
OB–HTC–EMSRN–BUS- 10608 Number of MSRN provision P B /// R3+

SUB requests failures because
(4) of MS busy condition
OB–HTC–SODBIC 10609 Number of Incoming calls refused P B /// R4.1

due to ODB of Incoming calls
OB–HTC–SNIREA2 10610 Number of second Camel P B /// R4.2

OB–HSC–SNDTR 11001 Number of authentication vectors P B /// R2

requests received
OB–HSC–ENDTR 11002 Number of authentication vectors P B /// R2

request failures
OB–HSC–RAUTREP 11003 Number of Authentication Failure P B /// G9.2

Report received (UMTS only)
OB–HTR–ANARES 11601 Number of translations analysis P B translation R4.1

results observed result
OB–HSH–SNOSS 13001 Number of supplementary P B Suppl. R2

service operations Service
code (1)
OB–HSH–ENOSS 13002 Number of supplementary P B Suppl. R2

service operation failures Service
code (2)
OB–HSH–AR 13003 Number of USSD request for P B /// R3+

1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–HSH–SAR 13004 Number of USSD success for P B /// R3+

ED 01
AAC020023800DS En 89 / 260
260
OB–HSH–REGPWREQ 13005 Number of register password P B /// R4.1

request received
OB–HSH–REGPWRES 13006 Number of register password P B /// R4.1

result sent
OB–HSH–SODBSH 13007 Number of operations refused due P B /// R4.1

to ODB of SS operations
OB–HSH–NIUR 13008 Number of invoked NI USSD P B /// R5

requests without
OB–HSH–SNIUR 13009 Number of successful NI USSD P B /// R5

requests without
OB–HSH–NIUN 13010 Number of invoked NI USSD notifi- P B /// R5

cations
OB–HSH–SNIUN 13011 Number of successful NI USSD P B /// R5

notifications
OB–HGP–SGSNLO- 13501 Number of Update GPRS location P B /// R5

CREQ requests from SGSN
OB–HGP– 13502 Number of Update GPRS location P B /// R5

SGSNLOCRES result to SGSN
OB–HGP–ISDREQ 13503 Number of attempted framed P B nb of R5

Insert Subscriber Data procedures messages
towards an SGSN
OB–HGP–ISDRES 13504 Number of successful framed P B nb of R5

Insert Subscriber Data procedures messages
towards an SGSN
OB–HGP–CANLOCREQ 13505 Number of Cancel location P B /// R5

requests to SGSN
OB–HGP–CANLOCRES 13506 Number of Cancel location P B /// R5

result from SGSN
OB–HGP–DSDREQ 13507 Number of delete subscriber P B /// R5

data req. sent to SGSN
OB–HGP–DSDRES 13508 Number of delete subscriber P B /// R5

data result received from SGSN
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–HGP–SAISDREQ 13509 Number of stand–alone P B /// R5

request to SGSN
ED 01
AAC020023800DS En 90 / 260
260
OB–HGP–SAISDRES 13510 Number of stand–alone P B /// R5

success from SGSN
OB–HGP–PURGEMS 13511 Number of PurgeMS P B /// R5

requests from SGSN
OB–HGP–PUR- 13512 Number of PurgeMS P B /// R5

GEMSRES result to SGSN
OB–HGP–RGREQ 13513 Number of SRI for SM request P B /// R5.2

from SMS–GMSC supporting MT
SMS over GPRS
OB–HGP–RGRES 13514 Number of SRI for SM result to P B /// R5.2

SMS–GMSC supporting MT SMS
over GPRS
OB–HGP–RGSGSN 13515 Number of SRI for SM result with P B /// R5.2

SGSN number sent to SMS–
GMSC not supporting MT SMS
over GPRS
OB–HGP–RSMDREQ 13516 Number of Report SM delivery sta- P B /// R5.2

tus request from SMS–GMSC
supporting MT SMS over GPRS
OB–HGP–RSMDRES 13517 Number of Report SM delivery sta- P B /// R5.2

tus result to SMS–GMSC support-
ing MT SMS over GPRS
OB–HGP–MSPRESREQ 13518 Number of Ready for SM request P B /// R5.2

from SGSN with alert reason = MS
present
OB–HGP–SMSPRES 13519 Number of successful Ready for P B /// R5.2

SM from SGSN with alert reason =
MS present
OB–HGP–MAREQ 13520 Number of Ready for SM request P B /// R5.2

from SGSN with alert reason =
memory available
OB–HGP–SMA 13521 Number of successful Ready for P B /// R5.2

SM from SGSN with alert reason =
memory available
OB–HGP–PDPRGREQ 13522 Number of SRI for GPRS request P B /// R5.2

received from GGSN
1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–HGP–PDPRGRES 13523 Number of SRI for GPRS Result P B /// R5.2

sent to GGSN
ED 01
AAC020023800DS En 91 / 260
260
OB–HGP–PDPFRREQ 13524 Number of Failure Report Request P B /// R5.2

received from GGSN
OB–HGP–PDPFRRES 13525 Number of Failure Report Result P B /// R5.2

sent to GGSN
OB–HGP– 13526 Number of Note MS Present for P B /// R5.2

PDPMSPRESREQ GPRS Request sent to GGSN
OB–HGP– 13527 Number of Note MS Present for P B /// R5.2

PDPMSPRESRES GPRS Result received from
GGSN
OB–HSS–SRETRI 14001 Counter of reused sets of P B /// R2

five triplets
OB–HSS–SRESYN 14002 Counter of resynchronisations P B /// G9.2
OB–HOR–SRIINV 14701 Number of ’send routeing info’ P B /// R5

invoke with OR interrogation
OB–HOR–SRIRES 14702 Number of ’send routeing info’ P B /// R5

result optimized (with MSRN)
OB–HCT–ACTRMOD 14901 Number of Activate Trace P B /// R3

mode sent
OB–HCT–ACTRMODR 14902 Number of Activate Trace P B /// R3

mode Result received
OB–HCCB–INVA 15001 Number of automatic invocations P B /// G9.3

of CCBS on the A side
OB–HCCB–INVB 15002 Number of automatic invocations P B /// G9.3

of CCBS on the B side
OB–HCCB–RQA 15003 Number of successful CCBS calls P B /// G9.3

on the A side
OB–HCCB–RQB 15004 Number of successful CCBS calls P B /// G9.3

on the B side
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 92 / 260
260
OB–HCCP–REG 15201 Number of Register CC Entry P B SS codes G9.3

vice Completion
operations
in HLR
OB–HCCP–REG–F 15202 Number of Register CC Entry fail- P B SS codes G9.3

ure per supplementary service for Call
Completion
operations
in HLR
OB–HCCP–ERA 15203 Number of Erase CC Entry P B SS codes G9.3

vice Completion
operations
in HLR
OB–HCCP–ERA–F 15204 Number of Erase CC Entry failure P B SS codes G9.3

per supplementary service for Call
Completion
operations
in HLR
OB–HVH–FALLBACK 15401 Number of MAP version fallbacks P B /// R3
OB–HVH–FALLBACKUN 15402 Number of unexpected P B /// R3

MAP version fallbacks
OB–HVH–SRGI–REJ 15403 Number of send routing P B /// R4.1

info. reject for optimal routing
OB–HVH–SRGISM–REJ 15404 Number of send routing info. for P B /// R4.1

SM reject for optimal routing
OB–HCA–USSR 15701 Number of P B /// R5

Unstructured–SS–Request
received from the SCF
OB–HCA–USSROK 15702 Number of successful P B /// R5

Unstructured–SS–Request
OB–HCA–USSN 15703 Number of P B /// R5

Unstructured–SS–Notify
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 93 / 260
260
OB–HCA–USSNOK 15704 Number of successful P B /// R5

Unstructured–SS–Notify
OB–HCA–ATSI 15705 Number of P B ///

ATSI Request
OB–HCA–ATSIACK 15706 Number of P B ///

ATSI Result returned by the HLR
to the SCF (successful response)
OB–HCA–ATM 15707 Number of P B ///

ATM Request
OB–HCA–ATMACK 15708 Number of P B ///

ATM Result returned by the HLR
to the SCF (successful response)
OB–HLCS–SRIREQ 16201 Number of Send Routing Info for P B /// G10

location services request
OB–HLCS–SRIRES 16202 Number of Send Routing Info for P B /// G10

location services result
OB–HSA–SN 18801 Number of subscribers L B /// R3

in the HLR database (globally)
OB–HSA–SNC 18802 Number of subscribers L B E.212 G9.2

in the HLR database with access PLMN
to the circuit domain at least address
OB–HSA–SNP 18803 Number of subscribers L B E.212 G9.2

in the HLR database with access PLMN
to the packet domain at least address
OB–HCF–SODBFTN 19601 Number of Operations P B /// R4.1

FTN registration, OC or TC
OB–HCC–PCCBSMES 19701 Number of CCBS related P B ///

1AA 00014 0004 (9007) A4 – ALICE 04.10
messages received or sent

by the HLR
ED 01
AAC020023800DS En 94 / 260
260
OB–HCC–PCCBSREQ 19702 Number of CCBS Request P B ///

messages received by the HLR
OB–HSM–RGREQ 19801 Number of Send routing P B /// R2

info for Short Message request
OB–HSM–SRG 19802 Number of Send routing P B /// R2

info for Short Message result
OB–HSM–MWDREQ 19803 Number of Message Waiting P B /// R2

(3) Data/Report SM delivery
status request
OB–HSM–SMWD 19804 Number of Message Waiting P B /// R2

(3) Data/Report SM delivery
status successful
OB–HSM–ALMSC 19805 Number of Alert SC phase 1 P B /// R2

message
OB–HSM–MSPRES 19806 Number of MS present phase P B /// R2

1 message
OB–HSM–REJ 19807 Number of Send Routing Info for P B /// R3

SM not handled due to overload
OB–HSM–ALREQ 19808 Number of Alert SC phase 2 P B /// R4.1

message request
OB–HSM–SAL 19809 Number of Alert SC phase 2 P B /// R4.1

message successful
OB–HSM–MSPRESREQ 19810 Number of Ready for SM P B /// R4.1

reason = MS present
OB–HSM–SMSPRES 19811 Number of successful Ready P B /// R4.1

reason = MS present
OB–HSM–MAREQ 19812 Number of Ready for SM P B /// R4.1

OB–HSM–SMA 19813 Number of successful Ready P B /// R4.1

1AA 00014 0004 (9007) A4 – ALICE 04.10
OB–HSM–ISC 19814 Number of Inform Service P B /// R4.1

center message
ED 01
AAC020023800DS En 95 / 260
260
OB–HSM–RGFNU- 19815 Number of SRI for SM requests P B /// R3+

MENQ used as MSC number enquiry
(5)
OB–HSM–SODBSMTC 19816 Number of SMSMT refused P B /// R4.1

due to ODB of Incoming calls
(1) The list of Supplementary Service codes for the counter OB–HSH–SNOSS is given in 4.1.4 page 105
(2) The list of Supplementary Service codes for the counter OB–HSH–ENOSS is given in 4.1.4 page 105
(4) Applicable only if F_TC_011 is set.
(5) Applicable only if F_SMS_005 is set.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 96 / 260
260
2.5 Detailed description in the HLR station

I 204
I 303
OBS. ACQ. OMC
RTOS
HLR
For applicability, see counters definition
Figure 7. Functional description of Observation in the HLR station
2.5.2 List of HLR station observations to be sent to the OMC

C = Coding mode
is not available
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 97 / 260
260
N.B. If F–OBS–002 is active, these Observation counters are not sent to the OMC.
Name Nb. Description T C Id. Rel.

OB–ATH–SL–OTR 00001 Sum of numbers of bytes in the P B signalling R2


ing period
OB–ATH–SL–OREC 00002 Sum of numbers of bytes in the P B signalling R2

period
OB–ATH–SL–MTR 00003 Number of signalling frames with P B signalling R2

ling link (before ININEF)
OB–ATH–SL–MREC 00004 Number of signalling frames with P B signalling R2

nalling link (before ININEF)
OB–ATH–SL–OTR2 00011 Sum of numbers of bytes in the Pl B (NFSC, R3

ing period
per signalling link
(after ININEF)
OB–ATH–SL–OREC2 00012 Sum of numbers of bytes in the Pl B (NFSC, R3

period
per signalling link
(after ININEF)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 98 / 260
260
Name Nb. Description T C Id. Rel.
OB–ATH–SL–MTR2 00013 Number of signalling frames with Pl B (NFSC, R3


ling link
(after ININEF)
OB–ATH–SL–MREC2 00014 Number of signalling frames with Pl B (NFSC, R3

nalling link (after ININEF)
OB–ATH–SY–CPUO 00101 CPU average occupancy L B processor R2

identifier
OB–ATH–SP–BUFA 00102 Logical Buffer availability L B processor R2

identifier
OB–ATH–SY–PMA 00103 Private memory availability L B processor R2

identifier
OB–ATH–SP–LMA 00104 Local memory availability L B processor R2

identifier
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 99 / 260
260
3 INTERFACE MATRIX
Function (1)
Related functions Implementation

R R V H H R A interfaces
Name FB C C L L L T C
P F R R H OQ
S
Station observations U U P I303

generation
Bulk data collect P U I203

P U I200
P U I201
P U I204
P U I202
(1) P: Provider – U : User
ACQ : acquisition function (in the bulk data collect function)
FUNCTION: Observation
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 100 / 260
260
4 INTERFACES
4.1 I20y interface

This is the interface between:

– OBS and acquisition in the RCF : I200
– OBS and acquisition in the VLR : I201
– OBS and acquisition in the HLR : I202
– OBS and acquisition in the RCP STATION : I203
– OBS and acquisition in the HLR STATION : I204
4.1.1 J Interface definition
For all observation tickets:
– The real–time transfer mechanism with end–to–end acknowledgement is used.
– The J interface with securization must be used

=>Communication service on J = ”ES1J”
– Communication service on Q3= ”ESTQ”
– Each packet must be acknowledged on J before the next can be sent
– Current dispatch is aborted when packets are lost.
– The maximum packet size to be sent on J is: MAXIMUM_LENGTH_OF_SSDU

ACCEPTER_ON_ANIX_SESSION_IN_THE_RTOS_TO_ANIX_DIRECTION – 13 bytes
– One session connection must be established for each type/Service as defined hereafter (and vice–
versa).
– The generation period is a system parameter, with a value defined per type of service.
• For RCF observations ( 2.1.2 page 33):
– fast report: type/service=”OBRC”
– slow report: type/service=”OBR2”
• For VLR observations ( 2.2.2 page 73):
– fast report: type/service=”OBVL”
– slow report: type/service=”OBV2”
• For AK obs in RCP ( 2.3.2 page 83): type/service=”OBAK”
• For HLR observations ( 2.4.2 page 87): type/service=”OBHL”
• For AK obs in HLR ( 2.5.2 page 97): type/service=”OBAK”
4.1.2 Filter mechanism and Transfer of observation data
Filter mechanism and Transfer of observation data are organised as described in the following figure:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 101 / 260
260
STEP1: STEP2: STEP3: STEP4:
APPLICATION OBSERVATION PACKETS ON

RAW DISPATCH DISPATCH TICKETS J INTERFACE
counter 1 counter 1 header

identical counter
counter of list
type P or list ticket
L split
header
counter n counter n counter

list
count. n+1 counter p
counter of filtered
type Pl or
Ll list
counter t
counter z
a) An application raw dispatch is sent for each generating period (p) and each type/service.
The counters of a single family are always sent to the OMC (different or not different from zero)
except when a note specifies that they are not sent.
The part of the raw dispatch concerning the counters per couple (of type Pl or Ll) has to be filtered
to minimize the number of counters sent to the OMC: the counters to be sent are those which are
different from zero.
To avoid any data link saturation, a general threshold is defined for the number of Pl counters sent
to the OMC, which is a system parameter (value = 5000) far beyond the estimate number of counters
of this type to be sent. If this threshold is reached, a switch–over is requested, for defense purpose.
b) The observation dispatch may be split in several tickets sent one after the other if its size is greater
than the maximum packet size on J.
c) The order in which families of a dispatch, or counters of a family, are sent is not guaranteed.
d) To avoid the transmission of too many counters per couple in a single dispatch, the following thresh-
olds are defined:
– The maximum number of counters per couple (BSC or RNC, adjacent LAC) transmitted to the OMC,
see 4.1.5.
– The maximum number of counters per couple (BSC or RNC, local BSC or RNC) transmitted to the
OMC, see 4.1.5.
– The maximum number of counters per couple (priority, BSC or RNC) transmitted to the OMC, see
4.1.5.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– The maximum number of counters per couple (RNC, MSC) transmitted to the OMC, see 4.1.5.
ED 01
AAC020023800DS En 102 / 260
260
– The maximum number of counters per couple (BSC or RNC, adjacent RNC) transmitted to the OMC,
see 4.1.5.
– OBS 1 OVERFLOW : the maximum number of counters per couple with the SLOW class transmitted
to the OMC and
– OBS 2 OVERFLOW : the maximum number of counters per couple with the FAST class transmitted
to the OMC.
If a threshold is reached, a deferred alarm is emitted, and the emission of the concerned counters per cou-
ple is no more guaranteed.
4.1.3 Ticket format (sent by the ASP)
TICKET HEADER:
Parameter Length Coding Value
Date and Time of scanning 6 byte binary (note 1)

divided
in
– year 1 byte binary integer 0 – 99
– month in the year ’ ’ ’ ’ integer 1 – 12
– day in the month ’ ’ ’ ’ integer 1 – 31
– hour in the day ’ ’ ’ ’ integer 0 – 23
– minute in the hour ’ ’ ’ ’ integer 0 – 59
– second in the minute ’ ’ ’ ’ integer 0 – 59
Dispatch number 1 byte binary integer 0 – 255
Number of tickets in the 1 byte binary integer 1 – 255

dispatch (note 2)
Ticket number in the 1 byte binary integer 1 – 255

dispatch
N.B. (1) The time is the same for all tickets pertaining to the same dispatch
N.B. (2) The choice is given:

– to set this parameter to an undefined value ’FF’, except for the last ticket of the dispatch (exam-
ple of ticket counting: 1/FF, 2/FF, 3/FF, 4/4)
– to give this value in each ticket (example of ticket counting: 1/4, 2/4, 3/4, 4/4)
Both must be accepted.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 103 / 260
260
TICKET BODY is composed of a succession of counters with format (note 2):
Counter family identifier 2 bytes binary integer 0–65535

(note 3)
Type of counter 1 byte binary 1: Peg (cumulative)

2: Load counter
3: Peg with long identifier
4: Load with long identifier
Rank in the fam. identifier 8 bytes ASCII (note 4)

or
rank in the fam. long id. 16 bytes ASCII
Counter value 4 bytes binary 0 – (H’FFFFFFFF’)
Validity number 1 byte binary integer 0–255

(note 5)
N.B. (2) All Counters of the same family are grouped together in a dispatch (not true for RTOS count-
ers).
N.B. (3) counter number given in 2nd column of counter description.
N.B. (4) contains the identifier in the family left aligned and padded with spaces (see 4.1.4 page 105).
For P and L types of counter, this identifier is on 8 bytes.
For Pl and Ll types of counter, this identifier is on 16 bytes.
8 spaces if not used.
N.B. (5) A global validity information, common to all application and RTOS observation counters, is
increased by one on each switchover. Load type counters have no validity information.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 104 / 260
260
4.1.4 Detail about rank in the family identifier
The rank in the family is the identifier within the family indicated in the column ’identifier if family concerned’
of counter description. This parameter can be short (8 bytes) or long (16 bytes), depending of the counter
type.
General rule for the identifier definition is to use the same identity forms than those input by operator and
displayed by Man Machine Commands:
Short identifier (8 bytes):
– Emergency service
• the identifiers of emergency service definition is left to the customer, controlled by translator’s
MMCs
– List of Supplementary Service codes for operation counters in HLR

(for applicability, see document [3] page 23.)
• ”CFUN” for call forwarding unconditional
• ”CFBU” for call forwarding on mobile subscriber busy
• ”CFNR” for call forwarding on no reply
• ”CFIN” for call forwarding on subscriber not reachable
• ”CBOC” for barring of all outgoing calls
• ”CBOI” for barring of outgoing international calls
• ”CBOIEXHC” for barring of outgoing international calls except those directed to the Home
PLMN Country
• ”CBIC” for barring of incoming calls
• ”CBIO” for barring of incoming calls when roaming outside the home PLMN country
• ”CWAI” for call waiting
• ”OSSS01” for Operator specific s.s. 01
• ”CCBSA” for call completion on busy subscriber
• ”MLPP” for enhanced Multi–Level Precedence & Pre–emption
– List of Supplementary Service codes for operation counters in VLR

• ”CFUN” for call forwarding unconditional
• ”CFBU” for call forwarding on mobile subscriber busy
• ”CFNR” for call forwarding on no reply
• ”CFIN” for call forwarding on subscriber not reachable
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
”CBOC” for barring of all outgoing calls

• ”CBOI” for barring of outgoing international calls
• ”CBOIEXHC” for barring of outgoing international calls except those directed to the Home
PLMN country
ED 01
AAC020023800DS En 105 / 260
260
• ”CBIC” for barring of incoming calls
• ”CBIO” for barring of incoming calls when roaming outside the home PLMN country
• ”CWAI” for call waiting
• ”CLIP” for calling line identity presentation
• ”CLIR” for calling line identity restriction

• ”COLP” for connected line identity presentation

• ”COLR” for connected line identity restriction
• ”MLPP” for enhanced Multi–Level Precedence & Pre–emption
– List of Supplementary Service codes for invocation counters

• ”ICBINV” for incoming call barring invocation
• ”OCBINV” for outgoing call barring invocation
• ”CHINV” for call hold invocation
• ”CRINV” for call retrieve invocation
• ”ALINV” for alternate procedure invocation
• ”CWINV” for call waiting invocation
• ”CFININV” for call forwarding on subscriber not reachable invocation
• ”CFBUINV” for call forwarding on MS busy invocation
• ”CFNRINV” for call forwarding on no reply invocation
• ”CLIRINV” for calling line identity restriction to the called MS with calling line identity presenta-
tion subscription
• ”AOCIINV” for Advice of charge Information (AoCI) invocation
• ”AOCCINV” for Advice of charge Charging (AoCC) invocation
• ”CUGOCINV” for Closed User Group Outgoing Call invocation
• ”CUGTCINV” for Closed User Group Terminating Call invocation
• ”MCIINV” for Malicious Call Identification invocation
• ”CLIRAINV” for Calling line identity restriction subscribed in temporary mode with default value
”Presentation Allowed”, ”Presentation Restricted” invocation by the calling MS
• ”CLIRRINV” for Calling line identity restriction subscribed in temporary mode with default value
”Presentation Restricted”, ”Presentation Allowed” invocation by the calling MS
• ”CLIPOINV” for Calling line identity presentation due to the override category of the called MS
• ”ECTINV” for explicit call transfer invocation
• ”COLPINV” for connected line identity presentation to the calling number.
• ”COLRINV” for connected line identity restriction to the calling number with connected line iden-
tity presentation subscription.
• ”BMPTYINV” for BuildMPTY procedure invocation
• ”HMPTYINV” for HoldMPTY procedure invocation
• ”RMPTYINV” for RetrieveMPTY procedure invocation
• ”SMPTYINV” for SplitMPTY procedure invocation
• ”CCBSAINV” for call completion on busy subscriber
• ”MLPPINV” for priority invocation
– List of Supplementary Service codes for acceptance counters

• ”CHACK” for call hold acceptance
• ”CRACK” for call retrieve acceptance
• ”ALACK” for alternate procedure acceptance
• ”CWACK” for call waiting acceptance
• ”AOCCACK” for ”Advice of charge Charging” acceptance
1AA 00014 0004 (9007) A4 – ALICE 04.10
• ”CUGOCACK” for Closed User Group Outgoing Call acceptance

• ”CUGTCACK” for Closed User Group Terminating Call acceptance
• ”ECTACK” for explicit call transfer acceptance
ED 01
AAC020023800DS En 106 / 260
260
• ”COLPACK” for connected line identity presentation acceptance without the use of override
category.
• ”COLPOACK” for connected line identity presentation acceptance thanks to the enabling of
override category.
• ”BMPTYACK” for BuildMPTY procedure acceptance

• ”HMPTYACK” for HoldMPTY procedure acceptance

• ”RMPTYACK” for RetrieveMPTY procedure acceptance
• ”SMPTYACK” for SplitMPTY procedure acceptance
• ”CCBSAACK” for call completion on busy subscriber
• ”MLPPACK” for acceptance of requested priority
– List of Supplementary Service codes for Call Completion operation counters in HLR
– List of Supplementary Service codes for Call Completion operation counters in VLR
– List of Basic Services identificators

• ”TEL” for telephony (TS11)
• ”EMER” for emergency (TS12)
• ”SMSMT” for short message terminating (TS21)
• ”SMSMO” for short message originating (TS22)
• ”GBS20” for asynchronous General Bearer Service
• ”BS21” for data c.a.d. 300b/s
• ”GBS30” for synchronous General Bearer Service
• ”BS31” for data c.s.d. 1200b/s
• ”BS41” for PAD access asynchronous 300b/s
• ”TS61” for alternate speech and facsimile group 3.
• ”TS62” for automatic facsimile group 3.
• ”BS61A” for alternate speech and data asynchronous (300/9600 b/s)
• ”BS61S” for alternate speech and data synchronous (1200/9600 b/s)
• ”BS81A” for speech followed by data asynchronous (300/9600 b/s)
• ”BS81S” for speech followed by data synchronous (300/9600 b/s)
• ”Unknown” for not yet known basic service.
– List of data speed:

• ”2400”: 2400b/s
• ”4800”: 4800b/s
• ”9600”: 9600b/s
1AA 00014 0004 (9007) A4 – ALICE 04.10
• ”14400”: 14400b/s
– List of ITC:
• ”UDI” when ITC value of GSM–BC is ’1’,
ED 01
AAC020023800DS En 107 / 260
260
• ”3.1kHz” when ITC value of GSM–BC is ’2’,
• ”FAX” when ITC value of GSM–BC is ’3’.
– List of ITC/FNUR:
• ”UDI64” when ITC=UDI and FNUR=64kbit/s,

• ”RDI56” when ITC=RDI and FNUR=56kbit/s,

ITC and FNUR are values of the PLMN–BC.
– List of ITC/GBR:
• ”UDIG14” when ITC=UDI and GBR=14.4kbit/s,
• ”AUDG14” when ITC=3.1 kHz audio and GBR=14.4kbit/s,
ITC is a value of the PLMN–BC, GBR is a QoS parameter of the assigned RAB.
– List of E.212 PLMN addresses
In VLR, PLMN number : MCC + MNC converted in ASCII, corresponding to PLMNs with a roaming
agreement and for which at least one subscriber is registered in the VLR
• it is used to count the number of subscribers per PLMN registered in VLR; all PLMNs are taken
into account, FPLMNs and HPLMN
As the MCC–MNC is obtained from the IMSI, the RCP has to know if the MNC is on 2 or 3 digits
in order to determine the right PLMN.
For roamers registered in the VLR, the structure of IMSI (MNC on 2 or 3 digits) is deduced from
the structure of their PLMN identification which has been declared in accepted PLMN adm-
nistration MMCs (comparison between MCC/MNC of declared PLMNs with the same length in
IMSI). If this method does not allow to determine the structure of IMSI, a PLMN data value giving
the default length of MNC is used.
• the number of PLMNs that can be defined is the number of PLMNs with a roaming agreement
+ 1 (for HPLMN)
In HLR, PLMN number : MCC + MNC converted in ASCII, corresponding to the MCC / MNC of the
subscriber in the HLR database (relevant in case where the HLR supports several home PLMN with
different MCC/MNC). The number of PLMNs that can be defined is 5.
– PLMN name
mnemonic (up to 8 alphanumeric characters) defined in the translation result of a routeing number
pointing out the subscription PLMN of a ported subscriber (option F–MNP–001).
– SMIM name
mnemonic used in MMC converted in ASCII
– BSC /RNC name

mnemonic used in MMC converted in ASCII
– Location area code

Value used in MMC converted in ASCII
– Target LAC Identifier:

Value used in MMC (CREAML) converted in ASCII
– Origin MSC Identifier:

A mnemonic describing adjacent MSC must be used (global address is too long). It should be entered
in CREAML command. Dummy value could be ”ADJ–MSCS”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Signalling link
RTOS object identifier in ASCII
– Adjacent point code
ED 01
AAC020023800DS En 108 / 260
260
– Processor
– Release domain:
Recall:
A release counter family is associated to each type of following processed procedures:
– in GMSC : Gateway call (GW)
– in SMS–GMSC : short message terminating gateway (SMT)
– in VMSC: Originating call (OC), terminating call (TC), forwarded terminating call at VMSC
(FTC), location registration (LR), supplementary service handling (SH), short message
originating (SMO), short message terminating (SMT).
Several release counter families are associated to handover (HO) procedures, which may bring into
play several MSCs (target, serving, controlling) depending on the type of handover (intra MSC, inter
MSC, subsequent, subsequent return).
Scenarios are given in appendix D for each of these procedures.
At the end of a procedure, the incremented release counter is determined by the procedure type and
by the release domain associated to the detected release cause, whatever the internal functional
block which detected the release cause may be.
General principle of release causes classification into release domains are given below. The com-
plete mapping between failures and release domains is defined in document [4]. An indication of con-
cerned procedure types is also given.
• ”NORMAL” for normal successful cases

– Successful execution of the procedure (not call related procedures)
– Normal call release by calling or called party during the conversation phase (TC, OC, GW)
• ”MS” for release error causes due to the Mobile Station equipment (all procedures except for
GW and FTC)
• ”MSORRAD” for failure due to the MS or the radio part when the faulty part cannot be deter-
mined (no response from the mobile), or for radio failure release causes (all procedures except
for GW and FTC)
• ”USER” for release causes due to the user (or SIM card)
– absent subscriber (GW, TC, SMT)
– forwarding violation (GW)
– requested service not subscribed or not authorized (SH, OC, SMO, SMT, TC, GW)
– MS on black list (OC, TC, SMO, SMT)
– illegal MS (all procedures except for GTW, HO and FTC)
– call barred due to Call Barring SS (SMO, SMT, TC, GW)
– Normal call release by calling or called party outside the conversation phase (TC, OC),
• ”HOMSLOST” for timeout on waiting for MS in HO procedure in controlling MSC
• ”HORETURN” for MS returning on old channel in HO procedure (GSM only)
• ”HOENDLST” for end of HO list without selected candidate cell (GSM only)
1AA 00014 0004 (9007) A4 – ALICE 04.10
• ”MSNOTALW” for MS not allowed causes

– unauthorized PLMN, unauthorized LAC, unauthorized LSA (OC,SMO, SH, LR, SOLSA)
– call barred due to operator barring (OC, TC, SMO, SMT, SH)
ED 01
AAC020023800DS En 109 / 260
260
• ”NSUPPLY” for service not supplied by the NSS causes (OC, TC, SH, LR, SMO, SMT, GW)
• ”FALSENUM” for false number detected either in SSP or in RCP translation, or by the PSTN
(OC, TC, GW, SMT)
• ”CDNOANSW” for no answer from called party during ringing phase (OC, TC, GW)
• ”CDBUSY” for called party busy cause (OC, TC, GW)
• ”SMIM” for SMIM release causes (OC, TC)
• ”EIR” for EIR release causes (OC, TC, SMT, SMO)
• ”PSTN” for release causes due to the public network (HO, TC, OC, GW)
– all PSTN release causes, except for those translated into FALSENUM, NORMAL,
CDNOANSW or CDBUSY domain
• ”BSS” for release causes due to the BSS (all procedures except GW and FTC)
– radio environment description inconsistency between NSS and BSS
– radio resource congestion, no response, protocol error, service not supplied by the BSS
• ”RNS” for release causes due to the RNS (all procedures except GW and FTC)
– environment description inconsistency between Core Network and RNS
– resource congestion, no response, protocol error, service not supplied by the RNS
• ”SSP” for release causes due to the SSP (all procedures except for LR and SH)
– all received SSP release causes, except for those translated into FALSENUM domain
– protocol error detected for dialogue with the SSP
• ”HLR” for release causes due to the HLR (all procedures except for LR and SH)
– unknown subscriber
– protocol error detected for dialogue with the HLR
– operation not supported by the HLR
• ”SC” for release causes due to the Service Center (SMT, SMO)
• ”G_V_MSC” for release causes due to SMS–GMSC or VMSC (SMT)
• ”ADJ–MSC” for release causes due to adjacent MSC (HO)
• ”ADJ–VLR” for adjacent VLR release causes.

– not used
• ”MAP–ELMT” for any MAP entity release cause
• ”LOCAL” for RCP local defense release causes (all procedures)

– RCP translator internal failure
– internal interface RCF–VLR protocol failure
– some external error causes as Data missing, Unexpected data value
• ”MISCE” for miscellaneous release causes which cannot be affected to another release
domain (all procedures)
– it includes System failure error cause, due to several failures
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
”SCP” for Service Control Point release cause (OC,GW)
• ”CALLSUP” for conversation phase supervision timer release cause (OC, TC) and OC release
cause due to Call Gaping at RCP.
ED 01
AAC020023800DS En 110 / 260
260
• ”I_V_MSC” for release causes due to SMS_IWMSC or VMSC (SMO).
• ”AUXINS” for release causes due to auxiliary equipments insertion denied by the SSP.
• ”NPDB” for release causes due to Number Portability DataBases inconsistency.

• ”PREEMPT” for release causes due to preemption (applicable when eMLPP function can be
offered).
• ”GMLC” for Gateway Mobile Location Center release cause (MT_LR LCS procedure)
– Translation result
mnemonic used in MMC converted in ASCII (up to 8 alphanumeric characters)
– E.164 PLMN address

In RCF and VLR, 8 first characters of the mnemonic used in the MMC defining the MAP version han-
dling. For the HPLMN, the mnemonic ”HPLMN” is used.
In HLR, 8 first characters of the mnemonic used in the MMC defining the MAP version handling. For
the HPLMN (home PLMN which can be identified by several MCC/MNC if the functional option
F–SA–013 is active), the mnemonic ”HPLMN” is used.
– Service Key
Operator defined mnemonic in ASCII
– number of messages
• ”0”,”1”, ”2”, ”3”, ”4”, ”5”: number of messages used within the procedure
• ”MORE”: if more than 5 messages are requested within the procedure
– Film number
Film number (from error translation) converted in ASCII (up to 127 announcements in the range
1–2047)
– Tone number
Tone number (from error translation) converted in ASCII (1 to 127)
– Carrier identity
Carrier identity as provided by MMC in the RCP translation result.
For outgoing call attempts ( MS originating, rerouted or forwarded) the carrier identity is provided in
the RCP translation result with call origin ”carrier check”.
For incoming call (gateway or terminating) the carrier identity is provided either in the RCP translation
result with call origin ”network” or in a dedicated parameter TNS received from the network.
In both cases, the ”carrier identity” identifier is coded on eight ASCII characters :
• the three first indicating the type of carrier network identification : ITU for ITU standardized, NAT
for National
• the fourth indicating the netwotk identification plan : 0 to F
• the four following indicating the carrier identification code.
During the call set–up if a new ”carrier identity” identifier is found out a new rank in the family is
created. In this way, up to 31 ranks can be defined, when the rank 32 is reached all new carrier identity
identifier is assigned to the rank 32 which corresponds to other carriers. In this case the identifier
associated to the rank 32 is set to ”OTHER ”.
Only one list of up to 32 carriers is thus elaborated. This list is shared by all the observation counters
families per carrier.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Nb TCH: Number of TCH/F requested by the MS for an HSCSD call

Value = 1 to 4 converted in ASCII .
ED 01
AAC020023800DS En 111 / 260
260
– Priority (for eMLPP counters) :
(for eMLPP applicability, see document [3] page 23.)
”NO_PRIO” for no priority
”PRIO_4” for priority level 4


”PRIO_B” for priority level B
”PRIO_A” for priority level A
Long identifier (16 bytes):
– (BSCi/RNCi, local BSCj/RNCj) couple

the two mnemonics used in MMC converted in ASCII and concatenated
– (BSCi/RNCi, adjacent LACj) couple

mnemonic used in MMC converted in ASCII and value used in MMC converted in ASCII, concate-
nated.
– (NFSCi,COCj) couple
mnemonic used in MMC converted in ASCII (signalling link set name) and value used in MMC con-
verted in ASCII (signalling link number), concatenated.
– (data speed, data speed) couple

the previous data speed mnemonic concatened with the new data speed mnemonic.
– (Nb TCH, basic service) couple

the Nb TCH mnemonic concatened with the mnemonic basic service. Only the following mnemonics
of basic services are usable: GBS20, GBS30, GBS40, TS61, TS62, BS61A, BS61S, BS81A, BS81S.
– (Nb of requested TCH, Nb of allocated TCH) couple

the number of TCH requested (Nb TCH mnemonic) concatened with the number of TCH allocated
(Nb TCH mnemonic).
– E.164 SCP address

The digits of the SCP address encoded in ASCII without the first octet (nature of address and number-
ing plan).
– (Priority,BSC/RNC) couple
the priority mnemonic concatenated to the BSC/RNC mnemonic used in MMC converted in ASCII.
– (RNCi,MSCj) couple
the two mnemonics used in MMC (RNC name and MSC name) converted in ASCII and concate-
nated.
– (BSCi/RNCi, adjacent RNCj) couple

the two mnemonics used in MMC converted in ASCII and concatenated
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 112 / 260
260
4.1.5 Maximum number of counters sent per family
The maximum number of counters per family which can be transmitted together to the OMC is limited due
to dimensioning constraints.
Number of
FAMILY items
Value for
OMC
Emergency service 32
SMIM name 16
BSC/RNC name 50
ITC 3
ITC/FNUR 2
ITC/GBR 2
Location area code 1024
Target LAC identifier 72
Origin MSC identifier 32
Signalling link 124
Adjacent point code 62
Processor 14
Translation result 100
E.164 PLMN address 512
PLMN name 32
Service key 192
Film number 127
Tone number 127
Release domain 28
Basic service 25
(BSC/RNC, adjacent LAC) (1) 512
Supplementary service 25
(data speed, data speed) 16
Number of ISD messages 7
(NFSC, COC) 124
(BSC/RNC, local BSC/RNC) (1) 120
Priority 8
(Priority, BSC/RNC) (1) 150
E.212 PLMN address 512
(RNC, MSC) (1) 120
1AA 00014 0004 (9007) A4 – ALICE 04.10
(BSC/RNC, adjacent RNC) (1) 120
ED 01
AAC020023800DS En 113 / 260
260
Note:
(1) For counters per (RNC, MSC), per (BSC/RNC, LAC), per (Priority, BSC/RNC) or per (BSC/RNC,
BSC/RNC) the maximum number of items which can be transmitted together to the OMC is less than the
maximum number of members in the family, due to dimensioning constraints.In this case, then only the
first n counters of this type are sent to the OMC, even if more than n are available at the RCP.
4.2 I30y interface
(interface between OBS function and RTOS)

– OBS and RTOS in the RCP: I304
– OBS and RTOS in the HLR: I302
4.3 I40y interface
(interface between OBS function and TCAP)

– OBS and TCAP in the RCF: I400
– OBS and TCAP in the VLR: I401
– OBS and TCAP in the HLR: I402
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 114 / 260
260
APPENDIX A – RCF COUNTER IMPLEMENTATION
Counters are sorted by alphabetical order.

A.1 Warning
In the following definitions, ”reception of the message” means reception of a message syntaxically valid
transmitted to the application level but before any parameters content analysis which may further lead to
message rejection during the processing. As a consequence, incoming requests not transmitted in case
of overload detected by RTOS are not taken into account.
In the following definitions, ”transmission of the message” means transmission of a message by the
application to the base system: this includes the cases of local SCCP translation failure. This does not
include the re–emission of a message due to a fallback procedure.
A.2 –––––––––––––––––––– CA counters (357) –––––––––––––––––––––––––
A.2.1 OB–FCA–APPCHGREP (19) – Number of Apply Charging successful
counter incremented when the APPLY CHARGING Request has not failed.
A.2.2 OB–FCA–APPCHGREQ (18) – Number of Apply Charging
counter incremented when an APPLY CHARGING Request is received from the gsmSCP.
A.2.3 OB–FCA–CALLGAPREJ (35) Number of calls rejected by call gapping
counters (one counter per SCP ) incremented when a call is rejected as result of the call gapping
checks.
A.2.4 OB–FCA–CALLGAPREQ (34) Number of received call gap requests
counter incremented when a CALL GAP Request is received from an SCP and accepted.
A.2.5 OB–FCA–CALLINFOREP (21) – Number of Call Information successful
counter incremented when the CALL INFORMATION Request has not failed.
A.2.6 OB–FCA–CALLINFOREQ (20) – Number of Call Information Request
counter incremented when an CALL INFORMATION Request is received from the gsmSCP.
A.2.7 OB–FCA–CANCEL (33) Number of Cancel Call successful
counter incremented when a CANCEL CALL Request has not failed.

1AA 00014 0004 (9007) A4 – ALICE 04.10
A.2.8 OB–FCA–CANCELREQ (32) Number of Cancel Call Request
counter incremented when a CANCEL CALL Request is received from the gsmSCP.
ED 01
AAC020023800DS En 115 / 260
260
A.2.9 OB–FCA–DFC (25) – Number of Disconnect Forward Connection successful
counter incremented when the disconnection of a temporary connection has not failed.
A.2.10 OB–FCA–DFCREQ (24) – Number of Disconnect Forward Connection Request
counter incremented when a DISCONNECT FORWARD CONNECTION Request is received from

the gsmSCP.
A.2.11 OB–FCA–DISCONLEG (37) – Number of Disconnect Leg successful
counter incremented when the disconnection leg has not failed.
A.2.12 OB–FCA–DISCONLEGREQ (36) – Number of Disconnect Leg Request
counter incremented when a DISCONNECT LEG Request is received from the gsmSCP.
A.2.13 OB–FCA–ETC (23) – Number of Establish Temporary Connection successful
counter incremented when the establishment of a temporary connection has not failed.
A.2.14 OB–FCA–ETCREQ (22) – Number of Establish Temporary Connection request
counter incremented when an ESTABLISH TEMPORARY CONNECTION Request is received from

the gsmSCP.
A.2.15 OB–FCA–EVRPBCSMDP04 (09) – Number of Event Report BCSM at DP4
counter incremented when the gsmSSF notifies the gsmSCF of a Route–Select–Failure event.
counter incremented when the gsmSSF notifies the gsmSCF of a O–Called–Party–Busy event.
counter incremented when the gsmSSF notifies the gsmSCF of a O–NoAnswer event.
A.2.18 OB–FCA–EVRPBCSMDP07 (05) – Number of Event Report BCSM sent at DP07
Counters, per PLMN, incremented on emission (at Detection Point 07) of EVENT REPORT BCSM
message to the SCP.
message to the SCP.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 116 / 260
260
counter incremented when the gsmSSF notifies the gsmSCF of a O–Abandon event.
counter incremented when the gsmSSF notifies the gsmSCF of a T–Called–Party–Busy event.
counter incremented when the gsmSSF notifies the gsmSCF of a T–NoAnswer event.
message to the SCP.
message to the SCP.
counter incremented when the gsmSSF notifies the gsmSCF of a O–Abandon event.
A.2.26 OB–FCA–FCI (29) – Number of Furnish Charging Information successful
counter incremented when a FURNISH CHARGING INFORMATION Request has not failed.
A.2.27 OB–FCA–FCIREQ (28) – Number of Furnish Charging Information Request
counter incremented when a FURNISH CHARGING INFORMATION Request is received from the
gsmSCP.
A.2.28 OB–FCA–INDPIDP02 (01) – Number of InitialDP sent at DP02
Counters, per PLMN, incremented on emission (at Detection Point 02) of INITIALDP message to the
SCP.
A.2.29 OB–FCA–INDPIDP12 (03) – Number of InitialDP sent at DP12
Counters, per PLMN, incremented on emission (at Detection Point 12) of INITIALDP message to the
SCP.
A.2.30 OB–FCA–INDPRDP02 (02) – Number of response to InitialDP sent at DP02

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per PLMN, incremented on response (at Detection Point 02) to INITIALDP message. The
response may be CONNECT message, CONTINUE message or RELEASE CALL message.
ED 01
AAC020023800DS En 117 / 260
260
A.2.31 OB–FCA–INDPRDP12 (04) – Number of response to InitialDP sent at DP12
Counters, per PLMN, incremented on response (at Detection Point 12) to INITIALDP message. The
response may be CONNECT message, CONTINUE message or RELEASE CALL message.
A.2.32 OB–FCA–REQBCSM (38) – Number of Request Report BSCM Event
counter incremented when a REQUEST REPORT BCSM EVENT is received from the gsmSCP.
A.2.33 OB–FCA–RESETTIM (27) – Number of Reset Timer successful
counter incremented when a RESET TIMER Request has not failed.
A.2.34 OB–FCA–RESETTIMREQ (26) – Number of Reset Timer request
counter incremented when an RESET TIMER Request is received from the gsmSCP.
A.2.35 OB–FCA–SCI (31) – Number of Send Charging Information successful
counter incremented when a SEND CHARGING INFORMATION Request has not failed.
A.2.36 OB–FCA–SCIREQ (30) – Number of Send Charging Information Request
counter incremented when a SEND CHARGING INFORMATION Request is received from the
gsmSCP.
A.2.37 OB–FCA–SMINIDP1 – Number of initial–DP–SMS at DP1
Conter incremented when the gsmSSF notifies the gsmSCP of a collected–SMS–Info event.
A.2.38 OB–FCA–SMINRDP1 – Number of response to Initial–DP–SMS at DP1
Counter incremented when the gsmSSF receives one of the operation CONTINUE–SMS, CONNECT–
SMS or RELEASE–SMS in response to Initial–DP–SMS at DP1.
A.2.39 OB–FCA–SMRQRPSMSEVT– Number of Request Event Report SMS Event
Counter incremented when a RequestReportBCSMEvent is received from the gsmSCP.
A.2.40 OB–FCA–SMRQRPSMSDP2 – Number of Event Report SMS at DP2
Counter incremented when the gsmSSF notifies the gsmSCP of a SMS–Failure event.
A.2.41 OB–FCA–SMRQRPSMSDP3 – Number of Event Report SMS at DP3
Counter incremented when the gsmSSF notifies the gsmSCP of a SMS–Submitted event.
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.2.42 OB–FCA–SMRESETREQ – Number of Reset Timer SMS Request received from the SCP
Counter is incremented when a Reset Timer Request is received from the gsmSCP.
ED 01
AAC020023800DS En 118 / 260
260
A.2.43 OB–FCA–SMRESETSUC – Number of Reset Timer SMS successful
Counter is incremented when the Reset Timer request has not failed.
A.2.44 OB–FCA–SMFCIREC – Number of Furnish Charging Information SMS received
Counter is incremented when a Furnish Charging Information request is received from the gsmSCP.
A.2.45 OB–FCA–SMFCISUC – Number of Furnish Charging Information SMS successful
Counter is incremented when a Furnish Charging Information request has not failed.
A.3 ––––––––––––––––––– CCB counters (350) ––––––––––––––––––––––––––
A.3.1 OB–FCCB–CALL–A (02) – Number of successful CCBS calls on the A side
Counter incremented on sending of the CALL REPORT message to the VLR for the CCBS call reporting
on the A side, with call outcome = ’success’.
A.3.2 OB–FCCB–CALL–B (03) – Number of successful CCBS calls on the B side
Counter incremented on sending of the CALL REPORT message to the VLR for the CCBS call reporting
on the B side, with call outcome = ’success’.
A.3.3 OB–FCCB–REC–CALLB (04) – Number of CCBS calls received on the B side
Counter incremented on receipt of either COMPLETE CALL or PROCESS CALL WAITING message
from the VLR, containing the information ”CCBS call”.
A.3.4 OB–FCCB–RQ (01) – Number of CCBS requests received from the MS
Counter incremented on sending of the REGISTER CC ENTRY message to the VLR related to CCBS.
A.4 –––––––––––––––––––– CS counters (351) –––––––––––––––––––––––––
A.4.1 OB–FCS–ACFPC (02) – Number of forwarded call attempts per carrier
Counters, per carrier, incremented when sending the CREATE message to the SSP to perform a cond-
tional or unconditional call forwarding towards a given carrier.
A.4.2 OB–FCS–AOCPC (01) – Number of outgoing call attempts per carrier
Counters, per carrier, incremented when sending the CREATE message to the SSP to setup an originating
call towards a given carrier.
A.4.3 OB–FCS–ARRPC (03) – Number of rerouted call attempts per carrier

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per carrier, incremented when the GMSC sends the CREATE message to the SSP to route a
call towards a VMSC or a transit call via a given carrier.
ED 01
AAC020023800DS En 119 / 260
260
A.4.4 OB–FCS–IGWPC (04) – Number of incoming gateway calls per carrier
Counters, per carrier, incremented when the PROVIDE INSTRUCTION message received in the GMSC
indicates the call is coming (gateway or transit) from a given carrier.
A.4.5 OB–FCS–ITCPC (05) – Number of terminating calls per carrier
Counters, per carrier, incremented when the PROVIDE INSTRUCTION message received in the VMSC
indicates the call is coming from a given carrier.
A.5 –––––––––––––––––––– CT counters (349) –––––––––––––––––––––––––
A.5.1 OB–FCT–INVTR (01) – Number of Activate Trace mode sent
Counters, per BSC (resp. RNC), incremented on emission of the BSSMAP MSC_INVOKE_TRACE mes-
sage to the BSC (resp. RANAP CN INVOKE TRACE message to the RNC).
A.5.2 OB–FCT–INVTRHO (02) – Number of Activate Trace mode forwarded through Prepare
Handover
Counter incremented on emission of the BSSMAP MSC_INVOKE_TRACE message or the RANAP CN

INVOKE TRACE message encapsulated into the PREPARE_HANDOVER message.
A.6 –––––––––––––––––––– DA counters (348) –––––––––––––––––––––––––
A.6.1 OB–FDA–CMMCONF (10) – Number of channel mode modify success
Counter, per couple (previous data speed, new data speed), incremented on emission of the CMM_CONF
message.
A.6.2 OB–FDA–CMMREQ (9) – Number of channel mode modify procedures
Counter, per couple (previous data speed, new data speed), incremented on reception of the
CMM_REQUEST message from the SMIM.
A.6.3 OB–FDA–COMPOC (21) – Outgoing data calls with compression.
Counters, per asynchronous basic service in non transparent mode, incremented each time an IWF CON-
NECTION Request with data compression has been acknowledged by the IWF, for an Outgoing data
call.
A.6.4 OB–FDA–COMPTC (22) – Terminated data calls with compression.
Counters, per asynchronous basic service in non transparent mode, incremented each time an IWF CON-
NECTION Request with data compression has been acknowledged by the IWF, for an Incoming data
call.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 120 / 260
260
A.6.5 OB–FDA–EACK–OC (03) – IWF connection ack. unsuccessful for Outgoing data calls
Counters, per basic service, incremented each time an IWF CONNECTION Request is not successful,
due to NOK acknowledge returned by SMIM, for an Outgoing data call.
A.6.6 OB–FDA–EACK–TC (04) – IWF connection ack. unsuccessful for Incoming data calls
Counters, per basic service, incremented each time an IWF CONNECTION Request is not successful,
due to NOK acknowledge returned by SMIM, for an Incoming data call.
A.6.7 OB–FDA–ESIMP (05) – IMPULSE error signalled by SMIM on data calls
Counters, per SMIM, incremented each time an IW Error message is received from SMIM which indicates
an ”IMPULSE” error, for an Outgoing or Incoming data call.
A.6.8 OB–FDA–ESON (06) – Error signalled by SMIM on data calls
Counters, per SMIM, incremented each time an IW Error message is received from SMIM which indicates
an ”ON” error, for an Outgoing or Incoming data call.
A.6.9 OB–FDA–FORCERL (11) – Data call release forced by SMIM
Counters, per basic service, incremented on reception of the FORCED RELEASE message from the
SMIM.
A.6.10 OB–FDA–FRBUF (20) – Data call release forced by SMIM due to buffer overflow
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
related to buffer overflow.
A.6.11 OB–FDA–FRFAX (18) – Data call release forced by SMIM due to FAX protocol problems
related to FAX protocol problems.
A.6.12 OB–FDA–FRINT (19) – Data call release forced by SMIM due to internal failure
related to internal failure.
A.6.13 OB–FDA–FRRLP (15) – Data call release forced by SMIM due to RLP problems
related to RLP problems.
A.6.14 OB–FDA–FRSYNC (14)– Data call release forced by SMIM due to synchronisation prob-
lems
1AA 00014 0004 (9007) A4 – ALICE 04.10
related to synchronisation problems.
ED 01
AAC020023800DS En 121 / 260
260
A.6.15 OB–FDA–FRV42 (16) – Data call release forced by SMIM due to V.42 problems
related to V.42 problems.
A.6.16 OB–FDA–FRX25 (17) – Data call release forced by SMIM due to X.25 problems
related to X.25 problems.
A.6.17 OB–FDA–MODREQ (12) – Number of In–Call Modification procedure request
Counter incremented on reception of the MODIFY message received from the MS due to In–Call Modifica-
tion procedure (change from speech to data or fax or change from data or fax to speech for ”alternate” or
”followed by” services).
A.6.18 OB–FDA–MODRES (13) – Number of In–Call Modification procedure result
Counter incremented on transmission of the MODIFY COMPLETE message to the MS due to In–Call
Modification procedure.
A.6.19 OB–FDA–OCDATANS (33) – Number of answered originating fax/data calls.
When F–OBS–007 is active, the counter is incremented on request for connection of the IWF by the RCP
when the ITC field of the sent GSM–BC of CALL PROCEEDING indicates fax, 3.1kHz audio or UDI. When
F–OBS–007 is not active the counter remains equal ro zero.
A.6.20 OB–FDA–OCDATATT (31) – Number of originating fax/data call attempts.
When F–OBS–007 is active, the counter is incremented on reception of the SETUP message from the MS
when the ITC field of the carried GSM–BC indicates fax, 3.1kHz audio or UDI. When F–OBS–007 is not
active the counter remains equal ro zero.
A.6.21 OB–FDA–OFBACK (27) – Number of HSCSD (multislot and 14.4 singleslot) outgoing
request leading to use of fallback GSM–BC
Counters, per basic service, incremented on reception of the SETUP message received from the MS with
”multislot and 14.4 singleslot” parameters in GSM–BC (data or fax related GSM–BC in case of two
GSM–BC are received) if fallback GSM–BC is used fo the call.
A.6.22 OB–FDA–OHSCSD–REQ (25) – Number of HSCSD (multislot and 14.4 singleslot) outgo-
ing request
Counters, per basic service and number of traffic channels TCH/F, incremented on reception of the SETUP
message received from the MS with ”multislot and 14.4 singleslot” parameters in GSM–BC (data or fax
related GSM–BC in case of two GSM–BC are received) if a multislot or 14.4 singleslot call can be deter-
mined. The ”Maximum number of traffic channels” field of received GSM–BC gives the number of TCH
to be used as family identifier.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 122 / 260
260
A.6.23 OB–FDA–S14–4 (30) – Number of successful 14.4kbit/s singleslot call
Counters, per Nb of requested TCH, incremented on transmission or reception of CONNECT ACK mes-
sage if a singleslot TCH/F14.4 has been allocated by the BSC in Assignment complete after a singleslot
Assignment request. The number of TCH/F requested is the one received from the MS in SETUP or CALL
CONFIRMED.
These counters are not incremented for dual services (”alternate” or ”followed by”).
A.6.24 OB–FDA–SHSCSD (29) – Number of successful multislot call
Counters, per couple Nb of requested TCH, Nb of allocated TCH, incremented on transmission or recep-
tion of CONNECT ACK message for multislot call (multislot requested in Assignment request message).
The number of TCH/F requested is the one received from the MS in SETUP or CALL CONFIRMED, the
number of TCH/F allocated is the one returned by the BSC in Assignment complete.
These counters are not incremented for dual services (”alternate” or ”followed by”).
A.6.25 OB–FDA–SIWF–OC (01) – IWF connection successful for Outgoing data calls
Counters, per basic service, incremented each time an IWF CONNECTION Request is successful, for
an Outgoing data call.
A.6.26 OB–FDA–SIWF–TC (02) – IWF connection successful for Incoming data calls
Counters, per basic service, incremented each time an IWF CONNECTION Request is successful, for
an Incoming data call.
A.6.27 OB–FDA–SIWFOCREQ (07)– IWF connection request for Outgoing data calls
Counters, per basic service, incremented each time an IWF CONNECTION Request is requested, for an
Outgoing data call.
A.6.28 OB–FDA–SIWFTCREQ (08)– IWF connection request for Incoming data calls
Counters, per basic service, incremented each time an IWF CONNECTION Request is requested, for an
Incoming data call.
A.6.29 OB–FDA–TCDATANS (34) – Number of answered terminated fax/data calls.
When F–OBS–007 is active, the counter is incremented on request for connection of the IWF when the
ITC field of the GSM–BC received in CALL CONFIRMED indicates fax, 3.1kHz audio or UDI. When no
GSM–BC is received the ITC considered value is the one of the sent SETUP. When F–OBS–007 is not
active the counter remains equal ro zero.
A.6.30 OB–FDA–TCDATATT (32) – Number of terminated fax/data call attempts.
When F–OBS–007 is active, the counter is incremented on emission of the SETUP message by the RCP
when the ITC field of the sent GSM–BC indicates fax, 3.1kHz audio or UDI. When F–OBS–007 is not active
the counter remains equal ro zero.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 123 / 260
260
A.6.31 OB–FDA–TFBACK (28) – Number of HSCSD (multislot and 14.4 singleslot) terminating
request leading to use of fallback GSM–BC
Counters, per basic service, incremented on reception of the CALL CONFIRMED message received from
the MS with fallback GSM–BC when ”multislot and 14.4 singleslot” parameters have been sent in GSM–
BC of SetUp (data or fax related GSM–BC if two GSM–BC are received).
A.6.32 OB–FDA–THSCSD–REQ(26) – Number of HSCSD (multislot and 14.4 singleslot) terminat-

ing request
Counters, per basic service and number of traffic channels TCH/F, incremented on reception of the CALL
CONFIRMED message received from the MS with awaited multislot and 14.4 singleslot parameters in
GSM–BC (data or fax related GSM–BC if two GSM–BC are received). The ”Maximum number of traffic
channels” field of received GSM–BC gives the number of TCH to be used as family identifier.
A.6.33 OB–FDA–UIMREQ (23) – Number of User Initiated Modification procedure request
Counter incremented on reception of the MODIFY message received from the MS when the message is
related to an ”User Initiated modification (resources up or downgrading)” procedure during a multislot
HSCSD call.
A.6.34 OB–FDA–UIMRES (24) – Number of User Initiated Modification procedure result
Counter incremented on transmission of the MODIFY COMPLETE message to the MS after a successful
”User initiated resource up/downgrading” procedure.
A.6.35 OB–FDA–UMMOC (25) – Number of UMTS Multimedia OC calls.
Counters per ITC and per FNUR, incremented on reception of CONNECT ACK from the UE when a Multi-
media call is established in UMTS.
A.6.36 OB–FDA–UMMTC (26) – Number of UMTS Multimedia TC calls.
Counters per ITC and per FNUR, incremented on emission of CONNECT ACK to the UE when a Multime-
dia call is established in UMTS.
A.6.37 OB–FDA–UBS20OC (27) – Number of UMTS BS20 OC calls.
Counters per ITC and per GBR, incremented on reception of CONNECT ACK from the UE when a BS20
call is established in UMTS.
A.6.38 OB–FDA–UBS20TC (28) – Number of UMTS BS20 TC calls.
Counters per ITC and per GBR, incremented on emission of CONNECT ACK to the UE when a BS20 call
is established in UMTS.
A.7 –––––––––––––––––––– DN counters (331) –––––––––––––––––––––––––

1AA 00014 0004 (9007) A4 – ALICE 04.10
A.7.1 OB–FDN–CONFUSION (01) – confusion messages emitted toward a BSC
Counters, per BSC, incremented on emission of the CONFUSION message toward a BSC.
ED 01
AAC020023800DS En 124 / 260
260
A.8 –––––––––––––––––––– GP counters (335) –––––––––––––––––––––––––
A.8.1 OB–FGP–ERP–CGS (02) – Paging failures (calls only) on Gs–interface

Counter incremented on transmission of the PAGE error component with ”Absent Subscriber” as an error
code, and of the SEARCH error component with the same error code, for terminating calls.
This counter is incremented only when the event which has triggered the sending of the error message
has occurred due to a page or search procedure on Gs–interface.
A.8.2 OB–FGP–ERP–UGS (03) – Paging failures for call unrelated services on Gs–interface
code, and of the SEARCH error component with the same error code, for call unrelated services.
The call unrelated services match Short Message Terminating, Network Initiated USSD services, Location
services LCS.
has occurred due to a page or search procedure on Gs–interface.
A.8.3 OB–FGP–SRP–GS (01) – Paging repetitions on Gs–interface
Counter incremented each time the PAGING message sent on Gs interface is repeated.
The first paging attempt is not counted.
This counter is incremented in all cases of repetition on Gs–Interface, even if the paging message has
been sent on A–Interface in parallel.
A.9 –––––––––––––––––––– HO counters (307) –––––––––––––––––––––––––
N.B. For MAP > V1 messages, reception of the message means reception of a correct encapsulated
BSSMAP message.
A.9.1 OB–FHO–S3GCOMA (74) – Number of handover command (2G –> 3G intra–MSC hand-
over)
Counters, per couple (source BSC, target RNC), incremented on transmission of the HANDOVER COM-
MAND message to the source BSC for 2G –> 3G intra–MSC handover.
A.9.2 OB–FHO–S3GCOME (78) – Number of handover command at controlling MSC (2G –> 3G
Counters, per couple (source BSC, target RNC), incremented at controlling MSC on transmission of the
HANDOVER COMMAND message to source BSC for 2G –> 3G inter–MSC handover.
A.9.3 OB–FHO–S3GCOMS (82) – Number of handover command at serving MSC (2G –> 3G sub-
Counters, per couple (source BSC, target RNC), incremented at serving MSC on transmission of the
HANDOVER COMMAND message to source BSC for 2G –> 3G subsequent inter–MSC handover.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 125 / 260
260
A.9.4 OB–FHO–S3GCOMPA (75) – Number of handover complete (2G –> 3G intra–MSC hand-
over)
Counters, per couple (source BSC, target RNC), incremented on reception of the RELOCATION COM-
PLETE message from the target RNC for 2G –> 3G intra–MSC handover.
A.9.5 OB–FHO–S3GCOMPE (79) – Number of handover complete at controlling MSC (2G –> 3G
Counters, per couple (source BSC, target RNC), incremented at controlling MSC on reception of the
SEND END SIGNAL (HANDOVER COMPLETE) message from target MSC for 2G –> 3G inter–MSC
handover.
A.9.6 OB–FHO–S3GCOMPCS (86) – Number of handover complete at controlling MSC (2G –>
3G subsequent inter–MSC handover)
Counters, per couple (source BSC, target RNC), incremented at controlling MSC on reception of the
SEND END SIGNAL (HANDOVER COMPLETE) message from target MSC for 2G –> 3G subsequent
inter–MSC handover.
A.9.7 OB–FHO–S3GCOMPS (83) – Number of handover complete at serving MSC (2G –> 3G
subsequent inter–MSC handover)
Counters, per couple (source BSC, target RNC), incremented at serving MSC on reception of the SEND
END SIGNAL RESULT message from controlling MSC for 2G –> 3G subsequent inter–MSC handover.
A.9.8 OB–FHO–S3GHORQA (73) – Number of handover required (2G –> 3G intra–MSC hand-
over)
Counters, per couple (source BSC, target RNC), incremented on reception of the HANDOVER
REQUIRED message related to a RNC for 2G –> 3G intra–MSC handover.
A.9.9 OB–FHO–S3GPREPE (77) – Number of handover preparation request at controlling MSC

(2G –> 3G inter–MSC handover)
PREPARE HANDOVER (HANDOVER REQUEST) message for 2G –> 3G inter–MSC handover.
A.9.10 OB–FHO–S3GPREPCS (85) – Number of handover preparation request at controlling

MSC (2G –> 3G subsequent inter–MSC handover)
PREPARE HANDOVER (HANDOVER REQUEST) message for 2G –> 3G subsequent inter–MSC hand-
over.
A.9.11 OB–FHO–S3GPREPSS (81) – Number of handover preparation request at serving MSC

(2G –> 3G subsequent inter–MSC handover)
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per couple (source BSC, target RNC), incremented at serving MSC on transmission of the PRE-
PARE SUBSEQUENT HANDOVER (HANDOVER REQUEST) message for 2G –> 3G subsequent inter–
MSC handover.
ED 01
AAC020023800DS En 126 / 260
260
A.9.12 OB–FHO–S3GRERA (76) – Number of handover process released (2G –> 3G intra–MSC
handover)
Counters, per release domain, incremented on each release of 2G –> 3G intra–MSC handover between
HANDOVER REQUIRED reception and RELOCATION COMPLETE reception, and also on normal
release at the normal end of the process.
A.9.13 OB–FHO–S3GRERE (80) – Number of handover process released at controlling MSC (2G
–> 3G inter–MSC handover)
Counters, per release domain, incremented on each release of 2G –> 3G inter–MSC handover at control-
ling MSC between HANDOVER REQUIRED reception and SEND END SIGNAL (HANDOVER COM-
PLETE) reception, and also on normal release at the normal end of the process.
A.9.14 OB–FHO–S3GRERCS (87) – Number of handover process released at controlling MSC

(2G –> 3G subsequent inter–MSC handover)
Counters, per release domain, incremented on each release of 2G –> 3G subsequent inter–MSC hand-
over at controlling MSC between PREPARE SUBSEQUENT HANDOVER (HANDOVER REQUEST)
reception and SEND END SIGNAL RESULT reception, and also on normal release at the normal end of
the process.
A.9.15 OB–FHO–S3GRERSS (84) – Number of handover process released at serving MSC (2G
–> 3G subsequent inter–MSC handover)
over at serving MSC between HANDOVER REQUIRED reception and SEND END SIGNAL RESULT
reception, and also on normal release at the normal end of the process.
A.9.16 OB–FHO–EHOFFM (07) – HO failures signalled by the mobile stations
Counters, per BSC at the origin of the message, incremented on reception of the HANDOVER FAILURE
message with cause ”Reversion to old channel”, where it is received before HANDOVER COMPLETE
timer expiry (Trr7), in case of intra–MSC handover.
A.9.17 OB–FHO–EHOFFM–2 (51) – HO failures signalled by the mobile stations
Counters, per couple (BSC at the origin of the message, target BSC), incremented on reception of the
HANDOVER FAILURE message with cause ”Reversion to old channel”, where it is received before
HANDOVER COMPLETE timer expiry (Trr7), in case of intra–MSC handover.
A.9.18 OB–FHO–EHOFFMA (28) – HO failures signalled by the mobile stations
timer expiry (T103), in case of inter–MSC handover.
A.9.19 OB–FHO–EHOFFMA–2 (54) – HO failures signalled by the mobile stations

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per couple (origin BSC, target LAC), incremented on reception of the HANDOVER FAILURE
timer expiry (T103), in case of inter–MSC handover.
ED 01
AAC020023800DS En 127 / 260
260
A.9.20 OB–FHO–EHOFFMAGLO (68) – HO failures signalled by the mobile stations (global)
Counter incremented on reception of the HANDOVER FAILURE message with cause ”Reversion to old
channel”, where it is received before HANDOVER COMPLETE timer expiry (T103), in case of inter–MSC
handover.
A.9.21 OB–FHO–EHOFFMB (29) – HO failures signalled by the mobile stations
timer expiry (T103), in case of subsequent handover.
A.9.22 OB–FHO–EHOFFMB–2 (55) – HO failures signalled by the mobile stations
Counters, per couple (origin BSC, target LAC), incremented on reception of the HANDOVER FAILURE
timer expiry (T103), in case of subsequent handover.
A.9.23 OB–FHO–EHOFFMBGLO (69) – HO failures signalled by the mobile stations (global)
Counter, incremented on reception of the HANDOVER FAILURE message with cause ”Reversion to old
channel”, where it is received before HANDOVER COMPLETE timer expiry (T103), in case of subsequent
handover.
A.9.24 OB–FHO–EHOIAMSC (04) – Intra–MSC HO failures signalled by the network
Counters, per BSC at the origin of the handover , incremented when the mobile station timeout (Trr7) which
was started on transmission of the HANDOVER COMMAND message for intra–MSC handover has
expired.
A.9.25 OB–FHO–EHOIAMSC–2 (49) – Intra–MSC HO failures signalled by the network
Counters, per couple (BSC at the origin of the handover, target BSC), incremented when the mobile station
timeout (Trr7) which was started on transmission of the HANDOVER COMMAND message for intra–MSC
handover has expired.
A.9.26 OB–FHO–EHOIRMSC (03) – Inter–MSC HO failures signalled by the network
Counters, per BSC at the origin of the handover required, incremented when the mobile station timeout
(T103) which was started on transmission of the HANDOVER COMMAND message for inter– MSC hand-
over has expired.
A.9.27 OB–FHO–EHOIRMSC–2 (48) – Inter–MSC HO failures signalled by the network
Counters, per couple (origin BSC, target LAC), incremented when the mobile station timeout (T103) which
was started on transmission of the HANDOVER COMMAND message for inter–MSC handover has
expired.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 128 / 260
260
A.9.28 OB–FHO–EHOIRMSCGLO (65) – Inter–MSC HO failures signalled by the network (global)
Counter incremented when the mobile station timeout (T103) which was started on transmission of the
HANDOVER COMMAND message for inter–MSC handover has expired.
A.9.29 OB–FHO–EHOSMSCB (25) – HO failures detected by network
Counters, per BSC at the origin of the message, incremented in serving MSC, on SEND END SIGNAL
Result timer expiry, in case of subsequent handover.
A.9.30 OB–FHO–EHOSMSCB–2 (53) – HO failures detected by network
Counters, per couple (origin BSC, target LAC), incremented in serving MSC, on SEND END SIGNAL
Result timer expiry, in case of subsequent handover.
A.9.31 OB–FHO–EHOSMSCBGLO (67) – HO failures detected by network (global)
Counter incremented in serving MSC, on SEND END SIGNAL Result timer expiry, in case of subsequent
handover.
A.9.32 OB–FHO–REJ (58) – Incoming HO rejected for regulation cause
Counter incremented on rejection of PERF_HO Invoke (MAP phase 1) or PREP_HO Invoke (MAP phase
2) for traffic regulation cause.
A.9.33 OB–FHO–SDTR1 (05) – HO required
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message.
A.9.34 OB–FHO–SDTR2 (09) – HO started
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message hav-
ing started handover processes.
A.9.35 OB–FHO–SDTR3 (10) – HO updated
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message hav-
ing lead to the updating of the handover processes.
A.9.36 OB–FHO–SDTR4 (11) – Repeated HO
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message start-
ing a Handover process with same list of cells as previous handover
A.9.37 OB–FHO–SDTR5 (12) – HO required on signalling channel
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message
requesting a Handover process while the MS is only on SDCCH (MS has not traffic channel yet)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 129 / 260
260
A.9.38 OB–FHO–SDTR6 (72) – HO required with cause ’switch circuit pool’
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message with
cause ’switch circuit pool’.
A.9.39 OB–FHO–SHOACMB (26) – HO reception in target MSC
Counters, per origin MSC, incremented on transmission of the GEN_SIG (ACM) message in case of inter–
MSC or subsequent handover.
A.9.40 OB–FHO–SHOACOMP (17) – Efficient intra–MSC HO
Counters, per target BSC, incremented on reception of the HO_COMPLETE message, in case of intra–
MSC handover
A.9.41 OB–FHO–SHOAREQ (16) – Attempted intra–MSC HO
Counters, per target BSC, incremented on transmission of the HO_REQUEST message, excluding
HO_REQUEST resending due to reselection (CIC problem between BSC and SSP), in case of intra–MSC
HO.
A.9.42 OB–FHO–SHOAREQACK (27) – Efficient intra–MSC HO resource assignment
Counters, per target BSC, incremented on reception of the HO_REQUEST_ACK message, in case of
intra–MSC HO.
A.9.43 OB–FHO–SHOBREQ (30) – Attempted inter–MSC HO resource assignment
Counters, per target BSC, incremented on transmission of the HO_REQUEST message in case of inter–
MSC (and subsequent) HO in target MSC, excluding HO_REQUEST resending due to reselection (CIC
problem between BSC and SSP).
A.9.44 OB–FHO–SHOBREQACK (31) – Efficient inter–MSC HO resource assignment
Counters, per target BSC, incremented on reception of the HO_REQUEST_ACK message, in case of
inter–MSC HO.
A.9.45 OB–FHO–SHOC (06) – HO commands (intra–MSC HO)
Counters, per origin BSC (i.e. destination of the message), incremented on transmission of the HAND-
OVER COMMAND message, for intra–MSC handover.
A.9.46 OB–FHO–SHOC–2 (50) – HO commands (intra–MSC HO)
Counters, per couple (origin BSC, target BSC), incremented on transmission of the HANDOVER COM-
MAND message, for intra–MSC handover.
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.9.47 OB–FHO–SHOCIR (32) – HO commands (inter–MSC HO)
Counters, per origin BSC , incremented on transmission of the HANDOVER COMMAND message for
inter–MSC handover
ED 01
AAC020023800DS En 130 / 260
260
A.9.48 OB–FHO–SHOCIR–2 (56) – HO commands (inter–MSC HO)
Counters, per couple (origin BSC, target LAC), incremented on transmission of the HANDOVER COM-
MAND message for inter–MSC handover
A.9.49 OB–FHO–SHOCIRGLO (70) – HO commands (inter–MSC HO) (global)
Counter, incremented on transmission of the HANDOVER COMMAND message for inter–MSC handover
A.9.50 OB–FHO–SHOCS (33) – HO commands (subsequent HO)
Counters, per origin BSC , incremented in serving MSC, on transmission of the HANDOVER COMMAND
message for subsequent handovers
A.9.51 OB–FHO–SHOCS–2 (57) – HO commands (subsequent HO)
Counters, per couple (origin BSC, target LAC), incremented in serving MSC, on transmission of the
HANDOVER COMMAND message for subsequent handovers
A.9.52 OB–FHO–SHOCSGLO (71) – HO commands (subsequent HO)
Counter, incremented in serving MSC, on transmission of the HANDOVER COMMAND message for sub-
sequent handovers
A.9.53 OB–FHO–SHOIAMSC (01) – Efficient intra–MSC handovers
Counters, per BSC at the origin of the handover required , incremented on reception of the HANDOVER
COMPLETE message for an intra–MSC handover.
A.9.54 OB–FHO–SHOIAMSC–2 (46) – Efficient intra–MSC handovers
Counters, per couple (BSC at the origin of the handover required, target BSC), incremented on reception
of the HANDOVER COMPLETE message for an intra–MSC handover.
A.9.55 OB–FHO–SHOIMSCA (02) – Efficient outgoing inter–MSC HO
Counters, per BSC at the origin of the handover required, incremented in serving MSC, on reception of
the SEND END SIGNAL Invoke, in case of inter–MSC HO.
A.9.56 OB–FHO–SHOIMSCA–2 (47) – Efficient outgoing inter–MSC HO
Counters, per couple (origin BSC, target LAC), incremented in serving MSC, on reception of the SEND
END SIGNAL Invoke, in case of inter–MSC HO.
A.9.57 OB–FHO–SHOIMSCAGLO (64) – Efficient outgoing inter–MSC HO (global)
Counter incremented in serving MSC, on reception of the SEND END SIGNAL Invoke, in case of inter–
MSC HO.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 131 / 260
260
A.9.58 OB–FHO–SHOIMSCB (08) – Efficient incoming inter–MSC and subsequent HO (target)
Counters, per target BSC, incremented in target MSC on transmission of the message SEND END SIG-
NAL Invoke, in case of inter–MSC or subsequent HO.
A.9.59 OB–FHO–SHOIPHORA (34) – Efficient outgoing inter–MSC HO
Counters, per target LAC, incremented in the controlling/serving MSC on reception of the PERF_HO
Result (MAP phase 1) or the PREP_HO Result (MAP phase 2) message, in case of inter–MSC HO.
A.9.60 OB–FHO–SHOIPHORAGLO (63) – Efficient outgoing inter–MSC HO (global)
Counter, incremented in the controlling/serving MSC on reception of the PERF_HO Result (MAP phase
1) or the PREP_HO Result (MAP phase 2) message, in case of inter–MSC HO.
A.9.61 OB–FHO–SHOIPIVA (13) – Attempted outgoing inter–MSC HO
Counters, per target LAC, incremented in the controlling/serving MSC on transmission of the PERF_HO
Invoke (MAP phase 1) or the PREP_HO Invoke (MAP phase 2) message, in case of inter–MSC HO
A.9.62 OB–FHO–SHOIPIVAGLO (59) – Attempted outgoing inter–MSC HO (global)
Counter incremented in the controlling/serving MSC on transmission of the PERF_HO Invoke (MAP
phase 1) or the PREP_HO Invoke (MAP phase 2) message, in case of inter–MSC HO
A.9.63 OB–FHO–SHOIPIVB (15) – Attempted incoming inter–MSC HO
Counters, per origin MSC (determined by the serving cell parameter), incremented in the target MSC on
reception of the PERF_HO Invoke (MAP phase 1) or the PREP_HO Invoke (MAP phase 2) message,
in case of inter–MSC or subsequent HO.
A.9.64 OB–FHO–SHOIRIABSC (35) – Inter–BSC HO interruption by intra BSC HO
Counters, per origin BSC, incremented on reception of the HO_PERFORM messages leading to handover
process interruption
A.9.65 OB–FHO–SHOISESA (14) – Efficient outgoing inter–MSC HO
Counters, per target LAC, incremented in the controlling/serving MSC, on reception of the SEND END
SIGNAL Invoke message, in case of inter–MSC HO.
A.9.66 OB–FHO–SHOISESAGLO (60) – Efficient outgoing inter–MSC HO (global)
Counter incremented in the controlling/serving MSC, on reception of the SEND END SIGNAL Invoke
message, in case of inter–MSC HO.
A.9.67 OB–FHO–SHOREL (36) – intra–MSC HO process release

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per release domain, incremented on each release of intra– MSC HO process and on release
due to the End of HO list without selected candidate cell for intra or inter MSC HO, between
HO_REQUIRED reception and HO_COMPLETE reception.
ED 01
AAC020023800DS En 132 / 260
260
A.9.68 OB–FHO–SHORELA (37) – inter–MSC HO process release in controlling
Counters, per release domain, incremented on each release of inter– MSC HO process, in controlling
MSC, between HO_REQUIRED reception and SEND END SIGNAL Invoke reception.
A.9.69 OB–FHO–SHORELB (38) – HO process release in Target MSC
Counters, per release domain, incremented on each release of HO process, in target MSC, between
PERF_HO Invoke (MAP phase 1) or PREP_HO Invoke (MAP phase 2) (incrementation of
OB_FHO_SHOIPIVB) and SEND END SIGNAL Invoke emission.
A.9.70 OB–FHO–SHORMSCA (19) – Efficient incoming return subsequent HO
Counters, per serving MSC, incremented in controlling MSC on transmission of the SEND END SIGNAL
Result message
A.9.71 OB–FHO–SHORPSIA (18) – Attempted incoming return subsequent HO
Counters, per serving MSC (determined by the serving cell parameter), incremented in controlling MSC
on reception of the PERF_SUBS_HO Invoke (MAP phase 1) or the PREP_SUBS_HO Invoke (MAP
phase 2) message, when this message requests a return in controlling MSC.
A.9.72 OB–FHO–SHORSEL (41) – HO resource reselections
Counters, per target BSC, incremented on each HO resource allocation failure (i.e. HO_FAILURE mes-
sage reception with cause allowing reselection).
A.9.73 OB–FHO–SHOSAREQ (42) – Attempted return subseq HO resource assignment
Counters, per target BSC, incremented in controlling MSC, on transmission of the HO_REQUEST mes-
sage in case of return subsequent HO, excluding HO_REQUEST resending due to reselection (CIC prob-
lem between BSC and SSP)
A.9.74 OB–FHO–SHOSAREQACK (43)– Efficient return subs HO resource assignment
Counters, per target BSC, incremented in controlling MSC, on reception of the HO_REQUEST_ACK mes-
sage, in case of return subsequent HO.
A.9.75 OB–FHO–SHOSMSCA (21) – Efficient incoming subsequent HO
Counter incremented on transmission from controlling MSC, of the SEND END SIGNAL Result message,
in case of subsequent HO.
A.9.76 OB–FHO–SHOSMSCB (24) – Efficient outgoing subsequent HO
Counters, per BSC at the origin of the handover required, incremented in serving MSC, on reception of
the SEND END SIGNAL Result message, for subsequent HO.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 133 / 260
260
A.9.77 OB–FHO–SHOSMSCB–2 (52) – Efficient outgoing subsequent HO
Counters, per couple (BSC at the origin of the handover required, target LAC), incremented in serving
MSC, on reception of the SEND END SIGNAL Result message, for subsequent HO.
A.9.78 OB–FHO–SHOSPHORA (44) – Efficient subsequent HO resource assignment
Counter incremented on reception of the PERF_HO Result (MAP phase 1) or the PREP_HO Result (MAP
phase 2) message, in controlling MSC, in case of subsequent HO.
A.9.79 OB–FHO–SHOSPSHORA (45) – Efficient return subs HO in controlling MSC
Counter incremented on transmission in controlling MSC, of the PERF_SUBS_HO Result (MAP phase
1) or the PREP_SUBS_HO Result (MAP phase 2) message, in case of subsequent or return subsequent
handover.
A.9.80 OB–FHO–SHOSPSIA (20) – Attempted incoming subsequent HO
Counter incremented on reception in controlling MSC, of the PERF_SUBS_HO Invoke (MAP phase 1)
or the PREP_SUBS_HO Invoke (MAP phase 2) message, excluding the cases when a return subsequent
HO is requested.
A.9.81 OB–FHO–SHOSPSIB (22) – Attempted outgoing subsequent HO
Counters, per target LAC, incremented in the serving MSC, on transmission of the PERF_SUBS_HO
Invoke (MAP phase 1) or the PREP_SUBS_HO Invoke (MAP phase 2) message, in case of subsequent
or return subsequent HO.
A.9.82 OB–FHO–SHOSPSIBGLO (61) – Attempted outgoing subsequent HO (global)
Counter incremented in the serving MSC, on transmission of the PERF_SUBS_HO Invoke (MAP phase
1) or the PREP_SUBS_HO Invoke (MAP phase 2) message, in case of subsequent or return subsequent
HO.
A.9.83 OB–FHO–SHOSRELA (39) – SUBS return HO process release
Counter incremented on each release of subs return HO process, in controlling MSC, in case of return
subsequent HO, between PERF_SUBS_HO Invoke (MAP phase 1) or PREP_SUBS_HO Invoke (MAP
phase 2) message (incrementation of OB_FHO_SHORPSIA) reception and SEND END SIGNAL Result
emission.
A.9.84 OB–FHO–SHOSRELB (40) – SUBS HO process release in Serving MSC
Counter incremented on each release of subsequent HO process, in serving MSC in case of subsequent
HO, between HO–REQUIRED reception and SEND END SIGNAL Result reception.
A.9.85 OB–FHO–SHOSSERB (23) – Efficient outgoing subsequent HO

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per target LAC, incremented in the serving MSC, on reception of the SEND END SIGNAL
Result message.
ED 01
AAC020023800DS En 134 / 260
260
A.9.86 OB–FHO–SHOSSERBGLO (62) – Efficient outgoing subsequent HO (global)
Counter incremented in the serving MSC, on reception of the SEND END SIGNAL Result message.
A.10 ––––––––––––––––––––– IN counters (399) ––––––––––––––––––––––––
N.B. The external messages with the SCP are counted. The service provided by the RCP may not
correspond to the external protocol with the SCP.
A.10.1 OB–FIN–CONNECT (04) – Number of Connect at the IN interface
Counters, per Service Key, incremented on reception of the CONNECT message.
A.10.2 OB–FIN–CONTINUE (05) – Number of Continue at the IN interface
Counters, per Service Key, incremented on reception of the CONTINUE message.
A.10.3 OB–FIN–INDPE (02) – Number of InitialDP errors at the IN interface
Counters, per Service Key, incremented on reception of the INITIALDP Error message.
A.10.4 OB–FIN–INDPI (01) – Number of InitialDP invoke at the IN interface
Counters, per Service Key, incremented on emission of the INITIALDP Invoke message.
A.10.5 OB–FIN–NETWORK (06) – Number of originating calls routed by a network server
Counters, per Service Key, incremented on routing towards a network server (Originating call, terminating
call or intelligent network invocation after a forwarding case).
A.10.6 OB–FIN–RELCALL (03) – Number of release call at the IN interface
Counters, per Service Key, incremented on reception of the RELEASECALL message.
A.11 –––––––––––––––––––– LCS counters (362) –––––––––––––––––––––––––
A.11.1 OB–FLCS–MTLRREQ (03) Global number of Mobile terminating location request MT_LR
received from GMLC for LCS services
Counter incremented on receipt of the MAP Provide Subscriber Location invoke from a GMLC.
A.11.2 OB–FLCS–CURMTLRREQ (04) Number of Call unrelated Mobile terminating location

request MT_LR received from GMLC for LCS services
Counter incremented on receipt of the MAP Provide Subscriber Location invoke from a GMLC for call unre-
lated Mobile Terminating Location request MT_LR LCS services.
This counter is incremented only if the message is received from an authorised GMLC and the request
1AA 00014 0004 (9007) A4 – ALICE 04.10
is not related to an ongoing call.
ED 01
AAC020023800DS En 135 / 260
260
A.11.3 OB–FLCS–CURMTLRRES (05) Number of Call unrelated Mobile terminating location
request MT_LR result sent to GMLC for LCS services
Counter incremented on sending of the MAP Provide Subscriber Location result to a GMLC for call unrela-
ted Mobile Terminating Location request MT_LR LCS services.

A.11.4 OB–FLCS–CRMTLRREQ (06) Number of Call related Mobile terminating location request
MT_LR received from GMLC for LCS services
Counter incremented on receipt of the MAP Provide Subscriber Location invoke from a GMLC for call rela-
ted Mobile Terminating Location request MT_LR LCS services.
This counter is incremented only if the message is received from an authorised GMLC and the request
is related to an ongoing call.
A.11.5 OB–FLCS–CRMTLRRES (07) Number of Call related Mobile terminating location request
MT_LR result sent to GMLC for LCS services
Counter incremented on sending of the MAP Provide Subscriber Location result to a GMLC for call related
Mobile Terminating Location request MT_LR LCS services.
A.11.6 OB–FLCS–LOCREQ (01) Number of location request messages sent for LCS services
Counters per BSC/RNC, incremented on sending of the Location Reporting Control (Iu interface) or Per-
form Location request (A interface) message to the RNC for LCS services.
A.11.7 OB–FLCS–LOCRES (02) Number of location response messages received for LCS ser-
vices
Counters per BSC/RNC, incremented on receipt of the Location Report (Iu interface) or Perform Location
response (A interface) message for LCS services.
A.11.8 OB–FLCS–LOCNOTS (10) Number of Location Notification sent to the MS for Mobile Ter-
minating location request MT_LR LCS services
Counter incremented on sending of the LCS_LocationNotification facility invoke message to a MS for

Mobile Terminating Location request MT_LR LCS services.
A.11.9 OB–FLCS–LOCNOTR (11) Number of Location Notification result received from the MS
for Mobile Terminating location request MT_LR LCS services
Counter incremented on receipt of the LCS_LocationNotification facility return result from a MS for Mobile
Terminating Location request MT_LR LCS services.
A.11.10 OB–FLCS–MOLRREL (19) Number of Mobile Originating location request MO_LR pro-
cedure release
Counters, per release domain, incremented on release (after success or failure) of the Mobile Originating
Location request MO_LR LCS procedure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 136 / 260
260
A.11.11 OB–FLCS–MOLRREQ (12) Number of Mobile Originating location request MO_LR
received from MS for LCS services
Counter incremented on receipt of the LCS_MOLR facility invoke from a MS for Mobile Originating Loca-
tion request MO_LR LCS services.

A.11.12 OB–FLCS–MOLRRES (13) Number of Mobile Originating location request MO_LR result
sent to MS for LCS services
Counter incremented on sending of the LCS_MOLR facility return result message to a MS for Mobile Origi-
nating Location request MT_LR LCS services.
A.11.13 OB–FLCS–LOCREPIMO (14) Number of Subscriber Location report invoke sent to the
GMLC for Mobile Originating location request MO_LR LCS services
Counter incremented on sending of the MAP Subscriber Location Report invoke to a GMLC for Mobile
Originating Location request MO_LR LCS services.
A.11.14 OB–FLCS–LOCREPRMO (15) Number of Subscriber Location report result received

from the GMLC for Mobile Originating location request MO_LR LCS services
Counter incremented on receipt of the MAP Subscriber Location Report result from a GMLC for Mobile
Originating Location request MO_LR LCS services.
A.11.15 OB–FLCS–LOCREPINI (16) Number of Subscriber Location report invoke sent to the
GMLC for Network Initiated location request NI_LR LCS services
Counter incremented on sending of the MAP Subscriber Location Report invoke to a GMLC for Network
Initiated Location request NI_LR LCS services.
A.11.16 OB–FLCS–LOCREPRNI (17) Number of Subscriber Location report result received from
the GMLC for Network Initiated location request NI_LR LCS services
Counter incremented on receipt of the MAP Subscriber Location Report result from a GMLC for Network
Initiated Location request NI_LR LCS services.
A.11.17 OB–FLCS–MTLRREL (18) Number of Mobile Terminating location request MT_LR pro-
cedure release
Counters, per release domain, incremented on release (after success or failure) of the Mobile terminating
Location request MT_LR LCS procedure.
A.12 –––––––––––––––––––– LD counters (327) –––––––––––––––––––––––––
A.12.1 OB–FLD–OVL (01) – OVERLOAD message from BSC/RNC
Counters, per BSC (resp. RNC) at the origin of the message, incremented at receipt of BSSMAP OVER-
1AA 00014 0004 (9007) A4 – ALICE 04.10
LOAD message with parameter cause set to ”CCCH overload” or ”processor overload” (resp. RANAP
OVERLOAD message).
ED 01
AAC020023800DS En 137 / 260
260
A.13 –––––––––––––––––––– LR counters (304) –––––––––––––––––––––––––
A.13.1 OB–FLR–ATT (02) – IMSI attach received

Counters, per BSC/RNC at the origin of the message, incremented on reception of LOCATION UPDAT-
ING Request with location updating type set to ”IMSI ATTACH”.
A.13.2 OB–FLR–DET (03) – IMSI detach indication
Counters, per BSC/RNC at the origin of the message, incremented on reception of IMSI DETACH INDICA-
TION
A.13.3 OB–FLR–LOC–CTRL (10)
Counters per RNC, incremented on sending of the Location Reporting Control message to the RNC, with
a request of direct response from the RNC (excluding messages for LCS services).
A.13.4 OB–FLR–LOC–REP (11)
Counters per RNC, incremented on receipt of the Location Report message if the message is a direct res-
ponse and if the requested information is received from the RNC (excluding messages for LCS services).
A.13.5 OB–FLR–LR–REJ (09) – Rejected non periodic LR for regulation cause
Counter incremented on rejection for traffic regulation cause of a LOCATION UPDATING Request with
location updating type not set to ”periodical” or to ”IMSI attach”
A.13.6 OB–FLR–LRP–REJ (08) – Rejected periodic LR for regulation cause
Counter incremented on rejection for traffic regulation cause of a LOCATION UPDATING Request with
location updating type set to ”periodical”
A.13.7 OB–FLR–REL (07) – Location registration process release
Counters, per release domain, incremented on release of a location registration, or ATTACH procedure
(per release domain).
A.13.8 OB–FLR–SLU (05) – Registration requests for normal LR
Counters, per BSC/RNC at the origin of the message, incremented on reception of the LOCATION
UPDATING Request message with location updating type not set to ”periodical” or ”IMSI attach”.
A.13.9 OB–FLR–SLUA (01) – Registration requests
(identical to FLR–SLU + FLR–SLUP + FLR–ATT)
1AA 00014 0004 (9007) A4 – ALICE 04.10
UPDATING Request message.
ED 01
AAC020023800DS En 138 / 260
260
A.13.10 OB–FLR–SLUP (06) – Registration requests for periodic LR
UPDATING Request message with location updating type set to ”periodical”.
A.13.11 OB–FLR–SLUR (04) – Accepted registration requests
Counters, per BSC/RNC at the origin of the LOCATION UPDATING Request, incremented on transmis-
sion of the LOCATION UPDATING Accept message.
A.14 –––––––––––––––––––– LSA counters (359) –––––––––––––––––––––––––
A.14.1 OB–FLSA–MMINF (01) – Number of MM information messages due to SoLSA feature

sent to the MS
Counter incremented at the sending of MM INFORMATION message to the MS if the sending is due to
SoLSA feature.
A.14.2 OB–FLSA–LSAINF (02) – Number of LSA information messages
Counters, per BSC, incremented at the sending of LSA INFORMATION message to the BSC.
A.15 –––––––––––––––––––– MLP counters (361) –––––––––––––––––––––––––
A.15.1 OB–FMLP–MOPROC (01) – Number of authorized MO calls
Counter, per priority level and per BSC/RNC, incremented upon sending of CALL PROCEEDING mes-
sage to the calling MS (note that calls without any priority are taken into account).
A.15.2 OB–FMLP–MOALERT (02) – Number of delivered MO calls
Counter, per priority level and per BSC/RNC, incremented upon sending of ALERTING message to the
calling MS (note that calls without any priority are taken into account).
A.15.3 OB–FMLP–MTSETUP (03) – Number of authorized MT calls
Counter, per priority level and per BSC/RNC, incremented upon sending of SETUP message to the called
MS (note that calls without any priority are taken into account).
A.15.4 OB–FMLP–MTALERT (04) – Number of delivered MT calls
Counter, per priority level and per BSC/RNC, incremented upon receipt of ALERT message (or CONNECT
when ALERT is not received) from the called MS (note that calls without any priority are taken into
account).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 139 / 260
260
A.16 –––––––––––––––––––– MO (Short Message Originating) counters (346)
A.16.1 OB–FMO–IFSMREQ (07) – Incoming forward SM request (SMS–IWMSC)

Counter incremented at the reception of the FORWARD SHORT MESSAGE Request from the VMSC.
A.16.2 OB–FMO–MSALREQ (02) – Reception of RP–SMMA
Counter incremented at the reception of the RP–SMMA message (message indicating that MS has again
memory capacity available) from the MS.
A.16.3 OB–FMO–MSTRREQ (01) – Reception of RP–DATA
Counter incremented at the reception of the RP–DATA message from the MS.
A.16.4 OB–FMO–OFSMREQ (05) – Outgoing forward SM request (VMSC)
Counter incremented on sending the FORWARD SHORT message to the SMS–IWMSC.
A.16.5 OB–FMO–REL (11) – SMO procedure release (VMSC)
Counters, per release domain, incremented on release of short message originating procedure.
A.16.6 OB–FMO–SALERT (04) – Acknowledgment of an RP–SMMA
Counter incremented at the sending of the RP–ACK message to the MS as a successful response to a
previous RP–SMMA.
A.16.7 OB–FMO–SCACK (10) – Successful transfer to the SC (SMS–IWMSC)
Counter incremented on the reception of the RP–ACK from the Service Centre.
A.16.8 OB–FMO–SCREQ (09) – Transfer of a SM to the SC (SMS–IWMSC)
Counter incremented on sending the RP–DATA to the Service Centre.
A.16.9 OB–FMO–SIFSM (06) – Incoming succesful forward (VMSC)
Counter incremented at the reception of the FORWARD SHORT MESSAGE Result from the SMS–
IWMSC.
A.16.10 OB–FMO–SOFSM (08) – Outgoing successful forward (SMS–IWMSC)
Counter incremented on sending the FORWARD SHORT MESSAGE Result to the VMSC.
A.16.11 OB–FMO–SSMTR (03) – Acknowledgment of an RP–DATA

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented at the sending of the RP–ACK message (incremented once only in case of repeti-
tion) to the MS as a successful response to a previous RP–DATA.
ED 01
AAC020023800DS En 140 / 260
260
A.17 –––––––––––––––––––– MP counters (323) ––––––––––––––––––––––––
A.17.1 OB–FMP–START (01) – Request to start a multi–party call

Counter incremented when sending INAP ADD Invoke operation toward the SSP to start a multi–party
call (conference Information = start of conference).
A.17.2 OB–FMP–SUCCESS (02) – Successful multiparty calls
Counter incremented when receiving INAP ADD Result operation from the SSP further to the request to
start a multi–party call.
A.18 –––––––––––––––––––– NP counters (358) ––––––––––––––––––––––––
A.18.1 OB–FNP–FQOD (07) – Call forwarding NPDB query on digits analysis (OQoD)
Counter incremented when sending CS1 INITIAL–DP operation toward the Number Portability Data Base
in the GMSC or in the VMSC further to a forwarded–to number analysis which may be a ported MSISDN
(OQoD).
A.18.2 OB–FNP–FROD (08) – Calls forwarded to a ported MS – OQoD –
Counter incremented when receiving CS1 CONNECT operation from the Number Portability Data Base
further to a NPDB query on digits analysis for a call forwarded in the GMSC or in the VMSC.
A.18.3 OB–FNP–NPDBF (09) – NPDB query failure
Counter incremented when one of the following events is received further to a Number Portability Data
Base query :
– CS1 INITIAL–DP error,
– ABORT of the TCAP transaction with the NPDB,
– CONTINUE TCAP message (instead of TC–END),
– no response from NPDB (TCAP timer expiry).
A.18.4 OB–FNP–OQOD (05) – Originating NPDB query on digits analysis (OQoD)
in the VMSC further to an originating call toward a possibly ported MSISDN (OQoD).
A.18.5 OB–FNP–OROD (06) – Originating calls to a ported MS – OQoD –
further to a NPDB query on digits analysis for an originating call in the VMSC.
A.18.6 OB–FNP–QOHR (01) – Terminating NPDB query on HLR release (QoHR)
1AA 00014 0004 (9007) A4 – ALICE 04.10
in the gateway MSC further to a HLR release (SRI error) with the cause ”unknown susbcriber”.
ED 01
AAC020023800DS En 141 / 260
260
A.18.7 OB–FNP–ROHR (02) – Terminating calls to a ported MS – QoHR –
further to a NPDB query on HLR release (SRI error) in the gateway MSC.
A.18.8 OB–FNP–RRPLMN (09) – Calls rerouted to a ported subscriber toward a given PLMN
Counter incremented when a call is rerouted toward a PLMN of the portability cluster.
If the Signalling Relay Function for call related message is offered, the counter is incremented when receiv-
ing a Send Routing Information result message including portability information.
If the IN solution for call related message is offered, the counter is incremented when a CS1 CONNECT
message is received from the Number Portability Data Base
In both cases the destination PLMN is retrieved from the translation result of the routeing number.
A.18.9 OB–FNP–TQOD (03) – Terminating NPDB query on digits analysis (TQoD)
in the gateway MSC further to a possibly ported MSISDN analysis (TQoD).
A.18.10 OB–FNP–TROD (04) – Terminating calls to a ported MS – TQoD –
further to a NPDB query on digits analysis for a terminating call in the gateway MSC.
A.19 –––––––––––––––––––– OC counters (305) ––––––––––––––––––––––––
A.19.1 OB–FOC–ALERT (09) – MS originating calls with alerting
Counters, per destination BSC/RNC, incremented on transmission of the ALERTING message towards
the calling MS
A.19.2 OB–FOC–C–REL (29) – OC releases during conversation phase
Counters, per release domain, incremented on release of an originating call during conversation phase
A.19.3 OB–FOC–CALPROC (08) – Authorized MS originating calls
Counters, per destination BSC/RNC, incremented on transmission of the CALL PROCEEDING message
towards a MS.
A.19.4 OB–FOC–CGAP (30) – Rejected OC for call rate control cause
Counter incremented on rejection of an OC call by the CallGap procedure at RCP.
A.19.5 OB–FOC–CONNACK (13) – Established MS originating calls
Counters, per BSC/RNC at the origin of the message, incremented on reception of the CONNECT ACK
1AA 00014 0004 (9007) A4 – ALICE 04.10
message from the calling MS
ED 01
AAC020023800DS En 142 / 260
260
A.19.6 OB–FOC–CONNECT (11) – MS originating calls with called response
Counters, per destination BSC/RNC, incremented on transmission of the CONNECT message towards
a MS.
A.19.7 OB–FOC–DIRCONNECT (12) – Established MS originating calls
Counters, per destination BSC/RNC, incremented on transmission of the CONNECT message towards
a MS, without transmission of ALERTING message.
A.19.8 OB–FOC–DTMFCAL (07) – Calls requesting DTMF transmission.
Counter incremented for each call requesting DTMF TRANSMISSION regardless the number of requests
during the call.
A.19.9 OB–FOC–DTMFREQ (06) – START DTMF received.
Counter incremented on reception of START DTMF
A.19.10 OB–FOC–DURC–BS (27) – Conversation phase duration for originating calls
Time counters in seconds, per basic service, incremented at the end of the call (on reception or transmis-
sion of DISCONNECT message, radio link break ...) with the time elapsed between the CONNECT mes-
sage transmission and the end of the call; at the same time, OB–FOC–NBRC–BS is also incremented by
one
A.19.11 OB–FOC–DURE–BS (23) – Establishment phase duration for originating calls
Time counters in seconds, per basic service, incremented on transmission of ALERTING or CONNECT
message with the time elapsed between the beginning of the authentication phase and the ALERTING
or CONNECT message transmission; at the same time, OB–FOC–NBRE–BS is also incremented by one
A.19.12 OB–FOC–DURS–BS (25) – Ringing phase duration for originating calls
Time counters in seconds, per basic service, incremented on transmission of CONNECT message with
the time elapsed between the ALERTING message transmission and the CONNECT message transmis-
sion; at the same time, OB–FOC–NBRS–BS is also incremented by one
A.19.13 OB–FOC–EAEMOB (04) – Failures on call attempts from the MS
(included in release counter FOC–REL)
Counter incremented when the call sent by the mobile station is released before the ALERTING or, in the
case of OACSU, if it is not possible to find a radio resource.
A.19.14 OB–FOC–EMIMEI (17) – Number of emergency call on IMEI
Counter incremented on receipt of the CM SERVICE REQUEST message with CM service type set to
1AA 00014 0004 (9007) A4 – ALICE 04.10
”emergency call establishment” and IMEI as mobile identity, and on receipt of IMEI from MS in case of
emergency call routing on IMEI after an authentication failure.
ED 01
AAC020023800DS En 143 / 260
260
A.19.15 OB–FOC–NBRC–BS (28) – Number of calls taken into account in OB–FOC–DURC–BS
counter
Counters, per basic service, incremented by one on each incrementation of OB–FOC–DURC–BS counter
A.19.16 OB–FOC–NBRE–BS (24) – Number of calls taken into account in OB–FOC–DURE–BS

counter
Counters, per basic service, incremented by one on each incrementation of OB–FOC–DURE–BS counter
A.19.17 OB–FOC–NBRS–BS (26) – Number of calls taken into account in OB–FOC–DURS–BS

counter
Counters, per basic service, incremented by one on each incrementation of OB–FOC–DURS–BS counter
A.19.18 OB–FOC–PROGRESS (10) – MS originating calls with progress
Counters, per destination BSC/RNC, incremented on transmission of the PROGRESS message towards
the calling MS
A.19.19 OB–FOC–REJ (16) – Rejected OC for regulation cause
Counter incremented on rejection of a CM SERVICE REQUEST with CM service type set to ”mobile origi-
nating call establishment”, ”emergency call establishment” or ”short message originating”, for traffic regu-
lation cause.
A.19.20 OB–FOC–REL (14) – OC releases
Counters, per release domain, incremented on release of an originating call
A.19.21 OB–FOC–REQ–BS (15) – Outgoing call request
Counters, per basic service, incremented each time a SETUP (or EMSETUP) message is received from
the MS (Basic Service derived from GSM_BC)
A.19.22 OB–FOC–SAEMOB (03) – Call attempts from the MS.
Counters per originating BSC incremented on reception of the CM SERVICE REQUEST message with
either ”mobile originating call establishment”, ”emergency call establishment” or ”short message origi-
nating” in the CM service type parameter.
A.19.23 OB–FOC–SETUP (05) – Call setup requests from the MS
Counters per originating BSC incremented on reception of the SETUP or EMERGENCY SETUP message
for an originating call
A.19.24 OB–FOC–SHOP–SETUP (21) – Single Hop telephony Call setup requests from the MS
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter, per BSC, incremented on reception of the SETUP message for an originating call, related to a
telephony call and for which single hop information has been received previously in ”complete layer 3
information” message
ED 01
AAC020023800DS En 144 / 260
260
A.19.25 OB–FOC–SODBOC (18) – Number of OC refused due to ODB of outgoing calls
Counter incremented on detection of refusal of an outgoing call due to ODB of outgoing calls
A.19.26 OB–FOC–SODBPR (19) – Number of OC refused due to ODB of premium rate calls
Counter incremented on detection of refusal of an outgoing call due to ODB of premium rate calls.
A.19.27 OB–FOC–SODBSH (20) – Number of CH invocations refused due to ODB of SS man-

agement
Counter incremented on detection of refusal of call hold invocation during an outgoing call due to ODB
of supplementary service management.
A.19.28 OB–FOC–SRSU (01) – Emergency service requests
Counters, per emergency identifier, specified as an emergency service, incremented on reception of a

SET UP message containing the corresponding prefix and on reception of a EMERGENCY SET UP mes-
sage for the counter corresponding to the implicitly associated prefix.
A.20 –––––––––––––––––––– OR counters (347) ––––––––––––––––––––––––
A.20.1 OB–FOR–BASICOR (02) – Optimal routeing for basic MS to MS calls
Counter incremented by the GMSC on receiving, from an HLR of another PLMN, a SEND ROUTING INFO
Result with a roaming number.
A.20.2 OB–FOR–EARLYCF (03) – Number of early calls forwarding
Counter incremented by the GMSC on receiving, from an HLR of another PLMN, a SEND ROUTING INFO
Result with a forwarded–to number and when the call can be forwarded without contravening the charging
requirements for optimal routeing.
A.20.3 OB–FOR–LATECF (05) – Number of late calls forwarding in the GMSC
Counter incremented by the GMSC on receiving, from a VMSC, an RCH Invoke with a forwarded–to num-
ber and when the call can be forwarded without contravening the charging requirements for optimal route-
ing.
A.20.4 OB–FOR–RCHINV–GMSC (04) – Number of RCH invoke received in the GMSC
Counter incremented by the GMSC on receiving, from a VMSC, an RCH Invoke with a forwarded–to num-
ber.
A.20.5 OB–FOR–RCHINV–VMSC (06) – Number of RCH invoke sent by the VMSC
Counter incremented by the VMSC on sending to a GMSC an RCH Invoke with a forwarded–to number
1AA 00014 0004 (9007) A4 – ALICE 04.10
in order to perform a late call forwarding.
ED 01
AAC020023800DS En 145 / 260
260
A.20.6 OB–FOR–RCHRES (07) – Number of RCH result received in the VMSC
Counter incremented by the VMSC on receiving from the GMSC a positive response to the RCH. The call
is routed to the FTN directly by the GMSC.
A.20.7 OB–FOR–SRI–FOR (08) – Number of ’send routing info’ invoke with interrogation type
’forwarding’
Counter incremented by the GMSC on sending a SEND ROUTING INFO Request with an interrogation
type equal to forwarding.
A.20.8 OB–FOR–SRIINV (01) – Number of SRI invoke with OR interrogation
Counter incremented by the GMSC on sending a SENDROUTINGINFO Result to an HLR of another

PLMN.
A.21 –––––––––––––––––––– PG counters (303) –––––––––––––––––––––––––
A.21.1 OB–FPG–BUSY–C (13) – Terminating calls towards busy MS (calls only)
Counter incremented on transmission of the PAGE error component with ”Busy Subscriber” , ”Busy Sub-
scriber more calls allowed” or ”SDCCH allocated” as an error code, and of the SEARCH error component
with the same error code, for terminating calls.
A.21.2 OB–FPG–BUSY–SM (15) – Terminating short messages towards busy MS
Counter incremented on transmission of the PAGE error component with ”Busy Subscriber” and of the
SEARCH error component with the same error code, for short messages terminating.
A.21.3 OB–FPG–BUSYMS (03) – Terminating calls towards busy MS.
Counter incremented on transmission of the PAGE error component with ”Busy Subscriber” , ”Busy Sub-
scriber more calls allowed” or ”SDCCH allocated” as an error code, and of the SEARCH error component
with the same error code, for both terminating calls and terminating short messages.
A.21.4 OB–FPG–ERP (02) – Paging failures on A–interface or Iu interface
code, and of the SEARCH error component with the same error code, for calls and terminating short mes-
sages.
has occurred due to a page or search procedure on A–interface (GSM) or Iu interface (UMTS).
A.21.5 OB–FPG–ERP–C (12) – Paging failures (calls only) on A–interface or Iu interface
code, and of the SEARCH error component with the same error code, for terminating calls.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 146 / 260
260
A.21.6 OB–FPG–ERP–SM (14) – Paging failures (short messages) on A–interface or Iu interface
code, and of the SEARCH error component with the same error code, for short messages terminating.
A.21.7 OB–FPG–FBDCELL (07) – Number of paging on the forbidden cells of the VMSC.
Counter incremented each time a paging response is received from a cell belonging to a zone where
incoming calls and short messages are forbidden.
A.21.8 OB–FPG–HPA (09) – Paging with Alerting Required.
Counter incremented each time a PAGING message is sent with the Information ”Element Alerting
Required”.
A.21.9 OB–FPG–NACK (11) – Paging Nack
Counter incremented on reception of a PAGING NACK message (if F–PA–009 active).
A.21.10 OB–FPG–OPINTA (06) – Operator calls with intervention allowed
Counter incremented for operator calls on transmission of the PAGE error component with ”Busy Sub-
scriber Intervention Allowed” as an error code, and of the SEARCH error component with the same
error code.
A.21.11 OB–FPG–OPNDUB (05) – Operator calls toward busy MS
Counter incremented for operator calls on transmission of the PAGE error component with ”Busy Sub-
scriber”, ”Busy Subscriber more calls allowed” or ”SDCCH allocated” or ”Busy subscriber Interven-
tion Allowed” as an error code, and of the SEARCH error component with the same error code.
A.21.12 OB–FPG–OTC (08) – Number of successful paging for Optimized Terminating Call
Counter incremented each time a PAGING Result is received for an Optimized Terminating Call.
A.21.13 OB–FPG–PAGEIMSI (04) – Page with IMSI
Counter incremented on reception of the PAGE Result component with TMSI, after a requesting PAGE
Request with IMSI
A.21.14 OB–FPG–SHPA (10) – Successful Paging with Alerting Required.
Counter incremented each time a PAGING Result is received after sending of PAGING message with the
Information ”Element Alerting Required”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.21.15 OB–FPG–SRP (01) – Paging repetitions on A–interface or Iu interface
Counter incremented each time the PAGING message is repeated in the first BSC/RNC when paging mes-
sage is sent on A–interface (GSM) or Iu interface (UMTS).
ED 01
AAC020023800DS En 147 / 260
260
The first paging attempt is not counted and if the procedure is applied on more than one BSC/RNC where
further attempts are made, incrementation does not take place for each BSC/RNC.
This counter is incremented in all cases of repetition on A–Interface or Iu interface, even if the paging mes-
sage has been sent on Gs interface in parallel or previously.
A.22 –––––––––––––––––––– ALR counters (360) –––––––––––––––––––––––––
A.22.1 OB–FALR–PAGING (01) – Paging sent on A–interface or Iu interface for ALR Automatic
location retrieval
Counter incremented on transmission of the PAGING message to the BSS on A–Interface (GSM) or to
the RNS on Iu interface (UMTS) in case of ALR Automatic location retrieval.
A.23 –––––––––––––––––––– RE counters (308) –––––––––––––––––––––––––
A.23.1 OB–FRE–S2GPREPE (37) – Number of relocation preparation request at controlling MSC

(3G –> 2G inter–MSC handover) (intra–PLMN)
Counters, per couple (source RNC, target LAC), incremented at controlling MSC on transmission of the
PREPARE HANDOVER (HANDOVER REQUEST) message to the target MSC for 3G –> 2G inter–MSC
handover.
This counter applies for intra–PLMN case only.
A.23.2 OB–FRE–S2GPREPEE (47) – Number of relocation preparation request at controlling

MSC (3G –> 2G inter–MSC handover) (inter–PLMN)
Counters, per couple (source RNC, target MSC), incremented at controlling MSC on transmission of the
PREPARE HANDOVER (HANDOVER REQUEST) message to the target MSC for 3G –> 2G inter–MSC
handover.
This counter applies for inter–PLMN case only.
A.23.3 OB–FRE–S2GPREPSS (42) – Number of relocation preparation request at serving MSC

(subsequent 3G –> 2G inter–MSC handover) (intra–PLMN)
Counters, per couple (source RNC, target LAC), incremented at serving MSC on transmission of the PRE-
PARE SUBSEQUENT HANDOVER (HANDOVER REQUEST) message to the controlling MSC for sub-
sequent 3G –> 2G inter–MSC handover.
A.23.4 OB–FRE–S2GPREPSSE (51) – Number of relocation preparation request at serving MSC

(subsequent 3G –> 2G inter–MSC handover) (inter–PLMN)
Counters, per couple (source RNC, target MSC), incremented at serving MSC on transmission of the
PREPARE SUBSEQUENT HANDOVER (HANDOVER REQUEST) message to the controlling MSC for
subsequent 3G –> 2G inter–MSC handover.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 148 / 260
260
A.23.5 OB–FRE–S2GRECANA (33) – Number of relocation cancelled (3G –> 2G intra–MSC
handover)
Counters, per couple (source RNC, target BSC), incremented on reception of the RELOCATION CAN-
CEL message from the source RNC for 3G –> 2G intra–MSC handover.
A.23.6 OB–FRE–S2GRECANE (38) – Number of relocation cancelled at controlling MSC (3G –>
2G inter–MSC handover) (intra–PLMN)
Counters, per couple (source RNC, target LAC), incremented on reception at controlling MSC of the
RELOCATION CANCEL message from the source RNC for 3G –> 2G inter–MSC handover.
A.23.7 OB–FRE–S2GRECANEE (48) – Number of relocation cancelled at controlling MSC (3G –>
2G inter–MSC handover) (inter–PLMN)
Counters, per couple (source RNC, target MSC), incremented on reception at controlling MSC of the
RELOCATION CANCEL message from the source RNC for 3G –> 2G inter–MSC handover.
A.23.8 OB–FRE–S2GRECANS (43) – Number of relocation cancelled at serving MSC (3G –> 2G
subsequent inter–MSC handover) (intra–PLMN)
Counters, per couple (source RNC, target LAC), incremented on reception at serving MSC of the
RELOCATION CANCEL message from the source RNC for subsequent 3G –> 2G inter–MSC handover.
A.23.9 OB–FRE–S2GRECANSE (52) – Number of relocation cancelled at serving MSC (3G –>
2G subsequent inter–MSC handover) (inter–PLMN)
Counters, per couple (source RNC, target MSC), incremented on reception at serving MSC of the
RELOCATION CANCEL message from the source RNC for subsequent 3G –> 2G inter–MSC handover.
A.23.10 OB–FRE–S2GRECOMA (34) – Number of relocation command (3G –> 2G intra–MSC

handover)
Counters, per couple (source RNC, target BSC), incremented on transmission of the RELOCATION
COMMAND message to the source RNC for 3G –> 2G intra–MSC handover.
A.23.11 OB–FRE–S2GRECOME (39) – Number of relocation command at controlling MSC (3G

–> 2G inter–MSC handover) (intra–PLMN )
Counters, per couple (source RNC, target LAC), incremented at controlling MSC on transmission of the
RELOCATION COMMAND message to the source RNC for 3G –> 2G inter–MSC handover.
A.23.12 OB–FRE–S2GRECOMEE (49) – Number of relocation command at controlling MSC (3G

1AA 00014 0004 (9007) A4 – ALICE 04.10
–> 2G inter–MSC handover) (inter–PLMN )
Counters, per couple (source RNC, target MSC), incremented at controlling MSC on transmission of the
RELOCATION COMMAND message to the source RNC for 3G –> 2G inter–MSC handover.
ED 01
AAC020023800DS En 149 / 260
260
A.23.13 OB–FRE–S2GRECOMS (44) – Number of relocation command at serving MSC (3G –>
2G subsequent inter–MSC handover) (intra–PLMN)

Counters, per couple (source RNC, target LAC), incremented at serving MSC on transmission of the
RELOCATION COMMAND message to the source RNC for subsequent 3G –> 2G inter–MSC handover.
A.23.14 OB–FRE–S2GRECOMSE (53) – Number of relocation command at serving MSC (3G –>
Counters, per couple (source RNC, target MSC), incremented at serving MSC on transmission of the
RELOCATION COMMAND message to the source RNC for subsequent 3G –> 2G inter–MSC handover.
A.23.15 OB–FRE–S2GRECOMPA (35) – Number of relocation complete (3G –> 2G intra–MSC

handover)
Counters, per couple (source RNC, target BSC), incremented on reception of the HANDOVER COM-
PLETE message from the target BSC for 3G –> 2G intra–MSC handover.
A.23.16 OB–FRE–S2GRECOMPE (40) – Number of relocation complete at controlling MSC (3G

–> 2G inter–MSC handover) (intra–PLMN )
Counters, per couple (source RNC, target LAC), incremented on reception at controlling MSC of the SEND
END SIGNAL (HANDOVER COMPLETE) message from the target MSC for 3G –> 2G inter–MSC hand-
over.
A.23.17 OB–FRE–S2GRECOMPEE (50) – Number of relocation complete at controlling MSC (3G

–> 2G inter–MSC handover) (inter–PLMN )
Counters, per couple (source RNC, target MSC), incremented on reception at controlling MSC of the
SEND END SIGNAL (HANDOVER COMPLETE) message from the target MSC for 3G –> 2G inter–MSC
handover.
A.23.18 OB–FRE–S2GRECOMPS (45) – Number of relocation complete at serving MSC (3G –>
2G subsequent inter–MSC handover) (intra–PLMN)
Counters, per couple (source RNC, target LAC), incremented on reception at serving MSC of the SEND
END SIGNAL RESULT message from the controlling MSC for 3G –> 2G subsequent inter–MSC hand-
over.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 150 / 260
260
A.23.19 OB–FRE–S2GRECOMPSE (54) – Number of relocation complete at serving MSC (3G –>
Counters, per couple (source RNC, target MSC), incremented on reception at serving MSC of the SEND
END SIGNAL RESULT message from the controlling MSC for 3G –> 2G subsequent inter–MSC hand-
over.
A.23.20 OB–FRE–S2GRERA (36) – Number of relocation process released (3G –> 2G intra–MSC
handover)
Counters, per release domain, incremented on each release of 3G –> 2G intra–MSC handover between
RELOCATION REQUIRED and HANDOVER COMPLETE, and also on normal release at the normal end
of the process.
A.23.21 OB–FRE–S2GRERE (41) – Number of relocation process released at controlling MSC

(3G –> 2G inter–MSC handover)
Counters, per release domain, incremented on each release of 3G –> 2G inter–MSC handover at control-
ling MSC between RELOCATION REQUIRED and SEND END SIGNAL (HANDOVER COMPLETE), and
also on normal release at the normal end of the process.
A.23.22 OB–FRE–S2GRERSS (46) – Number of relocation process released at serving MSC (3G
–> 2G subsequent inter–MSC handover)
over at serving MSC between RELOCATION REQUIRED and SEND END SIGNAL RESULT, and also
on normal release at the normal end of the process.
A.23.23 OB–FRE–S2GRERQA (32) – Number of relocation required (3G –> 2G intra–MSC hand-
over)
Counters, per couple (source RNC, target BSC), incremented on reception of the RELOCATION
REQUIRED message related to a target LAC for 3G –> 2G intra–MSC handover.
A.23.24 OB–FRE–SACMTE (18) – Number of successful relocation preparation at target MSC

(inter–MSC and subsequent inter–MSC relocation)
Counters, per controlling MSC, incremented at target MSC on transmission of the ACM message to the
controlling MSC.
A.23.25 OB–FRE–SPREPE (10) – Number of relocation preparation request at controlling MSC

(inter–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented at controlling MSC on transmission of the
PREPARE HANDOVER (RELOCATION REQUEST) message to the target MSC for inter–MSC reloca-
tion.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 151 / 260
260
A.23.26 OB–FRE–SPREPCS (21) – Number of relocation preparation request at controlling MSC
(subsequent inter–MSC relocation)
Counter incremented at controlling MSC on transmission of the PREPARE HANDOVER (RELOCATION

REQUEST) message to the target MSC for subsequent inter–MSC relocation.

A.23.27 OB–FRE–SPREPSS (24) – Number of relocation preparation request at serving MSC

Counters, per couple (source RNC, target RNC), incremented at serving MSC on transmission of the
PREPARE SUBSEQUENT HANDOVER (RELOCATION REQUEST) message to the controlling MSC for
subsequent inter–MSC relocation.
A.23.28 OB–FRE–SPREPTE (15) – Number of relocation preparation request at target MSC

(inter–MSC and subsequent inter–MSC relocation)
Counters, per controlling MSC, incremented at target MSC on reception of the PREPARE HANDOVER
(RELOCATION REQUEST) message from the controlling MSC.
A.23.29 OB–FRE–SRECANA (06) – Number of relocation cancelled (intra–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on reception of the RELOCATION CAN-
CEL message from the source RNC for intra–MSC relocation.
A.23.30 OB–FRE–SRECANE (11) – Number of relocation cancelled at controlling MSC (inter–

MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on reception at controlling MSC of the
RELOCATION CANCEL message from the source RNC for inter–MSC relocation.
A.23.31 OB–FRE–SRECANS (25) – Number of relocation cancelled at serving MSC (subsequent

Counters, per couple (source RNC, target RNC), incremented on reception at serving MSC of the
RELOCATION CANCEL message from the source RNC for subsequent inter–MSC relocation.
A.23.32 OB–FRE–SRECOM (02) – Number of relocation command (all type of relocation)
Counters, per source RNC, incremented on transmission of the RELOCATION COMMAND message to
the source RNC.
A.23.33 OB–FRE–SRECOMA (07) – Number of relocation command (intra–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on transmission of the RELOCATION
COMMAND message to the source RNC for intra–MSC relocation.
A.23.34 OB–FRE–SRECOME (12) – Number of relocation command at controlling MSC (inter–

MSC relocation)
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per couple (source RNC, target RNC), incremented at controlling MSC on transmission of the
RELOCATION COMMAND message to the source RNC for inter–MSC relocation.
ED 01
AAC020023800DS En 152 / 260
260
A.23.35 OB–FRE–SRECOMS (26) – Number of relocation command at serving MSC (subse-
Counters, per couple (source RNC, target RNC), incremented at serving MSC on transmission of the
RELOCATION COMMAND message to the source RNC for subsequent inter–MSC relocation.
A.23.36 OB–FRE–SRECOMPA (08) – Number of relocation complete (intra–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on reception of the RELOCATION COM-
PLETE message from the target RNC for intra–MSC relocation.
A.23.37 OB–FRE–SRECOMPE (13) – Number of relocation complete at controlling MSC (inter–

MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on reception at controlling MSC of the
SEND END SIGNAL (RELOCATION COMPLETE) message from the target MSC for inter–MSC reloca-
tion.
A.23.38 OB–FRE–SRECOMPCS (22) – Number of relocation complete at controlling MSC (sub-

Counter incremented on reception at controlling MSC of the SEND END SIGNAL (RELOCATION COM-
PLETE) message from the target MSC for subsequent inter–MSC relocation.
A.23.39 OB–FRE–SRECOMPS (27) – Number of relocation complete at serving MSC (subse-

Counters, per couple (source RNC, target RNC), incremented on reception at serving MSC of the SEND
END SIGNAL RESULT message from the controlling MSC for subsequent inter–MSC relocation.
A.23.40 OB–FRE–SRECOMPR (31) – Number of relocation complete at target MSC (subsequent

return inter–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on reception at target MSC of the RELOCA-
TION COMPLETE message from the target RNC for subsequent return inter–MSC relocation.
A.23.41 OB–FRE–SRECOMPTE (19) – Number of relocation complete at target MSC (inter–MSC

and subsequent inter–MSC relocation)
Counters, per controlling MSC, incremented on transmission at target MSC of the SEND END SIGNAL
(RELOCATION COMPLETE) message to the controlling MSC for inter–MSC and inter–MSC subsequent
relocation.
A.23.42 OB–FRE–SRERA (09) – Number of relocation process released (intra–MSC relocation)
Counters, per release domain, incremented on each release of intra–MSC relocation between RELOCA-
TION REQUIRED and RELOCATION COMPLETE, and also on normal release at the normal end of the
process.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 153 / 260
260
A.23.43 OB–FRE–SRERCE (14) – Number of relocation process released at controlling MSC
(inter–MSC relocation)
Counters, per release domain, incremented on each release of inter–MSC relocation at controlling MSC
between RELOCATION REQUIRED and SEND END SIGNAL (RELOCATION COMPLETE), and also
on normal release at the normal end of the process.
A.23.44 OB–FRE–SRERCS (23) – Number of relocation process released at controlling MSC

Counters, per release domain, incremented on each release of subsequent inter–MSC relocation at con-
trolling MSC between PREPARE SUBSEQUENT HANDOVER (RELOCATION REQUEST) and SEND
END SIGNAL RESULT, and also on normal release at the normal end of the process.
A.23.45 OB–FRE–SRERSS (28) – Number of relocation process released at serving MSC (sub-
Counters, per release domain, incremented on each release of subsequent inter–MSC relocation at serv-
ing MSC between RELOCATION REQUIRED and SEND END SIGNAL RESULT, and also on normal
release at the normal end of the process.
A.23.46 OB–FRE–SRERTE (20) – Number of relocation process released at target MSC (inter–
MSC and inter–MSC subsequent relocation)
Counters, per release domain, incremented on each release of inter–MSC relocation at target MSC
between PREPARE HANDOVER (RELOCATION REQUEST) and SEND END SIGNAL (RELOCATION
COMPLETE), and also on normal release at the normal end of the process.
A.23.47 OB–FRE–SRERQ (01) – Number of relocation required (all type of relocation)
Counters, per source RNC, incremented on reception of the RELOCATION REQUIRED message.
A.23.48 OB–FRE–SRERQA (05) – Number of relocation required (intra–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented on reception of the RELOCATION
REQUIRED message related to a target RNC for intra–MSC relocation.
A.23.49 OB–FRE–SREREQA (03) – Number of relocation resource allocation request (intra–

MSC relocation)
Counters, per target RNC, incremented on transmission of the RELOCATION REQUEST message to the
target RNC for intra–MSC relocation.
A.23.50 OB–FRE–SREREQE (16) – Number of relocation resource allocation request at target

MSC (inter–MSC and subsequent inter–MSC relocation)
Counters, per target RNC, incremented on transmission of the RELOCATION REQUEST message at tar-
get MSC to the target RNC for inter–MSC and subsequent inter–MSC relocation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 154 / 260
260
A.23.51 OB–FRE–SREREQR (29) – Number of relocation resource allocation request at target
MSC (subsequent return inter–MSC relocation)
Counters, per target RNC, incremented on transmission of the RELOCATION REQUEST message at tar-
get MSC to the target RNC for subsequent return inter–MSC relocation.
A.23.52 OB–FRE–SREREQKA (04) – Number of relocation resource allocation acknowledge

(intra–MSC relocation)
Counters, per target RNC, incremented on reception of the RELOCATION REQUEST ACK message from
the target RNC for intra–MSC relocation.
A.23.53 OB–FRE–SREREQKE (17) – Number of relocation resource allocation acknowledge at

target MSC (inter–MSC and subsequent inter–MSC relocation)
Counters, per target RNC, incremented on reception of the RELOCATION REQUEST ACK message at
target MSC from the target RNC for inter–MSC and subsequent inter–MSC relocation.
A.23.54 OB–FRE–SREREQKR (30) – Number of relocation resource allocation acknowledge at

target MSC (subsequent return inter–MSC relocation)
Counters, per target RNC, incremented on reception of the RELOCATION REQUEST ACK message at
target MSC from the target RNC for subsequent return inter–MSC relocation.
A.24 –––––––––––––––––––– RM counters (315) ––––––––––––––––––––––––
A.24.1 OB–FRM–EASR (02) – traffic channel assignment failures
(success are counted by FRM–SASR)
Counter incremented on reception of the messages:

– ASSIGNMENT FAILURE
– HANDOVER FAILURE, if the corresponding HANDOVER REQUEST message included a request
for a traffic channel
– CLEAR REQUEST, if it is received after transmission of an ASSIGNEMENT REQUEST (or HAND-
OVER REQUEST) message and before reception of an ASSIGNEMENT COMPLETE (or HAND-
OVER COMPLETE) message.
A.24.2 OB–FRM–EASR–2 (12) – traffic channel assignment failures for pool related causes
Counters per BSC incremented on reception of the messages:

– HANDOVER FAILURE
including one of the following causes :
– Switch circuit pool
– Circuit pool mismatch
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 155 / 260
260
A.24.3 OB–FRM–ESVUNVL (11) – Speech version requested unavailable
Counters, per BSC, incremented either when a failure occurred as the MSC tried MS and BSC speech
version support interworking (e.g. MS ”EFR only” and BSC ”FR only”) or on reception of ASSIGNMENT
FAILURE or HO FAILURE with cause ”Requested speech version unavalilable”.

A.24.4 OB–FRM–FAXDOWN (15) – Forced downgrading for fax calls
Counter incremented if F_RM_009 is active on reception of the Assignment complete message for a fax
Transparent call when a ”Chosen channel” IE indicating a value different from ’Full rate TCH’ has been
accepted although the MSC has requested ’Full rate TCH’ and 9.6 kbit/s data rate in the ”Assignment
Request” message. This specific value indicates a forced downgrading, i.e. that the maximum user rate
for the call is 4.8 kbit/s (due to lack of satellite resources).
A.24.5 OB–FRM–LSANA (17) – traffic channel assignment failures for SoLSA related causes
Counters per BSC incremented on reception of the messages:

including one of the following causes :
– LSA not allowed
A.24.6 OB–FRM–OCASCOM (06) – Successful radio resource assignments for OC
Counters, per BSC (resp. RNC), incremented on reception of the message ASSIGNMENT COMPLETE
from the BSC (resp. RAB ASSIGNMENT RESPONSE indicating a successful RAB establishement from
the RNC) for an originating call.
A.24.7 OB–FRM–OCASREQ (05) – Radio resource assignment requests for OC
Counters, per BSC (resp. RNC), incremented on transmission of the message ASSIGNMENT REQUEST
towards the BSC (resp. RAB ASSIGNMENT REQUEST for RAB establishment towards the RNC) for an
originating call.
A.24.8 OB–FRM–POOL (13) – traffic channel assignment success with pool indication mis-
match
Counters per originating BSC incremented on reception of the messages:

– ASSIGNMENT COMPLETE
– HANDOVER REQUEST ACKNOWLEDGE
including a circuit pool different from the one in which the SSP has selected the circuit.
A.24.9 OB–FRM–RETRYACK (10) – Number of directed retry handover success
Counters, per originating BSC, incremented on completion of the TCH assignment procedure previously
interrupted by the reception of the HANDOVER REQUIRED message.
A.24.10 OB–FRM–RETRYREQ (09) – Number of directed retry handover request

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message during
the TCH assignment procedure.
ED 01
AAC020023800DS En 156 / 260
260
A.24.11 OB–FRM–SASR (01) – Radio resource (traffic channel) assignments
(replaced by FRM–OCASCOM + FRM–TCASCOM + FHO–SHOAREQACK + FHO–SHOBREQACK +

FHO–SHOSAREQACK)
Counter,per BSC, incremented on reception of the message ASSIGN COMPLETE and on reception of
the message HANDOVER REQUEST ACKNOWLEDGE.
A.24.12 OB–FRM–SDLIB (04) – Release requests ”BSC”
( included in global release counter)
Counters, per BSC at the origin of the message, incremented on reception of the CLEAR REQUEST mes-
sage, with cause different from ’no radio resource available’.
A.24.13 OB–FRM–SHOIABSC (03) – Successful intra–BSC handovers
Counters, per BSC at the origin of the message, incremented on reception of the HANDOVER PER-
FORMED message.
A.24.14 OB–FRM–SHOP–REASS (16) – TCH re–assignment requests due to Single Hop denial
Counter, per BSC, incremented on receipt of CHA_SEI internal message from OC function containing the
”single hop TCH realloc” parameter. It corresponds to a traffic channel re–assignment request on the origi-
nating side due to single hop denial.
A.24.15 OB–FRM–SHOPERF (14) – Receipt of Handover performed with change in multislot

configuration
Counter incremented on receipt of HANDOVER PERFORMED message (due to handover intra BSC or
”BSS initiated resource up– and downgrading” procedure) if the new chosen channel indicates a change
in the configuration of an HSCSD call which entails the sending of the Update_No_TCH message toward
IWF.
A.24.16 OB–FRM–TCASCOM (08) – Successful radio resource assignments for TC
Counters, per BSC (resp. RNC), incremented on reception of the message ASSIGNMENT COMPLETE
from the BSC (resp. RAB ASSIGNMENT RESPONSE indicating a successful RAB establishement from
the RNC) for a terminating call.
A.24.17 OB–FRM–TCASREQ (07) – Radio resource assignment requests for TC
Counters, per BSC (resp. RNC), incremented on transmission of the message ASSIGNMENT REQUEST
towards the BSC (resp. RAB ASSIGNMENT REQUEST for RAB establishment towards the RNC) for a
terminating call.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 157 / 260
260
A.25 –––––––––––––––––––– SC counters (310) ––––––––––––––––––––––––
A.25.1 OB–FSC–IMEIBLACK (04) – EIR answers with black IMEI

Counter incremented on reception from the EIR of the CHECK IMEI Result component with the Equip-
mentStatus parameter equal to ”black–listed”.
A.25.2 OB–FSC–IMEIGREY (03) – EIR answers with grey IMEI
mentStatus parameter equal to ”grey–listed”.
A.25.3 OB–FSC–IMEIINT (01) – EIR interrogation
Counter incremented on transmission to the EIR of the CHECK IMEI Invoke component.
A.25.4 OB–FSC–IMEIUNKNOWN (05) – EIR answers with unknown IMEI
Counter incremented on reception from the EIR of the CHECK IMEI Error component with the UnknownE-
quipment error cause.
A.25.5 OB–FSC–IMEIWHITE (02) – EIR answers with white IMEI
mentStatus parameter equal to ”white–listed”.
A.26 –––––––––––––––––––– SH counters (330) ––––––––––––––––––––––
See XX/SH counters.
A.27 –––––––––––––––––––– SM counters (398) ––––––––––––––––––––––
A.27.1 OB–FSM–ALSC (09) – Alert service center (IWMSC)
Counter incremented on sending the RP ALERT message to the SC.
A.27.2 OB–FSM–GTWREL (18) – Short message gateway procedure release (GMSC)
Counters incremented on release of a Short message gateway procedure, per release domain
A.27.3 OB–FSM–IEFW (17) – Incoming unsuccessful forward (GMSC)
Counter incremented on receiving in the GMSC the FORWARD SHORT MESSAGE Error with cause
”Absent subscriber” or ”Absent subscriber SM” (MAP v3).
A.27.4 OB–FSM–IEFWS (21) – Incoming unsuccessful forward from SGSN (GMSC)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on receiving in the GMSC the FORWARD SHORT MESSAGE Error with cause
”Absent subscriber” or ”Absent subscriber SM” (MAP v3) from a SGSN.
ED 01
AAC020023800DS En 158 / 260
260
A.27.5 OB–FSM–IFWREQ (10) – Incoming forward request (VMSC)
Counter incremented at the reception of the FORWARD SHORT MESSAGE Invoke from the GMSC.
A.27.6 OB–FSM–ISFW (04) – Incoming successful forward (GMSC)
Counter incremented at the reception of the FORWARD SHORT MESSAGE Result message from the
VMSC.
A.27.7 OB–FSM–ISFWS (20) – Incoming successful forward from SGSN (GMSC)
Counter incremented at the reception of the FORWARD SHORT MESSAGE Result message from a
SGSN.
A.27.8 OB–FSM–MWDREQ (07) – Message waiting data/Report SM delivery status request

(GMSC)
Counter incremented on sending the MESSAGE WAITING DATA Invoke (phase 1) or REPORT SM
DELIVERY STATUS Invoke (phase 2) to the HLR.
A.27.9 OB–FSM–OEFW (12) – Outgoing unssuccessful forward (VMSC)
Counter incremented on sending to the GMSC the FORWARD SHORT MESSAGE Error with cause
”Absent subscriber” or ”Absent subscriber SM” (MAP v3).
A.27.10 OB–FSM–OFWREQ (03) – Outgoing forward request (GMSC)
Counter incremented on sending the FORWARD SHORT MESSAGE Invoke to the VMSC.
A.27.11 OB–FSM–OFWREQS (19) – Outgoing forward request to SGSN (GMSC)
Counter incremented on sending the FORWARD SHORT MESSAGE Invoke to a SGSN.
A.27.12 OB–FSM–OSFW (11) – Outgoing successful forward (VMSC)
Counter incremented on sending the FORWARD SHORT MESSAGE Result message to the GMSC.
A.27.13 OB–FSM–RCFREQ (13) – RCF request (VMSC)
Counter incremented on sending the RP DATA message to the MS.
A.27.14 OB–FSM–REL (15) – SMT procedure release (VMSC)
Counters, per release domain, incremented on release of a Short Message Terminating procedure
A.27.15 OB–FSM–RGREQ (05) – routing request (GMSC)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on sending the SEND ROUTING INFO. FOR SHORT MESSAGE to the HLR.
ED 01
AAC020023800DS En 159 / 260
260
A.27.16 OB–FSM–SCREQ (01) – Service center request (GMSC)
Counter incremented on reception of the RP DATA message from the SC.

A.27.17 OB–FSM–SMWD (08) – Successful message waiting data/Report SM delivery status

(GMSC)
Counter incremented at the reception of the MESSAGE WAITING DATA Result (phase 1) or REPORT
SM DELIVERY STATUS Result (phase 2) from the HLR.
A.27.18 OB–FSM–SODBSMOC (16) – Number of SMSMO refused due to ODB of outgoing calls.
Counter incremented on detection of refusal of an SMSMO due to ODB of outgoing calls.
A.27.19 OB–FSM–SRG (06) – Successful routing (GMSC)
Counter incremented at the reception of the SEND ROUTING INFO. FOR SHORT MESSAGE Result
from the HLR.
A.27.20 OB–FSM–SSMRX (14) – successful short message reception (VMSC)
Counter incremented on reception of the RP ACK message from the MS.
A.27.21 OB–FSM–SSMTX (02) – Successful short message transmission (GMSC)
Counter incremented on sending the RP ACK message to the SC.
A.28 –––––––––––––––––––– SW counters (311)––––––––––––––––––––––––––
A.28.1 OB–FSW–ACMGTW (21) – Reception of ACM event
Counter incremented on reception of a ACM component in case of gateway procedure.
A.28.2 OB–FSW–ANMGTW (26) – Reception of ANM event
Counter incremented on reception of a ANM component in case of gateway procedure
A.28.3 OB–FSW–EAEVRF (02) – Outgoing call establishment failures
(included in release counters FTC–REL and FSW–GTWREL)
Counter incremented on reception of a CREATE error component and on reception of an

EVENT(release) component if it occurs before an EVENT(acm) component is received.
(Failure of inter MSC handover calls are not taken into account).
N.B. (1) This counter is not incremented on reception of periodical SSP test message.
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.28.4 OB–FSW–EARGMSC (09) – Call forwarding refusals (GMSC)
(identical to FSW–SRIFWDVIOL)
ED 01
AAC020023800DS En 160 / 260
260
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code is
”ForwardingViolation”.
A.28.5 OB–FSW–EIRAGMSC (07) – Failures of interrogation for rerouting call excepted For-
warding Violation
(success are counted by OB–FSW–SIRAGMSC)
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code dif-
fers from ForwardingViolation.
A.28.6 OB–FSW–ENAEMSC (05) – Incoming call failures in VMSC
(included in FTC–REL and FSW–GTWREL)
Counter incremented on transmission of a FREE Invoke component before transmission of a GENERATE

SIGNAL(acm) component for a non rerouted incoming call
N.B. This definition does not include some cases of no response to paging and the case of release
by the SSP.
A.28.7 OB–FSW–FILMCF (27) – Number of routing on announcement
Counters, per film number, incremented on transmission of SEND component with logical film number (not
including the SEND component re–emitted in case of handover).
A.28.8 OB–FSW–GTWREL (22) – Gateway procedure release
Counters, per release domain, incremented on release of a gateway procedure per release domain.
A.28.9 OB–FSW–IWFINSREQ (30) – Number of IWF insertion request
Counter incremented on sending of CREATE component for IWF insertion.
A.28.10 OB–FSW–IWFINSRES (31) – Number of IWF insertion success
Counter incremented on receipt of PROVIDE INSTRUCTION component for IWF insertion.
A.28.11 OB–FSW–IWFINS–MOD–REQ (43) – Number of IWF insertion requests for MODIFY

using the SSP generic function
Counter incremented on sending of INSERT invoke for IWF insertion after receiving a MODIFY request.
A.28.12 OB–FSW–IWFINS–MOD–RES(44) – Number of IWF insertion results for MODIFY using

the SSP generic function
Counter incremented on receipt of INSERT result for IWF insertion after receiving a MODIFY request.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 161 / 260
260
A.28.13 OB–FSW–IWFINS–OC–REQ (39) – Number of IWF insertion requests in OC call using
Counter incremented on sending of CREATE invoke with IWF insertion for OC call establishment.
A.28.14 OB–FSW–IWFINS–OC–RES (40) – Number of IWF insertion results in OC call using the
SSP generic function
Counter incremented on receipt of RETRIEVE result with IWF insertion for OC call establishment.
A.28.15 OB–FSW–IWFINS–TC–REQ (41) – Number of IWF insertion requests in TC call using

Counter incremented on sending of INSERT invoke with IWF insertion for TC call establishment.
A.28.16 OB–FSW–IWFINS–TC–RES (42) – Number of IWF insertion results in TC call using the
SSP generic function
Counter incremented on receipt of INSERT result with IWF insertion for TC call establishment.
A.28.17 OB–FSW–ODBECT (37) – Number of ECT refused due to ODB of call transfer calls
Counter incremented on detection of refusal of a call transfer invocation due to ODB of call transfer
A.28.18 OB–FSW–OPCALL (28) – Terminating operator calls in VMSC
Counter incremented on receipt of PROVIDE INSTRUCTION component indicating ”National operator

with offer facility” as CallingPartyCategory in case of TC procedure.
A.28.19 OB–FSW–OPINTR (29) – Interventions requested by operator
Counter incremented on transmission of a JOIN Invoke component requesting a connection between the
operator leg and the MS leg further to the receipt of EVENT (OPR) component when handling an operator
call.
A.28.20 OB–FSW–OTC–SRI (35) – Number of received SRI result with VlrContainer
Counter incremented each time a SEND ROUTING INFO Result containing extension related to Opti-
mized Terminating Call function is received.
A.28.21 OB–FSW–OTC–MSRN (36) – Number of local MSRN request
Counter incremented each time a Provide Local Roaming Number is requested (related to Optimized
Terminating Call function).
A.28.22 OB–FSW–SAEGVRF (10) – Calls outgoing from GMSC
Counter incremented on transmission of a CREATE Invoke component whose CalledPartyAddress

1AA 00014 0004 (9007) A4 – ALICE 04.10
parameter does not designate a BSC, for a gateway or unconditionally forwarded call (calling leg initiated
by a PROVIDE INSTRUCTION).
ED 01
AAC020023800DS En 162 / 260
260
A.28.23 OB–FSW–SAEVRF (01) – Calls outgoing from MSC.

parameter does not designate a BSC, for an originating call.
(CREATE for inter MSC handover are not taken into account).
N.B. (1) This counter is not incremented on transmission of periodical SSP test message.
A.28.24 OB–FSW–SARGMSC (08) – Calls forwarded (GMSC)
Counter incremented if the ForwardedToNumber parameter has been received in the SEND ROUTING
INFO Result component, and whe this ForwardedToNumber is used for routing the call.
A.28.25 OB–FSW–SARVRF (20) – Conditionally Forwarded calls outgoing from MSC

parameter does not designate a BSC, for a conditionally forwarded call
A.28.26 OB–FSW–SHOP–DENIED (38) – Single Hop denials on originating side
Counter, per BSC, incremented on receipt of ACM/CPG message from the terminating side for a single
hop call with acessInformation parameter containing a singleHopInfo parameter either with no other
parameter or with the indication ”TCH to be re–assigned”.
A.28.27 OB–FSW–SIRAGMSC (06) – Interrogations for call rerouting
(identical to FSW–SRIOC + FSW–SRICFMSC + FSW–SRIGTW)
Counter incremented on transmission of the SEND ROUTING INFO Invoke component.
A.28.28 OB–FSW–SNAEGMSC (03) – Calls from fixed network (GMSC).
Counter incremented on reception of a PROVIDE INSTRUCTION Invoke component whose Called-

PartyAddress parameter contains a MSISDN.
N.B. (1) This counter is not incremented on reception of periodical RCP test message.
A.28.29 OB–FSW–SNAEMSC (04) – Incoming calls (VMSC).
Counter incremented on reception of a PROVIDE INSTRUCTION Invoke component whose Called-

PartyAddress parameter contains a MSRN.
N.B. (1) This counter is not incremented on reception of periodical RCP test message or on recep-
tion of Provide instruction due to IWF insertion.
A.28.30 OB–FSW–SRIABSSUB (24) – Failures of interrogation for rerouting call because of

Absent Subscriber
1AA 00014 0004 (9007) A4 – ALICE 04.10
AbsentSubscriber.
ED 01
AAC020023800DS En 163 / 260
260
A.28.31 OB–FSW–SRICFMSC (18) – Interrogations for call rerouting (CF MSC)
Counter incremented on transmission of the SEND ROUTING INFO Invoke component, for a forwarded
call
A.28.32 OB–FSW–SRICFRES (19) – Results of interrogation for rerouting calls
Counter incremented on reception of the SEND ROUTING INFO Result component with the Roaming-
Number parameter, for a forwarded call
A.28.33 OB–FSW–SRIFWDVIOL (14) – Call forwarding violation
(replace FSW–EARGMSC)
”ForwardingViolation”.
A.28.34 OB–FSW–SRIGTW (11) – Interrogations for call rerouting (GTW)
Counter incremented on transmission of the SEND ROUTING INFO Invoke component, for a gateway
call.
This counter is not incremented in the second interrogation in CAMEL case (parameter Suppress TCSI
present).
A.28.35 OB–FSW–SRIGTW2 (32) – Interrogations for call rerouting (GTW)
Counter incremented on transmission of the SEND ROUTING INFO Invoke component, for a gateway
call, in CAMEL case.
A.28.36 OB–FSW–SRIGTWCAM (45) – Results of first interrogation without FTN nor MSRN
Counter incremented on reception of the SEND ROUTING INFO Result component without the Forwar-
dedToNumber and RoamingNumber parameters, for a gateway call (CAMEL case).
A.28.37 OB–FSW–SRIGTWCF (13) – Results of interrogation for rerouting calls (with CFU)
Counter incremented on reception of the SEND ROUTING INFO Result component with the Forwarded-
ToNumber parameter, for a gateway call
A.28.38 OB–FSW–SRIGTWRES (12) – Results of interrogation for rerouting calls
Number parameter, for a gateway call
A.28.39 OB–FSW–SRIOC (15) – Interrogations for call rerouting (OC)
Counter incremented on transmission of the SEND ROUTING INFO Invoke component, for an OC
towards a MS belonging to the PLMN.
1AA 00014 0004 (9007) A4 – ALICE 04.10
This counter is not incremented in the second interrogation in CAMEL case (parameter Suppress TCSI
present).
ED 01
AAC020023800DS En 164 / 260
260
A.28.40 OB–FSW–SRIOC2 (33) – Interrogations for call rerouting (OC)
Counter incremented on transmission of the SEND ROUTING INFO Invoke component, for an OC
towards a MS belonging to the PLMN, in CAMEL case.
A.28.41 OB–FSW–SRIOCCAM (46) – Results of first interrogation without FTN nor MSRN
Counter incremented on reception of the SEND ROUTING INFO Result component without the Forwar-
dedToNumber and RoamingNumber parameters, for an OC towards a MS belonging to the PLMN
(CAMEL case).
A.28.42 OB–FSW–SRIOCCF (17) – Results of interrogation for rerouting calls (with CFU)
Counter incremented on reception of the SEND ROUTING INFO Result component with the Forwarded-
ToNumber parameter, for an OC towards a MS belonging to the PLMN
A.28.43 OB–FSW–SRIOCRES (16) – Results of interrogation for rerouting calls
Number parameter, for an OC towards a MS belonging to the PLMN
A.28.44 OB–FSW–SRISNOTSU (25) – Failures of interrogation for rerouting call because of ser-
vice not supported
”BearerServiceNotProvided”, ”FacilityNotSupported” or ”TeleserviceNotProvided”.
A.28.45 OB–FSW–SRIUNKSUB (23) – Failures of interrogation for rerouting call because of

Unknown Subscriber
”Unknownsubscriber”.
A.28.46 OB–FSW–TONECF (34) – Number of routing on tone
Counters, per tone number, incremented on transmission of SEND component with logical tone number
(not including the SEND component re–emitted in case of handover).
A.29 –––––––––––––––––––– TC counters (306) ––––––––––––––––––––––––
A.29.1 OB–FTC–ALERT (05) – MS terminating calls with Alerting
Counters, per BSC/RNC, incremented on reception of ALERT message from MS.
A.29.2 OB–FTC–C–FORREL (19) – VMSC–forwarded TC during conversation phase
Counters, per release domain, incremented on release of a VMSC–forwarded terminating call during con-
1AA 00014 0004 (9007) A4 – ALICE 04.10
versation phase
ED 01
AAC020023800DS En 165 / 260
260
A.29.3 OB–FTC–C–REL (18) – TC releases during conversation phase
Counters, per release domain, incremented on release of a (not forwarded in VMSC or in GMSC) terminat-
ing call during conversation phase
A.29.4 OB–FTC–CALCONF (04) – Confirmed MS terminating calls
Counters, per BSC/RNC, incremented on reception of CALL_CONFIRMED from MS.
A.29.5 OB–FTC–CALCONF–BS (10) – Confirmed MS terminating calls per basic service
Counters, per basic service, incremented on reception of CALL_CONFIRMED from MS.
A.29.6 OB–FTC–CONNECT (06) – Successful MS terminating calls
Counters, per BSC/RNC, incremented on transmission of CONNECT_ACK message towards MS.
A.29.7 OB–FTC–DURC–BS (16) – Conversation phase duration for terminating calls
Time counters in seconds, per basic service, incremented at the end of the call (DISCONNECT, radio link
break ...) with the time elapsed between the CONNECT message reception and the end of the call; at the
same time, OB–FTC–NBRC–BS counter is also incremented by one.
A.29.8 OB–FTC–DURE–BS (12) – Establishment phase duration for terminating calls
Time counters in seconds, per basic service, incremented on reception of ALERTING or CONNECT mes-
sage with the time elapsed between the reception of a PROVIDE INSTRUCTION message with MSRN
and the ALERTING or CONNECT message reception; at the same time, OB–FTC–NBRE–BS counter is
also incremented by one.
When GMSC = VMSC, the counter is incremented with the time elapsed between the reception of a
SEND–ROUT–INFO–RES message with MSRN and the ALERTING or CONNECT message reception.
A.29.9 OB–FTC–DURS–BS (14) – Ringing phase duration for terminating calls
Time counters in seconds, per basic service, incremented on reception of CONNECT message with the
time elapsed between the ALERTING message reception and the CONNECT message reception; at the
same time, OB–FTC–NBRS–BS is also incremented by one.
A.29.10 OB–FTC–EARMSC (02) – Refusal of call forwarding (MSC)
Counter incremented on reception of the SEND INFO FOR INCOMING CALL SET UP Error component
whose error code is ”ForwardingViolation”.
A.29.11 OB–FTC–FORREL (09) – TC forwarded in VMSC
Counter, per release domain, incremented on release of a terminating call forwarded in the VMSC.
1AA 00014 0004 (9007) A4 – ALICE 04.10
A.29.12 OB–FTC–NBRC–BS (17) – Number of calls taken into account in OB–FTC–DURC–BS

counter
Counters, per basic service, incremented by one on each incrementation of OB–FTC–DURC–BS counter
ED 01
AAC020023800DS En 166 / 260
260
A.29.13 OB–FTC–NBRE–BS (13) – Number of calls taken into account in OB–FTC–DURE–BS
counter
Counters, per basic service, incremented by one on each incrementation of OB–FTC–DURE–BS counter
A.29.14 OB–FTC–NBRS–BS (15) – Number of calls taken into account in OB–FTC–DURS–BS

counter
Counters, per basic service, incremented by one on each incrementation of OB–FTC–DURS–BS counter
A.29.15 OB–FTC–REJ (08) – Rejected TC for regulation cause
Counter incremented on rejection of PROVIDE INSTRUCTION Request for traffic regulation cause.
A.29.16 OB–FTC–REL (07) – TC releases
Counters, per release domain, incremented on release of a (non forwarded) terminating call
A.29.17 OB–FTC–SARMSC (01) – Forwarded calls (MSC)
( identical to OB–FXX–SISS (CFxxINV))
Counter incremented on reception of the CONNECT TO FOLLOWING ADDRESS component.
A.29.18 OB–FTC–SNGWTC (03) – Incoming and MS terminating calls
Counter incremented on reception of the SEND ROUTING INFO Result component with local MSRN,
for an incoming call from fixed network.
A.29.19 OB–FTC–SODBSH (11) – Number of CH invocations due to ODB of SS management
Counter incremented on detection of refusal of call hold during a terminating call due to ODB of supple-
mentary service management.
A.30 ––––––––––––––––––––– TR counters (316) ––––––––––––––––––––––
A.30.1 OB–FTR–ANARES (01) – Number of translation analysis results observed
Counters, per observed translation result, incremented on each translator nvocation leading to this result.
A.31 ––––––––––––––––––––– UU counters (395) ––––––––––––––––––––––
A.31.1 OB–FUU–PUUSOC (01) – Number of OC with PUUS activated
Counter incremented on transmission of CREATE component (called address # BSC) for an originating
call with UUI included in the message.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 167 / 260
260
A.31.2 OB–FUU–PUUSTC (02) – Number of TC with PUUS activated
Counter incremented on transmission of a SETUP to the MS for a terminating call with UUI included in the
message.
A.31.3 OB–FUU–UUIMSN (03) – Number of UUI transferred from MS to network
Counter incremented on sending INAP messages to SSP (CREATE, FREE, GENERATE SIGNAL) with
UUI included for originating and terminating calls.
A.31.4 OB–FUU–UUINMS (04) – Number of UUI transferred form network to MS
Counter incremented on sending INT–A messages (ALERT, PROGRESS, CONNECT, DISCONNECT,

SETUP, RELEASE) with UUI included for originating and terminating call.
A.32 ––––––––––––––––––––– VH counters (354) ––––––––––––––––––––––
A.32.1 OB–FVH–FALLBACK (01) – Number of MAP version fallbacks
Counter incremented when a TC–BEGIN message is answered with a TC–ABORT message due to ver-
sion not supported for a given application context while there is a version supported by both entities for
this AC (this does not imply that a fallback procedure will occur).
A.32.2 OB–FVH–FALLBACKUN (02) – Number of unexpected MAP version fallbacks
Counter incremented on reception of the TC_U_Abort message as answer to a previous TC_BEGIN mes-
sage, due to version not supported for a given application context by a foreign PLMN entity which was
supposed to support it (the spontaneous message WR_VH_101 is emitted).
A.32.3 OB–FVH–PHASE1–TRANS (05) – Call independant SS with MS handled in phase 1
Counter incremented on reception of the Facility Information element with the SS version indicator
absent or equal to ”phase 1”.
A.32.4 OB–FVH–PHASE1CNX (03) – Connection with MS phase 1
Counter incremented on reception of the CM SERVICE REQUEST or PAGING RESPONSE message

with ”MS revision level” equal to ”phase 1”.
A.32.5 OB–FVH–PHASE2–TRANS (06) – Call independent SS with MS handled in phase 2
Counter incremented on reception of the Facility Information element with the SS version indicator
unknown or equal to ”phase 2”.
A.32.6 OB–FVH–PHASE2CNX (04) – Connection with MS phase 2

1AA 00014 0004 (9007) A4 – ALICE 04.10
with ”MS revision level” equal to ”phase 2”.
ED 01
AAC020023800DS En 168 / 260
260
A.32.7 OB–FVH–R99CNX (07) – Connection with MS Release 99 at least

with ”MS revision level” indicating that the MS supports at least the Release 99 version of the protocol.
A.33 –––––––––––––––––––– XX/SH counters (330) –––––––––––––––––––––
A.33.1 OB–FSH–REL (03) – Supplementary service operation release
Counters, per release domain, incremented on Supplementary service operation release.
A.33.2 OB–FXX–ASS (02) – Supplementary service acceptance
Counters incremented per supplementary service:
a) CALL HOLD
Counter incremented on sending of the message HOLD–ACK towards the mobile station.
b ) CALL RETRIEVE
Counter incremented on sending of the message RETRIEVE– ACK towards the mobile station.
c ) ALTERNATE PROCEDURE
Counter incremented on alternate tempo resetting
d ) CALL WAITING
Counter incremented on reception of M_CONNECT message from the MS.
e ) ADVICE OF CHARGE CHARGING
Counter incremented on receipt of the ForwardChargeAdvice (Result) component (within a FACIL-
ITY messsage) from the MS if AoC Charging is invoked.
f ) OUTGOING CUG
Counter incremented on receipt of CompleteCall message containing a CUG interlock code.
g ) TERMINATING CUG
Counter incremented on receipt of CompleteCall or ProcessCallWaiting message containing a
CUG index, or on ConnectToFollowingAddress message containing a CUG InterlockCode when
no CompleteCall has been received before.
h ) EXPLICIT CALL TRANSFER
Counter incremented on sending of the message DISC with facility invoke (result of ECT) or on send-
ing N_REL_COM with <successful text string> concerning ECT.
i ) CONNECTED LINE IDENTITY PRESENTATION
Counter incremented on receipt of MI_CONNECT message from SW function and before the send-
ing of the message MI_N_CONNECT towards the mobile station if COLP was requested and in the
message PI is set to allowed and LI is present.
j ) CONNECTED LINE IDENTITY PRESENTATION WITH OVERRIDE CATEGORY
Counter incremented on receipt of MI_CONNECT message from SW function and before the send-
ing of the message MI_N_CONNECT towards the mobile station if COLP was requested, if override
category is enabled and if in the message PI is set to restricted and LI is present
k ) BUILDMPTY
Counter incremented on sending of BuildMPTY Acknowledge to the MS
l ) HOLDMPTY
Counter incremented on sending of HoldMPTY Acknowledge to the MS
m ) RETRIEVEMPTY
Counter incremented on sending of RetrieveMPTY Acknowledge to the MS
1AA 00014 0004 (9007) A4 – ALICE 04.10
n ) SPLITMPTY
Counter incremented on sending of SplitMPTY Acknowledge to the MS
o ) CCBS REQUEST
Counter incremented on receipt of REGISTER CC ENTRY RES from the VLR related to CCBS
ED 01
AAC020023800DS En 169 / 260
260
p) eMLPP
Counter incremented on the receipt of COMPLETE CALL message indicating that eMLPP supple-
mentary service is subscribed without any information on the priority granted to the call (which means
that the priority explicitely requested for the call applies).
N.B. This includes explicit requests that the call be handled with no priority.
A.33.3 OB–FXX–SISS (01) – Supplementary service invocations
Counters incremented per supplementary service:
a) INCOMING CALL BARRING

Counter incremented on reception of the SEND ROUTING INFO Error component with the ”call
barred” error code, if the parameter associated to this error code is different from ”operator interven-
tion”.
b ) OUTGOING CALL BARRING
Counter incremented on reception of the SEND INFORMATION FOR O/C SET UP Error component
with the ”call barred” error code, if the parameter associated to this error code is different from ”opera-
tor intervention”.
c ) CALL WAITING
Counter incremented on reception of the PROCESS CALL WAITING Invoke component.
d ) CALL HOLD
Counter incremented on reception of the message HOLD received from the mobile station.
e ) CALL RETRIEVE
Counter incremented on reception of the message RETRIEVE received from the mobile station.
f ) ALTERNATE PROCEDURE
Counter incremented on alternate tempo setting
g ) CALL FORWARDING – Busy MS forwarding
Counter incremented on reception of the CON_F_AD_I component, for Busy MS cause.
h ) CALL FORWARDING – Unreachable MS forwarding
Counter incremented on reception of the CON_F_AD_I component, for unreachable MS cause
i ) CALL FORWARDING – No reply forwarding
Counter incremented on reception of the CON_F_AD_I component, for no reply condition timer
expiry cause.
j ) CLIR
Counter incremented on reception of the COM–CALL–I component, with CLIP provisioned at called
side and CLIR provisioned at calling side
k ) ADVICE OF CHARGE INFORMATION
Counter incremented on first sending of the FORWARDCHARGEADVICE (Invoke) component and
related to AoCI service (within a call control messsage) toward the MS.
l ) ADVICE OF CHARGE CHARGING
Counter incremented on first sending of the FORWARDCHARGEADVICE (Invoke) component and
related to AoCC service (within a call control messsage) toward the MS.
m ) OUTGOING CUG
Counter incremented on receipt of the SETUP message containing a FACILITY IE with Forward-
CUG–Info operation.
n ) TERMINATING CUG
Counter incremented on receipt of the PROVIDE INSTRUCTION message with CUG Interlock-
Code provided
o ) MALICIOUS CALL IDENTIFICATION
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented when issuing the spontaneous message WR_CG_103.
ED 01
AAC020023800DS En 170 / 260
260
p) CLIRAINV
Counter incremented on receipt of the SETUP message with CLIR invocation parameter present,
while CLIR service in temporary mode with default value ”Presentation Allowed” is subscribed by the
calling MS
q ) CLIRRINV
Counter incremented on receipt of the SETUP message with CLIR suppression parameter present,
while CLIR service in temporary mode with default value ”Presentation Restricted” is subscribed by
the calling MS
r ) CLIPOINV
Counter incremented on receipt of the PROVIDE INSTRUCTION message with CLIR requested,
while CLIP service with override category is subscribed by the called MS
s ) EXPLICIT CALL TRANSFER
Counter incremented on receipt of FACILITY (ECT) or FACILITY (USSD(ECT)) messages.
t ) CONNECTED LINE PRESENTATION
Counter incremented on receipt of the COMPLETE CALL Invoke message when COLP is provi-
sioned in originating call.
u ) CONNECTED LINE RESTRICTION
Counter incremented on receipt of the MI_N_CONNECT message from the MS and before the send-
ing of the MI_TC_CONNECT or MI_CW_CONNECT message (in case of call waiting) to the SW
function, when COLR is provisioned and if the connected line identity request indication is set to
Requested.
v ) BUILDMPTY
Counter incremented on receipt of BuildMPTY request from the MS.
w ) HOLDMPTY
Counter incremented on receipt of HoldMPTY request from the MS.
x ) RETRIEVEMPTY
Counter incremented on receipt of RetrieveMPTY request from the MS.
y ) SPLITMPTY
Counter incremented on receipt of SplitMPTY request from the MS.
z ) CCBS
Counter incremented on receipt of the REGISTER CC ENTRY request from the MS (for a MS sup-
porting PCP) or the FACILITY request indicating ”CCBS request” from the MS (for a MS not support-
ing PCP) (on the A side)
aa ) eMLPP
Counter incremented on the receipt of CM SERVICE REQUEST for MO or emergency call establish-
ment including a priority indication.
A.34 ––––––––––––––––––––– XX/SLI counters (300) ––––––––––––––––
A.34.1 OB–FXX–SEMN3 (02) – Level 3 messages from MSC to BSC/RNC
Counters per terminating BSC/RNC incremented on transmission of a DTAP or BSSMAP/RANAP mes-

sage. (during handover/relocation, OB– FXX–SEMN3 counter attached to old BSC/RNC may be increm-
ented for messages which will be in fact directed to the new one).
A.34.2 OB–FXX–SRMN3 (03) – Level 3 messages received by MSC from BSC/RNC
Counters per originating BSC/RNC incremented on reception of a DTAP or BSSMAP/RANAP message.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 171 / 260
260
APPENDIX B – VLR COUNTER IMPLEMENTATION

B.1 Warning.
transmitted to the application level but before any parameters content analysis which may further lead to
message rejection in the processing. As a consequence, incoming requests not transmitted in case of
overload detected by RTOS are not taken into account.
B.2 –––––––––––––––––––– CA counters (257) ––––––––––––––––––––––
B.2.1 OB–VCA–MMEVENTN (01)
Counter indicating the total number of MM–Event–Notification messages sent by VLR to SCP.
B.3 –––––––––––––––––––– CCP counters (252) ––––––––––––––––––––––
B.3.1 OB–VCCP–ERA (3) – Erase CC entry received per supplementary service related to call
completion
Counter incremented on receipt of the ERASE CC ENTRY Invoke component from RCF related to call
completion. There is one counter per supplementary service related to call completion.
B.3.2 OB–VCCP–ERA–F (4) – Erase CC entry failure per supplementary service related to call
completion
Counter incremented on receipt of the ERASE CC ENTRY Error component from HLR related to call
B.3.3 OB–VCCP–REG (1) – Register CC entry received per supplementary service related to call
completion
Counter incremented on receipt of the REGISTER CC ENTRY Invoke component from RCF related to
call completion. There is one counter per supplementary service related to call completion.
B.3.4 OB–VCCP–REG–F (2) – Register CC entry failure per supplementary service related to call
completion
Counter incremented on receipt of the REGISTER CC ENTRY Error component from HLR related to call
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 172 / 260
260
B.4 –––––––––––––––––––– CT counters (249) ––––––––––––––––––––––
B.4.1 OB–VCT–ACTRMOD (1) – Activate trace mode received

Counter incremented on reception of the ACTIVATE TRACE MODE Invoke component from HLR.
B.4.2 OB–VCT–ACTRMODR (2) – Activate trace mode sent
Counter incremented on transmission of the ACTIVATE TRACE MODE Result toward HLR.
B.5 –––––––––––––––––––– GP counters (235)–––––––––––––––––––––––––
B.5.1 OB–VGP–ALRTACK (11) – Alert Ack message received from a SGSN
Counter incremented on reception of a Alert Ack message from a SGSN.
B.5.2 OB–VGP–ALRTREQ (10) – Alert Request message sent to a SGSN
Counter incremented on sending of a Alert Request message to a SGSN.
B.5.3 OB–VGP–GPDETACK (14) – GPRS_Detach_Ack message sent to a SGSN
Counter incremented on sending of a GPRS_Detach_Ack message to a SGSN.
B.5.4 OB–VGP–GPDETIND (13) – GPRS_Detach_Indication message received from a SGSN
Counter incremented on reception of a GPRS_Detach_Indication message from a SGSN.
B.5.5 OB–VGP–IMDETACK (16) – IMSI_Detach_Ack message sent to a SGSN
Counter incremented on sending of a IMSI_Detach_Ack message to a SGSN.
B.5.6 OB–VGP–IMDETIND (15) – IMSI_Detach_Indication message received from a SGSN
Counter incremented on reception of a IMSI_Detach_Indication message from a SGSN.
B.5.7 OB–VGP–LOCUPACP (08) – Location Update Accept message sent to a SGSN
Counter incremented on sending of a Location Update Accept message to a SGSN.
B.5.8 OB–VGP–LOCUPREQ (07) – Location Update Request message received from a SGSN
Counter incremented on reception of a Location Update Request message from a SGSN.
B.5.9 OB–VGP–MMINFREQ (23) – MM_information Request message sent to a SGSN

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on sending of a MM_information Request message to a SGSN.
ED 01
AAC020023800DS En 173 / 260
260
B.5.10 OB–VGP–MOBMMR (24) – Mobile Status message received from a SGSN containing a
MM Information Request message
Counter incremented on reception of a Mobile Status message from a SGSN, containing a MM Information
Request message.
B.5.11 OB–VGP–MOBSTR (26) – Mobile Status message received from a SGSN
Counter incremented on reception of a Mobile Status message from a SGSN.
B.5.12 OB–VGP–MOBSTS (25) – Mobile Status message sent to a SGSN
Counter incremented on sending of a Mobile Status message to a SGSN.
B.5.13 OB–VGP–MSACTIV (12) – MS_Activity_Indication message received from a SGSN
Counter incremented on reception of a MS_Activity_Indication message from a SGSN.
B.5.14 OB–VGP–MSINFREQ (21) – MS_information Request message sent to a SGSN
Counter incremented on sending of a MS_information Request message to a SGSN.
B.5.15 OB–VGP–MSINFRES (22) – MS_information Response message received from a SGSN
Counter incremented on reception of a MS_information Response message from a SGSN.
B.5.16 OB–VGP–PAGREJ (02) – Paging Reject message received from a SGSN
Counter incremented on reception of a Paging Reject message from a SGSN, including Paging Reject
message for SMT, LCS,..
B.5.17 OB–VGP–PAGREQ (01) – Paging Request message sent to a SGSN
Counter incremented on sending of a Paging Request message to a SGSN, including Paging Request
message for SMT, LCS,..
B.5.18 OB–VGP–PASMRJ (05) – Paging Reject message for SMT received from a SGSN
Counter incremented on reception of a Paging Reject message for SMT from a SGSN.
B.5.19 OB–VGP–PASMRQ (04) – Paging Request message for SMT sent to a SGSN
Counter incremented on sending of a Paging Request for SMT message to a SGSN.
B.5.20 OB–VGP–RESTACKR (20) – Reset_Ack message received from a SGSN
Counter incremented on reception of a Reset_Ack message from a SGSN.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 174 / 260
260
B.5.21 OB–VGP–RESTACKS (18) – Reset_Ack message sent to a SGSN
Counter incremented on sending of a Reset_Ack message to a SGSN.

B.5.22 OB–VGP–RESTINDR (17) – Reset_Indication message received from a SGSN
Counter incremented on reception of a Reset_Indication message from a SGSN.
B.5.23 OB–VGP–RESTINDS (19) – Reset_Indication message sent to a SGSN
Counter incremented on sending of a Reset_Indication message to a SGSN.
B.5.24 OB–VGP–TMSIREAL (09) – TMSI_Reallocation_Complete message received from a

SGSN
Counter incremented on reception of a TMSI_Reallocation_Complete message from a SGSN.
B.5.25 OB–VGP–UNREACH (03) – MS_Unreachable message received from a SGSN
Counter incremented on reception of a MS_Unreachable message from a SGSN, including MS_Unreach-

able message for SMT
B.5.26 OB–VGP–UNREASM (06) – MS_Unreachable message for SMT received from a SGSN
Counter incremented on reception of a MS_Unreachable message for SMT from a SGSN.
B.6 –––––––––––––––––––– LR counters (204) –––––––––––––––––––––––––
B.6.1 OB–VLR–AUTHVISIT (12) – Authorized other PLMN MS registrations
Counter incremented on reception of UPDATE LOCATION Result component from other PLMN HLR with
allowed roaming.
B.6.2 OB–VLR–CANLOC–HOM (05) – home PLMN HLR registration cancellations
Counter incremented on reception of CANCEL LOCATION component from a home PLMN HLR, where
the IMSI is known and if its location area is known.
B.6.3 OB–VLR–CANLOC–OTH (06) – Other HLR registration cancellations
Counter incremented on reception of CANCEL LOCATION component from an other PLMN HLR, where
the IMSI is known and if its location area is known.
B.6.4 OB–VLR–DSDREQ (25) – Delete subscriber data request
Counter incremented on reception of DELETE SUBSCRIBER DATA Invoke component from HLR.
1AA 00014 0004 (9007) A4 – ALICE 04.10
B.6.5 OB–VLR–DSDRES (26) – Delete subscriber data success
Counter incremented on transmission of DELETE SUBSCRIBER DATA Result component toward HLR.
ED 01
AAC020023800DS En 175 / 260
260
B.6.6 OB–VLR–ENI (04) – Registration failures.
Counter incremented on transmission of the UPDATE LOCATION AREA Error component.

B.6.7 OB–VLR–EXTORI–LAC (14) – Registration request from external originating LAC
Counter incremented on reception of the UPDATE LOCATION AREA Invoke component with external
originating LAC.
B.6.8 OB–VLR–HLRCONF–FLAG (16) – Location update requests to HLR due to set of HLR
conf flag
Counter incremented on transmission of UPDATE LOCATION Invoke component towards HLR when
HLR conf flag is set.
B.6.9 OB–VLR–HLRLOCREQ (09) – Location update requests to HLR
Counter incremented on transmission of UPDATE LOCATION Invoke component towards HLR
B.6.10 OB–VLR–HLRLOCRES (10) – Location update result from HLR
Counter incremented on reception of UPDATE LOCATION Result component from HLR
B.6.11 OB–VLR–IMPDET (24) – Number or implicit detach
Counter incremented on IDT_WD timer expiry for each MS which is marked detached.
B.6.12 OB–VLR–ISDREQ (29) – Number of framed Insert Subscriber data procedure request
received from HLR
Counters, per number of INSERT SUBSCRIBER DATA Invoke message received in the procedure,
incremented at the end of Update location or Restore data procedure.
B.6.13 OB–VLR–ISDRES (30) – Number of framed Insert Subscriber data procedure success
sent to HLR
Counters, per number of INSERT SUBSCRIBER DATA Result message sent in the procedure, increm-
ented at the end of Update location or Restore data procedure.
B.6.14 OB–VLR–MS–UNKN (15) – Registration request from internal originating LAC, not regis-
tered in VLR
Counter incremented on reception of the UPDATE LOCATION AREA Invoke component with internal
originating LAC , but with MS not registered in VLR
B.6.15 OB–VLR–NOHLRUPD (31) – Number of intra VLR location registration without HLR
updating
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on transmission of UPDATE LOCATION AREA Result to RCF in case of location
registration without HLR updating.
ED 01
AAC020023800DS En 176 / 260
260
B.6.16 OB–VLR–NWVLRSPREQ (22) – Send parameters request number in new VLR
Counter incremented in new VLR, on transmission of SEND PARAMETER Invoke (MAP phase 1) or
SEND IDENTIFICATION Invoke (MAP phase 2) component.
B.6.17 OB–VLR–NWVLRSPRES (23) – Send parameters result number in new VLR
Counter incremented in new VLR, on reception of SEND PARAMETER Result (MAP phase 1) or SEND
IDENTIFICATION Result (MAP phase 2) component.
B.6.18 OB–VLR–OLVLRSPREQ (08) – Send parameters request number in old VLR
Counter incremented in old VLR, on reception of SEND PARAMETER Invoke (MAP phase 1) or SEND
IDENTIFICATION Invoke (MAP phase 2) component.
B.6.19 OB–VLR–OLVLRSPRES (21) – Send parameters result number in old VLR
Counter incremented in old VLR, on transmission of SEND PARAMETER Result (MAP phase 1) or SEND
IDENTIFICATION Result (MAP phase 2) component.
B.6.20 OB–VLR–OLVLRUKN (07) – Registration requests from unknown VLRs
Counter incremented on inter–MSC location updating, when origin VLR is unknown from VMSC.
B.6.21 OB–VLR–PSIREQ (32) – Number of PSI requests from HLR
Counter incremented on reception of the PROVIDE SUBSCRIBER INFORMATION Invoke message

from HLR.
B.6.22 OB–VLR–PSIRES (33) – Number of PSI results to HLR
Counter incremented on emission of the PROVIDE SUBSCRIBER INFORMATION Result message to

HLR.
B.6.23 OB–VLR–PURGEREQ (17) – Number of PurgeMS requests to HLR
Counter incremented on emission of the PURGE MS message toward HLR.
B.6.24 OB–VLR–PURGERES (18) – Number of PurgeMS responses from HLR
Counter incremented on reception of the PURGE MS Result message from HLR.
B.6.25 OB–VLR–RESTOREQ (19) – Number of restoreData requests to HLR
Counter incremented on emission of the RESTORE DATA Invoke message toward HLR.
B.6.26 OB–VLR–RESTORES (20) – Number of restoreData responses from HLR

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on reception of the RESTORE DATA Result message from HLR.
ED 01
AAC020023800DS En 177 / 260
260
B.6.27 OB–VLR–ROAMNALL (13) – Unallowed roaming
Counter incremented on reception of UPDATE LOCATION Error component from HLR with unallowed
roaming cause.
B.6.28 OB–VLR–SAISDREQ (27) – Number of stand–alone Insert Subscriber data request

received from HLR
Counter incremented on reception of a stand–alone INSERT SUBSCRIBER DATA Invoke component

from HLR.
B.6.29 OB–VLR–SAISDRES (28) – Number of stand–alone Insert Subscriber data success sent
to HLR
Counter incremented on transmission of a stand–alone INSERT SUBSCRIBER DATA Result component

to HLR.
B.6.30 OB–VLR–SANL (01) – Location cancellations
replaced by VLR–CANLOC–HOM + VLR–CANLOC–OTH
Counters, per location area, incremented on reception of the CANCEL LOCATION component where the
IMSI is known and if its location area is known.
This counter is only significant if option F–LR–015 is not active.
B.6.31 OB–VLR–SANLGLO (51) – Location cancellations (global)
Counter incremented on reception of the CANCEL LOCATION Invoke component where the IMSI is
known and if its location area is known.
B.6.32 OB–VLR–SATTGSAS (56) – Subscribers currently registered in the VLR with status ”IMSI
attach” and ”GPRS attach”.
This counter is available when the option F–OBS–008 is active.
– When functional option F–OBS–005 is not active:

This load counter gives the number of registered MS with the parameter ”IMSI attach/detach flag”
set to the value ”attach” and the parameter ”GS–STATE” set to the status ”GS–ASSOCIATED”.
– When functional option F–OBS–005 is active:

This load counter is calculated by addition of all the OB–VLR–SATTGSASP counters.
B.6.33 OB–VLR–SATTGSASP (58) – Subscribers currently registered in the VLR with status
”IMSI attach” and ”GPRS attach”for each PLMN.
This counter is available when the options F–OBS–005 and F–OBS–008 are active.
This load counter gives, per PLMN (E.212, MCC + MNC), the number of registered MS with the parameter
”IMSI attach/detach flag” set to the value ”attach” and the parameter ”GS–STATE” set to the status ”GS–
1AA 00014 0004 (9007) A4 – ALICE 04.10
ASSOCIATED”.
ED 01
AAC020023800DS En 178 / 260
260
B.6.34 OB–VLR–SATTGSNA (55) – Subscribers currently registered in the VLR with status
”IMSI attach” and not ”GPRS detach”.
This counter is available when the option F–OBS–008 is active.

– When functional option F–OBS–005 is not active:

This load counter gives the number of registered MS with the parameter ”IMSI attach/detach flag”
set to the value ”attach” and, for GPRS MS, the parameter ”GS–STATE” not set to the status ”GS–
ASSOCIATED”.
– When functional option F–OBS–005 is active:

This load counter is calculated by addition of all the OB–VLR–SATTGSNAP counters.
B.6.35 OB–VLR–SATTGSNAP (57) – Subscribers currently registered in the VLR with status
”IMSI attach” and not ”GPRS detach” for each PLMN.
This counter is available when the options F–OBS–005 and F–OBS–008 are active.
This load counter gives, per PLMN (E.212, MCC + MNC), the number of registered MS with the parameter
”IMSI attach/detach flag” set to the value ”attach” and, for GPRS MS, the parameter ”GS–STATE” not set
to the status ”GS–ASSOCIATED”.
B.6.36 OB–VLR–SNI (03) – Number of Registrations
Counters, per target location area, incremented on reception of the UPDATE LOCATION AREA Invoke
component depending on the TargetLocAreaId parameter.
B.6.37 OB–VLR–SNIA (02) – Subscribers currently registered in the VLR
When functional option F–OBS–005 is not active:

This Load counter is incremented each time subscriber data transmitted by a HLR for a new IMSI are regis-
tered in database, and decremented each time subscriber data are erased in data base.
When functional option F–OBS–005 is active:

this load counter is calculated by addition of all the OB–VLR–SNIAP counters.
B.6.38 OB–VLR–SNIAP (54) – Subscribers registered in the VLR in each PLMN
Counters, per PLMN (E.212, MCC + MNC) , incremented each time subscriber data transmitted by a HLR
for a new IMSI are registered in the database, and decremented each time subscriber data of a PLMN are
erased in the data base.
B.6.39 OB–VLR–SNIGLO (53) – Registrations number (global)
Counter incremented on reception of the UPDATE LOCATION AREA Invoke component, whatever the
location area may be.
B.6.40 OB–VLR–UNAUTHVISIT (11) – MS registrations from unauthorized PLMN
Counter incremented on location updating for an MS from an unauthorized PLMN.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 179 / 260
260
B.7 –––––––––––––––––––– NR counters (278) ––––––––––––––––––––––––
B.7.1 OB–VNR–UPLACREQ (01) – LAC updating requests through national roaming

Counter incremented on LAC updating (on UPDATE LOCATION, on SEARCH Result, on OUTGOING
Request) for a MS belonging to a PLMN agreed for National roaming.
B.7.2 OB–VNR–UPLACRES (02) – LAC updating success through national roaming
Counter incremented on LAC updating (on UPDATE LOCATION, on SEARCH Result, on OUTGOING
Request) for a MS belonging to a PLMN agreed for National roaming, with national roaming provided in
the current LAC.
B.8 –––––––––––––––––––– PG counters (203) ––––––––––––––––––––––––
B.8.1 OB–VPG–ENPAG (02) – Paging request failures
Counter incremented on reception of the PAGE Error component or the SEARCH Error component.
B.8.2 OB–VPG–PAGING (03) – Paging requests for calls
Counter incremented on transmission of the PAGE Invoke component, for terminating calls.
B.8.3 OB–VPG–PAGING–SM (06) – Paging requests for SM
Counter incremented on transmission of the PAGE Invoke component, for terminating short messages.
B.8.4 OB–VPG–PAGSRCHRES (05) – Paging /Search responses for calls
Counter incremented on reception of the PAGE Result component or the SEARCH Result component,
for terminating calls.
B.8.5 OB–VPG–PAGSRCHRES–SM (08) – Paging /Search responses for SM
Counter incremented on reception of the PAGE Result component or the SEARCH Result component,
for terminating short messages.
B.8.6 OB–VPG–SEARCH (04) – Search requests for calls
Counter incremented on transmission of the SEARCH Invoke component, for terminating calls.
B.8.7 OB–VPG–SEARCH–SM (07) – Search requests for SM
Counter incremented on transmission of the SEARCH Invoke component, for terminating short mes-
sages.
1AA 00014 0004 (9007) A4 – ALICE 04.10
B.8.8 OB–VPG–SNPAG (01) – Paging requests
(identical to VPG–PAGING + VPG–SEARCH)
ED 01
AAC020023800DS En 180 / 260
260
Counter incremented on transmission of the PAGE Invoke
B.9 –––––––––––––––––––– SC counters (210) ––––––––––––––––––––––––

B.9.1 OB–VSC–EALGO (09) – Key reallocation failures due to A5–X algo. uncompatibility (GSM/
BSS coverage)
Counter incremented on reception of the SET CIPHERING MODE Error component with the A5–X incom-
patibility error code.
B.9.2 OB–VSC–ERALG (11) – Key reallocation failures due to algorithm uncompatibility

(UTRAN coverage)
Counter incremented on reception of the SET CIPHERING MODE Error component with the algorithm
incompatibility error code.
B.9.3 OB–VSC–EDAUT (04) – Unsuccessful Authentications with triplets
Counter incremented on reception of an incorrect sres in the AUTHENTICATE Result component.
B.9.4 OB–VSC–EAUTH (12) – Unsuccessful Authentications with quintuplets
Counter incremented on reception of an incorrect res in the AUTHENTICATE Result component.
B.9.5 OB–VSC–EDTRH (02)– Failures of authentication vectors requests to HLR
Counter incremented on reception of the SEND PARAMETERS Error (MAP phase 1) corresponding to
a request for triplets or SEND AUTHENTICATION INFO Error (MAP >= phase 2) component.
B.9.6 OB–VSC–ERESYN (16)– Authentication Failure with Synchro Failure cause (UMTS only)
Counter incremented on reception of the AUTHENTIFICATION_Failure including the failure cause ”Syn-
chro Failure”.
B.9.7 OB–VSC–EAFAIL (17)– Authentication Failure with MAC Failure cause (UMTS only)
Counter incremented on reception of the AUTHENTIFICATION_Failure including the failure cause ”MAC
Failure”.
B.9.8 OB–VSC–ENREAC (06) – Ciphering command failures with triplets
Counter incremented when the SET CIPHERING MODE Result component timeout expires or on recep-
tion of the SET CIPHERING MODE Error component with the A5–X incompatibility error code.
B.9.9 OB–VSC–ECIPH (13) – Ciphering command failures with quintuplets
Counter incremented when the SET CIPHERING MODE Result component timeout expires or on recep-
1AA 00014 0004 (9007) A4 – ALICE 04.10
tion of the SET CIPHERING MODE Error component with the algorithm incompatibility error code.
ED 01
AAC020023800DS En 181 / 260
260
B.9.10 OB–VSC–ENREAT (08) – TMSI reallocation failures
Counter incremented when the FORWARD NEW TMSI Result component timeout expires.
B.9.11 OB–VSC–SDAUT (03) – Authentication requests with triplets
Counter incremented on transmission of the AUTHENTICATE Invoke component for subscriber with trip-
lets under GSM or UMTS coverage.
B.9.12 OB–VSC–URAUT (14) – Authentication requests with quintuplets
Counter incremented on transmission of the AUTHENTICATE Invoke component for subscribers with
quintuplets under UTRAN coverage
B.9.13 OB–VSC–SDTRH (01) – Authentication vectors requests to the HLR
Counter incremented on transmission of the SEND PARAMETERS Invoke (MAP phase 1) where it is
used to request the HLR for triplets or SEND AUTHENTICATION INFO Invoke (MAP >= phase 2) compo-
nent.
B.9.14 OB–VSC–SNREAC (05) – Ciphering commands with triplets
Counter incremented on transmission of the SET CIPHERING MODE Invoke component (even if this
component is not transmitted in a SET CIPHERING MODE command at the A interface in case of A5–X
incompatibility between MSC and MS) with triplets.
B.9.15 OB–VSC–NBCIPH (15) – Ciphering commands with quintuplets
Counter incremented on transmission of the SET CIPHERING MODE Invoke component with quintuplets.
B.9.16 OB–VSC–SNREAT (07) – TMSI reallocations
Counter incremented on transmission of the FORWARD NEW TMSI Invoke component.
B.9.17 OB–VSC–TRREUSED (10) – Triplet reused
Counter incremented on revalidation of already used triplets.
B.10 –––––––––––––––––––– SH counters (230)–––––––––––––––––––––––––
B.10.1 OB–VSH–AR (05) – Unstructured SS operations related to AR function request
Counter incremented on reception of Unstructured–SS request operation related to AR function.
B.10.2 OB–VSH–ENOSS (02) – Supplementary service operation failures
Counters, per supplementary service, incremented for a given service, determined by the ss code param-
1AA 00014 0004 (9007) A4 – ALICE 04.10
eter, on transmission of the following components:

– REGISTER SUPPLEMENTARY SERVICE Error,
– ERASE SUPPLEMENTARY SERVICE Error,
ED 01
AAC020023800DS En 182 / 260
260
– ACTIVATE SUPPLEMENTARY SERVICE Error,
– DEACTIVATE SUPPLEMENTARY SERVICE Error,
– INTERROGATE SUPPLEMENTARY SERVICE Error,
B.10.3 OB–VSH–NIUN (12) – Network initiated unstructured supplementary service notification

invoke
Counter incremented on reception of the following component from the HLR:

– UNSTRUCTURED SS NOTIFY invoke
B.10.4 OB–VSH–NIUR (10) – Network initiated unstructured supplementary service request

invoke
Counter incremented on reception of the following component from the HLR (except for the automatic
relocation procedure):
– UNSTRUCTURED SS REQUEST invoke
B.10.5 OB–VSH–REGPWREQ (07) – Register password request sent
Counter incremented on transmission of REGISTER PASSWORD Invoke message toward the HLR.
B.10.6 OB–VSH–REGPWRES (08) – Register password result received
Counter incremented on reception of REGISTER PASSWORD Result message from the HLR.
B.10.7 OB–VSH–SAR (06) – Unstructured SS operations related to AR function success
Counter incremented on transmission of UNSTRUCTURED–SS Request success when related to AR

function.
B.10.8 OB–VSH–SNIUN (13) – Network initiated unstructured supplementary service notifica-

tion success
Counter incremented on emission of the following component towards the HLR:

– UNSTRUCTURED SS NOTIFY result
B.10.9 OB–VSH–SNIUR (11) – Network initiated unstructured supplementary service request

success
Counter incremented on transmission of the following components towards the HLR (except for automatic
– UNSTRUCTURED SS REQUEST result
B.10.10 OB–VSH–SNOSS (01) – Supplementary service operations
Counters, per supplementary service, incremented for a given service, determined by the ss code param-
eter, on reception of the following component:
– REGISTER SUPPLEMENTARY SERVICE Invoke,
1AA 00014 0004 (9007) A4 – ALICE 04.10
– ERASE SUPPLEMENTARY SERVICE Invoke,

– ACTIVATE SUPPLEMENTARY SERVICE Invoke,
– DEACTIVATE SUPPLEMENTARY SERVICE Invoke,
ED 01
AAC020023800DS En 183 / 260
260
– INTERROGATE SUPPLEMENTARY SERVICE Invoke,
B.10.11 OB–VSH–SODBSH (09) – Number of operations refused due to ODB of SS management

Counter incremented on detection of refusal of an operation due to ODB of supplementary service man-
agement.
B.10.12 OB–VSH–SUSS (04) – Unstructured supplementary service operation success
Counter incremented on transmission of the following components:

– PROCESS UNSTRUCTURED SS DATA Result (phase 1) ,
– PROCESS UNSTRUCTURED SS REQUEST Result (phase 2) ,
– UNSTRUCTURED SS REQUEST Result (phase 2) ,
– UNSTRUCTURED SS NOTIFY Result (phase 2) ,
B.10.13 OB–VSH–USS (03) – Unstructured supplementary service operation requests
Counter incremented on reception of the following components:

– PROCESS UNSTRUCTURED SS DATA Invoke (phase 1)
– PROCESS UNSTRUCTURED SS REQUEST Invoke (phase 2)
– UNSTRUCTURED SS REQUEST Invoke (phase 2)
– UNSTRUCTURED SS NOTIFY Invoke (phase 2)
B.11 ––––––––––––––––––––– SM (Short Message Terminating) counters (298)

–
B.11.1 OB–VSM–MAREQ (04) – Ready for SM request (Memory available)
Counter incremented on sending the READY FOR SM Invoke phase 2 message to the HLR with alert
reason set to ”Memory available”.
B.11.2 OB–VSM–MSABS (01) – MS present (VMSC)
Counter incremented on sending the MS PRESENT (phase 1) message to the HLR.
B.11.3 OB–VSM–MSPRESREQ (02) – Ready for SM request (MS present)
Counter incremented on sending the READY FOR SM Invoke phase 2 message to the HLR with alert
reason set to ”MS present”.
B.11.4 OB–VSM–SMA (05) – Successful Ready for SM (Memory available)
Counter incremented on receipt of the READY FOR SM Result phase 2 message from the HLR due to
”Memory available” request.
B.11.5 OB–VSM–SMSPRES (03) – Successful Ready for SM (MS present)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on receipt of the READY FOR SM Result phase 2 message from the HLR due to
”MS present” request.
ED 01
AAC020023800DS En 184 / 260
260
B.12 –––––––––––––––––––– TC counters (206) ––––––––––––––––––––––––
B.12.1 OB–VTC–EMSRN–ABSSUB (04) – Failures for Roaming number Requests because of

Absent Subscriber
Counter incremented each time the PROVIDEROAMINGNUMBER Error is sent to the HLR with the
”AbsentSubscriber” error code.
B.12.2 OB–VTC–EMSRN–FNOTSU (05) – Failures for Roaming number Requests because of

Facility Not Supported
Counter incremented each time the PROVIDEROAMINGNUMBER Error is sent to the HLR with the Faci-
lityNotSupported error code.
B.12.3 OB–VTC–EMSRN–FNOTSU2 (06) – Failures for Roaming number Requests because of

Facility Not Supported (per E.164 PLMN address)
Counters, per E.164 PLMN address, incremented each time the PROVIDEROAMINGNUMBER Error is
sent to the HLR with the FacilityNotSupported error code. When no PLMN can be identified, this counter
is not incremented.
B.12.4 OB–VTC–MSRN–REJ (07) – Roaming number request reject for regulation cause
Counter incremented on rejection of PROVIDE ROAMING NUMBER for traffic regulation cause.
B.12.5 OB–VTC–REQ–BS (02) – Terminating call request
Counters, per basic service, incremented each time a SENDINFOFORINCOMMINGCALLSETUP

Invoke is received from RCF.
B.12.6 OB–VTC–REQ–MSRN (03) – Roaming number Requests
Counter incremented each time the PROVIDEROAMINGNUMBER Invoke is received from the HLR.
B.12.7 OB–VTC–RES–BS–MSRN (01) – Roaming Number Request Results
Counters, per basic service, incremented each time the PROVIDEROAMINGNUMBER Result is sent to
the HLR (Basic service derived from GSM–BC).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 185 / 260
260
APPENDIX C – HLR COUNTER IMPLEMENTATION

C.1 Warning.
transmitted at the application level but before any parameters content analysis which may further lead to
message rejection in the processing. As a consequence, incoming requests not transmitted in case of
overload detected by RTOS are not taken into account.
C.2 –––––––––––––––––––– CA counters (157) ––––––––––––––––––––
C.2.1 OB–HCA–USSN (03) – Number of Unstructured SS Notify messages
Counter indicating the total number of USS–N messages received from the SCF.
C.2.2 OB–HCA–USSNOK (04) – Number of Unstructured SS Notify
Counter indicating the total number of successful USS–N messages received from the SCF.
C.2.3 OB–HCA–USSR (01) – Number of Unstructured SS Request messages
Counter indicating the total number of USS–R messages received from the SCF.
C.2.4 OB–HCA–USSROK (02) – Number of Unstructured SS Request
Counter indicating the total number of successful USS–R messages received from the SCF.
C.2.5 OB–HCA–ATSI (05) – Number of ATSI Request
Counter indicating the total number of ATSI_I messages received from the SCF.
C.2.6 OB–HCA–ATSIACK (06) – Number of ATSI Result
Counter indicating the total number of ATSI_R messages returned by the HLR to the SCF.
C.2.7 OB–HCA–ATM (07) – Number of ATM Request
Counter indicating the total number of ATM_I messages received from the SCF.
C.2.8 OB–HCA–ATMACK (05) – Number of ATM Result

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter indicating the total number of ATM_R messages returned by the HLR to the SCF.
ED 01
AAC020023800DS En 186 / 260
260
C.3 –––––––––––––––––––– CC counters (197) ––––––––––––––––––––
C.3.1 OB–HCC–PCCBSMES (01) – Number of PCCBS related messages

Counter indicating the total number of CCBS related messages received or sent by the HLR (i.e. SSN of
CCBS–ASE used).
C.3.2 OB–HCC–PCCBSREQ (02) Number of PCCBS Request messages
Total number of CCBS activation requests, namely number of received CCBS Request messages.
C.4 –––––––––––––––––––– CCB counters (150) ––––––––––––––––––––
C.4.1 OB–HCCB–INVA (01) – Number of automatic invocations of CCBS on the A side
Counter incremented on receipt of the REMOTE USER FREE message from the HLR / DLE B.
C.4.2 OB–HCCB–INVB (02) – Number of automatic invocations of CCBS on the B side
Counter incremented on sending of the REMOTE USER FREE message to the HLR / OLE A.
C.4.3 OB–HCCB–RQA (03) – Number of successful CCBS calls on the A side
Counter incremented on receipt of the STATUS REPORT message from the VLR, with call outcome =
”success” and for the A side.
C.4.4 OB–HCCB–RQB (04) – Number of successful CCBS calls on the B side
Counter incremented on receipt of the STATUS REPORT message from the VLR, with call outcome =
”success” and for the B side.
C.5 –––––––––––––––––––– CCP counters (152) ––––––––––––––––––––––
C.5.1 OB–HCCP–ERA (03) – Erase CC entry received per supplementary service related to call
completion
Counter incremented on receipt of the ERASE CC ENTRY Invoke component from VLR related to call
C.5.2 OB–HCCP–ERA–F (04) – Erase CC entry failure per supplementary service related to call
completion
Counter incremented on sending of the ERASE CC ENTRY Error component to VLR related to call
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 187 / 260
260
C.5.3 OB–HCCP–REG (01) – Register CC entry received per supplementary service related to
call completion
Counter incremented on receipt of the REGISTER CC ENTRY Invoke component from VLR related to
call completion. There is one counter per supplementary service related to call completion.
C.5.4 OB–HCCP–REG–F (02) – Register CC entry failure per supplementary service related to
call completion
Counter incremented on sending of the REGISTER CC ENTRY Error component to VLR related to call
C.6 –––––––––––––––––––– CF counters (196) ––––––––––––––––––––
C.6.1 OB–HCF–SODBFTN (01) – Number of operations refused due to ODB of FTN registration,
OC or TC
Counter incremented on detection of refusal of an operation due to ODB of registration of forwarded–to

number, ODB of outgoing calls or ODB of incoming calls.
C.7 –––––––––––––––––––– CT counters (149) ––––––––––––––––––––
C.7.1 OB–HCT–ACTRMOD (01) – Number of Activate trace mode
Counter incremented on transmission of the ACTIVATE TRACE MODE Invoke component toward VLR.
C.7.2 OB–HCT–ACTRMODR (02) – Number of Activate trace mode results
Counter incremented on reception of the ACTIVATE TRACE MODE Result from VLR.
C.8 ––––––––––––––––––––– GP counters (135) –––––––––––––––––––
C.8.1 OB–HGP–CANLOCREQ (05) – Number of Cancel Location requests sent to SGSN
Counter incremented on transmission of the CANCEL LOCATION Invoke component to SGSN.
C.8.2 OB–HGP–CANLOCRES (06) – Number of Cancel Location results sent from SGSN
Counter incremented on reception of the CANCEL LOCATION Result component from SGSN.
C.8.3 OB–HGP–DSDREQ (07) – Delete subscriber data request sent to SGSN
Counter incremented on transmission of DELETE SUBSCRIBER DATA Invoke component to SGSN.
C.8.4 OB–HGP–DSDRES (08) – Delete subscriber data result from SGSN

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on reception of DELETE SUBSCRIBER DATA Result component from SGSN.
ED 01
AAC020023800DS En 188 / 260
260
C.8.5 OB–HGP–ISDREQ (03) – Number of attempted framed Insert Subscriber data procedures
towards an SGSN
Counters, per number of INSERT SUBSCRIBER DATA Invoke message sent in the procedure, increm-
ented at the end of the Update GPRS location procedure.

C.8.6 OB–HGP–ISDRES (04) – Number of successful framed Insert Subscriber data procedures
towards an SGSN
Counters, per number of INSERT SUBSCRIBER DATA Result message received in the procedure,
incremented at the end of the Update GPRS location procedure.
C.8.7 OB–HGP–MAREQ (20) – Ready for SM request from SGSN (Memory available)
Counter incremented on receipt of the READY FOR SM Invoke message from the SGSN with alert rea-
son set to ”Memory available”
C.8.8 OB–HGP–MSPRESREQ (18) – Ready for SM request from SGSN (MS present)
Counter incremented on receipt of the READY FOR SM Invoke message from the SGSN with alert rea-
son set to ”MS present”
C.8.9 OB–HGP–PDPRGREQ (22) – Send Routing Info for GPRS Invoke received from GGSN
Counter incremented on receipt of the Send Routing Info for GPRS Invoke message from the GGSN
C.8.10 OB–HGP–PDPRGRES (23) – Send Routing Info for GPRS Result sent to GGSN
Counter incremented on sending the Send Routing Info for GPRS Result message to the GGSN
C.8.11 OB–HGP–PDPFRREQ (24) –Failure Report Invoke received from GGSN
Counter incremented at receipt of the Failure Report Invoke message from the GGSN
C.8.12 OB–HGP–PDPFRRES (25) –Failure Report Result sent to GGSN
Counter incremented on sending of the Failure Report Result message to the GGSN
C.8.13 OB–HGP–PDPMSPRESREQ (26) –Note MS Present for GPRS Invoke sent to GGSN
Counter incremented on sending of the Note MS Present for GPRS Invoke message to the GGSN
C.8.14 OB–HGP–PDPMSPRESRES (27) –Note MS Present for GPRS Result from GGSN
Counter incremented at receipt of the Note MS Present for GPRS Result message from the GGSN
C.8.15 OB–HGP–PURGEMS (11) – Number of PurgeMS requests from SGSN

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on reception of the PURGE MS message from SGSN.
ED 01
AAC020023800DS En 189 / 260
260
C.8.16 OB–HGP–PURGEMSRES (12) – Number of PurgeMS result to SGSN
Counter incremented on transmission of the PURGE MS Result message to the SGSN.

C.8.17 OB–HGP–RGREQ (13) – Routing request from a SMS–GMSC supporting MT SMS over
GPRS
Counter incremented at the reception of the SEND ROUTING INFO.FOR SHORT MESSAGE from a
SMS–GMSC supporting MT SMS over GPRS.
C.8.18 OB–HGP–RGRES (14) – Successful routing sent to a SMS–GMSC supporting MT SMS

over GPRS
Counter incremented on sending the SEND ROUTING INFO. FOR SHORT MESSAGE Result to a SMS–
GMSC supporting MT SMS over GPRS.
C.8.19 OB–HGP–RGSGSN (15) – Successful routing with SGSN number
Counter incremented on sending the SEND ROUTING INFO. FOR SHORT MESSAGE Result with
SGSN number to a SMS–GMSC not supporting MT SMS over GPRS.
C.8.20 OB–HGP–RSMDREQ (16) – Report SM delivery status request from a SMS–GMSC sup-
porting MT SMS over GPRS
Counter incremented at the reception of REPORT SM DELIVERY STATUS Invoke message from a SMS–
GMSC supporting MT SMS over GPRS.
C.8.21 OB–HGP–RSMDRES (17) – Report SM delivery status result sent to a SMS–GMSC sup-
porting MT SMS over GPRS
Counter incremented on sending of REPORT SM DELIVERY STATUS Result message to a SMS–GMSC

supporting MT SMS over GPRS.
C.8.22 OB–HGP–SAISDREQ (09) – Number of stand–alone Insert Subscriber data request sent
to SGSN
Counter incremented on transmission of a stand–alone INSERT SUBSCRIBER DATA Invoke component

to SGSN.
C.8.23 OB–HGP–SAISDRES (10) – Number of stand–alone Insert Subscriber data success

received from SGSN
Counter incremented on reception of a stand–alone INSERT SUBSCRIBER DATA Result component

from SGSN.
C.8.24 OB–HGP–SGSNLOCREQ (01) – Number of Update GPRS Location requests received

from SGSN
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on reception of the UPDATE GPRS LOCATION Invoke component from SGSN.
ED 01
AAC020023800DS En 190 / 260
260
C.8.25 OB–HGP–SGSNLOCRES (02) – Number of Update GPRS Location results sent to SGSN
Counter incremented on transmission of the UPDATE GPRS LOCATION Result component to SGSN.
C.8.26 OB–HGP–SMA (21) – Successful Ready for SM sent to SGSN (Memory available)
Counter incremented on sending of the READY FOR SM Result message to the SGSN due to ”Memory
available” request.
C.8.27 OB–HGP–SMSPRES (19) – Successful Ready for SM sent to SGSN (MS present)
Counter incremented on sending of the READY FOR SM Result message to the SGSN due to ”MS pres-
ent” request.
C.9 –––––––––––––––––––––– LCS counters (162) –––––––––––––––––––––––––
C.9.1 OB–HLCS–SRIREQ (01) – Number of routing request for LCS
Counter incremented on reception of Send Routing Info For Location services (LCS) invoke message
from the GMLC.
C.9.1 OB–HLCS–SRIRES (02) – Number of successful routing for LCS
Counter incremented on sending of Send Routing Info For Location services (LCS) result message
to the GMLC.
C.10 ––––––––––––––––––––– LR counters (104) –––––––––––––––––––
C.10.1 OB–HLR–ATIREQ (18) – Number of ATI requests from the SCP
Counter incremented on reception of the ANY TIME INTERROGATION Invoke message from the SCP.
C.10.2 OB–HLR–ATIRES (19) – Number of ATI results sent to the SCP
Counter incremented on transmission of the ANY TIME INTERROGATION Result message to the SCP.
C.10.3 OB–HLR–CANLOCREQ (08) – Number of Cancel Location requests sent to VLR
Counter incremented on transmission of the CANCEL LOCATION Invoke component to VLR.
C.10.4 OB–HLR–CANLOCRES (09) – Number of Cancel Location results sent from VLR
Counter incremented on reception of the CANCEL LOCATION Result component from VLR.
C.10.5 OB–HLR–DSDREQ (10) – Delete subscriber data request
Counter incremented on transmission of DELETE SUBSCRIBER DATA Invoke component to VLR.

1AA 00014 0004 (9007) A4 – ALICE 04.10
C.10.6 OB–HLR–DSDRES (11) – Delete subscriber data success
Counter incremented on reception of DELETE SUBSCRIBER DATA Result component from VLR.
ED 01
AAC020023800DS En 191 / 260
260
C.10.7 OB–HLR–ISDREQ (06) – Number of framed Insert Subscriber data procedure request
sent to VLR
Counters, per number of INSERT SUBSCRIBER DATA Invoke message sent in the procedure, increm-
ented at the end of Update location or Restore data procedure.

C.10.8 OB–HLR–ISDRES (07) – Number of framed Insert Subscriber data procedure success
received from VLR
Counters, per number of INSERT SUBSCRIBER DATA Result message received in the procedure,
incremented at the end of Update location or Restore data procedure.
C.10.9 OB–HLR–PSIREQ (16) – Number of PSI requests to the VLR
Counter incremented on transmission of the PROVIDE SUBSCRIBER INFORMATION Invoke message

to the VLR.
C.10.10 OB–HLR–PSIRES (17) – Number of PSI results from VLR
Counter incremented on reception of the PROVIDE SUBSCRIBER INFORMATION Result message

from VLR.
C.10.11 OB–HLR–PURGEMS (01) – Number of PurgeMS requests from VLR
Counter incremented on reception of the PURGE MS message.
C.10.12 OB–HLR–RESTORE (02) – Number of RestoreData requests from VLR
Counter incremented on reception of the RESTORE DATA Invoke message.
C.10.13 OB–HLR–RESTORERES (14) – Number of RestoreData success to VLR
Counter incremented on transmission of the RESTORE DATA Result message to VLR.
C.10.14 OB–HLR–SAISDREQ (12) – Number of stand–alone Insert Subscriber data request sent
to VLR
Counter incremented on transmission of a stand–alone INSERT SUBSCRIBER DATA Invoke component

to VLR.
C.10.15 OB–HLR–SAISDRES (13) – Number of stand–alone Insert Subscriber data success

received from VLR
Counter incremented on reception of a stand–alone INSERT SUBSCRIBER DATA Result component

from VLR.
C.10.16 OB–HLR–SENDIMSI (03) – Number of IMSI requests from VLR

1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on reception of the SEND IMSI message.
ED 01
AAC020023800DS En 192 / 260
260
C.10.17 OB–HLR–SODBROAM (15) – Number of operations refused due to ODB of roaming
Counter incremented on detection of refusal of an operation due to ODB of roaming.

C.10.18 OB–HLR–VLRLOCREQ (04) – Number of Update Location requests received from VLR
Counter incremented on reception of the UPDATE LOCATION Invoke component from VLR.
C.10.19 OB–HLR–VLRLOCRES (05) – Number of Update Location results sent to VLR
Counter incremented on transmission of the UPDATE LOCATION Result component to VLR.
C.11 –––––––––––––––––––– OR counters (147) ––––––––––––––––––––––––
C.11.1 OB–HOR–SRIINV (01) – Number of SRI invoke with OR interrogation
Counter incremented by the HLR on receiving an SEND ROUTING INFO Invoke with OR interrogation.
C.11.2 OB–HOR–SRIRES (02) – Number of SRI result optimized
Counter incremented by the HLR when the call can be routed without contravening the charging require-
ments for optimal routeing (response with MSRN).
C.12 ––––––––––––––––––––– SA counters (188) –––––––––––––––––––
C.12.1 OB–HSA–SN (01) – Number of subscriber in the HLR database (globally)
Load counter incremented each time a subscriber is added in the HLR database and decremented each
time a subscriber is erased from this base.
C.12.2 OB–HSA–SNC (02) – Number of subscribers in the HLR database with access to the cir-
cuit domain at least
Load counters, per PLMN (MCC+MNC), incremented each time a subscriber with access to the circuit
domain is added in the HLR database or each time a subscriber obtains an access to the circuit domain
and decremented each time a subscriber with access to the circuit domain is erased from this base or each
time a subscriber has no more access to the circuit domain.
A subscriber with access to the circuit domain is a subscriber defined with a Network Access Mode (NAM)
set to ”non–GPRS” or ”both” value.
C.12.3 OB–HSA–SNP (03) – Number of subscribers in the HLR database with access to the
packet domain at least
Load counters, per PLMN (MCC+MNC), incremented each time a subscriber with access to the packet
domain is added in the HLR database or each time a subscriber obtains an access to the packet domain
and decremented each time a subscriber with access to the packet domain is erased from this base or
each time a subscriber has no more access to the packet domain.
1AA 00014 0004 (9007) A4 – ALICE 04.10
A subscriber with access to the packet domain is a subscriber defined with a Network Access Mode (NAM)
set to ”GPRS only” or ”both” value.
ED 01
AAC020023800DS En 193 / 260
260
C.13 ––––––––––––––––––––– SC counters (110) –––––––––––––––––––
C.13.1 OB–HSC–ENDTR (02) – Authentication Vectors request failures

Counter incremented on transmission of the SEND PARAMETERS Error component (MAP phase 1) cor-
responding to a request for Authentication Vectors or on reception of the SEND AUTHENTICATION INFO
Error component (MAP > = phase 2).
C.13.2 OB–HSC–SNDTR (01) – Authentication Vectors requests received
Counter incremented on reception of the SEND PARAMETERS Invoke component (MAP phase 1) where
it is used to request Authentication Vectors or on reception of the SEND AUTHENTICATION INFO Invoke
component (MAP>= phase 2).
C.13.3 OB–HSC–RAUREP (03) – Authentication_Failure_report received (UMTS only)
Counter incremented on reception of the AUTHENTICATION_Failure_Report Invoke component.
C.14 ––––––––––––––––––––– SH counters (130) –––––––––––––––––––
C.14.1 OB–HSH–AR (03) – Unstructured SS operations related to AR function request
Counter incremented on reception of PROCESSUNSTRUCTUREDSS Request operation related to AR

function.
C.14.2 OB–HSH–ENOSS (02) – Supplementary service operation failures
Counters, per supplementary service, incremented for a given service, determined by the SS CODE
parameter, on transmission of any one of the following components:
– REGISTER SUPPLEMENTARY SERVICE Error,
– ERASE SUPPLEMENTARY SERVICE Error,
– ACTIVATE SUPPLEMENTARY SERVICE Error,
– DEACTIVATE SUPPLEMENTARY SERVICE Error,
– INTERROGATE SUPPLEMENTARY SERVICE Error,
C.14.3 OB–HSH–NIUN (10) – Network initiated unstructured supplementary service notification

invoke
Counter incremented on emission of the following component towards the VLR:

– UNSTRUCTURED SS NOTIFY invoke
C.14.4 OB–HSH–NIUR (08) – Network initiated unstructured supplementary service request

invoke
Counter incremented on emission of the following component towards the VLR (except for the automatic
– UNSTRUCTURED SS REQUEST invoke
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 194 / 260
260
C.14.5 OB–HSH–REGPWREQ (05) – Register password request received
Counter incremented on reception of REGISTER PASSWORD Invoke message from the VLR.
C.14.6 OB–HSH–REGPWRES (06) – Register password result sent
Counter incremented on transmission of REGISTER PASSWORD Result message toward the VLR.
C.14.7 OB–HSH–SAR (04) – Unstructured SS operations related to AR function success
Counter incremented on transmission of PROCESSUNSTRUCTUREDSS Request success when

related to AR function.
C.14.8 OB–HSH–SNIUN (11) – Network initiated unstructured supplementary service notifica-

tion success
Counter incremented on reception of the following component from the VLR:

– UNSTRUCTURED SS NOTIFY result
C.14.9 OB–HSH–SNIUR (09) – Network initiated unstructured supplementary service request

success
Counter incremented on reception of the following component from the VLR (except for the automatic
– UNSTRUCTURED SS REQUEST result
C.14.10 OB–HSH–SNOSS (01) – Supplementary service operations
Counters, per supplementary service, incremented for a given service, determined by the SS CODE
parameter, on reception of any one of the following components:
– REGISTER SUPPLEMENTARY SERVICE Invoke,
– ERASE SUPPLEMENTARY SERVICE Invoke,
– ACTIVATE SUPPLEMENTARY SERVICE Invoke,
– DEACTIVATE SUPPLEMENTARY SERVICE Invoke,
– INTERROGATE SUPPLEMENTARY SERVICE Invoke,
C.14.11 OB–HSH–SODBSH (07) – Number of operation refused due to ODB of SS management
Counter incremented on detection of refusal of an operation due to ODB of supplementary service man-
agement.
C.15 ––––––––––––––––––––– SM counters (198) –––––––––––––––––––
C.15.1 OB–HSM–ALMSC (05) – Alert MSC
Counter incremented on sending the ALERT SC phase 1 message to the IWMSC.

1AA 00014 0004 (9007) A4 – ALICE 04.10
C.15.2 OB–HSM–ALREQ (08) – Alert MSC phase 2 request
Counter incremented on sending of the ALERT SC phase 2 message to the IWMSC.
ED 01
AAC020023800DS En 195 / 260
260
C.15.3 OB–HSM–ISC (14) – Inform service center
Counter incremented on sending of the INFORM SERVICE CENTER message to the GMSC.
C.15.4 OB–HSM–MAREQ (12) – Ready for SM request (Memory available)
Counter incremented on receipt of the READY FOR SM Invoke phase 2 message from the VLR with alert
reason set to ”Memory available”
C.15.5 OB–HSM–MSPRES (06) – MS present
Counter incremented at the reception of the MS PRESENT phase 1 message from the VLR.
C.15.6 OB–HSM–MSPRESREQ (10) – Ready for SM request (MS present)
Counter incremented on receipt of the READY FOR SM Invoke phase 2 message from the VLR with alert
reason set to ”MS present”.
C.15.7 OB–HSM–MWDREQ (03) – Message waiting data/Report SM delivery status request
Counter incremented at the reception of the MESSAGE WAITING DATA Invoke phase 1 message or
REPORT SM DELIVERY STATUS Invoke phase 2 message from the GMSC.
C.15.8 OB–HSM–REJ (07) – Number of Send Routing Info for SM requests not handled due to
HLR overload
Counter incremented on reception of a SEND ROUTING INFO FOR SM message not handled for traffic
regulation cause.
C.15.9 OB–HSM–RGFNUMENQ (15) – Number of Send Routing Info for SM requests used as a
MSC number enquiry
Counter incremented on reception of a SEND ROUTING INFO FOR SM Invoke used as a MSC number
enquiry (offered with functional option F_SMS_005).
C.15.10 OB–HSM–RGREQ (01) – Routing request
Counter incremented at the reception of the SEND ROUTING INFO.FOR SHORT MESSAGE from the
GMSC.
C.15.11 OB–HSM–SAL (09) – Alert MSC phase 2 successful
Counter incremented on receipt of the ALERT SC Result phase 2 message from the IWMSC.
C.15.12 OB–HSM–SMA (13) – Successful Ready for SM (Memory available)
Counter incremented on sending of the READY FOR SM Result phase 2 message to the VLR due to
”Memory available” request.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 196 / 260
260
C.15.13 OB–HSM–SMSPRES (11) – Successful Ready for SM (MS present)
Counter incremented on sending of the READY FOR SM Result phase 2 message to the VLR due to ”MS
present” request.
C.15.14 OB–HSM–SMWD (04) – successful message waiting data/report SM delivery status
Counter incremented on sending the MESSAGE WAITING DATA Result phase 1 message or REPORT
SM DELIVERY STATUS Result phase 2 message to the GMSC.
C.15.15 OB–HSM–SODBSMTC (16) – Number of SMSMT refused due to ODB of incoming calls.
Counter incremented on detection of refusal of an SMSMT due to ODB of incoming calls.
C.15.16 OB–HSM–SRG (02) – successful routing
Counter incremented on sending the SEND ROUTING INFO. FOR SHORT MESSAGE Result to the
GMSC.
C.16 ––––––––––––––––––––– SS counters (140) ––––––––––––––––––––
C.16.1 OB–HSS–SRETRI (01) – Number of reused triplets
Counter incremented on re–used of already used triplets.
C.16.2 OB–HSS–SRESYN (02) – Number of resynchronisations
Counter of resynchronisations. Counter incremented on reception of the SEND AUTHENTICATION INFO

invoke component with ”re–synchronisation info” parameter.
C.17 ––––––––––––––––––––– TC counters (106) –––––––––––––––––––
C.17.1 OB–HTC–EMSRN–ABSSUB (05) – Number of MSRN provision request failures because

of absent subscriber
Counters, per E.164 PLMN address, incremented on reception of the PROVIDE ROAMING NUMBER fail-
ure from the VLR with the ”AbsentSubscriber” error code.
C.17.2 OB–HTC–EMSRN–BUSSUB (08) – Number of MSRN provision request failures because

of MS busy
Counter incremented, according to F_TC_11 functional option, on reception of the PROVIDE ROAMING
NUMBER failure from the VLR with the ”ussd Busy” error code.
C.17.3 OB–HTC–EMSRN–FNOTSU (06) – Number of MSRN provision request failures because

of Facility not supported
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per E.164 PLMN address, incremented on reception of the PROVIDE ROAMING NUMBER fail-
ure from the VLR with the” FacilityNotSupported” error code.
ED 01
AAC020023800DS En 197 / 260
260
C.17.4 OB–HTC–ENIREA (02) – Failures of interrogation for call rerouting
Counter incremented on transmission of the SEND ROUTING INFO Error component.

C.17.5 OB–HTC–REJ (07) – Number of routing requests for TC not handled due to overload
Counter incremented on rejection of a SEND ROUTING INFO for TC message from the GMSC for traffic
regulation cause.
C.17.6 OB–HTC–REQ–MSRN (03) – Number of MSRN provision request
Counters, per E.164 PLMN address, incremented on transmission of the PROVIDE ROAMING NUMBER
Request to the VLR.
C.17.7 OB–HTC–RES–MSRN (04) – Number of MSRN provision request result
Counters, per E.164 PLMN address, incremented on reception of the PROVIDE ROAMING NUMBER
Result from the VLR.
C.17.8 OB–HTC–SNIREA (01) – Interrogations for call rerouting
Counter incremented on reception of the SEND ROUTING INFO Invoke component.

This counter is not invoked for the second SEND ROUTING INFO message in CAMEL case (parameter
Suppress TCSI present).
C.17.9 OB–HTC–SNIREA2 (10) – Interrogations for call rerouting
Counter incremented on reception of the SEND ROUTING INFO Invoke component in CAMEL case
(parameter Suppress TCSI present).
C.17.10 OB–HTC–SODBIC (09) – Number of TC refused due to ODB of incoming calls
Counter incremented on detection of refusal of an incoming call due to ODB of incoming calls.
C.18 ––––––––––––––––––––– TR counters (116) –––––––––––––––––––
C.18.1 OB–HTR–ANARES (01) – Number of translation analysis result observed
Counters, per observed translation result, incremented on each translator nvocation leading to this result.
C.19 ––––––––––––––––––––– VH counters (154) –––––––––––––––––––
C.19.1 OB–HVH–FALLBACK (01) – Number of MAP version fallbacks
Counter incremented when a TC–BEGIN message is answered with a TC–ABORT message due to ver-
1AA 00014 0004 (9007) A4 – ALICE 04.10
sion not supported for a given application context while there is a version supported by both entities for
this AC (this does not imply that a fallback procedure will occur).
ED 01
AAC020023800DS En 198 / 260
260
C.19.2 OB–HVH–FALLBACKUN (02) – Number of unexpected MAP version fallbacks
Counter incremented on reception of the TC_U_Abort message as answer to a previous TC_BEGIN mes-
sage, due to version not supported for a given application context by a foreign PLMN entity which was
supposed to support it (the spontaneous message WR_VH_301 is emitted).

C.19.3 OB–HVH–SRGI–REJ (03) – Number of Send routing informations reject for optimal rout-
ing
Counter incremented on TC_U_ABORT (MAP phase 2) or TC_REJECT cause ”unrecognized operation”

(MAP phase 1) sending for SEND ROUTING INFO Invoke component reception from a non HPMLN
GMSC.
C.19.4 OB–HVH–SRGISM–REJ (04) – Number of Send routing informations for SM reject for
optimal routing
Counter incremented on TC_U_ABORT (MAP phase 2) or TC_REJECT cause ”unrecognized operation”

(MAP phase 1) sending for SEND ROUTING INFO FOR SM Invoke component reception from a non
HPMLN GMSC.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 199 / 260
260
APPENDIX D OBSERVATION SCENARIOS
D.1 LR INTRA VLR

MS BSS RCP VLR HLR SCP
Location updating request
CC
OBS: FLR–SLU (/BSC) or FLR–SLUP (

or FLR–ATT ( /BSC)
OBS: VLR–SNI
OBS: VLR–ENI /BSC)
Security phase:
Authentication request
OBS: VSC –SDAUT(or UDAUT)
Authentication response
OBS: VSC –EDAUT(or EAUTH)
OR
Authentication failure
OBS: VSC –ERESYN or EAFAIL
Ciphering mode command
OBS: VSC –SNREAC(or NBCIPH)

Ciphering mode complete
OBS: VSC –ENREAC(or ECIPH)

OBS: VSC –EALGO(or ERALG)
TMSI reallocation command
OBS: VSC –SNREAT

TMSI reallocation complete
OBS: VSC –ENREAT
end of LR procedure:
Location updating accept
OBS: FLR –SLUR( /BSC)

MM–Event–Notification
OBS:VCA–MMEVENTN
CLEAR COMMAND
CLEAR COMPLETE
1AA 00014 0004 (9007) A4 – ALICE 04.10
DDC
CDC
ED 01
AAC020023800DS En 200 / 260
260
D.2 LR INTER VLR
MS BSS RCP VLR HLR

Mobile registration
Location updating request
CC
OBS: FLR –SLU ( /BSC) or FLR –SLUP (/BSC)

or FLR –ATT ( /BSC)
OBS: VLR –SNI
OBS: VLR –EXTORI–LAC,VLR –MS –UNKN
OBS: VLR –ENI
OBS: VLR –OLVLRUKN
BEGIN (I SEND PARAMETER)
END (RL SEND PARAMETER)
security phase –> see LR INTRA VLR
Mobile registration (continuation)
BEGIN (I UPDATE LOCATION)
OBS: VLR –UNAUTHVISIT OBS:HLR –VLRLOCREQ

OBS: VLR –HLRLOCREQ
OBS: VLR –HLRCONF –FLAG
R3: Cancel by the HLR –> see below
CONT(I INSERT SUBSCRIBER DATA)
OBS: VLR –ISDREQ OBS:HLR –ISDREQ

( /nb msg) ( /nb msg)
CONT (RL INSERT SUBSCRIBER DATA)
OBS: VLR –ISDRES OBS:HLR –ISDRES

( /nb msg) ( /nb msg)
END (RL UPDATE LOCATION)
OBS: VLR–HLRLOCRES OBS:HLR –VLRLOCRES

OBS: VLR–AUTHVISIT
OBS: VLR–ROAMNALL
end of LR procedure –> see LR INTRA VLR

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 201 / 260
260
MS BSS RCP VLR HLR
Interrogation by the new VLR

OBS: VLR–NWVLRSPREQ
BEGIN (I SEND PARAMETER)
ph.2: BEGIN (I SEND IDENTIFICATION)
OBS: VLR–OLVLRSPREQ
END (RL SEND PARAMETER)

ph.2: END (RL SEND IDENTIFICATION) .
OBS: VLR–OLVLRSPRES
OBS: VLR–NWVLRSPRES
R2: Cancel by the HLR –> see below
MS BSS RCP VLR HLR
Cancel by the HLR

OBS: HLR_CANLOCREQ
BEGIN (I CANCEL LOCATION)
OBS: VLR–CANLOC–HOM or
OBS: VLR–CANLOC–OTH
END (RL CANCEL LOCATION)
(1) OBS: HLR_CANLOCRES
Note 1: OBS: FLR–REL(/release domain) : release between location updating request reception and CDC
reception
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 202 / 260
260
D.3 OC
MS BSS SMIM RCP HLR SSP

Establishment (1)
CM service request
CCO
OBS: FOC–SAEMOB ( /BSC)
Security phase –> see LR INTRA VLR scenario
Setup
OBS: FOC–SETUP ( /BSC)

OBS: FOC–REQ–BS ( /Basic Service)
IN phase –> see IN services scenario
(1)
Call proceeding
OBS: FOC–CALPROC ( /BSC)
Note 1: after the SETUP, RCP (VLR) cheks the MS acces rights Basic Service, Call barring...): cases of
originating call barring are counted in FXX–SISS (ICBINV)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 203 / 260
260
Establishment (2)
BEGIN (I CREATE, I RETRIEVE)
CONT (RL RETRIEVE)
ASSIGNMENT REQUEST
OBS: FRM–OCASREQ ( /BSC)

ASSIGNMENT COMPLETE
OBS: FRM–OCASCOM ( /BSC)

OBS: FRM–POOL (2) ( /BSC)
if the called party is an MSISDN, HLR interrogation
BEGIN (I SEND ROUTING INFO)
OBS: FSW–SRIOC
OBS: HTC–SNIREA
OBS: HTC–ENIREA
END (RL SEND ROUTING INFO)
OBS: FSW–SRIOCRES
OBS: FSW–SRIOCCFU
OBS: FSW–SRIFWDVIOL
IN phase –> see IN services scenario (1)
Note 1: If the IN service invocation connects to a PLMN subscriber, the HLR interrogation is triggered
again and the IN service is called a second time with the new CalledPartyNumber.
Note 2: If circuit pool indicated in ASSIGNMENT COMPLETE is different from circuit pool in which the SSP
has selected the circuit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 204 / 260
260
Passing in ringing and conversation

CONT (I CREATE)
OBS: FSW–SAEVRF
CONT (I EVENT ACM)
Alerting
OBS: FOC–ALERT ( /BSC)

OBS: FOC–PROGRESS ( /BSC)
if Data Transmission call, request to the SMIM
IWF CON REQ
OBS: FDA–SIWFOCREQ ( /Basic Service)

IWF CON ACK
OBS: FDA–SIWF –OC ( /Basic Service) or

OBS: FDA–EACK–OC ( /Basic Service)
CONT (I EVENT ANM)
Connect
OBS: FOC–CONNECT ( /BSC) or

OBS: FOC–DIRCONNECT ( /BSC)
Connect ack
OBS: FOC–CONNACK ( /BSC)

(1)
Note 1: note that this counter can’t be compared per BSC to the OC number, since the BSC may have
changed (handover)
OBS: FOC–REL(/release domain): OC Call release

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 205 / 260
260
D.4 PURE GATEWAY

Establishment
BEGIN (I PROVIDE INSTRUCTION)
OBS: FSW –SNAEGMSC
OBS: FSW –SRIGTW

OBS: HTC–SNIREA
OBS: HTC–ENIREA
OBS: FSW –SRIGTWRES

OBS: FSW –SRIGTWCFU
OBS: FSW –SRIFWDVIOL
IN phase –> see IN services scenario (1)
CONT (I CREATE)
OBS: FSW –SAEGVRF
CONT (I GEN ECHO CANCELLER)
CONT (I EVENT ACM)
OBS: FSW –ACMGTW
Note 1: If the IN service invocation connects to a PLMN subscriber, the HLR interrogation is triggered
again and the IN service is called a second time with the new CalledPartyNumber.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 206 / 260
260
Called party hanging up
CONT (I EVENT SUSPEND)
CONT (I GEN SUSPEND)
CONT (I EVENT REL)
END (I FREE)
Calling party hanging up

CONT (I EVENT REL)
END (I FREE)
(1)
Note 1: OBS: FSW–GTWREL (/release domain): Gateway Call release

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 207 / 260
260
D.5 GATEWAY + TC

Establishment (1)
(1)
BEGIN (I PROVIDE ROAMING NUMBER)
OBS: HTC –REQ –MSRN

( /Mobile Country code)
OBS: VTC –REQ –MSRN
END (RL PROVIDE ROAMING NUMBER)
OBS: VTC –RES –BS –MSRN ( /Basic Service)

OBS: HTC –RES –MSRN
( /Mobile Country code)
OBS: VTC –REQ –BS ( /Basic Service)

OBS: FTC–SNGWTC: GTW call which becomes TC

PAGING
OBS: VPG–PAGING or VPG –SEARCH

OBS: FPG–SRP (repetition)
OBS: FPG –ERP (no MS response)
Paging response
OBS: VPG–PAGSRCHRES
OBS: FPG–PAGEIMSI
CCO
Note : If the IN service invocation connects to a PLMN subscriber, the HLR interrogation is triggered again
and the IN service is called a second time with the new CalledPartyNumber.
Note 1: see PURE GATEWAY scenario

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 208 / 260
260
Establishment (2)
Setup
Call confirmed
OBS: FTC –CALCONF ( /BSC)

OBS: FTC –CALCONF–BS ( /BS)
CONT (I CREATE, I RETRIEVE)
CONT (RL RETRIEVE)
ASSIGNMENT REQUEST
OBS: FRM –TCASREQ ( /BSC)

ASSIGNMENT COMPLETE
OBS: FRM –TCASCOM ( /BSC)

OBS: FRM–POOL (1) ( /BSC)
Note 1: If circuit pool indicated in ASSIGNMENT COMPLETE is different from circuit pool in which the SSP
has selected the circuit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 209 / 260
260
Ringing phase and conversation phase

Alert
OBS: FTC –ALERT ( /BSC)

CONT (I GEN ACM, I SEND RECEIVE)
Connect
CONT (I JOIN, I GEN ANM)
Connect acknowledgement
OBS: FTC –CONNECT ( /BSC)
if DATA transmission call, connection request to the SMIM
IWF CON REQ
OBS: FDA –SIWFTCREQ ( /Basic Service)

IWF CON ACK
OBS: FDA –SIWF–TC or FDA –EACK –TC ( /Basic Service)

IWF CON REQ
(1)
Release –> see OC scenario
Note 1: OBS: FTC–REL (/release domain) : TC call release

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 210 / 260
260
D.6 TC

Establishment
OBS: HTC –REQ–MSRN

( /Country code)
OBS: VTC–REQ –MSRN
OBS: VTC–RES–BS –MSRN ( /Basic Service)

OBS: HTC–RES–MSRN
( /Country code)
OBS: FSW–SNAEMSC
PAGING
Establishment (cont.) –> idem Gateway + TC

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 211 / 260
260
D.7 GATEWAY + TC TO MS CONDITIONALY FORWARDED (no paging response)

Establishment: beginning idem Gateway + TC
OBS: HTC–REQ –MSRN

( /Country code)
OBS: VTC–REQ–MSRN
OBS: VTC –RES –BS –MSRN ( /Basic Service)

OBS: HTC–RES –MSRN
( /Country code)

PAGING
OBS: FPG –ERP or FPG –BUSYMS

OBS: FXX –SISS (CFNRINV) cf on no reply
OBS: FXX –SISS (CFBUINV) cf on MS busy
if the forwarding call is an MSISDN, HLR interrogation
OBS: FSW–SRICFMSC
OBS: FSW –SRICFRES

OBS: FSW –SRIFWDVIOL
CONT (I CREATE, I JOIN)
OBS: FSW –SARVRF

CONT (I EVENT ACM)
Continuation –> Idem Gateway

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 212 / 260
260
D.8 GATEWAY + TC TO MS CONDITIONALY FORWARDED (subs not reachable)

Establishment: beginning and security phase : idem Gateway + TC
Setup
Call confirmed
OBS: FTC –CALCONF ( /BSC)

OBS: FTC –CALCONF–BS ( /BS)
CONT (I CREATE, I RETRIEVE)
CONT (RL RETRIEVE)
ASSIGNMENT REQUEST
ASSIGNMENT FaiLuRe
OBS: FXX –SISS (CFININV)
END (I FREE)
Continuation –> Idem GWT + TC to MS CF (no paging response)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 213 / 260
260
D.9 GSM to GSM HANDOVER (GSM only)
D.9.1 INTRA–MSC HANDOVER

MS BSC1 RCP SSP BSC2
Intra–MSC handover: preliminary phase
HO_REQuired
OBS: FHO–SDTR1 ( /origin BSC)

OBS: FHO–SDTR2 ( /origin BSC) if no HO running for that MS
OBS: FHO–SDTR3 ( /origin BSC) if cell list updated
OBS: FHO–SDTR4 ( /origin BSC) if repeated HO req
OBS: FHO–SDTR5 ( /origin BSC) if HO req on SDCCH
OBS: FHO–SDTR6 ( /origin BSC) if cause Switch circuit pool
CREATE REtrieve
Retrieve Result
HO_REQUest
OBS: FHO –SHOAREQ ( /target BSC), reselections not counted
HO_REQuest ACK
OBS: FHO–SHOAREQACK ( /target BSC)

OBS: FHO–SHORSEL ( /target BSC) reselections for all HO types
OBS: FRM–POOL (1) ( /target BSC)
Note 1: If the circuit pool indicated in HANDOVER REQUEST ACKNOWLEDGE is different from the circuit
pool in which the SSP has selected the circuit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 214 / 260
260
MS BSC1 RCP SSP BSC2
Intra–MSC Handover: execution

HO_CoMmanD
OBS: FHO–SHOC ( /origin BSC)

HO_CoMmanD
HO_COMplete
HO_COMplete
OBS: FHO –SHOACOMP success ( /target BSC)

OBS: FHO –SHOIAMSC success ( /origin BSC)
OBS: FHO –EHOFFM return on old channel ( /origin BSC)
OBS: FHO –EHOIAMSC failures with lost mobile ( /origin BSC)
(1)
CLEAR_CoMmanD
CLEAR_COMplete
FREE old leg
Note 1:
counters SHOC, SHOACOMP, EHOFFM and EHOIAMSC are counted per couple (Origin BSC, tar-
get BSC)
OBS: FHO–SHOREL counts globally all intra–MSC Handover releases, per release domain,
between HO_ReQuireD reception and HO_COMPlete reception
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 215 / 260
260
D.9.2 INTER–MSC HANDOVER
MS BSCA RCPA SSPA RCPB SSPB BSCB HLR

Inter–MSC handover: preliminary phase
HO_REQuired
(1)
ph1 : PERForm_HO_Invoke
ph2 : PREPare_HO_Invoke
OBS: FHO–SHOIPIVA (/Target LAC)

OBS: FHO–SHOIPIVB (/Origin MSC)
CREATE REtrieve
Retrieve Result
OBS: FHO–SHOBREQ (/target BSC)
HO_REQUest
HO_REQuest ACK
OBS: FHO–SHOBREQACK (/target BSC)
OBS: FHO–SHORSEL (/target BSC)
OBS: FRM–POOL (2) ( /target BSC)
ph1 : PERForm_HO_Result
ph2 : PREPare_HO_Result
OBS: FHO–SHOIPHORA (/Target LAC)
Note 1: OBS: see Intra–MSC handover
Note 2: If the circuit pool indicated in HANDOVER REQUEST ACKNOWLEDGE is different from the circuit
pool in which the SSP has selected the circuit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 216 / 260
260
Inter–MSC handover: execution (1)

CREATE (HO leg)
GEN SIG (EchoCan Off)
MIF
PROV_INS
DETACH
ATTACH
GENSIG (ACM)
OBS: FHO –SHOACMB ( /Origin MSC)
JOIN (No immed exec)
ACM
EVENT (ACM)
HO_CoMmanD
OBS: FHO –SHOCIR ( /origin BSC)

HO_CoMmanD
JOIN (Split)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 217 / 260
260
Inter–MSC handover: execution (2)

HO_COMplete
HO_COMplete
OBS: FHO –SHOIMSCB ( /Target BSC)

(1)
Send End SIgnal Invoke
OBS: FHO –SHOIMSCA ( /origin BSC)

OBS: FHO –SHOISESA ( /Target LAC)
OBS: FHO –EHOIRMSC ( /origin BSC) failure (mobile lost)
OBS: FHO –EHOFFMA ( /origin BSC) return on old channel
(2)
GEN SIG (ANM)
ANM (RIU)
EVENT (ANM)
CLEAR_CoMmanD
CLEAR_COMplete
FREE old leg
Note 1: OBS: FHO–SHORELB counts globally all inter–MSC handover releases, per release domain,
between Perf–HO–Inv reception and Send End SIgnal Invoke emission, in the TARGET MSC
Note 2: counters SHOCIR, SHOIMSCA, EHOFFMA and EHOIRMSC are counted per couple (Origin
BSC, Target LAC)
OBS: FHO–SHORELA counts globally all inter–MSC handover releases, per release domain,
between HO_ReQuireD reception and Send End SIgnal Invoke reception, in the CONTROLLING
MSC
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 218 / 260
260
D.9.3 SUBSEQUENT HANDOVER (A –> B –> C)
MS BSCB RCPB SSPB RCPA SSPA RCPC SSPC BSCC

Subsequent handover B –> C: preliminary phase
HO_REQuired
(1)
ph1 : PERForm_SUBS_HO_Invoke
ph2 : PREPare_SUBS_HO_Invoke
OBS: FHO–SHOSPSIB (/Target LAC)

OBS: FHO–SHOSPSIA (global)
ph1 : PERForm_HO_Invoke
ph2 : PREPare_HO_Invoke
(2)
CREATE REtrieve
Retrieve Result
(2)
HO_REQUest
HO_REQuest ACK
(2)
ph1 : PERForm_HO_Result
ph2 : PREPare_HO_Result
OBS: FHO–SHOSPHORA (global)
Note 1: OBS: see intra–msc handover
Note 2: RCPC is in same situation as RCPB in inter–MSC case (TARGET). Same counters apply.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 219 / 260
260
Subsequent handover B> C: execution (1)

CREATE (HO leg)
MIF
PROV_INS
DETACH
ATTACH
GENSIG (ACM)
(1)
JOIN (No immed exec)
GENSIG (EchoCan Off)
ACM
EVENT (ACM)
ph1 : PERForm_SUBS_HO_RESult
ph2 : PREPare_SUBS_HO_RESult
OBS: FHO–SHOSPSHORA (global)

JOIN (Split)
HO_CoMmanD
OBS: FHO–SHOCS (/Origin BSC)

HO_CoMmanD
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 220 / 260
260
Subsequent handover B> C: execution (2)
HO_DETect
HO_COMplete
HO_COMplete
(1)
Send End SIgnal Invoke
OBS: FHO–SHOSMSCA (global)

SEND_END_SIGNAL_RESult
(2)
OBS: FHO–SHOSSERB ( /Target LAC)
OBS: FHO–SHOSMSCB ( /Origin BSC)
OBS: FHO–EHOFFMB ( /Origin BSC) if return on old channel
OBS: FHO–EHOSMSCB ( /Origin BSC) if mobile lost
(3)
CLEAR_CoMmanD
CLEAR_COMplete
FREE old leg
Note 2: OBS: FHO–SHOSRELA counts globally all subsequent handover releases, per release domain,
between PERF–SUBS–HO–I reception and Send End SIgnal Result emission, in the CONTROLLING
MSC
Note 3: counters SHOCS, SHOSMSCB, EHOFFMB, EHOSMSCB are counted per couple (Origin BSC,
Target LAC)
OBS: FHO–SHOSRELB counts globally all subsequent handover releases, per release domain,
between HO_REQuired reception and Send End SIgnal Result reception in the SERVING MSC
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 221 / 260
260
D.9.4 RETURN SUBSEQUENT HANDOVER (A–>B, B–>A)

Return subsequent handover, preliminary phase
HO_REQuired
(1)
ph1 : PERForm_SUBSequent_HO_Invoke
ph2 : PREPare_SUBSequent_HO_Invoke
(1)
OBS: FHO–SHORPSIA (/serving MSC)
CREATE REtrieve
Retrieve Result
OBS: FHO–SHOSAREQ (/target BSC)

HO_REQUest
HO_REQuest ACK
(2)
ph1 : PERForm_SUBSequent_HO_Result
ph2 : PREPare_SUBSequent_HO_Result
OBS: FHO–SHOSSPHORA (global)

(1)
Note 1: RCPB is in same situation as RCPB in subsequent HO case (SERVING), same counters apply
Note 2: RCPB is in same situation as RCPB in inter–MSC case (TARGET). Same counters apply.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 222 / 260
260
Return subsequent handover, execution

HO_CoMmanD
(1)
HO_CoMmanD
HO_COMplete
HO_COMplete
Send End SIgnal Result
OBS: FHO –SHORMSCA ( /serving MSC)
(2)
(1)
CLEAR_CoMmanD
CLEAR_COMplete
FREE old leg
Note 1: RCPB is in same situation as RCPB in subsequent HO case (SERVING), same counters apply
Note 2: OBS: FHO–SHOSRELA counts globally all return subsequent HO releases, per release domain,
between Perf–SUBS–HO–I reception and Send_End_Signal Result sending, in the CONTROLLING
MSC.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 223 / 260
260
D.10 SRNS relocation (UMTS only)
These scenario apply to SRNS relocation but, for MSC/VLR, apply also to hard handover with switching
to the Core Network (configuration without Iur interface).
D.10.1 Name of counters
Counters related to SRNS relocation are globally named FRE–Sxxxxxx.

More precisely, counters specific to intra–MSC relocation ends by ”A” letter, counters specific to inter–
MSC relocation ends by ”E” letter, counters specific to inter–MSC subsequent relocation ends by ”S” letter
and counters specific to inter–MSC subsequent return relocation ends by ”R” letter.
An inter–MSC counter (”E” letter) may be used also for inter–MSC subsequent and subsequent return
relocation if no specific counter exists. An inter–MSC subsequent counter (”S” letter) may be used also
for inter–MSC subsequent return relocation if no specific counter exists.
Counters specific to UMTS to GSM handovers are globally named FRE–S2Gxxxxxx.
Counters specific to GSM to UMTS handovers are globally named FHO–S3Gxxxxxx.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 224 / 260
260
D.10.2 Intra MSC SRNS relocation
Source Target
RNC RNC
UE RNCA RCP SSP RNCB

Relocation
Relocation required Preparation
OBS: FRE–SRERQ (01)

OBS: FRE–SRERQA (05)
Relocation
resource
Relocation request allocation
OBS: FRE–SREREQA (03)
ALCAP Iu data transport bearer set up
Relocation request ack
OBS: FRE–SREREQKA (04)
Relocation command
OBS: FRE–SRECOM (02)
OBS: FRE–SRECOMA (07)
Relocation commit
Relocation
Relocation detect execution
switch user plane from source RNC to target RNC

Relocation complete
OBS: FRE–SRECOMPA (08)
Iu release command
ALCAP Iu data transport bearer release
Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 225 / 260
260
a) The observation of the relocation preparation procedure is made by a couple of counters per source
RNC:
• FRE–SRERQ: Number of relocation required (all type of relocation)
• FRE–SRECOM: Successfull end of the procedure: number of relocation command (all type of
relocation)
and also by a counter per (source RNC, target RNC):

• FRE–SRERQA: Number of relocation required (intra–MSC)
which may be compared with counters defined in d ).
b) The observation of the relocation resource allocation procedure is made by a couple of counters per
target RNC:
• FRE–SREREQA: Number of relocation request (intra–MSC)
• FRE–SREREQKA: Successfull end of the procedure: number of relocation request ack (intra–
MSC)
The relocation failures messages are not counted, they are considered as belonging to unsuccessful
end of this procedure.
c) The observation of relocation cancel procedure is made by the counter per (source RNC, target
RNC):
• FRE–SRECANA: Number of relocation cancel (intra–MSC)
The value of this counter has to be compared with the value of number of relocation required counter.
N.B. The relocation cancel message may be received by the RCP from the source RNC
at any time between the relocation required and the completion of SRNS relocation.
d) The observation of relocation procedure is made by a couple of counters per (source RNC, target
RNC):
• FRE–SRECOMA: Number of relocation command (intra–MSC)
• FRE–SRECOMPA: Successfull end of the procedure: number of relocation complete (intra–
MSC)
e) FRE–SRERA counts globally all intra–MSC SRNS relocation releases, per release domain, between
Relocation required and Relocation complete.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 226 / 260
260
D.10.3 Inter MSC (A –> B) SRNS relocation
Controlling MSC Target MSC

UE RNCA RCPA SSPA RCPB SSPB RNCB

Relocation required
Prepare HO (Relocation request)
OBS: FRE–SPREPE (10)

OBS: FRE–SPREPTE (15)
Relocation request
OBS: FRE–SREREQE (16)

OBS: FRE–SREREQKE (17)

Prepare HO (Relocation request ack)
Create HO leg
IAM
Join HO leg with new MS leg

ACM OBS: FRE–SACMTE (18)
Relocation command
OBS: FRE–SRECOME (12)
Relocation commit
Relocation detect
Process access signal (Relocation detect)
Join HO leg with network leg

ANM
Relocation complete
OBS: FRE–SRECOMPTE (19)

Send End Signal (Relocation complete)
OBS: FRE–SRECOMPE (13)
Iu release command

Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 227 / 260
260
D.10.3.1Observation in Controlling MSC
RNC:

relocation)
• FHO–SPREPE: Number of prepare Handover (relocation request)
which may be compared with counters defined in c ).
b) The observation of relocation cancel procedure is made by the counter per (source RNC, target
RNC):
• FRE–SRECANE: Number of relocation cancel (inter–MSC)
The value of this counter has to be compared with the value of number of prepare handover counter.
c) The observation of relocation procedure is made by a couple of counters per (source RNC, target
RNC):
• FRE–SRECOME: Number of relocation command (inter–MSC)
• FRE–SRECOMPE: Successfull end of the procedure: number of Send End Signal (relocation
complete) (inter–MSC)
d) FRE–SRERCE counts globally all inter–MSC SRNS relocation releases at controlling MSC, per
release domain, between Relocation required and Send End Signal (relocation complete).
D.10.3.2Observation in target MSC
a) The observation of the relocation preparation procedure is made by a couple of counters per control-
ling MSC:
• FRE–SPREPTE: Number of prepare Handover (relocation request)
• FRE–SACMTE: Number of ACM
b) The observation of the relocation resource allocation procedure is made by a couple of counters per
target RNC:
• FRE–SREREQE: Number of relocation request (inter–MSC)
• FRE–SREREQKE: Successfull end of the procedure: number of relocation request ack (inter–
MSC)
c) The observation of relocation procedure is made by a counter per controlling MSC:

• FRE–SRECOMPTE: Successfull end of the procedure: number of relocation complete (inter–
MSC)
The value of this counter may be compared with counters defined in a ).
d) FRE–SRERTE counts globally all inter–MSC SRNS relocation releases at target MSC, per release
domain, between Preparation HO (relocation request) and Send End Signal (relocation complete).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 228 / 260
260
D.10.4 Subsequent inter MSC SRNS relocation – three MSC involved (A–> B –> C)
Serving MSC Controlling MSC Target MSC

UE RNCB RCPB SSPB RCPA SSPA RCPC SSPC RNCC

Relocation required
Prepare subsequent HO (Relocation request)
OBS: FRE–SPREPSS (24)

OBS: FRE–SPREPCS (21)
Prepare HO (Relocation request)

Relocation request

Prepare HO (Relocation request ack)
Create HO leg
IAM
OBS: FRE–SACMTE (18)

ACM
Prepare subsequent HO (Relocation request ack)
Relocation command
OBS: FRE–SRECOMS (26)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 229 / 260
260
UE RNCB RCPB SSPB RCPA SSPA RCPC SSPC RNCC

Relocation commit
Relocation detect
Process access signal (Relocation detect)

ANM
Relocation complete

Send End Signal (Relocation complete)
OBS: FRE–SRECOMPCS (22)
Free old HO leg
Send End Signal result
OBS: FRE–SRECOMPS (27)

Iu release command

Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 230 / 260
260
a) The observation of relocation procedure is made by a couple of counters:

• FRE–SPREPCS: Number of prepare Handover
• FRE–SRECOMPCS: Successfull end of the procedure: number of Send End Signal (relocation
complete)
b) FRE–SRERCS counts globally all inter–MSC subsequent SRNS relocation releases at controlling
MSC , per release domain, between Prepare subsequent HO (relocation request) and Send end sig-
nal result.
D.10.4.2Observation in serving MSC
RNC:
relocation)
• FHO–SPREPSS: Number of prepare subsequent Handover (relocation request)
which may be compared with counters defined in c ).
RNC):
• FRE–SRECANS: Number of relocation cancel (inter–MSC subsequent)
The value of this counter has to be compared with the value of number of prepare subsequent hand-
over counter.
c) The observation of relocation procedure is made by a couple of counters per (source RNC, target
RNC):
• FRE–SRECOMS: Number of relocation command (inter–MSC subsequent)
• FRE–SRECOMPS: Successfull end of the procedure: number of Send End Signal result (inter–
MSC subsequent)
d) FRE–SRERSS counts globally all inter–MSC SRNS relocation releases at serving MSC, per release
domain, between Relocation required and Send End Signal result.
Same as for inter–MSC relocation § D.10.3.2.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 231 / 260
260
D.10.5 Return subsequent inter MSC SRNS relocation – two MSC involved (A–> B –> A)
Serving MSC Controlling/target MSC

UE RNCB RCPB SSPB RCPA SSPA RNCA

Relocation required
Prepare subsequent HO (Relocation request)
OBS: FRE–SPREPSS (24)

Relocation request
OBS: FRE–SREREQR (29)

OBS: FRE–SREREQKR (30)
Prepare subsequent HO (Relocation request ack)
Relocation command
OBS: FRE–SRECOMS (26)
Relocation commit
Relocation detect
switch user plane from source RNC to target RNC
Relocation complete
OBS: FRE–SRECOMPR (31)
Free old HO leg

OBS: FRE–SRECOMPS (27)
Iu release command

Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 232 / 260
260
D.10.5.1Observation in Controlling/target MSC
a) The observation of the relocation resource allocation procedure is made by a couple of counters per
target RNC:
• FRE–SREREQR: Number of relocation request (inter–MSC subsequent return)

• FRE–SREREQKR: Successfull end of the procedure: number of relocation request ack (inter–
MSC subsequent return)
b) The observation of relocation procedure is made by a counter per target RNC:

• FRE–SRECOMPR: Successfull end of the procedure: number of relocation complete (inter–
MSC subsequent return)
The value of this counter may be compared with counters defined in a ).
c) FRE–SRERCS counts globally all inter–MSC subsequent SRNS relocation releases at controlling
MSC, per release domain, between Preparation subsequent HO (relocation request) and Send End
Signal result.
Same as for inter–MSC subsequent relocation § D.10.4.2

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 233 / 260
260
D.11 UMTS to GSM handover
D.11.1 Intra MSC UTRAN to GSM handover

Source
RNC
UE SRNC RCP SSP BSC

Handover
Relocation required Preparation
resource
OBS: FRE–S2GRERQA (32) allocation
create new MS leg
Handover request
OBS: FHO–SHOAREQ (30716)
OBS: FHO–SHOAREQACK (30727)
Relocation command
OBS: FRE–S2GCOMA (34)
handover to GSM Handover

Handover detect
switch user plane from source RNC to target BSC

handover complete
OBS: FRE–S2GCOMPA (35)
Iu release command
Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 234 / 260
260
a) The observation of the handover preparation procedure is made by a couple of counters per source
RNC:
• FRE–SRERQ: Number of relocation required (all type of handover)
handover)
Same counters as for SRNS relocation.

In addition a counter per (source RNC, target BSC)
• FRE–S2GRERQA: Number of relocation required (intra–MSC)
may be compared with counters defined in d ).
b) The observation of the resource allocation procedure is made by a couple of counters per target BSC:
• FHO–SHOAREQ: Number of handover request (intra–MSC handover)
• FHO–SHOAREQACK: Successfull end of the procedure: number of handover request ack
(intra–MSC handover)
Same counters as for GSM–GSM handover.
c) The observation of relocation cancel procedure is made by the counter per (source RNC, target
BSC):
• FRE–S2GRECANA: Number of relocation cancel (intra–MSC)
The value of this counter has to be compared with the value of number of relocation required counter.
at any time between the relocation required and the completion of inter system hand-
over.
d) The observation of handover procedure is made by a couple of counters per (source RNC, target
BSC):
• FRE–S2GCOMA: Number of relocation command (intra–MSC handover)
• FRE–S2GCOMPA: Successfull end of the procedure: number of handover complete (intra–
MSC handover)
e) FRE–S2GRERA counts globally all intra–MSC handover from UMTS to GSM releases, per release
domain, between Relocation required and Handover complete.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 235 / 260
260
D.11.2 Inter MSC UTRAN to GSM handover

UE RNCA RCPA SSPA RCPB SSPB BSCB

Relocation required

Prepare HO (Handover request)
OBS: FRE–S2GPREPE (37) or FRE–S2GPREPEE (47)

Handover request
Handover request ack
Prepare HO (handover request ack)
Create HO leg
IAM

ACM
Relocation command

OBS: FRE–S2GCOME (39) or FRE–S2GCOMEE (49)
handover to GSM
Handover detect
Process access signal (Handover detect)

ANM
Handover complete
Send End Signal (handover complete)
OBS: FRE–S2GCOMPE (40) or FRE–S2GCOMPEE (50)

Iu release command

Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 236 / 260
260
RNC:

handover)
In addition a counter per (source RNC, target LAC)
• FRE–S2GPREPE: Number of prepare handover (handover request) (inter–MSC) (intra–
PLMN)
may be compared with counters defined in c ).
In case of inter–PLMN handover, FRE–S2GPREPE is replaced by a counter per (source RNC, target
MSC)
• FRE–S2GPREPEE: Number of prepare handover (handover request) (inter–MSC) (inter–
PLMN)
LAC):
• FRE–S2GRECANE: Number of relocation cancel (inter–MSC) (intra–PLMN)
The value of this counter has to be compared with the value of number of prepare handover counter.
In case of inter–PLMN handover, FRE–S2GRECANE is replaced by a counter per (source RNC, tar-
get MSC)
• FRE–S2GRECANEE: Number of relocation cancel (inter–MSC) (inter–PLMN)
c) The observation of handover procedure is made by a couple of counters per (source RNC, target
LAC):
• FRE–S2GCOME: Number of relocation command (inter–MSC handover) (intra–PLMN)
• FRE–S2GCOMPE: Successfull end of the procedure: number of handover complete (inter–
MSC handover) (intra–PLMN)
In case of inter–PLMN handover, FRE–S2GCOME and FRE–S2GCOMPE are replaced by counters
per (source RNC, target MSC)
• FRE–S2GCOMEE: Number of relocation command (inter–MSC handover) (inter–PLMN)
• FRE–S2GCOMPEE: Successfull end of the procedure: number of handover complete (inter–
MSC handover) (inter–PLMN)
d) FRE–S2GRERE counts globally all inter–MSC handover from UMTS to GSM releases, per release
domain, between Relocation required and Send End Signal (Handover complete).
Same as for GSM–GSM inter–MSC handover, see § D.9.2. The counters are not given in the scenario
above.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 237 / 260
260
D.11.3 Subsequent inter MSC UTRAN to GSM handover – three MSC involved

UE RNCB RCPB SSPB RCPA SSPA RCPC SSPC BSCC

Relocation required
Prepare subsequent HO (Handover request)
OBS: FRE–S2GPREPSS (42) or FRE–S2GPREPSSE (51)
Handover request
Prepare HO (Handover request ack)
Create HO leg
IAM

ACM
Prepare subsequent HO (Handover request ack)
Relocation command
OBS: SRE–SRECOM (02)
OBS: SRE–S2GCOMS (44) or SRE–S2GCOMSE (53)
handover to GSM
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 238 / 260
260
UE RNCB RCPB SSPB RCPA SSPA RCPC SSPC BSCC

Handover detect

ANM
Handover complete
Send End Signal (Handover complete)
Free old HO leg
OBS: FRE–S2GCOMPS (45) or FRE–S2GCOMPSE (54)

Iu release command

Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 239 / 260
260
Same as for GSM–GSM inter–MSC subsequent handover, see § D.9.3.


RNC:
handover)
In addition a counter per (source RNC, target LAC)
• FRE–S2GPREPSS: Number of prepare subsequent handover (inter–MSC subsequent)
In case of inter–PLMN handover, FRE–S2GPREPSS is replaced by a counter per (source RNC, tar-
get MSC)
• FRE–S2GPREPSSE: Number of prepare handover (handover request) (inter–MSC subse-
quent) (inter–PLMN)
LAC):
• FRE–S2GRECANS: Number of relocation cancel (inter–MSC subsequent)
The value of this counter has to be compared with the value of number of prepare subsequent hand-
over counter.
In case of inter–PLMN handover, FRE–S2GRECANS is replaced by a counter per (source RNC, tar-
get MSC)
• FRE–S2GRECANSE: Number of relocation cancel (inter–MSC subsequent) (inter–PLMN)
c) The observation of handover procedure is made by a couple of counters per (source RNC, target
LAC):
• FRE–S2GCOMS: Number of relocation command (inter–MSC subsequent)
• FRE–S2GCOMPS: Successfull end of the procedure: number of handover complete (inter–
MSC subsequent)
In case of inter–PLMN handover, FRE–S2GCOMS and FRE–S2GCOMPS are replaced by counters
per (source RNC, target MSC)
• FRE–S2GCOMSE: Number of relocation command (inter–MSC subsequent handover) (inter–
PLMN)
• FRE–S2GCOMPSE: Successfull end of the procedure: number of handover complete (inter–
MSC subsequent handover) (inter–PLMN)
d) FRE–S2GRERSS counts globally all inter–MSC handover from UMTS to GSM releases, per release
domain, between Relocation required and Send End Signal result.
Same as for GSM–GSM inter–MSC subsequent handover, see § D.9.3. The counters are not given in the
scenario above.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 240 / 260
260
D.11.4 Return subsequent inter MSC UTRAN to GSM handover – two MSC involved

UE RNCB RCPB SSPB RCPA SSPA BSCA

Relocation required

OBS: FRE–S2GPREPSS (42) or FRE–S2GPREPSSE (51)

Handover request
Relocation command
OBS: SRE–SRECOM (02)

OBS: SRE–S2GCOMS (44) or SRE–S2GCOMSE (53)
handover to GSM
handover detect
switch user plane from source RNC to target BSC
Handover complete
Free old HO leg

OBS: FRE–S2GCOMPS (45) or FRE–S2GCOMPSE (54)
Iu release command

Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 241 / 260
260
Same as for GSM–GSM inter–MSC subsequent return handover, see § D.9.4. The counters are not given
in the scenario above.
Same as for UTRAN to GSM inter–MSC subsequent handover, see § D.11.3.2.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 242 / 260
260
D.12 GSM to UMTS handover
D.12.1 Intra MSC GSM to UTRAN handover

Source Target
BSC RNC
UE BSC RCP SSP RNC

Handover
Handover required Preparation
OBS: FHO–SDTRx (30709,...)

OBS: FHO–S3GHORQA (73)
resource
Relocation request allocation
OBS: FRE–SREREQA (03)
OBS: FRE–SREREQKA (04)
Handover command
OBS: FHO–SHOC (30706)
OBS: FHO–S3GCOMA (74)
handover to UTRAN
Relocation detect Handover
switch user plane from source BSC to target RNC

Relocation complete
OBS: FHO–S3GCOMPA (75)
Clear command
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 243 / 260
260
BSC:
• FHO–SDTRx: Number of handover required (all type of handover)
• FHO–SHOC: Successfull end of the procedure: number of handover command (all type of
handover)

In addition a counter per (source BSC, target RNC)
• FHO–S3GHORQA: Number of handover required (intra–MSC)
b) The observation of the resource allocation procedure is made by a couple of counters per target
RNC:
• FRE–SREREQA: Number of relocation request (intra–MSC)
• FRE–SREREQKA: Successfull end of the procedure: number of relocation request ack (intra–
MSC)
c) The observation of handover procedure is made by a couple of counters per (source BSC, target
RNC):
• FHO–S3GCOMA: Number of handover command (intra–MSC)
• FHO–S3GCOMPA: Successfull end of the procedure: number of relocation complete (intra–
MSC)
d) FHO–S3GRERA counts globally all intra–MSC handover from GSM to UMTS releases, per release
domain, between Handover required and Relocation complete.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 244 / 260
260
D.12.2 Inter MSC GSM to UTRAN handover

UE BSCA RCPA SSPA RCPB SSPB RNCB

Handover required
OBS: FHO–SDTRx (30709,...)

OBS: FHO–S3GPREPE (77)

Relocation request


Create HO leg
IAM

Handover command
OBS: FHO–S3GCOME (78)
handover to UTRAN
Relocation detect

ANM
Relocation complete

OBS: FHO–S3GCOMPE (79)

Clear command
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 245 / 260
260
BSC:

handover)
• FHO–S3GPREPE: Number of prepare handover (inter–MSC)
may be compared with counters defined in b ).
b) The observation of handover procedure is made by a couple of counters per (source BSC, target
RNC):
• FHO–S3GCOME: Number of handover command (inter–MSC)
• FHO–S3GCOMPE: Successfull end of the procedure: number of relocation complete (inter–
MSC)
c) FHO–S3GRERE counts globally all inter–MSC handover from GSM to UMTS releases, per release
domain, between Handover required and Send End Signal (handover complete).
Same as for SRNS relocation, see § D.10.3.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 246 / 260
260
D.12.3 Subsequent inter MSC GSM to UTRAN handover – three MSC involved

MS BSCB RCPB SSPB RCPA SSPA RCPC SSPC RNCC

Handover required
OBS: FHO–SDTRx (30709,...

OBS: FHO–S3GPREPSS (81)

OBS: FHO–S3GPREPCS (85)
Relocation request

Create HO leg
IAM

Handover command

OBS: FHO–S3GCOMS (82)
handover to UTRAN
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 247 / 260
260
MS BSCB RCPB SSPB RCPA SSPA RCPC SSPC RNCC

Relocation detect

ANM
Relocation complete

OBS: FHO–S3GCOMPCS (86)
Free old HO leg
OBS: FHO–S3GCOMPS (83)

Clear command
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 248 / 260
260
a) The observation of relocation procedure is made by a couple of counters:

• FHO–S3GPREPCS: Number of prepare Handover
• FHO–S3GCOMPCS: Successfull end of the procedure: number of Send End Signal (handover
complete)
b) FHO–S3GRERCS counts globally all inter–MSC subsequent handover from GSM to UMTS
releases, per release domain, between Prepare subsequent HO (handover request) and Send End
Signal result.
BSC:
handover)
• FHO–S3GPREPSS: Number of prepare subsequent handover (inter–MSC)
may be compared with counters defined in b ).
b) The observation of handover procedure is made by a couple of counters per (source BSC, target
RNC):
• FHO–S3GCOMS: Number of handover command (inter–MSC subsequent)
• FHO–S3GCOMPS: Successfull end of the procedure: number of relocation complete (inter–
MSC subsequent)
c) FHO–S3GRERSS counts globally all inter–MSC subsequent handover from GSM to UMTS
releases, per release domain, between Handover required and Send End Signal result.
Same as for SRNS relocation, see § D.10.3.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 249 / 260
260
D.12.4 Return subsequent inter MSC GSM to UTRAN handover – two MSC involved

MS BSCB RCPB SSPB RCPA SSPA RNCA

Handover required
OBS: FHO–SDTRx (30709,...

Relocation request
OBS: FRE–SREREQR (29)

OBS: FRE–SREREQKR (30)
Prepare subsequent HO (handover request ack)
Handover command

OBS: FHO–S3GCOMS (82)
handover to UTRAN
Relocation detect
switch user plane from source BSC to target RNC
Relocation complete
OBS: FRE–SRECOMPR (31)
Free old HO leg

OBS: FHO–S3GCOMPS (83)
Clear command
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 250 / 260
260
Same as for SRNS relocation, see § D.10.5.1.


Same as for GSM to UTRAN inter–MSC subsequent handover, see § D.12.3.2.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 251 / 260
260
D.13 IN SERVICES INVOCATION
RCP SCP HLR

Service Control Point invocation
BEGIN (I INITIALDP)
OBS: FIN –INDPI ( /IDSV)

1) call handling follows on
END (RL CONTINUE)
OBS: FIN –CONTINUE ( /IDSV)

<Next Service Control Point invocation, if needed>
2) call handling follows on with a new CalledPartyNumber
END (RL CONNECT)
OBS: FIN –CONNECT ( /IDSV)
<Next Service Control Point invocation, if needed>

3) call is released
END (RL RELEASECALL)
OBS: FIN –RELCALL ( /IDSV)

<Call release>
4) refusal of InitialDP invoke
END (RL INITIALDP ERROR)
OBS: FIN –INDPE ( /IDSV)

<Call release>
Note: the observation scenarios corresponding to a call forwarded or released after IN services invocation
are not described.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 252 / 260
260
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
MS
01
BSS
D.14 SMIM INSERTION
SMIM
RCP
END (I CREATE)
Continuation –> Idem GATEWAY + TC
260
AAC020023800DS
HLR
En
SSP
253 / 260
D.15 SHORT MESSAGE TERMINATING (phase 2)
SC RCP HLR RCP BSS MS

GMSC VMSC
Successful case
CONNECTION REQUEST
CONNECTION CONFIRM
RP_MT_data
OBS : OB –FSM –SCREQ
BEGIN (I SEND ROUTING INFO FOR SM)
OBS : OB –FSM– OBS : OB –HSM –RGREQ

RGREQ
(RL SEND ROUTING INFO FOR SM)
OBS : OB –FSM OBS : OB –HSM –SRG

SRG
END (INFORM SC)
OBS : OB –HSM–ISC
SRG
BEGIN (I FORWARD SHORT MSG)
OBS : OB –FSM–OFWREQ OBS : OB –FSM –IFWREQ
Paging phase –> see GATEWAY + TC scenario

Check IMEI phase (not described)
CP DATA
RP_Data
OBS : OB –FSM–RCFREQ
CP ACK
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 254 / 260
260
GMSC VMSC
CP DATA
RP_Ack
OBS : OB –FSM –SSMRX
CP ACK
CONT (RL FORWARD SHORT MSG)
OBS : OB –FSM –ISFW OBS : OB –FSM –OSFW
RP_MT_ack
OBS : OB –FSM –SSMTX
(1)
Note 1: OBS : OB–FSM–REL (/release domain) : release of short message terminating procedure
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 255 / 260
260
GMSC VMSC
Unsuccessful case : SM delivery status report procedure

See Successful case for beginning (no paging response)
END (E FORWARD SHORT MSG)
OBS : OB –FSM –IEFW OBS : OB –FSM –OEFW

(1)
BEGIN (I REPORT SM DELIVERY STATUS)
OBS : OB –FSM– OBS : OB –HSM –MWDREQ

MWDREQ
END (RL REPORT SM DELIVERY STATUS)
OBS : OB –FSM– OBS : OB –HSM –SMWDQ

SMWD
RP–MT –Error
(1)
Note 1: OBS : OB–FSM–REL (/release domain) : release of short message terminating procedure
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 256 / 260
260
SC RCF VLR HLR
IWMSC
Alerting service center procedure required by VLR
CONT (I READY FOR SM)
OBS : OB–VSM– OBS : OB–HSM –MAREQ or

MAREQ or MSPRESREQ MSPRESREQ
CONT (RL READY FOR SM)
OBS : OB–VSM– OBS : OB–HSM –SMA or

SMA or SMSPRES SMSPRES
BEGIN (I ALERT SC)
OBS : OB–HSM –ALREQ
UDT
RP–Alert
OBS : OB–FSM –ALSC
END (RL ALERT SC)
OBS : OB –HSM –SAL

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 257 / 260
260
D.16 SHORT MESSAGE ORIGINATING
MS RCF SMS–IWMSC SC
CP_DATA
RP_Data OBS : OB –FMO –MSTRREQ
CP_ACK
ForwardShortMessage
OBS : OB –FMO –OFSMREQ OBS : OB –FOM –IFSMREQ
RP_MO_Data
OBS : OB –FMO –SCREQ

RP_MO_Ack
OBS : OB –FMO –SCACK
ForwardShortMessage Result
OBS : OB –FMO –SIFSM OBS : OB –FOM –SOFSM
CP_DATA
RP_Ack OBS : OB –FMO –SSMTR
CP_ACK
(1)
Note 1: OBS : OB–FMO–REL (/release domain) : release of short message originating procedure
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 258 / 260
260
D.17 CAMEL CONTROL AND INTERROGATION OF SUBSCRIPTION DATA : ANY
TIME INFORMATION HANDLING
MS BSS RCP VLR HLR SCP
ATSI_I
OBS:HCA–ATSI
ATSI_R
OBS:HCA–ATSIACK
ATM_I
OBS:HCA–ATM
ATM_R
OBS:HCA–ATMACK
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
AAC020023800DS En 259 / 260
260
D.18 Mobile Terminating Location Request (MT_LR) LCS procedure
MS RAN RCP HLR GMLC

Send Routing Info for LCS
OBS:HLCS–SRIREQ
Send Routing Info for LCS result
OBS:HLCS–SRIRES
Provide Subscriber Location
OBS:FLCS–MTLRREQ
OBS:FLCS–CURMTLRREQ or
OBS:FLCS–CRMTLRREQ
Page
OBS:VPG–PAGING–SM
Paging response
OBS:VPG–PAGSRCHRES–SM
Register (LCS–Location Notification)
OBS:FLCS–LOCNOTS
Release complete (LCS–Location Notification result)
OBS:FLCS–LOCNOTR
Location Reporting Control / perform Location Request
OBS:FLCS–LOCREQ (/ BSCor RNC)
Location Report / perform Location Response

OBS:FLCS–LOCRES (/ BSC or RNC)
Provide Subscriber Location result
OBS:FLCS–CURMTLRRES or
OBS:FLCS–CRMTLRRES
1AA 00014 0004 (9007) A4 – ALICE 04.10
END OF DOCUMENT
ED 01
AAC020023800DS En 260 / 260
260

RCP Counters

Загружено:

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

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

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

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

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

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

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

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

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

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

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

RCP Counters

Загружено:

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

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

FUNCTIONAL SPECIFICATION

not permitted without written authorization from Alcatel.

LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3 INTERFACE MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

01 020122 DP4 SYS/DFB

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

4.1.3 Ticket format (sent by the ASP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4.1.4 Detail about rank in the family identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

APPENDIX A – RCF COUNTER IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

A.2.39 OB–FCA–SMRQRPSMSEVT– Number of Request Event Report SMS Event . . . . . 118

A.2.45 OB–FCA–SMFCISUC – Number of Furnish Charging Information SMS successful . 119

A.3 ––––––––––––––––––– CCB counters (350) –––––––––––––––––––––––––– . . . . . . . . . 119

nating request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

A.9.18 OB–FHO–EHOFFMA (28) – HO failures signalled by the mobile stations . . . . . . . . . . 127

A.9.26 OB–FHO–EHOIRMSC (03) – Inter–MSC HO failures signalled by the network . . . . . 128

A.9.27 OB–FHO–EHOIRMSC–2 (48) – Inter–MSC HO failures signalled by the network . . . 128

A.9.70 OB–FHO–SHORMSCA (19) – Efficient incoming return subsequent HO . . . . . . . . . . . 133

A.9.78 OB–FHO–SHOSPHORA (44) – Efficient subsequent HO resource assignment . . . . . 134

A.9.79 OB–FHO–SHOSPSHORA (45) – Efficient return subs HO in controlling MSC . . . . . . 134

A.13 –––––––––––––––––––– LR counters (304) ––––––––––––––––––––––––– . . . . . . . . . . 138

A.13.1 OB–FLR–ATT (02) – IMSI attach received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

A.19.6 OB–FOC–CONNECT (11) – MS originating calls with called response . . . . . . . . . . . . . 143

A.19.7 OB–FOC–DIRCONNECT (12) – Established MS originating calls . . . . . . . . . . . . . . . . . 143

A.21.14 OB–FPG–SHPA (10) – Successful Paging with Alerting Required. . . . . . . . . . . . . . . . 147

A.21.15 OB–FPG–SRP (01) – Paging repetitions on A–interface or Iu interface . . . . . . . . . . . 147

A.23.21 OB–FRE–S2GRERE (41) – Number of relocation process released at controlling MSC

A.23.25 OB–FRE–SPREPE (10) – Number of relocation preparation request at controlling MSC

(inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

MSC (inter–MSC and subsequent inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

A.23.54 OB–FRE–SREREQKR (30) – Number of relocation resource allocation acknowledge at

target MSC (subsequent return inter–MSC relocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

A.27.14 OB–FSM–REL (15) – SMT procedure release (VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . 159

A.27.19 OB–FSM–SRG (06) – Successful routing (GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

A.27.20 OB–FSM–SSMRX (14) – successful short message reception (VMSC) . . . . . . . . . . . 160

A.28.35 OB–FSW–SRIGTW2 (32) – Interrogations for call rerouting (GTW) . . . . . . . . . . . . . . 164

A.28.43 OB–FSW–SRIOCRES (16) – Results of interrogation for rerouting calls . . . . . . . . . . 165

A.33.1 OB–FSH–REL (03) – Supplementary service operation release . . . . . . . . . . . . . . . . . . 169

APPENDIX B – VLR COUNTER IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

B.1 Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

B.2 –––––––––––––––––––– CA counters (257) –––––––––––––––––––––– . . . . . . . . . . . . . 172

B.6.6 OB–VLR–ENI (04) – Registration failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

B.7 –––––––––––––––––––– NR counters (278) –––––––––––––––––––––––– . . . . . . . . . . . . 180

B.8.5 OB–VPG–PAGSRCHRES–SM (08) – Paging /Search responses for SM . . . . . . . . . . . . 180

B.8.6 OB–VPG–SEARCH (04) – Search requests for calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

B.11.2 OB–VSM–MSABS (01) – MS present (VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Facility Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

B.12.3 OB–VTC–EMSRN–FNOTSU2 (06) – Failures for Roaming number Requests because of

APPENDIX C – HLR COUNTER IMPLEMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

C.10.14 OB–HLR–SAISDREQ (12) – Number of stand–alone Insert Subscriber data request

C.15.12 OB–HSM–SMA (13) – Successful Ready for SM (Memory available) . . . . . . . . . . . . . 196

C.16.1 OB–HSS–SRETRI (01) – Number of reused triplets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

C.16.2 OB–HSS–SRESYN (02) – Number of resynchronisations . . . . . . . . . . . . . . . . . . . . . . . . 197

APPENDIX D OBSERVATION SCENARIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

D.11 UMTS to GSM handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

D.12.2 Inter MSC GSM to UTRAN handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Figure 1. General description of Observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 3. Functional description of Observation in the RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 4. Functional description of Observation in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Review: 04/02/02 (MND/MC/R&D/CASYSM/EV/02.035.004/MB)

[1] AAC020023800DT – Observation Feature Description

[2] See note 1 – Functional Option List

[3] AAC020416700DT – Basic Services and Supplementary Services applicability

[4] AAC033528000DS – Error classification