MAP Protocols
description
Transcript of MAP Protocols
Mobile Application Part Interface (MAPI) Specification
Mobile Application Part Interface (MAPI)
SpecificationVersion 0.9a Edition 8
Updated 2008-10-31Distributed with Package strss7-0.9a.8
Copyright c© 2008 OpenSS7 CorporationAll Rights Reserved.
Abstract
This document is a Specification containing technical details concerning theimplementation of the Mobile Application Part Interface (MAPI) for OpenSS7.It contains recommendations on software architecture as well as platform andsystem applicability of the Mobile Application Part Interface (MAPI).
Brian Bidulock <[email protected]> for
The OpenSS7 Project <http://www.openss7.org/>
Copyright c© 2001-2008 OpenSS7 CorporationCopyright c© 1997-2000 Brian F. G. BidulockAll Rights Reserved.
Published by:
OpenSS7 Corporation1469 Jefferys CrescentEdmonton, Alberta T6L 6T1Canada
Unauthorized distribution or duplication is prohibited.
Permission to use, copy and distribute this documentation without modification, for anypurpose and without fee or royalty is hereby granted, provided that both the above copy-right notice and this permission notice appears in all copies and that the name of OpenSS7Corporation not be used in advertising or publicity pertaining to distribution of this docu-mentation or its contents without specific, written prior permission. OpenSS7 Corporationmakes no representation about the suitability of this documentation for any purpose. It isprovided “as is” without express or implied warranty.
Notice:
OpenSS7 Corporation disclaims all warranties with regard to this documentation includingall implied warranties of merchantability, fitness for a particular purpose, non-infringement,or title; that the contents of the document are suitable for any purpose, or that the im-plementation of such contents will not infringe on any third party patents, copyrights,trademarks or other rights. In no event shall OpenSS7 Corporation be liable for any di-rect, indirect, special or consequential damages or any damages whatsoever resulting fromloss of use, data or profits, whether in an action of contract, negligence or other tortiousaction, arising out of or in connection with any use of this document or the performanceor implementation of the contents thereof.
OpenSS7 Corporation reserves the right to revise this software and documentation for anyreason, including but not limited to, conformity with standards promulgated by variousagencies, utilization of advances in the state of the technical arts, or the reflection of changesin the design of any techniques, or procedures embodied, described, or referred to herein.OpenSS7 Corporation is under no obligation to provide any feature listed herein.
i
Short Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 The Mobile Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 MAPI Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4 MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5 Diagnostics Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Addendum for 3GPP Conformance . . . . . . . . . . . . . . . . . . . . . . . . . 381
A Mapping MAPI Primitives to 3GPP TS 29.002 . . . . . . . . . . . 383
B State/Event Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
C Primitive Precedence Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
D MAPI Header File Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
iii
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Intent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.3 Access Management Services . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1.4 Handover Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.1.11 Subscriber Information Services . . . . . . . . . . . . . . . . . . . . 14
2.3.2 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.4.1 Supplementary Service Services . . . . . . . . . . . . . . . . . . . . . . 15
2.3.5 SMS Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.5.1 Short Message Service Management Services . . . . . . . . . 15
iv Mobile Application Part Interface (MAPI)
2.3.6 Network-Requested PDP Context Activation . . . . . . . . . . . . . 162.3.6.1 Network-Requested PDP Context Activation Services
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.7 Location Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.7.1 Location Service Management Services . . . . . . . . . . . . . . . 162.4 MAP User Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4.1 Mobile Switching Centre (MSC) Service Sets . . . . . . . . . . . . . 162.4.2 Home Location Register (HLR) Service Sets . . . . . . . . . . . . . . 172.4.3 Visitor Location Register (VLR) Service Sets . . . . . . . . . . . . . 192.4.4 Equipment Identity Register (EIR) Service Sets . . . . . . . . . . . 202.4.5 Serving GPRS Support Node (SGSN) Service Sets . . . . . . . . 202.4.6 Gateway GPRS Support Node (GGSN) Service Sets . . . . . . 212.4.7 Interworking MSC (IWMSC) for Short Message Service
Service Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4.8 Gateway MSC (GMSC) for Short Message Service Service
Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4.9 Gateway Mobile Location Center (GMLC) Service Sets . . . 22
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.1 Dialogue Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.1.1 User Primitives for Successful MAP DialogueEstablishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.1.2 Provider Primitives for Successful MAP DialogueEstablishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.2 Dialogue Component Transfer Phase . . . . . . . . . . . . . . . . . . . . . . 273.2.2.1 User Primitives for Component Transfer . . . . . . . . . . . . . 273.2.2.2 Provider Primitives for Component Transfer . . . . . . . . . 27
3.2.3 Dialogue Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.3.1 User Primitives for Dialogue Abort . . . . . . . . . . . . . . . . . . 283.2.3.2 Provider Primitives for Dialogue Abort . . . . . . . . . . . . . . 28
v
4 MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.1 Management Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1.1 Information Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1.2 Information Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1.3 Bind Application Context Request . . . . . . . . . . . . . . . . . . . . . . . . 374.1.4 Bind Application Context Acknowledgement . . . . . . . . . . . . . . 394.1.5 Unbind Application Context Request . . . . . . . . . . . . . . . . . . . . . 404.1.6 Options Management Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.1.7 Get Protocol Address Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.1.8 Get Protocol Address Acknowledgement . . . . . . . . . . . . . . . . . . 444.1.9 Options Management Acknowledgement . . . . . . . . . . . . . . . . . . 454.1.10 Error Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.1.11 Successful Receipt Acknowledgement . . . . . . . . . . . . . . . . . . . . 47
4.2 Association Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.2.1 Association Establishment Request . . . . . . . . . . . . . . . . . . . . . . . 484.2.2 Association Establishment Indication . . . . . . . . . . . . . . . . . . . . . 494.2.3 Association Establishment Response . . . . . . . . . . . . . . . . . . . . . . 504.2.4 Association Establishment Confirmation . . . . . . . . . . . . . . . . . . 51
4.3 Component Transfer Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.3.1 Component Delimitation Request . . . . . . . . . . . . . . . . . . . . . . . . . 524.3.2 Component Delimitation Indication . . . . . . . . . . . . . . . . . . . . . . . 53
4.4 Association Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4.1 Association Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4.2 Association Release Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.4.3 Association Abort Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.4.4 Association User Abort Indication . . . . . . . . . . . . . . . . . . . . . . . . 574.4.5 Association Provider Abort Indication . . . . . . . . . . . . . . . . . . . . 584.4.6 Association Notice Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.5 Secure Transport Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.5.1 Secure Transport Class 1 Request . . . . . . . . . . . . . . . . . . . . . . . . 604.5.2 Secure Transport Class 1 Indication . . . . . . . . . . . . . . . . . . . . . . 614.5.3 Secure Transport Class 2 Request . . . . . . . . . . . . . . . . . . . . . . . . 624.5.4 Secure Transport Class 2 Indication . . . . . . . . . . . . . . . . . . . . . . 634.5.5 Secure Transport Class 3 Request . . . . . . . . . . . . . . . . . . . . . . . . 644.5.6 Secure Transport Class 3 Indication . . . . . . . . . . . . . . . . . . . . . . 654.5.7 Secure Transport Class 4 Request . . . . . . . . . . . . . . . . . . . . . . . . 664.5.8 Secure Transport Class 4 Indication . . . . . . . . . . . . . . . . . . . . . . 67
4.6 Service Specific Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.6.1 Activate Supplementary Service Request . . . . . . . . . . . . . . . . . . 684.6.2 Activate Supplementary Service Indication . . . . . . . . . . . . . . . . 694.6.3 Activate Supplementary Service Response . . . . . . . . . . . . . . . . 704.6.4 Activate Supplementary Service Confirmation. . . . . . . . . . . . . 714.6.5 Activate Traceec Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . 724.6.6 Activate Traceec Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . 734.6.7 Activate Traceec Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . 744.6.8 Activate Traceec Mode Confirmation . . . . . . . . . . . . . . . . . . . . . 754.6.9 Alert Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764.6.10 Alert Service Center Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 77
vi Mobile Application Part Interface (MAPI)
4.6.11 Alert Service Center Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.6.12 Alert Service Center Confirmation . . . . . . . . . . . . . . . . . . . . . . . 794.6.13 Allocate Handover Number Request . . . . . . . . . . . . . . . . . . . . . 804.6.14 Allocate Handover Number Indication . . . . . . . . . . . . . . . . . . . 814.6.15 Allocate Handover Number Response . . . . . . . . . . . . . . . . . . . . 824.6.16 Allocate Handover Number Confirmation . . . . . . . . . . . . . . . . 834.6.17 Any Time Modification Request . . . . . . . . . . . . . . . . . . . . . . . . . 844.6.18 Any Time Modification Indication . . . . . . . . . . . . . . . . . . . . . . . 854.6.19 Any Time Modification Response . . . . . . . . . . . . . . . . . . . . . . . . 864.6.20 Any Time Modification Confirmation . . . . . . . . . . . . . . . . . . . . 874.6.21 Any Time Interrogation Request . . . . . . . . . . . . . . . . . . . . . . . . 884.6.22 Any Time Interrogation Indication . . . . . . . . . . . . . . . . . . . . . . 894.6.23 Any Time Interrogation Response . . . . . . . . . . . . . . . . . . . . . . . 904.6.24 Any Time Interrogation Confirmation . . . . . . . . . . . . . . . . . . . 914.6.25 Any Time Subscription Interrogation Request . . . . . . . . . . . 924.6.26 Any Time Subscription Interrogation Indication . . . . . . . . . 934.6.27 Any Time Subscription Interrogation Response . . . . . . . . . . 944.6.28 Any Time Subscription Interrogation Confirmation . . . . . . 954.6.29 Authentication Failure Report Request . . . . . . . . . . . . . . . . . . 964.6.30 Authentication Failure Report Indication . . . . . . . . . . . . . . . . 974.6.31 Authentication Failure Report Response . . . . . . . . . . . . . . . . . 984.6.32 Authentication Failure Report Confirmation . . . . . . . . . . . . . 994.6.33 Authenticate Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.6.34 Authenticate Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014.6.35 Authenticate Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024.6.36 Authenticate Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034.6.37 Cancel Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044.6.38 Cancel Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054.6.39 Cancel Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064.6.40 Cancel Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 1074.6.41 Reset Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084.6.42 Reset Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.6.43 Reset Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.6.44 Reset Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.6.45 Restore Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.6.46 Restore Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134.6.47 Restore Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144.6.48 Restore Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154.6.49 Resume Call Handling Request . . . . . . . . . . . . . . . . . . . . . . . . . 1164.6.50 Resume Call Handling Indication . . . . . . . . . . . . . . . . . . . . . . . 1174.6.51 Resume Call Handling Confirmation . . . . . . . . . . . . . . . . . . . . 1184.6.52 Resume Call Handling Response . . . . . . . . . . . . . . . . . . . . . . . 1194.6.53 Search for MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.6.54 Search for MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.6.55 Search for MS Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.6.56 Search for MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.6.57 Check IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.6.58 Check IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
vii
4.6.59 Check IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.6.60 Check IEMI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.6.61 Deactivate Supplementary Service Request . . . . . . . . . . . . . 1284.6.62 Deactivate Supplementary Service Indication . . . . . . . . . . . 1294.6.63 Deactivate Supplementary Service Response . . . . . . . . . . . . 1304.6.64 Deactivate Supplementary Service Confirmation . . . . . . . . 1314.6.65 Deactivate Trace Mode Request . . . . . . . . . . . . . . . . . . . . . . . . 1324.6.66 Deactivate Trace Mode Indication . . . . . . . . . . . . . . . . . . . . . . 1334.6.67 Deactivate Trace Mode Response . . . . . . . . . . . . . . . . . . . . . . . 1344.6.68 Deactivate Trace Mode Confirmation . . . . . . . . . . . . . . . . . . . 1354.6.69 Delete Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . . 1364.6.70 Delete Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . . 1374.6.71 Delete Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . . 1384.6.72 Delete Subscriber Data Confirmation . . . . . . . . . . . . . . . . . . . 1394.6.73 Erase CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.6.74 Erase CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414.6.75 Erase CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424.6.76 Erase CC Entry Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 1434.6.77 Erase Supplementatry Service Request . . . . . . . . . . . . . . . . . 1444.6.78 Erase Supplementatry Service Indication . . . . . . . . . . . . . . . 1454.6.79 Erase Supplementatry Service Response . . . . . . . . . . . . . . . . 1464.6.80 Erase Supplementatry Service Confirmation . . . . . . . . . . . . 1474.6.81 Failure Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.6.82 Failure Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494.6.83 Failure Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504.6.84 Failure Report Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514.6.85 Forward Access Signalling Request . . . . . . . . . . . . . . . . . . . . . 1524.6.86 Forward Access Signalling Indication . . . . . . . . . . . . . . . . . . . 1534.6.87 Forward Access Signalling Response . . . . . . . . . . . . . . . . . . . . 1544.6.88 Forward Access Signalling Confirmation . . . . . . . . . . . . . . . . 1554.6.89 Forward Check SS Indication Request . . . . . . . . . . . . . . . . . . 1564.6.90 Forward Check SS Indication Indication . . . . . . . . . . . . . . . . 1574.6.91 Forward Check SS Indication Response . . . . . . . . . . . . . . . . . 1584.6.92 Forward Check SS Indication Confirmation . . . . . . . . . . . . . 1594.6.93 Forward Group Call Signalling Request . . . . . . . . . . . . . . . . . 1604.6.94 Forward Group Call Signalling Indication . . . . . . . . . . . . . . . 1614.6.95 Forward Group Call Signalling Response . . . . . . . . . . . . . . . 1624.6.96 Forward Group Call Signalling Confirmation . . . . . . . . . . . 1634.6.97 Forward New IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644.6.98 Forward New IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 1654.6.99 Forward New IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664.6.100 Forward New IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . 1674.6.101 Obtain IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684.6.102 Obtain IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694.6.103 Obtain IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.6.104 Obtain IEMI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714.6.105 Get Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.6.106 Get Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
viii Mobile Application Part Interface (MAPI)
4.6.107 Get Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.6.108 Get Password Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754.6.109 Inform Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . 1764.6.110 Inform Service Center Indication . . . . . . . . . . . . . . . . . . . . . . 1774.6.111 Inform Service Center Response . . . . . . . . . . . . . . . . . . . . . . . 1784.6.112 Inform Service Center Confirmation . . . . . . . . . . . . . . . . . . . 1794.6.113 Insert Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . 1804.6.114 Insert Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . 1814.6.115 Insert Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . 1824.6.116 Insert Subscriber Data Confirmation . . . . . . . . . . . . . . . . . . 1834.6.117 Iterrogate Supplementary Service Request . . . . . . . . . . . . . 1844.6.118 Iterrogate Supplementary Service Indication . . . . . . . . . . . 1854.6.119 Iterrogate Supplementary Service Response . . . . . . . . . . . . 1864.6.120 Iterrogate Supplementary Service Confirmation . . . . . . . . 1874.6.121 IST Alert Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884.6.122 IST Alert Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894.6.123 IST Alert Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904.6.124 IST Alert Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914.6.125 IST Command Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924.6.126 IST Command Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1934.6.127 IST Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944.6.128 IST Command Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 1954.6.129 Note MM Event Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1964.6.130 Note MM Event Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974.6.131 Note MM Event Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984.6.132 Note MM Event Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . 1994.6.133 Mobile Originated Forward Short Message Request . . . . 2004.6.134 Mobile Originated Forward Short Message Indication . . 2014.6.135 Mobile Originated Forward Short Message Response . . . 2024.6.136 Mobile Originated Forward Short Message Confirmation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2034.6.137 Note MS Present for GRPS Request . . . . . . . . . . . . . . . . . . 2044.6.138 Note MS Present for GRPS Indication . . . . . . . . . . . . . . . . 2054.6.139 Note MS Present for GRPS Response . . . . . . . . . . . . . . . . . 2064.6.140 Note MS Present for GRPS Confirmation . . . . . . . . . . . . . 2074.6.141 Mobile Terminated Forward Short Message Request . . . 2084.6.142 Mobile Terminated Forward Short Message Indication
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094.6.143 Mobile Terminated Forward Short Message Response . . 2104.6.144 Mobile Terminated Forward Short Message Confirmation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114.6.145 Page Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124.6.146 Page Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134.6.147 Page Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2144.6.148 Page Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154.6.149 Prepare Group Call Request . . . . . . . . . . . . . . . . . . . . . . . . . . 2164.6.150 Prepare Group Call Indication . . . . . . . . . . . . . . . . . . . . . . . . 2174.6.151 Prepare Group Call Response . . . . . . . . . . . . . . . . . . . . . . . . . 218
ix
4.6.152 Prepare Group Call Confirmation . . . . . . . . . . . . . . . . . . . . . 2194.6.153 Prepare Handover Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2204.6.154 Prepare Handover Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 2214.6.155 Prepare Handover Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 2224.6.156 Prepare Handover Confirmation . . . . . . . . . . . . . . . . . . . . . . . 2234.6.157 Prepare Subsequent Handover Request . . . . . . . . . . . . . . . . 2244.6.158 Prepare Subsequent Handover Indication . . . . . . . . . . . . . . 2254.6.159 Prepare Subsequent Handover Response . . . . . . . . . . . . . . . 2264.6.160 Prepare Subsequent Handover Confirmation . . . . . . . . . . . 2274.6.161 Process Access Signalling Request . . . . . . . . . . . . . . . . . . . . . 2284.6.162 Process Access Signalling Indication . . . . . . . . . . . . . . . . . . . 2294.6.163 Process Access Signalling Response . . . . . . . . . . . . . . . . . . . . 2304.6.164 Process Access Signalling Confirmation . . . . . . . . . . . . . . . . 2314.6.165 Process Group Call Signalling Request . . . . . . . . . . . . . . . . 2324.6.166 Process Group Call Signalling Indication . . . . . . . . . . . . . . 2334.6.167 Process Group Call Signalling Response . . . . . . . . . . . . . . . 2344.6.168 Process Group Call Signalling Confirmation . . . . . . . . . . . 2354.6.169 Process Unstructured SS Request . . . . . . . . . . . . . . . . . . . . . 2364.6.170 Process Unstructured SS Indication . . . . . . . . . . . . . . . . . . . 2374.6.171 Process Unstructured SS Response . . . . . . . . . . . . . . . . . . . . 2384.6.172 Process Unstructured SS Confirmation . . . . . . . . . . . . . . . . 2394.6.173 Provide IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404.6.174 Provide IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2414.6.175 Provide IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424.6.176 Provide IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434.6.177 Provide Roaming Number Request . . . . . . . . . . . . . . . . . . . . 2444.6.178 Provide Roaming Number Indication . . . . . . . . . . . . . . . . . . 2454.6.179 Provide Roaming Number Response . . . . . . . . . . . . . . . . . . . 2464.6.180 Provide Roaming Number Confirmation . . . . . . . . . . . . . . . 2474.6.181 Provide Subscriber Location Request . . . . . . . . . . . . . . . . . . 2484.6.182 Provide Subscriber Location Indication . . . . . . . . . . . . . . . . 2494.6.183 Provide Subscriber Location Response . . . . . . . . . . . . . . . . 2504.6.184 Provide Subscriber Location Confirmation . . . . . . . . . . . . . 2514.6.185 Provide Subscriber Information Request . . . . . . . . . . . . . . . 2524.6.186 Provide Subscriber Information Indication . . . . . . . . . . . . . 2534.6.187 Provide Subscriber Information Response . . . . . . . . . . . . . 2544.6.188 Provide Subscriber Information Confirmation . . . . . . . . . . 2554.6.189 Purge MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564.6.190 Purge MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2574.6.191 Purge MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2584.6.192 Purge MS Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2594.6.193 Ready for SM Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2604.6.194 Ready for SM Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2614.6.195 Ready for SM Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2624.6.196 Ready for SM Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2634.6.197 Register CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 2644.6.198 Register CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . 2654.6.199 Register CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . 266
x Mobile Application Part Interface (MAPI)
4.6.200 Register CC Entry Confirmation . . . . . . . . . . . . . . . . . . . . . . 2674.6.201 Register Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2684.6.202 Register Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 2694.6.203 Register Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . 2704.6.204 Register Password Confirmation . . . . . . . . . . . . . . . . . . . . . . . 2714.6.205 Register Supplementary Service Request . . . . . . . . . . . . . . 2724.6.206 Register Supplementary Service Indication . . . . . . . . . . . . 2734.6.207 Register Supplementary Service Response . . . . . . . . . . . . . 2744.6.208 Register Supplementary Service Confirmation . . . . . . . . . 2754.6.209 Remote User Free Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2764.6.210 Remote User Free Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 2774.6.211 Remote User Free Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 2784.6.212 Remote User Free Confirmation . . . . . . . . . . . . . . . . . . . . . . . 2794.6.213 Send Identification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 2804.6.214 Send Identification Indication . . . . . . . . . . . . . . . . . . . . . . . . . 2814.6.215 Send Identification Response . . . . . . . . . . . . . . . . . . . . . . . . . . 2824.6.216 Send Identification Confirmation . . . . . . . . . . . . . . . . . . . . . . 2834.6.217 Set Ciphering Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . 2844.6.218 Set Ciphering Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . 2854.6.219 Set Ciphering Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . 2864.6.220 Set Ciphering Mode Confirmation . . . . . . . . . . . . . . . . . . . . . 2874.6.221 Set Reporting State Request . . . . . . . . . . . . . . . . . . . . . . . . . . 2884.6.222 Set Reporting State Indication . . . . . . . . . . . . . . . . . . . . . . . . 2894.6.223 Set Reporting State Response . . . . . . . . . . . . . . . . . . . . . . . . . 2904.6.224 Set Reporting State Confirmation . . . . . . . . . . . . . . . . . . . . . 2914.6.225 Report Short Message Delivery Status Request . . . . . . . . 2924.6.226 Report Short Message Delivery Status Indication . . . . . . 2934.6.227 Report Short Message Delivery Status Response . . . . . . . 2944.6.228 Report Short Message Delivery Status Confirmation . . . 2954.6.229 Send Authentication Information Request . . . . . . . . . . . . . 2964.6.230 Send Authentication Information Indication . . . . . . . . . . . 2974.6.231 Send Authentication Information Response . . . . . . . . . . . . 2984.6.232 Send Authentication Information Confirmation . . . . . . . . 2994.6.233 Send End Signal Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3004.6.234 Send End Signal Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 3014.6.235 Send End Signal Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3024.6.236 Send End Signal Confirmation . . . . . . . . . . . . . . . . . . . . . . . . 3034.6.237 Send Group Call End Signal Request . . . . . . . . . . . . . . . . . . 3044.6.238 Send Group Call End Signal Indication . . . . . . . . . . . . . . . . 3054.6.239 Send Group Call End Signal Response . . . . . . . . . . . . . . . . 3064.6.240 Send Group Call End Signal Confirmation . . . . . . . . . . . . . 3074.6.241 Send Routing Information for GPRS Request . . . . . . . . . . 3084.6.242 Send Routing Information for GPRS Indication . . . . . . . 3094.6.243 Send Routing Information for GPRS Response . . . . . . . . 3104.6.244 Send Routing Information for GPRS Confirmation . . . . 3114.6.245 Send Handover Report Request . . . . . . . . . . . . . . . . . . . . . . . 3124.6.246 Send Handover Report Indication . . . . . . . . . . . . . . . . . . . . . 3134.6.247 Send Handover Report Response . . . . . . . . . . . . . . . . . . . . . . 314
xi
4.6.248 Send Handover Report Confirmation . . . . . . . . . . . . . . . . . . 3154.6.249 Send IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3164.6.250 Send IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3174.6.251 Send IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3184.6.252 Send IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3194.6.253 Send Routing Information for LCS Request . . . . . . . . . . . 3204.6.254 Send Routing Information for LCS Indication . . . . . . . . . 3214.6.255 Send Routing Information for LCS Response . . . . . . . . . . 3224.6.256 Send Routing Information for LCS Confirmation . . . . . . 3234.6.257 Send Mobile Originated SMS Information Request . . . . . 3244.6.258 Send Mobile Originated SMS Information Indication . . . 3254.6.259 Send Mobile Originated SMS Information Response . . . 3264.6.260 Send Mobile Originated SMS Information Confirmation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3274.6.261 Send Mobile Terminated SMS Information Request . . . . 3284.6.262 Send Mobile Terminated SMS Information Indication . . 3294.6.263 Send Mobile Terminated SMS Information Response . . . 3304.6.264 Send Mobile Terminated SMS Information Confirmation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3314.6.265 Send Routing Information Request . . . . . . . . . . . . . . . . . . . . 3324.6.266 Send Routing Information Indication . . . . . . . . . . . . . . . . . . 3334.6.267 Send Routing Information Response . . . . . . . . . . . . . . . . . . . 3344.6.268 Send Routing Information Confirmation . . . . . . . . . . . . . . . 3354.6.269 Send Routing Information for SM Request . . . . . . . . . . . . 3364.6.270 Send Routing Information for SM Indication . . . . . . . . . . 3374.6.271 Send Routing Information for SM Response . . . . . . . . . . . 3384.6.272 Send Routing Information for SM Confirmation . . . . . . . 3394.6.273 SS Invocation Notification Request . . . . . . . . . . . . . . . . . . . . 3404.6.274 SS Invocation Notification Indication . . . . . . . . . . . . . . . . . . 3414.6.275 SS Invocation Notification Response . . . . . . . . . . . . . . . . . . . 3424.6.276 SS Invocation Notification Confirmation . . . . . . . . . . . . . . . 3434.6.277 Status Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3444.6.278 Status Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3454.6.279 Status Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3464.6.280 Status Report Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3474.6.281 Subscriber Location Report Request . . . . . . . . . . . . . . . . . . 3484.6.282 Subscriber Location Report Indication . . . . . . . . . . . . . . . . 3494.6.283 Subscriber Location Report Response . . . . . . . . . . . . . . . . . 3504.6.284 Subscriber Location Report Confirmation . . . . . . . . . . . . . 3514.6.285 Note Subscriber Data Modified Request . . . . . . . . . . . . . . . 3524.6.286 Note Subscriber Data Modified Indication . . . . . . . . . . . . . 3534.6.287 Note Subscriber Data Modified Response . . . . . . . . . . . . . . 3544.6.288 Note Subscriber Data Modified Confirmation . . . . . . . . . . 3554.6.289 Trace Subscriber Activity Request . . . . . . . . . . . . . . . . . . . . 3564.6.290 Trace Subscriber Activity Indication . . . . . . . . . . . . . . . . . . 3574.6.291 Trace Subscriber Activity Response . . . . . . . . . . . . . . . . . . . 3584.6.292 Trace Subscriber Activity Confirmation . . . . . . . . . . . . . . . 3594.6.293 Update GPRS Location Request . . . . . . . . . . . . . . . . . . . . . . 360
xii Mobile Application Part Interface (MAPI)
4.6.294 Update GPRS Location Indication . . . . . . . . . . . . . . . . . . . . 3614.6.295 Update GPRS Location Response . . . . . . . . . . . . . . . . . . . . . 3624.6.296 Update GPRS Location Confirmation . . . . . . . . . . . . . . . . . 3634.6.297 Update Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3644.6.298 Update Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 3654.6.299 Update Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3664.6.300 Update Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . 3674.6.301 Unstructured Supplementary Service Notify Request . . . 3684.6.302 Unstructured Supplementary Service Notify Indication
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3694.6.303 Unstructured Supplementary Service Notify Response
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3704.6.304 Unstructured Supplementary Service Notify Confirmation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3714.6.305 Unstructured Supplementary Service Request . . . . . . . . . 3724.6.306 Unstructured Supplementary Service Indication . . . . . . . 3734.6.307 Unstructured Supplementary Service Response . . . . . . . . 3744.6.308 Unstructured Supplementary Service Confirmation . . . . 375
5 Diagnostics Requirements . . . . . . . . . . . . . . . . . . . 3775.1 Non-Fatal Error Handling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3775.2 Fatal Error Handling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Addendum for 3GPP Conformance . . . . . . . . . . . . 381
Appendix A Mapping MAPI Primitives to3GPP TS 29.002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
A.1 Application Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Appendix B State/Event Tables . . . . . . . . . . . . . . 393
Appendix C Primitive Precedence Tables . . . 395
Appendix D MAPI Header File Listing . . . . . . 397
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399GNU Free Documentation License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399Terms and Conditions for Copying, Distribution and Modification
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399How to use this License for your documents . . . . . . . . . . . . . . . . . . . . 405
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Mobile Application Part Interface (MAPI) Table of Contents
List of Figures
2008-10-31 1
List of Tables
2 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Preface
Preface
Security Warning
Permission to use, copy and distribute this documentation without modification, for anypurpose and without fee or royalty is hereby granted, provided that both the above copy-right notice and this permission notice appears in all copies and that the name of OpenSS7Corporation not be used in advertising or publicity pertaining to distribution of this docu-mentation or its contents without specific, written prior permission. OpenSS7 Corporationmakes no representation about the suitability of this documentation for any purpose. It isprovided “as is” without express or implied warranty.
OpenSS7 Corporation disclaims all warranties with regard to this documentation includingall implied warranties of merchantability, fitness for a particular purpose, non-infringement,or title; that the contents of the document are suitable for any purpose, or that the im-plementation of such contents will not infringe on any third party patents, copyrights,trademarks or other rights. In no event shall OpenSS7 Corporation be liable for any di-rect, indirect, special or consequential damages or any damages whatsoever resulting fromloss of use, data or profits, whether in an action of contract, negligence or other tortiousaction, arising out of or in connection with any use of this document or the performance orimplementation of the contents thereof.
OpenSS7 Corporation is making this documentation available as a reference point for theindustry. While OpenSS7 Corporation believes that these interfaces are well defined in thisrelease of the document, minor changes may be made prior to products conforming to theinterfaces being made available.
Abstract
This document is a Specification containing technical details concerning the implementationof the Mobile Application Part Interface (MAPI) for OpenSS7. It contains recommenda-tions on software architecture as well as platform and system applicability of the MobileApplication Part Interface (MAPI).
Purpose
The purpose of this document is to provide technical documentation of the Mobile Appli-cation Part Interface (MAPI). This document is intended to be included with the OpenSS7STREAMS software package released by OpenSS7 Corporation. It is intended to assist soft-ware developers, maintainers and users of the Mobile Application Part Interface (MAPI)with understanding the software architecture and technical interfaces that are made avail-able in the software package.
Intent
It is the intent of this document that it act as the primary source of information concern-ing the Mobile Application Part Interface (MAPI). This document is intended to provide
2008-10-31 3
Preface
information for writers of OpenSS7 Mobile Application Part Interface (MAPI) applicationsas well as writers of OpenSS7 Mobile Application Part Interface (MAPI) Users.
Audience
The audience for this document is software developers, maintainers and users and integratorsof the Mobile Application Part Interface (MAPI). The target audience is developers andusers of the OpenSS7 SS7 stack.
Disclaimer
Although the author has attempted to ensure that the information in this document is com-plete and correct, neither the Author nor OpenSS7 Corporation will take any responsibilityin it.
Revision History
Take care that you are working with a current version of this documentation: you will notbe notified of updates. To ensure that you are working with a current version, check theOpenSS7 Project website for a current version.Only the texinfo or roff source is controlled. A printed (or postscript) version of thisdocument is an UNCONTROLLED VERSION.
mapi.texi,v
Revision 0.9.2.14 2008-09-20 11:04:29 brian
- added package patchlevel
Revision 0.9.2.13 2008-08-03 06:03:30 brian
- protected agains texinfo commands in log entries
Revision 0.9.2.12 2008-08-03 05:05:14 brian
- conditional @syncodeindex frags out automake, fails distcheck
Revision 0.9.2.11 2008-07-11 09:36:11 brian
- updated documentation
Revision 0.9.2.10 2008-04-29 07:10:38 brian
- updating headers for release
Revision 0.9.2.9 2007/06/27 08:42:10 brian
- added MTPI spec document
Revision 0.9.2.8 2007/03/17 08:31:39 brian
- corrected formatting problems
Revision 0.9.2.7 2006/08/26 09:17:14 brian
- better release file generation
Revision 0.9.2.6 2006/08/22 12:44:17 brian
- documentation updates
Revision 0.9.2.5 2006/01/04 08:04:14 brian
- corrected documentation
4 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Preface
2008-10-31 5
Mobile Application Part Interface (MAPI) Introduction
1 Introduction
This document specifies a STREAMS-based kernel-level instantiation of the 3GPPGSM/UMTS TS.29002 Mobile Application Part (MAP) service definition. The MobileApplication Part Interface (MAPI) enables the user of a mobile application serviceto access and use a wide variety of conforming mobile application service providerswithout specific knowledge of the provider’s protocol. The service interface is designed tosupport any operation class of transaction protocol. This interface only specifies access tomobile application layer service providers, and does not address issues concerning mobileapplication layer management, protocol performance, and performance analysis tools.This specification assumes that the reader is familiar with the 3GPP GSM/UTMS referencepoints and 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 MobileApplications Part (MAP) specification for 3GPP GSM/UMTS as described in 3GPP TS29.002. These specifications are targeted for use by developers and testers of protocolmodules that require Mobile Applications 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
2008-10-31 7
Chapter 1: Introduction
MTP Message Transfer Part
TR Transaction Sub-Layer
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 UserA 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
STREAMSA communication services development facility first available with UNIX Sys-tem V Release 3.
8 Version 0.9a Rel. 8
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 mobilenetwork. It is responsible for the routing and management of data exchange between theMAP-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 ofprimitives defined as STREAMS messages that provide access to the MAP layer services,and are transferred between the MAP user entity and the MAP provider. These primitivesare of two types: ones that originate from the MAP user, and others that originate fromthe MAP provider. The primitives that originate from the MAP user make requests to theMAP provider, or respond to an event of the MAP provider. The primitives that originatefrom the MAP provider are either confirmation of a request or are indications to the MAPuser that the event has occurred. Figure 1 shows the model of the MAPI. (See Section“Modelling Principles” in 3GPP TS 29.002 V6.6.0.)� �
Figure 1 – Module of the MAP Interface
Indication/ConfirmationPrimitives
Request/ResponsePrimitives
TC User
MAPProvider
Full Duplex ConnectionMAPI
MAPUser
Application Context
The MAPI allows the MAP provider to be configured with any MAP user (such as an HLR,MSC or SGSN application) that also conforms to the MAPI. A MAP user can also be a
2008-10-31 9
Chapter 2: The Mobile Application Layer
user program that conforms to the MAPI and accesses the MAP provider using ‘putmsg()’and ‘getmsg()’ system calls.1
2.2 MAP Services
The features of the MAP are defined in terms of the services provided by the MAP provider,and the 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 corre-sponding to the 3GPP TS 29.002 Mobile Application Part application contexts. In addition,the MAP supports services 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 allapplication contexts. 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
1 See Section “putmsg(2)” in The UNIX Manual Pages, also see Section “getmsg(2)” in The UNIX ManualPages.
10 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) The Mobile Application Layer
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
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 SGSN
2008-10-31 11
Chapter 2: The Mobile Application Layer
MAP 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 MSCMAP 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 HLR
12 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) The Mobile Application Layer
MAP 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-AMAP 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 Performer
2008-10-31 13
Chapter 2: The Mobile Application Layer
MAP 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
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 HLR
14 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) The Mobile Application Layer
MAP-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 VLRVLR MSC
MAP USSDNTFY SCF HLRHLR 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 VLR
2008-10-31 15
Chapter 2: The Mobile Application Layer
MAP 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.
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
16 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) The Mobile Application Layer
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-AMAP 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 HLR
2008-10-31 17
Chapter 2: The Mobile Application Layer
MAP 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 VLRMAP 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 SCF
18 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) The Mobile Application Layer
MAP 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
Table 4. VLR invoked services.
Service Invoker PerformerMAP UDLOC VLR HLRMAP SENDID VLR old VLRMAP PURGEMS VLR HLR
2008-10-31 19
Chapter 2: The Mobile Application Layer
MAP 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 SGSNMAP DELSUBD HLR SGSN
20 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) The Mobile Application Layer
MAP 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 ServiceService Sets
Table X. SMS-IWMSC performed services.
Service Invoker PerformerMAP MOFSMS MSC SMS-IWMSCMAP ALERTSC HLR SMS-IWMSC
2008-10-31 21
Chapter 2: The Mobile Application Layer
2.4.8 Gateway MSC (GMSC) for Short Message Service ServiceSets
Table X. SMS-GMSC performed services.
Service Invoker PerformerMAP INFORMSC HLR SMS-GMSC
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
22 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Services Definition
3 MAPI Services Definition
This chapter describes the services of the MAP primitives. Time-sequence diagrams thatillustrate the sequence of primitives is included. (Conventions for the time-sequence dia-grams are defined in ITU-T X.210). The format of the primitives will be defined later inthe document.
3.1 Local Management Services Definition
The services defined in this section are outside the scope of the international standards.These services apply to all applications contexts and specific service primitives. They areinvoked for the initialization or de-initialization of a stream connected to the MAP provider.They are also used to manage options supported by the MAP provider and to report infor-mation on the supported parameter 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 allthe supported 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 returnsthe values of the supported protocol parameters to the MAP user.
The sequence of primitives for mobile application part information management is shownin Figure 2.� �
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 astream. It allows the MAP user to negotiate the number of dialogues that can remain out-standing for that MAP user (a dialogue is considered unacknowledged while it is awaitinga corresponding response or abort from the MAP user). This service also defines a mecha-nism that allows a stream (bound to a network address of the MAP user) to be reserved tohandle remote initiated dialogues only. This stream is referred to as the listener stream.
• MAP_BIND_REQ: This primitive requests that the MAP user be bound to a particu-lar network address and application context, and negotiate the number of allowableoutstanding open indications for that address.
• MAP_BIND_ACK: This primitive is in response to the MAP_BIND_REQ primitive and indi-cates to the user that the specified MAP user has been bound to a network addressand application context.
The sequence of primitives for the MAP user bind service is shown in Figure 3.
2008-10-31 23
Chapter 3: MAPI Services Definition� �Figure 2. Sequence of Primitives;
MAP User Bind Service 3.1.3 MAP User Unbind Service
This service allows the MAP user to be unbound from a network address and applicationcontext.
• MAP_UNBIND_REQ: This primitive requests that the MAP user be unbound from thenetwork address 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 useroriginated primitive was received successfully by the MAP provider.
An example showing the sequence of primitives for successful receipt acknowledgement isdepicted in Figure 4.
3.1.5 Options Management Service
This service allows the MAP user to manage the QOS parameter values and other optionsassociated with the MAP provider.
• MAP_OPTMGMT_REQ: This primitive allows the MAP user to select default values forQoS parameters within the range supported by the MAP provider, and to indicate thedefault selection of additional 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 hasoccurred in the last MAP user originated request or response primitive (listed in Figure6), on the stream.
Figure 6 shows the sequence of primitives for the error acknowledgement service.� �Figure 6. Sequence of Primitives;Error Acknowledgement Service.
24 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Services Definition
3.2 Dialogue Handling Definition
This section describes the required MAP service primitives that define the Dialogue Han-dling interface.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 pairof queues linking the two MAP user entities. There is one queue for each direction ofinformation flow. Each queue represents a flow control function in one direction of transfer.The ability of a user to add objects to a queue will be determined by the behaviour of theuser removing objects from that queue, and the state of the queue. The pair of queues isconsidered to be available for each potential MAP dialogue. Objects that are entered orremoved from the queue are either as a result of interactions at the two MAP users, or asa 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,
subject to 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 as they 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 thesame type), or
— if the following object is defined to be destructive with respect to the precedingobject on the queue. If necessary, the last object on the queue will be deleted toallow a destructive object to be entered – the will therefore always be added to thequeue. For example, “abort” objects are defined to be destructive with respect toall 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 precedingObject Y.
DES Indicates that Object X is defined to be destructive with respect to the preced-ing Object Y.
2008-10-31 25
Chapter 3: MAPI Services Definition
– Indicates that Object X is neither destructive with respect to Object Y, norable to advance ahead of Object Y.
N/A Indicates that Object X will not occur in a position succeeding Object Y in avalid state of a queue.
3.2.1 Dialogue Establishment Phase
A pair of queues is associated with a MAP dialogue between two MAP user entities whenthe MAP provider receives a MAP_OPEN_REQ primitive at one of the MAP user interfacesresulting in the “begin” object being entered into the queue. The queues will remainassociated with the MAP dialogue until a MAP_CLOSE_REQ or indication primitive (resultingin an “end” object) is either entered or removed from a queue. Similarly, in the queue fromthe called MAP user, objects can be entered into the queue only after the “continue” objectassociated with the MAP_OPEN_RES primitive has been entered into the queue. Alternatively,the called MAP user can enter a an “end” or “abort” object into the queue instead of the“continue” object to terminate the dialogue.The MAP dialogue establishment procedure will fail if the MAP provider is unable toestablish a TCAP dialogue, or if the destination MAP user is unable to accept the MAP_OPEN_IND.
3.2.1.1 User Primitives for Successful MAP DialogueEstablishment
• MAP_OPEN_REQ: This primitive requests that the MAP provider establish a dialogue tothe specified destination under an application context.
• MAP_OPEN_RES: This primitives requests that the MAP provider accept a previousdialogue indication.
3.2.1.2 Provider Primitives for Successful MAP DialogueEstablishment
• MAP_OPEN_IND: This primitive indicates to the MAP user that a dialogue request hasbeen made 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 hasbeen confirmed on the specified responding address.
The sequence of primitives for a successful MAP dialogue establishment is defined by thetime sequence diagram as shown in Figure 7. The sequence of primitives for the MAPdialogue response token value determination is shown in Figure 8 (procedures for MAPresponse token value determination are discussed later).� �
Figure 7. Sequence of Primitives;Successful MAP Dialogue Establishment � �
Figure 8. Sequence of Primitives;MAP Dialogue Response Token Value Determination
26 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Services Definition
3.2.2 Dialogue Component Transfer Phase
Flow control within the MAP dialogue is performed by management of the queue capacity,and by allowing 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 aservice and transfer the specified (and any subsequent) components.
• Service Specific Responses: These primitives request that the MAP provider returnresult for a service invocation and transfer the specified (and any subsequent) compo-nents.
• MAP_DELIM_IND: This primitive requests that the MAP provider deliver any accumu-lated components from previous service specific request or response primitives.
3.2.2.2 Provider Primitives for Component Transfer
• Service Specific Indications: These primitives indicate to the MAP user an invocationand the indicated (and any subsequent) components.
• Service Specific Confirmations: These primitives indicate to the MAP user a returnresult and the indicated (and any subsequent) components.
• MAP_DELIM_IND: This primitive indicates that the MAP provider has delivered anyaccumulated components belonging to the previous service specific indication or con-firmation primitive.
Figure 9 shows the sequence of primitives for successful component transfer. The sequenceof primitives 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 sequencediagram as shown in Figure 10.� �
Figure 10. Sequence of Primitives;Successful Confirmation of Receipt.
2008-10-31 27
Chapter 3: MAPI Services Definition
The sequence of primitives as shown above may remain incomplete if a MAP_UABORT, MAP_PABORT or MAP_CLOSE primitive occurs (see Table 3). A MAP user must not issue a ServiceSpecific Response primitive if no Service Specific Indication primitive for a confirmed servicehas been received, or if all such Service Specific Indication primitives have been previouslyconfirmed. Following a MAP_UABORT or MAP_PABORT, a MAP user may not issue a ServiceSpecific Response to confirm outstanding Service Specific Indication primitives receivedbefore the abort procedure was signalled.
Note — The witholding of confirmation of a service by a MAP user can have an effect onthe attainable throughput.
The sequence of primitives for component transfer is shown in the time sequence diagram inFigure 11. This sequence of primitives may remain incomplete if a MAP_ABORT or MAP_CLOSEprimitive is issued.� �
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”object into the queue. As shown in Table 3, the “abort” is destructive with respect to otherobjects in the queue, and eventually results in the emptying of queues and termination ofthe MAP dialogue.
The sequence of primitivies depends on the origin of the release action. The sequence ofprimitives may be:
1. invoked by one MAP user, with a request from that MAP user leading to an indicationto the other;
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 fromthe originating MAP user and an indication to the other.
3.2.3.1 User Primitives for Dialogue Abort
• MAP_ABORT_REQ: This primitive requests that the MAP provider deny an outstandingrequest for 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 forassociation has been denied or an existing association has been terminated.
• MAP_PABORT_IND: This primitive indicates to the MAP user that either a request forassociation has 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, 18and 19.
28 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Services Definition� �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 originator parameter in the MAP_UABORT_IND primitive will indicate MAP user invokedrelease. The sequence 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 therequester by a MAP_PABORT_IND. The originator in this primitive indicates a MAP providerinvoked release. This is shown in Figure 21.� �
Figure 21. Sequence of Primitives;MAP Provider Rejection of a MAP Association Establishement Attempt.
2008-10-31 29
Mobile Application Part Interface (MAPI) MAPI Primitives
4 MAPI Primitives
This section describes the format and parameters of the MAPI primitives (Appendix Ashows the mapping of the MAPI primitives to the primitives defined in 3GPP TS 29.002and ANSI41-D). Also, it discusses the states in which the primitive is valid, the resultingstate and the acknowledgement that the primitive expects. (The state/event tables for theseprimitives are shown in Appendix B. The precedence tables for the MAPI primitives areshown in Appendix C.) Rules for 3GPP and ANSI conformance are described in Addendumto this document.
Tabel 4. Local Management Service Primitives.
SERVICE PRIMITIVE PARAMETERSInformation MAP_INFO_REQReporting MAP_INFO_ACKBind MAP_BIND_REQ
MAP_BIND_ACKUnbind MAP_UNBIND_REQError MAP_ERROR_ACKSuccess 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, Originat-ing address, Originating reference, Specificinformation)
Establishment MAP_OPEN_IND (Application context name, Destinationaddress, Destination reference, Originat-ing address, Originating reference, Specificinformation)
MAP_OPEN_RES (Application context name, Respondingaddress, Result, Refuse-reason, Specificinformation)
MAP_OPEN_CON (Application context name, Respondingaddress, Result, Refuse-reason, Specific in-formation, 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)
2008-10-31 31
Chapter 4: MAPI Primitives
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)Termination MAP_CLOSE_IND (Specific information)Assocation MAP_ABORT_REQ (User reason, Diagnostic information, Spe-
cific information)Abort MAP_UABORT_IND (User reason, Diagnostic information, Spe-
cific information)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_INDClass 2 MAP_STC2_REQ
MAP_STC2_INDClass 3 MAP_STC3_REQ
MAP_STC3_INDClass 4 MAP_STC4_REQ
MAP_STC4_IND
32 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
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 protocolparameters (see Section 4.1.2 [Information Acknowledgement], page 34), and also the currentstate of the MAP provider.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 acknowledgementsupon receipt of the pirmitive:— Successful: Acknowledgement of the primitive with the MAP_INFO_ACK primitive de-
scribed in Section 4.1.2 [Information Acknowledgement], page 34.— 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 393.
2008-10-31 33
Chapter 4: MAPI Primitives
4.1.2 Information Acknowledgement
MAP INFO ACK
This primitive indicates to the MAP users any relevant protocol-dependent parameters.1
It should be initiated in response to the MAP_INFO_REQ primitive described above inSection 4.1.1 [Information Request], page 33.
Format
The format of the message is one ‘M_PCPROTO’ message block. The format of the ‘M_PCPROTO’message block 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 typeIndicates the primitive type.
TSDU sizeSpecifies the maximum size (in octets) of Transaction Service User Data sup-ported by the MAP provider.
ETSDU sizeSpecifies the maximum size (in octets) of Expedited Transaction Service UserData supported by the MAP provider.
CDATA sizeSpecifies the maximum number of octets of data that may be associated witha transaction initiation primitive for operations class 1, 2 and 3 operation.
1
34 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
DDATA sizeSpecifies the maximum number of octets of data that may be associated witha transaction termination primitive for operations class 1, 2 and 3 operation.
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_PCPROTOmessage block of the network address bound on the stream on which the MAP_INFO_REQ was issued (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 exceedthe tunable system limit, if non-zero, for the size of a STREAMS message.
SERV typeThis field specified the service type supported by the MAP provider, and is oneof the following:
CURRENT stateTHis is the current state of the MAP provider.
PROVIDER typeThis field specifies additional properties specific to the MAP provider and mayalter the way the MAP user communicates. MAP providers supporting thefeatures of XTI in XPG4 and beyond must send up a version number as specifiedbelow. The following flags may be set by the provider:
SENDZERO This flag indicates that the MAP provider support the sending ofzero-length (component-less) TSDUs.
XPG4_1 This indicates that the MAP provider conforms to XTI in XPG4and supports primitives MAP_ADDR_REQ and MAP_ADDR_ACK.
TODU sizePROTOID length, PROTOID offsetMAPI version
Flags
Valid States
New State
2 This is the amount of user components that may be present in a single service specific primitive.
2008-10-31 35
Chapter 4: MAPI Primitives
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.
36 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.1.3 Bind Application Context Request
MAP BIND REQ
This primitive requests that the MAP provider bind a protocol address to the stream,negotiate the number of dialogue open indications allowed to be outstanding by the MAPprovider for the specified protocol address, and activate1 the stream associated with theprotocol address.
Format
The format of the message is one ‘M_PROTO’ message block. The format of the ‘M_PROTO’message block 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 addressbegins. The address in the ‘M_PROTO’ message block is however, aligned the sameas it was received from the MAP user.
DIAIND number3 The requested number of connection indications4 allowed to be outstandingby the MAP provider for the specified protocol address.
Flags
Valid States
New State
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.
2008-10-31 37
Chapter 4: MAPI Primitives
Acknowledgements
This primitive requires the MAP provider to geenrate one of the following acknowledgementsupon receipt of the primitive, and the MAP user must wait for the acknowledgement beforeissuing any other primitive:— 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 39.
— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitivedescribed in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TBADADDR This indicates that the protocol address was in an incorrect format orthe address contained illegal information. It is not indended to indicateprotocol 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 ofthe requested address.
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
TADDRBUSYThis indicated that the requested address is already in use.
38 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.1.4 Bind Application Context Acknowledgement
MAP BIND ACK
This primitive indicates to the MAP user that the specified protoocl address has beenbound to the stream, that the specified number of dialogue open indications are allowedto be queued by the MAP provider for th specified protocol address, and that the streamassociated with the specified protocol address has ben activated.
Format
The format of the message is one ‘M_PCPROTO’ message block. The format of the ‘M_PCPROTO’message block 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
2008-10-31 39
Chapter 4: MAPI Primitives
4.1.5 Unbind Application Context Request
MAP UNBIND REQ
This primitive requests that the MAP provider unbind the protocol address associated withthe stream and deactivate the stream.
Format
The format of the message is one ‘M_PROTO’ message block. The format of the ‘M_PROTO’mesage block 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 uponreceipt of the primitive and that the MAP user must wait for the acknowledgement beforeissuing any other primitives:— Successful: Correct acknowledgement of the primitive is indicated with the MAP_OK_ACK
primitive described in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occurred and the UNIX system error is indicated in theprimitive.
40 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.1.6 Options Management Request
MAP OPTMGMT REQ
This primitive allows the MAP user to manage the options associated with the stream.
Format
The format of the message is one ‘M_PROTO’ message block. The format of the ‘M_PROTO’message block is as follows:
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
PRIM typeIndicates the primitive type.
OPT lengthThe length of the protocol options associated with the primitive.
OPT offsetThe offset from the beginning of the ‘M_PROTO’ message block where the optionsbegin. The proper alignment of options is not guaranteed. The options are,however, aligned the same as they were received from the MAP user.
MGMT flagsThe flags which define the request made by the MAP user.
Flags
T_NEGOTIATENegotiate and set the options with the MAP provider.
T_CHECK Check the validity of the specified options.
T_CURRENTReturn the options currently in effect.
T_DEFAULTReturn the default options.
Rules
For the rules governing the requests made by this primitive, see the MAP_OPTMGMT_ACKprimitive described in Section 4.1.9 [Options Management Acknowledgement], page 45.
Valid States
New State
2008-10-31 41
Chapter 4: MAPI Primitives
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledgementsupon receipt of the primitive and that the MAP user await the acknowledgement beforeissuing any othe primitives:— Successful: Acknowledgement of the primitive with the MAP_OPTMGMT_ACK primitive
described in Section 4.1.9 [Options Management Acknowledgement], page 45.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TACCES This indicates that the user did not have proper permissions for the use ofthe requested options.
TOUTSTATEThe primitive would place the MAP interface out of state.
TBADOPT This indicates that the options as specified were in an incorrect format, orthey contained 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 theprimitive.
TNOTSUPPORTThis MAP provider does not support the requested flag (T_CHECK or T_CURRENT).
42 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.1.7 Get Protocol Address Request
MAP ADDR REQ
This primitive requests that the MAP provider return the local protocol address that isbound to the stream and the address of the remote MAP entity if a dialogue has beenestablished.
Format
The format of the message is one ‘M_PROTO’ message block. The format of the ‘M_PROTO’message block is as follows:
typedef struct {
long PRIM_type; /* always MAP_ADDR_REQ */
} MAP_addr_req_t;
Parameters
PRIM typeIndicates the primitive type.
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other 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 44.
— Non-fatal errors: There are no errors associated with the issuance of this primitive.
2008-10-31 43
Chapter 4: MAPI Primitives
4.1.8 Get Protocol Address Acknowledgement
MAP ADDR ACK
Format
Parameters
Flags
Valid States
New State
44 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.1.9 Options Management Acknowledgement
MAP OPTMGMT ACK
Format
Parameters
Flags
Valid States
New State
2008-10-31 45
Chapter 4: MAPI Primitives
4.1.10 Error Acknowledgement
MAP ERROR ACK
Format
Parameters
Valid Error Codes
Valid States
New State
46 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.1.11 Successful Receipt Acknowledgement
MAP OK ACK
Format
Parameters
Valid States
New State
2008-10-31 47
Chapter 4: MAPI Primitives
4.2 Association Establishment Phase
4.2.1 Association Establishment Request
MAP OPEN REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Successful Association Establishment:
— Unsuccessful Association Establishment:
— Non-fatal errors:
48 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.2.2 Association Establishment Indication
MAP OPEN IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 49
Chapter 4: MAPI Primitives
4.2.3 Association Establishment Response
MAP OPEN RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
50 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.2.4 Association Establishment Confirmation
MAP OPEN CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 51
Chapter 4: MAPI Primitives
4.3 Component Transfer Phase
4.3.1 Component Delimitation Request
MAP DELIM REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
52 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.3.2 Component Delimitation Indication
MAP DELIM IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 53
Chapter 4: MAPI Primitives
4.4 Association Termination Phase
4.4.1 Association Release Request
MAP CLOSE REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
54 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.4.2 Association Release Indication
MAP CLOSE IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 55
Chapter 4: MAPI Primitives
4.4.3 Association Abort Request
MAP ABORT REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
56 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.4.4 Association User Abort Indication
MAP UABORT IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 57
Chapter 4: MAPI Primitives
4.4.5 Association Provider Abort Indication
MAP PABORT IND
Format
Parameters
Flags
Valid States
New State
58 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.4.6 Association Notice Indication
MAP NOTICE IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 59
Chapter 4: MAPI Primitives
4.5 Secure Transport Primitives
4.5.1 Secure Transport Class 1 Request
MAP STC1 REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
60 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.5.2 Secure Transport Class 1 Indication
MAP STC1 IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 61
Chapter 4: MAPI Primitives
4.5.3 Secure Transport Class 2 Request
MAP STC2 REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
62 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.5.4 Secure Transport Class 2 Indication
MAP STC2 IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 63
Chapter 4: MAPI Primitives
4.5.5 Secure Transport Class 3 Request
MAP STC3 REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
64 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.5.6 Secure Transport Class 3 Indication
MAP STC3 IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 65
Chapter 4: MAPI Primitives
4.5.7 Secure Transport Class 4 Request
MAP STC4 REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
66 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.5.8 Secure Transport Class 4 Indication
MAP STC4 IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 67
Chapter 4: MAPI Primitives
4.6 Service Specific Primitives
4.6.1 Activate Supplementary Service Request
MAP ACTSS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
68 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.2 Activate Supplementary Service Indication
MAP ACTSS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 69
Chapter 4: MAPI Primitives
4.6.3 Activate Supplementary Service Response
MAP ACTSS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
70 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.4 Activate Supplementary Service Confirmation
MAP ACTSS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 71
Chapter 4: MAPI Primitives
4.6.5 Activate Traceec Mode Request
MAP ACTTM REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
72 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.6 Activate Traceec Mode Indication
MAP ACTTM IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 73
Chapter 4: MAPI Primitives
4.6.7 Activate Traceec Mode Response
MAP ACTTM RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
74 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.8 Activate Traceec Mode Confirmation
MAP ACTTM CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 75
Chapter 4: MAPI Primitives
4.6.9 Alert Service Center Request
MAP ALERTSC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
76 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.10 Alert Service Center Indication
MAP ALERTSC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 77
Chapter 4: MAPI Primitives
4.6.11 Alert Service Center Response
MAP ALERTSC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
78 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.12 Alert Service Center Confirmation
MAP ALERTSC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 79
Chapter 4: MAPI Primitives
4.6.13 Allocate Handover Number Request
MAP ALLOCHN REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
80 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.14 Allocate Handover Number Indication
MAP ALLOCHN IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 81
Chapter 4: MAPI Primitives
4.6.15 Allocate Handover Number Response
MAP ALLOCHN RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
82 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.16 Allocate Handover Number Confirmation
MAP ALLOCHN CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 83
Chapter 4: MAPI Primitives
4.6.17 Any Time Modification Request
MAP ANYMOD REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
84 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.18 Any Time Modification Indication
MAP ANYMOD IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 85
Chapter 4: MAPI Primitives
4.6.19 Any Time Modification Response
MAP ANYMOD RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
86 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.20 Any Time Modification Confirmation
MAP ANYMOD CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 87
Chapter 4: MAPI Primitives
4.6.21 Any Time Interrogation Request
MAP ANYQRY REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
88 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.22 Any Time Interrogation Indication
MAP ANYQRY IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 89
Chapter 4: MAPI Primitives
4.6.23 Any Time Interrogation Response
MAP ANYQRY RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
90 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.24 Any Time Interrogation Confirmation
MAP ANYQRY CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 91
Chapter 4: MAPI Primitives
4.6.25 Any Time Subscription Interrogation Request
MAP ANYSUB REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
92 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.26 Any Time Subscription Interrogation Indication
MAP ANYSUB IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 93
Chapter 4: MAPI Primitives
4.6.27 Any Time Subscription Interrogation Response
MAP ANYSUB RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
94 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.28 Any Time Subscription Interrogation Confirmation
MAP ANYSUB CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 95
Chapter 4: MAPI Primitives
4.6.29 Authentication Failure Report Request
MAP AUTHFAIL REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
96 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.30 Authentication Failure Report Indication
MAP AUTHFAIL IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 97
Chapter 4: MAPI Primitives
4.6.31 Authentication Failure Report Response
MAP AUTHFAIL RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
98 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.32 Authentication Failure Report Confirmation
MAP AUTHFAIL CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 99
Chapter 4: MAPI Primitives
4.6.33 Authenticate Request
MAP AUTH REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
100 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.34 Authenticate Indication
MAP AUTH IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 101
Chapter 4: MAPI Primitives
4.6.35 Authenticate Response
MAP AUTH RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
102 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.36 Authenticate Confirmation
MAP AUTH CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 103
Chapter 4: MAPI Primitives
4.6.37 Cancel Location Request
MAP CANCLOC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
104 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.38 Cancel Location Indication
MAP CANCLOC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 105
Chapter 4: MAPI Primitives
4.6.39 Cancel Location Response
MAP CANCLOC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
106 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.40 Cancel Location Confirmation
MAP CANCLOC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 107
Chapter 4: MAPI Primitives
4.6.41 Reset Request
MAP RESET REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
108 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.42 Reset Indication
MAP RESET IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 109
Chapter 4: MAPI Primitives
4.6.43 Reset Response
MAP RESET CON
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
110 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.44 Reset Confirmation
MAP RESET RES
Format
Parameters
Flags
Valid States
New State
2008-10-31 111
Chapter 4: MAPI Primitives
4.6.45 Restore Request
MAP RESTORE REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
112 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.46 Restore Indication
MAP RESTORE IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 113
Chapter 4: MAPI Primitives
4.6.47 Restore Response
MAP RESTORE CON
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
114 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.48 Restore Confirmation
MAP RESTORE RES
Format
Parameters
Flags
Valid States
New State
2008-10-31 115
Chapter 4: MAPI Primitives
4.6.49 Resume Call Handling Request
MAP RESUME REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
116 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.50 Resume Call Handling Indication
MAP RESUME IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 117
Chapter 4: MAPI Primitives
4.6.51 Resume Call Handling Confirmation
MAP RESUME RES
Format
Parameters
Flags
Valid States
New State
118 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.52 Resume Call Handling Response
MAP RESUME CON
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
2008-10-31 119
Chapter 4: MAPI Primitives
4.6.53 Search for MS Request
MAP SEARCH REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
120 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.54 Search for MS Indication
MAP SEARCH IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 121
Chapter 4: MAPI Primitives
4.6.55 Search for MS Confirmation
MAP SEARCH RES
Format
Parameters
Flags
Valid States
New State
122 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.56 Search for MS Response
MAP SEARCH CON
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
2008-10-31 123
Chapter 4: MAPI Primitives
4.6.57 Check IEMI Request
MAP CKIEMI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
124 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.58 Check IEMI Indication
MAP CKIEMI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 125
Chapter 4: MAPI Primitives
4.6.59 Check IEMI Response
MAP CKIEMI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
126 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.60 Check IEMI Confirmation
MAP CKIEMI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 127
Chapter 4: MAPI Primitives
4.6.61 Deactivate Supplementary Service Request
MAP DEACTSS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
128 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.62 Deactivate Supplementary Service Indication
MAP DEACTSS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 129
Chapter 4: MAPI Primitives
4.6.63 Deactivate Supplementary Service Response
MAP DEACTSS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
130 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.64 Deactivate Supplementary Service Confirmation
MAP DEACTSS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 131
Chapter 4: MAPI Primitives
4.6.65 Deactivate Trace Mode Request
MAP DEACTTM REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
132 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.66 Deactivate Trace Mode Indication
MAP DEACTTM IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 133
Chapter 4: MAPI Primitives
4.6.67 Deactivate Trace Mode Response
MAP DEACTTM RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
134 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.68 Deactivate Trace Mode Confirmation
MAP DEACTTM CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 135
Chapter 4: MAPI Primitives
4.6.69 Delete Subscriber Data Request
MAP DELSUBD REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
136 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.70 Delete Subscriber Data Indication
MAP DELSUBD IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 137
Chapter 4: MAPI Primitives
4.6.71 Delete Subscriber Data Response
MAP DELSUBD RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
138 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.72 Delete Subscriber Data Confirmation
MAP DELSUBD CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 139
Chapter 4: MAPI Primitives
4.6.73 Erase CC Entry Request
MAP ERASECC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
140 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.74 Erase CC Entry Indication
MAP ERASECC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 141
Chapter 4: MAPI Primitives
4.6.75 Erase CC Entry Response
MAP ERASECC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
142 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.76 Erase CC Entry Confirmation
MAP ERASECC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 143
Chapter 4: MAPI Primitives
4.6.77 Erase Supplementatry Service Request
MAP ERASESS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
144 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.78 Erase Supplementatry Service Indication
MAP ERASESS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 145
Chapter 4: MAPI Primitives
4.6.79 Erase Supplementatry Service Response
MAP ERASESS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
146 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.80 Erase Supplementatry Service Confirmation
MAP ERASESS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 147
Chapter 4: MAPI Primitives
4.6.81 Failure Report Request
MAP FAILURE REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
148 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.82 Failure Report Indication
MAP FAILURE IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 149
Chapter 4: MAPI Primitives
4.6.83 Failure Report Response
MAP FAILURE RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
150 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.84 Failure Report Confirmation
MAP FAILURE CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 151
Chapter 4: MAPI Primitives
4.6.85 Forward Access Signalling Request
MAP FAS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
152 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.86 Forward Access Signalling Indication
MAP FAS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 153
Chapter 4: MAPI Primitives
4.6.87 Forward Access Signalling Response
MAP FAS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
154 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.88 Forward Access Signalling Confirmation
MAP FAS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 155
Chapter 4: MAPI Primitives
4.6.89 Forward Check SS Indication Request
MAP FCKSSIND REQ
Format
Parameters
Flags
Valid States
New State
156 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.90 Forward Check SS Indication Indication
MAP FCKSSIND IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 157
Chapter 4: MAPI Primitives
4.6.91 Forward Check SS Indication Response
MAP FCKSSIND RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
158 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.92 Forward Check SS Indication Confirmation
MAP FCKSSIND CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 159
Chapter 4: MAPI Primitives
4.6.93 Forward Group Call Signalling Request
MAP FGRCSIG REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
160 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.94 Forward Group Call Signalling Indication
MAP FGRCSIG IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 161
Chapter 4: MAPI Primitives
4.6.95 Forward Group Call Signalling Response
MAP FGRCSIG RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
162 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.96 Forward Group Call Signalling Confirmation
MAP FGRCSIG CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 163
Chapter 4: MAPI Primitives
4.6.97 Forward New IMSI Request
MAP FNEWIMSI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
164 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.98 Forward New IMSI Indication
MAP FNEWIMSI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 165
Chapter 4: MAPI Primitives
4.6.99 Forward New IMSI Response
MAP FNEWIMSI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
166 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.100 Forward New IMSI Confirmation
MAP FNEWIMSI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 167
Chapter 4: MAPI Primitives
4.6.101 Obtain IEMI Request
MAP GETIEMI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
168 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.102 Obtain IEMI Indication
MAP GETIEMI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 169
Chapter 4: MAPI Primitives
4.6.103 Obtain IEMI Response
MAP GETIEMI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
170 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.104 Obtain IEMI Confirmation
MAP GETIEMI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 171
Chapter 4: MAPI Primitives
4.6.105 Get Password Request
MAP GETPASS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
172 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.106 Get Password Indication
MAP GETPASS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 173
Chapter 4: MAPI Primitives
4.6.107 Get Password Response
MAP GETPASS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
174 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.108 Get Password Confirmation
MAP GETPASS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 175
Chapter 4: MAPI Primitives
4.6.109 Inform Service Center Request
MAP INFORMSC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
176 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.110 Inform Service Center Indication
MAP INFORMSC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 177
Chapter 4: MAPI Primitives
4.6.111 Inform Service Center Response
MAP INFORMSC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
178 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.112 Inform Service Center Confirmation
MAP INFORMSC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 179
Chapter 4: MAPI Primitives
4.6.113 Insert Subscriber Data Request
MAP INSSUBSD REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
180 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.114 Insert Subscriber Data Indication
MAP INSSUBSD IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 181
Chapter 4: MAPI Primitives
4.6.115 Insert Subscriber Data Response
MAP INSSUBSD RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
182 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.116 Insert Subscriber Data Confirmation
MAP INSSUBSD CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 183
Chapter 4: MAPI Primitives
4.6.117 Iterrogate Supplementary Service Request
MAP INTERGSS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
184 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.118 Iterrogate Supplementary Service Indication
MAP INTERGSS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 185
Chapter 4: MAPI Primitives
4.6.119 Iterrogate Supplementary Service Response
MAP INTERGSS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
186 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.120 Iterrogate Supplementary Service Confirmation
MAP INTERGSS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 187
Chapter 4: MAPI Primitives
4.6.121 IST Alert Request
MAP ISTALERT REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
188 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.122 IST Alert Indication
MAP ISTALERT IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 189
Chapter 4: MAPI Primitives
4.6.123 IST Alert Response
MAP ISTALERT RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
190 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.124 IST Alert Confirmation
MAP ISTALERT CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 191
Chapter 4: MAPI Primitives
4.6.125 IST Command Request
MAP ISTCMD REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
192 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.126 IST Command Indication
MAP ISTCMD IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 193
Chapter 4: MAPI Primitives
4.6.127 IST Command Response
MAP ISTCMD RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
194 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.128 IST Command Confirmation
MAP ISTCMD CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 195
Chapter 4: MAPI Primitives
4.6.129 Note MM Event Request
MAP MMEVENT REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
196 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.130 Note MM Event Indication
MAP MMEVENT IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 197
Chapter 4: MAPI Primitives
4.6.131 Note MM Event Response
MAP MMEVENT RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
198 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.132 Note MM Event Confirmation
MAP MMEVENT CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 199
Chapter 4: MAPI Primitives
4.6.133 Mobile Originated Forward Short Message Request
MAP MOFSMS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
200 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.134 Mobile Originated Forward Short Message Indication
MAP MOFSMS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 201
Chapter 4: MAPI Primitives
4.6.135 Mobile Originated Forward Short Message Response
MAP MOFSMS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
202 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.136 Mobile Originated Forward Short Message Confirmation
MAP MOFSMS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 203
Chapter 4: MAPI Primitives
4.6.137 Note MS Present for GRPS Request
MAP MSGRPSPRES REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
204 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.138 Note MS Present for GRPS Indication
MAP MSGRPSPRES IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 205
Chapter 4: MAPI Primitives
4.6.139 Note MS Present for GRPS Response
MAP MSGRPSPRES RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
206 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.140 Note MS Present for GRPS Confirmation
MAP MSGRPSPRES CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 207
Chapter 4: MAPI Primitives
4.6.141 Mobile Terminated Forward Short Message Request
MAP MTFSMS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
208 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.142 Mobile Terminated Forward Short Message Indication
MAP MTFSMS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 209
Chapter 4: MAPI Primitives
4.6.143 Mobile Terminated Forward Short Message Response
MAP MTFSMS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
210 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.144 Mobile Terminated Forward Short Message Confirmation
MAP MTFSMS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 211
Chapter 4: MAPI Primitives
4.6.145 Page Request
MAP PAGE REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
212 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.146 Page Indication
MAP PAGE IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 213
Chapter 4: MAPI Primitives
4.6.147 Page Response
MAP PAGE RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
214 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.148 Page Confirmation
MAP PAGE CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 215
Chapter 4: MAPI Primitives
4.6.149 Prepare Group Call Request
MAP PREPGC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
216 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.150 Prepare Group Call Indication
MAP PREPGC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 217
Chapter 4: MAPI Primitives
4.6.151 Prepare Group Call Response
MAP PREPGC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
218 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.152 Prepare Group Call Confirmation
MAP PREPGC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 219
Chapter 4: MAPI Primitives
4.6.153 Prepare Handover Request
MAP PREPHO REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
220 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.154 Prepare Handover Indication
MAP PREPHO IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 221
Chapter 4: MAPI Primitives
4.6.155 Prepare Handover Response
MAP PREPHO RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
222 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.156 Prepare Handover Confirmation
MAP PREPHO CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 223
Chapter 4: MAPI Primitives
4.6.157 Prepare Subsequent Handover Request
MAP PREPSH REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
224 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.158 Prepare Subsequent Handover Indication
MAP PREPSH IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 225
Chapter 4: MAPI Primitives
4.6.159 Prepare Subsequent Handover Response
MAP PREPSH RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
226 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.160 Prepare Subsequent Handover Confirmation
MAP PREPSH CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 227
Chapter 4: MAPI Primitives
4.6.161 Process Access Signalling Request
MAP PROCAS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
228 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.162 Process Access Signalling Indication
MAP PROCAS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 229
Chapter 4: MAPI Primitives
4.6.163 Process Access Signalling Response
MAP PROCAS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
230 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.164 Process Access Signalling Confirmation
MAP PROCAS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 231
Chapter 4: MAPI Primitives
4.6.165 Process Group Call Signalling Request
MAP PROCGC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
232 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.166 Process Group Call Signalling Indication
MAP PROCGC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 233
Chapter 4: MAPI Primitives
4.6.167 Process Group Call Signalling Response
MAP PROCGC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
234 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.168 Process Group Call Signalling Confirmation
MAP PROCGC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 235
Chapter 4: MAPI Primitives
4.6.169 Process Unstructured SS Request
MAP PROCUSS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
236 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.170 Process Unstructured SS Indication
MAP PROCUSS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 237
Chapter 4: MAPI Primitives
4.6.171 Process Unstructured SS Response
MAP PROCUSS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
238 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.172 Process Unstructured SS Confirmation
MAP PROCUSS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 239
Chapter 4: MAPI Primitives
4.6.173 Provide IMSI Request
MAP PROVIMSI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
240 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.174 Provide IMSI Indication
MAP PROVIMSI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 241
Chapter 4: MAPI Primitives
4.6.175 Provide IMSI Response
MAP PROVIMSI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
242 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.176 Provide IMSI Confirmation
MAP PROVIMSI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 243
Chapter 4: MAPI Primitives
4.6.177 Provide Roaming Number Request
MAP PROVRN REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
244 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.178 Provide Roaming Number Indication
MAP PROVRN IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 245
Chapter 4: MAPI Primitives
4.6.179 Provide Roaming Number Response
MAP PROVRN RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
246 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.180 Provide Roaming Number Confirmation
MAP PROVRN CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 247
Chapter 4: MAPI Primitives
4.6.181 Provide Subscriber Location Request
MAP PROVSLOC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
248 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.182 Provide Subscriber Location Indication
MAP PROVSLOC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 249
Chapter 4: MAPI Primitives
4.6.183 Provide Subscriber Location Response
MAP PROVSLOC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
250 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.184 Provide Subscriber Location Confirmation
MAP PROVSLOC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 251
Chapter 4: MAPI Primitives
4.6.185 Provide Subscriber Information Request
MAP PROVSUBI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
252 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.186 Provide Subscriber Information Indication
MAP PROVSUBI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 253
Chapter 4: MAPI Primitives
4.6.187 Provide Subscriber Information Response
MAP PROVSUBI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
254 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.188 Provide Subscriber Information Confirmation
MAP PROVSUBI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 255
Chapter 4: MAPI Primitives
4.6.189 Purge MS Request
MAP PURGEMS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
256 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.190 Purge MS Indication
MAP PURGEMS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 257
Chapter 4: MAPI Primitives
4.6.191 Purge MS Response
MAP PURGEMS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
258 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.192 Purge MS Confirmation
MAP PURGEMS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 259
Chapter 4: MAPI Primitives
4.6.193 Ready for SM Request
MAP RDYSM REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
260 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.194 Ready for SM Indication
MAP RDYSM IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 261
Chapter 4: MAPI Primitives
4.6.195 Ready for SM Response
MAP RDYSM RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
262 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.196 Ready for SM Confirmation
MAP RDYSM CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 263
Chapter 4: MAPI Primitives
4.6.197 Register CC Entry Request
MAP REGCC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
264 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.198 Register CC Entry Indication
MAP REGCC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 265
Chapter 4: MAPI Primitives
4.6.199 Register CC Entry Response
MAP REGCC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
266 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.200 Register CC Entry Confirmation
MAP REGCC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 267
Chapter 4: MAPI Primitives
4.6.201 Register Password Request
MAP REGPW REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
268 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.202 Register Password Indication
MAP REGPW IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 269
Chapter 4: MAPI Primitives
4.6.203 Register Password Response
MAP REGPW RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
270 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.204 Register Password Confirmation
MAP REGPW CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 271
Chapter 4: MAPI Primitives
4.6.205 Register Supplementary Service Request
MAP REGSS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
272 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.206 Register Supplementary Service Indication
MAP REGSS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 273
Chapter 4: MAPI Primitives
4.6.207 Register Supplementary Service Response
MAP REGSS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
274 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.208 Register Supplementary Service Confirmation
MAP REGSS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 275
Chapter 4: MAPI Primitives
4.6.209 Remote User Free Request
MAP REMUSRFREE REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
276 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.210 Remote User Free Indication
MAP REMUSRFREE IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 277
Chapter 4: MAPI Primitives
4.6.211 Remote User Free Response
MAP REMUSRFREE RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
278 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.212 Remote User Free Confirmation
MAP REMUSRFREE CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 279
Chapter 4: MAPI Primitives
4.6.213 Send Identification Request
MAP SENDID REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
280 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.214 Send Identification Indication
MAP SENDID IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 281
Chapter 4: MAPI Primitives
4.6.215 Send Identification Response
MAP SENDID RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
282 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.216 Send Identification Confirmation
MAP SENDID CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 283
Chapter 4: MAPI Primitives
4.6.217 Set Ciphering Mode Request
MAP SETCM REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
284 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.218 Set Ciphering Mode Indication
MAP SETCM IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 285
Chapter 4: MAPI Primitives
4.6.219 Set Ciphering Mode Response
MAP SETCM RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
286 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.220 Set Ciphering Mode Confirmation
MAP SETCM CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 287
Chapter 4: MAPI Primitives
4.6.221 Set Reporting State Request
MAP SETREP REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
288 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.222 Set Reporting State Indication
MAP SETREP IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 289
Chapter 4: MAPI Primitives
4.6.223 Set Reporting State Response
MAP SETREP RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
290 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.224 Set Reporting State Confirmation
MAP SETREP CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 291
Chapter 4: MAPI Primitives
4.6.225 Report Short Message Delivery Status Request
MAP SMDELIVSTAT REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
292 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.226 Report Short Message Delivery Status Indication
MAP SMDELIVSTAT IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 293
Chapter 4: MAPI Primitives
4.6.227 Report Short Message Delivery Status Response
MAP SMDELIVSTAT RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
294 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.228 Report Short Message Delivery Status Confirmation
MAP SMDELIVSTAT CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 295
Chapter 4: MAPI Primitives
4.6.229 Send Authentication Information Request
MAP SENDAUTHI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
296 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.230 Send Authentication Information Indication
MAP SENDAUTHI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 297
Chapter 4: MAPI Primitives
4.6.231 Send Authentication Information Response
MAP SENDAUTHI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
298 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.232 Send Authentication Information Confirmation
MAP SENDAUTHI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 299
Chapter 4: MAPI Primitives
4.6.233 Send End Signal Request
MAP SENDEND REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
300 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.234 Send End Signal Indication
MAP SENDEND IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 301
Chapter 4: MAPI Primitives
4.6.235 Send End Signal Response
MAP SENDEND RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
302 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.236 Send End Signal Confirmation
MAP SENDEND CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 303
Chapter 4: MAPI Primitives
4.6.237 Send Group Call End Signal Request
MAP SENDGCEND REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
304 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.238 Send Group Call End Signal Indication
MAP SENDGCEND IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 305
Chapter 4: MAPI Primitives
4.6.239 Send Group Call End Signal Response
MAP SENDGCEND RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
306 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.240 Send Group Call End Signal Confirmation
MAP SENDGCEND CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 307
Chapter 4: MAPI Primitives
4.6.241 Send Routing Information for GPRS Request
MAP SENDGPRSRI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
308 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.242 Send Routing Information for GPRS Indication
MAP SENDGPRSRI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 309
Chapter 4: MAPI Primitives
4.6.243 Send Routing Information for GPRS Response
MAP SENDGPRSRI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
310 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.244 Send Routing Information for GPRS Confirmation
MAP SENDGPRSRI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 311
Chapter 4: MAPI Primitives
4.6.245 Send Handover Report Request
MAP SENDHOREP REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
312 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.246 Send Handover Report Indication
MAP SENDHOREP IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 313
Chapter 4: MAPI Primitives
4.6.247 Send Handover Report Response
MAP SENDHOREP RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
314 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.248 Send Handover Report Confirmation
MAP SENDHOREP CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 315
Chapter 4: MAPI Primitives
4.6.249 Send IMSI Request
MAP SENDIMSI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
316 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.250 Send IMSI Indication
MAP SENDIMSI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 317
Chapter 4: MAPI Primitives
4.6.251 Send IMSI Response
MAP SENDIMSI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
318 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.252 Send IMSI Confirmation
MAP SENDIMSI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 319
Chapter 4: MAPI Primitives
4.6.253 Send Routing Information for LCS Request
MAP SENDLCSRI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
320 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.254 Send Routing Information for LCS Indication
MAP SENDLCSRI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 321
Chapter 4: MAPI Primitives
4.6.255 Send Routing Information for LCS Response
MAP SENDLCSRI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
322 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.256 Send Routing Information for LCS Confirmation
MAP SENDLCSRI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 323
Chapter 4: MAPI Primitives
4.6.257 Send Mobile Originated SMS Information Request
MAP SENDMOSMSI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
324 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.258 Send Mobile Originated SMS Information Indication
MAP SENDMOSMSI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 325
Chapter 4: MAPI Primitives
4.6.259 Send Mobile Originated SMS Information Response
MAP SENDMOSMSI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
326 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.260 Send Mobile Originated SMS Information Confirmation
MAP SENDMOSMSI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 327
Chapter 4: MAPI Primitives
4.6.261 Send Mobile Terminated SMS Information Request
MAP SENDMTSMSI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
328 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.262 Send Mobile Terminated SMS Information Indication
MAP SENDMTSMSI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 329
Chapter 4: MAPI Primitives
4.6.263 Send Mobile Terminated SMS Information Response
MAP SENDMTSMSI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
330 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.264 Send Mobile Terminated SMS Information Confirmation
MAP SENDMTSMSI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 331
Chapter 4: MAPI Primitives
4.6.265 Send Routing Information Request
MAP SENDRI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
332 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.266 Send Routing Information Indication
MAP SENDRI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 333
Chapter 4: MAPI Primitives
4.6.267 Send Routing Information Response
MAP SENDRI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
334 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.268 Send Routing Information Confirmation
MAP SENDRI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 335
Chapter 4: MAPI Primitives
4.6.269 Send Routing Information for SM Request
MAP SENDSMSRI REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
336 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.270 Send Routing Information for SM Indication
MAP SENDSMSRI IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 337
Chapter 4: MAPI Primitives
4.6.271 Send Routing Information for SM Response
MAP SENDSMSRI RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
338 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.272 Send Routing Information for SM Confirmation
MAP SENDSMSRI CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 339
Chapter 4: MAPI Primitives
4.6.273 SS Invocation Notification Request
MAP SSINV REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
340 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.274 SS Invocation Notification Indication
MAP SSINV IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 341
Chapter 4: MAPI Primitives
4.6.275 SS Invocation Notification Response
MAP SSINV RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
342 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.276 SS Invocation Notification Confirmation
MAP SSINV CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 343
Chapter 4: MAPI Primitives
4.6.277 Status Report Request
MAP STATUS REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
344 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.278 Status Report Indication
MAP STATUS IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 345
Chapter 4: MAPI Primitives
4.6.279 Status Report Response
MAP STATUS RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
346 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.280 Status Report Confirmation
MAP STATUS CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 347
Chapter 4: MAPI Primitives
4.6.281 Subscriber Location Report Request
MAP SUBLOCREP REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
348 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.282 Subscriber Location Report Indication
MAP SUBLOCREP IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 349
Chapter 4: MAPI Primitives
4.6.283 Subscriber Location Report Response
MAP SUBLOCREP RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
350 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.284 Subscriber Location Report Confirmation
MAP SUBLOCREP CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 351
Chapter 4: MAPI Primitives
4.6.285 Note Subscriber Data Modified Request
MAP SUBSDATAMOD REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
352 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.286 Note Subscriber Data Modified Indication
MAP SUBSDATAMOD IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 353
Chapter 4: MAPI Primitives
4.6.287 Note Subscriber Data Modified Response
MAP SUBSDATAMOD RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
354 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.288 Note Subscriber Data Modified Confirmation
MAP SUBSDATAMOD CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 355
Chapter 4: MAPI Primitives
4.6.289 Trace Subscriber Activity Request
MAP TRACESA REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
356 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.290 Trace Subscriber Activity Indication
MAP TRACESA IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 357
Chapter 4: MAPI Primitives
4.6.291 Trace Subscriber Activity Response
MAP TRACESA RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
358 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.292 Trace Subscriber Activity Confirmation
MAP TRACESA CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 359
Chapter 4: MAPI Primitives
4.6.293 Update GPRS Location Request
MAP UDGRPSLOC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
360 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.294 Update GPRS Location Indication
MAP UDGRPSLOC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 361
Chapter 4: MAPI Primitives
4.6.295 Update GPRS Location Response
MAP UDGRPSLOC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
362 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.296 Update GPRS Location Confirmation
MAP UDGRPSLOC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 363
Chapter 4: MAPI Primitives
4.6.297 Update Location Request
MAP UDLOC REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
364 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.298 Update Location Indication
MAP UDLOC IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 365
Chapter 4: MAPI Primitives
4.6.299 Update Location Response
MAP UDLOC RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
366 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.300 Update Location Confirmation
MAP UDLOC CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 367
Chapter 4: MAPI Primitives
4.6.301 Unstructured Supplementary Service Notify Request
MAP USSDNTFY REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
368 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.302 Unstructured Supplementary Service Notify Indication
MAP USSDNTFY IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 369
Chapter 4: MAPI Primitives
4.6.303 Unstructured Supplementary Service Notify Response
MAP USSDNTFY RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
370 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.304 Unstructured Supplementary Service Notify Confirmation
MAP USSDNTFY CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 371
Chapter 4: MAPI Primitives
4.6.305 Unstructured Supplementary Service Request
MAP USSDREQ REQ
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
372 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.306 Unstructured Supplementary Service Indication
MAP USSDREQ IND
Format
Parameters
Flags
Valid States
New State
2008-10-31 373
Chapter 4: MAPI Primitives
4.6.307 Unstructured Supplementary Service Response
MAP USSDREQ RES
Format
Parameters
Flags
Valid States
New State
Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledege-ments upon receipt of the primitive, and the MAP user must wait for the acknowledgementbefore issuing any other primitives:— Success: Acknowledgement of the primitive with the MAP_OK_ACK primitive described
in Section 4.1.11 [Successful Receipt Acknowledgement], page 47.— Non-fatal errors: These errors will be indicated with the MAP_ERROR_ACK primitive
described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errorsare as follows:
TOUTSTATEThe primitive would place the MAP interface out of state.
TSYSERR A system error has occured and the UNIX System error in indicated in theprimitive.
374 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) MAPI Primitives
4.6.308 Unstructured Supplementary Service Confirmation
MAP USSDREQ CON
Format
Parameters
Flags
Valid States
New State
2008-10-31 375
Mobile Application Part Interface (MAPI) Diagnostics Requirements
5 Diagnostics Requirements
Two error handling facilities should be provided to the MAP service user: one to handlenon-fatal errors, 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 theMAP service user and provide the user with the option of reissuing the MAP primitivewith the corrected options specification. The non-fatal error handling is provided only tothose primitives that require acknowledgements, and uses the MAP_ERROR_ACK to reportthese errors. These errors retain the state of the MAP service interface the same as it wasbefore the MAP provider received the primitive that was in error. Syntax errors and ruleviolations 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 correctableby the MAP user, or if it is unable to report a correctible error to the MAP service user.Fatal errors are indicated via the STREAMS message type M_ERROR with the UNIX systemerror EPROTO. The M_ERROR STREAMS message type will result in the failure of all theUNIX system calls on the stream. The MAP service user can recover from a fatal error byhaving all the processes close the files associated with the stream, and then reopening themfor processing.
2008-10-31 377
Mobile Application Part Interface (MAPI) References
6 References
1. CCITT X.213, (Geneva, 1986), “Network Service Definition for Open Systems Inter-connection (OSI) for CCITT Applications,” (Grey Book).
2. ISO 8348 — “Information Processing Systems — Data Communications — NewtorkService Definition,” 4/15/87
3. ISO 8348/AD — “Information Processing Systems — Data Communications — New-tork Service Definition — Addendum 1: Connectionless Mode Transmission,” 4/15/87
4. ISO 8373 — “Information Processing Systems — Data Communicatoins Protocol forProviding the Connectionless Mode Network Service,” SC6 N4542
5. ISO 8208 — “Information Processing Systems — X.25 Packet Level Protocol for DataTerminal Equipment,” 9/1/87
6. ISO 8878 — “Information Processing Systems — Data Communications — Use of X.25to Provide the OSI Connection-Mode Network Service,” 9/1/87
7. System V Interface Definition, Issue 2 – Volume 38. CCITT X.210, (Geneva 1984), “Open Systems Interconnection (OSI) Layer Service
Definition Conventions,” (Red Book)
2008-10-31 379
Mobile Application Part Interface (MAPI) Addendum for 3GPP Conformance
Addendum for 3GPP Conformance
2008-10-31 381
Mobile Application Part Interface (MAPI) Mapping MAPI Primitives to 3GPP TS 29.002
Appendix A Mapping MAPI Primitives to 3GPPTS 29.002
Table A-1 shows the mapping of the MAPI primitives to the MAP service definition prim-itives listed in 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 rsp
2008-10-31 383
Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 rspMAP_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 cnf
384 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 cnfMAP_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 req
2008-10-31 385
Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 reqMAP_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 ind
386 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 indMAP_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 rsp
2008-10-31 387
Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 rspMAP_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 cnf
388 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 cnfMAP_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 req
2008-10-31 389
Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002
MAP_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 checkIEMIv2 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
390 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Mapping MAPI Primitives to 3GPP TS 29.002
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 anyTimeInterrogationv3 anyTimeInfoHandlingContext anyTimeSubscriptionInterrogation,
anyTimeModificationv3 ss-InvocationNotificationContext ss-InvocationNotificationv3 groupCallControlContext prepareGroupCall,
processGroupCallSignalling,forwardGroupCallSignalling,sendGroupCallEndSignal
v3 reportingContext setReportingState,statusReport,remoteUserFree
v3 callCompletionContext registerCC-Entry,eraceCC-Entry
v3 isAlertingContext isAlertv3 ServiceTerminationContext istCommand
2008-10-31 391
Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002
v3 locationSvcEnquiryContext provideSubscriberLocation,subscriberLocationReport
v3 locationSvcGatewayContext sendRoutingInfoForLCSv3 mm-EventReportingContext noteMM-Eventv3 subscriberDataModificationNotificationContext noteSubscriberDataModifiedv3 authenticationFailureReportContext authenticationFailureReportv3 secureTransportHandlingContext secureTransportClass1,
secureTransportClass2,secureTransportClass3,secureTransportClass4
392 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) State/Event Tables
Appendix B State/Event Tables
2008-10-31 393
Mobile Application Part Interface (MAPI) Primitive Precedence Tables
Appendix C Primitive Precedence Tables
2008-10-31 395
Mobile Application Part Interface (MAPI) MAPI Header File Listing
Appendix D MAPI Header File Listing
2008-10-31 397
Mobile Application Part Interface (MAPI) License
License
GNU Free Documentation License
GNU FREE DOCUMENTATION LICENSEVersion 1.1, March 2000
Copyright c© 2000 Free Software Foundation, Inc.59 Temple Place, Suite 330, Boston, MA 02111-1307, USA
Everyone is permitted to copy and distribute verbatim copiesof this license document, but changing it is not allowed.
Preamble
The purpose of this License is to make a manual, textbook, or other written document freein the sense of freedom: to assure everyone the effective freedom to copy and redistributeit, with or without modifying it, either commercially or noncommercially. Secondarily, thisLicense preserves for the author and publisher a way to get credit for their work, while notbeing considered responsible for modifications made by others.This License is a kind of “copyleft”, which means that derivative works of the documentmust themselves be free in the same sense. It complements the GNU General Public License,which is 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;it can be used for any textual work, regardless of subject matter or whether it is publishedas a printed book. We recommend this License principally for works whose purpose isinstruction or reference.
Terms and Conditions for Copying, Distribution and Modification
1. APPLICABILITY AND DEFINITIONSThis License applies to any manual or other work that contains a notice placed bythe copyright holder saying it can be distributed under the terms of this License. The“Document”, below, refers to any such manual or work. Any member of the public isa licensee, and is addressed as “you”.A “Modified Version” of the Document means any work containing the Document ora portion of it, either copied verbatim, or with modifications and/or translated intoanother language.A “Secondary Section” is a named appendix or a front-matter section of the Documentthat deals exclusively with the relationship of the publishers or authors of the Documentto the Document’s overall subject (or to related matters) and contains nothing thatcould fall directly within that overall subject. (For example, if the Document is in part a
2008-10-31 399
License texi/fdl.texi
textbook of mathematics, a Secondary Section may not explain any mathematics.) Therelationship could be a matter of historical connection with the subject or with relatedmatters, or of legal, commercial, philosophical, ethical or political position regardingthem.
The “Invariant Sections” are certain Secondary Sections whose titles are designated, asbeing those of Invariant Sections, in the notice that says that the Document is releasedunder this License.
The “Cover Texts” are certain short passages of text that are listed, as Front-CoverTexts or Back-Cover Texts, in the notice that says that the Document is released underthis License.
A “Transparent” copy of the Document means a machine-readable copy, representedin a format whose specification is available to the general public, whose contents canbe viewed and edited directly and straightforwardly with generic text editors or (forimages composed of pixels) generic paint programs or (for drawings) some widely avail-able drawing editor, and that is suitable for input to text formatters or for automatictranslation to a variety of formats suitable for input to text formatters. A copy madein an otherwise Transparent file format whose markup has been designed to thwart ordiscourage subsequent modification by readers is not Transparent. A copy that is not“Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain ascii withoutmarkup, Texinfo input format, LaTEX input format, SGML or XML using apublicly available DTD, and standard-conforming simple HTML designed for humanmodification. Opaque formats include PostScript, PDF, proprietary formats that canbe read and edited only by proprietary word processors, SGML or XML for which theDTD and/or processing tools are not generally available, and the machine-generatedHTML produced by some word processors for output purposes only.
The “Title Page” means, for a printed book, the title page itself, plus such followingpages as are needed to hold, legibly, the material this License requires to appear in thetitle page. For works in formats which do not have any title page as such, “Title Page”means the text near the most prominent appearance of the work’s title, preceding thebeginning of the body of the text.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either commercially ornoncommercially, provided that this License, the copyright notices, and the licensenotice saying this License applies to the Document are reproduced in all copies, andthat you add no other conditions whatsoever to those of this License. You may not usetechnical measures to obstruct or control the reading or further copying of the copiesyou make or distribute. However, you may accept compensation in exchange for copies.If you distribute a large enough number of copies you must also follow the conditionsin section 3.
You may also lend copies, under the same conditions stated above, and you may publiclydisplay copies.
400 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) License
3. COPYING IN QUANTITYIf you publish printed copies of the Document numbering more than 100, and theDocument’s license notice requires Cover Texts, you must enclose the copies in coversthat carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the frontcover, and Back-Cover Texts on the back cover. Both covers must also clearly andlegibly identify you as the publisher of these copies. The front cover must present thefull title with all words of the title equally prominent and visible. You may add othermaterial on the covers in addition. Copying with changes limited to the covers, as longas they preserve the title of the Document and satisfy these conditions, can be treatedas verbatim copying in other respects.If the required texts for either cover are too voluminous to fit legibly, you should putthe first ones listed (as many as fit reasonably) on the actual cover, and continue therest onto adjacent pages.If you publish or distribute Opaque copies of the Document numbering more than 100,you must either include a machine-readable Transparent copy along with each Opaquecopy, or state in or with each Opaque copy a publicly-accessible computer-networklocation containing a complete Transparent copy of the Document, free of added ma-terial, which the general network-using public has access to download anonymously atno charge using public-standard network protocols. If you use the latter option, youmust take reasonably prudent steps, when you begin distribution of Opaque copiesin quantity, to ensure that this Transparent copy will remain thus accessible at thestated location until at least one year after the last time you distribute an Opaquecopy (directly or through your agents or retailers) of that edition to the public.It is requested, but not required, that you contact the authors of the Document wellbefore redistributing any large number of copies, to give them a chance to provide youwith an updated version of the Document.
4. MODIFICATIONSYou may copy and distribute a Modified Version of the Document under the conditionsof sections 2 and 3 above, provided that you release the Modified Version under preciselythis License, with the Modified Version filling the role of the Document, thus licensingdistribution and modification of the Modified Version to whoever possesses a copy ofit. In addition, you must 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 History section of the Document). You may use the same title asa previous version if the original publisher of that version gives permission.
B. List on the Title Page, as authors, one or more persons or entities responsible forauthorship of the modifications in the Modified Version, together with at least fiveof the principal authors of the Document (all of its principal authors, if it has lessthan five).
C. State on the Title page the name of the publisher of the Modified Version, as thepublisher.
D. Preserve all the copyright notices of the Document.
2008-10-31 401
License texi/fdl.texi
E. Add an appropriate copyright notice for your modifications adjacent to the othercopyright notices.
F. Include, immediately after the copyright notices, a license notice giving the publicpermission to use the Modified Version under the terms of this License, in the formshown in the Addendum below.
G. Preserve in that license notice the full lists of Invariant Sections and required CoverTexts given in the Document’s license notice.
H. Include an unaltered copy of this License.I. Preserve the section entitled “History”, and its title, and add to it an item stating
at least the title, year, new authors, and publisher of the Modified Version asgiven on the Title Page. If there is no section entitled “History” in the Document,create one stating the title, year, authors, and publisher of the Document as givenon its Title Page, then add an item describing the Modified Version as stated inthe previous sentence.
J. Preserve the network location, if any, given in the Document for public access toa Transparent copy of the Document, and likewise the network locations given inthe Document for previous versions it was based on. These may be placed in the“History” section. You may omit a network location for a work that was publishedat least four years before the Document itself, or if the original publisher of theversion it refers to gives permission.
K. In any section entitled “Acknowledgments” or “Dedications”, preserve the sec-tion’s title, and preserve in the section all the substance and tone of each of thecontributor acknowledgments and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document, unaltered in their text andin their titles. Section numbers or the equivalent are not considered part of thesection titles.
M. Delete any section entitled “Endorsements”. Such a section may not be includedin the Modified Version.
N. Do not retitle any existing section as “Endorsements” or to conflict in title withany Invariant Section.
If the Modified Version includes new front-matter sections or appendices that qualifyas Secondary Sections and contain no material copied from the Document, you may atyour option designate some or all of these sections as invariant. To do this, add theirtitles to the list of Invariant Sections in the Modified Version’s license notice. Thesetitles must be distinct from any other section titles.You may add a section entitled “Endorsements”, provided it contains nothing butendorsements of your Modified Version by various parties—for example, statements ofpeer review or that the text has been approved by an organization as the authoritativedefinition of a standard.You may add a passage of up to five words as a Front-Cover Text, and a passage of upto 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the ModifiedVersion. Only one passage of Front-Cover Text and one of Back-Cover Text may be
402 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) License
added by (or through arrangements made by) any one entity. If the Document alreadyincludes a cover text for the same cover, previously added by you or by arrangementmade by the same entity you are acting on behalf of, you may not add another; butyou may replace the old one, on explicit permission from the previous publisher thatadded the old one.The author(s) and publisher(s) of the Document do not by this License give permissionto use their names for publicity for or to assert or imply endorsement of any ModifiedVersion.
5. COMBINING DOCUMENTSYou may combine the Document with other documents released under this License,under the terms defined in section 4 above for modified versions, provided that youinclude in the combination all of the Invariant Sections of all of the original documents,unmodified, and list them all as Invariant Sections of your combined work in its licensenotice.The combined work need only contain one copy of this License, and multiple identicalInvariant Sections may be replaced with a single copy. If there are multiple InvariantSections with the same name but different contents, make the title of each such sectionunique by adding at the end of it, in parentheses, the name of the original author orpublisher of that section if known, or else a unique number. Make the same adjustmentto the section titles in the list of Invariant Sections in the license notice of the combinedwork.In the combination, you must combine any sections entitled “History” in the variousoriginal documents, forming one section entitled “History”; likewise combine any sec-tions entitled “Acknowledgments”, and any sections entitled “Dedications”. You mustdelete all sections entitled “Endorsements.”
6. COLLECTIONS OF DOCUMENTSYou may make a collection consisting of the Document and other documents releasedunder this License, and replace the individual copies of this License in the variousdocuments with a single copy that is included in the collection, provided that youfollow the rules of this License for verbatim copying of each of the documents in allother respects.You may extract a single document from such a collection, and distribute it individu-ally under this License, provided you insert a copy of this License into the extracteddocument, and follow this License in all other respects regarding verbatim copying ofthat document.
7. AGGREGATION WITH INDEPENDENT WORKSA compilation of the Document or its derivatives with other separate and independentdocuments or works, in or on a volume of a storage or distribution medium, does notas a whole count as a Modified Version of the Document, provided no compilationcopyright is claimed for the compilation. Such a compilation is called an “aggregate”,and this License does not apply to the other self-contained works thus compiled withthe Document, on account of their being thus compiled, if they are not themselvesderivative works of the Document.
2008-10-31 403
License texi/fdl.texi
If the Cover Text requirement of section 3 is applicable to these copies of the Document,then if the Document is less than one quarter of the entire aggregate, the Document’sCover Texts may be placed on covers that surround only the Document within theaggregate. Otherwise they must appear on covers around the whole aggregate.
8. TRANSLATIONTranslation is considered a kind of modification, so you may distribute translationsof the Document under the terms of section 4. Replacing Invariant Sections withtranslations requires special permission from their copyright holders, but you mayinclude translations of some or all Invariant Sections in addition to the original versionsof these Invariant Sections. You may include a translation of this License provided thatyou also include the original English version of this License. In case of a disagreementbetween the translation and the original English version of this License, the originalEnglish version will prevail.
9. TERMINATIONYou may not copy, modify, sublicense, or distribute the Document except as expresslyprovided for under this License. Any other attempt to copy, modify, sublicense ordistribute the Document is void, and will automatically terminate your rights underthis License. However, parties who have received copies, or rights, from you under thisLicense will not have their licenses terminated so long as such parties remain in fullcompliance.
10. FUTURE REVISIONS OF THIS LICENSEThe Free Software Foundation may publish new, revised versions of the GNU FreeDocumentation License from time to time. Such new versions will be similar in spiritto the present version, 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 Documentspecifies that a particular numbered version of this License “or any later version”applies to it, you have the option of following the terms and conditions either of thatspecified version or of any later version that has been published (not as a draft) bythe Free Software Foundation. If the Document does not specify a version number ofthis License, you may choose any version ever published (not as a draft) by the FreeSoftware Foundation.
END OF TERMS AND CONDITIONS
404 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) License
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 thedocument and 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.1
or any later version published by the Free Software Foundation;
with the Invariant Sections being list their titles, with the
Front-Cover Texts being list, and with the Back-Cover Texts being list.
A copy of the license is included in the section entitled ‘‘GNU
Free Documentation License’’.
If you have no Invariant Sections, write “with no Invariant Sections” instead of saying whichones are invariant. If you have no Front-Cover Texts, write “no Front-Cover Texts” insteadof “Front-Cover Texts being list”; likewise for Back-Cover Texts.If your document contains nontrivial examples of program code, we recommend releasingthese examples in parallel under your choice of free software license, such as the GNUGeneral Public License, to permit their use in free software.
2008-10-31 405
Mobile Application Part Interface (MAPI) Index
Index
AADDR_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39ADDR_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39
DDIAIND_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39
Llicense, FDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399license, GNU Free Documentation License . . . . 399
MMAP_ABORT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56MAP_ACTSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71MAP_ACTSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69MAP_ACTSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68MAP_ACTSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70MAP_ACTTM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75MAP_ACTTM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73MAP_ACTTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72MAP_ACTTM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74MAP_ADDR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44MAP_ADDR_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43MAP_addr_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43MAP_ALERTSC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79MAP_ALERTSC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77MAP_ALERTSC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76MAP_ALERTSC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78MAP_ALLOCHN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83MAP_ALLOCHN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81MAP_ALLOCHN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80MAP_ALLOCHN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82MAP_ANYMOD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87MAP_ANYMOD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85MAP_ANYMOD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84MAP_ANYMOD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86MAP_ANYQRY_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91MAP_ANYQRY_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89MAP_ANYQRY_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88MAP_ANYQRY_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90MAP_ANYSUB_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95MAP_ANYSUB_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93MAP_ANYSUB_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92MAP_ANYSUB_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94MAP_AUTH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103MAP_AUTH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101MAP_AUTH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100MAP_AUTH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102MAP_AUTHFAIL_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
MAP_AUTHFAIL_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97MAP_AUTHFAIL_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96MAP_AUTHFAIL_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98MAP_BIND_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39MAP_bind_ack_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39MAP_BIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37MAP_bind_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37MAP_CANCLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107MAP_CANCLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105MAP_CANCLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104MAP_CANCLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106MAP_CKIEMI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127MAP_CKIEMI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125MAP_CKIEMI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124MAP_CKIEMI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126MAP_CLOSE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55MAP_CLOSE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54MAP_DEACTSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131MAP_DEACTSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129MAP_DEACTSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128MAP_DEACTSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130MAP_DEACTTM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135MAP_DEACTTM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133MAP_DEACTTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132MAP_DEACTTM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134MAP_DELIM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53MAP_DELIM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52MAP_DELSUBD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139MAP_DELSUBD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137MAP_DELSUBD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136MAP_DELSUBD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138MAP_ERASECC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143MAP_ERASECC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141MAP_ERASECC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140MAP_ERASECC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142MAP_ERASESS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147MAP_ERASESS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145MAP_ERASESS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144MAP_ERASESS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146MAP_ERROR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46MAP_FAILURE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151MAP_FAILURE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149MAP_FAILURE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148MAP_FAILURE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150MAP_FAS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155MAP_FAS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153MAP_FAS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152MAP_FAS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154MAP_FCKSSIND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159MAP_FCKSSIND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157MAP_FCKSSIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156MAP_FCKSSIND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2008-10-31 407
Index
MAP_FGRCSIG_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163MAP_FGRCSIG_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161MAP_FGRCSIG_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160MAP_FGRCSIG_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162MAP_FNEWIMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167MAP_FNEWIMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165MAP_FNEWIMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164MAP_FNEWIMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166MAP_GETIEMI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171MAP_GETIEMI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169MAP_GETIEMI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168MAP_GETIEMI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170MAP_GETPASS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175MAP_GETPASS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173MAP_GETPASS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172MAP_GETPASS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174MAP_INFO_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34MAP_info_ack_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34MAP_INFO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33MAP_info_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33MAP_INFORMSC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179MAP_INFORMSC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177MAP_INFORMSC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176MAP_INFORMSC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178MAP_INSSUBSD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183MAP_INSSUBSD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181MAP_INSSUBSD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180MAP_INSSUBSD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182MAP_INTERGSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187MAP_INTERGSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185MAP_INTERGSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184MAP_INTERGSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186MAP_ISTALERT_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191MAP_ISTALERT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189MAP_ISTALERT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188MAP_ISTALERT_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190MAP_ISTCMD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195MAP_ISTCMD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193MAP_ISTCMD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192MAP_ISTCMD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194MAP_MMEVENT_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199MAP_MMEVENT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197MAP_MMEVENT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196MAP_MMEVENT_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198MAP_MOFSMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203MAP_MOFSMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201MAP_MOFSMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200MAP_MOFSMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202MAP_MSGRPSPRES_CON . . . . . . . . . . . . . . . . . . . . . . . . . 207MAP_MSGRPSPRES_IND . . . . . . . . . . . . . . . . . . . . . . . . . 205MAP_MSGRPSPRES_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 204MAP_MSGRPSPRES_RES . . . . . . . . . . . . . . . . . . . . . . . . . 206MAP_MTFSMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211MAP_MTFSMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209MAP_MTFSMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208MAP_MTFSMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
MAP_NOTICE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59MAP_OK_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47MAP_OPEN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51MAP_OPEN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49MAP_OPEN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48MAP_OPEN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50MAP_OPTMGMT_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45MAP_OPTMGMT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41MAP_optmgmt_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41MAP_PABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58MAP_PAGE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215MAP_PAGE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213MAP_PAGE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212MAP_PAGE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214MAP_PREPGC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219MAP_PREPGC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217MAP_PREPGC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216MAP_PREPGC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218MAP_PREPHO_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223MAP_PREPHO_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221MAP_PREPHO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220MAP_PREPHO_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222MAP_PREPSH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227MAP_PREPSH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225MAP_PREPSH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224MAP_PREPSH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226MAP_PROCAS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231MAP_PROCAS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229MAP_PROCAS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228MAP_PROCAS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230MAP_PROCGC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235MAP_PROCGC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233MAP_PROCGC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232MAP_PROCGC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234MAP_PROCUSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239MAP_PROCUSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237MAP_PROCUSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236MAP_PROCUSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238MAP_PROVIMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243MAP_PROVIMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241MAP_PROVIMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240MAP_PROVIMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242MAP_PROVRN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247MAP_PROVRN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245MAP_PROVRN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244MAP_PROVRN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246MAP_PROVSLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251MAP_PROVSLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249MAP_PROVSLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248MAP_PROVSLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250MAP_PROVSUBI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255MAP_PROVSUBI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253MAP_PROVSUBI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252MAP_PROVSUBI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254MAP_PURGEMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259MAP_PURGEMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
408 Version 0.9a Rel. 8
Mobile Application Part Interface (MAPI) Index
MAP_PURGEMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256MAP_PURGEMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258MAP_RDYSM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263MAP_RDYSM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261MAP_RDYSM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260MAP_RDYSM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262MAP_REGCC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267MAP_REGCC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265MAP_REGCC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264MAP_REGCC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266MAP_REGPW_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271MAP_REGPW_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269MAP_REGPW_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268MAP_REGPW_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270MAP_REGSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275MAP_REGSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273MAP_REGSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272MAP_REGSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274MAP_REMUSRFREE_CON . . . . . . . . . . . . . . . . . . . . . . . . . 279MAP_REMUSRFREE_IND . . . . . . . . . . . . . . . . . . . . . . . . . 277MAP_REMUSRFREE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 276MAP_REMUSRFREE_RES . . . . . . . . . . . . . . . . . . . . . . . . . 278MAP_RESET_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110MAP_RESET_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109MAP_RESET_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108MAP_RESET_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111MAP_RESTORE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114MAP_RESTORE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113MAP_RESTORE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112MAP_RESTORE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115MAP_RESUME_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119MAP_RESUME_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117MAP_RESUME_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116MAP_RESUME_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118MAP_SEARCH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123MAP_SEARCH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121MAP_SEARCH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120MAP_SEARCH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122MAP_SENDAUTHI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 299MAP_SENDAUTHI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 297MAP_SENDAUTHI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 296MAP_SENDAUTHI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 298MAP_SENDEND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303MAP_SENDEND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301MAP_SENDEND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300MAP_SENDEND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302MAP_SENDGCEND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 307MAP_SENDGCEND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 305MAP_SENDGCEND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 304MAP_SENDGCEND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 306MAP_SENDGPRSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 311MAP_SENDGPRSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 309MAP_SENDGPRSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 308MAP_SENDGPRSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 310MAP_SENDHOREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 315MAP_SENDHOREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 313
MAP_SENDHOREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 312MAP_SENDHOREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 314MAP_SENDID_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283MAP_SENDID_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281MAP_SENDID_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280MAP_SENDID_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282MAP_SENDIMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319MAP_SENDIMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317MAP_SENDIMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316MAP_SENDIMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318MAP_SENDLCSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 323MAP_SENDLCSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 321MAP_SENDLCSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 320MAP_SENDLCSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 322MAP_SENDMOSMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 327MAP_SENDMOSMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 325MAP_SENDMOSMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 324MAP_SENDMOSMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 326MAP_SENDMTSMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 331MAP_SENDMTSMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 329MAP_SENDMTSMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 328MAP_SENDMTSMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 330MAP_SENDRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335MAP_SENDRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333MAP_SENDRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332MAP_SENDRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334MAP_SENDSMSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 339MAP_SENDSMSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 337MAP_SENDSMSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 336MAP_SENDSMSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 338MAP_SETCM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287MAP_SETCM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285MAP_SETCM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284MAP_SETCM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286MAP_SETREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291MAP_SETREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289MAP_SETREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288MAP_SETREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290MAP_SMDELIVSTAT_CON . . . . . . . . . . . . . . . . . . . . . . . . 295MAP_SMDELIVSTAT_IND . . . . . . . . . . . . . . . . . . . . . . . . 293MAP_SMDELIVSTAT_REQ . . . . . . . . . . . . . . . . . . . . . . . . 292MAP_SMDELIVSTAT_RES . . . . . . . . . . . . . . . . . . . . . . . . 294MAP_SSINV_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343MAP_SSINV_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341MAP_SSINV_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340MAP_SSINV_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342MAP_STATUS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347MAP_STATUS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345MAP_STATUS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344MAP_STATUS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346MAP_STC1_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61MAP_STC1_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60MAP_STC2_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63MAP_STC2_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62MAP_STC3_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65MAP_STC3_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2008-10-31 409
Index
MAP_STC4_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67MAP_STC4_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66MAP_SUBLOCREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 351MAP_SUBLOCREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 349MAP_SUBLOCREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 348MAP_SUBLOCREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 350MAP_SUBSDATAMOD_CON . . . . . . . . . . . . . . . . . . . . . . . . 355MAP_SUBSDATAMOD_IND . . . . . . . . . . . . . . . . . . . . . . . . 353MAP_SUBSDATAMOD_REQ . . . . . . . . . . . . . . . . . . . . . . . . 352MAP_SUBSDATAMOD_RES . . . . . . . . . . . . . . . . . . . . . . . . 354MAP_TRACESA_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359MAP_TRACESA_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357MAP_TRACESA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356MAP_TRACESA_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358MAP_UABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57MAP_UDGRPSLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 363MAP_UDGRPSLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 361MAP_UDGRPSLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 360MAP_UDGRPSLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 362MAP_UDLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367MAP_UDLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365MAP_UDLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364MAP_UDLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366MAP_UNBIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
MAP_unbind_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40MAP_USSDNTFY_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371MAP_USSDNTFY_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369MAP_USSDNTFY_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368MAP_USSDNTFY_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370MAP_USSDREQ_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375MAP_USSDREQ_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373MAP_USSDREQ_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372MAP_USSDREQ_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374MGMT_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
OOPT_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41OPT_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
PPRIM_type . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39, 41, 43PRIM_type: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
SSTREAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 7, 8
410 Version 0.9a Rel. 8