Alcatel Functional Specification for Short Message Service Terminating

FUNCTIONAL SPECIFICATION
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Options list in FS Short Message Terminating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 DETAILED DESCRIPTION AND SCENARIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Subscriber data related to SMSMT and Flags definition . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 SMS connection between the SC and the SMSGMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Establishment of the connection and determination of SMSAP version . . . . . . . . . . . . . 2.2.2 Forwarding of first Short Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Forwarding of Subsequent Short Message (phase 1 feature) . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Forwarding of Multiple Short Message (phase 2 feature) . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.5 Release of connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.6 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Retrieval of routing information procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 MSC number inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Forwarding of short message procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Messages; Forwarding of single short message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.2 Messages; Forwarding of multiple short messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.3 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Set Message waiting data and SM Delivery Status Report procedures . . . . . . . . . . . . . 2.6.1 SMSGMSC treatments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.2 HLR treatments at the reception of the message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.3 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7 Alerting Service Center procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.1 Alert procedure triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.2 Alert procedure at HLR level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.3 Alert procedure at IWMSC level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.4 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 04 03 01 980513 970926 9608 DATE CHANGE NOTE SYS/DFB SYS/DFB DSR APPRAISAL AUTHORITY F. SALIS Y.MARTY Y.MARTY ORIGINATOR 4 5 5 7 7 9 9 9 9 9 10 10 11 12 15 15 17 18 18 19 19 24 26 37 37 38 39 41 41 42 43 44
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
SHORT MESSAGE SERVICE TERMINATING SMT
ED
04 AAC020298400DS 135 En 1 / 135
CIT
3 INTERFACE MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
4 CONSEQUENCES OF V1 AND V2 MAP APPLICATION CONTEXTS MIX BETWEEN PLMN ENTITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1 Restrictions of feature induced by use of v1 context: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.2 Consequences of v1 and v2 Application Context mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5 INTERFACES WITHIN THE FUNCTION SHORT MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 MIRSMSSM: Interface between the GMSC and the SC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 MIRSMHSM: Interface between RCF and HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1 Send Routing Information for Short Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.2 InformServiceCentre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.3 Set Message Waiting Data / Report SM Delivery Status . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.4 AlertServiceCenterWithoutResult (Phase 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.5 Alert Service Center (Phase 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 MIRSMRSM : Interface between GMSC and VMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Forward Short Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 MIRSMVSM: Interface between servicing MSC and VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Send Information for SMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Complete Short Message Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Set MNRF flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 MIRSMBSM: Interface between RCF in VMSC and BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 CPDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.2 CPACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.3 CPERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.4 Specific defense treatments upon DTAP protocol (CPlayer) . . . . . . . . . . . . . . . . . . . . . . 5.6 MIRSMRSM : Interface inside the RCF in the VMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.1 MI_DBL_STR_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.2 MI_DBL_STR_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 INTERFACE WITH OTHER FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Security Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 Between VLR and HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.2 Within VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.3 Within RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 LOCATION REGISTRATION INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.1 Within HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2 Between VLR and RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3 Between VLR and HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Short message originating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 Paging Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1 Within VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.2 Within RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 Call Barring Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 Radio Resource Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Charging Data Collection Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 Observation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9 Supplementary Service Handling interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 MM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 SPONTANEOUS MESSAGES TO OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 53 53 53 56 57 59 60 61 61 63 63 63 64 65 65 67 68 68 69 69 69 70 70 70 71 72 72 72 72 73 73 73 73 73 74 74 74 74 74 75 76 77 77 78
1AA 00014 0004 (9007) A4 ALICE 04.10
8 ERROR GENERATED BY SMT FUNCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Definition of Internal errors generated by SM in HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Definition of Internal Errors generated by SM in VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
04 AAC020298400DS 135 En 2 / 135
CIT
8.3 Definition of internal errors generated by SM in RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 TIMERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Timer in RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1 SMSGMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.2 VMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.3 IWMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Timer in VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 Timer in HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SDL DIAGRAMS HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SDL DIAGRAMS VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 SDL DIAGRAMS RCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ANNEXE A OVERVIEW OF PROTOCOLS USED IN SMSMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1 Network structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2 Transfer protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.1 Simplified protocol layer overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.2 SC/PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.3 SMSGMSC/HLR and HLR/SMSIWMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.4 SMSGMSC/MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.5 VLR/HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.6 MSC/VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.7 MSC/MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78 81 81 81 81 82 82 82 83 97 101 131 131 131 131 132 132 133 133 133 134
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 3 / 135
CIT
LIST OF FIGURES AND TABLES

Figure 1. Functional environment of the Short Message terminating function . . . . . . . . . . . . . . . . . . Figure 2. SMS connection setup (1/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. SMS connection setup (2/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. SMS connection setup (3/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Retrieval of routing information from the HLR(1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. Retrieval of routing information from the HLR(2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. Channels used for short message transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Forwarding of short message (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. Forwarding of short message single transfer (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Forwarding of short message Multiple transfer (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. Forwarding of short message Multiple transfer (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. IMSI unknown (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. IMSI unknown (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14. Send info for SMT error (1/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 15. Send info for SMT error (2/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Send info for SMT error (3/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Check IMEI failure (4/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 18. Error case VMSC <> MS CP level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 19. Error case VMSC <> MS RP level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 20. Failure at the radio side (1/1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 21. Set message waiting data/ SM Delivery Status report Absent subscriber case . . . . . . Figure 22. Set message waiting data/ SM Delivery Status report Memory capacity exceeded case 40 Figure 23. SM Delivery Status report Successful delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 24. Alert procedure triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 25. Alert service center (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 26. Alert service center (2/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 27. Alert service center (3/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 28. Alert service center (4/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 29. Alert service center (5/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 30. Short Message Service Funtional Matrix(1/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 31. Short Message Service Funtional Matrix(2/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 32. Short Message Service Funtional Matrix(3/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 33. Send Routing Information for Short Message : messages layout . . . . . . . . . . . . . . . . . . . Figure 34. Set Message Waiting Data : messages layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 35. Report SM Delivery Status : messages layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 36. Alert Service Center Without Result message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 37. Alert Service Center message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 38. Forward Short Message: messages layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 39. Send Information for SMT : messages layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 40. Complete SMT call: message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 41. Set MNRF flag : messages layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 42. CPDATA message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 43. RPData message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 44. RPError message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 45. RPAck message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 46. CPACK message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 47. CPERROR message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 48. ReadyForSM (VLR>HLR) message layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 49. Note MSpresent (HLR LR>HLR SMT) message layout . . . . . . . . . . . . . . . . . . . . . . . . . 8 12 13 14 17 17 22 26 27 28 29 29 30 31 32 33 34 35 35 36 39 .. 40 41 44 45 45 46 47 48 49 50 54 57 58 59 60 61 63 64 64 65 66 66 67 68 68 71 72
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 4 / 135
CIT
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01 on 960830 Creation 04 on 980513 Updated 03 on 970926 Updating by RT/DM 02 on 970314 Updating by RT/DM
CIT
HISTORY
04
AAC020298400DS
135
En
5 / 135
REFERENCED DOCUMENTS
[1]
AAC020298400DT Mobile Terminating point to point SMS AAC030546400DT Mobile Originating point to point SMS AAC030546400DS Mobile Originating point to point SMS AAC030205400DS SMSAP MSC SC protocol for SMS AAC020006400DS Terminating call AAC020003400DS Paging AAC020010400DS Security AAC020015400DS Radio Resource Management AAC020097400DS Internal and external Error Mapping
[2] [3] [4] [5] [6] [7] [8] [9]
[10] AAC020004400DS Location Registration [11] AAC020023400DS Observations [12] AAC020018400DS Call Barring [13] AAC020017400DS Charging Data Collection [14] AAC020030400DS Supplementary Service Handling [15] AAC020016400DS Traduction [16] AAC020754400DS Version handling [17] AAC020031400DS Defence of PLMN [18] AAC030508400DS Operator Determined Barring [19] AAC020748400DS Application document for GSM PH.2 TS 09.02 (MSC/VLR behaviour) [20] AAC020747400DS Application document for GSM PH.2 TS 09.02 (HLR behaviour) [21] Functional Options List (note 1) Note 1 : One document per customer
GLOSSARY
1AA 00014 0004 (9007) A4 ALICE 04.10
BSSAP BSSMAP DTAP DT1 HLR HLR SMT MAP MCEF 04
Base Station System Application Part Base Station System Management Application Part Direct Transfer Application Part Data Form 1 Home Location Register HLR Short Message terminating Function Mobile Application Part Memory Capacity Exceeded Flag
ED
CIT
AAC020298400DS 135
En
6 / 135
MNR MWD MWI MS MSC RCF RCF SMT RPDU SAPI SC SCCP SMT SMO SM MT PP SM MO PP SMS SMSAP SMS GMSC SMS IWMSC SMS VMSC TPDU UDT VLR VLR SMT
Mobile station Not Reachable Flag Messages Waiting Data Messages Waiting Indication Mobile Station Mobile Services Switching Center Radio Control Function RCF Short Message Function Relay Protocol Data Unit Service Access Point Identifier Service Center Signalling Connection Control Part Short Message Terminating Function Short Message Originating Function Short Message Mobile Terminating Point To Point Short Message Mobile Originating Point To Point Short Message Service Short Message Service Application Part Gateway MSC for short messages service Interworking MSC for short messages service Visited MSC for short messages service Transfer Protocol Data Unit Unit DaTa Visited Location Register VLR Short Message terminating Function
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 7 / 135
CIT
1 INTRODUCTION
The general description of a Mobile Terminating SMS PP function is given in the associated feature description (see [1] page 6). The SM MT PP is a teleservice offered by the short message point to point function: the general purpose of the function, within the PLMN, is to transfer short messages from a SC to the MS (TPDU SMSDELIVER) or a status report from a SC to the MS (TPDU SMSSTATUSREPORT associated with a previous SMSMO procedure). In this document, the term short message is used by extension to design both cases. Therefore a mobile terminating short message procedure has to perform all the actions needed to establish a transaction for Short message transfer required by a Service Center towards the MS, to guarantee the short message forwarding, to handle the failure cases that may arise during the setup of the transaction or the forwarding of the message and to report to the SC the result of the message transfer attempt. The PLMN entities will handle also the alert procedure in order to inform the SC that the MS has recovered operation or has recovered available memory (phase 2 dialogue only). To perform correctly the short message transfer, the SMT (Short Message Terminating) function is implemented in the PLMN entities. The HLR SMT has to provide the routing information requested by the RCF SMT (acting as SMS GMSC) and to handle all the different kind of error report. It has to handle also the Set Message Waiting Data procedure (phase 1) or SM delivery status report procedure (phase 2) on request from RCF SMT in SMSGMSC. Besides it has to handle the Alert procedure towards the IWMSC. The VLR SMT has to provide the information needed to complete the call towards the MS (e.g. by the authentication or the ciphering procedure). Besides it has to handle the failures related to the terminating call and the procedure to inform the SC (via the HLR) that the MS is again reachable (MS present). N.B. The VLR SMO function has to handle the procedure to inform the HLR that the MS has recovered available memory.
The RCF SMT in the SMSGMSC has to perform the forwarding of the Short Message between the SMSGMSC and the SMSVMSC. Besides it has to initiate the Set Message Waiting Data procedure (phase 1) or SM Delivery Status Report procedure (phase 2) towards the HLR and all the failures of the message transfer attempt. The RCF SMT in the SMS_VMSC has to perform the forwarding of the short message between the VMSC and the MS. Besides it has to handle all the failure condition (i.e. failure detected by the SMT function in the VLR, SM delivery failure). The RCF SMT in the IWMSC has to handle the Alert procedure towards the Service Center.
1.1 Options list in FS Short Message Terminating

FSMS001 FSMS002 FSMS003 FSMS004 FSMS005 FSMS006 FSMS007 Addressing mode of SMS IWMSC VMSC and GMSC supports SMS SMS offered with IMSI unknown,including an update location Handling in HLR of the priority on SM delivery Special use of SRI for SM as MSC number inquiry HLR protection against optimal routing for SMSMT SDCCh assignment for SMS
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 8 / 135
CIT
FODB001 FHB001 FSC011

Operator Determined Barring function Hot billing option Authentication 1/n
BSS PA MS
RCF SC OB
Service Center
SMS function
SMT
RM
CG
VLR PA RCF SMT SMT SC CB
HLR LR
SMT
OB
LR SMO
OB
Abreviations : CB : Call Barring SC : Security PA : Paging CG : Charging OB : Observation RM : Radio Management LR : Location Registration SMT : Short Message Terminating SMO: Short Message Originating
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. Functional environment of the Short Message terminating function
ED
04 AAC020298400DS 135 En 9 / 135
CIT
2 DETAILED DESCRIPTION AND SCENARIOS 2.1 Subscriber data related to SMSMT and Flags definition
a) b) In the HLR, the MSISDNAlert indicator marks the MSISDN to be used as MSISDNAlert. As part of MessagesWaitingIndication (MWI), the MessagesWaitingData (MWD) is stored in the HLR against the subscriber MSISDNAlert. MWD consists of an address list of the SCs which have messages waiting to be delivered to the MS. As part of MessagesWaitingIndication (MWI), the MobileStationNotReachableFlag (MNRF) is stored in the VLR and the HLR. MNRF is a boolean indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message has failed at VLR with Absent Subscriber cause due to the MS temporarily absent. due to the MS located in a non authorized area (due to national roaming, regional subscription or unsupported feature in the current VLR). As part of MessagesWaitingIndication (MWI), the MobileStationMemoryCapacityExceeded Flag (MCEF) is stored only in the HLR. MCEF is a boolean indicating SM Delivery failure due to MS Memory Capacity Exceeded.
c)
d)
2.2 SMS connection between the SC and the SMSGMSC

2.2.1 Establishment of the connection and determination of SMSAP version See < [4] page 6>. 2.2.2 Forwarding of first Short Message When connection is established, the SC sends the message DATA FORM 1 (SCCP class 2 message) to the SMS GMSC to carry the first short message (as a user data). The MT SMS PP procedure at the GMSC is then started by the SMT function which checks the RP_MT_Data content. If no error is detected, the procedure continues in the normal way with retreival of routing information procedure (see section 2.3 page 16). If any error is detected in the layout of the RP_MT_Data message, DATA FORM 1 (SCCP class 2 message) is sent by the SMS GMSC (SMT function) to inform the SC about the failure of the RP_MT_Data message transfer attempt. The DT1 message contains as user data parameter the RP_MT_Error message including the RP_cause element. When GMSC is informed of the successful end of retrieval of routing information, i.e. on reception of MI_S_RGI_SM_R from the HLR, the Forward Short Message procedure is started by sending to the VMSC the MI_F_SM_I message (see section 2.5 page 20). In case of unsuccessful retrieval of routing information, i.e. on reception of MI_S_RGI_SM_E from the HLR, SMT fonction in GMSC informs the SC about the failure of the RP_MT_Data message transfer attempt by sending the message DATA FORM 1 (SCCP class 2 message) which contains as user data parameter the RP_MT_Error message.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 10 / 135
CIT
2.2.2.1 End of the forwarding of first Short message in SMS GMSC When GMSC, waiting for response from VMSC, receives MI_F_SM_R message, it triggers the SM Delivery Status Report procedure in case of phase 2 dialogue with HLR, if MCEF and/or MNRF is known to be set in HLR (refer 2.6 page 38); Then, it sends DATA FORM 1 (SCCP class 2 message) to the service center. The DT1 message contains as user data parameter the RP_MT_Ack message which indicates that the mobile terminating SM procedure has been correctly completed. If the GMSC receives MI_F_SM_E message, it means that forwarding of the Short Message to the MS has failed. The RCF SMT of the GMSC informs the SC about the failure of the RP_MT_Data message transfer attempt by sending the message DATA FORM 1 (SCCP class 2 message) which carries as user data parameter the RP_MT_Error message. 2.2.3 Forwarding of Subsequent Short Message (phase 1 feature) This procedure is used by the SC and the SMSGMSC when the dialogue between both entities is based on SMSAP V1 protocol. After each DATA FORM 1 message, carrying a RP_MT_Error message when SM transfer has failed or carrying a RP_MT_Ack message when SM transfer has been successful, sent to the SC, SMT in GMSC waits for a DATA FORM 1 message carrying a subsequent short message to forward. When a subsequent RP_MT_Data is received, SMT in GMSC checks its content and verifies that the subsequent Short message is to be sent to the same MS than the previous Short Message. If it is not the case, a DATA FORM 1(SCCP class 2 message) message which carries as user data parameter the RP_MT_Error message is sent to the SC. If a subsequent RP_MT_Data is received when retrieval of routing information for the previous Short Message has not been done or has been unsuccessful, SMT in GMSC starts again retrieval of routing information procedure before to forward the SM to the VMSC (like for the first RP_MT_Data). If a subsequent RP_MT_Data is received when retrieval of routing information has been successful and forward short message procedure has been initiated for the previous short message, SMT in GMSC starts directly the Forward Short Message procedure for this subsequent Short Message. If SMT in GMSC receives a RP_MT_Data from the SC when there is already a Short Message being treated with no report already sent to the SC, DATA FORM 1 message which carries as user data parameter the RP_MT_Error message is sent to the SC.
N.B.
2.2.3.1 End of the forwarding of subsequent Short message in SMS GMSC Same handling as for the first one. 2.2.4 Forwarding of Multiple Short Message (phase 2 feature) This procedure may be used by the SC and the SMSGMSC when the dialogue between both entities is based on SMSAP V2 protocol.
1AA 00014 0004 (9007) A4 ALICE 04.10
The SC informs the SMSGMSC that a subsequent short message will follow in inserting the More Message To send parameter in a RPMTData. This parameter is forwarded towards the VMSC (See < 2.5.2 page 25>). At the end of short message transfer procedure (sending of RPMTAck), the SMSGMSC will be waiting for another subsequent message.
ED
04 AAC020298400DS 135 En 11 / 135
CIT
If a RPMTError is returned to SC instead RPMTAck (procedure unsuccessful), no more subsequent message will be expected by SMSGMSC.
The handling of subsequent short message is the same as above. 2.2.5 Release of connection The release of the SMS connection and therefore of the short message procedure may be requested either by the SC, the GMSC or the MS. 2.2.5.1 Release requested by the SC (Normal release). The procedure is started by sending the message RELEASED (SCCP class 2 RLSD) to the GMSC. At the reception of the message the resources involved in the procedure have to be released, that is the GMSC releases the TCAP transaction towards the VMSC or the HLR (if still active) by sending an Abort Request message and replies to the SC by sending the RELEASECONFIRM (SCCP class 2 RLC) message. 2.2.5.2 Release requested by the MS In this case the radio side (BSS) releases autonomously the short message procedure and then informs the VMSC by sending the SAPInCLRCMND message. The SC is not informed about the release since the message from the BSC is ignored. N.B. The short message release procedure is implicitly invoked on reception from the BSC of a CLEAR REQUEST message due to the detection of radio failures (on the SAPI 3 as well as on the SAPI 0) implying the release of all the radio resources.
For further details, see [8] page 6. 2.2.5.3 Release requested by the GMSC A timer (TSCRLS) supervises at the GMSC the release of the SCCP connection from the SC. It will be started on sending the RP_MT_Ack message (or RP_MT_Error) and stopped at the reception of either a RP_MT_Data message or a RLSD message. At the expiry of the timer the GMSC releases autonomously the SCCP connection by sending the RLSD message to the SC.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 12 / 135
CIT
2.2.6 Scenarios 2.2.6.1 Successful case

FORWARDING OF SINGLE SHORT MESSAGE SMSGMSC SC RCF Connection Request Connection Confirm Data Form 1 (RP MTData) RPMTdata is tested by SMT function Send Routing information (TC_BEGIN) Send Routing information (TC_END) Forward Short Message (TC_BEGIN) Forward Short Message Res (TC_END) Data Form 1 (RP MTAck) Released Release confirm toward HLR Res from HLR toward VMSC from VMSC
Figure 2. SMS connection setup (1/3)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 13 / 135
CIT
FORWARDING OF MULTIPLE SHORT MESSAGES SMSGMSC

SC RCF Connection Request Connection Confirm Data Form 1 (RPMTData) Send Routing information (TC_BEGIN) Send Routing information (TC_END) Forward Short Message (TC_BEGIN) Forward Short Message Res (TC_CONT) Data Form 1 (RP MTAck) Data Form 1 (RP MTData) Forward Short Message (TC_CONT) Forward Short Message Res (TC_END) Data Form 1 (RP MTAck) Released Release confirm toward VMSC from VMSC toward HLR Res from HLR toward VMSC from VMSC
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 14 / 135
CIT
2.2.6.2 Unsuccessful cases PARAMETERS ERROR DETECTED AT APPLICATION LEVEL

SMSGMSC SC RCF Data Form 1 (RPMTData the RPMTData message is tested by the SMT function which detects errors in the message layout (i.e. mandatory information element error, information el. not Data Form 1 implemented) (RP MTError)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 15 / 135
CIT
2.3 Retrieval of routing information procedure

2.3.1 Messages 2.3.1.1 MI_S_RGI_SM_I (MAP Send Routing Information for SM) a) This message is sent by the RCF SMT of the GMSC to the HLR SMT retrieved from the MSISDN number. On receipt by the HLR, if the functional option FSMS006 is applicable, the message is rejected if the originating SMSGMSC does not belong to HPLMN. For all that, if the dialogue between SMS GMSC and HLR is phase 2, the dialogue is aborted by SMT function with a TCUABORT . If the dialogue between SMSGMSC and HLR is phase 1, RCF SMT function sends a TCREJECT. If the operation has to be handled, SMT in HLR : verifies the validity of the message fields; verifies that the MS can be identified from the MSIsdn number; verifies that the MS does not contravene Operator Determined Barring if FODB001 is active, or that the MS is not locked verifies that the mobile subscription, identified by the MSIsdn number, comprises the MT SM service; verifies that the MS is not deregistered; verifies that the VMSC where the MS is roaming has the SMS capability (SMSMT flag is set); verifies that roaming is allowed for this subscriber (see [10] page 6 If anyone of the checks fails the SMT HLR sends to the RCF SMT (GMSC) the message MI_S_RGI_SM_E (MAP SM Routing Information error for SM) containing a cause field identifying the failure. The cause Absent Subscriber indicates that the MS is deregistered or that roaming is not allowed in that MSC area and in this case, the HLR will include, if possible, the new SC address in the MWD. If the checks are successful the HLR SMT sends the message MI_ICB_CHECK (Internal message) to CB function in HLR to check whether the incoming call is barred or not. If the call is barred the HLR CB sends to the HLR SMT the message MI_ICB (call barred). At the reception of the message the HLR SMT sends to the RCF SMT (in the GMSC) the message MI_S_RGI_SM_E(MAP SM Routing Information error) including as error the Call barred indication. If the call is not barred the HLR CB sends to the HLR SMT the message MI_NO_ICB (Internal message indicating No Barring). The optionnal function FSMS004 indicates if the priority feature is handled in HLR to deliver Short Message. If FSMS004 is not applicable, the message is assumed to be nonpriority message and the parameter SM_RP_PRI is ignored. If FSMS004 is applicable, the parameter SM_RP_PRI is taken into account (SM_RP_PRI = true indicates the message is a priority one, SM_RP_PRI = false, a nonpriority message). The message MI_S_RGI_SM_R reporting routing informations is sent to RCF SMT in GMSC as follows:
1AA 00014 0004 (9007) A4 ALICE 04.10
b)
If the message is a priority one. N.B. MNRF and/or MCEF flags set in HLR do not prevent the routing of the message in this case.
ED
04 AAC020298400DS 135 En 16 / 135
CIT
If the message is a nonpriority message and the MNRF flag is not set in HLR database. N.B. MCEF flag set in HLR does not prevent the routing of a short message to VMSC.
In the opposite, the message MI_S_RGI_SM_E reporting Absent subscriber error is sent to RCF SMT in GMSC if the message is a nonpriority message and the MNRF flag is set in HLR database. Furthermore, in this case, the HLR includes the SC address in MWD, if SC address is not already in MWD and if MWD is not full. N.B. MNRF flag is set only when the MS is not reachable at VMSC level.
2.3.1.2 MI_I_SC_I (MAP Phase 2 Inform Service Centre) This message is sent by the HLR in phase 2 dialogue with SMSGMSC in the same message as SendRoutingInfo error or result: After the HLR has sent a SendRoutingInfoForSM error The InformServiceCenter is only sent in case of Absent subscriber error. The storedMSISDN parameter is included if the MSISDN of SendRoutingInfoForSM invoke is not the same as MSISDNAlert used in MWD file. The mwStatus parameter is always included. After the HLR has sent a SendRoutingInfoForSM result The InformServiceCenter is sent if: either MNRF or MCEF flag or both are set in HLR, The mwStatus parameter is then included with mnrfset and/or mcefset. The SCAddressNotIncluded is set if SC address is not in MWD list. the MSISDN of SendRoutingInfoForSM invoke is not the same as MSISDNAlert. The storedMSISDN parameter is then filled with MSISDNAlert. In phase 1 dialogue between HLR and SMSGMSC, the mwdset parameter is always included in SendRoutingInfoForSM result MI_S_RGI_SM_R, in SendRoutingInfoForSM error MI_S_RGI_SM_E in case of Absent subscriber error. Refer to message description < 5.2.1 page 54>. 2.3.1.3 After retrieval of routing information procedure a) If MI_S_RGI_SM_R has been received in RCF SMT in GMSC, the routing information is available and the procedure continues in the normal way (see section 2.5 page 20). If MISRGISME has been received the GMSC (SMT function in RCF) informs the SC about the failure of the RPData message transfer attempt by sending the message: DATA FORM 1(SCCP class 2 message) which contains as user data parameter the RP_MT_Error message.
b)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 17 / 135
CIT
2.3.2 Scenarios 2.3.2.1 Successful case

Successful case in phase 1 dialogue with HLR Successful case in phase 2 dialogue with HLR (MCEF and MNRF not set, MSISDN = MSISDNAlert)
SMSGMSC SMT MIS RGISMI (TCBegin)
HLR SMT CB
MIICBCHECK MINOICB MISRGISMR (TCEnd) forward short message towards VMSC
Figure 5. Retrieval of routing information from the HLR(1/2)
Successful case with phase 2 dialogue with HLR (MCEF and/or MNRF set) and/or (MSISDN <> MSISDNAlert)
SMSGMSC SMT MISRGISMI (TCBegin)
HLR SMT CB
MIICBCHECK MINOICB MISRGISMR MIISCI (TCEnd) forward short message towards VMSC
Figure 6. Retrieval of routing information from the HLR(2/2)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 18 / 135
CIT
2.4 MSC number inquiry

If the option FSMS005 is set and a particular private numbering plan used for MSISDN indicates the special message usage, the following applies. 2.4.1 Messages MI_S_RGI_SM_I(MAP Send Routing Information for SM) This message is sent in order to retrieve the address of the MSC in which area the MS is currently registered in. At the reception of this message SMT in HLR : verifies the validity of the message fields; verifies that the MS can be identified from the MSIsdn number; verifies that the MS is not locked; verifies that roaming is allowed for this subscriber (see [15] page 6 If anyone of the checks fails, the SMT HLR returns the message MI_S_RGI_SM_E(MAP Send Routing Information For SM error) containing a cause field identifying the failure. The cause absent subscriber indicates that the MS is not registered. In the successful case, the message MI_S_RGI_SM_R (MAP Send Routing Information For SM result) reporting the address of the MSC the MS concerned is controlled by is sent back to the requesting entity.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 19 / 135
CIT
2.5 Forwarding of short message procedure

2.5.1 Messages; Forwarding of single short message N.B. This paragraph concerns only the forwarding of a single short message, the multiple short message case is described separately.
2.5.1.1 SMS GMSC <> SMS VMSC <> VLR interface a) MIFSMI(MAP Forward short message) This message is sent by the RCF SMT of the GMSC to the RCF SMT of the VMSC to request the forwarding of an MS terminated short message. After the determination of the MAP dialogue version, some checks are performed to determine if the length of User data allows the MAP transfer and, in the positive case, if segmentation is needed for MAP version > 1. Three system parameters are defined: L1 Max length of User data supported by MAP, whatever MAP version. L2 Max length of User data supported by a MAP version > 1 with segmenting process. L3 Max length of User data which can be carried by a MAP version > 1 without segmenting. If User data length <= L3, then no segmenting process is needed, whatever MAP version of dialogue. If L3 < User data length <= L2, then segmenting process is required if the MAP version of dialogue is > 1. If L1 < User data length, the RP_MT_DATA is rejected during the check of the parameters ( see 2.2.2 page 10) just after the receipt of the message from the SC. If segmenting would be needed, TCBEGIN is sent with ACN, with or without USI (< 5.3.1 page 62>) and without component to open the dialogue with the VMSC, and after the reception of an empty TC CONT, a TCCONT is sent with TCINVOKE component. After the sending, RCF SMT in GMSC waits for the response from RCF SMT in VMSC. N.B. MAP interface is maintained even if the GMSC and the VMSC are colocated. Yet, in this case the interface is internal within MSC/VLR.
b)
At the reception of the message, RCF SMT in VMSC verifies that it supports the short message service (FSMS002 option is active). In case the option FSMS002 is inactive, RCF SMT in VMSC sends to RCF SMT in GMSC the message MIFSME. Then, the RCF SMT in VMSC verifies the parameters of the message (see < 5.3.1 page 62>). In case of error, it sends to the RCF SMT in GMSC the message MIFSME(MAP Short message forwarding error). If the message from the GMSC is correctly received, RCF SMT in VMSC sends to the VLR SMT in VMSC the message MI_SINF_SMT_I (Specific RCFVLR interface message).
c)
At the reception of the message, the VLR verifies that the IMSI is known. If the IMSI is unknown (unknown at the VLR but known at the HLR)
1AA 00014 0004 (9007) A4 ALICE 04.10
If FSMS003 function is offered, a searching procedure is attempted and VLR SMT asks VLR PA for searching by sending MI_SEAR_SMT_REQ message.
ED
04 AAC020298400DS 135 En 20 / 135
CIT
If Searching succeeds, it will result in an update location toward the HLR after authentification. (if the MS answers with TMSI to the paging request, SM delivery will fail).
If FSMS003 function is not offered, the treatment specified by the GSM applies (i.e VLR SMT sends to RCF SMT in VMSC the message MI_SINF_SMT_E with cause Unidentified subscriber).
If the IMSI is known, then VLR verifies that the IMSI is not detached and that the LA is allowed (see [10] page 6 If the IMSI is detached or if the LA is not allowed, VLR SMT sends to RCF SMT in VMSC the message MI_SINF_SMT_E with cause Absent subscriber, after having set to true the MNRF flag. The VLR verifies also that the subscriber data are available (flag MSDATAKNOWN see [10] page 6. If the subscriber data are not available, the VLR SMT sends to RCF SMT in VMSC the message MI_SINF_SMT_E with cause Unidentified subscriber. At the reception of the message MI_SINF_SMT_E, RCF SMT in VMSC sends MI_F_SM_E to the RCF SMT in GMSC including the reason of the failure. If the checks are successful, (IMSI known, data known, not detached and LA allowed) SMT in VLR asks PA in VLR for paging by sending MI_PAGE_SMT_REQ (Internal message) in order to establish the radio contact with the called MS. If the functional option FSMS007 is activated, a Channel seizure is sent by PA function to RM function after the Paging response to allocate a SDDCH. This message is not sent if the parameter chosen channel is present and set to SDCCH in paging response. For further details about paging (or searching) procedure for an SMT transaction, see [6] page 6. If the VLR has an IMSI marked LA not known the VLR handles the request in the normal way, except that SMT in VLR sends MI_SEAR_SMT_REQ to PA in the VLR. MI_PAGE_SMT_ACK is sent back by PA to SMT in VLR when paging is successful. It contains the status of the connection which is established with the called MS on the radio side. In case of paging failure or if the mobile is not SMS equipped (Classmark 2 SM capability), the message sent back by PA to SMT in VLR is MI_PAGE_SMT_NACK In case of paging failure due to Not SMS equipped the security procedure is nevertheless started and, if succeeded, SMDeliveryfailure(MSNotEquipped) will be forwarded in ForwardShortMessage error. If the security procedure failed, the paging error is forgotten and security error is taken into account. MI_VSM_SC_REQ (Internal message) is sent by SMT in VLR to SC in VLR in order to perform, if needed, MS authentification, TMSI reallocation and ciphering command. Information received in the MI_PAGE_SMT_ACK is used. MI_VSM_SC_RES (Internal message) is sent back by SC in VLR to SMT in VLR when security related operations have been performed successfuly. In case of security failure, the message sent back by SC to SMT in VLR is MI_VSM_SC_ERR After a good completion of PA and SC actions, MI_COM_SMT_I (Specific RCFVLR interface message) is sent by SMT in VLR to SMT in RCF, indicating that the SMT call can be offered to the MS.
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
If there is an other transaction waiting for the end of MM procedures, SMT in RCF sends a MI_DBL_STR_RES message to inform the awaiting transactions that its MM procedure has finished with success. 04 AAC020298400DS 135 En 21 / 135
ED
CIT
If the MS is currently involved in a Location Registration procedure when a short message is to be offered to the MS, as LR function in RCF never registers the IMSI (in its context data), PA function in RCF will not be aware that the MS is running a MM procedure. The LR procedure will normally succeed, and the PA procedure will fail in case of LAC change. The paging may succeed (due to paging repetition) if the LR procedure is a periodic one (no LAC change). e) RCF SMT in VMSC waits for result of IMEI checking from Security before sending the short message to the mobile. MI_IMEI_ACK (Internal message) is sent back by Security in RCF to SMT in RCF at the end of the check IMEI process. If case of IMEI check failure (e.g.black list) MI_IMEI_NACK is sent back by Security to SMT in RCF. A message MI_F_SM_E is then forwarded to the GMSC. RCF SMT in VMSC waits for result of the Short Message transfer before sending any response to RCF SMT in GMSC. f) Description of the Short Message delivery to the MS (RCF SMT in VMSC <> MS interface) is described at section 2.5.1.2 page 22. Error cases If paging or security has failed, VLR SMT sends MI_SINF_SMT_E to RCF SMT, containing the failure cause. If there is an other transaction waiting for the end of MM procedures, SMT in RCF sends a MI_DBL_STR_ERR message to inform the awaiting transactions that its MM procedure has finished with error. N.B. If the MS has not answered to the paging (cause Absent Subscriber), the VLR sets the MNRF flag to true.
g)
At the reception of this message RCF SMT in VMSC sends MI_F_SM_E (MAP Forward Short Message Error) to the RCF SMT in GMSC including the reason of the failure. h) On reception of an acknowledge from the MS that the SM has been correctly received (RPACK), the VMSC sends MI_F_SM_R (MAP Forward short message Result) to the RCF SMT of the SMS GMSC. It doesnt contain user data field since it only indicates that the message transfer to the MS has been successfully completed; In case of failure of a short message transfer to the MS, the VMSC sends MI_F_SM_E to the RCF SMT in SMSGMSC. For further details about failure causes, see 2.5.1.2 page 22. The end of the Forward Short Message procedure in SMSGMSC is described at section 2.2.2 page 10 2.5.1.2 MSC <> BSC BSSAP interface At the reception of the MICOMSMTI confirming that the MS has been reached, the RCF SMT function is ready to forward the RPData message to the MS (via the BSSMAP of the BSC).
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
An SMT transaction can take place during an OC or a TC or an SH or several others SMT transactions. But only ONE Short Message can be sent to the MS at one and the same time; as several Short Messages can arrive at the same time for the same MS (from different Service Centers), SMT function in RCF in VMSC has to serialize the distribution of Short Messages to the MS. 04 AAC020298400DS 135 En 22 / 135
ED
CIT
So before to send the RP_Data, SMT tests if there is an other transaction sending a Short Message to the MS : If there is one, SMT has to wait for the end of the transaction, which will be signalled to it with MI_DBL_STR_RES message from an other SMT transaction, before to send RP_Data. If there is not, RP_Data can be sent at once. a) The RPData is sent within the user data of a CPDATA (DTAP message) message. The CPDATA will be the user data of a SCCP DATA IND message carrying a DTAP message (that is to say the layer 3 Information sent to the BSS within a SCCP DATAIND message) and will be identified by the following Distribution Data Unit: Discriminator parameter = 1 DLCI = C2 C1 000 S3 S2 S1 Where S3 S2 S1 = SAPI 3 = short message = 3 C2 C1 = radio channel on which the short message has to be transferred (only significant for phase 1 BSS) Value 0 is set by the MSC irrespective of the BSC type. The SDCCH or SACCH will be used according to the fact that the TCH is already allocated (when the Short Message has to be sent) or not : if the TCH is allocated (a transaction using SAPI 0 is active on a TCH), the short message is transferred on the SACCH, if the TCH is not allocated (a transaction using SAPI 0 is active on a SDCCH), the short message is transferred on the SDCCH, if the TCH is allocated during the short message transfer (a transaction on a TCH is in progress (using SAPI 0)), the short message will be moved, at the radio side, from the SDCCH to the SACCH; if a transaction on TCH using SAPI 0 is terminated but the short message transfer is still active, the TCH is maintained as long as the short messages procedure is activated. The following table summarizes the channels use:
Channel dependency TCH not allocated TCH not allocated > TCH allocated TCH allocated TCH allocated > TCH not allocated
Channel used SDCCH SDCCH > SACCH SACCH SACCH > SACCH
Figure 7. Channels used for short message transfer b) The MS acknowledges the CPDATA message by sending the message CPACK(DTAP message) which doesnt contain user information and which is forwarded by the BSC (DTAP) to the VMSC (RCF SMT function). The MS may refuse the CPDATA by sending the message CPERROR(DTAP message) containing a CPcause field identifying the error (see phase 1 & 2 GSM 04.11, 8.1.4.2). After translation of error, the VMSC (RCF SMT) sends the message MIFSME to indicate to the GMSC a transfer failure. c)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 23 / 135
CIT
If the MS has correctly received the short message (RPDATA) it sends the message CPDATA (DTAP message) containing the RPACK message. If the CP_DATA is correct the VMSC (RCF SMT) acknowledges the message by sending to the MS the message CPACK and it sends the message MIFSMR to the GMSC. In case of invalid data in the CP_DATA, the VMSC (RCF SMT) sends to the MS the CP ERROR message containing a CPcause field identifying the error (see phase 1 & 2 GSM 04.11, 8.1.4.2) and sends the message MIFSME to indicate to the GMSC a transfer failure.
The failures of the message transfer attempt detected by the MS are notified to the MSC (RCF) by the CPDATA message containing the RPERROR message with the related cause. The RCF SMT acknowledges the CPDATA(RP ERROR) by sending the CPACK message (without user information) and sends to the GMSC the message MIFSME to indicate to the GMSC a transfer failure. If the RP_Userdata field of RPERROR message is longer than L4 threshold (proposed value of L4= 200 bytes), the RP_Userdata cannot be inserted in diagnostic field of ForwardShortMessage error. Then the RPERROR is ignored and a CPERROR will be sent to the MS when TR1N will expire.
N.B. If the SMT transaction ends right, it has possibly to inform an other SMT transaction waiting for forwarding a Short Message, if there is at least one, by sending MI_DBL_STR_RES message to the awaiting transaction. If the SMT transaction ends wrong due to Channel release indication received from RM, or CPERROR / RPERROR received from the MS, all the awaiting short message transaction are aborted by sending MI_DBL_STR_ERR message. If the SMT transaction ends wrong due to others events, a MI_DBL_STR_RES message is also sent to the awaiting transaction. 2.5.1.2.1 CP messages loss Due to structure of message flow on SAPI 0 and SAPI 3 it is possible that the CPACK of a short message transfer might not be received (e.g. due to handover). If the first CPACK (acknowledging the CPDATA that carried the first TPDU) is not received, the reception of CPDATA is interpreted as the reception of the awaited CPACK and CPDATA message. Furthermore, to prevent against CP messages loss the following timers have to be implemented by the MSC (according to the GSM 04.11): Timer TC1N : started on sending the CPDATA message to the MS : it supervises the reception of the CPACK from the MS. The starting value of TC1N shall not be affected by a change of channel type after transmission of the initial CPDATA. If it expires, the CPDATA is retransmitted, up to n times (n system parameter, default value = 3) unless TR1N expires. If the CPACK is always not received, then the short message transfer attempt is considered as failed and the MI_F_SM_E (cause SM Delivery failure) is sent to the GMSC. It supervises the reception of the RPACK from the MS. Started on sending the CPDATA message to the MS.
1AA 00014 0004 (9007) A4 ALICE 04.10
Timer TR1N :
ED
04 AAC020298400DS 135 En 24 / 135
CIT
If it expires the short message transfer attempt is considered as failed and the MI_F_SM_E (cause SM Delivery failure) is sent to the GMSC.
2.5.1.3 Release of MM connection When the MM connection has to be released, the VMSC (RCF SMT) sends a Channel release to RM function. But this message is sent only when a timer T_BEFORE_REL has expired to ensure the BSS is able to send its last DTAP message. This T_BEFORE_REL timer is set when the last DTAP message is sent to the MS. When the SMT function in RCF receives from RM a Channel release indication, if the cause of the Clear Request message received from the MS is radio interface message failure, it returns a ForwardShortMessage error with Absent subscriber cause. Then SetMNRF message is sent by SMT RCF to SMT VLR to request the setting of MNRF flag in VLR database. When the SMT function in RCF receives from RM a Channel release indication due to an IMSI detach procedure (cause set to specific LR error ERR_LR_104), and a transfer towards the MS is ongoing with the CPDATA(RPACK) not yet received, it returns a ForwardShortMessage error with Absent subscriber cause. Then SetMNRF message is sent by SMT RCF to SMT VLR to request the setting of MNRF flag in VLR database. 2.5.2 Messages; Forwarding of multiple short messages If the dialogue versions between SC , SMSGMSC and VMSC are adequate (SMSAP V2 and MAP phase 2), the SC indicates to SMSGMSC that other message is following. Then, the SMSGMSC forwards this information to the VMSC. If the dialogue versions are inadequate, the transfer of several and subsequent short messages is handled at VMSC as independant short messages. a) Transfer of the first short message: The More message to send parameter of FSM message indicates to VMSC that a subsequent short message has to be waited. The message is treated in the same way as a single short message, except that At the end of transfer, the VMSC does not release the MS. The ForwardShortMessage result is sent in a TCCONTINUE. Yet, if the VMSC sends a ForwardShortMessage error, the transaction to the gateway MSC is terminated even if a new ForwardShortMessage is expected on the same transaction. A timer T_SUBSEQ is introduced to supervise the receipt of the subsequent ForwardShortMessage in the same TCAP dialogue. If the timer expires, the MSC shall close the TCAP transaction with a TCEND and requests a Channel release to RM function. b) Transfer of following short messages: The subsequent messages expected on the same MAP transaction suspend the treatment of short messages waiting in the delivery queue (MT short message coming from others SCs). The authentication and identification procedures are not performed again. The same RR connection is used to transfer a subsequent MT short message. The Transaction Identifier used for the new transaction is different from the last one used. The CPData is coded using the SmRPDA of the initial MT short message transfer. The MSC ignores the eventual SmRPOA of the subsequent ForwardShortMessage and uses the one of the initial message.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 25 / 135
CIT
2.5.2.1 Management of the Forward Check SS Indication RCF SMT in VMSC may receive at any time the MI_F_C_SS_H_I message which comes from the HLR through the VLR. As soon as MI_F_C_SS_H_I message is received, SMT forwards the ForwardCheckSSIndication to SH in the MI_FCSS_SH_REQ message.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 26 / 135
CIT
2.5.3 Scenarios 2.5.3.1 Successful case Single Short Message Transfer

S C
GMSC RCF SMT SMT
VMSC RCF PA SC SH SMT
VMSC VLR PA SC LR
MS
MIFSMI (TCBeg) MISINFSMTI (TCBegin) MIPAGESMTREQ Paging (see [6] page 6)
MIPAGESMT ACK MIVSMSC REQ Security (see [7] page 6)
MIVSMSCRES Check IMEI (see [7] page 6)
MI_F_C_SS_H_I (1) MI_FCSS_SH_REQ MICOMSMTI (TCEnd) MI_DBL_STR_RES IMEI_ACK (1) If received from the HLR
Figure 8. Forwarding of short message (1/2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 27 / 135
CIT
S C
GMSC RCF SMT SMT
VMSC RCF PA SC SH RM SMT
VMSC VLR PA SC LR
MS
CPDATA (RPData) CPACK CPDTA (RPAck) CPACK MIFSMR (TCEnd) Figure 9. Forwarding of short message single transfer (2/2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 28 / 135
CIT
2.5.3.2 Successful case Multiple Short Message Transfer Phase 2 dialogue GMSCVMSC S C GMSC RCF SMT SMT VMSC RCF PA SC SH RM SMT VMSC VLR PA SC LR MS
See SMS connection between SC and SMSGMSC Data Form 1 (RPMTDATA) See retrieval of routing information MIFSMI (1) (TCBegin) MISINFSMTI See successful case Single SM transfer MICOMSMTI CPDATA (RPData) CPACK CPDATA (RPAck) CPACK MIFSMR (TCContinue) Data Form 1 (RPMTACK) (1) with MoreMessageToSend parameter Figure 10. Forwarding of short message Multiple transfer (1/2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 29 / 135
CIT
S C
GMSC RCF SMT SMT
VMSC RCF PA SC SH RM SMT
VMSC VLR PA SC LR
MS
Data Form 1 (RPMTDATA) MIFSMI (TCContinue) CPDATA (RPData) CPACK CPDATA (RPAck) CPACK MIFSMR (TCEnd) Data Form 1 (RPMTACK) set message waiting data or SM delivery status report procedure is started
Figure 11. Forwarding of short message Multiple transfer (2/2)
2.5.3.3 Unsuccessful case GMSC <> VMSC <> VLR interface IMSI UNKNOWN FSMS003 is not offered GMSC RCF SMT MIFSMI (TCBegin) MISINFSMTI (TCBegin) IMSI unknown MISINFSMTE (unidentified subscriber (TCEnd) MIFSME (TCEnd)
1AA 00014 0004 (9007) A4 ALICE 04.10
S C
VMSC RCF SMT SMT
VMSC VLR
Figure 12. IMSI unknown (1/2)
ED
04 AAC020298400DS 135 En 30 / 135
CIT
IMSI UNKNOWN FSMS003 is offered

S C
GMSC RCF SMT MIFSMI (TCBegin)
VMSC RCF SMT SMT
VMSC VLR PA
MISINFSMTI (TCBegin) IMSI unknown MI_SEAR_SMT_REQ
SECURITY PHASE
UPDATE LOCATION MI_F_SM_R (TCend)
Figure 13. IMSI unknown (2/2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 31 / 135
CIT
IMSI DETACHED GMSC RCF SMT MIFSMI (TCBegin) MISINFSMTI (TCBegin) IMSI detached or LA not allowed MISINFSMTE (absent subscriber) (TCEnd) SM sets to true MNRF MIFSME (absent subscriber) (TCEnd) set message waiting data or SM Delivery status report procedure is started VMSC RCF SMT SMT VMSC VLR
S C
Figure 14. Send info for SMT error (1/4)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 32 / 135
CIT
PAGE NEGATIVE ACKNOWLEDGE GMSC RCF SMT MIFSMI (TCBegin) MSINFSMTI (TCBegin) MIPAGESMTREQ Paging (see [6] page 6) VMSC RCF SMT PA SMT VMSC VLR PA
S C
MS
no answer from the MS MIPAGESMTNACK (Absent Subscriber) SMTfunction sets the MNRF to true MISINFSMTE (Absent Subscriber) (TCEnd) MI_DBL_STR_ERR MIFSME (Absent subscriber) (TCEnd) set message waiting data or SM Delivery status report procedure is started
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 33 / 135
CIT
SECURITY REQUEST REJECT GMSC RCF SMT MIFSMI (TCBegin) MISINFSMTI (TCBegin) MIPAGESMTREQ Paging (see [6] page 6) MIPAGESMTACK MIVMSSCREQ Security (see [7] page 6) MIVSMSCERR (Illegal MS) MISINFSMTE (Illegal MS) (TCEnd) MI_DBL_STR_ERR MIAUTHREJ MIFSME (Illegal MS) (TCEnd) VMSC RCF SMT PA SMT VMSC VLR PA SC
S C
MS
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 34 / 135
CIT
IMEI CHEK FAILED GMSC RCF SMT MIFSMI (TCBegin) MISINFSMTI (TCBegin) MIPAGESMTREQ Paging (see [6] page 6) MIPAGESMTACK MIVSMSCREQ Security (see [7] page 6) MIVSMSCRES Check IMEI (see [7] page 6) MICOMSMTI (TCEnd) MI_DBL_STR_RES IMEI_NACK MI_F_SM_E (TCEnd) SMT VMSC RCF PA SC SMT VMSC VLR PA SC
S C
MS
Figure 17. Check IMEI failure (4/4)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 35 / 135
CIT
2.5.3.4 Unsuccessful case VMSC <> MS CP level S C GMSC RCF SMT SMT VMSC RCF PA SC SH RM SMT VMSC VLR PA SC LR MS
MIFSMI Successful case Receipt of CPERROR: CPDATA (RPData) CPERROR MIFSME OR Invalid CPDATA: CPDATA (RPData) CPACK CPDATA (RPAck) CPERROR MIFSME
Figure 18. Error case VMSC <> MS CP level 2.5.3.5 Unsuccessful case VMSC <> MS RP level S C GMSC RCF SMT SMT VMSC RCF PA SC SH RM SMT VMSC VLR PA SC LR MS
MIFSMI Successful case CPDATA (RPData) CPACK Receipt of RPERROR: CPDATA (RPError) CPACK
1AA 00014 0004 (9007) A4 ALICE 04.10
MIFSME
Figure 19. Error case VMSC <> MS RP level
ED
04 AAC020298400DS 135 En 36 / 135
CIT
2.5.3.6 Unsuccessful case RCF <> BSSMAP interface

SAPI n REJECT GMSC RCF SMT SMT VMSC RCF RM BSS MS BSSMAP
S C
CPDATA (RPData) SAPI n REJECT Radio Ressource Management See [8] page 6) MICHRELIND MIFSME (TCEnd)
Figure 20. Failure at the radio side (1/1)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 37 / 135
CIT
2.6 Set Message waiting data and SM Delivery Status Report procedures
a)
The procedure is started in case of unsuccessful delivery attempt due to: Absent subscriber (i.e. IMSI detached, no paging response, or LA not allowed), Unidentified subscriber at VMSC, SM delivery failure with cause memory capacity exceeded (only when phase 2 dialogue with HLR). MI_S_MW_I (MAP phase 1 Set message waiting data) or MI_R_SMD_S_I (MAP phase 2 Report SM Delivery Status) with AbsentSubscriber or MemoryCapacityExceeded as SMDeliveryOutcome is sent by the RCF SMT of the SMSGMSC to the HLR SMT in order to include a new SC address in the MWD.
b)
The procedure is also started in case of successful delivery attemp to report the HLR about a successful transfer and then to trigger an Alert procedure (only when phase 2 dialogue with HLR). MI_R_SMD_S_I (MAP phase 2 Report SM Delivery Status) with Successful Transfer as SMDeliveryOutcome is sent by the RCF SM of the SMSGMSC to the HLR SM.
2.6.1 SMSGMSC treatments 2.6.1.1 Sending of Set Message Waiting Data / Report SM Delivery Status This message is sent by the SMSGMSC as follows: a) After the SMSGMSC has received a ForwardShortMessage error with error cause set to: SMDeliveryfailure with cause Memory capacity exceeded: With phase 2 dialogue with HLR, the SMSGMSC sends the ReportSMDeliveryStatus, with SM_DeliveryOutcome set to MemoryCapacityExceeded, if the MCEF flag is clear in HLR or if the SC address is not yet included in MWD. With phase 1 dialogue with HLR, no specific action is performed by the SMSGMSC. Absent subscriber or Unidentified subscriber: With phase 2 dialogue with HLR, the SMSGMSC sends the ReportSMDeliveryStatus, with SM_DeliveryOutcome set to AbsentSubscriber, if the MNRF flag is clear in HLR or if the SC address is not yet included in MWD. With phase 1 dialogue with HLR, the SMSGMSC sends the SetMessageWaitingData message, if the MNRF flag is clear in HLR or if the SC address is not yet included in MWD. N.B. The GMSC has got the state of flags and MWD file from the HLR in InformServiceCenter (phase 2) or SendRoutingInfoForSM result (phase1) message, otherwise a default information is used (Flags clear and SC address not included in MWD). b) After the SMSGMSC has received a ForwardShortMessage result With phase 2 dialogue with HLR, the SMSGMSC sends the ReportSMDeliveryStatus, with SM_DeliveryOutcome set to SuccessfulTransfert, if MNRF and/or MCEF flag is set in HLR (data got by the GMSC from the HLR in InformServiceCenter message). The HLR is in that way informed of successful transfer and can reset MNRF and MCEF flags and triggers an Alert procedure.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 38 / 135
CIT
With phase 1 dialogue with HLR, the SMSGMSC performs no action. 2.6.1.2 End of set message waiting data / SM delivery status report procedure
After the end of the procedure (receipt of result or error from HLR), the GMSC (RCF SMT) informs the SC about the original error received from VMSC by sending a DT1 containing a RPMTERROR message which layout depends on the result of the set message waiting or SM delivery status report procedure: RPMW flag, indicating whether the MWD has been updated, RPcause (error cause received from VMSC in Forward short message error translated towards the SC) RPMSISDN (only SMSAP V2) indicating the MSISDNAlert if received from HLR in SM delivery status report procedure. RPUserdata (only SMSAP V2) which contains, if received in MI_F_SM_E, the field DiagnosticInfo of SMDeliveryFailure error cause. 2.6.2 HLR treatments at the reception of the message At the reception of the message, the HLR SMT verifies the correctness of the data content; verifies that the MSISDN number is known; Futhermore, If the SM delivery outcome reports a successful delivery, the HLR alert the SCs in the MWD list as described in < 2.7 page 42>. If the SM delivery outcome reports a unsuccessful delivery, the HLR verifies that the MWD is not full.
If any of the checks fails, the message MI_S_MW_E (MAP phase 1 Set message waiting data error) or MI_R_SMD_S_E (MAP phase 2 Report SM Delivery Status error) is returned to the RCF SMT in GMSC. If the MWD is correctly updated, The MCEF flag is set and MNRF reset if SM delivery outcome is memory capacity exceeded. The MNRF flag is set if SM delivery outcome is absent subscriber. The message MI_S_MW_R (MAP phase 1 Set message waiting data result) or MI_R_SMD_S_R (MAP phase 2 Report SM Delivery Status result) with the MSISDNalert as parameter is returned to the RCF SMT in GMSC. N.B. To avoid that the SC addresses remain in the MWD in case the MS is not reachable for a long period, the HLR will provide, for each SC address, a timer T_MWD to be started when the SC address has been added to the MWD. It will be stopped after the SC address has been deleted from the MWD (owing to the sending of an Alert message to the IWMSC). At the expiry of the timer the SC address is deleted from the MWD.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 39 / 135
CIT
2.6.3 Scenarios S C GMSC RCF SMT VMSC RCF SMT VMSC VLR SMT HLR SMT
MISINFSMTE (absent subscriber) (TCEnd) MIFSME (absent subscriber) (TCEnd) MISMWI / MIRSMDSI (TCBegin) the SC address is added to the MWD MRF flag is set
MISMWR / MIRSMDSR (TCEnd) Data Form 1 RPMTError
Figure 21. Set message waiting data/ SM Delivery Status report Absent subscriber case
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 40 / 135
CIT
S C
GMSC RCF SMT
VMSC RCF SMT
HLR MS SMT
CPDATA (RPError) (Memory capacity exceeded) CPACK MIFSME SMdeliveryFailure cause MemoryCapacityExceeded (TCEnd) MIRSMDSI (1) (TCBegin) the SC address is added to the MWD MCEF flag is set MNRF flag is reset
MIRSMDSR (TCEnd) Data Form 1 RPMTError (1) Only in MAP phase 2 dialogue with HLR
Figure 22. Set message waiting data/ SM Delivery Status report Memory capacity exceeded case GMSC RCF SMT VMSC RCF SMT VMSC VLR SMT HLR SMT
S C
MIFSMR (TCEnd) MIRSMDSI (1) (TCBegin) MIRSMDSR or MIRSMDSE (TCEnd) Data Form 1 RPMTAck
1AA 00014 0004 (9007) A4 ALICE 04.10
(1) may trigger an Alert procedure Figure 23. SM Delivery Status report Successful delivery
ED
04 AAC020298400DS 135 En 41 / 135
CIT
2.7 Alerting Service Center procedure

The purpose of the procedure is to inform a SC that: a MS for which a delivery attempt has been unsuccessful (due to IMSI detached, no paging response or LA not allowed reason) is again reachable, a MS for which a delivery attempt has been unsuccessful (due to memory capacity exceeded) has again memory capacity to accept a short message, a delivery attempt ended with success towards a MS for which a delivery attempt has been previously unsuccessful. The alerting of the service center is always invoked by the HLR (via the IWMSC) either directly or on the VLR request. 2.7.1 Alert procedure triggering GMSC HLR LR HLR (2) LR VLR VMSC
(1)
(3)
SC VLR
SMT (5) RCF
SMT HLR
(4)
SMO VLR
SMO RCF
(1) Note MS present (internal interface) triggered by an Update location procedure at HLR level (2) Ready for SM / Note subscriber present (mspresent as alert reason) triggered by an Update location procedure at VLR level (3) Ready for SM / Note subscriber present (mspresent as alert reason) triggered by a Security request (from OC,TC,LR,SH,SMT, SMO) ended with success (4) Ready for SM (memoryavailable as alert reason) triggered by a Short message originating procedure with SMMemoryAvailable (5) Report SM delivery status (successfultransfert as SMDeliveryOutcome) triggered by a successful short message transfer Figure 24. Alert procedure triggering
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 42 / 135
CIT
The messages which may trigger an Alert procedure in HLR are:

MIMSPI (MAP phase 1 NoteSubscriberPresent) or MIRFSMI (MAP phase 2 ReadyForSM) with mspresent as alert reason is sent by the VLR to the HLR SMT when the VLR detects that one of the following procedure has been successfully completed: Paging or searching; Update location area; Attach IMSI; Process access request;
and if MNRF indicates that there is at least one message waiting to be delivered to the MS. The message is sent at the completion either of the security procedures or of the update location procedure (when no security procedure is required). This message is sent by Security function in VLR, only if the mobile station has SMS capability. Refer to SDLs of SC function in VLR < [7] page 6>. It can be sent also by LR in case flag MNRF is true and the MS is allowed to roam in the new LA. Moreover it can also be sent by LR if no Security is performed for this Update Location. Refer to SDLs of LR function in VLR < [10] page 6>. In Phase 1 dialogue with the HLR, after sending the message the MNRF is reset to false. In Phase 2 dialogue with the HLR, the MNRF flag is cleared only if the procedure is successful (receipt of MIRFSMR). MIRFSMI (MAP phase 2 ReadyForSM) with memoryavailable as alert reason is sent by the VLR to the HLR SMT when the VLR detects that the MS has again memory available for short message. MIRSMDSI (MAP phase 2 ReportSMDeliveryStatus) with SuccessfulTransfert as SMDeliveryOutcome is sent by the GMSC to the HLR SMT when a short message has ended successfully and MNRF and/or MCEF are known set in HLR. MIMSPRESENT (Internal message) is sent by the HLR LR to the HLR SMT when an update location procedure has been correctly completed.
2.7.2 Alert procedure at HLR level If one of these messages is not correctly received, no further action is performed by the HLR. If one message is correctly received and the MWD is not empty,the HLR SMT, for each SC address of the MWD, sends to the IWMSC the message MIASCWRI (MAP phase 1 AlertServiceCenterWithoutResult) or the message MIASCI (MAP phase 2 AlertServiceCenter). Furthermore, For Alerting required by the VLR with MS present reason, the Alert procedure is not triggered if MCEF flag is set. The trigger of Alert procedure is delayed if neither MCEF, nor MNRF flag are set (a race situation with Report SM delivery status is then assumed, refer to the scenario for the particular treatment). The HLR MNRF flag is cleared in any cases. For Alerting required by the VLR with memory available reason, the trigger of Alert procedure is delayed if neither MCEF, nor MNRF flag are set (a race situation is then assumed, refer to the scenario for the particular treatment). The HLR MNRF and MCEF flags are cleared. 04 AAC020298400DS 135 En 43 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
For Alerting required by the GMSC with successful transfer reason, the HLR MNRF and MCEF flags are cleared.
In accordance with the option FSMS001, routing information towards the IWMSC is retrieved either by analysis of the SC address or by analysis of one IWMSC address contained in an HLR data. In Phase 1 dialogue with the IWMSC, after sending the message the SC address is deleted from the MWD. In Phase 2 dialogue with the IWMSC, The MWD entry is deleted when the positive acknowledge is received from the IWMSC. The unsuccessful alert is repeated (the number of attempts is a system parameter, default value = 2). In the unsuccessful case, the MWD is purged by the treatment described in 2.6 page 38. 2.7.3 Alert procedure at IWMSC level If the message is correctly received, the RCF (SMT) alerts the Service Center by sending the message RP_ALERT containing the involved MSIsdn. The message is sent to the SC in a connectionless mode that is using a UDT SCCP message which will contain the following fields: Calling address = MS address = MS ISDN Called address = SC address User data = RP Alert message Just after the sending towards the SC, the IWMSC acknowledges the HLR Alert message.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 44 / 135
CIT
2.7.4 Scenarios ALERTING REQUIRED BY THE VLR (MS PRESENT)

S C
IWMSC RCF SMT
VLR SMT SC OC LR
HLR SMT
security procedure (requested by TC, LR, OC, SH, SMT, SMO successfuly ended) MNRF is true MIMSPI or MIRFSMI (1) MIRFSMR (2) MIASCWRI or MIASCI (3) (TCBegin) UDT (RP_Alert) MIASCR (2) (TCEnd) (1) It can be sent also by LR in case flag MNRFis true and the MS is allowed to roam in the new LA. Moreover it can also be sent by LR if no Security is performed for this Update Location. (2) Only in MAP phase 2 dialogue (3) Only if MCEF is false Figure 25. Alert service center (1/5)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 45 / 135
CIT
ALERTING REQUIRED BY THE VLR (MEMORY AVAILABLE) Only if Phase 2 dialogue between VLR and HLR
S C
IWMSC RCF SMT
VLR SMO
HLR SMT
MIRFSMI (memory available) MIRFSMR MIASCWRI or MIASCI (TCBegin) UDT (RP_Alert) MIASCR (2) (TCEnd) (2) Only in MAP phase 2 dialogue Figure 26. Alert service center (2/5) ALERTING REQUIRED BY THE GMSC (SUCCESSFUL TRANSFER) Only if Phase 2 dialogue between GMSC and HLR S C IWMSC RCF SMT GMSC RCF SMT HLR SMT
MIRSMDSI (successful transfer) (1) MIRSMDSR Data Form 1 (RPMTACK) MIASCWRI or MIASCI (TCBegin) UDT (RP_Alert) MIASCR (2) (TCEnd) (1) Only if MNRF and/or MCEF are known set in HLR (2) Only in MAP phase 2 dialogue Figure 27. Alert service center (3/5)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 46 / 135
CIT
ALERTING REQUIRED BY THE VLR (RACE SITUATION) SMSGMSC RCF SMT VLR SMT HLR SMT
S C
MIMSPI or MIRFSMI (1) MIRFSMR (4) MIRSMDSI (2) MIRSMDSR (4) MIASCWRI or MIASCI (TCBegin) UDT (RPAlert) MIASCR (4) (TCEnd) (1) If neither MNRF nor MCEF are set, it is assumed that a race situation occurs. Then, a timer T_RACE is triggered to wait the Report SM delivery status message. (2) If a Report SM delivery status is received when the timer is running, this message is handled normally. At the timer expiry, if the MNRF or MCEF are set the Alert procedure is restarted. Elseif no further treatment is performed. (4) Only in MAP phase 2 dialogue Figure 28. Alert service center (4/5)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 47 / 135
CIT
ALERTING REQUIRED BY THE HLR IWMSC RCF SMT VLR SMT PA LR SC HLR SMT LR
S C
MIMSPRESENT MWD not empty MIASCWRI or MIASCI (TCBegin) UDT (RP_Alert) MIASCR (2) (TCEnd) (2) Only in MAP phase 2 dialogue Figure 29. Alert service center (5/5)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 48 / 135
CIT
3 INTERFACE MATRIX
The names of interfaces use SM for SMT function and MO for SMO function (e.g. MIVMOHSM refers to the interface between SMO function in VLR and SMT function in HLR). Function Implementation Messages Name FB B R V H S C L L S F R R S C
Related functions
Short Message Service Terminating
P U U U
U P P P
MIRSMSSM RPMTData (DT1) RPMTError (DT1) RPMTAck (DT1) RPAlert (UDT) MIRSMHSM Send routing info for SM (INV/RES/ERR) Inform Service Center (INV) Set Message Waiting Data (INV/RES/ERR) Report SM Delivery Status (INV/RES/ERR) Alert Service Center (INV/RES/ERR) Alert Service Center Without Result (INV) MIRSMRSM Forward Short Message (INV/RES/ERR) MIRSMVSM Send info inc sm call (INV/ERR) Complete sm call (INV) Set MNRF flag MIRSMRSM DeblockSMtransaction (Res/Err)
U P U U
P U P P
P P
U U
U/P
U P P U
U
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 30. Short Message Service Funtional Matrix(1/3)
ED
04 AAC020298400DS 135 En 49 / 135
CIT
Related functions
Function Implementation Messages B R V H S C L L S F R R S C
Name
FB
Short Message Service terminating P U P U U P U Paging VLR U U U P U P P U P
MIRSMSSM MIRSMBSM CPData(RPdata) CPACK CPACK CPData(RPAck) CPData(RPError) CPError CPError MIVSMVPA Page request (Request/ack/nack) Search request (Request/ack/nack)
Security
VLR U U U
MIVSMVSC Security Req. from SM (Request/ack/reject) Security Release from SM IMEI Check (Ack/nack) MIVSCHSM Note subscriber present (INV) Ready For SM (INV/RES/ERR)
U P U P
Location Registration
HLR U VLR P U P
MIHLRHSM Note MS present MIRSMVLR ForwardCheckSSIndication MIVLRHSM Ready For SM (INV/RES/ERR)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 50 / 135
CIT
Related functions
Function Implementation Messages B R V H S C L L S F R R S C
Name
FB
Call Barring
HLR U
MIHSMHCB Inc. call barring check (Request/result) MIRSMRRM Chann. rel. Ind. Channel release Channel release complete Channel in use MIRSMRCG Charging request from SM
Radio Res. Management
RCF U U U U
Charging
RCF U
Sup. Service Handling
RCF U
MIRSHRSM ForwardCheckSS transfer (Request) MIRMMRMM Deblock transaction waiting for MM proc. (Res/Err)
MM
RCF
Short Message Service Originating
VLR MIVMOHSM Ready For SM (INV/RES/ERR)
U P
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 51 / 135
CIT
4 CONSEQUENCES OF V1 AND V2 MAP APPLICATION CONTEXTS MIX BETWEEN PLMN ENTITIES

Assumption: The data at HLR and VLR level are according to phase 2 (handling of MSISDNAlert, MNRF, MCEF and MWD). The phase 2 treatments at HLR and VLR level are always used. They are designed to be compatible with phase 1. Phase 1 dialogues between entities entails only some restrictions of feature. SMSIWMSC SMSGMSC (4) (1) (3)
HLR (2)
MSC/VLR
(1) shortMsgGatewayContext V1/V2 : SendRoutingInfoForSM ReportSMDeliveryStatus/SetMessageWaitingData InformServiceCenter (2) shortMsgMTRelayContext V2, shortMsgRelayContext V1 : ForwardShortMessage (3) mwdMngtContext V1/V2 : ReadyForSM/NoteSubscriberPresent (4) shortmsgAlertContext V1/V2 : AlertServiceCenter/AlertServiceCenterwithoutresult
4.1 Restrictions of feature induced by use of v1 context:

(1) Use of v1 context entails: The SC cannot received indication on MNRF and MCEF flags. The HLR cannot be informed of successful transfer for triggerring an Alert procedure. The HLR cannot be informed of MemoryCapacityExceeded for inserting the SC address in MWD. (2) Use of v1 context entails no main feature restriction (a new dialogue is used for each transfer and the SMSDELIVERREPORT TPDU cannot be forwarded towards the SC) (3) The Alert procedure with reason memoryavailable cannot be triggered in case of v1 context use. (4) Use of v1 context entails no feature restriction (the message has no response).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 52 / 135
CIT
4.2 Consequences of v1 and v2 Application Context mix

Some inconsistencies may occur related to MemoryCapacityExceeded/Available feature. MCEF flag being handled only in HLR , incoherency between HLR and VLR is not possible. But, if (1) Application Context is in V2 and (3) in V1, and there is memory capacity exceeded in the MS: SC address will be inserted in MWD and MCEF flag set in HLR, The Alert procedure will never be triggered by the VMSC. It is not unsafe because: The MCEF flag set in HLR does not prevent the short message to be forwarded towards VMSC. A successful transfer reset MCEF flag and may trigger an Alerting procedure. Furthermore, the described case above occurs also with a phase 1 MS which cannot indicate memory avalaible event. In the opposite, if (1) is in V1 and (3) in V2, on receipt of ReadyForSM with alert reason MemoryAvailable, an Alert procedure will be triggered if MNRF is set at HLR.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 53 / 135
CIT
5 INTERFACES WITHIN THE FUNCTION SHORT MESSAGE 5.1 MIRSMSSM: Interface between the GMSC and the SC
See < [4] page 6>.
5.2 MIRSMHSM: Interface between RCF and HLR

5.2.1 Send Routing Information for Short Message This message is sent by the RCF of the GMSC to the HLR to retrieve routing information. If the functional option FSMS005 is offered, this message may be sent to the HLR in order to retrieve the MSC address only. Any particularities are described in note (11). Identity of the interface : MIRSMHSM Type of interface : MAP Ref : GSM phase 1 09.02 fig. 6.2/13 (Sheet 1 of 2) GSM phase 2 09.02 14.6.5 Information exchanged on the interface :
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 54 / 135
CIT
Message Identification SendRoutingInfoForSM (Invoke)
Parameters msIsdn smRPPRI ServiceCenterAddress TeleserviceCode (1) (2) (3) (4)
V1 V2 M M M O M M M
MI_S_RGI_SM_I RCF>HLR SendRoutingInfoForSM (Error) See also note (11) UnknownSubscriber CallBarred CallBarringCause CUGReject TeleserviceNot provisioned AbsentSubscriber mwdset FacilityNotSupported SystemFailure DataMissing UnexpectedDataValue x x O x x x O x x x x x x O x x O x x x x
(5)
(6) (boolean) (7)
MI_S_RGI_SM_E
HLR>RCF SendRoutingInfoForSM (Result) imsi locationInfo MSCNumber lmsi mwdSet
See also note (11) M M O O M M O O
(8) (9) (boolean) (10)
MI_S_RGI_SM_R HLR>RCF (M) means Mandatory (O) means Optional Figure 33. Send Routing Information for Short Message : messages layout Notes: (1) : The RCF sends to HLR an E.164 international number (i.e. Nature of address indicator = international number and Numbering indicator = ISDN/Telephony number plan (REC E.164)). The digits are those of RPDestinationaddress received from SC in RPMTData. The HLR accepts an E.164 number with Nature of address indicator = international number or national number . (2) : Handling of parameter SMRPPRI depends on a functional option (F_SMS_004). When priority is not handled, all short messages are considered to be nonpriority messages. When priority is handled, this parameter is filled according to the RPPriority parameter received from SC in RPMTData. (3) : International Number ISDN/Telephony E.164. See also note (11)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 55 / 135
CIT
Digits are those received from SC in RPOriginatingaddress parameter of RPMTData.

(4) : The field is not sent by the RCF. If the HLR receives the CUGInterlock parameter, it would be rejected with the error mistyped parameter. If the HLR receives the teleservice code parameter, it would be ignored. (5) : CallBarringCause may be BarringServiceActive or OperatorBarring (6) : In MAP phase 1, the associated parameter is the mwdset indicating whether the SC address has been included in the MWD or not. Always sent in MAP phase 1 by the HLR. When not sent by a HLR, RCF does as it is FALSE. The mwdSet, not foreseen in GSM phase 2 09.02, is set Optional in order to ignore it, if received in phase 2 dialogue. In MAP phase 2, see InformServiceCenter message. The Absent subscriber error corresponds with the following cases: No MSC identity in HLR MSC area restricted flag set in HLR MS purged flag set in HLR SMRPPRI = false and MNRF flag set in HLR (MCEF any)
(7) : This cause (SMSMT not supported by the VMSC) is sent to RCF due to the check of SMSMT flag. (8) : The LocationInfo may indicate roaming number or servicing MSC address; but the RCF handles only the MSC address. (9) : It is mandatory for the HLR to include the LMSI, if the VLR has used the LMSI (See update location procedure). (10) : The mwdSet, not foreseen in GSM phase 2 09.02, is set Optional in order to ignore it, if received in phase 2 dialogue. In MAP phase 2, see InformServiceCenter message. Always sent in MAP phase 1 by the HLR. When not sent by a HLR, RCF does as it is FALSE. (11) : If the option FSMS005 is set the MSISDN sent in Private Numbering Plan will be accepted. The following applies in this case: ServiceCenterAddress is an international E.164 number, but may have a dummy value TeleserviceCode is not sent the following errors are not applicable Cugreject TeleserviceNotProvisioned FacilityNotSupported lmsi is not sent by the HLR mwdset is not applicable
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 56 / 135
CIT
5.2.2 InformServiceCentre This service is used between the HLR and the SMSGMSC to inform the SC which MSISDN number is stored in the MWD file. This service replaces also the parameter mwdset of SRI message in use for phase 1 dialogue. Identity of the interface : MIRSMHSM Type of interface : MAP Ref : GSM phase 2 09.02 14.6.5 Information exchanged on the interface : Message Identification InformServiceCentre MI_I_SC_I Parameters storedMSISDN mwStatus Bit String( .scAddressNotIncluded .mnrfset .mcefset) (1) (2) V2 O O
HLR>RCF
Notes: (1): If the stored MSISDN number is not the same than the one received from the GMSC in the SRI, the stored number is included. The stored MSISDN is the MSISDNAlert. (2): If mwStatus is not received, the value zero is assumed. SCAddressNotIncluded indicates the status of the particular SC address presence in the MWD file (i.e. if the SC address is not included in the MWD list). See < 2.3.1.2 page 17> for details (when this message is sent and how it is filled).
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 57 / 135
CIT
5.2.3 Set Message Waiting Data / Report SM Delivery Status 5.2.3.1 Set Message Waiting Data
This message is sent by the RCF to the HLR to request the inclusion of the new SC address in the MWD. Identity of the interface : MIRSMHSM Type of interface : MAP Ref : GSM phase 1 09.02 fig. 6.2/13 (Sheet 2 of 2) Information exchanged on the interface : Message Identification SetMessageWaitingData (Invoke) MI_S_MW_I RCF>HLR SetMessageWaitingData (Error) MI_S_MW_E HLR>RCF SetMessageWaitingData (Result) MI_S_MW_R HLR>RCF (M) means Mandatory (O) means Optional Figure 34. Set Message Waiting Data : messages layout none UnknownSubscriber MessageWaitingListFull UnexpectedDataValue Data missing Parameters msIsdn ServiceCenterAddress V1 M M
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 58 / 135
CIT
5.2.3.2 Report SM Delivery Status This service is used by the SMSGMSC to set the MWD into the HLR or to inform the HLR of successful SM transfer. Identity of the interface : MIRSMHSM Type of interface : MAP Ref : GSM phase 2 09.02 14.6.5 Information exchanged on the interface : Message Identification ReportSMDeliveryStatus (Invoke) MI_R_SMD_S_I Parameters msIsdn ServiceCenterAddress smDeliveryOutcome Enumerated (AbsentSubscriber (MemoryCapacityExceeded (SuccessfulTransfert UnknownSubscriber MessageWaitingListFull UnexpectedDataValue DataMissing V2 M M M
RCF>HLR ReportSMDeliveryStatus (Error) MI_R_SMD_S_E HLR>RCF ReportSMDeliveryStatus (Result) MI_R_SMD_S_R HLR>RCF (M) means Mandatory (O) means Optional
storedMSISDN
(1)
Figure 35. Report SM Delivery Status : messages layout Note: (1) It is the MSISDNAlert. Stored MSISDN parameter is inserted if the MSISDNAlert is not the same as MSISDN of invoke. See < 2.6.1 page 38> for details (when this message is sent and how it is filled).
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 59 / 135
CIT
5.2.4 AlertServiceCenterWithoutResult (Phase 1) This message is sent by the HLR to the IWMSC to invoke the starting of the Alert procedure towards the SCs. Identity of the interface : MIRSMHSM Type of interface : MAP Ref : GSM phase 1 09.02 fig. 6.2/13 (Sheet 2 of 2) Information exchanged on the interface : Message Identification AlertServiceCenterwithout Result (Invoke) MI_A_SC_WR_I HLR>RCF (M) means Mandatory (O) means Optional Figure 36. Alert Service Center Without Result message layout Note: (1) : The provided MSISDN shall be the one which is stored in the MWD file (MSISDNAlert). Parameters msIsdn ServiceCenterAddress (1) V1 M M
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 60 / 135
CIT
5.2.5 Alert Service Center (Phase 2) The HLR sends this message if a subscriber, whose is in the MWD file, becomes active or the MS has memory available. Identity of the interface : MIRSMHSM Type of interface : MAP Ref : GSM phase 2 09.02 14.6.5 Information exchanged on the interface : Message Identification AlertServiceCenter (Invoke) MI_A_SC_I HLR>RCF AlertServiceCenter (Error) MI_A_SC_E RCF>HLR AlertServiceCenter (Result) MI_A_SC_R RCF>HLR (M) means Mandatory (O) means Optional Figure 37. Alert Service Center message layout Note: (1) : The provided MSISDN shall be the one which is stored in the MWD file (MSISDNAlert). SystemFailure DataMissing UnexpectedDataValue Parameters msIsdn ServiceCenterAddress (1) V2 M M
none
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 61 / 135
CIT
5.3 MIRSMRSM : Interface between GMSC and VMSC

5.3.1 Forward Short Message This message is sent by the RCF of the gateway MSC to the RCF of the servicing MSC to require the forward of the short message. In phase 2, the MAP ForwardShortMessage may be received at the beginning of the MAP transaction or as a subsequent message in the same MAP transaction. Identity of the interface : MIRSMRSM Type of interface : MAP Ref : GSM phase 1 09.02 fig. 6.2/13 (Sheet 2 of 2) GSM phase 2 09.02 14.6.5 Information exchanged on the interface : Message Identification ForwardShortMessage (Invoke) MI_F_SM_I Parameters SMRPDA Choice ( .imsi .lmsi .roamingnumber .noSMRPDA ) SMRPOA Choice ( .ServiceCenterAddressOA .noSMRPOA) SMRPUI MoreMessagesToSend UnidentifiedSubscriber AbsentSubscriber FacilityNotSupported IllegalMS IllegalSubscriber SystemFailure UnexpectedDataValue SMDeliveryFailure .Cause (memory capacity exceeded (equipment protocol error (equipment Not SM equipped .DiagnosticInfo IllegalEquipment DataMissing SubscriberBusyForMT (1) V1 V2 M x x x (2) M x (3) (4) M M x x x M x x M O x x x x x x x M x x x O x x x
RCF>RCF ForwardShortMessage (Error)
x x x x (5) x x x M x x x (6) (7) (8)
MI_F_SM_E
RCF>RCF
ForwardShortMessage (Result) MIFSMR RCF>RCF

1AA 00014 0004 (9007) A4 ALICE 04.10
none
(M) means Mandatory (O) means Optional Figure 38. Forward Short Message: messages layout
ED
04 AAC020298400DS 135 En 62 / 135
CIT
Notes:
(1) : The SMSGMSC sends the LMSI if received from HLR in the SendRoutingInfoForSM result. In this case, the IMSI is included in the User Information Part (USI) : destination reference field of TC BEGIN dialog portion (mapopen choice of MAPDialoguePDU, see GSM 09.02 v4.12.0 5.3.1 and 14.4). For a phase 1 dialogue, SMRPDA shall contain an IMSI. Receipt of LMSI at VMSC entails a ForwardShortMessage error in response. For a phase 2 dialogue, SMRPDA may contain an IMSI or a LMSI. In case of LMSI, the IMSI must be retreived from the User Information Part (USI) in the destination reference field of TCBEGIN dialog portion. In case of IMSI, SMRPDA contains the IMSI which is not present in the USI. At VMSC, if LMSI is not send by the SMSGMSC, even though the VLR has sent it in update location procedure, the received IMSI is used and a spontaneous message is issued. The parameter roamingNumber is not accepted by the VMSC which responds with a ForwardShortMessage error. It is never sent by our SMSGMSC. NoSMRPDA is used by the SMSGMSC in case of subsequent MT short message transfer. SMRPDA parameter is ignored by the VMSC in case of multiple MT short message transfer in the same TCAP transaction; the value of the first ForwardShortMessage is used.
(2) : ServiceCenterAddressOA is received from the SC in RPOriginator Address of RPMTData message. The lack of address is indicated, either by an empty address (i.e.reduced to the first octet), or by the use of noSMRPOA in phase 2 dialogue. In this case, the MSC code this Information Element of the RPDATA towards the MS with a length equal to 0. NoSMRPOA is used by the SMSGMSC in case of subsequent MT short message transfer. SMRPOA parameter is ignored by the VMSC in case of multiple MT short message transfer in the same TCAP transaction; the value of the first ForwardShortMessage is used. (3) : RP_User_Data of RP_MT_Data message received from the SC. The content of the SMRPUI parameter is not checked by the MSC (MSC transparent to the TL protocol). (4) : The MoreMessagesToSend parameter is set if a MoreMessagesToSend indication has been received from the SC. In phase 1 dialogue the element MoreMessagesToSend cannot be transmitted. In this case, if there are more than one message from SC, the SMSGMSC process one phase 1 procedure for each message. (5) : Delivery of SM failed because the MS fails to be authenticate. (6) : SMDELIVERYREPORT can be transfered in this field (transfer without analysis of RPuserdata field of RPError received from MS) (7) : Delivery of SM failed because the IMEI check fails. (8) : Only used in phase 2 dialogue. Sent by the MSC when the delivery queue in VMSC cannot store a short message. Sent also by the MSC when PA function responds with busy subscriber error.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 63 / 135
CIT
5.4 MIRSMVSM: Interface between servicing MSC and VLR

5.4.1 Send Information for SMT This message is sent by the RCF to the VLR to request whether the call can be offered to the MS. Identity of the interface : MIRSMVSM Type of interface : Specific RCFVLR internal interface Ref : no GSM reference Information exchanged on the interface : Message Identification Send Info for short message (Invoke) MISINFSMTI RCF>VLR SendInfoforMTSMS (Error) MISINFSMTE VLR>RCF Unidentified subscriber Absent subscriber Illegal MS Illegal equipment System failure impossible call completion MS not equipped A5/X incompatibility Parameters IMSI (M)
(M) means Mandatory (O) means Optional Figure 39. Send Information for SMT : messages layout
5.4.2 Complete Short Message Call This message is sent by the VLR to the RCF to confirm that the call can be offered to the MS.
1AA 00014 0004 (9007) A4 ALICE 04.10
Identity of the interface : MIRSMVSM Type of interface : Specific RCFVLR internal interface Ref : no GSM reference Information exchanged on the interface :
ED
04 AAC020298400DS 135 En 64 / 135
CIT
Message Identification COMplete SMT call (Invoke) MICOMSMTI
Parameters Category MSISDN Authentication status (M) (1) (M) (2) (O) (3)
VLR>RCF (M) means Mandatory (O) means Optional Figure 40. Complete SMT call: message layout (1) : Category indicates to RCF the possible Hot Billing discrimination of the called MS, for generation of the Hot Billing ticket (if FHB001 functionnality is offered). (2) : e.g. for charging purpose (see ref. [13] ). (3) : Applies if FSC011 is active. Aunthentication status, set to ON when authentication is not performed due to Authentication 1/n function, is passed to RCF in order to not request authentication for further transactions established in parallel.
5.4.3 Set MNRF flag This message is sent by the RCF to the VLR to request the MNRF flag to be set in VLR database. Identity of the interface : MIRSMVSM Type of interface : Specific RCFVLR internal interface Ref : no GSM reference Information exchanged on the interface : Message Identification Set MNRF flag (Invoke) MISETMNRFI RCF>VLR (M) means Mandatory (O) means Optional Figure 41. Set MNRF flag : messages layout Parameters IMSI (M)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 65 / 135
CIT
5.5 MIRSMBSM: Interface between RCF in VMSC and BSS

5.5.1 CPDATA This message may be sent either by the RCF to the MS (via the BSS) or by the MS to the RCF (via the BSS). In the direction to the MS, it contains the short message. In the direction to the RCF it contains the acknowledge of the short message. Identity of the interface : MIRSMBSM Type of interface : BSSAP (DTAP) message Ref : GSM phase 1 04.11 table 7.1 GSM phase 2 04.11 7.2.1 Information exchanged on the interface : Message Identification CPDATA (DTAP) Parameters Protocol discriminator Transaction Identifier Message Type CPUser Data RCF<>MS (M) means Mandatory (O) means Optional Figure 42. CPDATA message layout Note: (1) : Length of CPUser Data parameter <= 249 bytes. The parameter CPUser Data is set Optional in contrary of GSM 04.11 where it is mandatory to allow the checks described in defence specification < [17] page 6>. The field RPDU of CPUser Data parameter is : the RPDATA from RCF towards the MS, in line with RP_MT_Data received by the GMSC from the SC and forwarded to the VMSC in MI_F_SM_I message. (see section 5.5.1.1 page 66). the RPERROR from MS towards the RCF (see section 5.5.1.2 page 67). the RPACK from MS towards the RCF (see section 5.5.1.3 page 68). 5.5.1.1 RPDATA layout Ref : GSM phase 1 04.11, table 7.4 & figure 8.3 and GSM phase 2 04.11 7.3.1, in line with GSM 03.40. Information exchanged on the interface : V1 V2 M M M M M M M O
(1)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 66 / 135
CIT
Message Identification RPData

Parameters Priority indicator Message type indicator Message reference Originator Address Destination Address RPUser data (1) (2) (3) (4) (5)
V1 V2 M M M M M M
M M M M M
RCF>MS (M) means Mandatory (O) means Optional Figure 43. RPData message layout Notes: (1) : Set to 0. Priority indicator (bit 6 of the first octet) is not significant in phase 2 message. (2) : Sequence number used to link a RP_Ack or RP_Error message to the RP_Data transfer attempt; its value may be the transaction number. (3) : Service Center Address. Refer to < [4] page 6>. (4) : Not relevant, so length value = 0. (5) : Same as received from the SC. Length <= 234 bytes.
5.5.1.2 RPERROR layout Ref : GSM phase 1 04.11 table 7.6 & figure 8.5 and GSM phase 2 04.11 7.3.4, in line with GSM 03.40. Information exchanged on the interface : Message Identification RPError Parameters Message type indicator Message reference RPCause Cause value Diagnostic field RPUser Data V1 V2 M M M M M M
(1)
MS>RCF (M) means Mandatory (O) means Optional
(2)
Figure 44. RPError message layout (1) : the possible causes are indicated in GSM phase 1 04.11 table 8.4 and GSM phase 2 04.11 8.2.5.4. Diagnostic field is ignored when received. (2) : RPUser Data has to be forwarded by the RCF in SMDeliveryFailure of ForwardShortMessage (diagnostic information).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 67 / 135
CIT
5.5.1.3 RPACK layout

Ref : GSM 04.11 table 7.5 & figure 8.4, in line with GSM 03.40. and GSM phase 2 04.11 7.3.3, in line with GSM 03.40. Information exchanged on the interface : Message Identification RPAck MS>RCF Parameters Message type indicator Message reference V1 V2 M M M M
(M) means Mandatory (O) means Optional Figure 45. RPAck message layout 5.5.1.4 Specific defense treatments upon RPlayer 97VFT100000348VRM1 Any additional IE not described in the RP messages shall be ignored. RP layer protocol; unknown or unforeseen message reference The RP entity within the MSC shall ignore any RP message whose Message Reference is missing or not associated with active short message transfer. The CPDATA message carrying the RPDU shall be acknowledged by a CPACK. RP layer protocol; unknown or unforeseen message type The RP entity within the MSC shall ignore any RP Message whose RP message Type is missing or not corresponding to ms>n message type. It shall also ignore any RP message outside the specified sequence. The CPDATA message carrying the RPDU shall be acknowledged by a CPACK. RP layer protocol; Nonsemantical mandatory IE errors In the case of an invalid RPDU (RPERROR with a missing RPcause IE) the MSC shall acknowledge it by a CPACK. The MSC shall also return a ForwardShortMessage error with SMdeliveryfailure(protocol error). 5.5.2 CPACK This message is sent to acknowledge a CPDATA message : it is sent either by the MS (via the BSS) to the RCF or by the RCF (via the BSS) to the MS. Identity of the interface : MIRSMBSM Type of interface : BSSAP (DTAP) message Ref : GSM phase 1 04.11 table 7.2 GSM phase 2 04.11 7.2.2 Information exchanged on the interface :
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 68 / 135
CIT
Message Identification CPACK (DTAP)
Parameters Protocol discriminator Transaction Identifier Message Type M M M M M M
MS<>RCF (M) means Mandatory (O) means Optional Figure 46. CPACK message layout
5.5.3 CPERROR This message is sent by the RCF to the MS or by the MS to the RCF to report invalid CPDATA content. Identity of the interface : MIRSMBSM Type of interface : BSSAP (DTAP) message Ref : GSM phase 1 04.11 table 7.3 GSM phase 2 04.11 7.2.3 Information exchanged on the interface : Message Identification CPERROR (DTAP) Parameters Protocol discriminator Transaction Identifier Message Type CPcause MS<RCF MS>RCF (M) means Mandatory (O) means Optional Figure 47. CPERROR message layout (1) : the possible causes are indicated in GSM phase 1 04.11 table 8.2 and GSM phase 2 04.11 8.1.4.2 V1 V2 M M M M M M M M
(1)
5.5.4 Specific defense treatments upon DTAP protocol (CPlayer) Refer to < [17] page 6>.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 69 / 135
CIT
5.6 MIRSMRSM : Interface inside the RCF in the VMSC

5.6.1 MI_DBL_STR_RES This message is sent by an SMT transaction in RCF which has finished to transfer a Short Message to the MS, to an other SMT transaction in RCF which is awaiting to forward a Short Message to the same MS. Identity of the interface : MIRSMRSM Type of interface : Internal message Ref : None Information exchanged on the interface : None.
5.6.2 MI_DBL_STR_ERR This message is sent by an SMT transaction in RCF which has not transfered with success a Short Message (CPERROR, RPERROR or CLEAR REQUEST received from the MS) to an other SMT transaction in RCF which is awaiting to forward a Short Message to the same MS. Identity of the interface : MIRSMRSM Type of interface : Internal message Ref : None Information exchanged on the interface : None.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 70 / 135
CIT
6 INTERFACE WITH OTHER FUNCTIONS 6.1 Security Interface

6.1.1 Between VLR and HLR 6.1.1.1 NoteSubscriberPresent (phase 1) The message NotesubscriberPresent is sent by the VLR (SC function) to the HLR (SMT function) when the MS is again reachable. Identity of the interface : MIVSCHSM Type of interface : MAP Ref : GSM phase 1 09.02 fig. 6.2/13 (Sheet 2 of 2) Information exchanged on the interface : Message Identification Note Subscriber Present (Invoke) MIMSPI VLR>HLR 6.1.1.2 ReadyForSM (phase 2) The message ReadyForSM is sent by the VLR (SC function) to the HLR (SMT function) when the MS is again reachable. Identity of the interface : MIVSCHSM Type of interface : MAP Ref : GSM phase 2 09.02 14.6.5 Information exchanged on the interface : Parameters imsi V1 M
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 71 / 135
CIT
Message Identification ReadyForSM (Invoke) MIRFSMI VLR>HLR ReadyForSM (Error) MIRFSME HLR>VLR ReadyForSM (Result) MIRFSMR HLR>VLR (M) means Mandatory (O) means Optional
Parameters imsi alertReason (msPresent (memoryAvailable
V2 M M
(1)
DataMissing UnexpectedDataValue FacilityNotSupported UnknownSubscriber
(2) (3)
none
Figure 48. ReadyForSM (VLR>HLR) message layout Notes: (1) : Use of mspresent by SC and LR function in VLR, use of memory available by SMO function in VLR. (2) : If the HLR does not support the MNRF,MCEF and MWD feature. Never sent by our HLR. (3) : If the IMSI is unknown at HLR.
6.1.1.2.1 Protocol fallback For mspresent alert reason, NoteSubscriberPresent is used instead of ReadyForSM if the HLR supports MAP V1 only. For memoryavailable alert reason, a facility not supported error is returned to RCF by the VLR. 6.1.2 Within VLR This interface is used by SMT function to ask SC (Security) function for authentication procedures after a successful paging.
1AA 00014 0004 (9007) A4 ALICE 04.10
Identity of the interface : MIVSMVSC Type of interface : internal to VLR Ref : no GSM reference Information exchanged on the interface : see [7] page 6.
ED
04 AAC020298400DS 135 En 72 / 135
CIT
6.1.3 Within RCF This interface is used by SC function to provide the result of the IMEI check to continue short message service establishment. Identity of the interface : MIRSMRSC Type of interface : internal to RCF Ref : no GSM reference Information exchanged on the interface : see [7] page 6.
6.2 LOCATION REGISTRATION INTERFACE

6.2.1 Within HLR This interface is used by LR function to inform SMT function that the MS is again reachable. Identity of the interface : MIHLRHSM Type of interface : internal to HLR Ref : no GSM reference Information exchanged on the interface : Message Identification Note MS present MIMSPRESENT Parameters IMSI (M)
(M) means Mandatory (O) means Optional Figure 49. Note MSpresent (HLR LR>HLR SMT) message layout
6.2.2 Between VLR and RCF This interface is used by LR function to inform SMT function that the ForwardCheckSS Indication has to be forwarded to the MS.
1AA 00014 0004 (9007) A4 ALICE 04.10
Identity of the interface : MIRSMVLR Type of interface : Internal Ref : No GSM reference Information exchanged on the interface : see [10] page 6.
ED
04 AAC020298400DS 135 En 73 / 135
CIT
6.2.3 Between VLR and HLR The message ReadyForSM (phase 2) or NoteSubscriberPresent (phase 1) is sent by the VLR (LR function) to the HLR (SMT function) when the MS is again reachable. Identity of the interface : MIVLRHSM Type of interface : MAP Ref : GSM phase 1 09.02 fig.6.2/13 (Sheet 2 of 2) GSM phase 2 09.02 14.6.5 Information exchanged on the interface : see < 6.1.1 page 71>
6.3 Short message originating

The message ReadyForSM is sent by the VLR (SMO function) to the HLR (SMT function) when the MS indicates memory available situation (only phase 2 feature). Identity of the interface : MIVMOHSM Type of interface : MAP Ref : GSM phase 2 09.02 14.6.5 Information exchanged on the interface : see < 6.1.1 page 71>
6.4 Paging Interface

6.4.1 Within VLR This interface allows SMT function to ask PA (Paging) function for establishment of the radio contact with the called MS. Identity of the interface : MIVSMVPA Type of interface : internal to VLR Ref : no GSM reference Information exchanged on the interface : see [6] page 6.
6.4.2 Within RCF This interface is used by the SMT function to inform the PA function that the call is released so that the PA function can terminate its processing without waiting for a timer expiry.
1AA 00014 0004 (9007) A4 ALICE 04.10
Identity of the interface : MIRSMRPA Type of interface : internal to RCF Ref : no GSM reference Information exchanged on the interface : see [6] page 6.
ED
04 AAC020298400DS 135 En 74 / 135
CIT
6.5 Call Barring Interface

This interface is used in HLR by SMT function to ask CB (Call barring) function for call barring checking.
Identity of the interface : MIHSMHCB Type of interface : internal to HLR Ref : no GSM reference Information exchanged on the interface : see [12] page 6.
6.6 Radio Resource Management Interface

This interface is used by SMT function to ask the Radio Resource Management (RM) function for release of the channel used for the call. The interface is also used by RM to indicate to SMT that the channel allocated for short message purpose has to be released or that the SAPI 3 has not been established at the radio side. SMT has to release its resources and to ask RM for channel release. Identity of the interface : MIRSMRRM Type of interface : internal to RCF Ref : no GSM reference Information exchanged on the interface : see [8] page 6.
6.7 Charging Data Collection Interface

This interface is used by SMT function in the RCF: for billing purpose at the successful completion of a SMS terminating call procedure, charging tickets have to be generated by the GMSC and by the MSC as well. Identity of the interface : MIRSMRCG Type of interface : internal to RCF Ref : no GSM reference Information exchanged on the interface : see [13] page 6.
6.8 Observation Interface

The purpose of this interface is to take into account the main events during a short message service terminating call. The counters incremented during a SMS terminating call are listed in [11] page 6.
6.9 Supplementary Service Handling interface

1AA 00014 0004 (9007) A4 ALICE 04.10
The message MI_FCSS_SH_REQ is sent by SMT function to ask SH function in the RCP to open an independant SS transaction with the mobile in order to forward the ForwardCheckSSIndication. Identity of the interface : MIRSHRSM 04 AAC020298400DS 135 En 75 / 135
ED
CIT

Type of interface : internal to RCF Ref : no GSM reference Information exchanged on the interface : see [14] page 6
6.10 MM interface
This interface is used to inform the other activities of the same mobile that the MM procedures for SMS are ended. Refer to [6] page 6. Identity of the interface : MIRMMRMM Type of interface : internal to RCF Ref : no GSM reference Messages exchanged on the interface : MI_DBL_STR_RES MI_DBL_STR_ERR
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 76 / 135
CIT
7 SPONTANEOUS MESSAGES TO OPERATOR

Spontaneous messages are issued to the operator if SMT function detects, during its operation, an illegal or erroneous event. Spontaneous messages in RCF WR_SM_300 wording meaning
parameters
CALLED NUMBER/SCCP ROUTE TRANSLATION FAILURE CLDLEN= CLDNBR= This warning is edited when the analysis of the called number to determine the SCCP route informations has failed (No SCCP route from MSISDN number or from MSC address or from SC address). CLDLEN = Called number length CLDNBR = Called number
WR_SM_302 wording meaning
parameters
LMSI NOT PROVIDED IN FORWARD SHORT MESSAGE This warning is edited when the LMSI is not provided in ForwardShortMessage operation. The transfer is performed with the provided IMSI. IMSI of the subscriber = IMSI
Spontaneous messages in HLR WR_SM_301 wording meaning parameters
TRANSLATION ERROR CALLED NUMBER / SCCP ROUTE This warning is edited when it is impossible to find SCCP route of the IWMSC. MSCADD = IWMSV address
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 77 / 135
CIT
8 ERROR GENERATED BY SMT FUNCTION 8.1 Definition of Internal errors generated by SM in HLR
ERR_SM_100 Data Missing in the MI_S_RGI_SM_I (MAP Send Routing Info for SM) message. ERR_SM_101 Unexpected Data Value in the MI_S_RGI_SM_I message ERR_SM_102 Data Missing in the MI_S_MW_I (MAP Set message waiting data) message or MI_R_SMD_S_I (MAP Report SM Delivery Status) message ERR_SM_103 Short Message Terminating function is not supported in VMSC ERR_SM_104 Unexpected Data Value in the MI_S_MW_I message or MI_R_SMD_S_I message ERR_SM_105 AbsentSubscriber due to MNRF set and non priority message ERR_SM_106 Data missing in MI_R_F_SM_I (MAP Ready for SM) message ERR_SM_107 Unexpected data value in MI_R_F_SM_I message ERR_SM_108 Unknown IMSI received in MI_R_F_SM_I message ERR_SM_109 A MI_S_RGI_SM_I message has been received from an entity which does not belong to HPLMN ERR_SM_110 Unknown MSISDN received in MI_S_RGI_SM_I message ERR_SM_111 Teleservice not provisioned to the MS. ERR_SM_112 MWD list full. ERR_SM_113 MS barred due to Operator Determined Barring ERR_SM_114 Incoming call barring applicable. ERR_SM_115 Spare. ERR_SM_116 No MSC address in the subscriber data, or MS not allowed to roam. ERR_SM_117 04 AAC020298400DS 135 En 78 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
Unknown MSISDN received in MI_S_MW_I message or MI_R_SMD_S_I message
8.2 Definition of Internal Errors generated by SM in VLR

ERR_SM_200 Spare. ERR_SM_201 Spare. ERR_SM_202 Unidentified subscriber. ERR_SM_203 AbsentSubscriber.
8.3 Definition of internal errors generated by SM in RCF

ERR_SM_300 (GMSC) RP_Originator Address or RP_Destination Address are not correct in RP_MT_DATA message. ERR_SM_301 (VMSC) Unidentified subscriber (IMSI not received in RP_DA) in phase 1 dialogue with GMSC. ERR_SM_302 (VMSC) USI syntactically incorrect in TC_BEGIN ERR_SM_303 (GSMC) Unexpected data value in the S_RGI_SM_R. ERR_SM_304 (GMSC) T_smr, timer on S_RGI_SM opration, expiry. ERR_SM_305 (GMSC) Abort Indication (RCF_HLR Transaction). ERR_SM_306 (VMSC) Destination reference of USI is not an IMSI address ERR_SM_307 (VMSC) CP_Userdata IE missing or not matching its length in CP_Data ERR_SM_308 (VMSC) Timer TC1N expiry. ERR_SM_309 (VMSC) Timer TR1N expiry. ERR_SM_310 (GMSC) Impossible translation of the MSISDN into SCCP route. ERR_SM_311 (GMSC) Impossible translation of the MSC address into SCCP route. ERR_SM_312 (VMSC) Abort Indication (RCF_VLR transaction). 04 AAC020298400DS 135 En 79 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
ERR_SM_313 (GMSC) (VMSC) Short Message Terminating function not supported in the MSC. ERR_SM_314 (VMSC) Unexpected data value or SC address too long in the MI_F_SM_I message. ERR_SM_315 (GMSC) (VMSC) Abort Indication (RCF_RCF transaction). ERR_SM_316 (GMSC) Tfsm, timer on F_SM operation, expiry. ERR_SM_317 (VMSC) Lack of IMSI in ForwardShortMessage. ERR_SM_318 (GMSC) Tmwd, timer on S_MW operation, expiry. ERR_SM_319 (VMSC) Tsism, timer on SINF_SMT operation, expiry. ERR_SM_320 (GMSC) Map error SMDeliveryFailure, with parameter value memory capacity exceeded, received in MI_F_SM_E message. ERR_SM_321 (GMSC) Map error SMDeliveryFailure, with parameter value MS protocol error, received in MI_F_SM_E message. ERR_SM_322 (GMSC) Map error SMDeliveryFailure, with parameter value MS not equipped, received in MI_F_SM_E message. ERR_SM_323 (GMSC) A subsequent RP_MT_Data has been received for a subscriber different from the first. ERR_SM_324 (GMSC) A subsequent RP_MT_Data has been received when an other is already being treated. ERR_SM_325 (GMSC) A subsequent RP_MT_Data has been received with priority low and MWD is set. ERR_SM_326 (IWMSC) Unexpected data value in MI_A_SC_I message ERR_SM_327 (IWMSC) Impossible translation of the SC address into SCCP route ERR_SM_328 (GMSC) RP User data is too long to be carried by the MAP ERR_SM_329 (VMSC) IMSI received in USI and LMSI not present in FSM message ERR_SM_330 (VMSC) Default error due to lack of RPCause in RPError or CPCause in CPError ERR_SM_331 (VMSC) 04 AAC020298400DS 135 En 80 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
Max number of transaction waiting at VMSC reached

ERR_SM_332 (GMSC) Memory capacity exceeded not reported to HLR in ReportSMDelivery message due to MAP v1 dialogue with HLR
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 81 / 135
CIT
9 TIMERS 9.1 Timer in RCF

9.1.1 SMSGMSC T_SCRLS Supervises at GMSC the release of the SCCP connection or the receipt of another awaited short message from the SC. PLMN data Range : 15s > 60s Default value = 60 s. Supervises MAP SendRoutingInfoForSM operation System parameter Value = refer to < [19] page 6>. Supervises MAP ForwardShortMessage operation System parameter Value = refer to < [19] page 6>. Supervises MAP SetMessageWaitingData or ReportSMDeliveryStatus operation System parameter Value = refer to < [19] page 6>.
T_smr
T_fsm
T_mwd
9.1.2 VMSC TC1N Supervises the reception of CPACK message from the MS. PLMN data Range : 2s > 30s Default value : 20 s for SACCH and SDCCH. Supervises the reception of RPACK message from the MS. PLMN data Range : 2s > 60s with constraint : 2TC1N + 5 = TR1N Defaut value : 45 s Supervises the reception of subsequent short message in the same TCAP dialogue. PLMN data Range: 15s > 60s Default value = 20s Delay for sending a Channel release (to ensure the BSS is able to send its last DTAP message). PLMN data Range: 100ms > 2s Default value = 200ms Supervises the receipt of a TC_CONT from the SMSGMSC after an empty TC_BEGIN. system parameter Default value = 10s
TR1N
T_SUBSEQ
T_BEFORE_REL
T_CONT
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 82 / 135
CIT
9.1.3 IWMSC T_WAIT_SSCS

Activated when sending RPAlert to the SC See < [15] page 6> for the value.
9.2 Timer in VLR

None
9.3 Timer in HLR

T_asc Supervises MAP AlertServiceCenter operation System parameter Value = refer to < [20] page 6>. Watch dog timer for the duration of a SC address in the MWD file. PLMN data Range: maximum 10 days, be aware of impacts on the storage capacity of MWD file. Default value = 24 hours. Activated when sending MI_A_SC_WR (AlertServiceCenterWithoutResult) phase 1 only message to the IWMSC. See < [15] page 6> for the value. Triggered by the HLR if an Alert procedure is requested and neither MCEF nor MNRF are set, to prevent a race situation with a successful transfer. System parameter Value = 5s
T_MWD
T_WAIT_SSCS
T_RACE
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 83 / 135
CIT
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
10 SDL DIAGRAMS HLR
04
AAC020298400DS
135
En
84 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
85 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
86 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
87 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
88 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
89 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
90 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
91 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
92 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
93 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
94 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
95 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
96 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
97 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
11 SDL DIAGRAMS VLR
04
AAC020298400DS
135
En
98 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
99 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
100 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
101 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
12 SDL DIAGRAMS RCF
04
AAC020298400DS
135
En
102 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
103 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
104 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
105 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
106 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
107 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
108 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
109 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
110 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
111 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
112 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
113 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
114 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
115 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
116 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
117 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
118 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
119 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
120 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
121 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
122 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
123 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
124 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
125 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
126 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
127 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
128 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
129 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
130 / 135
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CIT
04
AAC020298400DS
135
En
131 / 135
ANNEXE A OVERVIEW OF PROTOCOLS USED IN SMSMT
A.1 Network structure

SC
PLMN SMS GMSC link 1 IWFSMS link 2 link 5 link 3 MSC link 6 MS
SMS IWMSC link 1
link 2
HLR
link 4
VLR
A.2 Transfer protocols

A.2.1 Simplified protocol layer overview
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 132 / 135
CIT
SC
SMS GMSC SMS IWMSC
MSC
MS
SMAL Appli SMTL Transf SMRL Relay SMLL Layer 3 (SCCP) (TCAP) (SCCP) RPMT N (SMSAP) TC (MAP E) CP (DTAP) (SCCP) RS MAP RP
SMS SMRL SMR entity MNSMS CM sublayer MMSMS SMC entity MM sublayer RR sublayer
Layer 2 TPDU at SMTL : (1) (1)
(1) (2)
SMSDELIVER conveying a SM from SC to MS SMSSTATUSREPORT conveying a status report from SC to MS SMSDELIVERREPORT (if necessary) (2) SMSSUBMIT conveying a SM from MS to SC (2) SMSCOMMAND conveying a command from MS to SC SMSSUBMITREPORT (if necessary) Use of short message terminating procedure Use of short message Originating procedure
A.2.2 SC/PLMN Refer to Link 1. No mandatory protocol between the Service Centre and the PLMN is specified by GSM. The protocol used is an Alcatel generic implementation which uses the Signalling Connection Control Part (SCCP) of CCITT no 7. The subsystem user of SCCP for SMS is called SMSAP. See < [4] page 6>. RPMTData: for transferring a SMSDeliver or SMSStatusreport from SC to MS, RPMTAck: for acknowledging an RPMTData, RPMTError: for informing of an unsuccessful RPMTData transfer attempt. The RPMSISDN parameter of RPMTError can give the MSISDN Alert to be used by the SC. RPAlert: for alerting the SC that the MS has recovered operation A.2.3 SMSGMSC/HLR and HLR/SMSIWMSC
1AA 00014 0004 (9007) A4 ALICE 04.10
Refer to Link 2. MAP is used. MAP messages used to obtain routing information:
ED
04 AAC020298400DS 135 En 133 / 135
CIT

Send routing information for short message (from SMSGMSC to HLR). Short message routing information or an error message (result sent by HLR to SMSGMSC).
In phase 2 MAP dialogue, HLR may, if necessary, send to the SMSGMSC the MSISDN Alert of the MS and the state of MWI in Inform Service Center message In case of phase 1 MAP dialogue between SMSGMSC and HLR, MAP messages used to request inclusion of a Service Centre address in the Message Waiting Data in the HLR: Set message waiting data (from SMSGMSC to HLR). Set message waiting data ack or an error message (result sent by HLR to SMSGMSC). In case of phase 2 MAP dialogue between SMSGMSC and HLR, MAP messages used to report the SM delivery status to the HLR Report SM delivery status (from SMSGMSC to HLR). Report SM delivery status ack or an error message (result sent by HLR to SMSGMSC). If necessary, the HLR, on recept of this message set the Service Center address in the Message Waiting Data. The MAP message: Alert Service Centre (phase 2) or Alert Service Centre Without Result (phase 1) is used by the HLR to request a SMSIWMSC to inform a Service Centre that the MS is again available or the MS has again available memory or a Short message has been successfuly delivered to the MS A.2.4 SMSGMSC/MSC Refer to Link 3. MAP is used. The MAP message Forward short message is used by the SMSGMSC to request the servicing MSC to forward a short message to the MS. The MSC sends back a forwarding acknowledge message if the short message has been successfully delivered to the MS, otherwise an error message (absent subscriber, system failure, ...) is sent back to the SMSGMSC. A.2.5 VLR/HLR Refer to Link 4. MAP is used. In case of phase 1 MAP dialogue between VLR and HLR, the MAP message: Note subscriber present is used by a VLR to inform the HLR that the MS may be reachable again. In case of phase 2 MAP dialogue between VLR and HLR, the MAP message: Ready for SM is used by a VLR to inform the HLR that the MS may be reachable again or the MS has available memory. A.2.6 MSC/VLR
1AA 00014 0004 (9007) A4 ALICE 04.10
Refer to Link 5. The MSC uses the message Send information for short message to retrieve subscriber information from VLR.
ED
04 AAC020298400DS 135 En 134 / 135
CIT
The message Complete call is used by the VLR to request the MSC to transfer the short message to the MS. The message Ready for SM is used by the MSC, when a subscriber indicates memory available situation, to request VLR to initiate an Alert procedure. A.2.7 MSC/MS Refer to Link 6. BSSAP is used. Direct Transfer Application Part (DTAP): CPmessages are DTAP messages used to transfer on the Air Interface SMS data between the MSC and the MS. In these messages the Data Link Connection Identification (DLCI) parameter indicates the SAPI value 3 (reserved to SMS). CPmessages during a short message transfer procedure : CPData : From MSC to MS contains a RPDATA (contains itself a SMSDELIVER or a SMSSTATUSREPORT) From MS to MSC contains a RPACK or a RPERROR (response of the RPDATA) The RPERROR may contains itself a SMSDELIVERREPORT to be forwarded from MS to SC. CPAck : acknowledge of the CPData CPError CPmessages when the MS indicates that memory capacity is again available : CPData : From MS to MSC contains a RPSMMA (SM Memory Available) From MSC to MS contains a RPACK or a RPERROR (response of the RPSMMA) CPAck : acknowledge of the CPData CPError Base Station System Management Application Part (BSSMAP): The SAPI 3 establishment is initiated by the BSC itself for the first transfer request from the MSC (CPData). SAPI N Reject message is sent by the BSC when the BSS is not able to send the short message (BSS not equipped, MS not equipped, processor overload, O&M intervention).
FIN DE DOCUMENT
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04 AAC020298400DS 135 En 135 / 135
CIT

Alcatel Functional Specification for Short Message Service Terminating

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Alcatel Functional Specification for Short Message Service Terminating

Transféré par

Droits d'auteur :

Formats disponibles

FUNCTIONAL SPECIFICATION

1AA 00014 0004 (9007) A4 ALICE 04.10

SHORT MESSAGE SERVICE TERMINATING SMT

04 AAC020298400DS 135 En 1 / 135

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 2 / 135

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 3 / 135

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 4 / 135

1AA 00014 0004 (9007) A4 ALICE 04.10

[2] [3] [4] [5] [6] [7] [8] [9]

1AA 00014 0004 (9007) A4 ALICE 04.10

BSSAP BSSMAP DTAP DT1 HLR HLR SMT MAP MCEF 04

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 7 / 135

1.1 Options list in FS Short Message Terminating

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 8 / 135

FODB001 FHB001 FSC011

Operator Determined Barring function Hot billing option Authentication 1/n

VLR PA RCF SMT SMT SC CB

Figure 1. Functional environment of the Short Message terminating function

04 AAC020298400DS 135 En 9 / 135

2.2 SMS connection between the SC and the SMSGMSC

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 10 / 135

04 AAC020298400DS 135 En 11 / 135

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 12 / 135

2.2.6 Scenarios 2.2.6.1 Successful case

Figure 2. SMS connection setup (1/3)

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 13 / 135

FORWARDING OF MULTIPLE SHORT MESSAGES SMSGMSC

Figure 3. SMS connection setup (2/3)

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 14 / 135

2.2.6.2 Unsuccessful cases PARAMETERS ERROR DETECTED AT APPLICATION LEVEL

Figure 4. SMS connection setup (3/3)

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 15 / 135

2.3 Retrieval of routing information procedure

04 AAC020298400DS 135 En 16 / 135

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 17 / 135

2.3.2 Scenarios 2.3.2.1 Successful case

SMSGMSC SMT MIS RGISMI (TCBegin)

MIICBCHECK MINOICB MISRGISMR (TCEnd) forward short message towards VMSC

Figure 5. Retrieval of routing information from the HLR(1/2)

SMSGMSC SMT MISRGISMI (TCBegin)

Figure 6. Retrieval of routing information from the HLR(2/2)

04 AAC020298400DS 135 En 18 / 135

2.4 MSC number inquiry

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 19 / 135

2.5 Forwarding of short message procedure

1AA 00014 0004 (9007) A4 ALICE 04.10

04 AAC020298400DS 135 En 20 / 135

1AA 00014 0004 (9007) A4 ALICE 04.10

1AA 00014 0004 (9007) A4 ALICE 04.10