Mobile Application Part Interface (MAPI) Specification

Mobile Application Part Interface (MAPI) Specification

Mobile Application Part Interface (MAPI)

SpecificationVersion 1.1 Edition 7.20141001

Updated October 25, 2014Distributed with Package openss7-1.1.7.20141001

Copyright c© 2008-2014 Monavacon LimitedAll Rights Reserved.

Abstract:

This document is a Specification containing technical details concerning the imple-mentation of the Mobile Application Part Interface (MAPI) for OpenSS7. It containsrecommendations on software architecture as well as platform and system applicabilityof the Mobile Application Part Interface (MAPI). It provides abstraction of the MobileApplication Part (MAP) interface to these components as well as providing a basis forMobile Application Part control for other Mobile Application Part protocols.

Brian Bidulock <[email protected]> for

The OpenSS7 Project <http://www.openss7.org/>

mailto:[email protected]

http://www.openss7.org/

Published by:

OpenSS7 Corporation1469 Jefferys CrescentEdmonton, Alberta T6L 6T1Canada

Copyright c© 2008-2014 Monavacon LimitedCopyright c© 2001-2008 OpenSS7 CorporationCopyright c© 1997-2000 Brian F. G. Bidulock

All Rights Reserved.

Unauthorized distribution or duplication is prohibited.

Permission is granted to copy, distribute and/or modify this document under the terms of theGNU Free Documentation License, Version 1.3 or any later version published by the Free SoftwareFoundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy ofthe license is included in the section entitled [GNU Free Documentation License], page 405.

Permission to use, copy and distribute this documentation without modification, for any purposeand without fee or royalty is hereby granted, provided that both the above copyright notice andthis permission notice appears in all copies and that the name of OpenSS7 Corporation not beused in advertising or publicity pertaining to distribution of this documentation or its contentswithout specific, written prior permission. OpenSS7 Corporation makes no representation aboutthe suitability of this documentation for any purpose. It is provided “as is” without express orimplied warranty.

Notice:

OpenSS7 Corporation disclaims all warranties with regard to this documentation including all im-plied warranties of merchantability, fitness for a particular purpose, non-infringement, or title; thatthe contents of the document are suitable for any purpose, or that the implementation of suchcontents will not infringe on any third party patents, copyrights, trademarks or other rights. In noevent shall OpenSS7 Corporation be liable for any direct, indirect, special or consequential dam-ages or any damages whatsoever resulting from loss of use, data or profits, whether in an action ofcontract, negligence or other tortious action, arising out of or in connection with any use of thisdocument or the performance or implementation of the contents thereof.

http://www.openss7.com/

http://www.monavacon.com/


mailto:[email protected]

i

Short Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 The Mobile Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 MAPI Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5 Diagnostics Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Addendum for 3GPP Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

A Mapping MAPI Primitives to 3GPP TS 29.002 . . . . . . . . . . . . . . 379

B State/Event Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

C Primitive Precedence Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

D MAPI Header File Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

iii

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Intent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

ISO 9000 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4U.S. Government Restricted Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.1 Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Definitions, Acronyms, Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 The Mobile Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Model of the MAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 MAP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.2.1 Local Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2.2 Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2.3 Specific Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3 Service Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.1 Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.1.1 Location Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.1.2 Paging and Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.1.3 Access Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.1.4 Handover Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.1.5 Authentication Management Services . . . . . . . . . . . . . . . . . . . . . . 132.3.1.6 Security Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.7 IEMI Managment Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.8 Subscriber Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.9 Identity Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.10 Fault Recovery Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.11 Subscriber Information Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.3.2 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.2.1 Subscriber Tracing Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.2.2 Miscellaneous Operation and Maintenance Services . . . . . . . . . 14

2.3.3 Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.3.1 Call Handling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3.4 Supplementary Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.4.1 Supplementary Service Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3.5 SMS Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.5.1 Short Message Service Management Services . . . . . . . . . . . . . . . 15

2.3.6 Network-Requested PDP Context Activation . . . . . . . . . . . . . . . . . . . . 15

iv Mobile Application Part Interface (MAPI)

2.3.6.1 Network-Requested PDP Context Activation Services . . . . . . 152.3.7 Location Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.7.1 Location Service Management Services . . . . . . . . . . . . . . . . . . . . . 152.4 MAP User Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4.1 Mobile Switching Centre (MSC) Service Sets . . . . . . . . . . . . . . . . . . . . 152.4.2 Home Location Register (HLR) Service Sets . . . . . . . . . . . . . . . . . . . . . 172.4.3 Visitor Location Register (VLR) Service Sets . . . . . . . . . . . . . . . . . . . . 182.4.4 Equipment Identity Register (EIR) Service Sets . . . . . . . . . . . . . . . . . 192.4.5 Serving GPRS Support Node (SGSN) Service Sets . . . . . . . . . . . . . . 192.4.6 Gateway GPRS Support Node (GGSN) Service Sets . . . . . . . . . . . . . 202.4.7 Interworking MSC (IWMSC) for Short Message Service Service Sets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.4.8 Gateway MSC (GMSC) for Short Message Service Service Sets . . 202.4.9 Gateway Mobile Location Center (GMLC) Service Sets . . . . . . . . . . 21

3 MAPI Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Local Management Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1.1 MAP Information Reporting Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1.2 MAP User Bind Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1.3 MAP User Unbind Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.4 Receipt Acknowledgement Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.5 Options Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.6 Error Acknowledgement Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.2 Dialogue Handling Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.1 Dialogue Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.2.1.1 User Primitives for Successful MAP Dialogue Establishment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.1.2 Provider Primitives for Successful MAP DialogueEstablishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.2 Dialogue Component Transfer Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2.2.1 User Primitives for Component Transfer . . . . . . . . . . . . . . . . . . . 263.2.2.2 Provider Primitives for Component Transfer . . . . . . . . . . . . . . . 27

3.2.3 Dialogue Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2.3.1 User Primitives for Dialogue Abort . . . . . . . . . . . . . . . . . . . . . . . . 283.2.3.2 Provider Primitives for Dialogue Abort . . . . . . . . . . . . . . . . . . . . 28

4 MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.1 Management Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.1.1 Information Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.1.2 Information Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.1.3 Bind Application Context Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1.4 Bind Application Context Acknowledgement . . . . . . . . . . . . . . . . . . . . 364.1.5 Unbind Application Context Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.1.6 Options Management Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.1.7 Get Protocol Address Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.1.8 Get Protocol Address Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 414.1.9 Options Management Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . 424.1.10 Error Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.1.11 Successful Receipt Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.2 Association Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.2.1 Association Establishment Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.2.2 Association Establishment Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

v

4.2.3 Association Establishment Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.2.4 Association Establishment Confirmation . . . . . . . . . . . . . . . . . . . . . . . . 48

4.3 Component Transfer Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.3.1 Component Delimitation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.3.2 Component Delimitation Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.4 Association Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.4.1 Association Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.4.2 Association Release Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.4.3 Association Abort Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.4.4 Association User Abort Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4.5 Association Provider Abort Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 554.4.6 Association Notice Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.5 Secure Transport Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.5.1 Secure Transport Class 1 Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.5.2 Secure Transport Class 1 Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.5.3 Secure Transport Class 2 Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.5.4 Secure Transport Class 2 Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.5.5 Secure Transport Class 3 Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.5.6 Secure Transport Class 3 Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.5.7 Secure Transport Class 4 Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.5.8 Secure Transport Class 4 Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4.6 Service Specific Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.6.1 Activate Supplementary Service Request . . . . . . . . . . . . . . . . . . . . . . . . 654.6.2 Activate Supplementary Service Indication . . . . . . . . . . . . . . . . . . . . . . 664.6.3 Activate Supplementary Service Response . . . . . . . . . . . . . . . . . . . . . . . 674.6.4 Activate Supplementary Service Confirmation . . . . . . . . . . . . . . . . . . . 684.6.5 Activate Traceec Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.6.6 Activate Traceec Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.6.7 Activate Traceec Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714.6.8 Activate Traceec Mode Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.6.9 Alert Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.6.10 Alert Service Center Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744.6.11 Alert Service Center Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754.6.12 Alert Service Center Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764.6.13 Allocate Handover Number Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 774.6.14 Allocate Handover Number Indication . . . . . . . . . . . . . . . . . . . . . . . . . 784.6.15 Allocate Handover Number Response . . . . . . . . . . . . . . . . . . . . . . . . . . 794.6.16 Allocate Handover Number Confirmation . . . . . . . . . . . . . . . . . . . . . . 804.6.17 Any Time Modification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.6.18 Any Time Modification Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.6.19 Any Time Modification Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834.6.20 Any Time Modification Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 844.6.21 Any Time Interrogation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.6.22 Any Time Interrogation Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864.6.23 Any Time Interrogation Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874.6.24 Any Time Interrogation Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 884.6.25 Any Time Subscription Interrogation Request . . . . . . . . . . . . . . . . . . 894.6.26 Any Time Subscription Interrogation Indication . . . . . . . . . . . . . . . . 904.6.27 Any Time Subscription Interrogation Response . . . . . . . . . . . . . . . . . 914.6.28 Any Time Subscription Interrogation Confirmation . . . . . . . . . . . . . 924.6.29 Authentication Failure Report Request . . . . . . . . . . . . . . . . . . . . . . . . . 934.6.30 Authentication Failure Report Indication . . . . . . . . . . . . . . . . . . . . . . 944.6.31 Authentication Failure Report Response . . . . . . . . . . . . . . . . . . . . . . . 95

vi Mobile Application Part Interface (MAPI)

4.6.32 Authentication Failure Report Confirmation . . . . . . . . . . . . . . . . . . . 964.6.33 Authenticate Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974.6.34 Authenticate Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984.6.35 Authenticate Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994.6.36 Authenticate Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.6.37 Cancel Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014.6.38 Cancel Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024.6.39 Cancel Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034.6.40 Cancel Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044.6.41 Reset Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054.6.42 Reset Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064.6.43 Reset Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074.6.44 Reset Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084.6.45 Restore Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.6.46 Restore Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.6.47 Restore Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.6.48 Restore Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.6.49 Resume Call Handling Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134.6.50 Resume Call Handling Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144.6.51 Resume Call Handling Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 1154.6.52 Resume Call Handling Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164.6.53 Search for MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174.6.54 Search for MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184.6.55 Search for MS Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.6.56 Search for MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.6.57 Check IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.6.58 Check IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.6.59 Check IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.6.60 Check IEMI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.6.61 Deactivate Supplementary Service Request . . . . . . . . . . . . . . . . . . . . 1254.6.62 Deactivate Supplementary Service Indication . . . . . . . . . . . . . . . . . . 1264.6.63 Deactivate Supplementary Service Response . . . . . . . . . . . . . . . . . . 1274.6.64 Deactivate Supplementary Service Confirmation . . . . . . . . . . . . . . . 1284.6.65 Deactivate Trace Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294.6.66 Deactivate Trace Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.6.67 Deactivate Trace Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.6.68 Deactivate Trace Mode Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . 1324.6.69 Delete Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.6.70 Delete Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344.6.71 Delete Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354.6.72 Delete Subscriber Data Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . 1364.6.73 Erase CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374.6.74 Erase CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384.6.75 Erase CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.6.76 Erase CC Entry Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.6.77 Erase Supplementatry Service Request . . . . . . . . . . . . . . . . . . . . . . . . 1414.6.78 Erase Supplementatry Service Indication . . . . . . . . . . . . . . . . . . . . . . 1424.6.79 Erase Supplementatry Service Response . . . . . . . . . . . . . . . . . . . . . . . 1434.6.80 Erase Supplementatry Service Confirmation . . . . . . . . . . . . . . . . . . . 1444.6.81 Failure Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454.6.82 Failure Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464.6.83 Failure Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.6.84 Failure Report Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

vii

4.6.85 Forward Access Signalling Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494.6.86 Forward Access Signalling Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 1504.6.87 Forward Access Signalling Response . . . . . . . . . . . . . . . . . . . . . . . . . . 1514.6.88 Forward Access Signalling Confirmation . . . . . . . . . . . . . . . . . . . . . . 1524.6.89 Forward Check SS Indication Request . . . . . . . . . . . . . . . . . . . . . . . . . 1534.6.90 Forward Check SS Indication Indication . . . . . . . . . . . . . . . . . . . . . . 1544.6.91 Forward Check SS Indication Response . . . . . . . . . . . . . . . . . . . . . . . 1554.6.92 Forward Check SS Indication Confirmation . . . . . . . . . . . . . . . . . . . 1564.6.93 Forward Group Call Signalling Request . . . . . . . . . . . . . . . . . . . . . . . 1574.6.94 Forward Group Call Signalling Indication . . . . . . . . . . . . . . . . . . . . . 1584.6.95 Forward Group Call Signalling Response . . . . . . . . . . . . . . . . . . . . . . 1594.6.96 Forward Group Call Signalling Confirmation . . . . . . . . . . . . . . . . . . 1604.6.97 Forward New IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.6.98 Forward New IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624.6.99 Forward New IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634.6.100 Forward New IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644.6.101 Obtain IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654.6.102 Obtain IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664.6.103 Obtain IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.6.104 Obtain IEMI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684.6.105 Get Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694.6.106 Get Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.6.107 Get Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714.6.108 Get Password Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.6.109 Inform Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734.6.110 Inform Service Center Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.6.111 Inform Service Center Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754.6.112 Inform Service Center Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . 1764.6.113 Insert Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774.6.114 Insert Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784.6.115 Insert Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1794.6.116 Insert Subscriber Data Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . 1804.6.117 Iterrogate Supplementary Service Request . . . . . . . . . . . . . . . . . . . 1814.6.118 Iterrogate Supplementary Service Indication . . . . . . . . . . . . . . . . . 1824.6.119 Iterrogate Supplementary Service Response . . . . . . . . . . . . . . . . . . 1834.6.120 Iterrogate Supplementary Service Confirmation . . . . . . . . . . . . . . 1844.6.121 IST Alert Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854.6.122 IST Alert Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864.6.123 IST Alert Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1874.6.124 IST Alert Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884.6.125 IST Command Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894.6.126 IST Command Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904.6.127 IST Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914.6.128 IST Command Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924.6.129 Note MM Event Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1934.6.130 Note MM Event Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944.6.131 Note MM Event Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954.6.132 Note MM Event Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1964.6.133 Mobile Originated Forward Short Message Request . . . . . . . . . . 1974.6.134 Mobile Originated Forward Short Message Indication . . . . . . . . 1984.6.135 Mobile Originated Forward Short Message Response . . . . . . . . . 1994.6.136 Mobile Originated Forward Short Message Confirmation . . . . . 2004.6.137 Note MS Present for GRPS Request . . . . . . . . . . . . . . . . . . . . . . . . . 201

viii Mobile Application Part Interface (MAPI)

4.6.138 Note MS Present for GRPS Indication . . . . . . . . . . . . . . . . . . . . . . . 2024.6.139 Note MS Present for GRPS Response . . . . . . . . . . . . . . . . . . . . . . . . 2034.6.140 Note MS Present for GRPS Confirmation . . . . . . . . . . . . . . . . . . . . 2044.6.141 Mobile Terminated Forward Short Message Request . . . . . . . . . . 2054.6.142 Mobile Terminated Forward Short Message Indication . . . . . . . . 2064.6.143 Mobile Terminated Forward Short Message Response . . . . . . . . 2074.6.144 Mobile Terminated Forward Short Message Confirmation . . . . 2084.6.145 Page Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094.6.146 Page Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2104.6.147 Page Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114.6.148 Page Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124.6.149 Prepare Group Call Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134.6.150 Prepare Group Call Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2144.6.151 Prepare Group Call Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154.6.152 Prepare Group Call Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2164.6.153 Prepare Handover Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2174.6.154 Prepare Handover Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2184.6.155 Prepare Handover Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2194.6.156 Prepare Handover Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2204.6.157 Prepare Subsequent Handover Request . . . . . . . . . . . . . . . . . . . . . . . 2214.6.158 Prepare Subsequent Handover Indication . . . . . . . . . . . . . . . . . . . . 2224.6.159 Prepare Subsequent Handover Response . . . . . . . . . . . . . . . . . . . . . 2234.6.160 Prepare Subsequent Handover Confirmation . . . . . . . . . . . . . . . . . 2244.6.161 Process Access Signalling Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 2254.6.162 Process Access Signalling Indication . . . . . . . . . . . . . . . . . . . . . . . . . 2264.6.163 Process Access Signalling Response . . . . . . . . . . . . . . . . . . . . . . . . . . 2274.6.164 Process Access Signalling Confirmation . . . . . . . . . . . . . . . . . . . . . . 2284.6.165 Process Group Call Signalling Request . . . . . . . . . . . . . . . . . . . . . . . 2294.6.166 Process Group Call Signalling Indication . . . . . . . . . . . . . . . . . . . . . 2304.6.167 Process Group Call Signalling Response . . . . . . . . . . . . . . . . . . . . . 2314.6.168 Process Group Call Signalling Confirmation . . . . . . . . . . . . . . . . . . 2324.6.169 Process Unstructured SS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2334.6.170 Process Unstructured SS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 2344.6.171 Process Unstructured SS Response . . . . . . . . . . . . . . . . . . . . . . . . . . 2354.6.172 Process Unstructured SS Confirmation . . . . . . . . . . . . . . . . . . . . . . . 2364.6.173 Provide IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2374.6.174 Provide IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2384.6.175 Provide IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2394.6.176 Provide IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404.6.177 Provide Roaming Number Request . . . . . . . . . . . . . . . . . . . . . . . . . . 2414.6.178 Provide Roaming Number Indication . . . . . . . . . . . . . . . . . . . . . . . . 2424.6.179 Provide Roaming Number Response . . . . . . . . . . . . . . . . . . . . . . . . . 2434.6.180 Provide Roaming Number Confirmation . . . . . . . . . . . . . . . . . . . . . 2444.6.181 Provide Subscriber Location Request . . . . . . . . . . . . . . . . . . . . . . . . 2454.6.182 Provide Subscriber Location Indication . . . . . . . . . . . . . . . . . . . . . . 2464.6.183 Provide Subscriber Location Response . . . . . . . . . . . . . . . . . . . . . . . 2474.6.184 Provide Subscriber Location Confirmation . . . . . . . . . . . . . . . . . . . 2484.6.185 Provide Subscriber Information Request . . . . . . . . . . . . . . . . . . . . . 2494.6.186 Provide Subscriber Information Indication . . . . . . . . . . . . . . . . . . . 2504.6.187 Provide Subscriber Information Response . . . . . . . . . . . . . . . . . . . . 2514.6.188 Provide Subscriber Information Confirmation . . . . . . . . . . . . . . . . 2524.6.189 Purge MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2534.6.190 Purge MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

ix

4.6.191 Purge MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2554.6.192 Purge MS Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564.6.193 Ready for SM Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2574.6.194 Ready for SM Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2584.6.195 Ready for SM Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2594.6.196 Ready for SM Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2604.6.197 Register CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2614.6.198 Register CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2624.6.199 Register CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2634.6.200 Register CC Entry Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2644.6.201 Register Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2654.6.202 Register Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2664.6.203 Register Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2674.6.204 Register Password Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2684.6.205 Register Supplementary Service Request . . . . . . . . . . . . . . . . . . . . . 2694.6.206 Register Supplementary Service Indication . . . . . . . . . . . . . . . . . . . 2704.6.207 Register Supplementary Service Response . . . . . . . . . . . . . . . . . . . . 2714.6.208 Register Supplementary Service Confirmation . . . . . . . . . . . . . . . . 2724.6.209 Remote User Free Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2734.6.210 Remote User Free Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2744.6.211 Remote User Free Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2754.6.212 Remote User Free Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2764.6.213 Send Identification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2774.6.214 Send Identification Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2784.6.215 Send Identification Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2794.6.216 Send Identification Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2804.6.217 Set Ciphering Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2814.6.218 Set Ciphering Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2824.6.219 Set Ciphering Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2834.6.220 Set Ciphering Mode Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2844.6.221 Set Reporting State Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2854.6.222 Set Reporting State Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2864.6.223 Set Reporting State Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2874.6.224 Set Reporting State Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2884.6.225 Report Short Message Delivery Status Request . . . . . . . . . . . . . . 2894.6.226 Report Short Message Delivery Status Indication . . . . . . . . . . . . 2904.6.227 Report Short Message Delivery Status Response . . . . . . . . . . . . . 2914.6.228 Report Short Message Delivery Status Confirmation . . . . . . . . . 2924.6.229 Send Authentication Information Request . . . . . . . . . . . . . . . . . . . . 2934.6.230 Send Authentication Information Indication . . . . . . . . . . . . . . . . . 2944.6.231 Send Authentication Information Response . . . . . . . . . . . . . . . . . . 2954.6.232 Send Authentication Information Confirmation . . . . . . . . . . . . . . 2964.6.233 Send End Signal Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2974.6.234 Send End Signal Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2984.6.235 Send End Signal Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2994.6.236 Send End Signal Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3004.6.237 Send Group Call End Signal Request . . . . . . . . . . . . . . . . . . . . . . . . 3014.6.238 Send Group Call End Signal Indication . . . . . . . . . . . . . . . . . . . . . . 3024.6.239 Send Group Call End Signal Response . . . . . . . . . . . . . . . . . . . . . . . 3034.6.240 Send Group Call End Signal Confirmation . . . . . . . . . . . . . . . . . . . 3044.6.241 Send Routing Information for GPRS Request . . . . . . . . . . . . . . . . 3054.6.242 Send Routing Information for GPRS Indication . . . . . . . . . . . . . . 3064.6.243 Send Routing Information for GPRS Response . . . . . . . . . . . . . . . 307

x Mobile Application Part Interface (MAPI)

4.6.244 Send Routing Information for GPRS Confirmation . . . . . . . . . . . 3084.6.245 Send Handover Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3094.6.246 Send Handover Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3104.6.247 Send Handover Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3114.6.248 Send Handover Report Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . 3124.6.249 Send IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3134.6.250 Send IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3144.6.251 Send IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3154.6.252 Send IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3164.6.253 Send Routing Information for LCS Request . . . . . . . . . . . . . . . . . . 3174.6.254 Send Routing Information for LCS Indication . . . . . . . . . . . . . . . . 3184.6.255 Send Routing Information for LCS Response . . . . . . . . . . . . . . . . . 3194.6.256 Send Routing Information for LCS Confirmation . . . . . . . . . . . . . 3204.6.257 Send Mobile Originated SMS Information Request . . . . . . . . . . . 3214.6.258 Send Mobile Originated SMS Information Indication . . . . . . . . . 3224.6.259 Send Mobile Originated SMS Information Response . . . . . . . . . . 3234.6.260 Send Mobile Originated SMS Information Confirmation . . . . . . 3244.6.261 Send Mobile Terminated SMS Information Request . . . . . . . . . . 3254.6.262 Send Mobile Terminated SMS Information Indication . . . . . . . . 3264.6.263 Send Mobile Terminated SMS Information Response . . . . . . . . . 3274.6.264 Send Mobile Terminated SMS Information Confirmation . . . . . 3284.6.265 Send Routing Information Request . . . . . . . . . . . . . . . . . . . . . . . . . . 3294.6.266 Send Routing Information Indication . . . . . . . . . . . . . . . . . . . . . . . . 3304.6.267 Send Routing Information Response . . . . . . . . . . . . . . . . . . . . . . . . . 3314.6.268 Send Routing Information Confirmation . . . . . . . . . . . . . . . . . . . . . 3324.6.269 Send Routing Information for SM Request . . . . . . . . . . . . . . . . . . . 3334.6.270 Send Routing Information for SM Indication . . . . . . . . . . . . . . . . . 3344.6.271 Send Routing Information for SM Response . . . . . . . . . . . . . . . . . . 3354.6.272 Send Routing Information for SM Confirmation . . . . . . . . . . . . . . 3364.6.273 SS Invocation Notification Request . . . . . . . . . . . . . . . . . . . . . . . . . . 3374.6.274 SS Invocation Notification Indication . . . . . . . . . . . . . . . . . . . . . . . . 3384.6.275 SS Invocation Notification Response . . . . . . . . . . . . . . . . . . . . . . . . . 3394.6.276 SS Invocation Notification Confirmation . . . . . . . . . . . . . . . . . . . . . 3404.6.277 Status Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3414.6.278 Status Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3424.6.279 Status Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3434.6.280 Status Report Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3444.6.281 Subscriber Location Report Request . . . . . . . . . . . . . . . . . . . . . . . . . 3454.6.282 Subscriber Location Report Indication . . . . . . . . . . . . . . . . . . . . . . . 3464.6.283 Subscriber Location Report Response . . . . . . . . . . . . . . . . . . . . . . . . 3474.6.284 Subscriber Location Report Confirmation . . . . . . . . . . . . . . . . . . . . 3484.6.285 Note Subscriber Data Modified Request . . . . . . . . . . . . . . . . . . . . . 3494.6.286 Note Subscriber Data Modified Indication . . . . . . . . . . . . . . . . . . . 3504.6.287 Note Subscriber Data Modified Response . . . . . . . . . . . . . . . . . . . . 3514.6.288 Note Subscriber Data Modified Confirmation . . . . . . . . . . . . . . . . 3524.6.289 Trace Subscriber Activity Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 3534.6.290 Trace Subscriber Activity Indication . . . . . . . . . . . . . . . . . . . . . . . . . 3544.6.291 Trace Subscriber Activity Response . . . . . . . . . . . . . . . . . . . . . . . . . . 3554.6.292 Trace Subscriber Activity Confirmation . . . . . . . . . . . . . . . . . . . . . . 3564.6.293 Update GPRS Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3574.6.294 Update GPRS Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 3584.6.295 Update GPRS Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 3594.6.296 Update GPRS Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . 360

xi

4.6.297 Update Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3614.6.298 Update Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3624.6.299 Update Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3634.6.300 Update Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3644.6.301 Unstructured Supplementary Service Notify Request . . . . . . . . . 3654.6.302 Unstructured Supplementary Service Notify Indication . . . . . . . 3664.6.303 Unstructured Supplementary Service Notify Response . . . . . . . . 3674.6.304 Unstructured Supplementary Service Notify Confirmation . . . . 3684.6.305 Unstructured Supplementary Service Request . . . . . . . . . . . . . . . . 3694.6.306 Unstructured Supplementary Service Indication . . . . . . . . . . . . . . 3704.6.307 Unstructured Supplementary Service Response . . . . . . . . . . . . . . . 3714.6.308 Unstructured Supplementary Service Confirmation . . . . . . . . . . . 372

5 Diagnostics Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3735.1 Non-Fatal Error Handling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3735.2 Fatal Error Handling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Addendum for 3GPP Conformance . . . . . . . . . . . . . . . . . . . . . . . . 377

Appendix A Mapping MAPI Primitives to 3GPP TS

29.002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379A.1 Application Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Appendix B State/Event Tables . . . . . . . . . . . . . . . . . . . . . . . . . 389

Appendix C Primitive Precedence Tables . . . . . . . . . . . . . . . 391

Appendix D MAPI Header File Listing . . . . . . . . . . . . . . . . . 393

Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395GNU Affero General Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395How to Apply These Terms to Your New Programs . . . . . . . . . . . . . . . . . . . 404

GNU Free Documentation License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Mobile Application Part Interface (MAPI) Table of Contents

List of Figures

2014-10-25 1

List of Tables

2 Version 1.1 Rel. 7.20141001

Mobile Application Part Interface (MAPI) Preface

Preface

Notice

Software in this document and related software is released under the AGPL (see [GNU Affero GeneralPublic License], page 395). Please note, however, that there are different licensing terms for someof the manual package and some of the documentation. Consult permission notices contained in thedocumentation of those components for more information.

This document is released under the FDL (see [GNU Free Documentation License], page 405) withno invariant sections, no front-cover texts and no back-cover texts.

Abstract

This document is a Specification containing technical details concerning the implementation of theMobile Application Part Interface (MAPI) for OpenSS7. It contains recommendations on softwarearchitecture as well as platform and system applicability of the Mobile Application Part Interface(MAPI).

This document specifies a Mobile Application Part Interface (MAPI) Specification in support of theOpenSS7 Mobile Application Part (MAP) protocol stacks. It provides abstraction of the MobileApplication Part interface to these components as well as providing a basis for Mobile ApplicationPart control for other Mobile Application Part protocols.

Purpose

The purpose of this document is to provide technical documentation of the Mobile ApplicationPart Interface (MAPI). This document is intended to be included with the OpenSS7 STREAMS

software package released by OpenSS7 Corporation. It is intended to assist software developers,maintainers and users of the Mobile Application Part Interface (MAPI) with understanding thesoftware architecture and technical interfaces that are made available in the software package.

Intent

It is the intent of this document that it act as the primary source of information concerning theMobile Application Part Interface (MAPI). This document is intended to provide information forwriters of OpenSS7 Mobile Application Part Interface (MAPI) applications as well as writers ofOpenSS7 Mobile Application Part Interface (MAPI) Users.

Audience

The audience for this document is software developers, maintainers and users and integrators ofthe Mobile Application Part Interface (MAPI). The target audience is developers and users of theOpenSS7 SS7 stack.

Revision History

Take care that you are working with a current version of this documentation: you will not benotified of updates. To ensure that you are working with a current version, check the OpenSS7Project website for a current version.

A current version of this specification is normally distributed with the OpenSS7 package, openss7-1.1.7.20141001.1

1 http://www.openss7.org/repos/tarballs/openss7-1.1.7.20141001.tar.bz2

2014-10-25 3



http://www.openss7.org/repos/tarballs/openss7-1.1.7.20141001.tar.bz2

Preface

Version Control

Although the author has attempted to ensure that the information in this document is complete andcorrect, neither the Author nor OpenSS7 Corporation will take any responsibility in it. OpenSS7Corporation is making this documentation available as a reference point for the industry. WhileOpenSS7 Corporation believes that these interfaces are well defined in this release of the document,minor changes may be made prior to products conforming to the interfaces being made available.OpenSS7 Corporation reserves the right to revise this software and documentation for any reason,including but not limited to, conformity with standards promulgated by various agencies, utilizationof advances in the state of the technical arts, or the reflection of changes in the design of anytechniques, or procedures embodied, described, or referred to herein. OpenSS7 Corporation is underno obligation to provide any feature listed herein.

$Log: mapi.texi,v $

Revision 1.1.2.2 2011-02-07 02:21:40 brian

- updated manuals

Revision 1.1.2.1 2009-06-21 10:53:58 brian

- added files to new distro

ISO 9000 Compliance

Only the TEX, texinfo, or roff source for this maual is controlled. An opaque (printed, postscript orportable document format) version of this manual is a UNCONTROLLED VERSION.

Disclaimer

OpenSS7 Corporation disclaims all warranties with regard to this documentation including all im-plied warranties of merchantability, fitness for a particular purpose, non-infrincement, or title; thatthe contents of the manual are suitable for any purpose, or that the implementation of such con-tents will not infringe on any third party patents, copyrights, trademarks or other rights. In noevent shall OpenSS7 Corporation be liable for any direct, indirect, special or consequential dam-ages or any damages whatsoever resulting from loss of use, data or profits, whether in an action orcontract, negligence or other tortious action, arising out of or in connection with any use of thisdocumentation or the performance or implementation of the contents thereof.

U.S. Government Restricted Rights

If you are licensing this Software on behalf of the U.S. Government ("Government"), the followingprovisions apply to you. If the Software is supplied by the Department of Defense ("DoD"), it is clas-sified as "Commercial Computer Software" under paragraph 252.227-7014 of the DoD Supplementto the Federal Aquisition Regulations ("DFARS") (or any successor regulations) and the Govern-ment is acquiring only the license rights granded herein (the license rights customarily provided tonon-Government users). If the Software is supplied to any unit or agency of the Government otherthan DoD, it is classified as "Restricted Computer Software" and the Government’s rights in theSoftware are defined in paragraph 52.227-19 of the Federal Acquisition Regulations ("FAR") (or anysuccessor regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the NASA Supplermentto the FAR (or any successor regulations).

Acknowledgements

The OpenSS7 Project was funded in part by:

4 Version 1.1 Rel. 7.20141001


Mobile Application Part Interface (MAPI) Preface

• Monavacon Limited

• OpenSS7 Corporation

Thanks to the subscribers to and sponsors of The OpenSS7 Project. Without their support, opensoftware like this would not be possible.

As with most open source projects, this project would not have been possible without the valiantefforts and productive software of the Free Software Foundation, the Linux Kernel Community, andthe open source software movement at large.

2014-10-25 5

http://www.monavacon.com/



http://www.fsf.org/

http://www.kernel.org/

Mobile Application Part Interface (MAPI) Introduction

1 Introduction

This document specifies a STREAMS-based kernel-level instantiation of the 3GPP GSM/UMTSTS.29002 Mobile Application Part (MAP) service definition. The Mobile Application Part Interface(MAPI) enables the user of a mobile application service to access and use a wide variety of con-forming mobile application service providers without specific knowledge of the provider’s protocol.The service interface is designed to support any operation class of transaction protocol. This inter-face only specifies access to mobile application layer service providers, and does not address issuesconcerning mobile application layer management, protocol performance, and performance analysistools.

This specification assumes that the reader is familiar with the 3GPP GSM/UTMS reference pointsand protocol stacks, Mobile Application Part services, and STREAMS.

1.1 Related Documentation

— 3GPP TS 29.002 Mobile Application Part (MAP)

— 3GPP TS 29.202

— 1993 ITU-T Q.771 Recommendation

— System V Interface Definition, Issue 2 – Volume 3

— CCITT Recommendation X.200

— CCITT Recommendation X.201

— System V Interface Definition, Issue 2 - Volume 3

1.1.1 Role

This document specifies an interface that supports the service provided by the Mobile ApplicationsPart (MAP) specification for 3GPP GSM/UMTS as described in 3GPP TS 29.002. These spec-ifications are targeted for use by developers and testers of protocol modules that require MobileApplications Part services.

1.2 Definitions, Acronyms, Abbreviations

Application ContextObject IdentifierCalling Party

The Calling Party.

Called PartyThe Called Party.

Operations ClassOne of 5 ISO/OSI Transport Protocol Classes.

MAP Mobile Applications Part

TCAP Transaction Capabilities Application Part

SCCP Service Connection Control Part

MTP Message Transfer Part

TR Transaction Sub-Layer

2014-10-25 7

Chapter 1: Introduction

TC Component Sub-Layer

IMSI International Mobile Station Identifier

MSISDN Mobile Station ISDN Directory Number (E.164)

ITU International Telecommunications Union

ITU-T International Telecommunications Union – Telecom Sector

OSI Open Systems Interconnect

ISO International Organization for Standardization

MAP User A user of the Mobile Application Part (MAP) Interface.

MAP ProviderA provider of the Mobile Application Part (MAP) Interface.

MAPI The Mobile Application Part (MAP) Interface.

MS Mobile Station.

ComponentsTransaction components as defined in ITU-T Recommendation Q.771.

QoS Quality of Service

STREAMS A communication services development facility first available with UNIX System VRelease 3.

8 Version 1.1 Rel. 7.20141001

Mobile Application Part Interface (MAPI) The Mobile Application Layer

2 The Mobile Application Layer

The Mobile Application Layer provides the means to manage the operation of a mobile network. Itis responsible for the routing and management of data exchange between the MAP-User entities.

2.1 Model of the MAPI

The MAPI defines the services provided by the MAP layer to the MAP-User at the boundarybetween the MAP layer and the MAP layer user entity. The interface consists of a set of primitivesdefined as STREAMS messages that provide access to the MAP layer services, and are transferredbetween the MAP user entity and the MAP provider. These primitives are of two types: ones thatoriginate from the MAP user, and others that originate from the MAP provider. The primitivesthat originate from the MAP user make requests to the MAP provider, or respond to an event ofthe MAP provider. The primitives that originate from the MAP provider are either confirmationof a request or are indications to the MAP user that the event has occurred. Figure 1 shows themodel of the MAPI. (See Modelling Principles in 3GPP TS 29.002 V6.6.0.)� �

Figure 1 – Module of the MAP Interface

Indication/Confirmation

Primitives

Request/Response

Primitives

TC User

MAPProvider

Full Duplex Connection

MAPI

MAP

User

Application Context

The MAPI allows the MAP provider to be configured with any MAP user (such as an HLR, MSCor SGSN application) that also conforms to the MAPI. A MAP user can also be a user programthat conforms to the MAPI and accesses the MAP provider using ‘putmsg()’ and ‘getmsg()’ systemcalls.1

1 See Section “putmsg(2s)” in The UNIX Manual Pages, also see Section “getmsg(2s)” in The UNIX ManualPages.

2014-10-25 9

Chapter 2: The Mobile Application Layer

2.2 MAP Services

The features of the MAP are defined in terms of the services provided by the MAP provider, andthe individual primitives that may flow between the MAP users and the MAP provider.

The services provided by the MAP are based on a number of application contexts corresponding tothe 3GPP TS 29.002 Mobile Application Part application contexts. In addition, the MAP supportsservices for local management.

• Local Management

• Common Services

• Mobility Services

2.2.1 Local Management

The MAP specifications also define a set of local management functions that apply to all applicationcontexts. These services have local significance only.

Tables 1 and 2 summarizes the MAPI service primitives by their state and service.

2.2.2 Common Services

Table X. Common Services

Service Invoker PerformerMAP OPENMAP DELIMMAP CLOSEMAP UABORT User UserMAP PABORT Provider UserMAP NOTICEMAP STC1MAP STC2MAP STC3MAP STC4

2.2.3 Specific Services

Table 3. Specific Services

Service Invoker PerformerMAP ACTSS MSC VLR

VLR HLRMAP ACTTM HLR VLR or SGSNMAP ALERTSC HLR SMS-IWMSCMAP ANYMOD SCF HLR

PNA VLR or SGSNMAP ANYSUB SCF HLRMAP AUTH VLR MSCMAP AUTHFAIL VLR or SGSN HLRMAP CANCLOC HLR VLR or SGSNMAP CKIEMI VLR MSC

10 Version 1.1 Rel. 7.20141001


MSC or SGSN EIRMAP DEACTSS MSC VLR

VLR HLRMAP DEACTTM HLR VLR or SGSNMAP DELSUBD HLR VLR or SGSNMAP ERASECC MSC VLR

VLR HLRMAP ERASESS MSC VLR

VLR HLRMAP FAILURE GGSN HLRMAP FAS MSC-A MSC-BMAP FCKSSIND HLR VLRMAP FGRCSIG Anchor MSC Relay MSCMAP MTFSMS SMS-GMSC MSC or SGSNMAP MOFSMS MSC SMS-IWMSCMAP GETPASS HLR VLR

VLR MSCMAP INFORMSC HLR SMS-GMSCMAP INSSUBSD HLR VLR or SGSNMAP INTERGSS MSC VLR

VLR HLRMAP ISTALERT VMSC or GMSC HLRMAP ISTCMD HLR VMSC or GMSCMAP MMEVENT VLR or SGSN SCFMAP MSGPRSPRES HLR GGSNMAP SUBSDATAMOD HLR SCFMAP PREPGC Anchor MSC Relay MSCMAP PREPHO MSC-A MSC-BMAP PREPSH MSC-B MSC-AMAP PROCAS MSC VLRMAP PROCGC Relay MSC Anchor MSCMAP PROCUSS MSC VLR

VLR HLRMAP PROVRN HLR VLRMAP PROVSLOC GMLC VMSC or SGSNMAP PROVSUBI VLR SGSNMAP PURGEMS VLR or SGSN HLRMAP RDYSM MSC VLR

VLR or SGSN HLRMAP REGCC MSC VLR

VLR HLRMAP REGPW MSC VLR

VLR HLRMAP REGSS MSC VLRMAP REMUSRFREE HLR VLRMAP SMDELIVSTAT SMS-GMSC HLRMAP RESET HLR VLR or SGSNMAP RESTORE VLR HLRMAP SENDGCEND Relay MSC Anchor MSC

2014-10-25 11


MAP SENDEND MSC-B MSC-AMAP SENDAUTHI VLR or SGSN HLRMAP SENDIMSI VLR MSCMAP SENDID VLR old VLRMAP SENDSMSRI SMS-GMSC HLRMAP SENDGPRSRI GGSN HLRMAP SENDLCSRI GMLC HLRMAP SENDRI GMSC or SCF HLR or NPLRMAP SETREP HLR VLRMAP STATUS VLR HLRMAP SUBLOCREP VMSC or SGSN GMLCMAP USSDNTFY SCF HLR

HLR VLRVLR MSC

MAP USSDREQ SCF HLRHLR VLRVLR MSC

MAP UDGPRSLOC SGSN HLRMAP UDLOC VLR HLR

2.3 Service Categories

2.3.1 Mobility Management

2.3.1.1 Location Management Services

Service Invoker PerformerMAP UDLOC VLR HLRMAP CANCLOC HLR VLR or SGSNMAP SENDID VLR old VLRMAP PURGEMS VLR or SGSN HLRMAP UDGPRSLOC SGSN HLRMAP MMEVENT VLR or SGSN SCF

2.3.1.2 Paging and Search

Service Invoker PerformerMAP PAGE VLR MSCMAP SEARCH VLR MSC

2.3.1.3 Access Management Services

Service Invoker PerformerMAP PROCAS MSC VLR

2.3.1.4 Handover Services

Service Invoker PerformerMAP PREPHO MSC-A MSC-BMAP SENDEND MSC-B MSC-AMAP PROCAS MSC-B MSC-A

12 Version 1.1 Rel. 7.20141001


MAP FAS MSC-A MSC-BMAP PREPSH MSC-B MSC-AMAP ALLOCHN MSC VLRMAP SENDHOREP VLR MSC-B

2.3.1.5 Authentication Management Services

Service Invoker PerformerMAP AUTH VLR MSCMAP SENDAUTHI VLR or SGSN HLRMAP AUTHFAIL VLR or SGSN HLR

2.3.1.6 Security Management Services

Service Invoker PerformerMAP SETCM VLR MSC

2.3.1.7 IEMI Managment Services

Service Invoker PerformerMAP CKIEMI VLR MSC

MSC or SGSN EIRMAP GETIEMI VLR MSC

2.3.1.8 Subscriber Management Services

Service Invoker PerformerMAP INSSUBSD HLR VLR or SGSNMAP DELSUBD HLR VLR or SGSN

2.3.1.9 Identity Management Services

Service Invoker PerformerMAP PROVIMSI VLR MSCMAP FNEWIMSI VLR MSC

2.3.1.10 Fault Recovery Services

Service Invoker PerformerMAP RESET HLR VLR or SGSNMAP FCKSSIND HLR VLRMAP RESTORE VLR HLR

2.3.1.11 Subscriber Information Services

Service Invoker PerformerMAP ANYQRY SCF HLR or GMLC or NPLRMAP PROVSUBI VLR SGSNMAP ANYSUB SCF HLRMAP ANYMOD SCF HLR

PNA VLR or SGSNMAP SUBSDATAMOD HLR SCF

2.3.2 Operation and Maintenance

2014-10-25 13


2.3.2.1 Subscriber Tracing Services

Service Invoker PerformerMAP ACTTM HLR VLR or SGSNMAP DEACTTM HLR VLR or SGSNMAP TRACESA VLR MSC

2.3.2.2 Miscellaneous Operation and Maintenance Services

Service Invoker PerformerMAP SENDIMSI VLR MSC

2.3.3 Call Handling

2.3.3.1 Call Handling Services

Service Invoker PerformerMAP SENDRI GMSC or SCF HLR or NPLRMAP PROVRN HLR VLRMAP RESUME VMSC GMSCMAP PREPGC Anchor MSC Relay MSCMAP PROCGC Relay MSC Anchor MSCMAP FGRCSIG Anchor MSC Relay MSCMAP SENDGCEND Relay MSC Anchor MSCMAP SETREP HLR VLRMAP STATUS VLR HLRMAP REMUSRFREE HLR VLRMAP ISTALERT VMSC or GMSC HLRMAP-ISTCMD HLR VMSC or GMSC

2.3.4 Supplementary Service

2.3.4.1 Supplementary Service Services

Service Invoker PerformerMAP REGSS MSC VLRMAP ERASESS MSC VLR

VLR HLRMAP ACTSS MSC VLR

VLR HLRMAP DEACTSS MSC VLR

VLR HLRMAP INTERGSS MSC VLR

VLR HLRMAP REGPW MSC VLR

VLR HLRMAP GETPASS HLR VLR

VLR MSCMAP PROCUSS MSC VLR

VLR HLRMAP USSDREQ SCF HLR

HLR VLR

14 Version 1.1 Rel. 7.20141001


VLR MSCMAP USSDNTFY SCF HLR

HLR VLRVLR MSC

MAP SSINV MSC or HLR SCFMAP REGCC MSC VLR

VLR HLRMAP ERASECC MSC VLR

VLR HLR

2.3.5 SMS Management Services

2.3.5.1 Short Message Service Management Services

Service Invoker PerformerMAP SENDSMSRI SMS-GMSC HLRMAP MOFSMS MSC SMS-IWMSCMAP SMDELIVSTAT SMS-GMSC HLRMAP RDYSM MSC VLRMAP RDYSM VLR or SGSN HLRMAP ALERTSC HLR SMS-IWMSCMAP INFORMSC HLR SMS-GMSCMAP SENDMTSMSI MSC VLRMAP SENDMOSMSI MSC VLRMAP MTFSMS SMS-GMSC MSC or SGSN

2.3.6 Network-Requested PDP Context Activation

2.3.6.1 Network-Requested PDP Context Activation Services

Service Invoker PerformerMAP SENDGPRSRI GGSN HLRMAP FAILURE GGSN HLRMAP MSGPRSPRES HLR GGSN

2.3.7 Location Service Management

2.3.7.1 Location Service Management Services

Service Invoker PerformerMAP SENDLCSRI GMLC HLRMAP PROVSLOC GMLC VMSC or SGSNMAP SUBLOCREP VMSC or SGSN GMLC

2.4 MAP User Entities

2.4.1 Mobile Switching Centre (MSC) Service Sets

Table X. MSC performed services.

2014-10-25 15


Service Invoker PerformerMAP PAGE VLR MSCMAP SEARCH VLR MSCMAP SENDHOREP VLR MSCMAP AUTH VLR MSCMAP SETCM VLR MSCMAP CKIEMI VLR MSCMAP GETIEMI VLR MSCMAP PROVIMSI VLR MSCMAP FNEWIMSI VLR MSCMAP TRACESA VLR MSCMAP SENDIMSI VLR MSCMAP ISTCMD HLR MSCMAP GETPASS VLR MSCMAP USSDREQ VLR MSCMAP USSDNTFY VLR MSCMAP MTFSMS SMS-GMSC MSCMAP PROVSLOC GMLC MSC

Table X. MSC invoked services.

Service Invoker PerformerMAP PROCAS MSC VLRMAP CKIEMI MSC EIRMAP ALLOCHN MSC VLRMAP RESUME MSC GMSCMAP ISTALERT MSC HLRMAP REGSS MSC VLRMAP ERASESS MSC VLRMAP ACTSS MSC VLRMAP DEACTSS MSC VLRMAP INTERGSS MSC VLRMAP REGPW MSC VLRMAP PROCUSS MSC VLRMAP SSINV MSC SCFMAP REGCC MSC VLRMAP ERASECC MSC VLRMAP MOFSMS MSC SMS-IWMSCMAP RDYSM MSC VLRMAP SENDMTSMSI MSC VLRMAP SENDMOSMSI MSC VLRMAP SUBLOCREP MSC GMLC

Table X. MSC peer services.

Service Invoker PerformerMAP PREPHO MSC-A MSC-BMAP SENDEND MSC-B MSC-AMAP PROCAS MSC-B MSC-A

16 Version 1.1 Rel. 7.20141001


MAP FAS MSC-A MSC-BMAP PREPSH MSC-B MSC-AMAP PREPGC Anchor MSC Relay MSCMAP PROCGC Relay MSC Anchor MSCMAP FGRCSIG Anchor MSC Relay MSCMAP SENDGCEND Relay MSC Anchor MSC

2.4.2 Home Location Register (HLR) Service Sets

Table 1. HLR performed services.

Service Invoker PerformerMAP UDLOC VLR HLRMAP PURGEMS VLR or SGSN HLRMAP UDGPRSLOC SGSN HLRMAP SENDAUTHI VLR or SGSN HLRMAP AUTHFAIL VLR or SGSN HLRMAP RESTORE VLR HLRMAP ANYQRY SCF HLRMAP ANYSUB SCF HLRMAP ANYMOD SCF HLRMAP SENDRI GMSC or SCF HLRMAP STATUS VLR HLRMAP ISTALERT VMSC or GMSC HLRMAP ERASESS VLR HLRMAP ACTSS VLR HLRMAP DEACTSS VLR HLRMAP INTERGSS VLR HLRMAP REGPW VLR HLRMAP PROCUSS VLR HLRMAP REGCC VLR HLRMAP ERASECC VLR HLRMAP SENDSMSRI SMS-GMSC HLRMAP SMDELIVSTAT SMS-GMSC HLRMAP RDYSM VLR or SGSN HLRMAP SENDGPRSRI GGSN HLRMAP FAILURE GGSN HLRMAP USSDREQ SCF HLRMAP SENDLCSRI GMLC HLRMAP USSDNTFY SCF HLR

Table 2. HLR invoked services.

Service Invoker PerformerMAP CANCLOC HLR VLR or SGSNMAP INSSUBSD HLR VLR or SGSNMAP DELSUBD HLR VLR or SGSNMAP RESET HLR VLR or SGSNMAP FCKSSIND HLR VLR

2014-10-25 17


MAP SUBSDATAMOD HLR SCFMAP ACTTM HLR VLR or SGSNMAP DEACTTM HLR VLR or SGSNMAP PROVRN HLR VLRMAP SETREP HLR VLRMAP REMUSRFREE HLR VLRMAP ISTCMD HLR VMSC or GMSCMAP GETPASS HLR VLRMAP USSDREQ HLR VLRMAP USSDNTFY HLR VLRMAP SSINV HLR SCFMAP ALERTSC HLR SMS-IWMSCMAP INFORMSC HLR SMS-GMSCMAP MSGPRSPRES HLR GGSN

2.4.3 Visitor Location Register (VLR) Service Sets

Table 3. VLR performed services.

Service Invoker PerformerMAP CANCLOC HLR VLRMAP PROCAS MSC VLRMAP ALLOCHN MSC VLRMAP INSSUBSD HLR VLRMAP DELSUBD HLR VLRMAP SENDID VLR old VLRMAP RESET HLR VLRMAP FCKSSIND HLR VLRMAP ANYMOD PNA VLRMAP ACTTM HLR VLRMAP DEACTTM HLR VLRMAP PROVRN HLR VLRMAP SETREP HLR VLRMAP REMUSRFREE HLR VLRMAP REGSS MSC VLRMAP ERASESS MSC VLRMAP ACTSS MSC VLRMAP DEACTSS MSC VLRMAP INTERGSS MSC VLRMAP REGPW MSC VLRMAP GETPASS HLR VLRMAP PROCUSS MSC VLRMAP USSDREQ HLR VLRMAP USSDNTFY HLR VLRMAP REGCC MSC VLRMAP ERASECC MSC VLRMAP RDYSM MSC VLRMAP SENDMTSMSI MSC VLRMAP SENDMOSMSI MSC VLR

18 Version 1.1 Rel. 7.20141001


Table 4. VLR invoked services.

Service Invoker PerformerMAP UDLOC VLR HLRMAP SENDID VLR old VLRMAP PURGEMS VLR HLRMAP MMEVENT VLR SCFMAP PAGE VLR MSCMAP SEARCH VLR MSCMAP SENDHOREP VLR MSC-BMAP AUTH VLR MSCMAP SENDAUTHI VLR HLRMAP AUTHFAIL VLR HLRMAP SETCM VLR MSCMAP CKIEMI VLR MSCMAP GETIEMI VLR MSCMAP PROVIMSI VLR MSCMAP FNEWIMSI VLR MSCMAP RESTORE VLR HLRMAP PROVSUBI VLR SGSNMAP TRACESA VLR MSCMAP SENDIMSI VLR MSCMAP STATUS VLR HLRMAP ERASESS VLR HLRMAP ACTSS VLR HLRMAP DEACTSS VLR HLRMAP INTERGSS VLR HLRMAP REGPW VLR HLRMAP GETPASS VLR MSCMAP PROCUSS VLR HLRMAP USSDREQ VLR MSCMAP USSDNTFY VLR MSCMAP REGCC VLR HLRMAP ERASECC VLR HLRMAP RDYSM VLR HLR

2.4.4 Equipment Identity Register (EIR) Service Sets

Table X. EIR performed services.

Service Invoker PerformerMAP CKIEMI MSC or SGSN EIR

2.4.5 Serving GPRS Support Node (SGSN) Service Sets

Table X. SGSN performed services.

Service Invoker PerformerMAP CANCLOC HLR SGSNMAP INSSUBSD HLR SGSN

2014-10-25 19


MAP DELSUBD HLR SGSNMAP RESET HLR SGSNMAP PROVSUBI VLR SGSNMAP ANYMOD PNA SGSNMAP ACTTM HLR SGSNMAP DEACTTM HLR SGSNMAP MTFSMS SMS-GMSC SGSNMAP PROVSLOC GMLC SGSN

Table X. SGSN invoked services.

Service Invoker PerformerMAP PURGEMS SGSN HLRMAP UDGPRSLOC SGSN HLRMAP MMEVENT SGSN SCFMAP SENDAUTHI SGSN HLRMAP AUTHFAIL SGSN HLRMAP CKIEMI SGSN EIRMAP RDYSM SGSN HLRMAP SUBLOCREP SGSN GMLC

2.4.6 Gateway GPRS Support Node (GGSN) Service Sets

Table X. GGSN performed services.

Service Invoker PerformerMAP MSGPRSPRES HLR GGSN

Table X. GGSN invoked services.

Service Invoker PerformerMAP SENDGPRSRI GGSN HLRMAP FAILURE GGSN HLR

2.4.7 Interworking MSC (IWMSC) for Short Message Service Service Sets

Table X. SMS-IWMSC performed services.

Service Invoker PerformerMAP MOFSMS MSC SMS-IWMSCMAP ALERTSC HLR SMS-IWMSC

2.4.8 Gateway MSC (GMSC) for Short Message Service Service Sets

Table X. SMS-GMSC performed services.

Service Invoker PerformerMAP INFORMSC HLR SMS-GMSC

20 Version 1.1 Rel. 7.20141001


Table X. SMS-GMSC invoked services.

Service Invoker PerformerMAP SENDSMSRI SMS-GMSC HLRMAP SMDELIVSTAT SMS-GMSC HLRMAP MTFSMS SMS-GMSC MSC or SGSN

2.4.9 Gateway Mobile Location Center (GMLC) Service Sets

Table X. GMLC performed services.

Service Invoker PerformerMAP ANYQRY SCF GMLCMAP SUBLOCREP VMSC or SGSN GMLC

Table X. GMLC invoked services.

Service Invoker PerformerMAP SENDLCSRI GMLC HLRMAP PROVSLOC GMLC VMSC or SGSN

2014-10-25 21

Mobile Application Part Interface (MAPI) MAPI Services Definition

3 MAPI Services Definition

This chapter describes the services of the MAP primitives. Time-sequence diagrams that illustratethe sequence of primitives is included. (Conventions for the time-sequence diagrams are defined inITU-T X.210). The format of the primitives will be defined later in the document.

3.1 Local Management Services Definition

The services defined in this section are outside the scope of the international standards. Theseservices apply to all applications contexts and specific service primitives. They are invoked for theinitialization or de-initialization of a stream connected to the MAP provider. They are also usedto manage options supported by the MAP provider and to report information on the supportedparameter values.

3.1.1 MAP Information Reporting Service

This service provides information on the options supported by the MAP provider.

• MAP_INFO_REQ: This primitive requests that the MAP provider return the values of all thesupported protocol parameters. This request may be invoked during any phase.

• MAP_INFO_ACK: This primitive is in response to the MAP_INFO_REQ primitive and returns thevalues of the supported protocol parameters to the MAP user.

The sequence of primitives for mobile application part information management is shown in Figure2.� �

Figure 2. Sequence of Primitives;MAP Information Reporting Serivce

3.1.2 MAP User Bind Service

The service allows a network address and application contexts to be associated with a stream. Itallows the MAP user to negotiate the number of dialogues that can remain outstanding for thatMAP user (a dialogue is considered unacknowledged while it is awaiting a corresponding responseor abort from the MAP user). This service also defines a mechanism that allows a stream (bound toa network address of the MAP user) to be reserved to handle remote initiated dialogues only. Thisstream is referred to as the listener stream.

• MAP_BIND_REQ: This primitive requests that the MAP user be bound to a particular networkaddress and application context, and negotiate the number of allowable outstanding open in-dications for that address.

• MAP_BIND_ACK: This primitive is in response to the MAP_BIND_REQ primitive and indicates tothe user that the specified MAP user has been bound to a network address and applicationcontext.

The sequence of primitives for the MAP user bind service is shown in Figure 3.� �Figure 2. Sequence of Primitives;

MAP User Bind Service 2014-10-25 23

Chapter 3: MAPI Services Definition

3.1.3 MAP User Unbind Service

This service allows the MAP user to be unbound from a network address and application context.

• MAP_UNBIND_REQ: This primitive requests that the MAP user be unbound from the networkaddress and application context(s) to which it was previously bound.

The sequence of primitives for MAP user unbind service is shown in Figure 4.� �Figure 4. Sequence of Primitives;

MAP User Unbind & Receipt Acknowledgement Services 3.1.4 Receipt Acknowledgement Service

• MAP_OK_ACK: This primitive indicates to the MAP user that the previous MAP user originatedprimitive was received successfully by the MAP provider.

An example showing the sequence of primitives for successful receipt acknowledgement is depictedin Figure 4.

3.1.5 Options Management Service

This service allows the MAP user to manage the QOS parameter values and other options associatedwith the MAP provider.

• MAP_OPTMGMT_REQ: This primitive allows the MAP user to select default values for QoS param-eters within the range supported by the MAP provider, and to indicate the default selection ofadditional options supported by the MAP provider.

Figure 5 shows the sequence of primitives for MAP options management service.� �Figure 5. Sequence of Primitives;Options Management Service.

3.1.6 Error Acknowledgement Service

• MAP_ERROR_ACK: This primitive indicates to the MAP user that a non-fatal error has occurredin the last MAP user originated request or response primitive (listed in Figure 6), on the stream.

Figure 6 shows the sequence of primitives for the error acknowledgement service.� �Figure 6. Sequence of Primitives;Error Acknowledgement Service.

3.2 Dialogue Handling Definition

This section describes the required MAP service primitives that define the Dialogue Handling inter-face.

The queue model for Dialogue Handling is discussed in more detail in CCITT X.219.

The queue module represents the operation of a MAP dialogue in the abstract by a pair of queueslinking the two MAP user entities. There is one queue for each direction of information flow. Eachqueue represents a flow control function in one direction of transfer. The ability of a user to addobjects to a queue will be determined by the behaviour of the user removing objects from that queue,

24 Version 1.1 Rel. 7.20141001


and the state of the queue. The pair of queues is considered to be available for each potential MAPdialogue. Objects that are entered or removed from the queue are either as a result of interactionsat the two MAP users, or as a result of MAP provider initiatives.

• A queue is empty until a dialogue object has been entered and can be returned to this state,with loss of its contents, by the MAP provider.

• Objects can be entered into a queue as a result of the actions of the source MAP user, subjectto control by the MAP provider.

• Objects may also be entered into a queue by the MAP provider.

• Objects are removed from the queue under the control of the MAP user in n the same order asthey were entered except:

— if the object is of a type defined to be able to advance ahead of the preceding object(however, no object is defined to be able to advance ahead of another object of the sametype), or

— if the following object is defined to be destructive with respect to the preceding object onthe queue. If necessary, the last object on the queue will be deleted to allow a destructiveobject to be entered – the will therefore always be added to the queue. For example,“abort” objects are defined to be destructive with respect to all other objects.

Table Y shows the ordering relationships among the queue model objects.

Table Y. Ordering Relationship Between Queue Model Objects.

Object XObject Y Open Components Delimiter Close AbortOpen N/A – – DESComponents N/A – – DESDeilmiter N/A – – DESClose N/A – – DESAbort N/A N/A N/A –

AA Indicates that Object X is defined to be able to advance ahead of preceding Object Y.

DES Indicates that Object X is defined to be destructive with respect to the precedingObject Y.

– Indicates that Object X is neither destructive with respect to Object Y, nor able toadvance ahead of Object Y.

N/A Indicates that Object X will not occur in a position succeeding Object Y in a validstate of a queue.

3.2.1 Dialogue Establishment Phase

A pair of queues is associated with a MAP dialogue between two MAP user entities when the MAPprovider receives a MAP_OPEN_REQ primitive at one of the MAP user interfaces resulting in the “begin”object being entered into the queue. The queues will remain associated with the MAP dialogue untila MAP_CLOSE_REQ or indication primitive (resulting in an “end” object) is either entered or removedfrom a queue. Similarly, in the queue from the called MAP user, objects can be entered into thequeue only after the “continue” object associated with the MAP_OPEN_RES primitive has been enteredinto the queue. Alternatively, the called MAP user can enter a an “end” or “abort” object into thequeue instead of the “continue” object to terminate the dialogue.

The MAP dialogue establishment procedure will fail if the MAP provider is unable to establish aTCAP dialogue, or if the destination MAP user is unable to accept the MAP_OPEN_IND.

2014-10-25 25


3.2.1.1 User Primitives for Successful MAP Dialogue Establishment

• MAP_OPEN_REQ: This primitive requests that the MAP provider establish a dialogue to thespecified destination under an application context.

• MAP_OPEN_RES: This primitives requests that the MAP provider accept a previous dialogueindication.

3.2.1.2 Provider Primitives for Successful MAP Dialogue Establishment

• MAP_OPEN_IND: This primitive indicates to the MAP user that a dialogue request has beenmade within an application context by a user at the specified source address.

• MAP_OPEN_CON: This primitive indicates to the MAP user that a dialogue request has beenconfirmed on the specified responding address.

The sequence of primitives for a successful MAP dialogue establishment is defined by the time se-quence diagram as shown in Figure 7. The sequence of primitives for the MAP dialogue responsetoken value determination is shown in Figure 8 (procedures for MAP response token value determi-nation are discussed later).� �

Figure 7. Sequence of Primitives;Successful MAP Dialogue Establishment � �

Figure 8. Sequence of Primitives;MAP Dialogue Response Token Value Determination

3.2.2 Dialogue Component Transfer Phase

Flow control within the MAP dialogue is performed by management of the queue capacity, and byallowing objects of certain types to be inserted to the queues as shown in Table 4.

Table 4. Flow Control Relationship Between Queued Model Objects

Object XObject Y Class 1 Class 2 Class 3 Class 4Class 1 Yes Yes Yes YesClass 2 Yes Yes Yes YesClass 3 Yes Yes Yes YesClass 4 Yes Yes Yes Yes

Yes The addition of Object X may prevent further addition of Object Y.

No The addition of Object X may not prevent the addition of Object Y.

3.2.2.1 User Primitives for Component Transfer

• Service Specific Requests: These primitives request that the MAP provider invoke a serviceand transfer the specified (and any subsequent) components.

• Service Specific Responses: These primitives request that the MAP provider return result fora service invocation and transfer the specified (and any subsequent) components.

• MAP_DELIM_IND: This primitive requests that the MAP provider deliver any accumulated com-ponents from previous service specific request or response primitives.

26 Version 1.1 Rel. 7.20141001


3.2.2.2 Provider Primitives for Component Transfer

• Service Specific Indications: These primitives indicate to the MAP user an invocation and theindicated (and any subsequent) components.

• Service Specific Confirmations: These primitives indicate to the MAP user a return result andthe indicated (and any subsequent) components.

• MAP_DELIM_IND: This primitive indicates that the MAP provider has delivered any accumulatedcomponents belonging to the previous service specific indication or confirmation primitive.

Figure 9 shows the sequence of primitives for successful component transfer. The sequence of prim-itives may remain incomplete if a MAP_ABORT or MAP_CLOSE primitive occurs.� �

Figure 9. Sequence of Primitives;Component Transfer.

The sequence of primitives in a successful Class 1 operation is defined in the time sequence diagramas shown in Figure 10.� �

Figure 10. Sequence of Primitives;Successful Confirmation of Receipt.

The sequence of primitives as shown above may remain incomplete if a MAP_UABORT, MAP_PABORT orMAP_CLOSE primitive occurs (see Table 3). A MAP user must not issue a Service Specific Responseprimitive if no Service Specific Indication primitive for a confirmed service has been received, or if allsuch Service Specific Indication primitives have been previously confirmed. Following a MAP_UABORT

or MAP_PABORT, a MAP user may not issue a Service Specific Response to confirm outstandingService Specific Indication primitives received before the abort procedure was signalled.

Note — The witholding of confirmation of a service by a MAP user can have an effect on theattainable throughput.

The sequence of primitives for component transfer is shown in the time sequence diagram in Figure11. This sequence of primitives may remain incomplete if a MAP_ABORT or MAP_CLOSE primitive isissued.� �

Figure 11. Sequence of Primitives;Expedited Data Transfer.

3.2.3 Dialogue Termination Phase

The MAP dialogue release procedure is initialized by the insertion of an “abort” or “end” objectinto the queue. As shown in Table 3, the “abort” is destructive with respect to other objects in thequeue, and eventually results in the emptying of queues and termination of the MAP dialogue.

The sequence of primitivies depends on the origin of the release action. The sequence of primitivesmay be:

1. invoked by one MAP user, with a request from that MAP user leading to an indication to theother;

2. invoked by both MAP users, with a request from each of the MAP users;

3. invoked by the MAP provider, with an indication to each of the MAP users;

4. invoked independently by one MAP user and the MAP provider, with a request from theoriginating MAP user and an indication to the other.

2014-10-25 27


3.2.3.1 User Primitives for Dialogue Abort

• MAP_ABORT_REQ: This primitive requests that the MAP provider deny an outstanding requestfor an association (MAP_OPEN_IND) or abort an existing association.

3.2.3.2 Provider Primitives for Dialogue Abort

• MAP_UABORT_IND: This primitive indicates to the MAP user that either a request for associationhas been denied or an existing association has been terminated.

• MAP_PABORT_IND: This primitive indicates to the MAP user that either a request for associationhas been denied or an existing association has been terminated.

The sequence of primitives are shown in the time sequence diagrams in n Figures 16, 17, 18 and 19.� �Figure 16. Sequence of Primitives;

MAP User Invoked Abort. � �Figure 17. Sequence of Primitives;

Simultaneous MAP User Invoked Abort. � �Figure 18. Sequence of Primitives;MAP Provider Invoked Abort. � �

Figure 19. Sequence of Primitives;Simultaneous MAP User and MAP Provider Invoked Abort.

A MAP user may reject a MAP association establishment by issuing a MAP_ABORT_REQ. The orig-inator parameter in the MAP_UABORT_IND primitive will indicate MAP user invoked release. Thesequence of events is shown in Figure 20.� �

Figure 20. Sequence of Primitives;MAP User Rejection of a MAP Association Establishment Attempt.

If the MAP provider is unable to establish a MAP association, it indicates this to the requester bya MAP_PABORT_IND. The originator in this primitive indicates a MAP provider invoked release. Thisis shown in Figure 21.� �

Figure 21. Sequence of Primitives;MAP Provider Rejection of a MAP Association Establishement Attempt.

28 Version 1.1 Rel. 7.20141001

Mobile Application Part Interface (MAPI) MAPI Primitives

4 MAPI Primitives

This section describes the format and parameters of the MAPI primitives (Appendix A shows themapping of the MAPI primitives to the primitives defined in 3GPP TS 29.002 and ANSI41-D). Also,it discusses the states in which the primitive is valid, the resulting state and the acknowledgementthat the primitive expects. (The state/event tables for these primitives are shown in Appendix B.The precedence tables for the MAPI primitives are shown in Appendix C.) Rules for 3GPP andANSI conformance are described in Addendum to this document.

Tabel 4. Local Management Service Primitives.

SERVICE PRIMITIVE PARAMETERSInformation MAP_INFO_REQ

Reporting MAP_INFO_ACK

Bind MAP_BIND_REQ

MAP_BIND_ACK

Unbind MAP_UNBIND_REQ

Error MAP_ERROR_ACK

Success MAP_OK_ACK

Tables 5, 6 and 7 provide a summary of the MAP primitives and their parameters.

Table 5. Association Establishment MAP Service Primitives.

SERVICE PRIMITIVE PARAMETERSAssociation MAP_OPEN_REQ (Application context name, Destination

address, Destination reference, Originatingaddress, Originating reference, Specificinformation)

Establishment MAP_OPEN_IND (Application context name, Destinationaddress, Destination reference, Originatingaddress, Originating reference, Specificinformation)

MAP_OPEN_RES (Application context name, Respondingaddress, Result, Refuse-reason, Specificinformation)

MAP_OPEN_CON (Application context name, Responding ad-dress, Result, Refuse-reason, Specific informa-tion, Provider-error)

Table 6. Component Transfer Service Primitives.

SERVICE PRIMITIVE PARAMETERSService MAP_XXX_REQ (Specific information)Specific MAP_XXX_IND (Specific information)Primitives MAP_XXX_RES (Specific information)

MAP_XXX_CON (Specific information)Delimitation MAP_DELIM_REQ (none)

MAP_DELIM_IND (none)

Table 7. Association Termination MAP Service Primitives.

SERVICE PRIMITIVE PARAMETERSAssociation MAP_CLOSE_REQ (Release method, Specific information)

2014-10-25 29

Chapter 4: MAPI Primitives

Termination MAP_CLOSE_IND (Specific information)Assocation MAP_ABORT_REQ (User reason, Diagnostic information, Specific

information)

Abort MAP_UABORT_IND (User reason, Diagnostic information, Specificinformation)

Abort MAP_PABORT_IND (Provider reason, Source)Notice MAP_NOTICE_IND ()

Table 8. Secure Transport Primitives.

SERVICE PRIMITIVE PARAMETERSClass 1 MAP_STC1_REQ

MAP_STC1_IND

Class 2 MAP_STC2_REQ

MAP_STC2_IND


MAP_STC3_IND


MAP_STC4_IND

30 Version 1.1 Rel. 7.20141001


4.1 Management Primitives

These primitives appy to all protocol classes.

4.1.1 Information Request

MAP INFO REQ

This primitive requests the MAP provider to return the values of all supported protocol parameters(see Section 4.1.2 [Information Acknowledgement], page 32), and also the current state of the MAPprovider.1

Format

The format of the message is one ‘M_PROTO’ message block and its structure is as follows:typedef struct {

ulong PRIM_type; /* always MAP_INFO_REQ */

} MAP_info_req_t;

Parameters

PRIM type:Indicates the primitive type.

Valid States

This primitive is valid in any state where a local acknowledgement is not pending.

New State

The new state remains unchanged from the old state.

Acknowledgements

This primitive requires the MAP provider to generate one of the following acknowledgements uponreceipt of the pirmitive:

— Successful: Acknowledgement of the primitive with the MAP_INFO_ACK primitive described inSection 4.1.2 [Information Acknowledgement], page 32.

— Non-fatal Errors: There are no errors associated with the issuance of this primitive.

1 The MAP_INFO_REQ and MAP_INFO_ACK primitives have no effect on the state of the MAP provider and donot appear in the state tables in Appendix B [State/Event Tables], page 389.

2014-10-25 31


4.1.2 Information Acknowledgement

MAP INFO ACK

This primitive indicates to the MAP users any relevant protocol-dependent parameters.1 It shouldbe initiated in response to the MAP_INFO_REQ primitive described above in Section 4.1.1 [InformationRequest], page 31.

Format

The format of the message is one ‘M_PCPROTO’ message block. The format of the ‘M_PCPROTO’ messageblock is as follows:

typedef struct {

ulong PRIM_type; /* always MAP_INFO_ACK */

ulong TSDU_size; /* maximum TSDU size */

ulong ETSDU_size; /* maximum ETSDU size */

ulong CDATA_size; /* connect data size */

ulong DDATA_size; /* disconnect data size */

ulong ADDR_size; /* address size */

ulong ADDR_length; /* address length */

ulong ADDR_offset; /* address offset */

ulong QOS_length; /* default QOS values length */

ulong QOS_offset; /* default QOS values offset */

ulong QOS_range_length; /* QOS range length */

ulong QOS_range_offset; /* QOS range offset */

ulong OPTIONS_flags; /* bit masking for options */

ulong TIDU_size; /* transaction interface data size */

long SERV_type; /* service type */

ulong CURRENT_state; /* current state */

ulong PROVIDER_type; /* type of provider */

ulong NODU_size; /* optimal TSDU size */

ulong PROTOID_length; /* length of bound protocol ids */

ulong PROTOID_offset; /* offset of bound protocol ids */

ulong MAPI_version; /* supported MAPI version number */

} MAP_info_ack_t;

Parameters

PRIM type Indicates the primitive type.

TSDU size Specifies the maximum size (in octets) of Transaction Service User Data supported bythe MAP provider.

ETSDU sizeSpecifies the maximum size (in octets) of Expedited Transaction Service User Datasupported by the MAP provider.

CDATA sizeSpecifies the maximum number of octets of data that may be associated with a trans-action initiation primitive for operations class 1, 2 and 3 operation.

DDATA sizeSpecifies the maximum number of octets of data that may be associated with a trans-action termination primitive for operations class 1, 2 and 3 operation.

1

32 Version 1.1 Rel. 7.20141001


ADDR sizeSpecifies the maximum size (in decimal digits) of a network address.

ADDR length, ADDR offsetSpecifies the length in bytes and offset from the beginning of the M_PCPROTO messageblock of the network address bound on the stream on which the MAP_INFO_REQ wasissued (a network address is bound to a stream via a MAP_BIND_REQ).

QOS length, QOS offsetQOS range length, QOS range offsetOPTIONS flagsTIDU size2

This is the size of the MAP protocol interface data unit, and should not exceed thetunable system limit, if non-zero, for the size of a STREAMS message.

SERV type This field specified the service type supported by the MAP provider, and is one of thefollowing:

CURRENT stateTHis is the current state of the MAP provider.

PROVIDER typeThis field specifies additional properties specific to the MAP provider and may alterthe way the MAP user communicates. MAP providers supporting the features of XTIin XPG4 and beyond must send up a version number as specified below. The followingflags may be set by the provider:

SENDZERO This flag indicates that the MAP provider support the sending of zero-length (component-less) TSDUs.

XPG4_1 This indicates that the MAP provider conforms to XTI in XPG4 andsupports primitives MAP_ADDR_REQ and MAP_ADDR_ACK.

TODU sizePROTOID length, PROTOID offsetMAPI version

Flags

Valid States

New State

Rules

The following rules apply when the type of service is operations class 4:

— The ETSDU size, CDATA size and DDATA size fields should be ‘-2’.

— The TSDU size should be equal to the TIDU size.

2 This is the amount of user components that may be present in a single service specific primitive.

2014-10-25 33


4.1.3 Bind Application Context Request

MAP BIND REQ

This primitive requests that the MAP provider bind a protocol address to the stream, negotiatethe number of dialogue open indications allowed to be outstanding by the MAP provider for thespecified protocol address, and activate1 the stream associated with the protocol address.

Format

The format of the message is one ‘M_PROTO’ message block. The format of the ‘M_PROTO’ messageblock is as follows:

typedef struct {

ulong PRIM_type; /* always MAP_BIND_REQ */

ulong ADDR_length; /* length of protocol address */

ulong ADDR_offset; /* offset of protocol address */

unsigned long DIAIND_number; /* requested number of dialogue indications to be queued */

} MAP_bind_req_t;

Parameters

PRIM typeIndicates the primitive type.

ADDR lengthThe length2 of the protocol address to be bound to the stream.

ADDR offsetThe offset from the beiginning of the ‘M_PROTO’ block where the protocol address begins.The address in the ‘M_PROTO’ message block is however, aligned the same as it wasreceived from the MAP user.

DIAIND number3 The requested number of connection indications4 allowed to be outstanding by theMAP provider for the specified protocol address.

Flags

Valid States

New State

Acknowledgements

This primitive requires the MAP provider to geenrate one of the following acknowledgements uponreceipt of the primitive, and the MAP user must wait for the acknowledgement before issuing anyother primitive:

1 A stream is viewed as active when the MAP provider may receive and transmit components (TrasactionProtocol Data Units) associated with the stream

2 All lengths, offsets and sizes in all structures refer to the number of bytes.3 This field should be ignored by those application contexts providing operations class 4 service.4 If the number outstanding connect indications equals CONIND number, the MAP provider need not discard

further incoming connect indications, but may chose to queue them internally until the number of outstandingconnect indications drops below CONNIND number.

34 Version 1.1 Rel. 7.20141001


— Successful: Correct acknowledgement of the primitive is indicated with the MAP_BIND_ACK

primitive described in Section 4.1.4 [Bind Application Context Acknowledgement], page 36.

— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive describedin Section 4.1.10 [Error Acknowledgement], page 43. The allowable errors are as follows:

TBADADDR This indicates that the protocol address was in an incorrect format or the addresscontained illegal information. It is not indended to indicate protocol errors.

TNOADDR This indicates that the MAP provider could not allocate an address.

TACCES This indicates that the user did not have proper permissions for the use of therequested address.

TOUTSTATE The primitive would place the MAP interface out of state.

TSYSERR A system error has occured and the UNIX System error in indicated in the prim-itive.

TADDRBUSY This indicated that the requested address is already in use.

2014-10-25 35


4.1.4 Bind Application Context Acknowledgement

MAP BIND ACK

This primitive indicates to the MAP user that the specified protoocl address has been bound tothe stream, that the specified number of dialogue open indications are allowed to be queued by theMAP provider for th specified protocol address, and that the stream associated with the specifiedprotocol address has ben activated.

Format

The format of the message is one ‘M_PCPROTO’ message block. The format of the ‘M_PCPROTO’ messageblock is as follows:

typedef struct {

long PRIM_type; /* always MAP_BIND_ACK */

long ADDR_length; /* length of address -- see note in sec. 1.4 */

long ADDR_offset; /* offset of address */

ulong DIAIND_number; /* dialogue open indications to be queued */

} MAP_bind_ack_t;

Parameters

PRIM typeADDR lengthADDR offsetDIAIND number

Flags

Valid States

New State

Rules

The following rules apply to the binding of the specified protocol address to the stream:

— If the ADDR length

36 Version 1.1 Rel. 7.20141001


4.1.5 Unbind Application Context Request

MAP UNBIND REQ

This primitive requests that the MAP provider unbind the protocol address associated with thestream and deactivate the stream.

Format

The format of the message is one ‘M_PROTO’ message block. The format of the ‘M_PROTO’ mesageblock is as follows:

typedef struct {

long PRIM_type; /* always MAP_UNBIND_REQ */

} MAP_unbind_req_t;

Parameters

PRIM type:Indicates primitive type.

Valid States

New State

Acknowledgements

This primitive requires the MAP provider to generate the following acknowledgements upon receiptof the primitive and that the MAP user must wait for the acknowledgement before issuing any otherprimitives:

— Successful: Correct acknowledgement of the primitive is indicated with the MAP_OK_ACK prim-itive described in Section 4.1.11 [Successful Receipt Acknowledgement], page 44.



TSYSERR A system error has occurred and the UNIX system error is indicated in the prim-itive.

2014-10-25 37


4.1.6 Options Management Request

MAP OPTMGMT REQ

This primitive allows the MAP user to manage the options associated with the stream.

Format


typedef struct {

long PRIM_type; /* always MAP_OPTMGMT_REQ */

long OPT_length; /* options length */

long OPT_offset; /* options offset */

long MGMT_flags; /* flags */

} MAP_optmgmt_req_t;

Parameters


OPT lengthThe length of the protocol options associated with the primitive.

OPT offset The offset from the beginning of the ‘M_PROTO’ message block where the options begin.The proper alignment of options is not guaranteed. The options are, however, alignedthe same as they were received from the MAP user.

MGMT flagsThe flags which define the request made by the MAP user.

Flags

T_NEGOTIATE

Negotiate and set the options with the MAP provider.

T_CHECK Check the validity of the specified options.

T_CURRENT Return the options currently in effect.

T_DEFAULT Return the default options.

Rules

For the rules governing the requests made by this primitive, see the MAP_OPTMGMT_ACK primitivedescribed in Section 4.1.9 [Options Management Acknowledgement], page 42.

Valid States

New State

Acknowledgements

This primitive requires the MAP provider to generate one of the following acknowledgements uponreceipt of the primitive and that the MAP user await the acknowledgement before issuing any otheprimitives:

38 Version 1.1 Rel. 7.20141001


— Successful: Acknowledgement of the primitive with the MAP_OPTMGMT_ACK primitive describedin Section 4.1.9 [Options Management Acknowledgement], page 42.


TACCES This indicates that the user did not have proper permissions for the use of therequested options.


TBADOPT This indicates that the options as specified were in an incorrect format, or theycontained illegal information.

TBADFLAG This indicates that the flags as specified were incorrect or illegal.

TSYSERR A system error has occured and the UNIX system error is indicated in the primi-tive.

TNOTSUPPORT

This MAP provider does not support the requested flag (T_CHECK or T_CURRENT).

2014-10-25 39


4.1.7 Get Protocol Address Request

MAP ADDR REQ

This primitive requests that the MAP provider return the local protocol address that is bound tothe stream and the address of the remote MAP entity if a dialogue has been established.

Format


typedef struct {

long PRIM_type; /* always MAP_ADDR_REQ */

} MAP_addr_req_t;

Parameters


Valid States

New State

Acknowledgements

This primitive requires the MAP provider to generate one of the following acknowledegements uponreceipt of the primitive, and the MAP user must wait for the acknowledgement before issuing anyother primitives:

— Successful: Correct acknowledgement of the primitive is indicated with the MAP_ADDR_ACK

primitive described in Section 4.1.8 [Get Protocol Address Acknowledgement], page 41.

— Non-fatal errors: There are no errors associated with the issuance of this primitive.

40 Version 1.1 Rel. 7.20141001


4.1.8 Get Protocol Address Acknowledgement

MAP ADDR ACK

Format

Parameters

Flags

Valid States

New State

2014-10-25 41


4.1.9 Options Management Acknowledgement

MAP OPTMGMT ACK

Format

Parameters

Flags

Valid States

New State

42 Version 1.1 Rel. 7.20141001


4.1.10 Error Acknowledgement

MAP ERROR ACK

Format

Parameters

Valid Error Codes

Valid States

New State

2014-10-25 43


4.1.11 Successful Receipt Acknowledgement

MAP OK ACK

Format

Parameters

Valid States

New State

44 Version 1.1 Rel. 7.20141001


4.2 Association Establishment Phase

4.2.1 Association Establishment Request

MAP OPEN REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements


— Successful Association Establishment:

— Unsuccessful Association Establishment:

— Non-fatal errors:

2014-10-25 45


4.2.2 Association Establishment Indication

MAP OPEN IND

Format

Parameters

Flags

Valid States

New State

46 Version 1.1 Rel. 7.20141001


4.2.3 Association Establishment Response

MAP OPEN RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements


— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described inSection 4.1.11 [Successful Receipt Acknowledgement], page 44.




2014-10-25 47


4.2.4 Association Establishment Confirmation

MAP OPEN CON

Format

Parameters

Flags

Valid States

New State

48 Version 1.1 Rel. 7.20141001


4.3 Component Transfer Phase

4.3.1 Component Delimitation Request

MAP DELIM REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 49


4.3.2 Component Delimitation Indication

MAP DELIM IND

Format

Parameters

Flags

Valid States

New State

50 Version 1.1 Rel. 7.20141001


4.4 Association Termination Phase

4.4.1 Association Release Request

MAP CLOSE REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 51


4.4.2 Association Release Indication

MAP CLOSE IND

Format

Parameters

Flags

Valid States

New State

52 Version 1.1 Rel. 7.20141001


4.4.3 Association Abort Request

MAP ABORT REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 53


4.4.4 Association User Abort Indication

MAP UABORT IND

Format

Parameters

Flags

Valid States

New State

54 Version 1.1 Rel. 7.20141001


4.4.5 Association Provider Abort Indication

MAP PABORT IND

Format

Parameters

Flags

Valid States

New State

2014-10-25 55


4.4.6 Association Notice Indication

MAP NOTICE IND

Format

Parameters

Flags

Valid States

New State

56 Version 1.1 Rel. 7.20141001


4.5 Secure Transport Primitives

4.5.1 Secure Transport Class 1 Request

MAP STC1 REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 57


4.5.2 Secure Transport Class 1 Indication

MAP STC1 IND

Format

Parameters

Flags

Valid States

New State

58 Version 1.1 Rel. 7.20141001



MAP STC2 REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 59



MAP STC2 IND

Format

Parameters

Flags

Valid States

New State

60 Version 1.1 Rel. 7.20141001



MAP STC3 REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 61



MAP STC3 IND

Format

Parameters

Flags

Valid States

New State

62 Version 1.1 Rel. 7.20141001



MAP STC4 REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 63



MAP STC4 IND

Format

Parameters

Flags

Valid States

New State

64 Version 1.1 Rel. 7.20141001


4.6 Service Specific Primitives

4.6.1 Activate Supplementary Service Request

MAP ACTSS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 65


4.6.2 Activate Supplementary Service Indication

MAP ACTSS IND

Format

Parameters

Flags

Valid States

New State

66 Version 1.1 Rel. 7.20141001


4.6.3 Activate Supplementary Service Response

MAP ACTSS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 67


4.6.4 Activate Supplementary Service Confirmation

MAP ACTSS CON

Format

Parameters

Flags

Valid States

New State

68 Version 1.1 Rel. 7.20141001


4.6.5 Activate Traceec Mode Request

MAP ACTTM REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 69


4.6.6 Activate Traceec Mode Indication

MAP ACTTM IND

Format

Parameters

Flags

Valid States

New State

70 Version 1.1 Rel. 7.20141001


4.6.7 Activate Traceec Mode Response

MAP ACTTM RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 71


4.6.8 Activate Traceec Mode Confirmation

MAP ACTTM CON

Format

Parameters

Flags

Valid States

New State

72 Version 1.1 Rel. 7.20141001


4.6.9 Alert Service Center Request

MAP ALERTSC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 73


4.6.10 Alert Service Center Indication

MAP ALERTSC IND

Format

Parameters

Flags

Valid States

New State

74 Version 1.1 Rel. 7.20141001


4.6.11 Alert Service Center Response

MAP ALERTSC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 75


4.6.12 Alert Service Center Confirmation

MAP ALERTSC CON

Format

Parameters

Flags

Valid States

New State

76 Version 1.1 Rel. 7.20141001


4.6.13 Allocate Handover Number Request

MAP ALLOCHN REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 77


4.6.14 Allocate Handover Number Indication

MAP ALLOCHN IND

Format

Parameters

Flags

Valid States

New State

78 Version 1.1 Rel. 7.20141001


4.6.15 Allocate Handover Number Response

MAP ALLOCHN RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 79


4.6.16 Allocate Handover Number Confirmation

MAP ALLOCHN CON

Format

Parameters

Flags

Valid States

New State

80 Version 1.1 Rel. 7.20141001


4.6.17 Any Time Modification Request

MAP ANYMOD REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 81


4.6.18 Any Time Modification Indication

MAP ANYMOD IND

Format

Parameters

Flags

Valid States

New State

82 Version 1.1 Rel. 7.20141001


4.6.19 Any Time Modification Response

MAP ANYMOD RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 83


4.6.20 Any Time Modification Confirmation

MAP ANYMOD CON

Format

Parameters

Flags

Valid States

New State

84 Version 1.1 Rel. 7.20141001


4.6.21 Any Time Interrogation Request

MAP ANYQRY REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 85


4.6.22 Any Time Interrogation Indication

MAP ANYQRY IND

Format

Parameters

Flags

Valid States

New State

86 Version 1.1 Rel. 7.20141001


4.6.23 Any Time Interrogation Response

MAP ANYQRY RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 87


4.6.24 Any Time Interrogation Confirmation

MAP ANYQRY CON

Format

Parameters

Flags

Valid States

New State

88 Version 1.1 Rel. 7.20141001


4.6.25 Any Time Subscription Interrogation Request

MAP ANYSUB REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 89


4.6.26 Any Time Subscription Interrogation Indication

MAP ANYSUB IND

Format

Parameters

Flags

Valid States

New State

90 Version 1.1 Rel. 7.20141001


4.6.27 Any Time Subscription Interrogation Response

MAP ANYSUB RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 91


4.6.28 Any Time Subscription Interrogation Confirmation

MAP ANYSUB CON

Format

Parameters

Flags

Valid States

New State

92 Version 1.1 Rel. 7.20141001


4.6.29 Authentication Failure Report Request

MAP AUTHFAIL REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 93


4.6.30 Authentication Failure Report Indication

MAP AUTHFAIL IND

Format

Parameters

Flags

Valid States

New State

94 Version 1.1 Rel. 7.20141001


4.6.31 Authentication Failure Report Response

MAP AUTHFAIL RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 95


4.6.32 Authentication Failure Report Confirmation

MAP AUTHFAIL CON

Format

Parameters

Flags

Valid States

New State

96 Version 1.1 Rel. 7.20141001


4.6.33 Authenticate Request

MAP AUTH REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 97


4.6.34 Authenticate Indication

MAP AUTH IND

Format

Parameters

Flags

Valid States

New State

98 Version 1.1 Rel. 7.20141001


4.6.35 Authenticate Response

MAP AUTH RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 99


4.6.36 Authenticate Confirmation

MAP AUTH CON

Format

Parameters

Flags

Valid States

New State

100 Version 1.1 Rel. 7.20141001


4.6.37 Cancel Location Request

MAP CANCLOC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 101


4.6.38 Cancel Location Indication

MAP CANCLOC IND

Format

Parameters

Flags

Valid States

New State

102 Version 1.1 Rel. 7.20141001


4.6.39 Cancel Location Response

MAP CANCLOC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 103


4.6.40 Cancel Location Confirmation

MAP CANCLOC CON

Format

Parameters

Flags

Valid States

New State

104 Version 1.1 Rel. 7.20141001


4.6.41 Reset Request

MAP RESET REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 105


4.6.42 Reset Indication

MAP RESET IND

Format

Parameters

Flags

Valid States

New State

106 Version 1.1 Rel. 7.20141001


4.6.43 Reset Response

MAP RESET CON

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 107


4.6.44 Reset Confirmation

MAP RESET RES

Format

Parameters

Flags

Valid States

New State

108 Version 1.1 Rel. 7.20141001


4.6.45 Restore Request

MAP RESTORE REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 109


4.6.46 Restore Indication

MAP RESTORE IND

Format

Parameters

Flags

Valid States

New State

110 Version 1.1 Rel. 7.20141001


4.6.47 Restore Response

MAP RESTORE CON

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 111


4.6.48 Restore Confirmation

MAP RESTORE RES

Format

Parameters

Flags

Valid States

New State

112 Version 1.1 Rel. 7.20141001


4.6.49 Resume Call Handling Request

MAP RESUME REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 113


4.6.50 Resume Call Handling Indication

MAP RESUME IND

Format

Parameters

Flags

Valid States

New State

114 Version 1.1 Rel. 7.20141001


4.6.51 Resume Call Handling Confirmation

MAP RESUME RES

Format

Parameters

Flags

Valid States

New State

2014-10-25 115


4.6.52 Resume Call Handling Response

MAP RESUME CON

Format

Parameters

Flags

Valid States

New State

Acknowledgements






116 Version 1.1 Rel. 7.20141001


4.6.53 Search for MS Request

MAP SEARCH REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 117


4.6.54 Search for MS Indication

MAP SEARCH IND

Format

Parameters

Flags

Valid States

New State

118 Version 1.1 Rel. 7.20141001


4.6.55 Search for MS Confirmation

MAP SEARCH RES

Format

Parameters

Flags

Valid States

New State

2014-10-25 119


4.6.56 Search for MS Response

MAP SEARCH CON

Format

Parameters

Flags

Valid States

New State

Acknowledgements






120 Version 1.1 Rel. 7.20141001


4.6.57 Check IEMI Request

MAP CKIEMI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 121


4.6.58 Check IEMI Indication

MAP CKIEMI IND

Format

Parameters

Flags

Valid States

New State

122 Version 1.1 Rel. 7.20141001


4.6.59 Check IEMI Response

MAP CKIEMI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 123


4.6.60 Check IEMI Confirmation

MAP CKIEMI CON

Format

Parameters

Flags

Valid States

New State

124 Version 1.1 Rel. 7.20141001


4.6.61 Deactivate Supplementary Service Request

MAP DEACTSS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 125


4.6.62 Deactivate Supplementary Service Indication

MAP DEACTSS IND

Format

Parameters

Flags

Valid States

New State

126 Version 1.1 Rel. 7.20141001


4.6.63 Deactivate Supplementary Service Response

MAP DEACTSS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 127


4.6.64 Deactivate Supplementary Service Confirmation

MAP DEACTSS CON

Format

Parameters

Flags

Valid States

New State

128 Version 1.1 Rel. 7.20141001


4.6.65 Deactivate Trace Mode Request

MAP DEACTTM REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 129


4.6.66 Deactivate Trace Mode Indication

MAP DEACTTM IND

Format

Parameters

Flags

Valid States

New State

130 Version 1.1 Rel. 7.20141001


4.6.67 Deactivate Trace Mode Response

MAP DEACTTM RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 131


4.6.68 Deactivate Trace Mode Confirmation

MAP DEACTTM CON

Format

Parameters

Flags

Valid States

New State

132 Version 1.1 Rel. 7.20141001


4.6.69 Delete Subscriber Data Request

MAP DELSUBD REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 133


4.6.70 Delete Subscriber Data Indication

MAP DELSUBD IND

Format

Parameters

Flags

Valid States

New State

134 Version 1.1 Rel. 7.20141001


4.6.71 Delete Subscriber Data Response

MAP DELSUBD RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 135


4.6.72 Delete Subscriber Data Confirmation

MAP DELSUBD CON

Format

Parameters

Flags

Valid States

New State

136 Version 1.1 Rel. 7.20141001


4.6.73 Erase CC Entry Request

MAP ERASECC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 137


4.6.74 Erase CC Entry Indication

MAP ERASECC IND

Format

Parameters

Flags

Valid States

New State

138 Version 1.1 Rel. 7.20141001


4.6.75 Erase CC Entry Response

MAP ERASECC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 139


4.6.76 Erase CC Entry Confirmation

MAP ERASECC CON

Format

Parameters

Flags

Valid States

New State

140 Version 1.1 Rel. 7.20141001


4.6.77 Erase Supplementatry Service Request

MAP ERASESS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 141


4.6.78 Erase Supplementatry Service Indication

MAP ERASESS IND

Format

Parameters

Flags

Valid States

New State

142 Version 1.1 Rel. 7.20141001


4.6.79 Erase Supplementatry Service Response

MAP ERASESS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 143


4.6.80 Erase Supplementatry Service Confirmation

MAP ERASESS CON

Format

Parameters

Flags

Valid States

New State

144 Version 1.1 Rel. 7.20141001


4.6.81 Failure Report Request

MAP FAILURE REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 145


4.6.82 Failure Report Indication

MAP FAILURE IND

Format

Parameters

Flags

Valid States

New State

146 Version 1.1 Rel. 7.20141001


4.6.83 Failure Report Response

MAP FAILURE RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 147


4.6.84 Failure Report Confirmation

MAP FAILURE CON

Format

Parameters

Flags

Valid States

New State

148 Version 1.1 Rel. 7.20141001


4.6.85 Forward Access Signalling Request

MAP FAS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 149


4.6.86 Forward Access Signalling Indication

MAP FAS IND

Format

Parameters

Flags

Valid States

New State

150 Version 1.1 Rel. 7.20141001


4.6.87 Forward Access Signalling Response

MAP FAS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 151


4.6.88 Forward Access Signalling Confirmation

MAP FAS CON

Format

Parameters

Flags

Valid States

New State

152 Version 1.1 Rel. 7.20141001


4.6.89 Forward Check SS Indication Request

MAP FCKSSIND REQ

Format

Parameters

Flags

Valid States

New State

2014-10-25 153


4.6.90 Forward Check SS Indication Indication

MAP FCKSSIND IND

Format

Parameters

Flags

Valid States

New State

154 Version 1.1 Rel. 7.20141001


4.6.91 Forward Check SS Indication Response

MAP FCKSSIND RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 155


4.6.92 Forward Check SS Indication Confirmation

MAP FCKSSIND CON

Format

Parameters

Flags

Valid States

New State

156 Version 1.1 Rel. 7.20141001


4.6.93 Forward Group Call Signalling Request

MAP FGRCSIG REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 157


4.6.94 Forward Group Call Signalling Indication

MAP FGRCSIG IND

Format

Parameters

Flags

Valid States

New State

158 Version 1.1 Rel. 7.20141001


4.6.95 Forward Group Call Signalling Response

MAP FGRCSIG RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 159


4.6.96 Forward Group Call Signalling Confirmation

MAP FGRCSIG CON

Format

Parameters

Flags

Valid States

New State

160 Version 1.1 Rel. 7.20141001


4.6.97 Forward New IMSI Request

MAP FNEWIMSI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 161


4.6.98 Forward New IMSI Indication

MAP FNEWIMSI IND

Format

Parameters

Flags

Valid States

New State

162 Version 1.1 Rel. 7.20141001


4.6.99 Forward New IMSI Response

MAP FNEWIMSI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 163


4.6.100 Forward New IMSI Confirmation

MAP FNEWIMSI CON

Format

Parameters

Flags

Valid States

New State

164 Version 1.1 Rel. 7.20141001


4.6.101 Obtain IEMI Request

MAP GETIEMI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 165


4.6.102 Obtain IEMI Indication

MAP GETIEMI IND

Format

Parameters

Flags

Valid States

New State

166 Version 1.1 Rel. 7.20141001


4.6.103 Obtain IEMI Response

MAP GETIEMI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 167


4.6.104 Obtain IEMI Confirmation

MAP GETIEMI CON

Format

Parameters

Flags

Valid States

New State

168 Version 1.1 Rel. 7.20141001


4.6.105 Get Password Request

MAP GETPASS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 169


4.6.106 Get Password Indication

MAP GETPASS IND

Format

Parameters

Flags

Valid States

New State

170 Version 1.1 Rel. 7.20141001


4.6.107 Get Password Response

MAP GETPASS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 171


4.6.108 Get Password Confirmation

MAP GETPASS CON

Format

Parameters

Flags

Valid States

New State

172 Version 1.1 Rel. 7.20141001


4.6.109 Inform Service Center Request

MAP INFORMSC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 173


4.6.110 Inform Service Center Indication

MAP INFORMSC IND

Format

Parameters

Flags

Valid States

New State

174 Version 1.1 Rel. 7.20141001


4.6.111 Inform Service Center Response

MAP INFORMSC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 175


4.6.112 Inform Service Center Confirmation

MAP INFORMSC CON

Format

Parameters

Flags

Valid States

New State

176 Version 1.1 Rel. 7.20141001


4.6.113 Insert Subscriber Data Request

MAP INSSUBSD REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 177


4.6.114 Insert Subscriber Data Indication

MAP INSSUBSD IND

Format

Parameters

Flags

Valid States

New State

178 Version 1.1 Rel. 7.20141001


4.6.115 Insert Subscriber Data Response

MAP INSSUBSD RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 179


4.6.116 Insert Subscriber Data Confirmation

MAP INSSUBSD CON

Format

Parameters

Flags

Valid States

New State

180 Version 1.1 Rel. 7.20141001


4.6.117 Iterrogate Supplementary Service Request

MAP INTERGSS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 181


4.6.118 Iterrogate Supplementary Service Indication

MAP INTERGSS IND

Format

Parameters

Flags

Valid States

New State

182 Version 1.1 Rel. 7.20141001


4.6.119 Iterrogate Supplementary Service Response

MAP INTERGSS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 183


4.6.120 Iterrogate Supplementary Service Confirmation

MAP INTERGSS CON

Format

Parameters

Flags

Valid States

New State

184 Version 1.1 Rel. 7.20141001


4.6.121 IST Alert Request

MAP ISTALERT REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 185


4.6.122 IST Alert Indication

MAP ISTALERT IND

Format

Parameters

Flags

Valid States

New State

186 Version 1.1 Rel. 7.20141001


4.6.123 IST Alert Response

MAP ISTALERT RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 187


4.6.124 IST Alert Confirmation

MAP ISTALERT CON

Format

Parameters

Flags

Valid States

New State

188 Version 1.1 Rel. 7.20141001


4.6.125 IST Command Request

MAP ISTCMD REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 189


4.6.126 IST Command Indication

MAP ISTCMD IND

Format

Parameters

Flags

Valid States

New State

190 Version 1.1 Rel. 7.20141001


4.6.127 IST Command Response

MAP ISTCMD RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 191


4.6.128 IST Command Confirmation

MAP ISTCMD CON

Format

Parameters

Flags

Valid States

New State

192 Version 1.1 Rel. 7.20141001


4.6.129 Note MM Event Request

MAP MMEVENT REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 193


4.6.130 Note MM Event Indication

MAP MMEVENT IND

Format

Parameters

Flags

Valid States

New State

194 Version 1.1 Rel. 7.20141001


4.6.131 Note MM Event Response

MAP MMEVENT RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 195


4.6.132 Note MM Event Confirmation

MAP MMEVENT CON

Format

Parameters

Flags

Valid States

New State

196 Version 1.1 Rel. 7.20141001


4.6.133 Mobile Originated Forward Short Message Request

MAP MOFSMS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 197


4.6.134 Mobile Originated Forward Short Message Indication

MAP MOFSMS IND

Format

Parameters

Flags

Valid States

New State

198 Version 1.1 Rel. 7.20141001


4.6.135 Mobile Originated Forward Short Message Response

MAP MOFSMS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 199


4.6.136 Mobile Originated Forward Short Message Confirmation

MAP MOFSMS CON

Format

Parameters

Flags

Valid States

New State

200 Version 1.1 Rel. 7.20141001


4.6.137 Note MS Present for GRPS Request

MAP MSGRPSPRES REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 201


4.6.138 Note MS Present for GRPS Indication

MAP MSGRPSPRES IND

Format

Parameters

Flags

Valid States

New State

202 Version 1.1 Rel. 7.20141001


4.6.139 Note MS Present for GRPS Response

MAP MSGRPSPRES RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 203


4.6.140 Note MS Present for GRPS Confirmation

MAP MSGRPSPRES CON

Format

Parameters

Flags

Valid States

New State

204 Version 1.1 Rel. 7.20141001


4.6.141 Mobile Terminated Forward Short Message Request

MAP MTFSMS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 205


4.6.142 Mobile Terminated Forward Short Message Indication

MAP MTFSMS IND

Format

Parameters

Flags

Valid States

New State

206 Version 1.1 Rel. 7.20141001


4.6.143 Mobile Terminated Forward Short Message Response

MAP MTFSMS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 207


4.6.144 Mobile Terminated Forward Short Message Confirmation

MAP MTFSMS CON

Format

Parameters

Flags

Valid States

New State

208 Version 1.1 Rel. 7.20141001


4.6.145 Page Request

MAP PAGE REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 209


4.6.146 Page Indication

MAP PAGE IND

Format

Parameters

Flags

Valid States

New State

210 Version 1.1 Rel. 7.20141001


4.6.147 Page Response

MAP PAGE RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 211


4.6.148 Page Confirmation

MAP PAGE CON

Format

Parameters

Flags

Valid States

New State

212 Version 1.1 Rel. 7.20141001


4.6.149 Prepare Group Call Request

MAP PREPGC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 213


4.6.150 Prepare Group Call Indication

MAP PREPGC IND

Format

Parameters

Flags

Valid States

New State

214 Version 1.1 Rel. 7.20141001


4.6.151 Prepare Group Call Response

MAP PREPGC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 215


4.6.152 Prepare Group Call Confirmation

MAP PREPGC CON

Format

Parameters

Flags

Valid States

New State

216 Version 1.1 Rel. 7.20141001


4.6.153 Prepare Handover Request

MAP PREPHO REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 217


4.6.154 Prepare Handover Indication

MAP PREPHO IND

Format

Parameters

Flags

Valid States

New State

218 Version 1.1 Rel. 7.20141001


4.6.155 Prepare Handover Response

MAP PREPHO RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 219


4.6.156 Prepare Handover Confirmation

MAP PREPHO CON

Format

Parameters

Flags

Valid States

New State

220 Version 1.1 Rel. 7.20141001


4.6.157 Prepare Subsequent Handover Request

MAP PREPSH REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 221


4.6.158 Prepare Subsequent Handover Indication

MAP PREPSH IND

Format

Parameters

Flags

Valid States

New State

222 Version 1.1 Rel. 7.20141001


4.6.159 Prepare Subsequent Handover Response

MAP PREPSH RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 223


4.6.160 Prepare Subsequent Handover Confirmation

MAP PREPSH CON

Format

Parameters

Flags

Valid States

New State

224 Version 1.1 Rel. 7.20141001


4.6.161 Process Access Signalling Request

MAP PROCAS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 225


4.6.162 Process Access Signalling Indication

MAP PROCAS IND

Format

Parameters

Flags

Valid States

New State

226 Version 1.1 Rel. 7.20141001


4.6.163 Process Access Signalling Response

MAP PROCAS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 227


4.6.164 Process Access Signalling Confirmation

MAP PROCAS CON

Format

Parameters

Flags

Valid States

New State

228 Version 1.1 Rel. 7.20141001


4.6.165 Process Group Call Signalling Request

MAP PROCGC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 229


4.6.166 Process Group Call Signalling Indication

MAP PROCGC IND

Format

Parameters

Flags

Valid States

New State

230 Version 1.1 Rel. 7.20141001


4.6.167 Process Group Call Signalling Response

MAP PROCGC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 231


4.6.168 Process Group Call Signalling Confirmation

MAP PROCGC CON

Format

Parameters

Flags

Valid States

New State

232 Version 1.1 Rel. 7.20141001


4.6.169 Process Unstructured SS Request

MAP PROCUSS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 233


4.6.170 Process Unstructured SS Indication

MAP PROCUSS IND

Format

Parameters

Flags

Valid States

New State

234 Version 1.1 Rel. 7.20141001


4.6.171 Process Unstructured SS Response

MAP PROCUSS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 235


4.6.172 Process Unstructured SS Confirmation

MAP PROCUSS CON

Format

Parameters

Flags

Valid States

New State

236 Version 1.1 Rel. 7.20141001


4.6.173 Provide IMSI Request

MAP PROVIMSI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 237


4.6.174 Provide IMSI Indication

MAP PROVIMSI IND

Format

Parameters

Flags

Valid States

New State

238 Version 1.1 Rel. 7.20141001


4.6.175 Provide IMSI Response

MAP PROVIMSI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 239


4.6.176 Provide IMSI Confirmation

MAP PROVIMSI CON

Format

Parameters

Flags

Valid States

New State

240 Version 1.1 Rel. 7.20141001


4.6.177 Provide Roaming Number Request

MAP PROVRN REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 241


4.6.178 Provide Roaming Number Indication

MAP PROVRN IND

Format

Parameters

Flags

Valid States

New State

242 Version 1.1 Rel. 7.20141001


4.6.179 Provide Roaming Number Response

MAP PROVRN RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 243


4.6.180 Provide Roaming Number Confirmation

MAP PROVRN CON

Format

Parameters

Flags

Valid States

New State

244 Version 1.1 Rel. 7.20141001


4.6.181 Provide Subscriber Location Request

MAP PROVSLOC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 245


4.6.182 Provide Subscriber Location Indication

MAP PROVSLOC IND

Format

Parameters

Flags

Valid States

New State

246 Version 1.1 Rel. 7.20141001


4.6.183 Provide Subscriber Location Response

MAP PROVSLOC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 247


4.6.184 Provide Subscriber Location Confirmation

MAP PROVSLOC CON

Format

Parameters

Flags

Valid States

New State

248 Version 1.1 Rel. 7.20141001


4.6.185 Provide Subscriber Information Request

MAP PROVSUBI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 249


4.6.186 Provide Subscriber Information Indication

MAP PROVSUBI IND

Format

Parameters

Flags

Valid States

New State

250 Version 1.1 Rel. 7.20141001


4.6.187 Provide Subscriber Information Response

MAP PROVSUBI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 251


4.6.188 Provide Subscriber Information Confirmation

MAP PROVSUBI CON

Format

Parameters

Flags

Valid States

New State

252 Version 1.1 Rel. 7.20141001


4.6.189 Purge MS Request

MAP PURGEMS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 253


4.6.190 Purge MS Indication

MAP PURGEMS IND

Format

Parameters

Flags

Valid States

New State

254 Version 1.1 Rel. 7.20141001


4.6.191 Purge MS Response

MAP PURGEMS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 255


4.6.192 Purge MS Confirmation

MAP PURGEMS CON

Format

Parameters

Flags

Valid States

New State

256 Version 1.1 Rel. 7.20141001


4.6.193 Ready for SM Request

MAP RDYSM REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 257


4.6.194 Ready for SM Indication

MAP RDYSM IND

Format

Parameters

Flags

Valid States

New State

258 Version 1.1 Rel. 7.20141001


4.6.195 Ready for SM Response

MAP RDYSM RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 259


4.6.196 Ready for SM Confirmation

MAP RDYSM CON

Format

Parameters

Flags

Valid States

New State

260 Version 1.1 Rel. 7.20141001


4.6.197 Register CC Entry Request

MAP REGCC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 261


4.6.198 Register CC Entry Indication

MAP REGCC IND

Format

Parameters

Flags

Valid States

New State

262 Version 1.1 Rel. 7.20141001


4.6.199 Register CC Entry Response

MAP REGCC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 263


4.6.200 Register CC Entry Confirmation

MAP REGCC CON

Format

Parameters

Flags

Valid States

New State

264 Version 1.1 Rel. 7.20141001


4.6.201 Register Password Request

MAP REGPW REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 265


4.6.202 Register Password Indication

MAP REGPW IND

Format

Parameters

Flags

Valid States

New State

266 Version 1.1 Rel. 7.20141001


4.6.203 Register Password Response

MAP REGPW RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 267


4.6.204 Register Password Confirmation

MAP REGPW CON

Format

Parameters

Flags

Valid States

New State

268 Version 1.1 Rel. 7.20141001


4.6.205 Register Supplementary Service Request

MAP REGSS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 269


4.6.206 Register Supplementary Service Indication

MAP REGSS IND

Format

Parameters

Flags

Valid States

New State

270 Version 1.1 Rel. 7.20141001


4.6.207 Register Supplementary Service Response

MAP REGSS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 271


4.6.208 Register Supplementary Service Confirmation

MAP REGSS CON

Format

Parameters

Flags

Valid States

New State

272 Version 1.1 Rel. 7.20141001


4.6.209 Remote User Free Request

MAP REMUSRFREE REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 273


4.6.210 Remote User Free Indication

MAP REMUSRFREE IND

Format

Parameters

Flags

Valid States

New State

274 Version 1.1 Rel. 7.20141001


4.6.211 Remote User Free Response

MAP REMUSRFREE RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 275


4.6.212 Remote User Free Confirmation

MAP REMUSRFREE CON

Format

Parameters

Flags

Valid States

New State

276 Version 1.1 Rel. 7.20141001


4.6.213 Send Identification Request

MAP SENDID REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 277


4.6.214 Send Identification Indication

MAP SENDID IND

Format

Parameters

Flags

Valid States

New State

278 Version 1.1 Rel. 7.20141001


4.6.215 Send Identification Response

MAP SENDID RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 279


4.6.216 Send Identification Confirmation

MAP SENDID CON

Format

Parameters

Flags

Valid States

New State

280 Version 1.1 Rel. 7.20141001


4.6.217 Set Ciphering Mode Request

MAP SETCM REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 281


4.6.218 Set Ciphering Mode Indication

MAP SETCM IND

Format

Parameters

Flags

Valid States

New State

282 Version 1.1 Rel. 7.20141001


4.6.219 Set Ciphering Mode Response

MAP SETCM RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 283


4.6.220 Set Ciphering Mode Confirmation

MAP SETCM CON

Format

Parameters

Flags

Valid States

New State

284 Version 1.1 Rel. 7.20141001


4.6.221 Set Reporting State Request

MAP SETREP REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 285


4.6.222 Set Reporting State Indication

MAP SETREP IND

Format

Parameters

Flags

Valid States

New State

286 Version 1.1 Rel. 7.20141001


4.6.223 Set Reporting State Response

MAP SETREP RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 287


4.6.224 Set Reporting State Confirmation

MAP SETREP CON

Format

Parameters

Flags

Valid States

New State

288 Version 1.1 Rel. 7.20141001


4.6.225 Report Short Message Delivery Status Request

MAP SMDELIVSTAT REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 289


4.6.226 Report Short Message Delivery Status Indication

MAP SMDELIVSTAT IND

Format

Parameters

Flags

Valid States

New State

290 Version 1.1 Rel. 7.20141001


4.6.227 Report Short Message Delivery Status Response

MAP SMDELIVSTAT RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 291


4.6.228 Report Short Message Delivery Status Confirmation

MAP SMDELIVSTAT CON

Format

Parameters

Flags

Valid States

New State

292 Version 1.1 Rel. 7.20141001


4.6.229 Send Authentication Information Request

MAP SENDAUTHI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 293


4.6.230 Send Authentication Information Indication

MAP SENDAUTHI IND

Format

Parameters

Flags

Valid States

New State

294 Version 1.1 Rel. 7.20141001


4.6.231 Send Authentication Information Response

MAP SENDAUTHI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 295


4.6.232 Send Authentication Information Confirmation

MAP SENDAUTHI CON

Format

Parameters

Flags

Valid States

New State

296 Version 1.1 Rel. 7.20141001


4.6.233 Send End Signal Request

MAP SENDEND REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 297


4.6.234 Send End Signal Indication

MAP SENDEND IND

Format

Parameters

Flags

Valid States

New State

298 Version 1.1 Rel. 7.20141001


4.6.235 Send End Signal Response

MAP SENDEND RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 299


4.6.236 Send End Signal Confirmation

MAP SENDEND CON

Format

Parameters

Flags

Valid States

New State

300 Version 1.1 Rel. 7.20141001


4.6.237 Send Group Call End Signal Request

MAP SENDGCEND REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 301


4.6.238 Send Group Call End Signal Indication

MAP SENDGCEND IND

Format

Parameters

Flags

Valid States

New State

302 Version 1.1 Rel. 7.20141001


4.6.239 Send Group Call End Signal Response

MAP SENDGCEND RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 303


4.6.240 Send Group Call End Signal Confirmation

MAP SENDGCEND CON

Format

Parameters

Flags

Valid States

New State

304 Version 1.1 Rel. 7.20141001


4.6.241 Send Routing Information for GPRS Request

MAP SENDGPRSRI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 305


4.6.242 Send Routing Information for GPRS Indication

MAP SENDGPRSRI IND

Format

Parameters

Flags

Valid States

New State

306 Version 1.1 Rel. 7.20141001


4.6.243 Send Routing Information for GPRS Response

MAP SENDGPRSRI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 307


4.6.244 Send Routing Information for GPRS Confirmation

MAP SENDGPRSRI CON

Format

Parameters

Flags

Valid States

New State

308 Version 1.1 Rel. 7.20141001


4.6.245 Send Handover Report Request

MAP SENDHOREP REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 309


4.6.246 Send Handover Report Indication

MAP SENDHOREP IND

Format

Parameters

Flags

Valid States

New State

310 Version 1.1 Rel. 7.20141001


4.6.247 Send Handover Report Response

MAP SENDHOREP RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 311


4.6.248 Send Handover Report Confirmation

MAP SENDHOREP CON

Format

Parameters

Flags

Valid States

New State

312 Version 1.1 Rel. 7.20141001


4.6.249 Send IMSI Request

MAP SENDIMSI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 313


4.6.250 Send IMSI Indication

MAP SENDIMSI IND

Format

Parameters

Flags

Valid States

New State

314 Version 1.1 Rel. 7.20141001


4.6.251 Send IMSI Response

MAP SENDIMSI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 315


4.6.252 Send IMSI Confirmation

MAP SENDIMSI CON

Format

Parameters

Flags

Valid States

New State

316 Version 1.1 Rel. 7.20141001


4.6.253 Send Routing Information for LCS Request

MAP SENDLCSRI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 317


4.6.254 Send Routing Information for LCS Indication

MAP SENDLCSRI IND

Format

Parameters

Flags

Valid States

New State

318 Version 1.1 Rel. 7.20141001


4.6.255 Send Routing Information for LCS Response

MAP SENDLCSRI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 319


4.6.256 Send Routing Information for LCS Confirmation

MAP SENDLCSRI CON

Format

Parameters

Flags

Valid States

New State

320 Version 1.1 Rel. 7.20141001


4.6.257 Send Mobile Originated SMS Information Request

MAP SENDMOSMSI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 321


4.6.258 Send Mobile Originated SMS Information Indication

MAP SENDMOSMSI IND

Format

Parameters

Flags

Valid States

New State

322 Version 1.1 Rel. 7.20141001


4.6.259 Send Mobile Originated SMS Information Response

MAP SENDMOSMSI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 323


4.6.260 Send Mobile Originated SMS Information Confirmation

MAP SENDMOSMSI CON

Format

Parameters

Flags

Valid States

New State

324 Version 1.1 Rel. 7.20141001


4.6.261 Send Mobile Terminated SMS Information Request

MAP SENDMTSMSI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 325


4.6.262 Send Mobile Terminated SMS Information Indication

MAP SENDMTSMSI IND

Format

Parameters

Flags

Valid States

New State

326 Version 1.1 Rel. 7.20141001


4.6.263 Send Mobile Terminated SMS Information Response

MAP SENDMTSMSI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 327


4.6.264 Send Mobile Terminated SMS Information Confirmation

MAP SENDMTSMSI CON

Format

Parameters

Flags

Valid States

New State

328 Version 1.1 Rel. 7.20141001


4.6.265 Send Routing Information Request

MAP SENDRI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 329


4.6.266 Send Routing Information Indication

MAP SENDRI IND

Format

Parameters

Flags

Valid States

New State

330 Version 1.1 Rel. 7.20141001


4.6.267 Send Routing Information Response

MAP SENDRI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 331


4.6.268 Send Routing Information Confirmation

MAP SENDRI CON

Format

Parameters

Flags

Valid States

New State

332 Version 1.1 Rel. 7.20141001


4.6.269 Send Routing Information for SM Request

MAP SENDSMSRI REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 333


4.6.270 Send Routing Information for SM Indication

MAP SENDSMSRI IND

Format

Parameters

Flags

Valid States

New State

334 Version 1.1 Rel. 7.20141001


4.6.271 Send Routing Information for SM Response

MAP SENDSMSRI RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 335


4.6.272 Send Routing Information for SM Confirmation

MAP SENDSMSRI CON

Format

Parameters

Flags

Valid States

New State

336 Version 1.1 Rel. 7.20141001


4.6.273 SS Invocation Notification Request

MAP SSINV REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 337


4.6.274 SS Invocation Notification Indication

MAP SSINV IND

Format

Parameters

Flags

Valid States

New State

338 Version 1.1 Rel. 7.20141001


4.6.275 SS Invocation Notification Response

MAP SSINV RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 339


4.6.276 SS Invocation Notification Confirmation

MAP SSINV CON

Format

Parameters

Flags

Valid States

New State

340 Version 1.1 Rel. 7.20141001


4.6.277 Status Report Request

MAP STATUS REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 341


4.6.278 Status Report Indication

MAP STATUS IND

Format

Parameters

Flags

Valid States

New State

342 Version 1.1 Rel. 7.20141001


4.6.279 Status Report Response

MAP STATUS RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 343


4.6.280 Status Report Confirmation

MAP STATUS CON

Format

Parameters

Flags

Valid States

New State

344 Version 1.1 Rel. 7.20141001


4.6.281 Subscriber Location Report Request

MAP SUBLOCREP REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 345


4.6.282 Subscriber Location Report Indication

MAP SUBLOCREP IND

Format

Parameters

Flags

Valid States

New State

346 Version 1.1 Rel. 7.20141001


4.6.283 Subscriber Location Report Response

MAP SUBLOCREP RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 347


4.6.284 Subscriber Location Report Confirmation

MAP SUBLOCREP CON

Format

Parameters

Flags

Valid States

New State

348 Version 1.1 Rel. 7.20141001


4.6.285 Note Subscriber Data Modified Request

MAP SUBSDATAMOD REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 349


4.6.286 Note Subscriber Data Modified Indication

MAP SUBSDATAMOD IND

Format

Parameters

Flags

Valid States

New State

350 Version 1.1 Rel. 7.20141001


4.6.287 Note Subscriber Data Modified Response

MAP SUBSDATAMOD RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 351


4.6.288 Note Subscriber Data Modified Confirmation

MAP SUBSDATAMOD CON

Format

Parameters

Flags

Valid States

New State

352 Version 1.1 Rel. 7.20141001


4.6.289 Trace Subscriber Activity Request

MAP TRACESA REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 353


4.6.290 Trace Subscriber Activity Indication

MAP TRACESA IND

Format

Parameters

Flags

Valid States

New State

354 Version 1.1 Rel. 7.20141001


4.6.291 Trace Subscriber Activity Response

MAP TRACESA RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 355


4.6.292 Trace Subscriber Activity Confirmation

MAP TRACESA CON

Format

Parameters

Flags

Valid States

New State

356 Version 1.1 Rel. 7.20141001


4.6.293 Update GPRS Location Request

MAP UDGRPSLOC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 357


4.6.294 Update GPRS Location Indication

MAP UDGRPSLOC IND

Format

Parameters

Flags

Valid States

New State

358 Version 1.1 Rel. 7.20141001


4.6.295 Update GPRS Location Response

MAP UDGRPSLOC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 359


4.6.296 Update GPRS Location Confirmation

MAP UDGRPSLOC CON

Format

Parameters

Flags

Valid States

New State

360 Version 1.1 Rel. 7.20141001


4.6.297 Update Location Request

MAP UDLOC REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 361


4.6.298 Update Location Indication

MAP UDLOC IND

Format

Parameters

Flags

Valid States

New State

362 Version 1.1 Rel. 7.20141001


4.6.299 Update Location Response

MAP UDLOC RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 363


4.6.300 Update Location Confirmation

MAP UDLOC CON

Format

Parameters

Flags

Valid States

New State

364 Version 1.1 Rel. 7.20141001


4.6.301 Unstructured Supplementary Service Notify Request

MAP USSDNTFY REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 365


4.6.302 Unstructured Supplementary Service Notify Indication

MAP USSDNTFY IND

Format

Parameters

Flags

Valid States

New State

366 Version 1.1 Rel. 7.20141001


4.6.303 Unstructured Supplementary Service Notify Response

MAP USSDNTFY RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 367


4.6.304 Unstructured Supplementary Service Notify Confirmation

MAP USSDNTFY CON

Format

Parameters

Flags

Valid States

New State

368 Version 1.1 Rel. 7.20141001


4.6.305 Unstructured Supplementary Service Request

MAP USSDREQ REQ

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 369


4.6.306 Unstructured Supplementary Service Indication

MAP USSDREQ IND

Format

Parameters

Flags

Valid States

New State

370 Version 1.1 Rel. 7.20141001


4.6.307 Unstructured Supplementary Service Response

MAP USSDREQ RES

Format

Parameters

Flags

Valid States

New State

Acknowledgements






2014-10-25 371


4.6.308 Unstructured Supplementary Service Confirmation

MAP USSDREQ CON

Format

Parameters

Flags

Valid States

New State

372 Version 1.1 Rel. 7.20141001

Mobile Application Part Interface (MAPI) Diagnostics Requirements

5 Diagnostics Requirements

Two error handling facilities should be provided to the MAP service user: one to handle non-fatalerrors, and the other to handle fatal errors.

5.1 Non-Fatal Error Handling Facility

These are errors that do not change the state of the MAP service interface as seen by the MAPservice user and provide the user with the option of reissuing the MAP primitive with the correctedoptions specification. The non-fatal error handling is provided only to those primitives that requireacknowledgements, and uses the MAP_ERROR_ACK to report these errors. These errors retain the stateof the MAP service interface the same as it was before the MAP provider received the primitive thatwas in error. Syntax errors and rule violations are reported via the non-fatal error handling facility.

5.2 Fatal Error Handling Facility

These errors are issued by the MAP provider when it detects errors that are not correctable by theMAP user, or if it is unable to report a correctible error to the MAP service user. Fatal errorsare indicated via the STREAMS message type M_ERROR with the UNIX system error EPROTO. TheM_ERROR STREAMS message type will result in the failure of all the UNIX system calls on thestream. The MAP service user can recover from a fatal error by having all the processes close thefiles associated with the stream, and then reopening them for processing.

2014-10-25 373

Mobile Application Part Interface (MAPI) References

6 References

1. CCITT X.213, (Geneva, 1986), “Network Service Definition for Open Systems Interconnection(OSI) for CCITT Applications,” (Grey Book).

2. ISO 8348 — “Information Processing Systems — Data Communications — Newtork ServiceDefinition,” 4/15/87

3. ISO 8348/AD — “Information Processing Systems — Data Communications — Newtork Ser-vice Definition — Addendum 1: Connectionless Mode Transmission,” 4/15/87

4. ISO 8373 — “Information Processing Systems — Data Communicatoins Protocol for Providingthe Connectionless Mode Network Service,” SC6 N4542

5. ISO 8208 — “Information Processing Systems — X.25 Packet Level Protocol for Data TerminalEquipment,” 9/1/87

6. ISO 8878 — “Information Processing Systems — Data Communications — Use of X.25 toProvide the OSI Connection-Mode Network Service,” 9/1/87

7. System V Interface Definition, Issue 2 – Volume 3

8. CCITT X.210, (Geneva 1984), “Open Systems Interconnection (OSI) Layer Service DefinitionConventions,” (Red Book)

2014-10-25 375

Mobile Application Part Interface (MAPI) Addendum for 3GPP Conformance

Addendum for 3GPP Conformance

2014-10-25 377

Mobile Application Part Interface (MAPI) Mapping MAPI Primitives to 3GPP TS 29.002

Appendix A Mapping MAPI Primitives to 3GPP TS 29.002

Table A-1 shows the mapping of the MAPI primitives to the MAP service definition primitives listedin 3GPP TS 29.002 Release 6.6.0.

Table A-1. Mapping of MAPI Primitives to 3GPP TS 29.002

MAP Primitive 3GPP Service PrimitiveMAP_OPEN_REQ MAP-OPEN reqMAP_OPEN_IND MAP-OPEN indMAP_OPEN_RES MAP-OPEN rspMAP_OPEN_CON MAP-OPEN cnfMAP_CLOSE_REQ MAP-CLOSE reqMAP_CLOSE_IND MAP-CLOSE indMAP_DELIM_REQ MAP-DELIMITER reqMAP_DELIM_IND MAP-DELIMITER indMAP_ABORT_REQ MAP-U-ABORT reqMAP_UABORT_IND MAP-U-ABORT indMAP_PABORT_IND MAP-P-ABORT indMAP_NOTICE_IND MAP-NOTICE indMAP_STC1_REQ MAP-SECURE-TRANSPORT-CLASS-1 reqMAP_STC1_IND MAP-SECURE-TRANSPORT-CLASS-1 indMAP_STC2_REQ MAP-SECURE-TRANSPORT-CLASS-2 reqMAP_STC2_IND MAP-SECURE-TRANSPORT-CLASS-2 indMAP_STC3_REQ MAP-SECURE-TRANSPORT-CLASS-3 reqMAP_STC3_IND MAP-SECURE-TRANSPORT-CLASS-3 indMAP_STC4_REQ MAP-SECURE-TRANSPORT-CLASS-4 reqMAP_STC4_IND MAP-SECURE-TRANSPORT-CLASS-4 indMAP_ACTSS_REQ MAP-ACTIVATE-SS reqMAP_ACTSS_IND MAP-ACTIVATE-SS indMAP_ACTSS_RES MAP-ACTIVATE-SS rspMAP_ACTSS_CON MAP-ACTIVATE-SS cnfMAP_ACTTM_REQ MAP-ACTIVATE-TRACE-MODE reqMAP_ACTTM_IND MAP-ACTIVATE-TRACE-MODE indMAP_ACTTM_RES MAP-ACTIVATE-TRACE-MODE rspMAP_ACTTM_CON MAP-ACTIVATE-TRACE-MODE cnfMAP_ALERTSC_REQ MAP-ALERT-SERVICE-CENTRE reqMAP_ALERTSC_IND MAP-ALERT-SERVICE-CENTRE indMAP_ALERTSC_RES MAP-ALERT-SERVICE-CENTRE rspMAP_ALERTSC_CON MAP-ALERT-SERVICE-CENTRE cnfMAP_ALLOCHN_REQ MAP-ALLOCATE-HANDOVER-NUMBER reqMAP_ALLOCHN_IND MAP-ALLOCATE-HANDOVER-NUMBER indMAP_ALLOCHN_RES MAP-ALLOCATE-HANDOVER-NUMBER rspMAP_ALLOCHN_CON MAP-ALLOCATE-HANDOVER-NUMBER cnfMAP_ANYMOD_REQ MAP-ANY-TIME-MODIFICATION reqMAP_ANYMOD_IND MAP-ANY-TIME-MODIFICATION indMAP_ANYMOD_RES MAP-ANY-TIME-MODIFICATION rspMAP_ANYMOD_CON MAP-ANY-TIME-MODIFICATION cnfMAP_ANYQRY_REQ MAP-ANY-TIME-INTERROGATION reqMAP_ANYQRY_IND MAP-ANY-TIME-INTERROGATION indMAP_ANYQRY_RES MAP-ANY-TIME-INTERROGATION rsp

2014-10-25 379

Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002

MAP_ANYQRY_CON MAP-ANY-TIME-INTERROGATION cnfMAP_ANYSUB_REQ MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION reqMAP_ANYSUB_IND MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION indMAP_ANYSUB_RES MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION rspMAP_ANYSUB_CON MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION cnfMAP_AUTH_REQ MAP-AUTHENTICATE reqMAP_AUTH_IND MAP-AUTHENTICATE indMAP_AUTH_RES MAP-AUTHENTICATE rspMAP_AUTH_CON MAP-AUTHENTICATE cnfMAP_AUTHFAIL_REQ MAP-AUTHENTICATION-FAILURE-REPORT reqMAP_AUTHFAIL_IND MAP-AUTHENTICATION-FAILURE-REPORT indMAP_AUTHFAIL_RES MAP-AUTHENTICATION-FAILURE-REPORT rspMAP_AUTHFAIL_CON MAP-AUTHENTICATION-FAILURE-REPORT cnfMAP_CANCLOC_REQ MAP-CANCEL-LOCATION reqMAP_CANCLOC_IND MAP-CANCEL-LOCATION indMAP_CANCLOC_RES MAP-CANCEL-LOCATION rspMAP_CANCLOC_CON MAP-CANCEL-LOCATION cnfMAP_CKIEMI_REQ MAP-CHECK-IEMI reqMAP_CKIEMI_IND MAP-CHECK-IEMI indMAP_CKIEMI_RES MAP-CHECK-IEMI rspMAP_CKIEMI_CON MAP-CHECK-IEMI cnfMAP_DEACTSS_REQ MAP-DEACTIVATE-SS reqMAP_DEACTSS_IND MAP-DEACTIVATE-SS indMAP_DEACTSS_RES MAP-DEACTIVATE-SS rspMAP_DEACTSS_CON MAP-DEACTIVATE-SS cnfMAP_DEACTTM_REQ MAP-DEACTIVATE-TRACE-MODE reqMAP_DEACTTM_IND MAP-DEACTIVATE-TRACE-MODE indMAP_DEACTTM_RES MAP-DEACTIVATE-TRACE-MODE rspMAP_DEACTTM_CON MAP-DEACTIVATE-TRACE-MODE cnfMAP_DELSUBD_REQ MAP-DELETE-SUBSCRIBER-DATA reqMAP_DELSUBD_IND MAP-DELETE-SUBSCRIBER-DATA indMAP_DELSUBD_RES MAP-DELETE-SUBSCRIBER-DATA rspMAP_DELSUBD_CON MAP-DELETE-SUBSCRIBER-DATA cnfMAP_ERASECC_REQ MAP-ERASE-CC-ENTRY reqMAP_ERASECC_IND MAP-ERASE-CC-ENTRY indMAP_ERASECC_RES MAP-ERASE-CC-ENTRY rspMAP_ERASECC_CON MAP-ERASE-CC-ENTRY cnfMAP_ERASESS_REQ MAP-ERASE-SS reqMAP_ERASESS_IND MAP-ERASE-SS indMAP_ERASESS_RES MAP-ERASE-SS rspMAP_ERASESS_CON MAP-ERASE-SS cnfMAP_FAILURE_REQ MAP-FAILURE-REPORT reqMAP_FAILURE_IND MAP-FAILURE-REPORT indMAP_FAILURE_RES MAP-FAILURE-REPORT rspMAP_FAILURE_CON MAP-FAILURE-REPORT cnfMAP_FAS_REQ MAP-FORWARD-ACCESS-SIGNALLING reqMAP_FAS_IND MAP-FORWARD-ACCESS-SIGNALLING indMAP_FAS_RES MAP-FORWARD-ACCESS-SIGNALLING rspMAP_FAS_CON MAP-FORWARD-ACCESS-SIGNALLING cnf

380 Version 1.1 Rel. 7.20141001


MAP_FCKSSIND_REQ MAP-FORWARD-CHECK-SS-INDICATION reqMAP_FCKSSIND_IND MAP-FORWARD-CHECK-SS-INDICATION indMAP_FCKSSIND_RES MAP-FORWARD-CHECK-SS-INDICATION rspMAP_FCKSSIND_CON MAP-FORWARD-CHECK-SS-INDICATION cnfMAP_FGRCSIG_REQ MAP-FORWARD-GROUP-CALL-SIGNALLING reqMAP_FGRCSIG_IND MAP-FORWARD-GROUP-CALL-SIGNALLING indMAP_FGRCSIG_RES MAP-FORWARD-GROUP-CALL-SIGNALLING rspMAP_FGRCSIG_CON MAP-FORWARD-GROUP-CALL-SIGNALLING cnfMAP_FNEWIMSI_REQ MAP-FORWARD-NEW-IMSI reqMAP_FNEWIMSI_IND MAP-FORWARD-NEW-IMSI indMAP_FNEWIMSI_RES MAP-FORWARD-NEW-IMSI rspMAP_FNEWIMSI_CON MAP-FORWARD-NEW-IMSI cnfMAP_GETIEMI_REQ MAP-OBTAIN-IEMI reqMAP_GETIEMI_IND MAP-OBTAIN-IEMI indMAP_GETIEMI_RES MAP-OBTAIN-IEMI rspMAP_GETIEMI_CON MAP-OBTAIN-IEMI cnfMAP_GETPASS_REQ MAP-GET-PASSWORD reqMAP_GETPASS_IND MAP-GET-PASSWORD indMAP_GETPASS_RES MAP-GET-PASSWORD rspMAP_GETPASS_CON MAP-GET-PASSWORD cnfMAP_INFORMSC_REQ MAP-INFORM-SERVICE-CENTER reqMAP_INFORMSC_IND MAP-INFORM-SERVICE-CENTER indMAP_INFORMSC_RES MAP-INFORM-SERVICE-CENTER rspMAP_INFORMSC_CON MAP-INFORM-SERVICE-CENTER cnfMAP_INSSUBSD_REQ MAP-INSERT-SUBSCRIBER-DATA reqMAP_INSSUBSD_IND MAP-INSERT-SUBSCRIBER-DATA indMAP_INSSUBSD_RES MAP-INSERT-SUBSCRIBER-DATA rspMAP_INSSUBSD_CON MAP-INSERT-SUBSCRIBER-DATA cnfMAP_INTERGSS_REQ MAP-INTERROGATE-SS reqMAP_INTERGSS_IND MAP-INTERROGATE-SS indMAP_INTERGSS_RES MAP-INTERROGATE-SS rspMAP_INTERGSS_CON MAP-INTERROGATE-SS cnfMAP_ISTALERT_REQ MAP-IST-ALERT reqMAP_ISTALERT_IND MAP-IST-ALERT indMAP_ISTALERT_RES MAP-IST-ALERT rspMAP_ISTALERT_CON MAP-IST-ALERT cnfMAP_ISTCMD_REQ MAP-IST-COMMAND reqMAP_ISTCMD_IND MAP-IST-COMMAND indMAP_ISTCMD_RES MAP-IST-COMMAND rspMAP_ISTCMD_CON MAP-IST-COMMAND cnfMAP_MMEVENT_REQ MAP-NOTE-MM-EVENT reqMAP_MMEVENT_IND MAP-NOTE-MM-EVENT indMAP_MMEVENT_RES MAP-NOTE-MM-EVENT rspMAP_MMEVENT_CON MAP-NOTE-MM-EVENT cnfMAP_MOFSMS_REQ MAP-MO-FORWARD-SHORT-MESSAGE reqMAP_MOFSMS_IND MAP-MO-FORWARD-SHORT-MESSAGE indMAP_MOFSMS_RES MAP-MO-FORWARD-SHORT-MESSAGE rspMAP_MOFSMS_CON MAP-MO-FORWARD-SHORT-MESSAGE cnfMAP_MSGRPSPRES_REQ MAP-NOTE-MS-PRESENT-FOR-GPRS req

2014-10-25 381


MAP_MSGRPSPRES_IND MAP-NOTE-MS-PRESENT-FOR-GPRS indMAP_MSGRPSPRES_RES MAP-NOTE-MS-PRESENT-FOR-GPRS rspMAP_MSGRPSPRES_CON MAP-NOTE-MS-PRESENT-FOR-GPRS cnfMAP_MTFSMS_REQ MAP-MT-FORWARD-SHORT-MESSAGE reqMAP_MTFSMS_IND MAP-MT-FORWARD-SHORT-MESSAGE indMAP_MTFSMS_RES MAP-MT-FORWARD-SHORT-MESSAGE rspMAP_MTFSMS_CON MAP-MT-FORWARD-SHORT-MESSAGE cnfMAP_PAGE_REQ MAP-PAGE reqMAP_PAGE_IND MAP-PAGE indMAP_PAGE_RES MAP-PAGE rspMAP_PAGE_CON MAP-PAGE cnfMAP_PREPGC_REQ MAP-PREPARE-GROUP-CALL reqMAP_PREPGC_IND MAP-PREPARE-GROUP-CALL indMAP_PREPGC_RES MAP-PREPARE-GROUP-CALL rspMAP_PREPGC_CON MAP-PREPARE-GROUP-CALL cnfMAP_PREPHO_REQ MAP-PREPARE-HANDOVER reqMAP_PREPHO_IND MAP-PREPARE-HANDOVER indMAP_PREPHO_RES MAP-PREPARE-HANDOVER rspMAP_PREPHO_CON MAP-PREPARE-HANDOVER cnfMAP_PREPSH_REQ MAP-PREPARE-SUBSEQUENT-HANDOVER reqMAP_PREPSH_IND MAP-PREPARE-SUBSEQUENT-HANDOVER indMAP_PREPSH_RES MAP-PREPARE-SUBSEQUENT-HANDOVER rspMAP_PREPSH_CON MAP-PREPARE-SUBSEQUENT-HANDOVER cnfMAP_PROCAS_REQ MAP-PROCESS-ACCESS-SIGNALLING reqMAP_PROCAS_IND MAP-PROCESS-ACCESS-SIGNALLING indMAP_PROCAS_RES MAP-PROCESS-ACCESS-SIGNALLING rspMAP_PROCAS_CON MAP-PROCESS-ACCESS-SIGNALLING cnfMAP_PROCGC_REQ MAP-PROCESS-GROUP-CALL-SIGNALLING reqMAP_PROCGC_IND MAP-PROCESS-GROUP-CALL-SIGNALLING indMAP_PROCGC_RES MAP-PROCESS-GROUP-CALL-SIGNALLING rspMAP_PROCGC_CON MAP-PROCESS-GROUP-CALL-SIGNALLING cnfMAP_PROCUSS_REQ MAP-PROCESS-UNSTRUCTURED-SS-REQUEST reqMAP_PROCUSS_IND MAP-PROCESS-UNSTRUCTURED-SS-REQUEST indMAP_PROCUSS_RES MAP-PROCESS-UNSTRUCTURED-SS-REQUEST rspMAP_PROCUSS_CON MAP-PROCESS-UNSTRUCTURED-SS-REQUEST cnfMAP_PROVIMSI_REQ MAP-PROVIDE-IMSI reqMAP_PROVIMSI_IND MAP-PROVIDE-IMSI indMAP_PROVIMSI_RES MAP-PROVIDE-IMSI rspMAP_PROVIMSI_CON MAP-PROVIDE-IMSI cnfMAP_PROVRN_REQ MAP-PROVIDE-ROAMING-NUMBER reqMAP_PROVRN_IND MAP-PROVIDE-ROAMING-NUMBER indMAP_PROVRN_RES MAP-PROVIDE-ROAMING-NUMBER rspMAP_PROVRN_CON MAP-PROVIDE-ROAMING-NUMBER cnfMAP_PROVSLOC_REQ MAP-PROVIDE-SUBSCRIBER-LOCATION reqMAP_PROVSLOC_IND MAP-PROVIDE-SUBSCRIBER-LOCATION indMAP_PROVSLOC_RES MAP-PROVIDE-SUBSCRIBER-LOCATION rspMAP_PROVSLOC_CON MAP-PROVIDE-SUBSCRIBER-LOCATION cnfMAP_PROVSUBI_REQ MAP-PROVIDE-SUBSCRIBER-INFO reqMAP_PROVSUBI_IND MAP-PROVIDE-SUBSCRIBER-INFO ind

382 Version 1.1 Rel. 7.20141001


MAP_PROVSUBI_RES MAP-PROVIDE-SUBSCRIBER-INFO rspMAP_PROVSUBI_CON MAP-PROVIDE-SUBSCRIBER-INFO cnfMAP_PURGEMS_REQ MAP-PURGE-MS reqMAP_PURGEMS_IND MAP-PURGE-MS indMAP_PURGEMS_RES MAP-PURGE-MS rspMAP_PURGEMS_CON MAP-PURGE-MS cnfMAP_RDYSM_REQ MAP-READY-FOR-SM reqMAP_RDYSM_IND MAP-READY-FOR-SM indMAP_RDYSM_RES MAP-READY-FOR-SM rspMAP_RDYSM_CON MAP-READY-FOR-SM cnfMAP_REGCC_REQ MAP-REGISTER-CC-ENTRY reqMAP_REGCC_IND MAP-REGISTER-CC-ENTRY indMAP_REGCC_RES MAP-REGISTER-CC-ENTRY rspMAP_REGCC_CON MAP-REGISTER-CC-ENTRY cnfMAP_REGPW_REQ MAP-REGISTER-PASSWORD reqMAP_REGPW_IND MAP-REGISTER-PASSWORD indMAP_REGPW_RES MAP-REGISTER-PASSWORD rspMAP_REGPW_CON MAP-REGISTER-PASSWORD cnfMAP_REGSS_REQ MAP-REGISTER-SS reqMAP_REGSS_IND MAP-REGISTER-SS indMAP_REGSS_RES MAP-REGISTER-SS rspMAP_REGSS_CON MAP-REGISTER-SS cnfMAP_REMUSRFREE_REQ MAP-REMOTE-USER-FREE reqMAP_REMUSRFREE_IND MAP-REMOTE-USER-FREE indMAP_REMUSRFREE_RES MAP-REMOTE-USER-FREE rspMAP_REMUSRFREE_CON MAP-REMOTE-USER-FREE cnfMAP_RESET_REQ MAP-RESET reqMAP_RESET_IND MAP-RESET indMAP_RESET_RES MAP-RESET rspMAP_RESET_CON MAP-RESET cnfMAP_RESTORE_REQ MAP-RESTORE-DATA reqMAP_RESTORE_IND MAP-RESTORE-DATA indMAP_RESTORE_RES MAP-RESTORE-DATA rspMAP_RESTORE_CON MAP-RESTORE-DATA cnfMAP_RESUME_REQ MAP-RESUME-CALL-HANDLING reqMAP_RESUME_IND MAP-RESUME-CALL-HANDLING indMAP_RESUME_RES MAP-RESUME-CALL-HANDLING rspMAP_RESUME_CON MAP-RESUME-CALL-HANDLING cnfMAP_SEARCH_REQ MAP-SEARCH-FOR-MS reqMAP_SEARCH_IND MAP-SEARCH-FOR-MS indMAP_SEARCH_RES MAP-SEARCH-FOR-MS rspMAP_SEARCH_CON MAP-SEARCH-FOR-MS cnfMAP_SENDAUTHI_REQ MAP-SEND-AUTHENTICATION-INFO reqMAP_SENDAUTHI_IND MAP-SEND-AUTHENTICATION-INFO indMAP_SENDAUTHI_RES MAP-SEND-AUTHENTICATION-INFO rspMAP_SENDAUTHI_CON MAP-SEND-AUTHENTICATION-INFO cnfMAP_SENDEND_REQ MAP-SEND-END-SIGNAL reqMAP_SENDEND_IND MAP-SEND-END-SIGNAL indMAP_SENDEND_RES MAP-SEND-END-SIGNAL rsp

2014-10-25 383


MAP_SENDEND_CON MAP-SEND-END-SIGNAL cnfMAP_SENDGCEND_REQ MAP-SEND-GROUP-CALL-END-SIGNAL reqMAP_SENDGCEND_IND MAP-SEND-GROUP-CALL-END-SIGNAL indMAP_SENDGCEND_RES MAP-SEND-GROUP-CALL-END-SIGNAL rspMAP_SENDGCEND_CON MAP-SEND-GROUP-CALL-END-SIGNAL cnfMAP_SENDGPRSRI_REQ MAP-SEND-ROUTING-INFO-FOR-GPRS reqMAP_SENDGPRSRI_IND MAP-SEND-ROUTING-INFO-FOR-GPRS indMAP_SENDGPRSRI_RES MAP-SEND-ROUTING-INFO-FOR-GPRS rspMAP_SENDGPRSRI_CON MAP-SEND-ROUTING-INFO-FOR-GPRS cnfMAP_SENDHOREP_REQ MAP-SEND-HANDOVER-REPORT reqMAP_SENDHOREP_IND MAP-SEND-HANDOVER-REPORT indMAP_SENDHOREP_RES MAP-SEND-HANDOVER-REPORT rspMAP_SENDHOREP_CON MAP-SEND-HANDOVER-REPORT cnfMAP_SENDID_REQ MAP-SEND-IDENTIFICATION reqMAP_SENDID_IND MAP-SEND-IDENTIFICATION indMAP_SENDID_RES MAP-SEND-IDENTIFICATION rspMAP_SENDID_CON MAP-SEND-IDENTIFICATION cnfMAP_SENDIMSI_REQ MAP-SEND-IMSI reqMAP_SENDIMSI_IND MAP-SEND-IMSI indMAP_SENDIMSI_RES MAP-SEND-IMSI rspMAP_SENDIMSI_CON MAP-SEND-IMSI cnfMAP_SENDLCSRI_REQ MAP-SEND-ROUTING-INFO-FOR-LCS reqMAP_SENDLCSRI_IND MAP-SEND-ROUTING-INFO-FOR-LCS indMAP_SENDLCSRI_RES MAP-SEND-ROUTING-INFO-FOR-LCS rspMAP_SENDLCSRI_CON MAP-SEND-ROUTING-INFO-FOR-LCS cnfMAP_SENDMOSMSI_REQ MAP-SEND-INFO-FOR-MO-SMS reqMAP_SENDMOSMSI_IND MAP-SEND-INFO-FOR-MO-SMS indMAP_SENDMOSMSI_RES MAP-SEND-INFO-FOR-MO-SMS rspMAP_SENDMOSMSI_CON MAP-SEND-INFO-FOR-MO-SMS cnfMAP_SENDMTSMSI_REQ MAP-SEND-INFO-FOR-MT-SMS reqMAP_SENDMTSMSI_IND MAP-SEND-INFO-FOR-MT-SMS indMAP_SENDMTSMSI_RES MAP-SEND-INFO-FOR-MT-SMS rspMAP_SENDMTSMSI_CON MAP-SEND-INFO-FOR-MT-SMS cnfMAP_SENDRI_REQ MAP-SEND-ROUTING-INFORMATION reqMAP_SENDRI_IND MAP-SEND-ROUTING-INFORMATION indMAP_SENDRI_RES MAP-SEND-ROUTING-INFORMATION rspMAP_SENDRI_CON MAP-SEND-ROUTING-INFORMATION cnfMAP_SENDSMSRI_REQ MAP-SEND-ROUTING-INFO-FOR-SM reqMAP_SENDSMSRI_IND MAP-SEND-ROUTING-INFO-FOR-SM indMAP_SENDSMSRI_RES MAP-SEND-ROUTING-INFO-FOR-SM rspMAP_SENDSMSRI_CON MAP-SEND-ROUTING-INFO-FOR-SM cnfMAP_SETCM_REQ MAP-SET-CIPHERING-MODE reqMAP_SETCM_IND MAP-SET-CIPHERING-MODE indMAP_SETCM_RES MAP-SET-CIPHERING-MODE rspMAP_SETCM_CON MAP-SET-CIPHERING-MODE cnfMAP_SETREP_REQ MAP-SET-REPORTING-STATE reqMAP_SETREP_IND MAP-SET-REPORTING-STATE indMAP_SETREP_RES MAP-SET-REPORTING-STATE rspMAP_SETREP_CON MAP-SET-REPORTING-STATE cnf

384 Version 1.1 Rel. 7.20141001


MAP_SMDELIVSTAT_REQ MAP-REPORT-SM-DELIVER-STATUS reqMAP_SMDELIVSTAT_IND MAP-REPORT-SM-DELIVER-STATUS indMAP_SMDELIVSTAT_RES MAP-REPORT-SM-DELIVER-STATUS rspMAP_SMDELIVSTAT_CON MAP-REPORT-SM-DELIVER-STATUS cnfMAP_SSINV_REQ MAP-SS-INVOCATION-NOTIFICATION reqMAP_SSINV_IND MAP-SS-INVOCATION-NOTIFICATION indMAP_SSINV_RES MAP-SS-INVOCATION-NOTIFICATION rspMAP_SSINV_CON MAP-SS-INVOCATION-NOTIFICATION cnfMAP_STATUS_REQ MAP-STATUS-REPORT reqMAP_STATUS_IND MAP-STATUS-REPORT indMAP_STATUS_RES MAP-STATUS-REPORT rspMAP_STATUS_CON MAP-STATUS-REPORT cnfMAP_SUBLOCREP_REQ MAP-SUBSCRIBER-LOCATION-REPORT reqMAP_SUBLOCREP_IND MAP-SUBSCRIBER-LOCATION-REPORT indMAP_SUBLOCREP_RES MAP-SUBSCRIBER-LOCATION-REPORT rspMAP_SUBLOCREP_CON MAP-SUBSCRIBER-LOCATION-REPORT cnfMAP_SUBSDATAMOD_REQ MAP-NOTE-SUBSCRIBER-DATA-MODIFIED reqMAP_SUBSDATAMOD_IND MAP-NOTE-SUBSCRIBER-DATA-MODIFIED indMAP_SUBSDATAMOD_RES MAP-NOTE-SUBSCRIBER-DATA-MODIFIED rspMAP_SUBSDATAMOD_CON MAP-NOTE-SUBSCRIBER-DATA-MODIFIED cnfMAP_TRACESA_REQ MAP-TRACE-SUBSCRIBER-ACTIVITY reqMAP_TRACESA_IND MAP-TRACE-SUBSCRIBER-ACTIVITY indMAP_TRACESA_RES MAP-TRACE-SUBSCRIBER-ACTIVITY rspMAP_TRACESA_CON MAP-TRACE-SUBSCRIBER-ACTIVITY cnfMAP_UDGRPSLOC_REQ MAP-UPDATE-GPRS-LOCATION reqMAP_UDGRPSLOC_IND MAP-UPDATE-GPRS-LOCATION indMAP_UDGRPSLOC_RES MAP-UPDATE-GPRS-LOCATION rspMAP_UDGRPSLOC_CON MAP-UPDATE-GPRS-LOCATION cnfMAP_UDLOC_REQ MAP-UPDATE-LOCATION reqMAP_UDLOC_IND MAP-UPDATE-LOCATION indMAP_UDLOC_RES MAP-UPDATE-LOCATION rspMAP_UDLOC_CON MAP-UPDATE-LOCATION cnfMAP_USSDNTFY_REQ MAP-UNSTRUCTURED-SS-NOTIFY reqMAP_USSDNTFY_IND MAP-UNSTRUCTURED-SS-NOTIFY indMAP_USSDNTFY_RES MAP-UNSTRUCTURED-SS-NOTIFY rspMAP_USSDNTFY_CON MAP-UNSTRUCTURED-SS-NOTIFY cnfMAP_USSDREQ_REQ MAP-UNSTRUCTURED-SS-REQUEST reqMAP_USSDREQ_IND MAP-UNSTRUCTURED-SS-REQUEST indMAP_USSDREQ_RES MAP-UNSTRUCTURED-SS-REQUEST rspMAP_USSDREQ_CON MAP-UNSTRUCTURED-SS-REQUEST cnf

A.1 Application Contexts

Table 1. Application Contexts

Ver. Application Contexts Operationsv3 locationCancellationContext cancelLocationv3 equipmentMngtContext checkIEMI

2014-10-25 385


v2 imsiRetrievalContext sendIMSIv3 infoRetrievalContext sendAuthenticationInfov3 interVlrInfoRetrievalContext sendIdentificationv3 handoverControlContext prepareHandover,

forwareAccessSignalling,sendEndSignal,processAccessSignalling,prepareSubsequentHandover

v3 mwdMngtContext readyForSMv3 msPurgingContext purgeMSv2 shortMsgAlertContext alertServiceCentrev2 resetContext resetv2 networkUnstructuredSsContext processUnstructuredSS-Request,

unstructuredSS-Request,unstructuredSS-Notify

v3 tracingContext activateTraceMode,deactivateTraceMode

v2 networkFunctionalSsContext registerSS,eraseSS,activateSS,deactivateSS,registerPassword,interrogateSS,getPassword

v3 shortMsgMO-RelayContext mo-forwardSMv3 shortMsgMT-RelayContext mt-forwardSMv3 shortMsgGatewayContext sendRoutingInfoForSM,

reportSM-DeliveryStatus,InformServiceCentre

v3 networkLocUpContext updateLocation,forwardCheckSs-Indication,restoreData,insertSubscriberData,activateTraceMode

v3 gprsLocationUpdateContext updateGprsLocation,insertSubscriberData,activateTraceMode

v3 subscriberDataMngtContext insertSubscriberData,deleteSubscriberData

v3 roamingNumberEnquiryContext provideRoamingNumberv3 locationInfoRetrievalContext sendRoutingInfov3 gprsNotifyContext noteMsPresentForGprsv4 gprsLocationInfoRetrievalContext sendRoutingInfoForGprsv3 failureReportContext failureReportv4 callControlTransferContext resumeCallHandlingv3 susbcriberInfoEnquiryContext provideSubscriberInfov3 anyTimeEnquiryContext anyTimeInterrogation

386 Version 1.1 Rel. 7.20141001


v3 anyTimeInfoHandlingContext anyTimeSubscriptionInterrogation,anyTimeModification

v3 ss-InvocationNotificationContext ss-InvocationNotificationv3 groupCallControlContext prepareGroupCall,

processGroupCallSignalling,forwardGroupCallSignalling,sendGroupCallEndSignal

v3 reportingContext setReportingState,statusReport,remoteUserFree

v3 callCompletionContext registerCC-Entry,eraceCC-Entry

v3 isAlertingContext isAlertv3 ServiceTerminationContext istCommandv3 locationSvcEnquiryContext provideSubscriberLocation,

subscriberLocationReport

v3 locationSvcGatewayContext sendRoutingInfoForLCSv3 mm-EventReportingContext noteMM-Eventv3 subscriberDataModificationNotificationContext noteSubscriberDataModifiedv3 authenticationFailureReportContext authenticationFailureReportv3 secureTransportHandlingContext secureTransportClass1,

secureTransportClass2,secureTransportClass3,secureTransportClass4

2014-10-25 387

Mobile Application Part Interface (MAPI) State/Event Tables

Appendix B State/Event Tables

2014-10-25 389

Mobile Application Part Interface (MAPI) Primitive Precedence Tables

Appendix C Primitive Precedence Tables

2014-10-25 391

Mobile Application Part Interface (MAPI) MAPI Header File Listing

Appendix D MAPI Header File Listing

2014-10-25 393

Mobile Application Part Interface (MAPI) Licenses

Licenses

All code presented in this manual is licensed under the [GNU Affero General Public License],page 395. The text of this manual is licensed under the [GNU Free Documentation License], page 405,with no invariant sections, no front-cover texts and no back-cover texts. Please note, however, thatit is just plain wrong to modify statements of, or attribute statements to, the Author or OpenSS7Corporation.

GNU Affero General Public License

The GNU Affero General Public License.Version 3, 19 November 2007

Copyright c© 2007 Free Software Foundation, Inc. http://fsf.org/

Everyone is permitted to copy and distribute verbatim copies of thislicense document, but changing it is not allowed.

Preamble

The GNU Affero General Public License is a free, copyleft license for software and other kinds ofworks, specifically designed to ensure cooperation with the community in the case of network serversoftware.

The licenses for most software and other practical works are designed to take away your freedomto share and change the works. By contrast, our General Public Licenses are intended to guaranteeyour freedom to share and change all versions of a program–to make sure it remains free softwarefor all its users.

When we speak of free software, we are referring to freedom, not price. Our General Public Licensesare designed to make sure that you have the freedom to distribute copies of free software (and chargefor them if you wish), that you receive source code or can get it if you want it, that you can changethe software or use pieces of it in new free programs, and that you know you can do these things.

Developers that use our General Public Licenses protect your rights with two steps: (1) assertcopyright on the software, and (2) offer you this License which gives you legal permission to copy,distribute and/or modify the software.

A secondary benefit of defending all users’ freedom is that improvements made in alternate versionsof the program, if they receive widespread use, become available for other developers to incorpo-rate. Many developers of free software are heartened and encouraged by the resulting cooperation.However, in the case of software used on network servers, this result may fail to come about. TheGNU General Public License permits making a modified version and letting the public access it ona server without ever releasing its source code to the public.

The GNU Affero General Public License is designed specifically to ensure that, in such cases, themodified source code becomes available to the community. It requires the operator of a networkserver to provide the source code of the modified version running there to the users of that server.Therefore, public use of a modified version, on a publicly accessible server, gives the public accessto the source code of the modified version.

An older license, called the Affero General Public License and published by Affero, was designed toaccomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero hasreleased a new version of the Affero GPL which permits relicensing under this license.

The precise terms and conditions for copying, distribution and modification follow.

2014-10-25 395

http://fsf.org/

Licenses texi/agpl3.texi

Terms and Conditions

0. Definitions.

“This License” refers to version 3 of the GNU Affero General Public License.

“Copyright” also means copyright-like laws that apply to other kinds of works, such as semi-conductor masks.

“The Program” refers to any copyrightable work licensed under this License. Each licensee isaddressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

To “modify” a work means to copy from or adapt all or part of the work in a fashion requiringcopyright permission, other than the making of an exact copy. The resulting work is called a“modified version” of the earlier work or a work “based on” the earlier work.

A “covered work” means either the unmodified Program or a work based on the Program.

To “propagate” a work means to do anything with it that, without permission, would make youdirectly or secondarily liable for infringement under applicable copyright law, except executingit on a computer or modifying a private copy. Propagation includes copying, distribution (withor without modification), making available to the public, and in some countries other activitiesas well.

To “convey” a work means any kind of propagation that enables other parties to make or receivecopies. Mere interaction with a user through a computer network, with no transfer of a copy,is not conveying.

An interactive user interface displays “Appropriate Legal Notices” to the extent that it includesa convenient and prominently visible feature that (1) displays an appropriate copyright notice,and (2) tells the user that there is no warranty for the work (except to the extent that warrantiesare provided), that licensees may convey the work under this License, and how to view a copyof this License. If the interface presents a list of user commands or options, such as a menu, aprominent item in the list meets this criterion.

1. Source Code.

The “source code” for a work means the preferred form of the work for making modificationsto it. “Object code” means any non-source form of a work.

A “Standard Interface” means an interface that either is an official standard defined by arecognized standards body, or, in the case of interfaces specified for a particular programminglanguage, one that is widely used among developers working in that language.

The “System Libraries” of an executable work include anything, other than the work as awhole, that (a) is included in the normal form of packaging a Major Component, but whichis not part of that Major Component, and (b) serves only to enable use of the work withthat Major Component, or to implement a Standard Interface for which an implementation isavailable to the public in source code form. A “Major Component”, in this context, means amajor essential component (kernel, window system, and so on) of the specific operating system(if any) on which the executable work runs, or a compiler used to produce the work, or anobject code interpreter used to run it.

The “Corresponding Source” for a work in object code form means all the source code neededto generate, install, and (for an executable work) run the object code and to modify the work,including scripts to control those activities. However, it does not include the work’s System Li-braries, or general-purpose tools or generally available free programs which are used unmodifiedin performing those activities but which are not part of the work. For example, Correspond-ing Source includes interface definition files associated with source files for the work, and the

396 Version 1.1 Rel. 7.20141001


source code for shared libraries and dynamically linked subprograms that the work is specif-ically designed to require, such as by intimate data communication or control flow betweenthose subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automaticallyfrom other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

2. Basic Permissions.

All rights granted under this License are granted for the term of copyright on the Program,and are irrevocable provided the stated conditions are met. This License explicitly affirms yourunlimited permission to run the unmodified Program. The output from running a covered workis covered by this License only if the output, given its content, constitutes a covered work. ThisLicense acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditionsso long as your license otherwise remains in force. You may convey covered works to others forthe sole purpose of having them make modifications exclusively for you, or provide you withfacilities for running those works, provided that you comply with the terms of this License inconveying all material for which you do not control copyright. Those thus making or runningthe covered works for you must do so exclusively on your behalf, under your direction andcontrol, on terms that prohibit them from making any copies of your copyrighted materialoutside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below.Sublicensing is not allowed; section 10 makes it unnecessary.

3. Protecting Users’ Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any applicablelaw fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of tech-nological measures to the extent such circumvention is effected by exercising rights under thisLicense with respect to the covered work, and you disclaim any intention to limit operationor modification of the work as a means of enforcing, against the work’s users, your or thirdparties’ legal rights to forbid circumvention of technological measures.

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program’s source code as you receive it, in any medium,provided that you conspicuously and appropriately publish on each copy an appropriate copy-right notice; keep intact all notices stating that this License and any non-permissive termsadded in accord with section 7 apply to the code; keep intact all notices of the absence of anywarranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer supportor warranty protection for a fee.

5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from theProgram, in the form of source code under the terms of section 4, provided that you also meetall of these conditions:

a. The work must carry prominent notices stating that you modified it, and giving a relevantdate.

2014-10-25 397


b. The work must carry prominent notices stating that it is released under this Licenseand any conditions added under section 7. This requirement modifies the requirement insection 4 to “keep intact all notices”.

c. You must license the entire work, as a whole, under this License to anyone who comes intopossession of a copy. This License will therefore apply, along with any applicable section7 additional terms, to the whole of the work, and all its parts, regardless of how they arepackaged. This License gives no permission to license the work in any other way, but itdoes not invalidate such permission if you have separately received it.

d. If the work has interactive user interfaces, each must display Appropriate Legal Notices;however, if the Program has interactive interfaces that do not display Appropriate LegalNotices, your work need not make them do so.

A compilation of a covered work with other separate and independent works, which are notby their nature extensions of the covered work, and which are not combined with it such asto form a larger program, in or on a volume of a storage or distribution medium, is called an“aggregate” if the compilation and its resulting copyright are not used to limit the access orlegal rights of the compilation’s users beyond what the individual works permit. Inclusion ofa covered work in an aggregate does not cause this License to apply to the other parts of theaggregate.

6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5,provided that you also convey the machine-readable Corresponding Source under the terms ofthis License, in one of these ways:

a. Convey the object code in, or embodied in, a physical product (including a physical dis-tribution medium), accompanied by the Corresponding Source fixed on a durable physicalmedium customarily used for software interchange.

b. Convey the object code in, or embodied in, a physical product (including a physical dis-tribution medium), accompanied by a written offer, valid for at least three years and validfor as long as you offer spare parts or customer support for that product model, to giveanyone who possesses the object code either (1) a copy of the Corresponding Source for allthe software in the product that is covered by this License, on a durable physical mediumcustomarily used for software interchange, for a price no more than your reasonable costof physically performing this conveying of source, or (2) access to copy the CorrespondingSource from a network server at no charge.

c. Convey individual copies of the object code with a copy of the written offer to provide theCorresponding Source. This alternative is allowed only occasionally and noncommercially,and only if you received the object code with such an offer, in accord with subsection 6b.

d. Convey the object code by offering access from a designated place (gratis or for a charge),and offer equivalent access to the Corresponding Source in the same way through the sameplace at no further charge. You need not require recipients to copy the CorrespondingSource along with the object code. If the place to copy the object code is a networkserver, the Corresponding Source may be on a different server (operated by you or a thirdparty) that supports equivalent copying facilities, provided you maintain clear directionsnext to the object code saying where to find the Corresponding Source. Regardless of whatserver hosts the Corresponding Source, you remain obligated to ensure that it is availablefor as long as needed to satisfy these requirements.

e. Convey the object code using peer-to-peer transmission, provided you inform other peers

398 Version 1.1 Rel. 7.20141001


where the object code and Corresponding Source of the work are being offered to thegeneral public at no charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the CorrespondingSource as a System Library, need not be included in conveying the object code work.

A “User Product” is either (1) a “consumer product”, which means any tangible personalproperty which is normally used for personal, family, or household purposes, or (2) anythingdesigned or sold for incorporation into a dwelling. In determining whether a product is aconsumer product, doubtful cases shall be resolved in favor of coverage. For a particularproduct received by a particular user, “normally used” refers to a typical or common use ofthat class of product, regardless of the status of the particular user or of the way in which theparticular user actually uses, or expects or is expected to use, the product. A product is aconsumer product regardless of whether the product has substantial commercial, industrial ornon-consumer uses, unless such uses represent the only significant mode of use of the product.

“Installation Information” for a User Product means any methods, procedures, authorizationkeys, or other information required to install and execute modified versions of a covered workin that User Product from a modified version of its Corresponding Source. The informationmust suffice to ensure that the continued functioning of the modified object code is in no caseprevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, aUser Product, and the conveying occurs as part of a transaction in which the right of possessionand use of the User Product is transferred to the recipient in perpetuity or for a fixed term(regardless of how the transaction is characterized), the Corresponding Source conveyed underthis section must be accompanied by the Installation Information. But this requirement doesnot apply if neither you nor any third party retains the ability to install modified object codeon the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continueto provide support service, warranty, or updates for a work that has been modified or installedby the recipient, or for the User Product in which it has been modified or installed. Accessto a network may be denied when the modification itself materially and adversely affects theoperation of the network or violates the rules and protocols for communication across thenetwork.

Corresponding Source conveyed, and Installation Information provided, in accord with thissection must be in a format that is publicly documented (and with an implementation availableto the public in source code form), and must require no special password or key for unpacking,reading or copying.

7. Additional Terms.

“Additional permissions” are terms that supplement the terms of this License by making ex-ceptions from one or more of its conditions. Additional permissions that are applicable to theentire Program shall be treated as though they were included in this License, to the extentthat they are valid under applicable law. If additional permissions apply only to part of theProgram, that part may be used separately under those permissions, but the entire Programremains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additionalpermissions from that copy, or from any part of it. (Additional permissions may be writtento require their own removal in certain cases when you modify the work.) You may placeadditional permissions on material, added by you to a covered work, for which you have or cangive appropriate copyright permission.

2014-10-25 399


Notwithstanding any other provision of this License, for material you add to a covered work,you may (if authorized by the copyright holders of that material) supplement the terms of thisLicense with terms:

a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16of this License; or

b. Requiring preservation of specified reasonable legal notices or author attributions in thatmaterial or in the Appropriate Legal Notices displayed by works containing it; or

c. Prohibiting misrepresentation of the origin of that material, or requiring that modifiedversions of such material be marked in reasonable ways as different from the originalversion; or

d. Limiting the use for publicity purposes of names of licensors or authors of the material; or

e. Declining to grant rights under trademark law for use of some trade names, trademarks,or service marks; or

f. Requiring indemnification of licensors and authors of that material by anyone who conveysthe material (or modified versions of it) with contractual assumptions of liability to therecipient, for any liability that these contractual assumptions directly impose on thoselicensors and authors.

All other non-permissive additional terms are considered “further restrictions” within the mean-ing of section 10. If the Program as you received it, or any part of it, contains a notice statingthat it is governed by this License along with a term that is a further restriction, you mayremove that term. If a license document contains a further restriction but permits relicensingor conveying under this License, you may add to a covered work material governed by the termsof that license document, provided that the further restriction does not survive such relicensingor conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevantsource files, a statement of the additional terms that apply to those files, or a notice indicatingwhere to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separatelywritten license, or stated as exceptions; the above requirements apply either way.

8. Termination.

You may not propagate or modify a covered work except as expressly provided under thisLicense. Any attempt otherwise to propagate or modify it is void, and will automaticallyterminate your rights under this License (including any patent licenses granted under the thirdparagraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyrightholder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finallyterminates your license, and (b) permanently, if the copyright holder fails to notify you of theviolation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if thecopyright holder notifies you of the violation by some reasonable means, this is the first timeyou have received notice of violation of this License (for any work) from that copyright holder,and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties whohave received copies or rights from you under this License. If your rights have been terminatedand not permanently reinstated, you do not qualify to receive new licenses for the same materialunder section 10.

400 Version 1.1 Rel. 7.20141001


9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program.Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peertransmission to receive a copy likewise does not require acceptance. However, nothing otherthan this License grants you permission to propagate or modify any covered work. These actionsinfringe copyright if you do not accept this License. Therefore, by modifying or propagating acovered work, you indicate your acceptance of this License to do so.

10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from theoriginal licensors, to run, modify and propagate that work, subject to this License. You are notresponsible for enforcing compliance by third parties with this License.

An “entity transaction” is a transaction transferring control of an organization, or substantiallyall assets of one, or subdividing an organization, or merging organizations. If propagation of acovered work results from an entity transaction, each party to that transaction who receives acopy of the work also receives whatever licenses to the work the party’s predecessor in interesthad or could give under the previous paragraph, plus a right to possession of the CorrespondingSource of the work from the predecessor in interest, if the predecessor has it or can get it withreasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmedunder this License. For example, you may not impose a license fee, royalty, or other charge forexercise of rights granted under this License, and you may not initiate litigation (including across-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making,using, selling, offering for sale, or importing the Program or any portion of it.

11. Patents.

A “contributor” is a copyright holder who authorizes use under this License of the Programor a work on which the Program is based. The work thus licensed is called the contributor’s“contributor version”.

A contributor’s “essential patent claims” are all patent claims owned or controlled by thecontributor, whether already acquired or hereafter acquired, that would be infringed by somemanner, permitted by this License, of making, using, or selling its contributor version, but donot include claims that would be infringed only as a consequence of further modification of thecontributor version. For purposes of this definition, “control” includes the right to grant patentsublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under thecontributor’s essential patent claims, to make, use, sell, offer for sale, import and otherwiserun, modify and propagate the contents of its contributor version.

In the following three paragraphs, a “patent license” is any express agreement or commitment,however denominated, not to enforce a patent (such as an express permission to practice apatent or covenant not to sue for patent infringement). To “grant” such a patent license to aparty means to make such an agreement or commitment not to enforce a patent against theparty.

If you convey a covered work, knowingly relying on a patent license, and the CorrespondingSource of the work is not available for anyone to copy, free of charge and under the termsof this License, through a publicly available network server or other readily accessible means,then you must either (1) cause the Corresponding Source to be so available, or (2) arrange todeprive yourself of the benefit of the patent license for this particular work, or (3) arrange,in a manner consistent with the requirements of this License, to extend the patent license to

2014-10-25 401


downstream recipients. “Knowingly relying” means you have actual knowledge that, but forthe patent license, your conveying the covered work in a country, or your recipient’s use of thecovered work in a country, would infringe one or more identifiable patents in that country thatyou have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, orpropagate by procuring conveyance of, a covered work, and grant a patent license to some ofthe parties receiving the covered work authorizing them to use, propagate, modify or convey aspecific copy of the covered work, then the patent license you grant is automatically extendedto all recipients of the covered work and works based on it.

A patent license is “discriminatory” if it does not include within the scope of its coverage,prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights thatare specifically granted under this License. You may not convey a covered work if you are aparty to an arrangement with a third party that is in the business of distributing software,under which you make payment to the third party based on the extent of your activity ofconveying the work, and under which the third party grants, to any of the parties who wouldreceive the covered work from you, a discriminatory patent license (a) in connection with copiesof the covered work conveyed by you (or copies made from those copies), or (b) primarily forand in connection with specific products or compilations that contain the covered work, unlessyou entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or otherdefenses to infringement that may otherwise be available to you under applicable patent law.

12. No Surrender of Others’ Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contra-dict the conditions of this License, they do not excuse you from the conditions of this License.If you cannot convey a covered work so as to satisfy simultaneously your obligations under thisLicense and any other pertinent obligations, then as a consequence you may not convey it at all.For example, if you agree to terms that obligate you to collect a royalty for further conveyingfrom those to whom you convey the Program, the only way you could satisfy both those termsand this License would be to refrain entirely from conveying the Program.

13. Remote Network Interaction; Use with the GNU General Public License.

Notwithstanding any other provision of this License, if you modify the Program, your modifiedversion must prominently offer all users interacting with it remotely through a network (ifyour version supports such interaction) an opportunity to receive the Corresponding Sourceof your version by providing access to the Corresponding Source from a network server at nocharge, through some standard or customary means of facilitating copying of software. ThisCorresponding Source shall include the Corresponding Source for any work covered by version3 of the GNU General Public License that is incorporated pursuant to the following paragraph.

Notwithstanding any other provision of this License, you have permission to link or combineany covered work with a work licensed under version 3 of the GNU General Public Licenseinto a single combined work, and to convey the resulting work. The terms of this License willcontinue to apply to the part which is the covered work, but the work with which it is combinedwill remain governed by version 3 of the GNU General Public License.

14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU AfferoGeneral Public License from time to time. Such new versions will be similar in spirit to thepresent version, but may differ in detail to address new problems or concerns.

402 Version 1.1 Rel. 7.20141001


Each version is given a distinguishing version number. If the Program specifies that a certainnumbered version of the GNU Affero General Public License “or any later version” applies to it,you have the option of following the terms and conditions either of that numbered version or ofany later version published by the Free Software Foundation. If the Program does not specifya version number of the GNU Affero General Public License, you may choose any version everpublished by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU AfferoGeneral Public License can be used, that proxy’s public statement of acceptance of a versionpermanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additionalobligations are imposed on any author or copyright holder as a result of your choosing to followa later version.

15. Disclaimer of Warranty.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTEDBY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THECOPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM“AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRERISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITHYOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OFALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. Limitation of Liability.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRIT-ING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIESAND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOUFOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSE-QUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PRO-GRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING REN-DERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR AFAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVENIF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OFSUCH DAMAGES.

17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given locallegal effect according to their terms, reviewing courts shall apply local law that most closelyapproximates an absolute waiver of all civil liability in connection with the Program, unless awarranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

2014-10-25 403

Licenses

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public,the best way to achieve this is to make it free software which everyone can redistribute and changeunder these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of eachsource file to most effectively state the exclusion of warranty; and each file should have at least the“copyright” line and a pointer to where the full notice is found.

one line to give the program’s name and a brief idea of what it does.

Copyright (C) year name of author

This program is free software: you can redistribute it and/or modify

it under the terms of the GNU Affero General Public License as published by

the Free Software Foundation, either version 3 of the License, or (at

your option) any later version.

This program is distributed in the hope that it will be useful, but

WITHOUT ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU

Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License

along with this program. If not, see http://www.gnu.org/licenses/.

Also add information on how to contact you by electronic and paper mail.

If your software can interact with users remotely through a network, you should also make sure thatit provides a way for users to get its source. For example, if your program is a web application, itsinterface could display a “Source” link that leads users to an archive of the code. There are manyways you could offer source, and different solutions will be better for different programs; see section13 for the specific requirements.

You should also get your employer (if you work as a programmer) or school, if any, to sign a“copyright disclaimer” for the program, if necessary. For more information on this, and how toapply and follow the GNU AGPL, see http://www.gnu.org/licenses/.

404 Version 1.1 Rel. 7.20141001

http://www.gnu.org/licenses/

http://www.gnu.org/licenses/


GNU Free Documentation License

GNU FREE DOCUMENTATION LICENSEVersion 1.3, 3 November 2008

Copyright c© 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.http://fsf.org/

Everyone is permitted to copy and distribute verbatim copiesof this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and usefuldocument free in the sense of freedom: to assure everyone the effective freedom to copy andredistribute it, with or without modifying it, either commercially or noncommercially. Secon-darily, this License preserves for the author and publisher a way to get credit for their work,while not being considered responsible for modifications made by others.

This License is a kind of “copyleft”, which means that derivative works of the document mustthemselves be free in the same sense. It complements the GNU General Public License, whichis a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because freesoftware needs free documentation: a free program should come with manuals providing thesame freedoms that the software does. But this License is not limited to software manuals; itcan be used for any textual work, regardless of subject matter or whether it is published as aprinted book. We recommend this License principally for works whose purpose is instructionor reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placedby the copyright holder saying it can be distributed under the terms of this License. Such anotice grants a world-wide, royalty-free license, unlimited in duration, to use that work underthe conditions stated herein. The “Document”, below, refers to any such manual or work. Anymember of the public is a licensee, and is addressed as “you”. You accept the license if youcopy, modify or distribute the work in a way requiring permission under copyright law.

A “Modified Version” of the Document means any work containing the Document or a portionof it, either copied verbatim, or with modifications and/or translated into another language.

A “Secondary Section” is a named appendix or a front-matter section of the Document thatdeals exclusively with the relationship of the publishers or authors of the Document to theDocument’s overall subject (or to related matters) and contains nothing that could fall directlywithin that overall subject. (Thus, if the Document is in part a textbook of mathematics,a Secondary Section may not explain any mathematics.) The relationship could be a matterof historical connection with the subject or with related matters, or of legal, commercial,philosophical, ethical or political position regarding them.

The “Invariant Sections” are certain Secondary Sections whose titles are designated, as beingthose of Invariant Sections, in the notice that says that the Document is released under thisLicense. If a section does not fit the above definition of Secondary then it is not allowed to bedesignated as Invariant. The Document may contain zero Invariant Sections. If the Documentdoes not identify any Invariant Sections then there are none.

2014-10-25 405

http://fsf.org/

Licenses texi/fdl13.texi

The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts orBack-Cover Texts, in the notice that says that the Document is released under this License. AFront-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A “Transparent” copy of the Document means a machine-readable copy, represented in a formatwhose specification is available to the general public, that is suitable for revising the documentstraightforwardly with generic text editors or (for images composed of pixels) generic paintprograms or (for drawings) some widely available drawing editor, and that is suitable for inputto text formatters or for automatic translation to a variety of formats suitable for input to textformatters. A copy made in an otherwise Transparent file format whose markup, or absence ofmarkup, has been arranged to thwart or discourage subsequent modification by readers is notTransparent. An image format is not Transparent if used for any substantial amount of text.A copy that is not “Transparent” is called “Opaque”.

Examples of suitable formats for Transparent copies include plain ascii without markup, Tex-info input format, LaTEX input format, SGML or XML using a publicly available DTD, andstandard-conforming simple HTML, PostScript or PDF designed for human modification. Ex-amples of transparent image formats include PNG, XCF and JPG. Opaque formats includeproprietary formats that can be read and edited only by proprietary word processors, SGML orXML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposesonly.

The “Title Page” means, for a printed book, the title page itself, plus such following pages asare needed to hold, legibly, the material this License requires to appear in the title page. Forworks in formats which do not have any title page as such, “Title Page” means the text nearthe most prominent appearance of the work’s title, preceding the beginning of the body of thetext.

The “publisher” means any person or entity that distributes copies of the Document to thepublic.

A section “Entitled XYZ” means a named subunit of the Document whose title either is preciselyXYZ or contains XYZ in parentheses following text that translates XYZ in another language.(Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”,“Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section whenyou modify the Document means that it remains a section “Entitled XYZ” according to thisdefinition.

The Document may include Warranty Disclaimers next to the notice which states that thisLicense applies to the Document. These Warranty Disclaimers are considered to be includedby reference in this License, but only as regards disclaiming warranties: any other implicationthat these Warranty Disclaimers may have is void and has no effect on the meaning of thisLicense.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncom-mercially, provided that this License, the copyright notices, and the license notice saying thisLicense applies to the Document are reproduced in all copies, and that you add no other con-ditions whatsoever to those of this License. You may not use technical measures to obstruct orcontrol the reading or further copying of the copies you make or distribute. However, you mayaccept compensation in exchange for copies. If you distribute a large enough number of copiesyou must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly displaycopies.

406 Version 1.1 Rel. 7.20141001


3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of theDocument, numbering more than 100, and the Document’s license notice requires Cover Texts,you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts:Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both coversmust also clearly and legibly identify you as the publisher of these copies. The front covermust present the full title with all words of the title equally prominent and visible. You mayadd other material on the covers in addition. Copying with changes limited to the covers, aslong as they preserve the title of the Document and satisfy these conditions, can be treated asverbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the firstones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacentpages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you musteither include a machine-readable Transparent copy along with each Opaque copy, or state inor with each Opaque copy a computer-network location from which the general network-usingpublic has access to download using public-standard network protocols a complete Transparentcopy of the Document, free of added material. If you use the latter option, you must takereasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensurethat this Transparent copy will remain thus accessible at the stated location until at least oneyear after the last time you distribute an Opaque copy (directly or through your agents orretailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well beforeredistributing any large number of copies, to give them a chance to provide you with an updatedversion of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions ofsections 2 and 3 above, provided that you release the Modified Version under precisely thisLicense, with the Modified Version filling the role of the Document, thus licensing distributionand modification of the Modified Version to whoever possesses a copy of it. In addition, youmust do these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document,and from those of previous versions (which should, if there were any, be listed in the Historysection of the Document). You may use the same title as a previous version if the originalpublisher of that version gives permission.

B. List on the Title Page, as authors, one or more persons or entities responsible for authorshipof the modifications in the Modified Version, together with at least five of the principalauthors of the Document (all of its principal authors, if it has fewer than five), unless theyrelease you from this requirement.

C. State on the Title page the name of the publisher of the Modified Version, as the publisher.

D. Preserve all the copyright notices of the Document.

E. Add an appropriate copyright notice for your modifications adjacent to the other copyrightnotices.

F. Include, immediately after the copyright notices, a license notice giving the public permis-sion to use the Modified Version under the terms of this License, in the form shown in theAddendum below.

2014-10-25 407


G. Preserve in that license notice the full lists of Invariant Sections and required Cover Textsgiven in the Document’s license notice.

H. Include an unaltered copy of this License.

I. Preserve the section Entitled “History”, Preserve its Title, and add to it an item statingat least the title, year, new authors, and publisher of the Modified Version as given on theTitle Page. If there is no section Entitled “History” in the Document, create one statingthe title, year, authors, and publisher of the Document as given on its Title Page, thenadd an item describing the Modified Version as stated in the previous sentence.

J. Preserve the network location, if any, given in the Document for public access to a Trans-parent copy of the Document, and likewise the network locations given in the Documentfor previous versions it was based on. These may be placed in the “History” section. Youmay omit a network location for a work that was published at least four years before theDocument itself, or if the original publisher of the version it refers to gives permission.

K. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of thesection, and preserve in the section all the substance and tone of each of the contributoracknowledgements and/or dedications given therein.

L. Preserve all the Invariant Sections of the Document, unaltered in their text and in theirtitles. Section numbers or the equivalent are not considered part of the section titles.

M. Delete any section Entitled “Endorsements”. Such a section may not be included in theModified Version.

N. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in titlewith any Invariant Section.

O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Sec-ondary Sections and contain no material copied from the Document, you may at your optiondesignate some or all of these sections as invariant. To do this, add their titles to the list ofInvariant Sections in the Modified Version’s license notice. These titles must be distinct fromany other section titles.

You may add a section Entitled “Endorsements”, provided it contains nothing but endorsementsof your Modified Version by various parties—for example, statements of peer review or thatthe text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Onlyone passage of Front-Cover Text and one of Back-Cover Text may be added by (or througharrangements made by) any one entity. If the Document already includes a cover text for thesame cover, previously added by you or by arrangement made by the same entity you are actingon behalf of, you may not add another; but you may replace the old one, on explicit permissionfrom the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to usetheir names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, underthe terms defined in section 4 above for modified versions, provided that you include in thecombination all of the Invariant Sections of all of the original documents, unmodified, and listthem all as Invariant Sections of your combined work in its license notice, and that you preserveall their Warranty Disclaimers.

408 Version 1.1 Rel. 7.20141001


The combined work need only contain one copy of this License, and multiple identical InvariantSections may be replaced with a single copy. If there are multiple Invariant Sections with thesame name but different contents, make the title of each such section unique by adding at theend of it, in parentheses, the name of the original author or publisher of that section if known,or else a unique number. Make the same adjustment to the section titles in the list of InvariantSections in the license notice of the combined work.

In the combination, you must combine any sections Entitled “History” in the various originaldocuments, forming one section Entitled “History”; likewise combine any sections Entitled“Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sectionsEntitled “Endorsements.”

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released underthis License, and replace the individual copies of this License in the various documents with asingle copy that is included in the collection, provided that you follow the rules of this Licensefor verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually underthis License, provided you insert a copy of this License into the extracted document, and followthis License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent docu-ments or works, in or on a volume of a storage or distribution medium, is called an “aggregate”if the copyright resulting from the compilation is not used to limit the legal rights of the com-pilation’s users beyond what the individual works permit. When the Document is included inan aggregate, this License does not apply to the other works in the aggregate which are notthemselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then ifthe Document is less than one half of the entire aggregate, the Document’s Cover Texts may beplaced on covers that bracket the Document within the aggregate, or the electronic equivalentof covers if the Document is in electronic form. Otherwise they must appear on printed coversthat bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of theDocument under the terms of section 4. Replacing Invariant Sections with translations requiresspecial permission from their copyright holders, but you may include translations of some orall Invariant Sections in addition to the original versions of these Invariant Sections. Youmay include a translation of this License, and all the license notices in the Document, andany Warranty Disclaimers, provided that you also include the original English version of thisLicense and the original versions of those notices and disclaimers. In case of a disagreementbetween the translation and the original version of this License or a notice or disclaimer, theoriginal version will prevail.

If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”,the requirement (section 4) to Preserve its Title (section 1) will typically require changing theactual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly providedunder this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void,and will automatically terminate your rights under this License.

2014-10-25 409


However, if you cease all violation of this License, then your license from a particular copyrightholder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finallyterminates your license, and (b) permanently, if the copyright holder fails to notify you of theviolation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if thecopyright holder notifies you of the violation by some reasonable means, this is the first timeyou have received notice of violation of this License (for any work) from that copyright holder,and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties whohave received copies or rights from you under this License. If your rights have been terminatedand not permanently reinstated, receipt of a copy of some or all of the same material does notgive you any rights to use it.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documen-tation License from time to time. Such new versions will be similar in spirit to the presentversion, but may differ in detail to address new problems or concerns. See http://www.gnu.

org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifiesthat a particular numbered version of this License “or any later version” applies to it, youhave the option of following the terms and conditions either of that specified version or of anylater version that has been published (not as a draft) by the Free Software Foundation. Ifthe Document does not specify a version number of this License, you may choose any versionever published (not as a draft) by the Free Software Foundation. If the Document specifiesthat a proxy can decide which future versions of this License can be used, that proxy’s publicstatement of acceptance of a version permanently authorizes you to choose that version for theDocument.

11. RELICENSING

“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web serverthat publishes copyrightable works and also provides prominent facilities for anybody to editthose works. A public wiki that anybody can edit is an example of such a server. A “MassiveMultiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightableworks thus published on the MMC site.

“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published byCreative Commons Corporation, a not-for-profit corporation with a principal place of businessin San Francisco, California, as well as future copyleft versions of that license published by thatsame organization.

“Incorporate” means to publish or republish a Document, in whole or in part, as part of anotherDocument.

An MMC is “eligible for relicensing” if it is licensed under this License, and if all works thatwere first published under this License somewhere other than this MMC, and subsequentlyincorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections,and (2) were thus incorporated prior to November 1, 2008.

The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SAon the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.

410 Version 1.1 Rel. 7.20141001

http://www.gnu.org/copyleft/

http://www.gnu.org/copyleft/


ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the documentand put the following copyright and license notices just after the title page:

Copyright (C) year your name.

Permission is granted to copy, distribute and/or modify this document

under the terms of the GNU Free Documentation License, Version 1.3

or any later version published by the Free Software Foundation;

with no Invariant Sections, no Front-Cover Texts, and no Back-Cover

Texts. A copy of the license is included in the section entitled ‘‘GNU

Free Documentation License’’.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with. . .Texts.”line with this:

with the Invariant Sections being list their titles, with

the Front-Cover Texts being list, and with the Back-Cover Texts

being list.

If you have Invariant Sections without Cover Texts, or some other combination of the three, mergethose two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing theseexamples in parallel under your choice of free software license, such as the GNU General PublicLicense, to permit their use in free software.

2014-10-25 411

Mobile Application Part Interface (MAPI) Index

Index

AADDR_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34, 36ADDR_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34, 36

DDIAIND_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34, 36

Llicense, AGPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395license, FDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405license, GNU Affero General Public License . . . 395license, GNU Free Documentation License . . . . 405

MMAP_ABORT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 30MAP_ABORT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53MAP_ABORT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_ACTSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68MAP_ACTSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66MAP_ACTSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65MAP_ACTSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67MAP_ACTTM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72MAP_ACTTM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70MAP_ACTTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69MAP_ACTTM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71MAP_ADDR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33, 40MAP_ADDR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41MAP_ADDR_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33MAP_ADDR_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40MAP_addr_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40MAP_ALERTSC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76MAP_ALERTSC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74MAP_ALERTSC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73MAP_ALERTSC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75MAP_ALLOCHN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80MAP_ALLOCHN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78MAP_ALLOCHN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77MAP_ALLOCHN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79MAP_ANYMOD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84MAP_ANYMOD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82MAP_ANYMOD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81MAP_ANYMOD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83MAP_ANYQRY_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88MAP_ANYQRY_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86MAP_ANYQRY_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85MAP_ANYQRY_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87MAP_ANYSUB_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92MAP_ANYSUB_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90MAP_ANYSUB_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

MAP_ANYSUB_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91MAP_AUTH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100MAP_AUTH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98MAP_AUTH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97MAP_AUTH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99MAP_AUTHFAIL_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96MAP_AUTHFAIL_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94MAP_AUTHFAIL_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93MAP_AUTHFAIL_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95MAP_BIND_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . 23, 29, 35MAP_BIND_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36MAP_bind_ack_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36MAP_BIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 23, 29, 33MAP_BIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34MAP_bind_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34MAP_CANCLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104MAP_CANCLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102MAP_CANCLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101MAP_CANCLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103MAP_CKIEMI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124MAP_CKIEMI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122MAP_CKIEMI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121MAP_CKIEMI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123MAP_CLOSE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30MAP_CLOSE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52MAP_CLOSE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_CLOSE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 29MAP_CLOSE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51MAP_CLOSE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_DEACTSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128MAP_DEACTSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126MAP_DEACTSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125MAP_DEACTSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127MAP_DEACTTM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132MAP_DEACTTM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130MAP_DEACTTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129MAP_DEACTTM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131MAP_DELIM_IND . . . . . . . . . . . . . . . . . . . . . . . . . 26, 27, 29MAP_DELIM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50MAP_DELIM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_DELIM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29MAP_DELIM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49MAP_DELIM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_DELSUBD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136MAP_DELSUBD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134MAP_DELSUBD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133MAP_DELSUBD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135MAP_ERASECC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140MAP_ERASECC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138MAP_ERASECC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137MAP_ERASECC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139MAP_ERASESS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2014-10-25 413

Index

MAP_ERASESS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142MAP_ERASESS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141MAP_ERASESS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143MAP_ERROR_ACK . . . . . . . . . . . . . . . . . . 24, 29, 35, 37, 39MAP_ERROR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43MAP_ERROR_ACK . . 47, 49, 51, 53, 57, 59, 61, 63, 65,

67, 69, 71, 73, 75, 77, 79, 81, 83, 85, 87, 89, 91,93, 95, 97, 99, 101, 103, 105, 107, 109, 111,113, 116, 117, 120, 121, 123, 125, 127, 129,131, 133, 135, 137, 139, 141, 143, 145, 147,149, 151, 155, 157, 159, 161, 163, 165, 167,169, 171, 173, 175, 177, 179, 181, 183, 185,187, 189, 191, 193, 195, 197, 199, 201, 203,205, 207, 209, 211, 213, 215, 217, 219, 221,223, 225, 227, 229, 231, 233, 235, 237, 239,241, 243, 245, 247, 249, 251, 253, 255, 257,259, 261, 263, 265, 267, 269, 271, 273, 275,277, 279, 281, 283, 285, 287, 289, 291, 293,295, 297, 299, 301, 303, 305, 307, 309, 311,313, 315, 317, 319, 321, 323, 325, 327, 329,331, 333, 335, 337, 339, 341, 343, 345, 347,349, 351, 353, 355, 357, 359, 361, 363, 365,367, 369, 371, 373

MAP_FAILURE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148MAP_FAILURE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146MAP_FAILURE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145MAP_FAILURE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147MAP_FAS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152MAP_FAS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150MAP_FAS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149MAP_FAS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151MAP_FCKSSIND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156MAP_FCKSSIND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154MAP_FCKSSIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153MAP_FCKSSIND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155MAP_FGRCSIG_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160MAP_FGRCSIG_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158MAP_FGRCSIG_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157MAP_FGRCSIG_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159MAP_FNEWIMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164MAP_FNEWIMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162MAP_FNEWIMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161MAP_FNEWIMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163MAP_GETIEMI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168MAP_GETIEMI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166MAP_GETIEMI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165MAP_GETIEMI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167MAP_GETPASS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172MAP_GETPASS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170MAP_GETPASS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169MAP_GETPASS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171MAP_INFO_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . 23, 29, 31MAP_INFO_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32MAP_info_ack_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32MAP_INFO_REQ . . . . . . . . . . . . . . . . . . . 23, 29, 31, 32, 33MAP_info_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

MAP_INFORMSC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176MAP_INFORMSC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174MAP_INFORMSC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173MAP_INFORMSC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175MAP_INSSUBSD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180MAP_INSSUBSD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178MAP_INSSUBSD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177MAP_INSSUBSD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179MAP_INTERGSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184MAP_INTERGSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182MAP_INTERGSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181MAP_INTERGSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183MAP_ISTALERT_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188MAP_ISTALERT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186MAP_ISTALERT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185MAP_ISTALERT_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187MAP_ISTCMD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192MAP_ISTCMD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190MAP_ISTCMD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189MAP_ISTCMD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191MAP_MMEVENT_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196MAP_MMEVENT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194MAP_MMEVENT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193MAP_MMEVENT_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195MAP_MOFSMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200MAP_MOFSMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198MAP_MOFSMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197MAP_MOFSMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199MAP_MSGRPSPRES_CON . . . . . . . . . . . . . . . . . . . . . . . . . 204MAP_MSGRPSPRES_IND . . . . . . . . . . . . . . . . . . . . . . . . . 202MAP_MSGRPSPRES_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 201MAP_MSGRPSPRES_RES . . . . . . . . . . . . . . . . . . . . . . . . . 203MAP_MTFSMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208MAP_MTFSMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206MAP_MTFSMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205MAP_MTFSMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207MAP_NOTICE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30MAP_NOTICE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56MAP_NOTICE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_OK_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 29, 37MAP_OK_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44MAP_OK_ACK . . 47, 49, 51, 53, 57, 59, 61, 63, 65, 67,

69, 71, 73, 75, 77, 79, 81, 83, 85, 87, 89, 91, 93,95, 97, 99, 101, 103, 105, 107, 109, 111, 113,116, 117, 120, 121, 123, 125, 127, 129, 131, 133,135, 137, 139, 141, 143, 145, 147, 149, 151,155, 157, 159, 161, 163, 165, 167, 169, 171,173, 175, 177, 179, 181, 183, 185, 187, 189,191, 193, 195, 197, 199, 201, 203, 205, 207,209, 211, 213, 215, 217, 219, 221, 223, 225,227, 229, 231, 233, 235, 237, 239, 241, 243,245, 247, 249, 251, 253, 255, 257, 259, 261,263, 265, 267, 269, 271, 273, 275, 277, 279,281, 283, 285, 287, 289, 291, 293, 295, 297,299, 301, 303, 305, 307, 309, 311, 313, 315,317, 319, 321, 323, 325, 327, 329, 331, 333,

414 Version 1.1 Rel. 7.20141001


335, 337, 339, 341, 343, 345, 347, 349, 351,353, 355, 357, 359, 361, 363, 365, 367, 369, 371

MAP_OPEN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26, 29MAP_OPEN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48MAP_OPEN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_OPEN_IND . . . . . . . . . . . . . . . . . . . . . . 25, 26, 28, 29MAP_OPEN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46MAP_OPEN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_OPEN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 26, 29MAP_OPEN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45MAP_OPEN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_OPEN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 26, 29MAP_OPEN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47MAP_OPEN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_OPTMGMT_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . 38, 39MAP_OPTMGMT_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42MAP_OPTMGMT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24MAP_OPTMGMT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38MAP_optmgmt_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38MAP_PABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 30MAP_PABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55MAP_PABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_PAGE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212MAP_PAGE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210MAP_PAGE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209MAP_PAGE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211MAP_PREPGC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216MAP_PREPGC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214MAP_PREPGC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213MAP_PREPGC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215MAP_PREPHO_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220MAP_PREPHO_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218MAP_PREPHO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217MAP_PREPHO_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219MAP_PREPSH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224MAP_PREPSH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222MAP_PREPSH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221MAP_PREPSH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223MAP_PROCAS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228MAP_PROCAS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226MAP_PROCAS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225MAP_PROCAS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227MAP_PROCGC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232MAP_PROCGC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230MAP_PROCGC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229MAP_PROCGC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231MAP_PROCUSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236MAP_PROCUSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234MAP_PROCUSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233MAP_PROCUSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235MAP_PROVIMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240MAP_PROVIMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238MAP_PROVIMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237MAP_PROVIMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239MAP_PROVRN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244MAP_PROVRN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

MAP_PROVRN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241MAP_PROVRN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243MAP_PROVSLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248MAP_PROVSLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246MAP_PROVSLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245MAP_PROVSLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247MAP_PROVSUBI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252MAP_PROVSUBI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250MAP_PROVSUBI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249MAP_PROVSUBI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251MAP_PURGEMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256MAP_PURGEMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254MAP_PURGEMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253MAP_PURGEMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255MAP_RDYSM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260MAP_RDYSM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258MAP_RDYSM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257MAP_RDYSM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259MAP_REGCC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264MAP_REGCC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262MAP_REGCC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261MAP_REGCC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263MAP_REGPW_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268MAP_REGPW_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266MAP_REGPW_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265MAP_REGPW_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267MAP_REGSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272MAP_REGSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270MAP_REGSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269MAP_REGSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271MAP_REMUSRFREE_CON . . . . . . . . . . . . . . . . . . . . . . . . . 276MAP_REMUSRFREE_IND . . . . . . . . . . . . . . . . . . . . . . . . . 274MAP_REMUSRFREE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 273MAP_REMUSRFREE_RES . . . . . . . . . . . . . . . . . . . . . . . . . 275MAP_RESET_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107MAP_RESET_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106MAP_RESET_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105MAP_RESET_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108MAP_RESTORE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111MAP_RESTORE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110MAP_RESTORE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109MAP_RESTORE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112MAP_RESUME_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116MAP_RESUME_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114MAP_RESUME_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113MAP_RESUME_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115MAP_SEARCH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120MAP_SEARCH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118MAP_SEARCH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117MAP_SEARCH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119MAP_SENDAUTHI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 296MAP_SENDAUTHI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 294MAP_SENDAUTHI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 293MAP_SENDAUTHI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 295MAP_SENDEND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300MAP_SENDEND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

2014-10-25 415

Index

MAP_SENDEND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297MAP_SENDEND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299MAP_SENDGCEND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 304MAP_SENDGCEND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 302MAP_SENDGCEND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 301MAP_SENDGCEND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 303MAP_SENDGPRSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 308MAP_SENDGPRSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 306MAP_SENDGPRSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 305MAP_SENDGPRSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 307MAP_SENDHOREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 312MAP_SENDHOREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 310MAP_SENDHOREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 309MAP_SENDHOREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 311MAP_SENDID_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280MAP_SENDID_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278MAP_SENDID_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277MAP_SENDID_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279MAP_SENDIMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316MAP_SENDIMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314MAP_SENDIMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313MAP_SENDIMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315MAP_SENDLCSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 320MAP_SENDLCSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 318MAP_SENDLCSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 317MAP_SENDLCSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 319MAP_SENDMOSMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 324MAP_SENDMOSMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 322MAP_SENDMOSMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 321MAP_SENDMOSMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 323MAP_SENDMTSMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 328MAP_SENDMTSMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 326MAP_SENDMTSMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 325MAP_SENDMTSMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 327MAP_SENDRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332MAP_SENDRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330MAP_SENDRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329MAP_SENDRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331MAP_SENDSMSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 336MAP_SENDSMSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 334MAP_SENDSMSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 333MAP_SENDSMSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 335MAP_SETCM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284MAP_SETCM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282MAP_SETCM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281MAP_SETCM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283MAP_SETREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288MAP_SETREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286MAP_SETREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285MAP_SETREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287MAP_SMDELIVSTAT_CON . . . . . . . . . . . . . . . . . . . . . . . . 292MAP_SMDELIVSTAT_IND . . . . . . . . . . . . . . . . . . . . . . . . 290MAP_SMDELIVSTAT_REQ . . . . . . . . . . . . . . . . . . . . . . . . 289MAP_SMDELIVSTAT_RES . . . . . . . . . . . . . . . . . . . . . . . . 291MAP_SSINV_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340MAP_SSINV_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

MAP_SSINV_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337MAP_SSINV_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339MAP_STATUS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344MAP_STATUS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342MAP_STATUS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341MAP_STATUS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343MAP_STC1_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58MAP_STC1_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57MAP_STC2_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60MAP_STC2_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59MAP_STC3_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62MAP_STC3_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61MAP_STC4_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64MAP_STC4_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63MAP_SUBLOCREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 348MAP_SUBLOCREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 346MAP_SUBLOCREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 345MAP_SUBLOCREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 347MAP_SUBSDATAMOD_CON . . . . . . . . . . . . . . . . . . . . . . . . 352MAP_SUBSDATAMOD_IND . . . . . . . . . . . . . . . . . . . . . . . . 350MAP_SUBSDATAMOD_REQ . . . . . . . . . . . . . . . . . . . . . . . . 349MAP_SUBSDATAMOD_RES . . . . . . . . . . . . . . . . . . . . . . . . 351MAP_TRACESA_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356MAP_TRACESA_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354MAP_TRACESA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353MAP_TRACESA_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355MAP_UABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . 28, 30MAP_UABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54MAP_UABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379MAP_UDGRPSLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 360MAP_UDGRPSLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 358MAP_UDGRPSLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 357MAP_UDGRPSLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 359MAP_UDLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364MAP_UDLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362MAP_UDLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361MAP_UDLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363MAP_UNBIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . 24, 29MAP_UNBIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37MAP_unbind_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37MAP_USSDNTFY_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368MAP_USSDNTFY_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366MAP_USSDNTFY_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365MAP_USSDNTFY_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367MAP_USSDREQ_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372MAP_USSDREQ_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370MAP_USSDREQ_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369MAP_USSDREQ_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371MGMT_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

OOPT_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38OPT_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

416 Version 1.1 Rel. 7.20141001


PPRIM_type . . . . . . . . . . . . . . . . . . . . . . . . . . 34, 36, 38, 40PRIM_type: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

S

STREAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 7, 8

2014-10-25 417

Documents

Mobile Application Part Interface (MAPI) Specification