Documente Academic
Documente Profesional
Documente Cultură
TABLE OF CONTENTS
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.1 The functional environment of the function in the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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.1 The functional environment of the function in the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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.1 The functional environment of the function in the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2.5.2 List of HLR station observations to be sent to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . 97
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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-
not permitted without written authorization from Alcatel.
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
(2G –> 3G inter–MSC handover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
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
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
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
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
not permitted without written authorization from Alcatel.
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
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
C.8.9 OB–HGP–PDPRGREQ (22) – Send Routing Info for GPRS Invoke received from GGSN . .
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
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
not permitted without written authorization from Alcatel.
193
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
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
not permitted without written authorization from Alcatel.
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
not permitted without written authorization from Alcatel.
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
ED 01
AAC020023800DS En 22 / 260
260
HISTORY
01 on 02–01–22
Creation from document AAC020023700DS Ed.03
not permitted without written authorization from Alcatel.
REFERENCED DOCUMENTS
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
ED 01
AAC020023800DS En 23 / 260
260
1 INTRODUCTION
The observation function describes the actions to be taken in the NSS so that its composite units can send
All rights reserved. Passing on and copying of this
document, use and communication of its contents
The OMC shall process this data, store it and make it available for consultation.
OMC
OBS.
APPLI.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ COLLECT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
(4)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACQUISITION
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
GENERIC
I20y
OBS.
I10y
I40y I30y
APPLI.
TCAP
HLR (AUC,HLR) RTOS APPLI.
or
RCP (RFC, VLR)
(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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
(I20y): sending of raw values of the counters in the form of tickets (formatting by the Application (OBS)).
The values of ”y” are:
– 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.
– 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)
(I30y): reading of RTOS counters by an observation function at the rate of a system period.
The values of ”y” are:
– 2 : HLR
– 3 : RCP
(I40y): reading of TCAP counters by an observation function at the rate of a system period.
The values of ”y” are:
– 0 : RCF
– 1 : VLR
– 2 : HLR
ED 01
AAC020023800DS En 25 / 260
260
1.1 General Principle about Application Counters Definition
1.1.1 Definition
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
– 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
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.1 Definition
– 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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
The MMC INTCLA displays the polling class for one or several families.
1.2.2.3 Modification and Interrogation of the polling period if F–OBS–006 is not active
The MMC MODPER at the RCP allows the modification and the interrogation of the polling class period.
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.
not permitted without written authorization from Alcatel.
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.
The MMC MODPER at the RCP allows the modification and the interrogation of the polling class period.
The MMC MODPER at the HLR allows the modification and the interrogation of the polling class period.
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
ED 01
AAC020023800DS En 29 / 260
260
2 DETAILED DESCRIPTION
The different interfaces are listed in this chapter for each unit as follows:
– RCF
not permitted without written authorization from Alcatel.
– VLR
All rights reserved. Passing on and copying of this
document, use and communication of its contents
– RCP station
– HLR
– HLR station
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:
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.
ED 01
AAC020023800DS En 30 / 260
260
y Unit number Unit name
A 0 STATION (RTOS)
not permitted without written authorization from Alcatel.
H 1 HLR
All rights reserved. Passing on and copying of this
document, use and communication of its contents
V 2 VLR/RCP
F 3 RCF/RCP
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
ED 01
AAC020023800DS En 31 / 260
260
2.1 Detailed description in the RCF
(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
ED 01
AAC020023800DS En 32 / 260
260
2.1.2 List of RCF observations to be sent to the OMC
ED 01
AAC020023800DS En 33 / 260
260
Name Nb. Description T C Identifier Rel.
with IMSI
ED 01
AAC020023800DS En 34 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 35 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 36 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 37 / 260
260
Name Nb. Description T C Identifier Rel.
domain
ED 01
AAC020023800DS En 38 / 260
260
Name Nb. Description T C Identifier Rel.
originating BSC
ED 01
AAC020023800DS En 39 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 40 / 260
260
Name Nb. Description T C Identifier Rel.
ment attempt
ED 01
AAC020023800DS En 41 / 260
260
Name Nb. Description T C Identifier Rel.
in controlling MSC
ED 01
AAC020023800DS En 42 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 43 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 44 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 45 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 46 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 47 / 260
260
Name Nb. Description T C Identifier Rel.
BSC)
(intra–PLMN case)
ED 01
AAC020023800DS En 48 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 49 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 50 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 51 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 52 / 260
260
Name Nb. Description T C Identifier Rel.
Transfer
ED 01
AAC020023800DS En 53 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 54 / 260
260
Name Nb. Description T C Identifier Rel.
per BSC
ED 01
AAC020023800DS En 55 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 56 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 57 / 260
260
Name Nb. Description T C Identifier Rel.
failure
ED 01
AAC020023800DS En 58 / 260
260
Name Nb. Description T C Identifier Rel.
overflow
ED 01
AAC020023800DS En 59 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 60 / 260
260
Name Nb. Description T C Identifier Rel.
Call)
ED 01
AAC020023800DS En 61 / 260
260
Name Nb. Description T C Identifier Rel.
address
ED 01
AAC020023800DS En 62 / 260
260
Name Nb. Description T C Identifier Rel.
face address
CA interface address
ED 01
AAC020023800DS En 63 / 260
260
Name Nb. Description T C Identifier Rel.
address
Address
ED 01
AAC020023800DS En 64 / 260
260
Name Nb. Description T C Identifier Rel.
Address
ED 01
AAC020023800DS En 65 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 66 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 67 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 68 / 260
260
Name Nb. Description T C Identifier Rel.
status request
ED 01
AAC020023800DS En 69 / 260
260
Name Nb. Description T C Identifier Rel.
Note :
(2) This counter is included in FOC–REL but is kept for compatibility reason.
(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.
not permitted without written authorization from Alcatel.
(13) This counter is replaced by counters per BSC and per procedure type:FRM–OCASCOM, FRM–
All rights reserved. Passing on and copying of this
document, use and communication of its contents
(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).
(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
ED 01
AAC020023800DS En 71 / 260
260
2.2 Detailed description in the VLR
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
(1) VLR and RCF TCAP IN and VH counters are merged in RCP counters and trans-
mitted in RCF ticket
ED 01
AAC020023800DS En 72 / 260
260
2.2.2 List of VLR observations to be sent to the OMC
ED 01
AAC020023800DS En 73 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 74 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 75 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 76 / 260
260
Name Nb. Description T C Identifier Rel.
erage
per SS code
ED 01
AAC020023800DS En 77 / 260
260
Name Nb. Description T C Identifier Rel.
operation requests
ED 01
AAC020023800DS En 78 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 79 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 80 / 260
260
Name Nb. Description T C Identifier Rel.
address
(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.
(4) Since R4.1, these counters are incremented for MAP phase 1 and MAP phase 2 messages.
(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
by the ”List of SupplementaryService codes for operation counters”.
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.
not permitted without written authorization from Alcatel.
(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.
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
ED 01
AAC020023800DS En 83 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 84 / 260
260
Name Nb. Description T C Identifier Rel.
on (1) These Observation counters related to the SCCP Gateway function are sent to the OMC only if
F–OBS–001 is active.
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
SM Short Message Terminating
SS Subscriber Security
TC Terminating Call
TCAP (I 402)
TR Translation HLR
VH Version Handling
ED 01
AAC020023800DS En 86 / 260
260
2.4.2 List of HLR observations to be sent to the OMC
ED 01
AAC020023800DS En 87 / 260
260
Name Nb. Description T C Identifier Rel.
address
ED 01
AAC020023800DS En 88 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 89 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 90 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 91 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 92 / 260
260
Name Nb. Description T C Identifier Rel.
vice Completion
operations
in HLR
ED 01
AAC020023800DS En 93 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 94 / 260
260
Name Nb. Description T C Identifier Rel.
ED 01
AAC020023800DS En 95 / 260
260
Name Nb. Description T C Identifier Rel.
(5)
(1) The list of Supplementary Service codes for the counter OB–HSH–SNOSS is given in 4.1.4 page 105
by the ”List of SupplementaryService codes for operation counters”.
(2) The list of Supplementary Service codes for the counter OB–HSH–ENOSS is given in 4.1.4 page 105
by the ”List of SupplementaryService codes for operation counters”.
(3) Since R4.1, these counters are incremented for MAP phase 1 and MAP phase 2 messages.
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
ED 01
AAC020023800DS En 97 / 260
260
N.B. If F–OBS–002 is active, these Observation counters are not sent to the OMC.
ED 01
AAC020023800DS En 98 / 260
260
Name Nb. Description T C Id. Rel.
ED 01
AAC020023800DS En 99 / 260
260
3 INTERFACE MATRIX
Function (1)
not permitted without written authorization from Alcatel.
R R V H H R A interfaces
Name FB C C L L L T C
P F R R H OQ
S
FUNCTION: Observation
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
4 INTERFACES
– 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”
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
260
STEP1: STEP2: STEP3: STEP4:
identical counter
counter of list
type P or list ticket
L split
header
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
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
not permitted without written authorization from Alcatel.
– OBS 2 OVERFLOW : the maximum number of counters per couple with the FAST class transmitted
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
TICKET HEADER:
N.B. (1) The time is the same for all tickets pertaining to the same dispatch
ED 01
260
TICKET BODY is composed of a succession of counters with format (note 2):
(note 3)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
N.B. (2) All Counters of the same family are grouped together in a dispatch (not true for RTOS count-
ers).
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
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
not permitted without written authorization from Alcatel.
type.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
General rule for the identifier definition is to use the same identity forms than those input by operator and
displayed by Man Machine Commands:
– Emergency service
• the identifiers of emergency service definition is left to the customer, controlled by translator’s
MMCs
ED 01
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
not permitted without written authorization from Alcatel.
ED 01
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.
not permitted without written authorization from Alcatel.
– List of Supplementary Service codes for Call Completion operation counters in HLR
• ”CCBSA” for call completion on busy subscriber
– List of Supplementary Service codes for Call Completion operation counters in VLR
• ”CCBSA” for call completion on busy subscriber
• ”14400”: 14400b/s
– List of ITC:
• ”UDI” when ITC value of GSM–BC is ’1’,
ED 01
260
• ”3.1kHz” when ITC value of GSM–BC is ’2’,
• ”FAX” when ITC value of GSM–BC is ’3’.
– List of ITC/FNUR:
not permitted without written authorization from Alcatel.
– 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.
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
– Signalling link
RTOS object identifier in ASCII
ED 01
260
RTOS object identifier in ASCII
– Processor
RTOS object identifier in ASCII
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
– 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.
• ”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),
• ”HOENDLST” for end of HO list without selected candidate cell (GSM only)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
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)
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
• ”CDNOANSW” for no answer from called party during ringing phase (OC, TC, GW)
• ”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)
• ”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
• ”CALLSUP” for conversation phase supervision timer release cause (OC, TC) and OC release
cause due to Call Gaping at RCP.
ED 01
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.
not permitted without written authorization from Alcatel.
• ”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)
– 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
ED 01
260
– Priority (for eMLPP counters) :
(for eMLPP applicability, see document [3] page 23.)
”NO_PRIO” for no priority
”PRIO_4” for priority level 4
not permitted without written authorization from Alcatel.
– (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.
– (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.
ED 01
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.
not permitted without written authorization from Alcatel.
Number of
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
ED 01
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
not permitted without written authorization from Alcatel.
maximum number of members in the family, due to dimensioning constraints.In this case, then only the
All rights reserved. Passing on and copying of this
document, use and communication of its contents
first n counters of this type are sent to the OMC, even if more than n are available at the RCP.
ED 01
260
APPENDIX A – RCF COUNTER IMPLEMENTATION
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.
counter incremented when the APPLY CHARGING Request has not failed.
counter incremented when an APPLY CHARGING Request is received from the gsmSCP.
counters (one counter per SCP ) incremented when a call is rejected as result of the call gapping
checks.
counter incremented when a CALL GAP Request is received from an SCP and accepted.
counter incremented when the CALL INFORMATION Request has not failed.
counter incremented when an CALL INFORMATION Request is received from the gsmSCP.
counter incremented when a CANCEL CALL Request is received from the gsmSCP.
ED 01
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
counter incremented when a DISCONNECT LEG Request is received from the gsmSCP.
counter incremented when the establishment of a temporary connection has not failed.
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.
Counters, per PLMN, incremented on emission (at Detection Point 07) of EVENT REPORT BCSM
message to the SCP.
Counters, per PLMN, incremented on emission (at Detection Point 09) of EVENT REPORT BCSM
message to the SCP.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
A.2.20 OB–FCA–EVRPBCSMDP10 (12) – Number of Event Report BCSM at DP10
counter incremented when the gsmSSF notifies the gsmSCF of a O–Abandon event.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counters, per PLMN, incremented on emission (at Detection Point 15) of EVENT REPORT BCSM
message to the SCP.
Counters, per PLMN, incremented on emission (at Detection Point 17) of EVENT REPORT BCSM
message to the SCP.
counter incremented when the gsmSSF notifies the gsmSCF of a O–Abandon event.
counter incremented when a FURNISH CHARGING INFORMATION Request has not failed.
counter incremented when a FURNISH CHARGING INFORMATION Request is received from the
gsmSCP.
Counters, per PLMN, incremented on emission (at Detection Point 02) of INITIALDP message to the
SCP.
Counters, per PLMN, incremented on emission (at Detection Point 12) of INITIALDP message to the
SCP.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
counter incremented when a REQUEST REPORT BCSM EVENT is received from the gsmSCP.
counter incremented when an RESET TIMER Request is received from the gsmSCP.
counter incremented when a SEND CHARGING INFORMATION Request has not failed.
counter incremented when a SEND CHARGING INFORMATION Request is received from the
gsmSCP.
Conter incremented when the gsmSSF notifies the gsmSCP of a collected–SMS–Info event.
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.
Counter incremented when the gsmSSF notifies the gsmSCP of a SMS–Failure event.
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
260
A.2.43 OB–FCA–SMRESETSUC – Number of Reset Timer SMS successful
Counter is incremented when the Reset Timer request has not failed.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter is incremented when a Furnish Charging Information request is received from the gsmSCP.
Counter is incremented when a Furnish Charging Information request has not failed.
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’.
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’.
Counter incremented on receipt of either COMPLETE CALL or PROCESS CALL WAITING message
from the VLR, containing the information ”CCBS call”.
Counter incremented on sending of the REGISTER CC ENTRY message to the VLR related to CCBS.
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.
Counters, per carrier, incremented when sending the CREATE message to the SSP to setup an originating
call towards a given carrier.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per carrier, incremented when the PROVIDE INSTRUCTION message received in the VMSC
indicates the call is coming from a given carrier.
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, per couple (previous data speed, new data speed), incremented on emission of the CMM_CONF
message.
Counter, per couple (previous data speed, new data speed), incremented on reception of the
CMM_REQUEST message from the SMIM.
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.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
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.
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
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
related to FAX protocol problems.
A.6.12 OB–FDA–FRINT (19) – Data call release forced by SMIM due to internal failure
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
related to internal failure.
A.6.13 OB–FDA–FRRLP (15) – Data call release forced by SMIM due to RLP problems
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
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
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
related to synchronisation problems.
ED 01
260
A.6.15 OB–FDA–FRV42 (16) – Data call release forced by SMIM due to V.42 problems
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
related to V.42 problems.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
A.6.16 OB–FDA–FRX25 (17) – Data call release forced by SMIM due to X.25 problems
Counters incremented on reception of the FORCED RELEASE message from the SMIM with a cause
related to X.25 problems.
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).
Counter incremented on transmission of the MODIFY COMPLETE message to the MS due to In–Call
Modification procedure.
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.
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
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
not permitted without written authorization from Alcatel.
Assignment request. The number of TCH/F requested is the one received from the MS in SETUP or CALL
All rights reserved. Passing on and copying of this
document, use and communication of its contents
CONFIRMED.
These counters are not incremented for dual services (”alternate” or ”followed by”).
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.
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.
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
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
not permitted without written authorization from Alcatel.
the MS with fallback GSM–BC when ”multislot and 14.4 singleslot” parameters have been sent in GSM–
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
Counter incremented on transmission of the MODIFY COMPLETE message to the MS after a successful
”User initiated resource up/downgrading” procedure.
Counters per ITC and per FNUR, incremented on reception of CONNECT ACK from the UE when a Multi-
media call is established in UMTS.
Counters per ITC and per FNUR, incremented on emission of CONNECT ACK to the UE when a Multime-
dia call is established in UMTS.
Counters per ITC and per GBR, incremented on reception of CONNECT ACK from the UE when a BS20
call is established in UMTS.
Counters per ITC and per GBR, incremented on emission of CONNECT ACK to the UE when a BS20 call
is established in UMTS.
Counters, per BSC, incremented on emission of the CONFUSION message toward a BSC.
ED 01
260
A.8 –––––––––––––––––––– GP counters (335) –––––––––––––––––––––––––
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
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 call unrelated services.
The call unrelated services match Short Message Terminating, Network Initiated USSD services, Location
services LCS.
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.
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.
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
inter–MSC handover)
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-
sequent inter–MSC handover)
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
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-
not permitted without written authorization from Alcatel.
PLETE message from the target RNC for 2G –> 3G intra–MSC handover.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
A.9.5 OB–FHO–S3GCOMPE (79) – Number of handover complete at controlling MSC (2G –> 3G
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 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.
Counters, per couple (source BSC, target RNC), incremented at controlling MSC on transmission of the
PREPARE HANDOVER (HANDOVER REQUEST) message for 2G –> 3G inter–MSC handover.
Counters, per couple (source BSC, target RNC), incremented at controlling MSC on transmission of the
PREPARE HANDOVER (HANDOVER REQUEST) message for 2G –> 3G subsequent inter–MSC hand-
over.
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
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
not permitted without written authorization from Alcatel.
HANDOVER REQUIRED reception and RELOCATION COMPLETE reception, and also on normal
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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)
Counters, per release domain, incremented on each release of 2G –> 3G subsequent inter–MSC hand-
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.
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.
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.
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 (T103), in case of inter–MSC handover.
Counters, per couple (origin BSC, target LAC), 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.
ED 01
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
not permitted without written authorization from Alcatel.
handover.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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 (T103), in case of subsequent handover.
Counters, per couple (origin BSC, target LAC), 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.
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.
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.
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.
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.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counters, per couple (origin BSC, target LAC), incremented in serving MSC, on SEND END SIGNAL
Result timer expiry, in case of subsequent handover.
Counter incremented in serving MSC, on SEND END SIGNAL Result timer expiry, in case of subsequent
handover.
Counter incremented on rejection of PERF_HO Invoke (MAP phase 1) or PREP_HO Invoke (MAP phase
2) for traffic regulation cause.
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message.
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message hav-
ing started handover processes.
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message hav-
ing lead to the updating of the handover processes.
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
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
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’.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per origin MSC, incremented on transmission of the GEN_SIG (ACM) message in case of inter–
MSC or subsequent handover.
Counters, per target BSC, incremented on reception of the HO_COMPLETE message, in case of intra–
MSC handover
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.
Counters, per target BSC, incremented on reception of the HO_REQUEST_ACK message, in case of
intra–MSC HO.
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).
Counters, per target BSC, incremented on reception of the HO_REQUEST_ACK message, in case of
inter–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.
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
Counters, per origin BSC , incremented on transmission of the HANDOVER COMMAND message for
inter–MSC handover
ED 01
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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter, incremented on transmission of the HANDOVER COMMAND message for inter–MSC handover
Counters, per origin BSC , incremented in serving MSC, on transmission of the HANDOVER COMMAND
message for subsequent handovers
Counters, per couple (origin BSC, target LAC), incremented in serving MSC, on transmission of the
HANDOVER COMMAND message for subsequent handovers
Counter, incremented in serving MSC, on transmission of the HANDOVER COMMAND message for sub-
sequent handovers
Counters, per BSC at the origin of the handover required , incremented on reception of the HANDOVER
COMPLETE message for an intra–MSC handover.
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.
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.
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.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
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
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
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.
Counters, per origin BSC, incremented on reception of the HO_PERFORM messages leading to handover
process interruption
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.
Counter incremented in the controlling/serving MSC, on reception of the SEND END SIGNAL Invoke
message, in case of inter–MSC HO.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counters, per serving MSC, incremented in controlling MSC on transmission of the SEND END SIGNAL
Result message
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.
Counters, per target BSC, incremented on each HO resource allocation failure (i.e. HO_FAILURE mes-
sage reception with cause allowing reselection).
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)
Counters, per target BSC, incremented in controlling MSC, on reception of the HO_REQUEST_ACK mes-
sage, in case of return subsequent HO.
Counter incremented on transmission from controlling MSC, of the SEND END SIGNAL Result message,
in case of 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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
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.
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.
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.
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.
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.
Counters, per target LAC, incremented in the serving MSC, on reception of the SEND END SIGNAL
Result message.
ED 01
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counters, per Service Key, incremented on reception of the INITIALDP Error message.
Counters, per Service Key, incremented on emission of the INITIALDP Invoke message.
Counters, per Service Key, incremented on routing towards a network server (Originating call, terminating
call or intelligent network invocation after a forwarding case).
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.
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
ED 01
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-
not permitted without written authorization from Alcatel.
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
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
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-
not permitted without written authorization from Alcatel.
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.
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.
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
260
A.13 –––––––––––––––––––– LR counters (304) –––––––––––––––––––––––––
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”.
Counters, per BSC/RNC at the origin of the message, incremented on reception of IMSI DETACH INDICA-
TION
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).
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).
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”
Counter incremented on rejection for traffic regulation cause of a LOCATION UPDATING Request with
location updating type set to ”periodical”
Counters, per release domain, incremented on release of a location registration, or ATTACH procedure
(per release domain).
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”.
Counters, per BSC/RNC at the origin of the message, incremented on reception of the LOCATION
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
A.13.10 OB–FLR–SLUP (06) – Registration requests for periodic LR
Counters, per BSC/RNC at the origin of the message, incremented on reception of the LOCATION
UPDATING Request message with location updating type set to ”periodical”.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per BSC/RNC at the origin of the LOCATION UPDATING Request, incremented on transmis-
sion of the LOCATION UPDATING Accept message.
Counter incremented at the sending of MM INFORMATION message to the MS if the sending is due to
SoLSA feature.
Counters, per BSC, incremented at the sending of LSA INFORMATION message to the BSC.
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).
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).
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).
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
260
A.16 –––––––––––––––––––– MO (Short Message Originating) counters (346)
Counter incremented at the reception of the FORWARD SHORT MESSAGE Request from the VMSC.
Counter incremented at the reception of the RP–SMMA message (message indicating that MS has again
memory capacity available) from the MS.
Counter incremented at the reception of the RP–DATA message from the MS.
Counters, per release domain, incremented on release of short message originating procedure.
Counter incremented at the sending of the RP–ACK message to the MS as a successful response to a
previous RP–SMMA.
Counter incremented on the reception of the RP–ACK from the Service Centre.
Counter incremented at the reception of the FORWARD SHORT MESSAGE Result from the SMS–
IWMSC.
Counter incremented on sending the FORWARD SHORT MESSAGE Result to the VMSC.
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
260
A.17 –––––––––––––––––––– MP counters (323) ––––––––––––––––––––––––
Counter incremented when sending INAP ADD Invoke operation toward the SSP to start a multi–party
call (conference Information = start of conference).
Counter incremented when receiving INAP ADD Result operation from the SSP further to the request to
start a multi–party call.
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).
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.
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).
Counter incremented when sending CS1 INITIAL–DP operation toward the Number Portability Data Base
in the VMSC further to an originating call toward a possibly ported MSISDN (OQoD).
Counter incremented when receiving CS1 CONNECT operation from the Number Portability Data Base
further to a NPDB query on digits analysis for an originating call in the VMSC.
Counter incremented when sending CS1 INITIAL–DP operation toward the Number Portability Data Base
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
260
A.18.7 OB–FNP–ROHR (02) – Terminating calls to a ported MS – QoHR –
Counter incremented when receiving CS1 CONNECT operation from the Number Portability Data Base
further to a NPDB query on HLR release (SRI error) in the gateway MSC.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counter incremented when sending CS1 INITIAL–DP operation toward the Number Portability Data Base
in the gateway MSC further to a possibly ported MSISDN analysis (TQoD).
Counter incremented when receiving CS1 CONNECT operation from the Number Portability Data Base
further to a NPDB query on digits analysis for a terminating call in the gateway MSC.
Counters, per destination BSC/RNC, incremented on transmission of the ALERTING message towards
the calling MS
Counters, per release domain, incremented on release of an originating call during conversation phase
Counters, per destination BSC/RNC, incremented on transmission of the CALL PROCEEDING message
towards a MS.
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
ED 01
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per destination BSC/RNC, incremented on transmission of the CONNECT message towards
a MS, without transmission of ALERTING message.
Counter incremented for each call requesting DTMF TRANSMISSION regardless the number of requests
during the call.
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
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
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
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.
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
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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per basic service, incremented by one on each incrementation of OB–FOC–DURE–BS counter
Counters, per basic service, incremented by one on each incrementation of OB–FOC–DURS–BS counter
Counters, per destination BSC/RNC, incremented on transmission of the PROGRESS message towards
the calling MS
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.
Counters, per basic service, incremented each time a SETUP (or EMSETUP) message is received from
the MS (Basic Service derived from GSM_BC)
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.
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
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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counter incremented on detection of refusal of call hold invocation during an outgoing call due to ODB
of supplementary service management.
Counter incremented by the GMSC on receiving, from an HLR of another PLMN, a SEND ROUTING INFO
Result with a roaming number.
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.
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.
Counter incremented by the GMSC on receiving, from a VMSC, an RCH Invoke with a forwarded–to num-
ber.
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
ED 01
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
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.
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.
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 calls and terminating short mes-
sages.
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 A–interface (GSM) or Iu interface (UMTS).
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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
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 A–interface (GSM) or Iu interface (UMTS).
ED 01
260
A.21.6 OB–FPG–ERP–SM (14) – Paging failures (short messages) on A–interface or Iu 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 short messages terminating.
not permitted without written authorization from Alcatel.
This counter is incremented only when the event which has triggered the sending of the error message
All rights reserved. Passing on and copying of this
document, use and communication of its contents
has occurred due to a page or search procedure on A–interface (GSM) or Iu interface (UMTS).
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.
Counter incremented each time a PAGING message is sent with the Information ”Element Alerting
Required”.
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.
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.
Counter incremented on reception of the PAGE Result component with TMSI, after a requesting PAGE
Request with IMSI
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
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
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.
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.
This counter applies for intra–PLMN case only.
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.
This counter applies for inter–PLMN case only.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
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-
not permitted without written authorization from Alcatel.
CEL message from the source RNC for 3G –> 2G intra–MSC handover.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
This counter applies for intra–PLMN case only.
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.
This counter applies for inter–PLMN case only.
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.
This counter applies for intra–PLMN case only.
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.
This counter applies for inter–PLMN case only.
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.
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.
This counter applies for intra–PLMN case only.
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
260
This counter applies for inter–PLMN case only.
A.23.13 OB–FRE–S2GRECOMS (44) – Number of relocation command at serving MSC (3G –>
not permitted without written authorization from Alcatel.
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.
This counter applies for intra–PLMN case only.
A.23.14 OB–FRE–S2GRECOMSE (53) – Number of relocation command at serving MSC (3G –>
2G subsequent inter–MSC handover) (inter–PLMN)
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.
This counter applies for inter–PLMN case only.
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.
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.
This counter applies for intra–PLMN case only.
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.
This counter applies for inter–PLMN case only.
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.
This counter applies for intra–PLMN case only.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
A.23.19 OB–FRE–S2GRECOMPSE (54) – Number of relocation complete 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 SEND
not permitted without written authorization from Alcatel.
END SIGNAL RESULT message from the controlling MSC for 3G –> 2G subsequent inter–MSC hand-
All rights reserved. Passing on and copying of this
document, use and communication of its contents
over.
This counter applies for inter–PLMN case only.
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.
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)
Counters, per release domain, incremented on each release of 3G –> 2G subsequent inter–MSC hand-
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.
Counters, per controlling MSC, incremented at target MSC on transmission of the ACM message to the
controlling MSC.
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
260
A.23.26 OB–FRE–SPREPCS (21) – Number of relocation preparation request at controlling MSC
(subsequent inter–MSC relocation)
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.
Counters, per controlling MSC, incremented at target MSC on reception of the PREPARE HANDOVER
(RELOCATION REQUEST) message from the controlling MSC.
Counters, per couple (source RNC, target RNC), incremented on reception of the RELOCATION CAN-
CEL message from the source RNC for intra–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.
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.
Counters, per source RNC, incremented on transmission of the RELOCATION COMMAND message to
the source RNC.
Counters, per couple (source RNC, target RNC), incremented on transmission of the RELOCATION
COMMAND message to the source RNC for intra–MSC relocation.
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
260
A.23.35 OB–FRE–SRECOMS (26) – Number of relocation command at serving MSC (subse-
quent inter–MSC relocation)
Counters, per couple (source RNC, target RNC), incremented at serving MSC on transmission of the
not permitted without written authorization from Alcatel.
RELOCATION COMMAND message to the source RNC for subsequent inter–MSC relocation.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per couple (source RNC, target RNC), incremented on reception of the RELOCATION COM-
PLETE message from the target RNC for intra–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.
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.
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.
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.
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.
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
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
not permitted without written authorization from Alcatel.
between RELOCATION REQUIRED and SEND END SIGNAL (RELOCATION COMPLETE), and also
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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-
sequent inter–MSC relocation)
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.
Counters, per source RNC, incremented on reception of the RELOCATION REQUIRED message.
Counters, per couple (source RNC, target RNC), incremented on reception of the RELOCATION
REQUIRED message related to a target RNC for intra–MSC relocation.
Counters, per target RNC, incremented on transmission of the RELOCATION REQUEST message to the
target RNC for intra–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
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-
not permitted without written authorization from Alcatel.
get MSC to the target RNC for subsequent return inter–MSC relocation.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per target RNC, incremented on reception of the RELOCATION REQUEST ACK message from
the target RNC for intra–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.
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.2 OB–FRM–EASR–2 (12) – traffic channel assignment failures for pool related causes
ED 01
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
not permitted without written authorization from Alcatel.
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 (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.
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 completion of the TCH assignment procedure previously
interrupted by the reception of the HANDOVER REQUIRED message.
Counters, per originating BSC, incremented on reception of the HANDOVER REQUIRED message during
the TCH assignment procedure.
ED 01
260
A.24.11 OB–FRM–SASR (01) – Radio resource (traffic channel) assignments
Counter,per BSC, incremented on reception of the message ASSIGN COMPLETE and on reception of
the message HANDOVER REQUEST ACKNOWLEDGE.
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’.
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.
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.
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.
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
260
A.25 –––––––––––––––––––– SC counters (310) ––––––––––––––––––––––––
Counter incremented on reception from the EIR of the CHECK IMEI Result component with the Equip-
mentStatus parameter equal to ”black–listed”.
Counter incremented on reception from the EIR of the CHECK IMEI Result component with the Equip-
mentStatus parameter equal to ”grey–listed”.
Counter incremented on transmission to the EIR of the CHECK IMEI Invoke component.
Counter incremented on reception from the EIR of the CHECK IMEI Error component with the UnknownE-
quipment error cause.
Counter incremented on reception from the EIR of the CHECK IMEI Result component with the Equip-
mentStatus parameter equal to ”white–listed”.
Counters incremented on release of a Short message gateway procedure, per release domain
Counter incremented on receiving in the GMSC the FORWARD SHORT MESSAGE Error with cause
”Absent subscriber” or ”Absent subscriber SM” (MAP v3).
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented at the reception of the FORWARD SHORT MESSAGE Result message from the
VMSC.
Counter incremented at the reception of the FORWARD SHORT MESSAGE Result message from a
SGSN.
Counter incremented on sending the MESSAGE WAITING DATA Invoke (phase 1) or REPORT SM
DELIVERY STATUS Invoke (phase 2) to the HLR.
Counter incremented on sending to the GMSC the FORWARD SHORT MESSAGE Error with cause
”Absent subscriber” or ”Absent subscriber SM” (MAP v3).
Counter incremented on sending the FORWARD SHORT MESSAGE Invoke to the VMSC.
Counter incremented on sending the FORWARD SHORT MESSAGE Result message to the GMSC.
Counters, per release domain, incremented on release of a Short Message Terminating procedure
Counter incremented on sending the SEND ROUTING INFO. FOR SHORT MESSAGE to the HLR.
ED 01
260
A.27.16 OB–FSM–SCREQ (01) – Service center request (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 at the reception of the SEND ROUTING INFO. FOR SHORT MESSAGE Result
from the HLR.
N.B. (1) This counter is not incremented on reception of periodical SSP test message.
1AA 00014 0004 (9007) A4 – ALICE 04.10
(identical to FSW–SRIFWDVIOL)
ED 01
260
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code is
”ForwardingViolation”.
not permitted without written authorization from Alcatel.
A.28.5 OB–FSW–EIRAGMSC (07) – Failures of interrogation for rerouting call excepted For-
All rights reserved. Passing on and copying of this
document, use and communication of its contents
warding Violation
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code dif-
fers from ForwardingViolation.
N.B. This definition does not include some cases of no response to paging and the case of release
by the SSP.
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).
Counters, per release domain, incremented on release of a gateway procedure per release domain.
Counter incremented on sending of INSERT invoke for IWF insertion after receiving a MODIFY request.
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
260
A.28.13 OB–FSW–IWFINS–OC–REQ (39) – Number of IWF insertion requests in OC call using
the SSP generic function
Counter incremented on sending of CREATE invoke with IWF insertion for OC call establishment.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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
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.
Counter incremented each time a SEND ROUTING INFO Result containing extension related to Opti-
mized Terminating Call function is received.
Counter incremented each time a Provide Local Roaming Number is requested (related to Optimized
Terminating Call function).
parameter does not designate a BSC, for a gateway or unconditionally forwarded call (calling leg initiated
by a PROVIDE INSTRUCTION).
ED 01
260
A.28.23 OB–FSW–SAEVRF (01) – Calls outgoing from MSC.
(CREATE for inter MSC handover are not taken into account).
All rights reserved. Passing on and copying of this
document, use and communication of its contents
N.B. (1) This counter is not incremented on transmission of periodical SSP test message.
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.
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”.
N.B. (1) This counter is not incremented on reception of periodical RCP test message.
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.
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code is
1AA 00014 0004 (9007) A4 – ALICE 04.10
AbsentSubscriber.
ED 01
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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on reception of the SEND ROUTING INFO Result component with the Roaming-
Number parameter, for a forwarded call
(replace FSW–EARGMSC)
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code is
”ForwardingViolation”.
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).
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
Counter incremented on reception of the SEND ROUTING INFO Result component with the Roaming-
Number parameter, for a gateway call
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
Counter incremented on reception of the SEND ROUTING INFO Result component with the Roaming-
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
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code is
”BearerServiceNotProvided”, ”FacilityNotSupported” or ”TeleserviceNotProvided”.
Counter incremented on reception of the SEND ROUTING INFO Error component whose error code is
”Unknownsubscriber”.
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).
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
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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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.
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.
Counter incremented on reception of the SEND INFO FOR INCOMING CALL SET UP Error component
whose error code is ”ForwardingViolation”.
Counter, per release domain, incremented on release of a terminating call forwarded in the VMSC.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counters, per basic service, incremented by one on each incrementation of OB–FTC–DURC–BS counter
ED 01
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
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counters, per basic service, incremented by one on each incrementation of OB–FTC–DURS–BS counter
Counter incremented on rejection of PROVIDE INSTRUCTION Request for traffic regulation cause.
Counters, per release domain, incremented on release of a (non forwarded) terminating call
Counter incremented on reception of the SEND ROUTING INFO Result component with local MSRN,
for an incoming call from fixed network.
Counter incremented on detection of refusal of call hold during a terminating call due to ODB of supple-
mentary service management.
Counters, per observed translation result, incremented on each translator nvocation leading to this result.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on sending INAP messages to SSP (CREATE, FREE, GENERATE SIGNAL) with
UUI included for originating and terminating calls.
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).
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).
Counter incremented on reception of the Facility Information element with the SS version indicator
absent or equal to ”phase 1”.
Counter incremented on reception of the Facility Information element with the SS version indicator
unknown or equal to ”phase 2”.
ED 01
260
A.32.7 OB–FVH–R99CNX (07) – Connection with MS Release 99 at least
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
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).
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
N.B. This includes explicit requests that the call be handled with no priority.
ED 01
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
not permitted without written authorization from Alcatel.
q ) CLIRRINV
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
ED 01
260
APPENDIX B – VLR COUNTER IMPLEMENTATION
B.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 in 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.
Counter indicating the total number of MM–Event–Notification messages sent by VLR to SCP.
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
completion. There is one counter per supplementary service related to call completion.
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
completion. There is one counter per supplementary service related to call completion.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
B.4 –––––––––––––––––––– CT counters (249) ––––––––––––––––––––––
Counter incremented on reception of the ACTIVATE TRACE MODE Invoke component from HLR.
Counter incremented on transmission of the ACTIVATE TRACE MODE Result toward HLR.
B.5.8 OB–VGP–LOCUPREQ (07) – Location Update Request message received from a SGSN
ED 01
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
not permitted without written authorization from Alcatel.
Request message.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on reception of a Paging Reject message from a SGSN, including Paging Reject
message for SMT, LCS,..
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
ED 01
260
B.5.21 OB–VGP–RESTACKS (18) – Reset_Ack message sent to a SGSN
B.5.26 OB–VGP–UNREASM (06) – MS_Unreachable message for SMT received from a SGSN
Counter incremented on reception of UPDATE LOCATION Result component from other PLMN HLR with
allowed roaming.
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.
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.
Counter incremented on reception of DELETE SUBSCRIBER DATA Invoke component from HLR.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Counter incremented on transmission of DELETE SUBSCRIBER DATA Result component toward HLR.
ED 01
260
B.6.6 OB–VLR–ENI (04) – Registration failures.
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.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented in new VLR, on reception of SEND PARAMETER Result (MAP phase 1) or SEND
IDENTIFICATION Result (MAP phase 2) component.
Counter incremented in old VLR, on reception of SEND PARAMETER Invoke (MAP phase 1) or SEND
IDENTIFICATION Invoke (MAP phase 2) component.
Counter incremented in old VLR, on transmission of SEND PARAMETER Result (MAP phase 1) or SEND
IDENTIFICATION Result (MAP phase 2) component.
Counter incremented on inter–MSC location updating, when origin VLR is unknown from VMSC.
Counter incremented on emission of the RESTORE DATA Invoke message toward HLR.
Counter incremented on reception of the RESTORE DATA Result message from HLR.
ED 01
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
B.6.29 OB–VLR–SAISDRES (28) – Number of stand–alone Insert Subscriber data success sent
to HLR
Counters, per location area, incremented on reception of the CANCEL LOCATION component where the
IMSI is known and if its location area is known.
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”.
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
260
B.6.34 OB–VLR–SATTGSNA (55) – Subscribers currently registered in the VLR with status
”IMSI attach” and not ”GPRS detach”.
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”.
Counters, per target location area, incremented on reception of the UPDATE LOCATION AREA Invoke
component depending on the TargetLocAreaId parameter.
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.
Counter incremented on reception of the UPDATE LOCATION AREA Invoke component, whatever the
location area may be.
ED 01
260
B.7 –––––––––––––––––––– NR counters (278) ––––––––––––––––––––––––
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.
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.
Counter incremented on reception of the PAGE Error component or the SEARCH Error component.
Counter incremented on transmission of the PAGE Invoke component, for terminating calls.
Counter incremented on transmission of the PAGE Invoke component, for terminating short messages.
Counter incremented on reception of the PAGE Result component or the SEARCH Result component,
for terminating calls.
Counter incremented on reception of the PAGE Result component or the SEARCH Result component,
for terminating short messages.
Counter incremented on transmission of the SEARCH Invoke component, for terminating calls.
Counter incremented on transmission of the SEARCH Invoke component, for terminating short mes-
sages.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
Counter incremented on transmission of the PAGE Invoke
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.
Counter incremented on reception of the SET CIPHERING MODE Error component with the algorithm
incompatibility error code.
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”.
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.
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
260
B.9.10 OB–VSC–ENREAT (08) – TMSI reallocation failures
Counter incremented when the FORWARD NEW TMSI Result component timeout expires.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on transmission of the AUTHENTICATE Invoke component for subscriber with trip-
lets under GSM or UMTS coverage.
Counter incremented on transmission of the AUTHENTICATE Invoke component for subscribers with
quintuplets under UTRAN coverage
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.
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.
Counter incremented on transmission of the SET CIPHERING MODE Invoke component with quintuplets.
Counters, per supplementary service, incremented for a given service, determined by the ss code param-
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
– ACTIVATE SUPPLEMENTARY SERVICE Error,
– DEACTIVATE SUPPLEMENTARY SERVICE Error,
– INTERROGATE SUPPLEMENTARY SERVICE Error,
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on reception of the following component from the HLR (except for the automatic
relocation procedure):
– UNSTRUCTURED SS REQUEST invoke
Counter incremented on transmission of REGISTER PASSWORD Invoke message toward the HLR.
Counter incremented on reception of REGISTER PASSWORD Result message from the HLR.
Counter incremented on transmission of the following components towards the HLR (except for automatic
relocation procedure):
– UNSTRUCTURED SS REQUEST result
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
ED 01
260
– INTERROGATE SUPPLEMENTARY SERVICE Invoke,
Counter incremented on detection of refusal of an operation due to ODB of supplementary service man-
agement.
Counter incremented on sending the READY FOR SM Invoke phase 2 message to the HLR with alert
reason set to ”Memory available”.
Counter incremented on sending the READY FOR SM Invoke phase 2 message to the HLR with alert
reason set to ”MS present”.
Counter incremented on receipt of the READY FOR SM Result phase 2 message from the HLR due to
”Memory available” request.
Counter incremented on receipt of the READY FOR SM Result phase 2 message from the HLR due to
”MS present” request.
ED 01
260
B.12 –––––––––––––––––––– TC counters (206) ––––––––––––––––––––––––
Absent Subscriber
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented each time the PROVIDEROAMINGNUMBER Error is sent to the HLR with the
”AbsentSubscriber” error code.
Counter incremented each time the PROVIDEROAMINGNUMBER Error is sent to the HLR with the Faci-
lityNotSupported error code.
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.
Counter incremented each time the PROVIDEROAMINGNUMBER Invoke is received from the HLR.
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
260
APPENDIX C – HLR COUNTER IMPLEMENTATION
C.1 Warning.
In the following definitions, ”reception of the message” means reception of a message syntaxically valid
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.
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.
Counter indicating the total number of USS–N messages received from the SCF.
Counter indicating the total number of successful USS–N messages received from the SCF.
Counter indicating the total number of USS–R messages received from the SCF.
Counter indicating the total number of successful USS–R messages received from the SCF.
Counter indicating the total number of ATSI_I messages received from the SCF.
Counter indicating the total number of ATSI_R messages returned by the HLR to the SCF.
Counter indicating the total number of ATM_I messages received from the SCF.
Counter indicating the total number of ATM_R messages returned by the HLR to the SCF.
ED 01
260
C.3 –––––––––––––––––––– CC counters (197) ––––––––––––––––––––
Counter indicating the total number of CCBS related messages received or sent by the HLR (i.e. SSN of
CCBS–ASE used).
Total number of CCBS activation requests, namely number of received CCBS Request messages.
Counter incremented on receipt of the REMOTE USER FREE message from the HLR / DLE B.
Counter incremented on sending of the REMOTE USER FREE message to the HLR / OLE A.
Counter incremented on receipt of the STATUS REPORT message from the VLR, with call outcome =
”success” and for the A side.
Counter incremented on receipt of the STATUS REPORT message from the VLR, with call outcome =
”success” and for the B side.
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
completion. There is one counter per supplementary service related to call completion.
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
completion. There is one counter per supplementary service related to call completion.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
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
not permitted without written authorization from Alcatel.
call completion. There is one counter per supplementary service related to call completion.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
completion. There is one counter per supplementary service related to call completion.
C.6.1 OB–HCF–SODBFTN (01) – Number of operations refused due to ODB of FTN registration,
OC or TC
Counter incremented on transmission of the ACTIVATE TRACE MODE Invoke component toward VLR.
Counter incremented on reception of the ACTIVATE TRACE MODE Result from VLR.
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.
Counter incremented on reception of DELETE SUBSCRIBER DATA Result component from SGSN.
ED 01
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-
not permitted without written authorization from Alcatel.
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
Counter incremented at receipt of the Failure Report Invoke message from the 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
ED 01
260
C.8.16 OB–HGP–PURGEMSRES (12) – Number of PurgeMS result to 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.
Counter incremented on sending the SEND ROUTING INFO. FOR SHORT MESSAGE Result to a SMS–
GMSC supporting MT SMS over GPRS.
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
C.8.22 OB–HGP–SAISDREQ (09) – Number of stand–alone Insert Subscriber data request sent
to SGSN
Counter incremented on reception of the UPDATE GPRS LOCATION Invoke component from SGSN.
ED 01
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
Counter incremented on reception of Send Routing Info For Location services (LCS) invoke message
from the GMLC.
Counter incremented on sending of Send Routing Info For Location services (LCS) result message
to the GMLC.
Counter incremented on reception of the ANY TIME INTERROGATION Invoke message from the SCP.
Counter incremented on transmission of the ANY TIME INTERROGATION Result message to the SCP.
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.
Counter incremented on reception of DELETE SUBSCRIBER DATA Result component from VLR.
ED 01
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-
not permitted without written authorization from Alcatel.
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.14 OB–HLR–SAISDREQ (12) – Number of stand–alone Insert Subscriber data request sent
to VLR
ED 01
260
C.10.17 OB–HLR–SODBROAM (15) – Number of operations refused 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.
Counter incremented by the HLR on receiving an SEND ROUTING INFO Invoke with OR interrogation.
Counter incremented by the HLR when the call can be routed without contravening the charging require-
ments for optimal routeing (response with MSRN).
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
260
C.13 ––––––––––––––––––––– SC counters (110) –––––––––––––––––––
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).
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).
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,
Counter incremented on emission of the following component towards the VLR (except for the automatic
relocation procedure):
– UNSTRUCTURED SS REQUEST invoke
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
C.14.5 OB–HSH–REGPWREQ (05) – Register password request received
Counter incremented on reception of REGISTER PASSWORD Invoke message from the VLR.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on transmission of REGISTER PASSWORD Result message toward the VLR.
Counter incremented on reception of the following component from the VLR (except for the automatic
relocation procedure):
– UNSTRUCTURED SS REQUEST result
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,
Counter incremented on detection of refusal of an operation due to ODB of supplementary service man-
agement.
ED 01
260
C.15.3 OB–HSM–ISC (14) – Inform service center
Counter incremented on sending of the INFORM SERVICE CENTER message to the GMSC.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Counter incremented on receipt of the READY FOR SM Invoke phase 2 message from the VLR with alert
reason set to ”Memory available”
Counter incremented at the reception of the MS PRESENT phase 1 message from the VLR.
Counter incremented on receipt of the READY FOR SM Invoke phase 2 message from the VLR with alert
reason set to ”MS present”.
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).
Counter incremented at the reception of the SEND ROUTING INFO.FOR SHORT MESSAGE from the
GMSC.
Counter incremented on receipt of the ALERT SC Result phase 2 message from the IWMSC.
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
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.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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 sending the SEND ROUTING INFO. FOR SHORT MESSAGE Result to the
GMSC.
Counters, per E.164 PLMN address, incremented on reception of the PROVIDE ROAMING NUMBER fail-
ure from the VLR with the ”AbsentSubscriber” error code.
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.
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
260
C.17.4 OB–HTC–ENIREA (02) – Failures of interrogation for call rerouting
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.
Counters, per E.164 PLMN address, incremented on transmission of the PROVIDE ROAMING NUMBER
Request to the VLR.
Counters, per E.164 PLMN address, incremented on reception of the PROVIDE ROAMING NUMBER
Result from the VLR.
Counter incremented on reception of the SEND ROUTING INFO Invoke component in CAMEL case
(parameter Suppress TCSI present).
Counter incremented on detection of refusal of an incoming call due to ODB of incoming calls.
Counters, per observed translation result, incremented on each translator nvocation leading to this result.
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
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
not permitted without written authorization from Alcatel.
C.19.3 OB–HVH–SRGI–REJ (03) – Number of Send routing informations reject for optimal rout-
ing
C.19.4 OB–HVH–SRGISM–REJ (04) – Number of Send routing informations for SM reject for
optimal routing
ED 01
260
APPENDIX D OBSERVATION SCENARIOS
not permitted without written authorization from Alcatel.
CC
Authentication request
OBS: VSC –SDAUT(or UDAUT)
Authentication response
OBS: VSC –EDAUT(or EAUTH)
OR
Authentication failure
OBS: VSC –ERESYN or EAFAIL
end of LR procedure:
OBS:VCA–MMEVENTN
CLEAR COMMAND
CLEAR COMPLETE
1AA 00014 0004 (9007) A4 – ALICE 04.10
DDC
CDC
ED 01
260
D.2 LR INTER VLR
Mobile registration
CC
ED 01
260
MS BSS RCP VLR HLR
not permitted without written authorization from Alcatel.
OBS: VLR–NWVLRSPREQ
BEGIN (I SEND PARAMETER)
ph.2: BEGIN (I SEND IDENTIFICATION)
OBS: VLR–OLVLRSPREQ
OBS: VLR–OLVLRSPRES
OBS: VLR–NWVLRSPRES
OBS: VLR–CANLOC–HOM or
OBS: VLR–CANLOC–OTH
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
260
D.3 OC
Establishment (1)
CM service request
CCO
Setup
(1)
Call proceeding
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
260
MS BSS SMIM RCP HLR SSP
not permitted without written authorization from Alcatel.
Establishment (2)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
ASSIGNMENT REQUEST
OBS: FSW–SRIOC
OBS: HTC–SNIREA
OBS: HTC–ENIREA
END (RL SEND ROUTING INFO)
OBS: FSW–SRIOCRES
OBS: FSW–SRIOCCFU
OBS: FSW–SRIFWDVIOL
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
260
MS BSS SMIM RCP HLR SSP
not permitted without written authorization from Alcatel.
CONT (I CREATE)
OBS: FSW–SAEVRF
CONT (I EVENT ACM)
Alerting
Connect
Note 1: note that this counter can’t be compared per BSC to the OC number, since the BSC may have
changed (handover)
ED 01
260
D.4 PURE GATEWAY
Establishment
CONT (I CREATE)
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
260
MS BSS SMIM RCP HLR SSP
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
END (I FREE)
END (I FREE)
(1)
ED 01
260
D.5 GATEWAY + TC
Establishment (1)
(1)
BEGIN (I SEND ROUTING INFO)
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.
ED 01
260
MS BSS SMIM RCP HLR SSP
not permitted without written authorization from Alcatel.
Establishment (2)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Setup
Call confirmed
ASSIGNMENT REQUEST
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
260
MS BSS SMIM RCP HLR SSP
not permitted without written authorization from Alcatel.
Alert
Connect
Connect acknowledgement
(1)
Release –> see OC scenario
ED 01
260
D.6 TC
Establishment
OBS: FSW–SNAEMSC
PAGING
ED 01
260
D.7 GATEWAY + TC TO MS CONDITIONALY FORWARDED (no paging response)
OBS: FSW–SRICFMSC
ED 01
260
D.8 GATEWAY + TC TO MS CONDITIONALY FORWARDED (subs not reachable)
Setup
Call confirmed
ASSIGNMENT REQUEST
ASSIGNMENT FaiLuRe
END (I FREE)
ED 01
260
D.9 GSM to GSM HANDOVER (GSM only)
HO_REQuired
CREATE REtrieve
Retrieve Result
HO_REQUest
HO_REQuest ACK
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
260
MS BSC1 RCP SSP BSC2
not permitted without written authorization from Alcatel.
HO_CoMmanD
HO_COMplete
HO_COMplete
(1)
CLEAR_CoMmanD
CLEAR_COMplete
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
260
D.9.2 INTER–MSC HANDOVER
HO_REQuired
(1)
ph1 : PERForm_HO_Invoke
ph2 : PREPare_HO_Invoke
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
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
260
MS BSCA RCPA SSPA RCPB SSPB BSCB HLR
not permitted without written authorization from Alcatel.
MIF
PROV_INS
DETACH
ATTACH
GENSIG (ACM)
ACM
EVENT (ACM)
HO_CoMmanD
JOIN (Split)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
MS BSCA RCPA SSPA RCPB SSPB BSCB HLR
not permitted without written authorization from Alcatel.
HO_COMplete
HO_COMplete
(2)
GEN SIG (ANM)
ANM (RIU)
EVENT (ANM)
CLEAR_CoMmanD
CLEAR_COMplete
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
260
D.9.3 SUBSEQUENT HANDOVER (A –> B –> C)
HO_REQuired
(1)
ph1 : PERForm_SUBS_HO_Invoke
ph2 : PREPare_SUBS_HO_Invoke
(2)
CREATE REtrieve
Retrieve Result
(2)
HO_REQUest
HO_REQuest ACK
(2)
ph1 : PERForm_HO_Result
ph2 : PREPare_HO_Result
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
260
MS BSCB RCPB SSPB RCPA SSPA RCPC SSPC BSCC
not permitted without written authorization from Alcatel.
MIF
PROV_INS
DETACH
ATTACH
GENSIG (ACM)
(1)
JOIN (No immed exec)
ACM
EVENT (ACM)
ph1 : PERForm_SUBS_HO_RESult
ph2 : PREPare_SUBS_HO_RESult
Note 1: 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
260
MS BSCB RCPB SSPB RCPA SSPA RCPC SSPC BSCC
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
HO_DETect
HO_COMplete
HO_COMplete
(1)
Send End SIgnal Invoke
(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
Note 1: RCPC is in same situation as RCPB in inter–MSC case (TARGET). Same counters apply.
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
260
D.9.4 RETURN SUBSEQUENT HANDOVER (A–>B, B–>A)
HO_REQuired
(1)
ph1 : PERForm_SUBSequent_HO_Invoke
ph2 : PREPare_SUBSequent_HO_Invoke
(1)
OBS: FHO–SHORPSIA (/serving MSC)
CREATE REtrieve
Retrieve Result
(2)
ph1 : PERForm_SUBSequent_HO_Result
ph2 : PREPare_SUBSequent_HO_Result
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
260
MS BSCA RCPA SSPA RCPB SSPB BSCB HLR
not permitted without written authorization from Alcatel.
HO_CoMmanD
(1)
HO_CoMmanD
HO_COMplete
HO_COMplete
(2)
(1)
CLEAR_CoMmanD
CLEAR_COMplete
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
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).
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
ED 01
260
D.10.2 Intra MSC SRNS relocation
Source Target
RNC RNC
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Relocation command
OBS: FRE–SRECOM (02)
OBS: FRE–SRECOMA (07)
Relocation commit
Relocation
Relocation detect execution
Iu release command
Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
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
not permitted without written authorization from Alcatel.
relocation)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
260
D.10.3 Inter MSC (A –> B) SRNS relocation
Relocation required
OBS: FRE–SRERQ (01)
Prepare HO (Relocation request)
Create HO leg
IAM
Relocation command
OBS: FRE–SRECOM (02)
OBS: FRE–SRECOME (12)
Relocation commit
Relocation detect
ED 01
260
D.10.3.1Observation in Controlling MSC
a) The observation of the relocation preparation procedure is made by a couple of counters per source
RNC:
not permitted without written authorization from Alcatel.
• 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):
• 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.
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.
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).
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)
The relocation failures messages are not counted, they are considered as belonging to unsuccessful
end of this procedure.
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
260
D.10.4 Subsequent inter MSC SRNS relocation – three MSC involved (A–> B –> C)
Relocation required
OBS: FRE–SRERQ (01)
Prepare subsequent HO (Relocation request)
Create HO leg
IAM
Relocation command
OBS: FRE–SRECOM (02)
OBS: FRE–SRECOMS (26)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
Serving MSC Controlling MSC Target MSC
Relocation commit
Relocation detect
Relocation complete
ED 01
260
D.10.4.1Observation in Controlling MSC
• FRE–SRECOMPCS: Successfull end of the procedure: number of Send End Signal (relocation
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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):
• FHO–SPREPSS: Number of prepare subsequent 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–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.
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.
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.
ED 01
260
D.10.5 Return subsequent inter MSC SRNS relocation – two MSC involved (A–> B –> A)
Relocation required
OBS: FRE–SRERQ (01)
Prepare subsequent HO (Relocation request)
Relocation command
OBS: FRE–SRECOM (02)
OBS: FRE–SRECOMS (26)
Relocation commit
Relocation detect
Relocation complete
Iu release command
ED 01
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:
not permitted without written authorization from Alcatel.
• FRE–SREREQKR: Successfull end of the procedure: number of relocation request ack (inter–
MSC subsequent return)
The relocation failures messages are not counted, they are considered as belonging to unsuccessful
end of this procedure.
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.
ED 01
260
D.11 UMTS to GSM handover
Source
RNC
Handover request
Relocation command
OBS: FRE–SRECOM (02)
OBS: FRE–S2GCOMA (34)
Iu release command
Iu release complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
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)
• FRE–SRECOM: Successfull end of the procedure: number of relocation command (all type of
not permitted without written authorization from Alcatel.
handover)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
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 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
260
D.11.2 Inter MSC UTRAN to GSM handover
Relocation required
Create HO leg
IAM
Relocation command
Handover complete
Send End Signal (handover complete)
ED 01
260
D.11.2.1Observation in Controlling MSC
a) The observation of the handover preparation procedure is made by a couple of counters per source
RNC:
not permitted without written authorization from Alcatel.
• FRE–SRECOM: Successfull end of the procedure: number of relocation command (all type of
handover)
Same counters as for SRNS relocation.
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)
b) The observation of relocation cancel procedure is made by the counter per (source RNC, target
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
260
D.11.3 Subsequent inter MSC UTRAN to GSM handover – three MSC involved
Relocation required
OBS: FRE–SRERQ (01)
Prepare subsequent HO (Handover request)
Handover request
Create HO leg
IAM
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
260
Serving MSC Controlling MSC Target MSC
Handover detect
Handover complete
ED 01
260
D.11.3.1Observation in Controlling MSC
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)
• FRE–SRECOM: Successfull end of the procedure: number of relocation command (all type of
handover)
Same counters as for SRNS relocation.
In addition a counter per (source RNC, target LAC)
• FRE–S2GPREPSS: Number of prepare subsequent handover (inter–MSC subsequent)
may be compared with counters defined in c ).
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)
b) The observation of relocation cancel procedure is made by the counter per (source RNC, target
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
260
D.11.4 Return subsequent inter MSC UTRAN to GSM handover – two MSC involved
Relocation required
Relocation command
Handover complete
Iu release command
ED 01
260
D.11.4.1Observation in Controlling/target MSC
Same as for GSM–GSM inter–MSC subsequent return handover, see § D.9.4. The counters are not given
in the scenario above.
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
ED 01
260
D.12 GSM to UMTS handover
Source Target
BSC RNC
resource
Relocation request allocation
Handover command
OBS: FHO–SHOC (30706)
OBS: FHO–S3GCOMA (74)
handover to UTRAN
Clear command
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
a) The observation of the handover preparation procedure is made by a couple of counters per source
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
not permitted without written authorization from Alcatel.
handover)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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)
Same counters as for SRNS relocation.
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
260
D.12.2 Inter MSC GSM to UTRAN handover
Handover required
Create HO leg
IAM
Handover command
OBS: FHO–SHOC (30706)
OBS: FHO–S3GCOME (78)
handover to UTRAN
Relocation detect
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
D.12.2.1Observation in Controlling MSC
a) The observation of the handover preparation procedure is made by a couple of counters per source
BSC:
not permitted without written authorization from Alcatel.
• FHO–SHOC: Successfull end of the procedure: number of handover command (all type of
handover)
Same counters as for GSM–GSM handover.
In addition a counter per (source BSC, target RNC)
• 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).
ED 01
260
D.12.3 Subsequent inter MSC GSM to UTRAN handover – three MSC involved
Handover required
Create HO leg
IAM
Handover command
handover to UTRAN
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
Serving MSC Controlling MSC Target MSC
Relocation detect
Relocation complete
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
D.12.3.1Observation in Controlling MSC
• FHO–S3GCOMPCS: Successfull end of the procedure: number of Send End Signal (handover
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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.
a) The observation of the handover preparation procedure is made by a couple of counters per source
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)
Same counters as for GSM–GSM handover.
In addition a counter per (source BSC, target RNC)
• 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.
ED 01
260
D.12.4 Return subsequent inter MSC GSM to UTRAN handover – two MSC involved
Handover required
Relocation request
OBS: FRE–SREREQR (29)
Handover command
Relocation complete
Clear command
Release resource
Clear complete
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
D.12.4.1Observation in Controlling/target MSC
ED 01
260
D.13 IN SERVICES INVOCATION
BEGIN (I INITIALDP)
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
260
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
MS
01
BSS
D.14 SMIM INSERTION
SMIM
RCP
END (I CREATE)
260
AAC020023800DS
HLR
En
BEGIN (I PROVIDE INSTRUCTION)
SSP
253 / 260
D.15 SHORT MESSAGE TERMINATING (phase 2)
GMSC VMSC
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Successful case
CONNECTION REQUEST
CONNECTION CONFIRM
RP_MT_data
OBS : OB –HSM–ISC
SRG
CP DATA
RP_Data
OBS : OB –FSM–RCFREQ
CP ACK
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 01
260
SC RCP HLR RCP BSS MS
GMSC VMSC
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
CP DATA
RP_Ack
OBS : OB –FSM –SSMRX
CP ACK
RP_MT_ack
(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
260
SC RCP HLR RCP BSS MS
GMSC VMSC
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
260
SC RCF VLR HLR
IWMSC
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
UDT
RP–Alert
OBS : OB–FSM –ALSC
ED 01
260
D.16 SHORT MESSAGE ORIGINATING
MS RCF SMS–IWMSC SC
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
CP_DATA
CP_ACK
ForwardShortMessage
RP_MO_Data
ForwardShortMessage Result
CP_DATA
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
260
D.17 CAMEL CONTROL AND INTERROGATION OF SUBSCRIPTION DATA : ANY
TIME INFORMATION HANDLING
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
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
260
D.18 Mobile Terminating Location Request (MT_LR) LCS procedure
OBS:HLCS–SRIREQ
Send Routing Info for LCS result
OBS:HLCS–SRIRES
OBS:FLCS–MTLRREQ
OBS:FLCS–CURMTLRREQ or
OBS:FLCS–CRMTLRREQ
Page
OBS:VPG–PAGING–SM
Paging response
OBS:VPG–PAGSRCHRES–SM
OBS:FLCS–LOCNOTS
Release complete (LCS–Location Notification result)
OBS:FLCS–LOCNOTR
OBS:FLCS–CURMTLRRES or
OBS:FLCS–CRMTLRRES
1AA 00014 0004 (9007) A4 – ALICE 04.10
END OF DOCUMENT
ED 01
260