Vous êtes sur la page 1sur 426

Mobile Application Part Interface (MAPI) Specication

Mobile Application Part Interface (MAPI) Specication


Version 0.9a Edition 8 Updated 2008-10-31 Distributed with Package strss7-0.9a.8

Copyright c 2008 OpenSS7 Corporation All Rights Reserved.

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

Brian Bidulock <bidulock@openss7.org> for The OpenSS7 Project <http://www.openss7.org/>

Copyright c 2001-2008 OpenSS7 Corporation Copyright c 1997-2000 Brian F. G. Bidulock All Rights Reserved.

Published by:
OpenSS7 Corporation 1469 Jeerys Crescent Edmonton, Alberta T6L 6T1 Canada Unauthorized distribution or duplication is prohibited. Permission to use, copy and distribute this documentation without modication, for any purpose and without fee or royalty is hereby granted, provided that both the above copyright notice and this permission notice appears in all copies and that the name of OpenSS7 Corporation not be used in advertising or publicity pertaining to distribution of this documentation or its contents without specic, written prior permission. OpenSS7 Corporation makes no representation about the suitability of this documentation for any purpose. It is provided as is without express or implied warranty.

Notice:
OpenSS7 Corporation disclaims all warranties with regard to this documentation including all implied warranties of merchantability, tness for a particular purpose, non-infringement, or title; that the contents of the document are suitable for any purpose, or that the implementation 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 direct, indirect, special or consequential damages or any damages whatsoever resulting from loss of use, data or prots, whether in an action of contract, negligence or other tortious action, arising out of or in connection with any use of this document or the performance or implementation of the contents thereof. OpenSS7 Corporation reserves the right to revise this software and documentation for any reason, including but not limited to, conformity with standards promulgated by various agencies, utilization of advances in the state of the technical arts, or the reection of changes in 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.

Short Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2 The Mobile Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 MAPI Services Denition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 3 3 4 4 4

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1.1 Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2 Denitions, Acronyms, Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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


2.1 2.2 Model of the MAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 MAP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2.1 Local Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2.2 Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2.3 Specic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3 Service Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3.1 Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3.1.1 Location Management Services . . . . . . . . . . . . . . . . . . . . . . 12 2.3.1.2 Paging and Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.3 Access Management Services . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.4 Handover Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.5 Authentication Management Services . . . . . . . . . . . . . . . . 13 2.3.1.6 Security Management Services . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.7 IEMI Managment Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.8 Subscriber Management Services . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.9 Identity Management Services . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1.10 Fault Recovery Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.1.11 Subscriber Information Services . . . . . . . . . . . . . . . . . . . . 14 2.3.2 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.2.1 Subscriber Tracing Services . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.2.2 Miscellaneous Operation and Maintenance Services. . . 14 2.3.3 Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.3.1 Call Handling Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.4 Supplementary Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.4.1 Supplementary Service Services . . . . . . . . . . . . . . . . . . . . . . 15 2.3.5 SMS Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.5.1 Short Message Service Management Services . . . . . . . . . 15

iv

Mobile Application Part Interface (MAPI) 2.3.6 Network-Requested PDP Context Activation . . . . . . . . . . . . . 2.3.6.1 Network-Requested PDP Context Activation Services ......................................................... 2.3.7 Location Service Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.7.1 Location Service Management Services . . . . . . . . . . . . . . . 2.4 MAP User Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 Mobile Switching Centre (MSC) Service Sets . . . . . . . . . . . . . 2.4.2 Home Location Register (HLR) Service Sets . . . . . . . . . . . . . . 2.4.3 Visitor Location Register (VLR) Service Sets . . . . . . . . . . . . . 2.4.4 Equipment Identity Register (EIR) Service Sets . . . . . . . . . . . 2.4.5 Serving GPRS Support Node (SGSN) Service Sets . . . . . . . . 2.4.6 Gateway GPRS Support Node (GGSN) Service Sets . . . . . . 2.4.7 Interworking MSC (IWMSC) for Short Message Service Service Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.8 Gateway MSC (GMSC) for Short Message Service Service Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.9 Gateway Mobile Location Center (GMLC) Service Sets . . . 16 16 16 16 16 16 17 19 20 20 21 21 22 22

MAPI Services Denition. . . . . . . . . . . . . . . . . . . . . 23


3.1 Local Management Services Denition . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 MAP Information Reporting Service . . . . . . . . . . . . . . . . . . . . . . 3.1.2 MAP User Bind Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 MAP User Unbind Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4 Receipt Acknowledgement Service . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5 Options Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.6 Error Acknowledgement Service . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Dialogue Handling Denition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 Dialogue Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.1 User Primitives for Successful MAP Dialogue Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2 Provider Primitives for Successful MAP Dialogue Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 Dialogue Component Transfer Phase. . . . . . . . . . . . . . . . . . . . . . 3.2.2.1 User Primitives for Component Transfer . . . . . . . . . . . . . 3.2.2.2 Provider Primitives for Component Transfer . . . . . . . . . 3.2.3 Dialogue Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.3.1 User Primitives for Dialogue Abort . . . . . . . . . . . . . . . . . . 3.2.3.2 Provider Primitives for Dialogue Abort . . . . . . . . . . . . . . 23 23 23 24 24 24 24 25 26 26 26 27 27 27 28 28 28

MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Management Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1 Information Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.2 Information Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.3 Bind Application Context Request . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4 Bind Application Context Acknowledgement . . . . . . . . . . . . . . 4.1.5 Unbind Application Context Request . . . . . . . . . . . . . . . . . . . . . 4.1.6 Options Management Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.7 Get Protocol Address Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.8 Get Protocol Address Acknowledgement . . . . . . . . . . . . . . . . . . 4.1.9 Options Management Acknowledgement . . . . . . . . . . . . . . . . . . 4.1.10 Error Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.11 Successful Receipt Acknowledgement . . . . . . . . . . . . . . . . . . . . 4.2 Association Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 Association Establishment Request . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 Association Establishment Indication . . . . . . . . . . . . . . . . . . . . . 4.2.3 Association Establishment Response . . . . . . . . . . . . . . . . . . . . . . 4.2.4 Association Establishment Conrmation . . . . . . . . . . . . . . . . . . 4.3 Component Transfer Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1 Component Delimitation Request . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 Component Delimitation Indication. . . . . . . . . . . . . . . . . . . . . . . 4.4 Association Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Association Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.2 Association Release Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.3 Association Abort Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.4 Association User Abort Indication . . . . . . . . . . . . . . . . . . . . . . . . 4.4.5 Association Provider Abort Indication . . . . . . . . . . . . . . . . . . . . 4.4.6 Association Notice Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5 Secure Transport Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 Secure Transport Class 1 Request . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Secure Transport Class 1 Indication . . . . . . . . . . . . . . . . . . . . . . 4.5.3 Secure Transport Class 2 Request . . . . . . . . . . . . . . . . . . . . . . . . 4.5.4 Secure Transport Class 2 Indication . . . . . . . . . . . . . . . . . . . . . . 4.5.5 Secure Transport Class 3 Request . . . . . . . . . . . . . . . . . . . . . . . . 4.5.6 Secure Transport Class 3 Indication . . . . . . . . . . . . . . . . . . . . . . 4.5.7 Secure Transport Class 4 Request . . . . . . . . . . . . . . . . . . . . . . . . 4.5.8 Secure Transport Class 4 Indication . . . . . . . . . . . . . . . . . . . . . . 4.6 Service Specic Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.1 Activate Supplementary Service Request . . . . . . . . . . . . . . . . . . 4.6.2 Activate Supplementary Service Indication. . . . . . . . . . . . . . . . 4.6.3 Activate Supplementary Service Response . . . . . . . . . . . . . . . . 4.6.4 Activate Supplementary Service Conrmation. . . . . . . . . . . . . 4.6.5 Activate Traceec Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.6 Activate Traceec Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . 4.6.7 Activate Traceec Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.8 Activate Traceec Mode Conrmation . . . . . . . . . . . . . . . . . . . . . 4.6.9 Alert Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.10 Alert Service Center Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 33 33 34 37 39 40 41 43 44 45 46 47 48 48 49 50 51 52 52 53 54 54 55 56 57 58 59 60 60 61 62 63 64 65 66 67 68 68 69 70 71 72 73 74 75 76 77

vi 4.6.11 4.6.12 4.6.13 4.6.14 4.6.15 4.6.16 4.6.17 4.6.18 4.6.19 4.6.20 4.6.21 4.6.22 4.6.23 4.6.24 4.6.25 4.6.26 4.6.27 4.6.28 4.6.29 4.6.30 4.6.31 4.6.32 4.6.33 4.6.34 4.6.35 4.6.36 4.6.37 4.6.38 4.6.39 4.6.40 4.6.41 4.6.42 4.6.43 4.6.44 4.6.45 4.6.46 4.6.47 4.6.48 4.6.49 4.6.50 4.6.51 4.6.52 4.6.53 4.6.54 4.6.55 4.6.56 4.6.57 4.6.58

Mobile Application Part Interface (MAPI) Alert Service Center Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Alert Service Center Conrmation . . . . . . . . . . . . . . . . . . . . . . . 79 Allocate Handover Number Request . . . . . . . . . . . . . . . . . . . . . 80 Allocate Handover Number Indication . . . . . . . . . . . . . . . . . . . 81 Allocate Handover Number Response . . . . . . . . . . . . . . . . . . . . 82 Allocate Handover Number Conrmation . . . . . . . . . . . . . . . . 83 Any Time Modication Request . . . . . . . . . . . . . . . . . . . . . . . . . 84 Any Time Modication Indication . . . . . . . . . . . . . . . . . . . . . . . 85 Any Time Modication Response . . . . . . . . . . . . . . . . . . . . . . . . 86 Any Time Modication Conrmation . . . . . . . . . . . . . . . . . . . . 87 Any Time Interrogation Request . . . . . . . . . . . . . . . . . . . . . . . . 88 Any Time Interrogation Indication . . . . . . . . . . . . . . . . . . . . . . 89 Any Time Interrogation Response . . . . . . . . . . . . . . . . . . . . . . . 90 Any Time Interrogation Conrmation . . . . . . . . . . . . . . . . . . . 91 Any Time Subscription Interrogation Request . . . . . . . . . . . 92 Any Time Subscription Interrogation Indication . . . . . . . . . 93 Any Time Subscription Interrogation Response . . . . . . . . . . 94 Any Time Subscription Interrogation Conrmation . . . . . . 95 Authentication Failure Report Request . . . . . . . . . . . . . . . . . . 96 Authentication Failure Report Indication . . . . . . . . . . . . . . . . 97 Authentication Failure Report Response . . . . . . . . . . . . . . . . . 98 Authentication Failure Report Conrmation . . . . . . . . . . . . . 99 Authenticate Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Authenticate Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Authenticate Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Authenticate Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Cancel Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Cancel Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Cancel Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Cancel Location Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Reset Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Reset Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Reset Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Reset Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Restore Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Restore Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Restore Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Restore Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Resume Call Handling Request . . . . . . . . . . . . . . . . . . . . . . . . . 116 Resume Call Handling Indication . . . . . . . . . . . . . . . . . . . . . . . 117 Resume Call Handling Conrmation . . . . . . . . . . . . . . . . . . . . 118 Resume Call Handling Response . . . . . . . . . . . . . . . . . . . . . . . 119 Search for MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Search for MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Search for MS Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Search for MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Check IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Check IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

vii 4.6.59 4.6.60 4.6.61 4.6.62 4.6.63 4.6.64 4.6.65 4.6.66 4.6.67 4.6.68 4.6.69 4.6.70 4.6.71 4.6.72 4.6.73 4.6.74 4.6.75 4.6.76 4.6.77 4.6.78 4.6.79 4.6.80 4.6.81 4.6.82 4.6.83 4.6.84 4.6.85 4.6.86 4.6.87 4.6.88 4.6.89 4.6.90 4.6.91 4.6.92 4.6.93 4.6.94 4.6.95 4.6.96 4.6.97 4.6.98 4.6.99 4.6.100 4.6.101 4.6.102 4.6.103 4.6.104 4.6.105 4.6.106 Check IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check IEMI Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivate Supplementary Service Request . . . . . . . . . . . . . Deactivate Supplementary Service Indication . . . . . . . . . . . Deactivate Supplementary Service Response . . . . . . . . . . . . Deactivate Supplementary Service Conrmation . . . . . . . . Deactivate Trace Mode Request . . . . . . . . . . . . . . . . . . . . . . . . Deactivate Trace Mode Indication . . . . . . . . . . . . . . . . . . . . . . Deactivate Trace Mode Response . . . . . . . . . . . . . . . . . . . . . . . Deactivate Trace Mode Conrmation . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Conrmation . . . . . . . . . . . . . . . . . . . Erase CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . Erase Supplementatry Service Request . . . . . . . . . . . . . . . . . Erase Supplementatry Service Indication . . . . . . . . . . . . . . . Erase Supplementatry Service Response . . . . . . . . . . . . . . . . Erase Supplementatry Service Conrmation . . . . . . . . . . . . Failure Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Report Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Request . . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Indication . . . . . . . . . . . . . . . . . . . Forward Access Signalling Response . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Conrmation . . . . . . . . . . . . . . . . Forward Check SS Indication Request . . . . . . . . . . . . . . . . . . Forward Check SS Indication Indication . . . . . . . . . . . . . . . . Forward Check SS Indication Response . . . . . . . . . . . . . . . . . Forward Check SS Indication Conrmation . . . . . . . . . . . . . Forward Group Call Signalling Request . . . . . . . . . . . . . . . . . Forward Group Call Signalling Indication. . . . . . . . . . . . . . . Forward Group Call Signalling Response . . . . . . . . . . . . . . . Forward Group Call Signalling Conrmation . . . . . . . . . . . Forward New IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward New IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . Forward New IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward New IMSI Conrmation . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173

viii

Mobile Application Part Interface (MAPI) 4.6.107 Get Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.6.108 Get Password Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 4.6.109 Inform Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . 176 4.6.110 Inform Service Center Indication . . . . . . . . . . . . . . . . . . . . . . 177 4.6.111 Inform Service Center Response . . . . . . . . . . . . . . . . . . . . . . . 178 4.6.112 Inform Service Center Conrmation . . . . . . . . . . . . . . . . . . . 179 4.6.113 Insert Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . 180 4.6.114 Insert Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . 181 4.6.115 Insert Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . 182 4.6.116 Insert Subscriber Data Conrmation . . . . . . . . . . . . . . . . . . 183 4.6.117 Iterrogate Supplementary Service Request . . . . . . . . . . . . . 184 4.6.118 Iterrogate Supplementary Service Indication . . . . . . . . . . . 185 4.6.119 Iterrogate Supplementary Service Response. . . . . . . . . . . . 186 4.6.120 Iterrogate Supplementary Service Conrmation . . . . . . . . 187 4.6.121 IST Alert Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 4.6.122 IST Alert Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 4.6.123 IST Alert Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 4.6.124 IST Alert Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 4.6.125 IST Command Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 4.6.126 IST Command Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 4.6.127 IST Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 4.6.128 IST Command Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . 195 4.6.129 Note MM Event Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 4.6.130 Note MM Event Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 4.6.131 Note MM Event Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 4.6.132 Note MM Event Conrmation. . . . . . . . . . . . . . . . . . . . . . . . . 199 4.6.133 Mobile Originated Forward Short Message Request . . . . 200 4.6.134 Mobile Originated Forward Short Message Indication . . 201 4.6.135 Mobile Originated Forward Short Message Response . . . 202 4.6.136 Mobile Originated Forward Short Message Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 4.6.137 Note MS Present for GRPS Request . . . . . . . . . . . . . . . . . . 204 4.6.138 Note MS Present for GRPS Indication . . . . . . . . . . . . . . . . 205 4.6.139 Note MS Present for GRPS Response . . . . . . . . . . . . . . . . . 206 4.6.140 Note MS Present for GRPS Conrmation . . . . . . . . . . . . . 207 4.6.141 Mobile Terminated Forward Short Message Request . . . 208 4.6.142 Mobile Terminated Forward Short Message Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 4.6.143 Mobile Terminated Forward Short Message Response . . 210 4.6.144 Mobile Terminated Forward Short Message Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 4.6.145 Page Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 4.6.146 Page Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 4.6.147 Page Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 4.6.148 Page Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 4.6.149 Prepare Group Call Request . . . . . . . . . . . . . . . . . . . . . . . . . . 216 4.6.150 Prepare Group Call Indication . . . . . . . . . . . . . . . . . . . . . . . . 217 4.6.151 Prepare Group Call Response . . . . . . . . . . . . . . . . . . . . . . . . . 218

ix 4.6.152 4.6.153 4.6.154 4.6.155 4.6.156 4.6.157 4.6.158 4.6.159 4.6.160 4.6.161 4.6.162 4.6.163 4.6.164 4.6.165 4.6.166 4.6.167 4.6.168 4.6.169 4.6.170 4.6.171 4.6.172 4.6.173 4.6.174 4.6.175 4.6.176 4.6.177 4.6.178 4.6.179 4.6.180 4.6.181 4.6.182 4.6.183 4.6.184 4.6.185 4.6.186 4.6.187 4.6.188 4.6.189 4.6.190 4.6.191 4.6.192 4.6.193 4.6.194 4.6.195 4.6.196 4.6.197 4.6.198 4.6.199 Prepare Group Call Conrmation . . . . . . . . . . . . . . . . . . . . . Prepare Handover Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Handover Indication . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Handover Response . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Handover Conrmation . . . . . . . . . . . . . . . . . . . . . . . Prepare Subsequent Handover Request . . . . . . . . . . . . . . . . Prepare Subsequent Handover Indication . . . . . . . . . . . . . . Prepare Subsequent Handover Response . . . . . . . . . . . . . . . Prepare Subsequent Handover Conrmation . . . . . . . . . . . Process Access Signalling Request . . . . . . . . . . . . . . . . . . . . . Process Access Signalling Indication . . . . . . . . . . . . . . . . . . . Process Access Signalling Response. . . . . . . . . . . . . . . . . . . . Process Access Signalling Conrmation . . . . . . . . . . . . . . . . Process Group Call Signalling Request . . . . . . . . . . . . . . . . Process Group Call Signalling Indication . . . . . . . . . . . . . . Process Group Call Signalling Response . . . . . . . . . . . . . . . Process Group Call Signalling Conrmation . . . . . . . . . . . Process Unstructured SS Request . . . . . . . . . . . . . . . . . . . . . Process Unstructured SS Indication . . . . . . . . . . . . . . . . . . . Process Unstructured SS Response . . . . . . . . . . . . . . . . . . . . Process Unstructured SS Conrmation . . . . . . . . . . . . . . . . Provide IMSI Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide Roaming Number Request . . . . . . . . . . . . . . . . . . . . Provide Roaming Number Indication . . . . . . . . . . . . . . . . . . Provide Roaming Number Response . . . . . . . . . . . . . . . . . . . Provide Roaming Number Conrmation . . . . . . . . . . . . . . . Provide Subscriber Location Request . . . . . . . . . . . . . . . . . . Provide Subscriber Location Indication . . . . . . . . . . . . . . . . Provide Subscriber Location Response . . . . . . . . . . . . . . . . Provide Subscriber Location Conrmation . . . . . . . . . . . . . Provide Subscriber Information Request . . . . . . . . . . . . . . . Provide Subscriber Information Indication . . . . . . . . . . . . . Provide Subscriber Information Response . . . . . . . . . . . . . Provide Subscriber Information Conrmation. . . . . . . . . . Purge MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge MS Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266

x 4.6.200 4.6.201 4.6.202 4.6.203 4.6.204 4.6.205 4.6.206 4.6.207 4.6.208 4.6.209 4.6.210 4.6.211 4.6.212 4.6.213 4.6.214 4.6.215 4.6.216 4.6.217 4.6.218 4.6.219 4.6.220 4.6.221 4.6.222 4.6.223 4.6.224 4.6.225 4.6.226 4.6.227 4.6.228 4.6.229 4.6.230 4.6.231 4.6.232 4.6.233 4.6.234 4.6.235 4.6.236 4.6.237 4.6.238 4.6.239 4.6.240 4.6.241 4.6.242 4.6.243 4.6.244 4.6.245 4.6.246 4.6.247

Mobile Application Part Interface (MAPI) Register CC Entry Conrmation . . . . . . . . . . . . . . . . . . . . . . Register Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . Register Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . Register Password Conrmation . . . . . . . . . . . . . . . . . . . . . . . Register Supplementary Service Request . . . . . . . . . . . . . . Register Supplementary Service Indication . . . . . . . . . . . . Register Supplementary Service Response . . . . . . . . . . . . . Register Supplementary Service Conrmation . . . . . . . . . Remote User Free Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote User Free Indication . . . . . . . . . . . . . . . . . . . . . . . . . . Remote User Free Response . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote User Free Conrmation . . . . . . . . . . . . . . . . . . . . . . . Send Identication Request . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Identication Indication . . . . . . . . . . . . . . . . . . . . . . . . . Send Identication Response . . . . . . . . . . . . . . . . . . . . . . . . . . Send Identication Conrmation . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Conrmation . . . . . . . . . . . . . . . . . . . . . Set Reporting State Request . . . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Indication . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Response . . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Conrmation . . . . . . . . . . . . . . . . . . . . . Report Short Message Delivery Status Request . . . . . . . . Report Short Message Delivery Status Indication . . . . . . Report Short Message Delivery Status Response . . . . . . . Report Short Message Delivery Status Conrmation . . . Send Authentication Information Request . . . . . . . . . . . . . Send Authentication Information Indication . . . . . . . . . . . Send Authentication Information Response . . . . . . . . . . . . Send Authentication Information Conrmation . . . . . . . . Send End Signal Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send End Signal Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . Send End Signal Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send End Signal Conrmation . . . . . . . . . . . . . . . . . . . . . . . . Send Group Call End Signal Request . . . . . . . . . . . . . . . . . . Send Group Call End Signal Indication . . . . . . . . . . . . . . . . Send Group Call End Signal Response . . . . . . . . . . . . . . . . Send Group Call End Signal Conrmation. . . . . . . . . . . . . Send Routing Information for GPRS Request. . . . . . . . . . Send Routing Information for GPRS Indication . . . . . . . Send Routing Information for GPRS Response . . . . . . . . Send Routing Information for GPRS Conrmation . . . . Send Handover Report Request . . . . . . . . . . . . . . . . . . . . . . . Send Handover Report Indication . . . . . . . . . . . . . . . . . . . . . Send Handover Report Response . . . . . . . . . . . . . . . . . . . . . . 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314

xi 4.6.248 Send Handover Report Conrmation . . . . . . . . . . . . . . . . . . 315 4.6.249 Send IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 4.6.250 Send IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 4.6.251 Send IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 4.6.252 Send IMSI Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 4.6.253 Send Routing Information for LCS Request . . . . . . . . . . . 320 4.6.254 Send Routing Information for LCS Indication . . . . . . . . . 321 4.6.255 Send Routing Information for LCS Response . . . . . . . . . . 322 4.6.256 Send Routing Information for LCS Conrmation . . . . . . 323 4.6.257 Send Mobile Originated SMS Information Request . . . . . 324 4.6.258 Send Mobile Originated SMS Information Indication. . . 325 4.6.259 Send Mobile Originated SMS Information Response . . . 326 4.6.260 Send Mobile Originated SMS Information Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 4.6.261 Send Mobile Terminated SMS Information Request . . . . 328 4.6.262 Send Mobile Terminated SMS Information Indication . . 329 4.6.263 Send Mobile Terminated SMS Information Response. . . 330 4.6.264 Send Mobile Terminated SMS Information Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 4.6.265 Send Routing Information Request . . . . . . . . . . . . . . . . . . . . 332 4.6.266 Send Routing Information Indication . . . . . . . . . . . . . . . . . . 333 4.6.267 Send Routing Information Response . . . . . . . . . . . . . . . . . . . 334 4.6.268 Send Routing Information Conrmation . . . . . . . . . . . . . . . 335 4.6.269 Send Routing Information for SM Request . . . . . . . . . . . . 336 4.6.270 Send Routing Information for SM Indication . . . . . . . . . . 337 4.6.271 Send Routing Information for SM Response . . . . . . . . . . . 338 4.6.272 Send Routing Information for SM Conrmation . . . . . . . 339 4.6.273 SS Invocation Notication Request . . . . . . . . . . . . . . . . . . . . 340 4.6.274 SS Invocation Notication Indication . . . . . . . . . . . . . . . . . . 341 4.6.275 SS Invocation Notication Response . . . . . . . . . . . . . . . . . . . 342 4.6.276 SS Invocation Notication Conrmation . . . . . . . . . . . . . . . 343 4.6.277 Status Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 4.6.278 Status Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 4.6.279 Status Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 4.6.280 Status Report Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 4.6.281 Subscriber Location Report Request . . . . . . . . . . . . . . . . . . 348 4.6.282 Subscriber Location Report Indication . . . . . . . . . . . . . . . . 349 4.6.283 Subscriber Location Report Response . . . . . . . . . . . . . . . . . 350 4.6.284 Subscriber Location Report Conrmation . . . . . . . . . . . . . 351 4.6.285 Note Subscriber Data Modied Request . . . . . . . . . . . . . . . 352 4.6.286 Note Subscriber Data Modied Indication . . . . . . . . . . . . . 353 4.6.287 Note Subscriber Data Modied Response . . . . . . . . . . . . . . 354 4.6.288 Note Subscriber Data Modied Conrmation . . . . . . . . . . 355 4.6.289 Trace Subscriber Activity Request . . . . . . . . . . . . . . . . . . . . 356 4.6.290 Trace Subscriber Activity Indication . . . . . . . . . . . . . . . . . . 357 4.6.291 Trace Subscriber Activity Response . . . . . . . . . . . . . . . . . . . 358 4.6.292 Trace Subscriber Activity Conrmation . . . . . . . . . . . . . . . 359 4.6.293 Update GPRS Location Request . . . . . . . . . . . . . . . . . . . . . . 360

xii

Mobile Application Part Interface (MAPI) 4.6.294 Update GPRS Location Indication . . . . . . . . . . . . . . . . . . . . 361 4.6.295 Update GPRS Location Response . . . . . . . . . . . . . . . . . . . . . 362 4.6.296 Update GPRS Location Conrmation . . . . . . . . . . . . . . . . . 363 4.6.297 Update Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 4.6.298 Update Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 4.6.299 Update Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 4.6.300 Update Location Conrmation . . . . . . . . . . . . . . . . . . . . . . . . 367 4.6.301 Unstructured Supplementary Service Notify Request. . . 368 4.6.302 Unstructured Supplementary Service Notify Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 4.6.303 Unstructured Supplementary Service Notify Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 4.6.304 Unstructured Supplementary Service Notify Conrmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 4.6.305 Unstructured Supplementary Service Request . . . . . . . . . 372 4.6.306 Unstructured Supplementary Service Indication . . . . . . . 373 4.6.307 Unstructured Supplementary Service Response . . . . . . . . 374 4.6.308 Unstructured Supplementary Service Conrmation . . . . 375

Diagnostics Requirements . . . . . . . . . . . . . . . . . . . 377


5.1 Non-Fatal Error Handling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 5.2 Fatal Error Handling Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Addendum for 3GPP Conformance . . . . . . . . . . . . 381 Appendix A Mapping MAPI Primitives to 3GPP TS 29.002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
A.1 Application Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Appendix B Appendix C Appendix D

State/Event Tables . . . . . . . . . . . . . . 393 Primitive Precedence Tables . . . 395 MAPI Header File Listing . . . . . . 397

License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
GNU Free Documentation License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Terms and Conditions for Copying, Distribution and Modication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 How to use this License for your documents . . . . . . . . . . . . . . . . . . . . 405

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Mobile Application Part Interface (MAPI)

Table of Contents

List of Figures

2008-10-31

List of Tables

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

Preface

Preface
Security Warning
Permission to use, copy and distribute this documentation without modication, for any purpose and without fee or royalty is hereby granted, provided that both the above copyright notice and this permission notice appears in all copies and that the name of OpenSS7 Corporation not be used in advertising or publicity pertaining to distribution of this documentation or its contents without specic, written prior permission. OpenSS7 Corporation makes no representation about the suitability of this documentation for any purpose. It is provided as is without express or implied warranty. OpenSS7 Corporation disclaims all warranties with regard to this documentation including all implied warranties of merchantability, tness for a particular purpose, non-infringement, or title; that the contents of the document are suitable for any purpose, or that the implementation 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 direct, indirect, special or consequential damages or any damages whatsoever resulting from loss of use, data or prots, whether in an action of contract, negligence or other tortious action, arising out of or in connection with any use of this document or the performance or implementation of the contents thereof. OpenSS7 Corporation is making this documentation available as a reference point for the industry. While OpenSS7 Corporation believes that these interfaces are well dened in this release of the document, minor changes may be made prior to products conforming to the interfaces being made available.

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

Purpose
The purpose of this document is to provide technical documentation of the Mobile Application Part Interface (MAPI). This document is intended to be included with the OpenSS7 STREAMS software package released by OpenSS7 Corporation. It is intended to assist software developers, maintainers and users of the Mobile Application Part Interface (MAPI) with understanding the software architecture and technical interfaces that are made available in the software package.

Intent
It is the intent of this document that it act as the primary source of information concerning 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) applications as well as writers of OpenSS7 Mobile Application Part Interface (MAPI) Users.

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

Disclaimer
Although the author has attempted to ensure that the information in this document is complete and correct, neither the Author nor OpenSS7 Corporation will take any responsibility in it.

Revision History
Take care that you are working with a current version of this documentation: you will not be notied of updates. To ensure that you are working with a current version, check the OpenSS7 Project website for a current version. Only the texinfo or ro source is controlled. A printed (or postscript) version of this document is an UNCONTROLLED VERSION.
mapi.texi,v Revision 0.9.2.14 2008-09-20 11:04:29 - added package patchlevel brian

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 - updated documentation Revision 0.9.2.10 2008-04-29 07:10:38 - updating headers for release Revision 0.9.2.9 2007/06/27 08:42:10 - added MTPI spec document Revision 0.9.2.8 2007/03/17 08:31:39 - corrected formatting problems Revision 0.9.2.7 2006/08/26 09:17:14 - better release file generation Revision 0.9.2.6 2006/08/22 12:44:17 - documentation updates Revision 0.9.2.5 2006/01/04 08:04:14 - corrected documentation brian

brian

brian

brian

brian

brian

brian

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

Preface

2008-10-31

Mobile Application Part Interface (MAPI)

Introduction

1 Introduction
This document species a STREAMS-based kernel-level instantiation of the 3GPP GSM/UMTS TS.29002 Mobile Application Part (MAP) service denition. The Mobile Application Part Interface (MAPI) enables the user of a mobile application service to access and use a wide variety of conforming mobile application service providers without specic knowledge of the providers protocol. The service interface is designed to support any operation class of transaction protocol. This interface only species access to mobile application layer service providers, and does not address issues concerning mobile application layer management, protocol performance, and performance analysis tools. This specication assumes that the reader is familiar with the 3GPP GSM/UTMS reference points 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 Denition, Issue 2 Volume 3 CCITT Recommendation X.200 CCITT Recommendation X.201 System V Interface Denition, Issue 2 - Volume 3

1.1.1 Role
This document species an interface that supports the service provided by the Mobile Applications Part (MAP) specication for 3GPP GSM/UMTS as described in 3GPP TS 29.002. These specications are targeted for use by developers and testers of protocol modules that require Mobile Applications Part services.

1.2 Denitions, Acronyms, Abbreviations


Application Context Object Identier Calling Party The Calling Party. Called Party The Called Party. Operations Class One of 5 ISO/OSI Transport Protocol Classes. MAP TCAP SCCP 2008-10-31 Mobile Applications Part Transaction Capabilities Application Part Service Connection Control Part 7

Chapter 1: Introduction

MTP TR TC IMSI MSISDN ITU ITU-T OSI ISO MAP User

Message Transfer Part Transaction Sub-Layer Component Sub-Layer International Mobile Station Identier Mobile Station ISDN Directory Number (E.164) International Telecommunications Union International Telecommunications Union Telecom Sector Open Systems Interconnect International Organization for Standardization A user of the Mobile Application Part (MAP) Interface.

MAP Provider A provider of the Mobile Application Part (MAP) Interface. MAPI MS The Mobile Application Part (MAP) Interface. Mobile Station.

Components Transaction components as dened in ITU-T Recommendation Q.771. QoS STREAMS A communication services development facility rst available with UNIX System V Release 3. Quality of Service

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 mobile network. It is responsible for the routing and management of data exchange between the MAP-User entities.

2.1 Model of the MAPI


The MAPI denes the services provided by the MAP layer to the MAP-User at the boundary between the MAP layer and the MAP layer user entity. The interface consists of a set of primitives dened as STREAMS messages that provide access to the MAP layer services, and are transferred between the MAP user entity and the MAP provider. These primitives are of two types: ones that originate from the MAP user, and others that originate from the MAP provider. The primitives that originate from the MAP user make requests to the MAP provider, or respond to an event of the MAP provider. The primitives that originate from the MAP provider are either conrmation of a request or are indications to the MAP user 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
MAP User

Request/Response Primitives

Application Context

MAPI
Full Duplex Connection

MAP Provider

Indication/Confirmation Primitives

TC User

The MAPI allows the MAP provider to be congured 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 dened in terms of the services provided by the MAP provider, and the individual primitives that may ow between the MAP users and the MAP provider. The services provided by the MAP are based on a number of application contexts corresponding 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 specications also dene a set of local management functions that apply to all application contexts. These services have local signicance 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 MAP OPEN MAP DELIM MAP CLOSE MAP UABORT MAP PABORT MAP NOTICE MAP STC1 MAP STC2 MAP STC3 MAP STC4 Invoker Performer

User Provider

User User

2.2.3 Specic Services


Table 3. Specic Services Service MAP ACTSS
1

Invoker MSC

Performer VLR

See Section putmsg(2) in The UNIX Manual Pages, also see Section getmsg(2) in The UNIX Manual Pages.

10

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

MAP ACTTM MAP ALERTSC MAP ANYMOD MAP MAP MAP MAP MAP ANYSUB AUTH AUTHFAIL CANCLOC CKIEMI

MAP DEACTSS MAP DEACTTM MAP DELSUBD MAP ERASECC MAP ERASESS MAP MAP MAP MAP MAP MAP MAP FAILURE FAS FCKSSIND FGRCSIG MTFSMS MOFSMS GETPASS

MAP INFORMSC MAP INSSUBSD MAP INTERGSS MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP ISTALERT ISTCMD MMEVENT MSGPRSPRES SUBSDATAMOD PREPGC PREPHO PREPSH PROCAS PROCGC PROCUSS

MAP PROVRN MAP PROVSLOC

VLR HLR HLR SCF PNA SCF VLR VLR or SGSN HLR VLR MSC or SGSN MSC VLR HLR HLR MSC VLR MSC VLR GGSN MSC-A HLR Anchor MSC SMS-GMSC MSC HLR VLR HLR HLR MSC VLR VMSC or GMSC HLR VLR or SGSN HLR HLR Anchor MSC MSC-A MSC-B MSC Relay MSC MSC VLR HLR GMLC

HLR VLR or SGSN SMS-IWMSC HLR VLR or SGSN HLR MSC HLR VLR or SGSN MSC EIR VLR HLR VLR or SGSN VLR or SGSN VLR HLR VLR HLR HLR MSC-B VLR Relay MSC MSC or SGSN SMS-IWMSC VLR MSC SMS-GMSC VLR or SGSN VLR HLR HLR VMSC or GMSC SCF GGSN SCF Relay MSC MSC-B MSC-A VLR Anchor MSC VLR HLR VLR VMSC or SGSN

2008-10-31

11

Chapter 2: The Mobile Application Layer

MAP PROVSUBI MAP PURGEMS MAP RDYSM MAP REGCC MAP REGPW MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP REGSS REMUSRFREE SMDELIVSTAT RESET RESTORE SENDGCEND SENDEND SENDAUTHI SENDIMSI SENDID SENDSMSRI SENDGPRSRI SENDLCSRI SENDRI SETREP STATUS SUBLOCREP USSDNTFY

MAP USSDREQ

MAP UDGPRSLOC MAP UDLOC

VLR VLR or SGSN MSC VLR or SGSN MSC VLR MSC VLR MSC HLR SMS-GMSC HLR VLR Relay MSC MSC-B VLR or SGSN VLR VLR SMS-GMSC GGSN GMLC GMSC or SCF HLR VLR VMSC or SGSN SCF HLR VLR SCF HLR VLR SGSN VLR

SGSN HLR VLR HLR VLR HLR VLR HLR VLR VLR HLR VLR or SGSN HLR Anchor MSC MSC-A HLR MSC old VLR HLR HLR HLR HLR or NPLR VLR HLR GMLC HLR VLR MSC HLR VLR MSC HLR HLR

2.3 Service Categories


2.3.1 Mobility Management 2.3.1.1 Location Management Services
Service MAP UDLOC MAP CANCLOC MAP SENDID MAP PURGEMS MAP UDGPRSLOC 12 Invoker VLR HLR VLR VLR or SGSN SGSN Performer HLR VLR or SGSN old VLR HLR HLR 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 MAP PAGE MAP SEARCH Invoker VLR VLR Performer MSC MSC

2.3.1.3 Access Management Services


Service MAP PROCAS Invoker MSC Performer VLR

2.3.1.4 Handover Services


Service MAP PREPHO MAP SENDEND MAP PROCAS MAP FAS MAP PREPSH MAP ALLOCHN MAP SENDHOREP Invoker MSC-A MSC-B MSC-B MSC-A MSC-B MSC VLR Performer MSC-B MSC-A MSC-A MSC-B MSC-A VLR MSC-B

2.3.1.5 Authentication Management Services


Service MAP AUTH MAP SENDAUTHI MAP AUTHFAIL Invoker VLR VLR or SGSN VLR or SGSN Performer MSC HLR HLR

2.3.1.6 Security Management Services


Service MAP SETCM Invoker VLR Performer MSC

2.3.1.7 IEMI Managment Services


Service MAP CKIEMI MAP GETIEMI Invoker VLR MSC or SGSN VLR Performer MSC EIR MSC

2.3.1.8 Subscriber Management Services


Service MAP INSSUBSD MAP DELSUBD Invoker HLR HLR Performer VLR or SGSN VLR or SGSN

2.3.1.9 Identity Management Services


Service 2008-10-31 Invoker Performer 13

Chapter 2: The Mobile Application Layer

MAP PROVIMSI MAP FNEWIMSI

VLR VLR

MSC MSC

2.3.1.10 Fault Recovery Services


Service MAP RESET MAP FCKSSIND MAP RESTORE Invoker HLR HLR VLR Performer VLR or SGSN VLR HLR

2.3.1.11 Subscriber Information Services


Service MAP ANYQRY MAP PROVSUBI MAP ANYSUB MAP ANYMOD MAP SUBSDATAMOD Invoker SCF VLR SCF SCF PNA HLR Performer HLR or GMLC or NPLR SGSN HLR HLR VLR or SGSN SCF

2.3.2 Operation and Maintenance 2.3.2.1 Subscriber Tracing Services


Service MAP ACTTM MAP DEACTTM MAP TRACESA Invoker HLR HLR VLR Performer VLR or SGSN VLR or SGSN MSC

2.3.2.2 Miscellaneous Operation and Maintenance Services


Service MAP SENDIMSI Invoker VLR Performer MSC

2.3.3 Call Handling 2.3.3.1 Call Handling Services


Service MAP SENDRI MAP PROVRN MAP RESUME MAP PREPGC MAP PROCGC MAP FGRCSIG MAP SENDGCEND MAP SETREP MAP STATUS MAP REMUSRFREE MAP ISTALERT 14 Invoker GMSC or SCF HLR VMSC Anchor MSC Relay MSC Anchor MSC Relay MSC HLR VLR HLR VMSC or GMSC Performer HLR or NPLR VLR GMSC Relay MSC Anchor MSC Relay MSC Anchor MSC VLR HLR VLR HLR 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 MAP REGSS MAP ERASESS MAP ACTSS MAP DEACTSS MAP INTERGSS MAP REGPW MAP GETPASS MAP PROCUSS MAP USSDREQ Invoker MSC MSC VLR MSC VLR MSC VLR MSC VLR MSC VLR HLR VLR MSC VLR SCF HLR VLR SCF HLR VLR MSC or HLR MSC VLR MSC VLR Performer VLR VLR HLR VLR HLR VLR HLR VLR HLR VLR HLR VLR MSC VLR HLR HLR VLR MSC HLR VLR MSC SCF VLR HLR VLR HLR

MAP USSDNTFY

MAP SSINV MAP REGCC MAP ERASECC

2.3.5 SMS Management Services 2.3.5.1 Short Message Service Management Services
Service MAP SENDSMSRI MAP MOFSMS MAP SMDELIVSTAT MAP RDYSM MAP RDYSM MAP ALERTSC MAP INFORMSC MAP SENDMTSMSI 2008-10-31 Invoker SMS-GMSC MSC SMS-GMSC MSC VLR or SGSN HLR HLR MSC Performer HLR SMS-IWMSC HLR VLR HLR SMS-IWMSC SMS-GMSC VLR 15

Chapter 2: The Mobile Application Layer

MAP SENDMOSMSI MAP MTFSMS

MSC SMS-GMSC

VLR MSC or SGSN

2.3.6 Network-Requested PDP Context Activation 2.3.6.1 Network-Requested PDP Context Activation Services
Service MAP SENDGPRSRI MAP FAILURE MAP MSGPRSPRES Invoker GGSN GGSN HLR Performer HLR HLR GGSN

2.3.7 Location Service Management 2.3.7.1 Location Service Management Services


Service MAP SENDLCSRI MAP PROVSLOC MAP SUBLOCREP Invoker GMLC GMLC VMSC or SGSN Performer HLR VMSC or SGSN GMLC

2.4 MAP User Entities


2.4.1 Mobile Switching Centre (MSC) Service Sets
Table X. MSC performed services. Service MAP PAGE MAP SEARCH MAP SENDHOREP MAP AUTH MAP SETCM MAP CKIEMI MAP GETIEMI MAP PROVIMSI MAP FNEWIMSI MAP TRACESA MAP SENDIMSI MAP ISTCMD MAP GETPASS MAP USSDREQ MAP USSDNTFY MAP MTFSMS MAP PROVSLOC 16 Invoker VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR HLR VLR VLR VLR SMS-GMSC GMLC Performer MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

Table X. MSC invoked services. Service MAP PROCAS MAP CKIEMI MAP ALLOCHN MAP RESUME MAP ISTALERT MAP REGSS MAP ERASESS MAP ACTSS MAP DEACTSS MAP INTERGSS MAP REGPW MAP PROCUSS MAP SSINV MAP REGCC MAP ERASECC MAP MOFSMS MAP RDYSM MAP SENDMTSMSI MAP SENDMOSMSI MAP SUBLOCREP Invoker MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC Performer VLR EIR VLR GMSC HLR VLR VLR VLR VLR VLR VLR VLR SCF VLR VLR SMS-IWMSC VLR VLR VLR GMLC

Table X. MSC peer services. Service MAP PREPHO MAP SENDEND MAP PROCAS MAP FAS MAP PREPSH MAP PREPGC MAP PROCGC MAP FGRCSIG MAP SENDGCEND Invoker MSC-A MSC-B MSC-B MSC-A MSC-B Anchor MSC Relay MSC Anchor MSC Relay MSC Performer MSC-B MSC-A MSC-A MSC-B MSC-A Relay MSC Anchor MSC Relay MSC Anchor MSC

2.4.2 Home Location Register (HLR) Service Sets


Table 1. HLR performed services. Service MAP UDLOC MAP PURGEMS MAP UDGPRSLOC 2008-10-31 Invoker VLR VLR or SGSN SGSN Performer HLR HLR HLR 17

Chapter 2: The Mobile Application Layer

MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP

SENDAUTHI AUTHFAIL RESTORE ANYQRY ANYSUB ANYMOD SENDRI STATUS ISTALERT ERASESS ACTSS DEACTSS INTERGSS REGPW PROCUSS REGCC ERASECC SENDSMSRI SMDELIVSTAT RDYSM SENDGPRSRI FAILURE USSDREQ SENDLCSRI USSDNTFY

VLR or SGSN VLR or SGSN VLR SCF SCF SCF GMSC or SCF VLR VMSC or GMSC VLR VLR VLR VLR VLR VLR VLR VLR SMS-GMSC SMS-GMSC VLR or SGSN GGSN GGSN SCF GMLC SCF

HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR

Service MAP CANCLOC MAP INSSUBSD MAP DELSUBD MAP RESET MAP FCKSSIND MAP SUBSDATAMOD MAP ACTTM MAP DEACTTM MAP PROVRN MAP SETREP MAP REMUSRFREE MAP ISTCMD MAP GETPASS MAP USSDREQ MAP USSDNTFY MAP SSINV 18

Table 2. HLR invoked services. Invoker HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR HLR

Performer VLR or SGSN VLR or SGSN VLR or SGSN VLR or SGSN VLR SCF VLR or SGSN VLR or SGSN VLR VLR VLR VMSC or GMSC VLR VLR VLR SCF Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

MAP ALERTSC MAP INFORMSC MAP MSGPRSPRES

HLR HLR HLR

SMS-IWMSC SMS-GMSC GGSN

2.4.3 Visitor Location Register (VLR) Service Sets


Table 3. VLR performed services. Invoker HLR MSC MSC HLR HLR VLR HLR HLR PNA HLR HLR HLR HLR HLR MSC MSC MSC MSC MSC MSC HLR MSC HLR HLR MSC MSC MSC MSC MSC

Service MAP CANCLOC MAP PROCAS MAP ALLOCHN MAP INSSUBSD MAP DELSUBD MAP SENDID MAP RESET MAP FCKSSIND MAP ANYMOD MAP ACTTM MAP DEACTTM MAP PROVRN MAP SETREP MAP REMUSRFREE MAP REGSS MAP ERASESS MAP ACTSS MAP DEACTSS MAP INTERGSS MAP REGPW MAP GETPASS MAP PROCUSS MAP USSDREQ MAP USSDNTFY MAP REGCC MAP ERASECC MAP RDYSM MAP SENDMTSMSI MAP SENDMOSMSI

Performer VLR VLR VLR VLR VLR old VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR

Service MAP UDLOC MAP SENDID MAP PURGEMS 2008-10-31

Table 4. VLR invoked services. Invoker VLR VLR VLR

Performer HLR old VLR HLR 19

Chapter 2: The Mobile Application Layer

MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP MAP

MMEVENT PAGE SEARCH SENDHOREP AUTH SENDAUTHI AUTHFAIL SETCM CKIEMI GETIEMI PROVIMSI FNEWIMSI RESTORE PROVSUBI TRACESA SENDIMSI STATUS ERASESS ACTSS DEACTSS INTERGSS REGPW GETPASS PROCUSS USSDREQ USSDNTFY REGCC ERASECC RDYSM

VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR VLR

SCF MSC MSC MSC-B MSC HLR HLR MSC MSC MSC MSC MSC HLR SGSN MSC MSC HLR HLR HLR HLR HLR HLR MSC HLR MSC MSC HLR HLR HLR

2.4.4 Equipment Identity Register (EIR) Service Sets


Table X. EIR performed services. Invoker MSC or SGSN

Service MAP CKIEMI

Performer EIR

2.4.5 Serving GPRS Support Node (SGSN) Service Sets


Table X. SGSN performed services. Invoker HLR HLR HLR

Service MAP CANCLOC MAP INSSUBSD MAP DELSUBD 20

Performer SGSN SGSN SGSN Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

MAP MAP MAP MAP MAP MAP MAP

RESET PROVSUBI ANYMOD ACTTM DEACTTM MTFSMS PROVSLOC

HLR VLR PNA HLR HLR SMS-GMSC GMLC

SGSN SGSN SGSN SGSN SGSN SGSN SGSN

Table X. SGSN invoked services. Service MAP PURGEMS MAP UDGPRSLOC MAP MMEVENT MAP SENDAUTHI MAP AUTHFAIL MAP CKIEMI MAP RDYSM MAP SUBLOCREP Invoker SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN Performer HLR HLR SCF HLR HLR EIR HLR GMLC

2.4.6 Gateway GPRS Support Node (GGSN) Service Sets


Table X. GGSN performed services. Service MAP MSGPRSPRES Invoker HLR Performer GGSN

Table X. GGSN invoked services. Service MAP SENDGPRSRI MAP FAILURE Invoker GGSN GGSN Performer HLR HLR

2.4.7 Interworking MSC (IWMSC) for Short Message Service Service Sets
Table X. SMS-IWMSC performed services. Service MAP MOFSMS MAP ALERTSC 2008-10-31 Invoker MSC HLR Performer SMS-IWMSC SMS-IWMSC 21

Chapter 2: The Mobile Application Layer

2.4.8 Gateway MSC (GMSC) for Short Message Service Service Sets
Table X. SMS-GMSC performed services. Invoker Performer HLR SMS-GMSC

Service MAP INFORMSC

Service MAP SENDSMSRI MAP SMDELIVSTAT MAP MTFSMS

Table X. SMS-GMSC invoked services. Invoker Performer SMS-GMSC HLR SMS-GMSC HLR SMS-GMSC MSC or SGSN

2.4.9 Gateway Mobile Location Center (GMLC) Service Sets


Table X. GMLC performed services. Invoker Performer SCF GMLC VMSC or SGSN GMLC

Service MAP ANYQRY MAP SUBLOCREP

Service MAP SENDLCSRI MAP PROVSLOC

Table X. GMLC invoked services. Invoker GMLC GMLC

Performer HLR VMSC or SGSN

22

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Services Denition

3 MAPI Services Denition


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

3.1 Local Management Services Denition


The services dened in this section are outside the scope of the international standards. These services apply to all applications contexts and specic service primitives. They are invoked 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 information 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 all the 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 returns the values of the supported protocol parameters to the MAP user. The sequence of primitives for mobile application part information management is shown in 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 a stream. It allows the MAP user to negotiate the number of dialogues that can remain outstanding for that MAP user (a dialogue is considered unacknowledged while it is awaiting a corresponding response or abort from the MAP user). This service also denes a mechanism that allows a stream (bound to a network address of the MAP user) to be reserved to handle 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 particular network address and application context, and negotiate the number of allowable outstanding open indications for that address. MAP_BIND_ACK: This primitive is in response to the MAP_BIND_REQ primitive and indicates to the user that the specied MAP user has been bound to a network address and 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 Denition


 

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 application context. MAP_UNBIND_REQ: This primitive requests that the MAP user be unbound from the network 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 user originated primitive was received successfully by the MAP provider. An example showing the sequence of primitives for successful receipt acknowledgement is depicted in Figure 4.

3.1.5 Options Management Service


This service allows the MAP user to manage the QOS parameter values and other options associated with the MAP provider. MAP_OPTMGMT_REQ: This primitive allows the MAP user to select default values for QoS parameters within the range supported by the MAP provider, and to indicate the default 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 has occurred in the last MAP user originated request or response primitive (listed in Figure 6), on the stream. Figure 6 shows the sequence of primitives for the error acknowledgement service.


Figure 6. Sequence of Primitives; Error Acknowledgement Service.

24

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Services Denition

3.2 Dialogue Handling Denition


This section describes the required MAP service primitives that dene the Dialogue Handling 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 pair of queues linking the two MAP user entities. There is one queue for each direction of information ow. Each queue represents a ow 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 the user removing objects from that queue, and the state of the queue. The pair of queues is considered to be available for each potential MAP dialogue. Objects that are entered or removed from the queue are either as a result of interactions at the two MAP users, or as a result of MAP provider initiatives. A queue is empty until a dialogue object has been entered and can be returned to this state, with loss of its contents, by the MAP provider. Objects can be entered into a queue as a result of the actions of the source MAP user, 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 dened to be able to advance ahead of the preceding object (however, no object is dened to be able to advance ahead of another object of the same type), or if the following object is dened to be destructive with respect to the preceding object on the queue. If necessary, the last object on the queue will be deleted to allow a destructive object to be entered the will therefore always be added to the queue. For example, abort objects are dened to be destructive with respect to all other objects. Table Y shows the ordering relationships among the queue model objects. Table Y. Ordering Relationship Between Queue Model Objects. Object X Object Y Open Components Deilmiter Close Abort AA DES Open N/A N/A N/A N/A N/A Components N/A Delimiter N/A Close DES DES DES DES Abort

Indicates that Object X is dened to be able to advance ahead of preceding Object Y. Indicates that Object X is dened to be destructive with respect to the preceding Object Y. 25

2008-10-31

Chapter 3: MAPI Services Denition

N/A

Indicates that Object X is neither destructive with respect to Object Y, nor able to advance ahead of Object Y. Indicates that Object X will not occur in a position succeeding Object Y in a valid 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 when the MAP provider receives a MAP_OPEN_REQ primitive at one of the MAP user interfaces resulting in the begin object being entered into the queue. The queues will remain associated with the MAP dialogue until a MAP_CLOSE_REQ or indication primitive (resulting in an end object) is either entered or removed from a queue. Similarly, in the queue from the called MAP user, objects can be entered into the queue only after the continue object associated 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 to establish 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 Dialogue Establishment


MAP_OPEN_REQ: This primitive requests that the MAP provider establish a dialogue to the specied destination under an application context. MAP_OPEN_RES: This primitives requests that the MAP provider accept a previous dialogue indication.

3.2.1.2 Provider Primitives for Successful MAP Dialogue Establishment


MAP_OPEN_IND: This primitive indicates to the MAP user that a dialogue request has been made within an application context by a user at the specied source address. MAP_OPEN_CON: This primitive indicates to the MAP user that a dialogue request has been conrmed on the specied responding address. The sequence of primitives for a successful MAP dialogue establishment is dened by the time sequence diagram as shown in Figure 7. The sequence of primitives for the MAP dialogue response token value determination is shown in Figure 8 (procedures for MAP response 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 Denition

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 X Object Y Class 1 Class 2 Class 3 Class 4 Yes No Class 1 Yes Yes Yes Yes Class 2 Yes Yes Yes Yes Class 3 Yes Yes Yes Yes Class 4 Yes Yes Yes Yes

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

3.2.2.1 User Primitives for Component Transfer


Service Specic Requests: These primitives request that the MAP provider invoke a service and transfer the specied (and any subsequent) components. Service Specic Responses: These primitives request that the MAP provider return result for a service invocation and transfer the specied (and any subsequent) components. MAP_DELIM_IND: This primitive requests that the MAP provider deliver any accumulated components from previous service specic request or response primitives.

3.2.2.2 Provider Primitives for Component Transfer


Service Specic Indications: These primitives indicate to the MAP user an invocation and the indicated (and any subsequent) components. Service Specic Conrmations: These primitives indicate to the MAP user a return result and the indicated (and any subsequent) components. MAP_DELIM_IND: This primitive indicates that the MAP provider has delivered any accumulated components belonging to the previous service specic indication or conrmation primitive. Figure 9 shows the sequence of primitives for successful component transfer. The sequence of 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 dened in the time sequence diagram as shown in Figure 10.


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

2008-10-31

27

Chapter 3: MAPI Services Denition

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 Service Specic Response primitive if no Service Specic Indication primitive for a conrmed service has been received, or if all such Service Specic Indication primitives have been previously conrmed. Following a MAP_UABORT or MAP_PABORT, a MAP user may not issue a Service Specic Response to conrm outstanding Service Specic Indication primitives received before the abort procedure was signalled. Note The witholding of conrmation of a service by a MAP user can have an eect on the attainable throughput. The sequence of primitives for component transfer is shown in the time sequence diagram in Figure 11. This sequence of primitives may remain incomplete if a MAP_ABORT or MAP_CLOSE primitive 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 other objects in the queue, and eventually results in the emptying of queues and termination of the MAP dialogue. The sequence of primitivies depends on the origin of the release action. The sequence of primitives may be: 1. invoked by one MAP user, with a request from that MAP user leading to an indication to 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 from the 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 outstanding request 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 for association has been denied or an existing association has been terminated. MAP_PABORT_IND: This primitive indicates to the MAP user that either a request for association 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, 18 and 19. 28 Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)


       

MAPI Services Denition

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 invoked release. 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 the requester by a MAP_PABORT_IND. The originator in this primitive indicates a MAP provider invoked 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 A shows the mapping of the MAPI primitives to the primitives dened in 3GPP TS 29.002 and ANSI41-D). Also, it discusses the states in which the primitive is valid, the resulting state and the acknowledgement that the primitive expects. (The state/event tables for these primitives are shown in Appendix B. The precedence tables for the MAPI primitives are shown in Appendix C.) Rules for 3GPP and ANSI conformance are described in Addendum to this document. Tabel 4. Local Management Service Primitives. SERVICE PRIMITIVE PARAMETERS Information MAP_INFO_REQ Reporting MAP_INFO_ACK Bind MAP_BIND_REQ MAP_BIND_ACK Unbind MAP_UNBIND_REQ Error MAP_ERROR_ACK Success MAP_OK_ACK Tables 5, 6 and 7 provide a summary of the MAP primitives and their parameters. Table 5. Association Establishment MAP Service Primitives. SERVICE PRIMITIVE PARAMETERS Association MAP_OPEN_REQ (Application context name, Destination address, Destination reference, Originating address, Originating reference, Specic information) Establishment MAP_OPEN_IND (Application context name, Destination address, Destination reference, Originating address, Originating reference, Specic information) MAP_OPEN_RES (Application context name, Responding address, Result, Refuse-reason, Specic information) MAP_OPEN_CON (Application context name, Responding address, Result, Refuse-reason, Specic information, Provider-error) Table 6. Component Transfer Service Primitives. PRIMITIVE PARAMETERS MAP_XXX _REQ (Specic information) MAP_XXX _IND (Specic information) MAP_XXX _RES (Specic information) MAP_XXX _CON (Specic information) 31

SERVICE Service Specic Primitives

2008-10-31

Chapter 4: MAPI Primitives

Delimitation

MAP_DELIM_REQ MAP_DELIM_IND

(none) (none)

SERVICE Association Termination Assocation Abort Abort Notice

Table 7. Association Termination MAP Service Primitives. PRIMITIVE PARAMETERS MAP_CLOSE_REQ (Release method, Specic information) MAP_CLOSE_IND (Specic information) MAP_ABORT_REQ (User reason, Diagnostic information, Specic information) MAP_UABORT_IND (User reason, Diagnostic information, Specic information) MAP_PABORT_IND (Provider reason, Source) MAP_NOTICE_IND () Table 8. Secure Transport Primitives. PRIMITIVE PARAMETERS MAP_STC1_REQ MAP_STC1_IND MAP_STC2_REQ MAP_STC2_IND MAP_STC3_REQ MAP_STC3_IND MAP_STC4_REQ MAP_STC4_IND

SERVICE Class 1 Class 2 Class 3 Class 4

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 protocol parameters (see Section 4.1.2 [Information Acknowledgement], page 34), and also the current state 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; } MAP_info_req_t; /* always MAP_INFO_REQ */

Parameters
PRIM type: Indicates the primitive type.

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

New State
The new state remains unchanged from the old state.

Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledgements upon receipt of the pirmitive: Successful: Acknowledgement of the primitive with the MAP_INFO_ACK primitive described in Section 4.1.2 [Information Acknowledgement], page 34. Non-fatal Errors: There are no errors associated with the issuance of this primitive.

The MAP_INFO_REQ and MAP_INFO_ACK primitives have no eect on the state of the MAP provider and do not 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 in Section 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; ulong TSDU_size; ulong ETSDU_size; ulong CDATA_size; ulong DDATA_size; ulong ADDR_size; ulong ADDR_length; ulong ADDR_offset; ulong QOS_length; ulong QOS_offset; ulong QOS_range_length; ulong QOS_range_offset; ulong OPTIONS_flags; ulong TIDU_size; long SERV_type; ulong CURRENT_state; ulong PROVIDER_type; ulong NODU_size; ulong PROTOID_length; ulong PROTOID_offset; ulong MAPI_version; } MAP_info_ack_t; /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* always MAP_INFO_ACK */ maximum TSDU size */ maximum ETSDU size */ connect data size */ disconnect data size */ address size */ address length */ address offset */ default QOS values length */ default QOS values offset */ QOS range length */ QOS range offset */ bit masking for options */ transaction interface data size */ service type */ current state */ type of provider */ optimal TSDU size */ length of bound protocol ids */ offset of bound protocol ids */ supported MAPI version number */

Parameters
PRIM type Indicates the primitive type. TSDU size Species the maximum size (in octets) of Transaction Service User Data supported by the MAP provider. ETSDU size Species the maximum size (in octets) of Expedited Transaction Service User Data supported by the MAP provider. CDATA size Species the maximum number of octets of data that may be associated with a 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 size Species the maximum number of octets of data that may be associated with a transaction termination primitive for operations class 1, 2 and 3 operation. ADDR size Species the maximum size (in decimal digits) of a network address. ADDR length, ADDR oset Species the length in bytes and oset from the beginning of the M_PCPROTO message 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 oset QOS range length, QOS range oset OPTIONS ags TIDU size 2 This is the size of the MAP protocol interface data unit, and should not exceed the tunable system limit, if non-zero, for the size of a STREAMS message. SERV type This eld specied the service type supported by the MAP provider, and is one of the following: CURRENT state THis is the current state of the MAP provider. PROVIDER type This eld species additional properties specic to the MAP provider and may alter the way the MAP user communicates. MAP providers supporting the features of XTI in XPG4 and beyond must send up a version number as specied below. The following ags may be set by the provider: SENDZERO XPG4_1 This ag indicates that the MAP provider support the sending of zero-length (component-less) TSDUs. This indicates that the MAP provider conforms to XTI in XPG4 and supports primitives MAP_ADDR_REQ and MAP_ADDR_ACK.

TODU size PROTOID length, PROTOID oset MAPI version

Flags Valid States New State


2

This is the amount of user components that may be present in a single service specic 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 elds 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 MAP provider for the specied protocol address, and activate1 the stream associated with the protocol address.

Format
The format of the message is one M_PROTO message block. The format of the M_PROTO message block is as follows:
typedef struct { ulong PRIM_type; ulong ADDR_length; ulong ADDR_offset; unsigned long DIAIND_number; } MAP_bind_req_t; /* /* /* /* always MAP_BIND_REQ */ length of protocol address */ offset of protocol address */ requested number of dialogue indications to be queued */

Parameters
PRIM type Indicates the primitive type. ADDR length The length2 of the protocol address to be bound to the stream. ADDR oset The oset from the beiginning of the M_PROTO block where the protocol address begins. The address in the M_PROTO message block is however, aligned the same as it was received from the MAP user. DIAIND number 3 The requested number of connection indications4 allowed to be outstanding by the MAP provider for the specied protocol address.

Flags Valid States New State


1 2 3 4

A stream is viewed as active when the MAP provider may receive and transmit components (Trasaction Protocol Data Units) associated with the stream All lengths, osets and sizes in all structures refer to the number of bytes. This eld should be ignored by those application contexts providing operations class 4 service. 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 outstanding connect 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 acknowledgements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before issuing 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 primitive described in Section 4.1.10 [Error Acknowledgement], page 46. The allowable errors are as follows: TBADADDR This indicates that the protocol address was in an incorrect format or the address contained illegal information. It is not indended to indicate protocol errors. This indicates that the MAP provider could not allocate an address. This indicates that the user did not have proper permissions for the use of the requested address. The primitive would place the MAP interface out of state. TSYSERR TADDRBUSY This indicated that the requested address is already in use. A system error has occured and the UNIX System error in indicated in the primitive.

TNOADDR TACCES TOUTSTATE

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 specied protoocl address has been bound to the stream, that the specied number of dialogue open indications are allowed to be queued by the MAP provider for th specied protocol address, and that the stream associated with the specied 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; long ADDR_length; long ADDR_offset; ulong DIAIND_number; } MAP_bind_ack_t; /* /* /* /* always MAP_BIND_ACK */ length of address -- see note in sec. 1.4 */ offset of address */ dialogue open indications to be queued */

Parameters
PRIM type ADDR length ADDR oset DIAIND number

Flags Valid States New State Rules


The following rules apply to the binding of the specied 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 with the 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; } MAP_unbind_req_t; /* always MAP_UNBIND_REQ */

Parameters
PRIM type: Indicates primitive type.

Valid States New State Acknowledgements


This primitive requires the MAP provider to generate the following acknowledgements upon receipt of the primitive and that the MAP user must wait for the acknowledgement before issuing 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occurred and the UNIX system error is indicated in the primitive.

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; long OPT_length; long OPT_offset; long MGMT_flags; } MAP_optmgmt_req_t; /* /* /* /* always MAP_OPTMGMT_REQ */ options length */ options offset */ flags */

Parameters
PRIM type Indicates the primitive type. OPT length The length of the protocol options associated with the primitive. OPT oset The oset from the beginning of the M_PROTO message block where the options begin. The proper alignment of options is not guaranteed. The options are, however, aligned the same as they were received from the MAP user. MGMT ags The ags which dene the request made by the MAP user.

Flags
T_NEGOTIATE Negotiate and set the options with the MAP provider. T_CHECK T_CURRENT Return the options currently in eect. T_DEFAULT Return the default options. Check the validity of the specied options.

Rules
For the rules governing the requests made by this primitive, see the MAP_OPTMGMT_ACK primitive 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 acknowledgements upon receipt of the primitive and that the MAP user await the acknowledgement before issuing 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 errors are as follows: TACCES TOUTSTATE The primitive would place the MAP interface out of state. TBADOPT TBADFLAG TSYSERR This indicates that the options as specied were in an incorrect format, or they contained illegal information. This indicates that the ags as specied were incorrect or illegal. A system error has occured and the UNIX system error is indicated in the primitive. This indicates that the user did not have proper permissions for the use of the requested options.

TNOTSUPPORT This MAP provider does not support the requested ag (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 is bound to the stream and the address of the remote MAP entity if a dialogue has been established.

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; } MAP_addr_req_t; /* always MAP_ADDR_REQ */

Parameters
PRIM type Indicates the primitive type.

Valid States New State Acknowledgements


This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

50

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.2.4 Association Establishment Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 Specic 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

70

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.4 Activate Supplementary Service Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

74

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.8 Activate Traceec Mode Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

78

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.12 Alert Service Center Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

82

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.16 Allocate Handover Number Conrmation MAP ALLOCHN CON Format Parameters Flags Valid States New State

2008-10-31

83

Chapter 4: MAPI Primitives

4.6.17 Any Time Modication Request MAP ANYMOD REQ Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

84

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.18 Any Time Modication Indication MAP ANYMOD IND Format Parameters Flags Valid States New State

2008-10-31

85

Chapter 4: MAPI Primitives

4.6.19 Any Time Modication Response MAP ANYMOD RES Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

86

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.20 Any Time Modication Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

90

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.24 Any Time Interrogation Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

94

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.28 Any Time Subscription Interrogation Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

98

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.32 Authentication Failure Report Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

102

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.36 Authenticate Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

106

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.40 Cancel Location Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

110

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.44 Reset Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

114

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.48 Restore Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

126

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.60 Check IEMI Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

130

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.64 Deactivate Supplementary Service Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

134

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.68 Deactivate Trace Mode Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

138

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.72 Delete Subscriber Data Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

142

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.76 Erase CC Entry Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

146

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.80 Erase Supplementatry Service Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

150

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.84 Failure Report Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

154

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.88 Forward Access Signalling Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

158

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.92 Forward Check SS Indication Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

162

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.96 Forward Group Call Signalling Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

166

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.100 Forward New IMSI Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

170

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.104 Obtain IEMI Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

174

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.108 Get Password Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

178

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.112 Inform Service Center Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

182

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.116 Insert Subscriber Data Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

186

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.120 Iterrogate Supplementary Service Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

190

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.124 IST Alert Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

194

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.128 IST Command Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

198

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.132 Note MM Event Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

202

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.136 Mobile Originated Forward Short Message Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

206

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.140 Note MS Present for GRPS Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

210

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.144 Mobile Terminated Forward Short Message Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

214

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.148 Page Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

218

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.152 Prepare Group Call Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

222

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.156 Prepare Handover Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

226

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.160 Prepare Subsequent Handover Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

230

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.164 Process Access Signalling Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

234

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.168 Process Group Call Signalling Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

238

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.172 Process Unstructured SS Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

242

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.176 Provide IMSI Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

246

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.180 Provide Roaming Number Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

250

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.184 Provide Subscriber Location Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

254

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.188 Provide Subscriber Information Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

258

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.192 Purge MS Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

262

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.196 Ready for SM Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

266

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.200 Register CC Entry Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

270

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.204 Register Password Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

274

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.208 Register Supplementary Service Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

278

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.212 Remote User Free Conrmation MAP REMUSRFREE CON Format Parameters Flags Valid States New State

2008-10-31

279

Chapter 4: MAPI Primitives

4.6.213 Send Identication Request MAP SENDID REQ Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

280

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.214 Send Identication Indication MAP SENDID IND Format Parameters Flags Valid States New State

2008-10-31

281

Chapter 4: MAPI Primitives

4.6.215 Send Identication Response MAP SENDID RES Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

282

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.216 Send Identication Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

286

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.220 Set Ciphering Mode Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

290

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.224 Set Reporting State Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

294

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.228 Report Short Message Delivery Status Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

298

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.232 Send Authentication Information Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

302

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.236 Send End Signal Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

306

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.240 Send Group Call End Signal Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

310

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.244 Send Routing Information for GPRS Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

314

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.248 Send Handover Report Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

318

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.252 Send IMSI Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

322

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.256 Send Routing Information for LCS Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

326

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.260 Send Mobile Originated SMS Information Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

330

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.264 Send Mobile Terminated SMS Information Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

334

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.268 Send Routing Information Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

338

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.272 Send Routing Information for SM Conrmation MAP SENDSMSRI CON Format Parameters Flags Valid States New State

2008-10-31

339

Chapter 4: MAPI Primitives

4.6.273 SS Invocation Notication Request MAP SSINV REQ Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

340

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.274 SS Invocation Notication Indication MAP SSINV IND Format Parameters Flags Valid States New State

2008-10-31

341

Chapter 4: MAPI Primitives

4.6.275 SS Invocation Notication Response MAP SSINV RES Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

342

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.276 SS Invocation Notication Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

346

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.280 Status Report Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

350

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.284 Subscriber Location Report Conrmation MAP SUBLOCREP CON Format Parameters Flags Valid States New State

2008-10-31

351

Chapter 4: MAPI Primitives

4.6.285 Note Subscriber Data Modied Request MAP SUBSDATAMOD REQ Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

352

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.286 Note Subscriber Data Modied 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 Modied Response MAP SUBSDATAMOD RES Format Parameters Flags Valid States New State Acknowledgements
This primitive requires the MAP provider to generate one of the following acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

354

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.288 Note Subscriber Data Modied Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

358

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.292 Trace Subscriber Activity Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

362

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.296 Update GPRS Location Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

366

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.300 Update Location Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

370

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.304 Unstructured Supplementary Service Notify Conrmation 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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

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 acknowledegements upon receipt of the primitive, and the MAP user must wait for the acknowledgement before 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 errors are as follows: TOUTSTATE The primitive would place the MAP interface out of state. TSYSERR A system error has occured and the UNIX System error in indicated in the primitive.

374

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.308 Unstructured Supplementary Service Conrmation 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 handle non-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 the MAP service user and provide the user with the option of reissuing the MAP primitive with the corrected options specication. The non-fatal error handling is provided only to those primitives that require acknowledgements, and uses the MAP_ERROR_ACK to report these errors. These errors retain the state of the MAP service interface the same as it was before the MAP provider received the primitive that was in error. Syntax errors and rule violations are reported via the non-fatal error handling facility.

5.2 Fatal Error Handling Facility


These errors are issued by the MAP provider when it detects errors that are not correctable by 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 system error EPROTO. The M_ERROR STREAMS message type will result in the failure of all the UNIX system calls on the stream. The MAP service user can recover from a fatal error by having all the processes close the les associated with the stream, and then reopening them for processing.

2008-10-31

377

Mobile Application Part Interface (MAPI)

References

6 References
1. CCITT X.213, (Geneva, 1986), Network Service Denition for Open Systems Interconnection (OSI) for CCITT Applications, (Grey Book). 2. ISO 8348 Information Processing Systems Data Communications Newtork Service Denition, 4/15/87 3. ISO 8348/AD Information Processing Systems Data Communications Newtork Service Denition Addendum 1: Connectionless Mode Transmission, 4/15/87 4. ISO 8373 Information Processing Systems Data Communicatoins Protocol for Providing the Connectionless Mode Network Service, SC6 N4542 5. ISO 8208 Information Processing Systems X.25 Packet Level Protocol for Data Terminal Equipment, 9/1/87 6. ISO 8878 Information Processing Systems Data Communications Use of X.25 to Provide the OSI Connection-Mode Network Service, 9/1/87 7. System V Interface Denition, Issue 2 Volume 3 8. CCITT X.210, (Geneva 1984), Open Systems Interconnection (OSI) Layer Service Denition 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 3GPP TS 29.002


Table A-1 shows the mapping of the MAPI primitives to the MAP service denition primitives 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 Primitive MAP_OPEN_REQ MAP-OPEN req MAP_OPEN_IND MAP-OPEN ind MAP_OPEN_RES MAP-OPEN rsp MAP_OPEN_CON MAP-OPEN cnf MAP_CLOSE_REQ MAP-CLOSE req MAP_CLOSE_IND MAP-CLOSE ind MAP_DELIM_REQ MAP-DELIMITER req MAP_DELIM_IND MAP-DELIMITER ind MAP_ABORT_REQ MAP-U-ABORT req MAP_UABORT_IND MAP-U-ABORT ind MAP_PABORT_IND MAP-P-ABORT ind MAP_NOTICE_IND MAP-NOTICE ind MAP_STC1_REQ MAP-SECURE-TRANSPORT-CLASS-1 req MAP_STC1_IND MAP-SECURE-TRANSPORT-CLASS-1 ind MAP_STC2_REQ MAP-SECURE-TRANSPORT-CLASS-2 req MAP_STC2_IND MAP-SECURE-TRANSPORT-CLASS-2 ind MAP_STC3_REQ MAP-SECURE-TRANSPORT-CLASS-3 req MAP_STC3_IND MAP-SECURE-TRANSPORT-CLASS-3 ind MAP_STC4_REQ MAP-SECURE-TRANSPORT-CLASS-4 req MAP_STC4_IND MAP-SECURE-TRANSPORT-CLASS-4 ind MAP_ACTSS_REQ MAP-ACTIVATE-SS req MAP_ACTSS_IND MAP-ACTIVATE-SS ind MAP_ACTSS_RES MAP-ACTIVATE-SS rsp MAP_ACTSS_CON MAP-ACTIVATE-SS cnf MAP_ACTTM_REQ MAP-ACTIVATE-TRACE-MODE req MAP_ACTTM_IND MAP-ACTIVATE-TRACE-MODE ind MAP_ACTTM_RES MAP-ACTIVATE-TRACE-MODE rsp MAP_ACTTM_CON MAP-ACTIVATE-TRACE-MODE cnf MAP_ALERTSC_REQ MAP-ALERT-SERVICE-CENTRE req MAP_ALERTSC_IND MAP-ALERT-SERVICE-CENTRE ind MAP_ALERTSC_RES MAP-ALERT-SERVICE-CENTRE rsp MAP_ALERTSC_CON MAP-ALERT-SERVICE-CENTRE cnf MAP_ALLOCHN_REQ MAP-ALLOCATE-HANDOVER-NUMBER req MAP_ALLOCHN_IND MAP-ALLOCATE-HANDOVER-NUMBER ind MAP_ALLOCHN_RES MAP-ALLOCATE-HANDOVER-NUMBER rsp MAP_ALLOCHN_CON MAP-ALLOCATE-HANDOVER-NUMBER cnf MAP_ANYMOD_REQ MAP-ANY-TIME-MODIFICATION req MAP_ANYMOD_IND MAP-ANY-TIME-MODIFICATION ind MAP_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_ANYQRY_REQ MAP_ANYQRY_IND MAP_ANYQRY_RES MAP_ANYQRY_CON MAP_ANYSUB_REQ MAP_ANYSUB_IND MAP_ANYSUB_RES MAP_ANYSUB_CON MAP_AUTH_REQ MAP_AUTH_IND MAP_AUTH_RES MAP_AUTH_CON MAP_AUTHFAIL_REQ MAP_AUTHFAIL_IND MAP_AUTHFAIL_RES MAP_AUTHFAIL_CON MAP_CANCLOC_REQ MAP_CANCLOC_IND MAP_CANCLOC_RES MAP_CANCLOC_CON MAP_CKIEMI_REQ MAP_CKIEMI_IND MAP_CKIEMI_RES MAP_CKIEMI_CON MAP_DEACTSS_REQ MAP_DEACTSS_IND MAP_DEACTSS_RES MAP_DEACTSS_CON MAP_DEACTTM_REQ MAP_DEACTTM_IND MAP_DEACTTM_RES MAP_DEACTTM_CON MAP_DELSUBD_REQ MAP_DELSUBD_IND MAP_DELSUBD_RES MAP_DELSUBD_CON MAP_ERASECC_REQ MAP_ERASECC_IND MAP_ERASECC_RES MAP_ERASECC_CON MAP_ERASESS_REQ MAP_ERASESS_IND MAP_ERASESS_RES MAP_ERASESS_CON

MAP-ANY-TIME-MODIFICATION cnf MAP-ANY-TIME-INTERROGATION req MAP-ANY-TIME-INTERROGATION ind MAP-ANY-TIME-INTERROGATION rsp MAP-ANY-TIME-INTERROGATION cnf MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION MAP-AUTHENTICATE req MAP-AUTHENTICATE ind MAP-AUTHENTICATE rsp MAP-AUTHENTICATE cnf MAP-AUTHENTICATION-FAILURE-REPORT req MAP-AUTHENTICATION-FAILURE-REPORT ind MAP-AUTHENTICATION-FAILURE-REPORT rsp MAP-AUTHENTICATION-FAILURE-REPORT cnf MAP-CANCEL-LOCATION req MAP-CANCEL-LOCATION ind MAP-CANCEL-LOCATION rsp MAP-CANCEL-LOCATION cnf MAP-CHECK-IEMI req MAP-CHECK-IEMI ind MAP-CHECK-IEMI rsp MAP-CHECK-IEMI cnf MAP-DEACTIVATE-SS req MAP-DEACTIVATE-SS ind MAP-DEACTIVATE-SS rsp MAP-DEACTIVATE-SS cnf MAP-DEACTIVATE-TRACE-MODE req MAP-DEACTIVATE-TRACE-MODE ind MAP-DEACTIVATE-TRACE-MODE rsp MAP-DEACTIVATE-TRACE-MODE cnf MAP-DELETE-SUBSCRIBER-DATA req MAP-DELETE-SUBSCRIBER-DATA ind MAP-DELETE-SUBSCRIBER-DATA rsp MAP-DELETE-SUBSCRIBER-DATA cnf MAP-ERASE-CC-ENTRY req MAP-ERASE-CC-ENTRY ind MAP-ERASE-CC-ENTRY rsp MAP-ERASE-CC-ENTRY cnf MAP-ERASE-SS req MAP-ERASE-SS ind MAP-ERASE-SS rsp MAP-ERASE-SS cnf

req ind rsp 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_IND MAP_FAILURE_RES MAP_FAILURE_CON MAP_FAS_REQ MAP_FAS_IND MAP_FAS_RES MAP_FAS_CON MAP_FCKSSIND_REQ MAP_FCKSSIND_IND MAP_FCKSSIND_RES MAP_FCKSSIND_CON MAP_FGRCSIG_REQ MAP_FGRCSIG_IND MAP_FGRCSIG_RES MAP_FGRCSIG_CON MAP_FNEWIMSI_REQ MAP_FNEWIMSI_IND MAP_FNEWIMSI_RES MAP_FNEWIMSI_CON MAP_GETIEMI_REQ MAP_GETIEMI_IND MAP_GETIEMI_RES MAP_GETIEMI_CON MAP_GETPASS_REQ MAP_GETPASS_IND MAP_GETPASS_RES MAP_GETPASS_CON MAP_INFORMSC_REQ MAP_INFORMSC_IND MAP_INFORMSC_RES MAP_INFORMSC_CON MAP_INSSUBSD_REQ MAP_INSSUBSD_IND MAP_INSSUBSD_RES MAP_INSSUBSD_CON MAP_INTERGSS_REQ MAP_INTERGSS_IND MAP_INTERGSS_RES MAP_INTERGSS_CON MAP_ISTALERT_REQ MAP_ISTALERT_IND MAP_ISTALERT_RES MAP_ISTALERT_CON MAP_ISTCMD_REQ 2008-10-31

MAP-FAILURE-REPORT req MAP-FAILURE-REPORT ind MAP-FAILURE-REPORT rsp MAP-FAILURE-REPORT cnf MAP-FORWARD-ACCESS-SIGNALLING req MAP-FORWARD-ACCESS-SIGNALLING ind MAP-FORWARD-ACCESS-SIGNALLING rsp MAP-FORWARD-ACCESS-SIGNALLING cnf MAP-FORWARD-CHECK-SS-INDICATION req MAP-FORWARD-CHECK-SS-INDICATION ind MAP-FORWARD-CHECK-SS-INDICATION rsp MAP-FORWARD-CHECK-SS-INDICATION cnf MAP-FORWARD-GROUP-CALL-SIGNALLING MAP-FORWARD-GROUP-CALL-SIGNALLING MAP-FORWARD-GROUP-CALL-SIGNALLING MAP-FORWARD-GROUP-CALL-SIGNALLING MAP-FORWARD-NEW-IMSI req MAP-FORWARD-NEW-IMSI ind MAP-FORWARD-NEW-IMSI rsp MAP-FORWARD-NEW-IMSI cnf MAP-OBTAIN-IEMI req MAP-OBTAIN-IEMI ind MAP-OBTAIN-IEMI rsp MAP-OBTAIN-IEMI cnf MAP-GET-PASSWORD req MAP-GET-PASSWORD ind MAP-GET-PASSWORD rsp MAP-GET-PASSWORD cnf MAP-INFORM-SERVICE-CENTER req MAP-INFORM-SERVICE-CENTER ind MAP-INFORM-SERVICE-CENTER rsp MAP-INFORM-SERVICE-CENTER cnf MAP-INSERT-SUBSCRIBER-DATA req MAP-INSERT-SUBSCRIBER-DATA ind MAP-INSERT-SUBSCRIBER-DATA rsp MAP-INSERT-SUBSCRIBER-DATA cnf MAP-INTERROGATE-SS req MAP-INTERROGATE-SS ind MAP-INTERROGATE-SS rsp MAP-INTERROGATE-SS cnf MAP-IST-ALERT req MAP-IST-ALERT ind MAP-IST-ALERT rsp MAP-IST-ALERT cnf MAP-IST-COMMAND req

req ind rsp cnf

385

Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002

MAP_ISTCMD_IND MAP_ISTCMD_RES MAP_ISTCMD_CON MAP_MMEVENT_REQ MAP_MMEVENT_IND MAP_MMEVENT_RES MAP_MMEVENT_CON MAP_MOFSMS_REQ MAP_MOFSMS_IND MAP_MOFSMS_RES MAP_MOFSMS_CON MAP_MSGRPSPRES_REQ MAP_MSGRPSPRES_IND MAP_MSGRPSPRES_RES MAP_MSGRPSPRES_CON MAP_MTFSMS_REQ MAP_MTFSMS_IND MAP_MTFSMS_RES MAP_MTFSMS_CON MAP_PAGE_REQ MAP_PAGE_IND MAP_PAGE_RES MAP_PAGE_CON MAP_PREPGC_REQ MAP_PREPGC_IND MAP_PREPGC_RES MAP_PREPGC_CON MAP_PREPHO_REQ MAP_PREPHO_IND MAP_PREPHO_RES MAP_PREPHO_CON MAP_PREPSH_REQ MAP_PREPSH_IND MAP_PREPSH_RES MAP_PREPSH_CON MAP_PROCAS_REQ MAP_PROCAS_IND MAP_PROCAS_RES MAP_PROCAS_CON MAP_PROCGC_REQ MAP_PROCGC_IND MAP_PROCGC_RES MAP_PROCGC_CON MAP_PROCUSS_REQ MAP_PROCUSS_IND

MAP-IST-COMMAND ind MAP-IST-COMMAND rsp MAP-IST-COMMAND cnf MAP-NOTE-MM-EVENT req MAP-NOTE-MM-EVENT ind MAP-NOTE-MM-EVENT rsp MAP-NOTE-MM-EVENT cnf MAP-MO-FORWARD-SHORT-MESSAGE req MAP-MO-FORWARD-SHORT-MESSAGE ind MAP-MO-FORWARD-SHORT-MESSAGE rsp MAP-MO-FORWARD-SHORT-MESSAGE cnf MAP-NOTE-MS-PRESENT-FOR-GPRS req MAP-NOTE-MS-PRESENT-FOR-GPRS ind MAP-NOTE-MS-PRESENT-FOR-GPRS rsp MAP-NOTE-MS-PRESENT-FOR-GPRS cnf MAP-MT-FORWARD-SHORT-MESSAGE req MAP-MT-FORWARD-SHORT-MESSAGE ind MAP-MT-FORWARD-SHORT-MESSAGE rsp MAP-MT-FORWARD-SHORT-MESSAGE cnf MAP-PAGE req MAP-PAGE ind MAP-PAGE rsp MAP-PAGE cnf MAP-PREPARE-GROUP-CALL req MAP-PREPARE-GROUP-CALL ind MAP-PREPARE-GROUP-CALL rsp MAP-PREPARE-GROUP-CALL cnf MAP-PREPARE-HANDOVER req MAP-PREPARE-HANDOVER ind MAP-PREPARE-HANDOVER rsp MAP-PREPARE-HANDOVER cnf MAP-PREPARE-SUBSEQUENT-HANDOVER req MAP-PREPARE-SUBSEQUENT-HANDOVER ind MAP-PREPARE-SUBSEQUENT-HANDOVER rsp MAP-PREPARE-SUBSEQUENT-HANDOVER cnf MAP-PROCESS-ACCESS-SIGNALLING req MAP-PROCESS-ACCESS-SIGNALLING ind MAP-PROCESS-ACCESS-SIGNALLING rsp MAP-PROCESS-ACCESS-SIGNALLING cnf MAP-PROCESS-GROUP-CALL-SIGNALLING req MAP-PROCESS-GROUP-CALL-SIGNALLING ind MAP-PROCESS-GROUP-CALL-SIGNALLING rsp MAP-PROCESS-GROUP-CALL-SIGNALLING cnf MAP-PROCESS-UNSTRUCTURED-SS-REQUEST req 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_PROCUSS_CON MAP_PROVIMSI_REQ MAP_PROVIMSI_IND MAP_PROVIMSI_RES MAP_PROVIMSI_CON MAP_PROVRN_REQ MAP_PROVRN_IND MAP_PROVRN_RES MAP_PROVRN_CON MAP_PROVSLOC_REQ MAP_PROVSLOC_IND MAP_PROVSLOC_RES MAP_PROVSLOC_CON MAP_PROVSUBI_REQ MAP_PROVSUBI_IND MAP_PROVSUBI_RES MAP_PROVSUBI_CON MAP_PURGEMS_REQ MAP_PURGEMS_IND MAP_PURGEMS_RES MAP_PURGEMS_CON MAP_RDYSM_REQ MAP_RDYSM_IND MAP_RDYSM_RES MAP_RDYSM_CON MAP_REGCC_REQ MAP_REGCC_IND MAP_REGCC_RES MAP_REGCC_CON MAP_REGPW_REQ MAP_REGPW_IND MAP_REGPW_RES MAP_REGPW_CON MAP_REGSS_REQ MAP_REGSS_IND MAP_REGSS_RES MAP_REGSS_CON MAP_REMUSRFREE_REQ MAP_REMUSRFREE_IND MAP_REMUSRFREE_RES MAP_REMUSRFREE_CON MAP_RESET_REQ MAP_RESET_IND MAP_RESET_RES 2008-10-31

MAP-PROCESS-UNSTRUCTURED-SS-REQUEST rsp MAP-PROCESS-UNSTRUCTURED-SS-REQUEST cnf MAP-PROVIDE-IMSI req MAP-PROVIDE-IMSI ind MAP-PROVIDE-IMSI rsp MAP-PROVIDE-IMSI cnf MAP-PROVIDE-ROAMING-NUMBER req MAP-PROVIDE-ROAMING-NUMBER ind MAP-PROVIDE-ROAMING-NUMBER rsp MAP-PROVIDE-ROAMING-NUMBER cnf MAP-PROVIDE-SUBSCRIBER-LOCATION req MAP-PROVIDE-SUBSCRIBER-LOCATION ind MAP-PROVIDE-SUBSCRIBER-LOCATION rsp MAP-PROVIDE-SUBSCRIBER-LOCATION cnf MAP-PROVIDE-SUBSCRIBER-INFO req MAP-PROVIDE-SUBSCRIBER-INFO ind MAP-PROVIDE-SUBSCRIBER-INFO rsp MAP-PROVIDE-SUBSCRIBER-INFO cnf MAP-PURGE-MS req MAP-PURGE-MS ind MAP-PURGE-MS rsp MAP-PURGE-MS cnf MAP-READY-FOR-SM req MAP-READY-FOR-SM ind MAP-READY-FOR-SM rsp MAP-READY-FOR-SM cnf MAP-REGISTER-CC-ENTRY req MAP-REGISTER-CC-ENTRY ind MAP-REGISTER-CC-ENTRY rsp MAP-REGISTER-CC-ENTRY cnf MAP-REGISTER-PASSWORD req MAP-REGISTER-PASSWORD ind MAP-REGISTER-PASSWORD rsp MAP-REGISTER-PASSWORD cnf MAP-REGISTER-SS req MAP-REGISTER-SS ind MAP-REGISTER-SS rsp MAP-REGISTER-SS cnf MAP-REMOTE-USER-FREE req MAP-REMOTE-USER-FREE ind MAP-REMOTE-USER-FREE rsp MAP-REMOTE-USER-FREE cnf MAP-RESET req MAP-RESET ind MAP-RESET rsp

387

Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002

MAP_RESET_CON MAP_RESTORE_REQ MAP_RESTORE_IND MAP_RESTORE_RES MAP_RESTORE_CON MAP_RESUME_REQ MAP_RESUME_IND MAP_RESUME_RES MAP_RESUME_CON MAP_SEARCH_REQ MAP_SEARCH_IND MAP_SEARCH_RES MAP_SEARCH_CON MAP_SENDAUTHI_REQ MAP_SENDAUTHI_IND MAP_SENDAUTHI_RES MAP_SENDAUTHI_CON MAP_SENDEND_REQ MAP_SENDEND_IND MAP_SENDEND_RES MAP_SENDEND_CON MAP_SENDGCEND_REQ MAP_SENDGCEND_IND MAP_SENDGCEND_RES MAP_SENDGCEND_CON MAP_SENDGPRSRI_REQ MAP_SENDGPRSRI_IND MAP_SENDGPRSRI_RES MAP_SENDGPRSRI_CON MAP_SENDHOREP_REQ MAP_SENDHOREP_IND MAP_SENDHOREP_RES MAP_SENDHOREP_CON MAP_SENDID_REQ MAP_SENDID_IND MAP_SENDID_RES MAP_SENDID_CON MAP_SENDIMSI_REQ MAP_SENDIMSI_IND MAP_SENDIMSI_RES MAP_SENDIMSI_CON MAP_SENDLCSRI_REQ MAP_SENDLCSRI_IND MAP_SENDLCSRI_RES MAP_SENDLCSRI_CON

MAP-RESET cnf MAP-RESTORE-DATA req MAP-RESTORE-DATA ind MAP-RESTORE-DATA rsp MAP-RESTORE-DATA cnf MAP-RESUME-CALL-HANDLING req MAP-RESUME-CALL-HANDLING ind MAP-RESUME-CALL-HANDLING rsp MAP-RESUME-CALL-HANDLING cnf MAP-SEARCH-FOR-MS req MAP-SEARCH-FOR-MS ind MAP-SEARCH-FOR-MS rsp MAP-SEARCH-FOR-MS cnf MAP-SEND-AUTHENTICATION-INFO req MAP-SEND-AUTHENTICATION-INFO ind MAP-SEND-AUTHENTICATION-INFO rsp MAP-SEND-AUTHENTICATION-INFO cnf MAP-SEND-END-SIGNAL req MAP-SEND-END-SIGNAL ind MAP-SEND-END-SIGNAL rsp MAP-SEND-END-SIGNAL cnf MAP-SEND-GROUP-CALL-END-SIGNAL req MAP-SEND-GROUP-CALL-END-SIGNAL ind MAP-SEND-GROUP-CALL-END-SIGNAL rsp MAP-SEND-GROUP-CALL-END-SIGNAL cnf MAP-SEND-ROUTING-INFO-FOR-GPRS req MAP-SEND-ROUTING-INFO-FOR-GPRS ind MAP-SEND-ROUTING-INFO-FOR-GPRS rsp MAP-SEND-ROUTING-INFO-FOR-GPRS cnf MAP-SEND-HANDOVER-REPORT req MAP-SEND-HANDOVER-REPORT ind MAP-SEND-HANDOVER-REPORT rsp MAP-SEND-HANDOVER-REPORT cnf MAP-SEND-IDENTIFICATION req MAP-SEND-IDENTIFICATION ind MAP-SEND-IDENTIFICATION rsp MAP-SEND-IDENTIFICATION cnf MAP-SEND-IMSI req MAP-SEND-IMSI ind MAP-SEND-IMSI rsp MAP-SEND-IMSI cnf MAP-SEND-ROUTING-INFO-FOR-LCS req MAP-SEND-ROUTING-INFO-FOR-LCS ind MAP-SEND-ROUTING-INFO-FOR-LCS rsp 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_SENDMOSMSI_IND MAP_SENDMOSMSI_RES MAP_SENDMOSMSI_CON MAP_SENDMTSMSI_REQ MAP_SENDMTSMSI_IND MAP_SENDMTSMSI_RES MAP_SENDMTSMSI_CON MAP_SENDRI_REQ MAP_SENDRI_IND MAP_SENDRI_RES MAP_SENDRI_CON MAP_SENDSMSRI_REQ MAP_SENDSMSRI_IND MAP_SENDSMSRI_RES MAP_SENDSMSRI_CON MAP_SETCM_REQ MAP_SETCM_IND MAP_SETCM_RES MAP_SETCM_CON MAP_SETREP_REQ MAP_SETREP_IND MAP_SETREP_RES MAP_SETREP_CON MAP_SMDELIVSTAT_REQ MAP_SMDELIVSTAT_IND MAP_SMDELIVSTAT_RES MAP_SMDELIVSTAT_CON MAP_SSINV_REQ MAP_SSINV_IND MAP_SSINV_RES MAP_SSINV_CON MAP_STATUS_REQ MAP_STATUS_IND MAP_STATUS_RES MAP_STATUS_CON MAP_SUBLOCREP_REQ MAP_SUBLOCREP_IND MAP_SUBLOCREP_RES MAP_SUBLOCREP_CON MAP_SUBSDATAMOD_REQ MAP_SUBSDATAMOD_IND MAP_SUBSDATAMOD_RES MAP_SUBSDATAMOD_CON MAP_TRACESA_REQ 2008-10-31

MAP-SEND-INFO-FOR-MO-SMS req MAP-SEND-INFO-FOR-MO-SMS ind MAP-SEND-INFO-FOR-MO-SMS rsp MAP-SEND-INFO-FOR-MO-SMS cnf MAP-SEND-INFO-FOR-MT-SMS req MAP-SEND-INFO-FOR-MT-SMS ind MAP-SEND-INFO-FOR-MT-SMS rsp MAP-SEND-INFO-FOR-MT-SMS cnf MAP-SEND-ROUTING-INFORMATION req MAP-SEND-ROUTING-INFORMATION ind MAP-SEND-ROUTING-INFORMATION rsp MAP-SEND-ROUTING-INFORMATION cnf MAP-SEND-ROUTING-INFO-FOR-SM req MAP-SEND-ROUTING-INFO-FOR-SM ind MAP-SEND-ROUTING-INFO-FOR-SM rsp MAP-SEND-ROUTING-INFO-FOR-SM cnf MAP-SET-CIPHERING-MODE req MAP-SET-CIPHERING-MODE ind MAP-SET-CIPHERING-MODE rsp MAP-SET-CIPHERING-MODE cnf MAP-SET-REPORTING-STATE req MAP-SET-REPORTING-STATE ind MAP-SET-REPORTING-STATE rsp MAP-SET-REPORTING-STATE cnf MAP-REPORT-SM-DELIVER-STATUS req MAP-REPORT-SM-DELIVER-STATUS ind MAP-REPORT-SM-DELIVER-STATUS rsp MAP-REPORT-SM-DELIVER-STATUS cnf MAP-SS-INVOCATION-NOTIFICATION req MAP-SS-INVOCATION-NOTIFICATION ind MAP-SS-INVOCATION-NOTIFICATION rsp MAP-SS-INVOCATION-NOTIFICATION cnf MAP-STATUS-REPORT req MAP-STATUS-REPORT ind MAP-STATUS-REPORT rsp MAP-STATUS-REPORT cnf MAP-SUBSCRIBER-LOCATION-REPORT req MAP-SUBSCRIBER-LOCATION-REPORT ind MAP-SUBSCRIBER-LOCATION-REPORT rsp MAP-SUBSCRIBER-LOCATION-REPORT cnf MAP-NOTE-SUBSCRIBER-DATA-MODIFIED req MAP-NOTE-SUBSCRIBER-DATA-MODIFIED ind MAP-NOTE-SUBSCRIBER-DATA-MODIFIED rsp MAP-NOTE-SUBSCRIBER-DATA-MODIFIED cnf MAP-TRACE-SUBSCRIBER-ACTIVITY req

389

Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002

MAP_TRACESA_IND MAP_TRACESA_RES MAP_TRACESA_CON MAP_UDGRPSLOC_REQ MAP_UDGRPSLOC_IND MAP_UDGRPSLOC_RES MAP_UDGRPSLOC_CON MAP_UDLOC_REQ MAP_UDLOC_IND MAP_UDLOC_RES MAP_UDLOC_CON MAP_USSDNTFY_REQ MAP_USSDNTFY_IND MAP_USSDNTFY_RES MAP_USSDNTFY_CON MAP_USSDREQ_REQ MAP_USSDREQ_IND MAP_USSDREQ_RES MAP_USSDREQ_CON

MAP-TRACE-SUBSCRIBER-ACTIVITY ind MAP-TRACE-SUBSCRIBER-ACTIVITY rsp MAP-TRACE-SUBSCRIBER-ACTIVITY cnf MAP-UPDATE-GPRS-LOCATION req MAP-UPDATE-GPRS-LOCATION ind MAP-UPDATE-GPRS-LOCATION rsp MAP-UPDATE-GPRS-LOCATION cnf MAP-UPDATE-LOCATION req MAP-UPDATE-LOCATION ind MAP-UPDATE-LOCATION rsp MAP-UPDATE-LOCATION cnf MAP-UNSTRUCTURED-SS-NOTIFY req MAP-UNSTRUCTURED-SS-NOTIFY ind MAP-UNSTRUCTURED-SS-NOTIFY rsp MAP-UNSTRUCTURED-SS-NOTIFY cnf MAP-UNSTRUCTURED-SS-REQUEST req MAP-UNSTRUCTURED-SS-REQUEST ind MAP-UNSTRUCTURED-SS-REQUEST rsp MAP-UNSTRUCTURED-SS-REQUEST cnf

A.1 Application Contexts


Table 1. Application Contexts Ver. v3 v3 v2 v3 v3 v3 Application Contexts locationCancellationContext equipmentMngtContext imsiRetrievalContext infoRetrievalContext interVlrInfoRetrievalContext handoverControlContext Operations cancelLocation checkIEMI sendIMSI sendAuthenticationInfo sendIdentication prepareHandover, forwareAccessSignalling, sendEndSignal, processAccessSignalling, prepareSubsequentHandover readyForSM purgeMS alertServiceCentre reset processUnstructuredSS-Request, unstructuredSS-Request, unstructuredSS-Notify activateTraceMode, deactivateTraceMode Version 0.9a Rel. 8

v3 v3 v2 v2 v2

mwdMngtContext msPurgingContext shortMsgAlertContext resetContext networkUnstructuredSsContext

v3

tracingContext

390

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

v2

networkFunctionalSsContext

v3 v3 v3

shortMsgMO-RelayContext shortMsgMT-RelayContext shortMsgGatewayContext

v3

networkLocUpContext

v3

gprsLocationUpdateContext

v3 v3 v3 v3 v4 v3 v4 v3 v3 v3 v3 v3

subscriberDataMngtContext roamingNumberEnquiryContext locationInfoRetrievalContext gprsNotifyContext gprsLocationInfoRetrievalContext failureReportContext callControlTransferContext susbcriberInfoEnquiryContext anyTimeEnquiryContext anyTimeInfoHandlingContext ss-InvocationNoticationContext groupCallControlContext

v3

reportingContext

v3 v3 v3

callCompletionContext isAlertingContext ServiceTerminationContext

registerSS, eraseSS, activateSS, deactivateSS, registerPassword, interrogateSS, getPassword mo-forwardSM mt-forwardSM sendRoutingInfoForSM, reportSM-DeliveryStatus, InformServiceCentre updateLocation, forwardCheckSs-Indication, restoreData, insertSubscriberData, activateTraceMode updateGprsLocation, insertSubscriberData, activateTraceMode insertSubscriberData, deleteSubscriberData provideRoamingNumber sendRoutingInfo noteMsPresentForGprs sendRoutingInfoForGprs failureReport resumeCallHandling provideSubscriberInfo anyTimeInterrogation anyTimeSubscriptionInterrogation, anyTimeModication ss-InvocationNotication prepareGroupCall, processGroupCallSignalling, forwardGroupCallSignalling, sendGroupCallEndSignal setReportingState, statusReport, remoteUserFree registerCC-Entry, eraceCC-Entry isAlert istCommand

2008-10-31

391

Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002

v3 v3 v3 v3 v3 v3

locationSvcEnquiryContext locationSvcGatewayContext mm-EventReportingContext subscriberDataModicationNoticationContext authenticationFailureReportContext secureTransportHandlingContext

provideSubscriberLocation, subscriberLocationReport sendRoutingInfoForLCS noteMM-Event noteSubscriberDataModied authenticationFailureReport 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 LICENSE Version 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 copies of 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 free in the sense of freedom: to assure everyone the eective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modications made by others. This License is a kind of copyleft, which means that derivative works of the document must 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 free software needs free documentation: a free program should come with manuals providing the same 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 published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

Terms and Conditions for Copying, Distribution and Modication


1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work that contains a notice placed by the 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 is a licensee, and is addressed as you. A Modied Version of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modications and/or translated into another language. A Secondary Section is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Documents overall subject (or to related matters) and contains nothing that could 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.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The Invariant Sections are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. The Cover Texts are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Transparent copy of the Document means a machine-readable copy, represented in a format whose specication is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent le format whose markup has been designed to thwart or discourage subsequent modication by readers is not Transparent. A copy that is not Transparent is called Opaque. Examples of suitable formats for Transparent copies include plain ascii without markup, Texinfo input format, LaTEX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modication. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only. The Title Page means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title 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 works title, preceding the beginning of the body of the text. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you 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 conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 400 Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

License

3. COPYING IN QUANTITY If you publish printed copies of the Document numbering more than 100, and the Documents license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to t legibly, you should put the rst ones listed (as many as t reasonably) on the actual cover, and continue the rest 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 Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (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 well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modied Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modied Version under precisely this License, with the Modied Version lling the role of the Document, thus licensing distribution and modication of the Modied Version to whoever possesses a copy of it. In addition, you must do these things in the Modied 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 as a 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 for authorship of the modications in the Modied Version, together with at least ve of the principal authors of the Document (all of its principal authors, if it has less than ve). C. State on the Title page the name of the publisher of the Modied Version, as the publisher. 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 modications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modied Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Documents 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 Modied Version as given 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 given on its Title Page, then add an item describing the Modied Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the 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 published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. In any section entitled Acknowledgments or Dedications, preserve the sections title, and preserve in the section all the substance and tone of each of the contributor acknowledgments and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. M. Delete any section entitled Endorsements. Such a section may not be included in the Modied Version. N. Do not retitle any existing section as Endorsements or to conict in title with any Invariant Section. If the Modied Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modied Versions license notice. These titles must be distinct from any other section titles. You may add a section entitled Endorsements, provided it contains nothing but endorsements of your Modied Version by various partiesfor example, statements of peer review or that the text has been approved by an organization as the authoritative denition of a standard. You may add a passage of up to ve words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modied Version. 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 already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modied Version. 5. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms dened in section 4 above for modied versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodied, and list them all as Invariant Sections of your combined work in its license notice. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but dierent contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections entitled History in the various original documents, forming one section entitled History; likewise combine any sections entitled Acknowledgments, and any sections entitled Dedications. You must delete all sections entitled Endorsements. 6. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modied Version of the Document, provided no compilation copyright 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 with the Document, on account of their being thus compiled, if they are not themselves derivative 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 Documents Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate. 8. TRANSLATION Translation is considered a kind of modication, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may dier in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. Each version of the License is given a distinguishing version number. If the Document species 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 that specied version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software 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 the document 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 which ones are invariant. If you have no Front-Cover Texts, write no Front-Cover Texts instead of Front-Cover Texts being list; likewise for Back-Cover Texts. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.

2008-10-31

405

Mobile Application Part Interface (MAPI)

Index

Index
A
ADDR_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39 ADDR_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39 MAP_AUTHFAIL_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 MAP_AUTHFAIL_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 MAP_AUTHFAIL_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 MAP_BIND_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 MAP_bind_ack_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 MAP_BIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 MAP_bind_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 MAP_CANCLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 MAP_CANCLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 MAP_CANCLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 MAP_CANCLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 MAP_CKIEMI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 MAP_CKIEMI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 MAP_CKIEMI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 MAP_CKIEMI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 MAP_CLOSE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 MAP_CLOSE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 MAP_DEACTSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 MAP_DEACTSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 MAP_DEACTSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 MAP_DEACTSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 MAP_DEACTTM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 MAP_DEACTTM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 MAP_DEACTTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 MAP_DEACTTM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 MAP_DELIM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 MAP_DELIM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 MAP_DELSUBD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 MAP_DELSUBD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 MAP_DELSUBD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 MAP_DELSUBD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 MAP_ERASECC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 MAP_ERASECC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 MAP_ERASECC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 MAP_ERASECC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 MAP_ERASESS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 MAP_ERASESS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 MAP_ERASESS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 MAP_ERASESS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 MAP_ERROR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 MAP_FAILURE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 MAP_FAILURE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 MAP_FAILURE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 MAP_FAILURE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 MAP_FAS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 MAP_FAS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 MAP_FAS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 MAP_FAS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 MAP_FCKSSIND_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 MAP_FCKSSIND_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 MAP_FCKSSIND_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 MAP_FCKSSIND_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

D
DIAIND_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39

L
license, FDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 license, GNU Free Documentation License . . . . 399

M
MAP_ABORT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 MAP_ACTSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 MAP_ACTSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 MAP_ACTSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 MAP_ACTSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 MAP_ACTTM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 MAP_ACTTM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 MAP_ACTTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 MAP_ACTTM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 MAP_ADDR_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 MAP_ADDR_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 MAP_addr_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 MAP_ALERTSC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 MAP_ALERTSC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 MAP_ALERTSC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 MAP_ALERTSC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 MAP_ALLOCHN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 MAP_ALLOCHN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 MAP_ALLOCHN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 MAP_ALLOCHN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 MAP_ANYMOD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 MAP_ANYMOD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 MAP_ANYMOD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 MAP_ANYMOD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 MAP_ANYQRY_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 MAP_ANYQRY_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 MAP_ANYQRY_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 MAP_ANYQRY_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 MAP_ANYSUB_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 MAP_ANYSUB_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 MAP_ANYSUB_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 MAP_ANYSUB_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 MAP_AUTH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 MAP_AUTH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 MAP_AUTH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 MAP_AUTH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 MAP_AUTHFAIL_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2008-10-31

407

Index

MAP_FGRCSIG_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 MAP_FGRCSIG_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 MAP_FGRCSIG_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 MAP_FGRCSIG_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 MAP_FNEWIMSI_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 MAP_FNEWIMSI_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 MAP_FNEWIMSI_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 MAP_FNEWIMSI_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 MAP_GETIEMI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 MAP_GETIEMI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 MAP_GETIEMI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 MAP_GETIEMI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 MAP_GETPASS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 MAP_GETPASS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 MAP_GETPASS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 MAP_GETPASS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 MAP_INFO_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 MAP_info_ack_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 MAP_INFO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 MAP_info_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 MAP_INFORMSC_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 MAP_INFORMSC_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 MAP_INFORMSC_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 MAP_INFORMSC_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 MAP_INSSUBSD_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 MAP_INSSUBSD_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 MAP_INSSUBSD_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 MAP_INSSUBSD_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 MAP_INTERGSS_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 MAP_INTERGSS_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 MAP_INTERGSS_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 MAP_INTERGSS_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 MAP_ISTALERT_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 MAP_ISTALERT_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 MAP_ISTALERT_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 MAP_ISTALERT_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 MAP_ISTCMD_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 MAP_ISTCMD_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 MAP_ISTCMD_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 MAP_ISTCMD_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 MAP_MMEVENT_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 MAP_MMEVENT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 MAP_MMEVENT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 MAP_MMEVENT_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 MAP_MOFSMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 MAP_MOFSMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 MAP_MOFSMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 MAP_MOFSMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 MAP_MSGRPSPRES_CON . . . . . . . . . . . . . . . . . . . . . . . . . 207 MAP_MSGRPSPRES_IND . . . . . . . . . . . . . . . . . . . . . . . . . 205 MAP_MSGRPSPRES_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 204 MAP_MSGRPSPRES_RES . . . . . . . . . . . . . . . . . . . . . . . . . 206 MAP_MTFSMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 MAP_MTFSMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 MAP_MTFSMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 MAP_MTFSMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

MAP_NOTICE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 MAP_OK_ACK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 MAP_OPEN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 MAP_OPEN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 MAP_OPEN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 MAP_OPEN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 MAP_OPTMGMT_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 MAP_OPTMGMT_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 MAP_optmgmt_req_t. . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 MAP_PABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 MAP_PAGE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 MAP_PAGE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 MAP_PAGE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 MAP_PAGE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 MAP_PREPGC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 MAP_PREPGC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 MAP_PREPGC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 MAP_PREPGC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 MAP_PREPHO_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 MAP_PREPHO_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 MAP_PREPHO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 MAP_PREPHO_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 MAP_PREPSH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 MAP_PREPSH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 MAP_PREPSH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 MAP_PREPSH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 MAP_PROCAS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 MAP_PROCAS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 MAP_PROCAS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 MAP_PROCAS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 MAP_PROCGC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 MAP_PROCGC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 MAP_PROCGC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 MAP_PROCGC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 MAP_PROCUSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 MAP_PROCUSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 MAP_PROCUSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 MAP_PROCUSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 MAP_PROVIMSI_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 MAP_PROVIMSI_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 MAP_PROVIMSI_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 MAP_PROVIMSI_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 MAP_PROVRN_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 MAP_PROVRN_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 MAP_PROVRN_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 MAP_PROVRN_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 MAP_PROVSLOC_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 MAP_PROVSLOC_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 MAP_PROVSLOC_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 MAP_PROVSLOC_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 MAP_PROVSUBI_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 MAP_PROVSUBI_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 MAP_PROVSUBI_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 MAP_PROVSUBI_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 MAP_PURGEMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 MAP_PURGEMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

408

Version 0.9a Rel. 8

Mobile Application Part Interface (MAPI)

Index

MAP_PURGEMS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_PURGEMS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RDYSM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RDYSM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RDYSM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RDYSM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGCC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGCC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGCC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGCC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGPW_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGPW_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGPW_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGPW_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGSS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGSS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGSS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REGSS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REMUSRFREE_CON . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REMUSRFREE_IND . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REMUSRFREE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . MAP_REMUSRFREE_RES . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESET_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESET_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESET_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESET_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESTORE_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESTORE_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESTORE_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESTORE_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESUME_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESUME_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESUME_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_RESUME_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SEARCH_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SEARCH_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SEARCH_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SEARCH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDAUTHI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDAUTHI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDAUTHI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDAUTHI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDEND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDEND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDEND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDEND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGCEND_CON . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGCEND_IND . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGCEND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGCEND_RES . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGPRSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGPRSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGPRSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDGPRSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDHOREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_SENDHOREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . .

256 258 263 261 260 262 267 265 264 266 271 269 268 270 275 273 272 274 279 277 276 278 110 109 108 111 114 113 112 115 119 117 116 118 123 121 120 122 299 297 296 298 303 301 300 302 307 305 304 306 311 309 308 310 315 313

MAP_SENDHOREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 312 MAP_SENDHOREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 314 MAP_SENDID_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 MAP_SENDID_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 MAP_SENDID_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 MAP_SENDID_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 MAP_SENDIMSI_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 MAP_SENDIMSI_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 MAP_SENDIMSI_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 MAP_SENDIMSI_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 MAP_SENDLCSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 323 MAP_SENDLCSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 321 MAP_SENDLCSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 320 MAP_SENDLCSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 322 MAP_SENDMOSMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 327 MAP_SENDMOSMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 325 MAP_SENDMOSMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 324 MAP_SENDMOSMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 326 MAP_SENDMTSMSI_CON . . . . . . . . . . . . . . . . . . . . . . . . . 331 MAP_SENDMTSMSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . 329 MAP_SENDMTSMSI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 328 MAP_SENDMTSMSI_RES . . . . . . . . . . . . . . . . . . . . . . . . . 330 MAP_SENDRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 MAP_SENDRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 MAP_SENDRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 MAP_SENDRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 MAP_SENDSMSRI_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 339 MAP_SENDSMSRI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 337 MAP_SENDSMSRI_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 336 MAP_SENDSMSRI_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 338 MAP_SETCM_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 MAP_SETCM_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 MAP_SETCM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 MAP_SETCM_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 MAP_SETREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 MAP_SETREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 MAP_SETREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 MAP_SETREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 MAP_SMDELIVSTAT_CON . . . . . . . . . . . . . . . . . . . . . . . . 295 MAP_SMDELIVSTAT_IND . . . . . . . . . . . . . . . . . . . . . . . . 293 MAP_SMDELIVSTAT_REQ . . . . . . . . . . . . . . . . . . . . . . . . 292 MAP_SMDELIVSTAT_RES . . . . . . . . . . . . . . . . . . . . . . . . 294 MAP_SSINV_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 MAP_SSINV_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 MAP_SSINV_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 MAP_SSINV_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 MAP_STATUS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 MAP_STATUS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 MAP_STATUS_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 MAP_STATUS_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 MAP_STC1_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 MAP_STC1_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 MAP_STC2_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 MAP_STC2_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 MAP_STC3_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 MAP_STC3_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

2008-10-31

409

Index

MAP_STC4_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 MAP_STC4_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 MAP_SUBLOCREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 351 MAP_SUBLOCREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 349 MAP_SUBLOCREP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 348 MAP_SUBLOCREP_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 350 MAP_SUBSDATAMOD_CON . . . . . . . . . . . . . . . . . . . . . . . . 355 MAP_SUBSDATAMOD_IND . . . . . . . . . . . . . . . . . . . . . . . . 353 MAP_SUBSDATAMOD_REQ . . . . . . . . . . . . . . . . . . . . . . . . 352 MAP_SUBSDATAMOD_RES . . . . . . . . . . . . . . . . . . . . . . . . 354 MAP_TRACESA_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 MAP_TRACESA_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 MAP_TRACESA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 MAP_TRACESA_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 MAP_UABORT_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 MAP_UDGRPSLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 363 MAP_UDGRPSLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 361 MAP_UDGRPSLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . 360 MAP_UDGRPSLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . 362 MAP_UDLOC_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 MAP_UDLOC_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 MAP_UDLOC_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 MAP_UDLOC_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 MAP_UNBIND_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

MAP_unbind_req_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 MAP_USSDNTFY_CON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 MAP_USSDNTFY_IND. . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 MAP_USSDNTFY_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 MAP_USSDNTFY_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 MAP_USSDREQ_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 MAP_USSDREQ_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 MAP_USSDREQ_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 MAP_USSDREQ_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 MGMT_flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

O
OPT_length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 OPT_offset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

P
PRIM_type . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39, 41, 43 PRIM_type:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

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

410

Version 0.9a Rel. 8

Vous aimerez peut-être aussi