You are on page 1of 438

Mobile Application Part Interface (MAPI) Specification

Mobile Application Part Interface (MAPI) Specification


Version 1.1 Edition 1.20110510 Updated October 28, 2011 Distributed with Package openss7-1.1.1.20110510

Copyright c 2008-2011 Monavacon Limited All Rights Reserved.

Abstract:
This document is a Specification 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). It provides abstraction of the Mobile Application Part (MAP) interface to these components as well as providing a basis for Mobile Application Part control for other Mobile Application Part protocols.

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

Published by:
OpenSS7 Corporation 1469 Jefferys Crescent Edmonton, Alberta T6L 6T1 Canada Copyright c 2008-2011 Monavacon Limited Copyright c 2001-2008 OpenSS7 Corporation Copyright c 1997-2000 Brian F. G. Bidulock All Rights Reserved. Unauthorized distribution or duplication is prohibited. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [GNU Free Documentation License], page 410. Permission to use, copy and distribute this documentation without modification, 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 specific, 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, fitness 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 profits, 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.

Short Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2 The Mobile Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 MAPI Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4 MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5 Diagnostics Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Addendum for 3GPP Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 A Mapping MAPI Primitives to 3GPP TS 29.002. . . . . . . . . . . . . . 383 B State/Event Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 C Primitive Precedence Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 D MAPI Header File Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

iii

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISO 9000 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . U.S. Government Restricted Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 3 3 3 3 4 4 4 4 5

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1.1 Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2 Definitions, 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 Specific 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 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

iv

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

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


3.1 Local Management Services Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 24 25 26 26 26 27 27 28 28 28

MAPI Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1 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 Confirmation . . . . . . . . . . . . . . . . . . . . . . . . 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 Specific 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 Confirmation . . . . . . . . . . . . . . . . . . . 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 Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.9 Alert Service Center Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.10 Alert Service Center Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Allocate Handover Number Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Allocate Handover Number Indication . . . . . . . . . . . . . . . . . . . . . . . . . 81 Allocate Handover Number Response . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Allocate Handover Number Confirmation . . . . . . . . . . . . . . . . . . . . . . 83 Any Time Modification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Any Time Modification Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Any Time Modification Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Any Time Modification Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Any Time Interrogation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Any Time Interrogation Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Any Time Interrogation Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Any Time Interrogation Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Any Time Subscription Interrogation Request . . . . . . . . . . . . . . . . . . 92 Any Time Subscription Interrogation Indication . . . . . . . . . . . . . . . . 93 Any Time Subscription Interrogation Response . . . . . . . . . . . . . . . . . 94 Any Time Subscription Interrogation Confirmation . . . . . . . . . . . . . 95 Authentication Failure Report Request. . . . . . . . . . . . . . . . . . . . . . . . . 96 Authentication Failure Report Indication . . . . . . . . . . . . . . . . . . . . . . 97 Authentication Failure Report Response . . . . . . . . . . . . . . . . . . . . . . . 98 Authentication Failure Report Confirmation . . . . . . . . . . . . . . . . . . . 99 Authenticate Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Authenticate Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Authenticate Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Authenticate Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Cancel Location Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Cancel Location Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Cancel Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Cancel Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Reset Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Reset Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Reset Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Reset Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Restore Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Restore Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Restore Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Restore Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Resume Call Handling Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Resume Call Handling Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Resume Call Handling Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Resume Call Handling Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Search for MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Search for MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Search for MS Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivate Supplementary Service Request . . . . . . . . . . . . . . . . . . . . Deactivate Supplementary Service Indication . . . . . . . . . . . . . . . . . . Deactivate Supplementary Service Response . . . . . . . . . . . . . . . . . . Deactivate Supplementary Service Confirmation. . . . . . . . . . . . . . . Deactivate Trace Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivate Trace Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivate Trace Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivate Trace Mode Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Subscriber Data Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase CC Entry Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Erase Supplementatry Service Request . . . . . . . . . . . . . . . . . . . . . . . . Erase Supplementatry Service Indication . . . . . . . . . . . . . . . . . . . . . . Erase Supplementatry Service Response. . . . . . . . . . . . . . . . . . . . . . . Erase Supplementatry Service Confirmation . . . . . . . . . . . . . . . . . . . Failure Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failure Report Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Indication. . . . . . . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Response . . . . . . . . . . . . . . . . . . . . . . . . . . Forward Access Signalling Confirmation . . . . . . . . . . . . . . . . . . . . . . Forward Check SS Indication Request. . . . . . . . . . . . . . . . . . . . . . . . . Forward Check SS Indication Indication . . . . . . . . . . . . . . . . . . . . . . Forward Check SS Indication Response . . . . . . . . . . . . . . . . . . . . . . . Forward Check SS Indication Confirmation . . . . . . . . . . . . . . . . . . . Forward Group Call Signalling Request . . . . . . . . . . . . . . . . . . . . . . . Forward Group Call Signalling Indication . . . . . . . . . . . . . . . . . . . . . Forward Group Call Signalling Response . . . . . . . . . . . . . . . . . . . . . . Forward Group Call Signalling Confirmation . . . . . . . . . . . . . . . . . . Forward New IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward New IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward New IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forward New IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtain IEMI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 4.6.107 4.6.108 4.6.109 4.6.110 4.6.111 4.6.112 4.6.113 4.6.114 4.6.115 4.6.116 4.6.117 4.6.118 4.6.119 4.6.120 4.6.121 4.6.122 4.6.123 4.6.124 4.6.125 4.6.126 4.6.127 4.6.128 4.6.129 4.6.130 4.6.131 4.6.132 4.6.133 4.6.134 4.6.135 4.6.136 4.6.137 4.6.138 4.6.139 4.6.140 4.6.141 4.6.142 4.6.143 4.6.144 4.6.145 4.6.146 4.6.147 4.6.148 4.6.149 4.6.150 4.6.151 4.6.152 4.6.153 4.6.154

Mobile Application Part Interface (MAPI) Get Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get Password Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inform Service Center Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inform Service Center Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inform Service Center Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inform Service Center Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . Insert Subscriber Data Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insert Subscriber Data Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insert Subscriber Data Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insert Subscriber Data Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . Iterrogate Supplementary Service Request . . . . . . . . . . . . . . . . . . . Iterrogate Supplementary Service Indication . . . . . . . . . . . . . . . . . Iterrogate Supplementary Service Response . . . . . . . . . . . . . . . . . . Iterrogate Supplementary Service Confirmation . . . . . . . . . . . . . . IST Alert Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Alert Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Alert Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Alert Confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Command Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Command Indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IST Command Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note MM Event Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note MM Event Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note MM Event Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note MM Event Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Originated Forward Short Message Request . . . . . . . . . . Mobile Originated Forward Short Message Indication . . . . . . . . Mobile Originated Forward Short Message Response . . . . . . . . . Mobile Originated Forward Short Message Confirmation . . . . . Note MS Present for GRPS Request . . . . . . . . . . . . . . . . . . . . . . . . . Note MS Present for GRPS Indication . . . . . . . . . . . . . . . . . . . . . . . Note MS Present for GRPS Response . . . . . . . . . . . . . . . . . . . . . . . . Note MS Present for GRPS Confirmation . . . . . . . . . . . . . . . . . . . . Mobile Terminated Forward Short Message Request . . . . . . . . . . Mobile Terminated Forward Short Message Indication. . . . . . . . Mobile Terminated Forward Short Message Response . . . . . . . . Mobile Terminated Forward Short Message Confirmation . . . . Page Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Group Call Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Group Call Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Group Call Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Group Call Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Handover Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Handover Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221

ix 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 4.6.200 4.6.201 4.6.202 Prepare Handover Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Handover Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare Subsequent Handover Request. . . . . . . . . . . . . . . . . . . . . . . Prepare Subsequent Handover Indication . . . . . . . . . . . . . . . . . . . . Prepare Subsequent Handover Response . . . . . . . . . . . . . . . . . . . . . Prepare Subsequent Handover Confirmation . . . . . . . . . . . . . . . . . Process Access Signalling Request . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Access Signalling Indication . . . . . . . . . . . . . . . . . . . . . . . . . Process Access Signalling Response . . . . . . . . . . . . . . . . . . . . . . . . . . Process Access Signalling Confirmation . . . . . . . . . . . . . . . . . . . . . . Process Group Call Signalling Request . . . . . . . . . . . . . . . . . . . . . . . Process Group Call Signalling Indication . . . . . . . . . . . . . . . . . . . . . Process Group Call Signalling Response . . . . . . . . . . . . . . . . . . . . . Process Group Call Signalling Confirmation. . . . . . . . . . . . . . . . . . Process Unstructured SS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Unstructured SS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . Process Unstructured SS Response . . . . . . . . . . . . . . . . . . . . . . . . . . Process Unstructured SS Confirmation . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide IMSI Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provide Roaming Number Request . . . . . . . . . . . . . . . . . . . . . . . . . . Provide Roaming Number Indication . . . . . . . . . . . . . . . . . . . . . . . . Provide Roaming Number Response . . . . . . . . . . . . . . . . . . . . . . . . . Provide Roaming Number Confirmation . . . . . . . . . . . . . . . . . . . . . Provide Subscriber Location Request . . . . . . . . . . . . . . . . . . . . . . . . Provide Subscriber Location Indication . . . . . . . . . . . . . . . . . . . . . . Provide Subscriber Location Response . . . . . . . . . . . . . . . . . . . . . . . Provide Subscriber Location Confirmation . . . . . . . . . . . . . . . . . . . Provide Subscriber Information Request . . . . . . . . . . . . . . . . . . . . . Provide Subscriber Information Indication . . . . . . . . . . . . . . . . . . . Provide Subscriber Information Response . . . . . . . . . . . . . . . . . . . . Provide Subscriber Information Confirmation . . . . . . . . . . . . . . . . Purge MS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge MS Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge MS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge MS Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ready for SM Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register CC Entry Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register Password Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register Password Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 267 268 269

x 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 4.6.248 4.6.249 4.6.250

Mobile Application Part Interface (MAPI) Register Password Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register Password Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register Supplementary Service Request . . . . . . . . . . . . . . . . . . . . . Register Supplementary Service Indication . . . . . . . . . . . . . . . . . . . Register Supplementary Service Response . . . . . . . . . . . . . . . . . . . . Register Supplementary Service Confirmation . . . . . . . . . . . . . . . . Remote User Free Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote User Free Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote User Free Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote User Free Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Identification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Identification Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Identification Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Identification Confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Ciphering Mode Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Indication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Reporting State Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Short Message Delivery Status Request . . . . . . . . . . . . . . Report Short Message Delivery Status Indication . . . . . . . . . . . . Report Short Message Delivery Status Response . . . . . . . . . . . . . Report Short Message Delivery Status Confirmation . . . . . . . . . Send Authentication Information Request. . . . . . . . . . . . . . . . . . . . Send Authentication Information Indication . . . . . . . . . . . . . . . . . Send Authentication Information Response . . . . . . . . . . . . . . . . . . Send Authentication Information Confirmation . . . . . . . . . . . . . . Send End Signal Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send End Signal Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send End Signal Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send End Signal Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Group Call End Signal Request . . . . . . . . . . . . . . . . . . . . . . . . Send Group Call End Signal Indication . . . . . . . . . . . . . . . . . . . . . . Send Group Call End Signal Response . . . . . . . . . . . . . . . . . . . . . . . Send Group Call End Signal Confirmation . . . . . . . . . . . . . . . . . . . Send Routing Information for GPRS Request . . . . . . . . . . . . . . . . Send Routing Information for GPRS Indication . . . . . . . . . . . . . . Send Routing Information for GPRS Response . . . . . . . . . . . . . . . Send Routing Information for GPRS Confirmation . . . . . . . . . . . Send Handover Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Handover Report Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Handover Report Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Handover Report Confirmation. . . . . . . . . . . . . . . . . . . . . . . . . Send IMSI Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send IMSI Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 315 316 317

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

xii 4.6.299 4.6.300 4.6.301 4.6.302 4.6.303 4.6.304 4.6.305 4.6.306 4.6.307 4.6.308

Mobile Application Part Interface (MAPI) Update Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Location Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unstructured Supplementary Service Notify Request . . . . . . . . . Unstructured Supplementary Service Notify Indication . . . . . . . Unstructured Supplementary Service Notify Response . . . . . . . . Unstructured Supplementary Service Notify Confirmation . . . . Unstructured Supplementary Service Request . . . . . . . . . . . . . . . . Unstructured Supplementary Service Indication . . . . . . . . . . . . . . Unstructured Supplementary Service Response . . . . . . . . . . . . . . . Unstructured Supplementary Service Confirmation . . . . . . . . . . . 366 367 368 369 370 371 372 373 374 375

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


5.1 5.2 Non-Fatal Error Handling Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 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

Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
GNU Affero General Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Apply These Terms to Your New Programs . . . . . . . . . . . . . . . . . . . GNU Free Documentation License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 399 409 410

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Mobile Application Part Interface (MAPI)

Table of Contents

List of Figures

2011-10-28

List of Tables

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Preface

Preface
Notice
Software in this document and related software is released under the AGPL (see [GNU Affero General Public License], page 399). Please note, however, that there are different licensing terms for some of the manual package and some of the documentation. Consult permission notices contained in the documentation of those components for more information. This document is released under the FDL (see [GNU Free Documentation License], page 410) with no invariant sections, no front-cover texts and no back-cover texts.

Abstract
This document is a Specification 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). This document specifies a Mobile Application Part Interface (MAPI) Specification in support of the OpenSS7 Mobile Application Part (MAP) protocol stacks. It provides abstraction of the Mobile Application Part interface to these components as well as providing a basis for Mobile Application Part control for other Mobile Application Part protocols. 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 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.

Revision History
Take care that you are working with a current version of this documentation: you will not be notified of updates. To ensure that you are working with a current version, check the OpenSS7 Project website for a current version. 2011-10-28 3

Preface

A current version of this specification is normally distributed with the OpenSS7 package, openss7-1.1.1.20110510.1 Version Control 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. OpenSS7 Corporation is making this documentation available as a reference point for the industry. While OpenSS7 Corporation believes that these interfaces are well defined in this release of the document, minor changes may be made prior to products conforming to the interfaces being made available. OpenSS7 Corporation reserves the right to revise this software and documentation for any reason, including but not limited to, conformity with standards promulgated by various agencies, utilization of advances in the state of the technical arts, or the reflection 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.
$Log: mapi.texi,v $ Revision 1.1.2.2 2011-02-07 02:21:40 - updated manuals Revision 1.1.2.1 2009-06-21 10:53:58 - added files to new distro brian

brian

ISO 9000 Compliance


Only the TEX, texinfo, or roff source for this maual is controlled. An opaque (printed, postscript or portable document format) version of this manual is a UNCONTROLLED VERSION. Disclaimer OpenSS7 Corporation disclaims all warranties with regard to this documentation including all implied warranties of merchantability, fitness for a particular purpose, non-infrincement, or title; that the contents of the manual 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 profits, whether in an action or contract, negligence or other tortious action, arising out of or in connection with any use of this documentation or the performance or implementation of the contents thereof. U.S. Government Restricted Rights If you are licensing this Software on behalf of the U.S. Government ("Government"), the following provisions apply to you. If the Software is supplied by the Department of Defense ("DoD"), it is classified as "Commercial Computer Software" under paragraph 252.227-7014 of the DoD Supplement to the Federal Aquisition Regulations ("DFARS") (or any successor regulations) and the Government is acquiring only the license rights granded herein (the license rights customarily provided to non-Government users). If the Software is supplied to any unit or agency of the Government other than DoD, it is classified as "Restricted Computer Software" and the Governments rights in the
1

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

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Preface

Software are defined in paragraph 52.227-19 of the Federal Acquisition Regulations ("FAR") (or any successor regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the NASA Supplerment to the FAR (or any successor regulations).

Acknowledgements
The OpenSS7 Project was funded in part by: Monavacon Limited OpenSS7 Corporation Thanks to the subscribers to and sponsors of The OpenSS7 Project. Without their support, open software like this would not be possible. As with most open source projects, this project would not have been possible without the valiant efforts and productive software of the Free Software Foundation, the Linux Kernel Community, and the open source software movement at large.

2011-10-28

Mobile Application Part Interface (MAPI)

Introduction

1 Introduction
This document specifies a STREAMS-based kernel-level instantiation of the 3GPP GSM/UMTS TS.29002 Mobile Application Part (MAP) service definition. The Mobile Application Part Interface (MAPI) enables the user of a mobile application service to access and use a wide variety of conforming mobile application service providers without specific knowledge of the providers protocol. The service interface is designed to support any operation class of transaction protocol. This interface only specifies access to mobile application layer service providers, and does not address issues concerning mobile application layer management, protocol performance, and performance analysis tools. This specification 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 Definition, Issue 2 Volume 3 CCITT Recommendation X.200 CCITT Recommendation X.201 System V Interface Definition, Issue 2 - Volume 3 1.1.1 Role This document specifies an interface that supports the service provided by the Mobile Applications Part (MAP) specification for 3GPP GSM/UMTS as described in 3GPP TS 29.002. These specifications are targeted for use by developers and testers of protocol modules that require Mobile Applications Part services.

1.2 Definitions, Acronyms, Abbreviations


Application Context Object Identifier Calling Party The Calling Party. Called Party The Called Party. Operations Class One of 5 ISO/OSI Transport Protocol Classes. MAP TCAP SCCP 2011-10-28 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 Identifier 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 Components Transaction components as defined in ITU-T Recommendation Q.771. QoS Quality of Service The Mobile Application Part (MAP) Interface. Mobile Station.

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

Version 1.1 Rel. 1.20110510

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 defines 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 defined as STREAMS messages that provide access to the MAP layer services, and are transferred between the MAP user entity and the MAP provider. These 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 confirmation of a request or are indications to the MAP user that the event has occurred. Figure 1 shows the model of the MAPI. (See 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 configured with any MAP user (such as an HLR, MSC or SGSN application) that also conforms to the MAPI. A MAP user can also be a user program that conforms to the MAPI and accesses the MAP provider using putmsg() and getmsg() system calls.1
1

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

2011-10-28

Chapter 2: The Mobile Application Layer

2.2 MAP Services


The features of the MAP are defined in terms of the services provided by the MAP provider, and the individual primitives that may flow between the MAP users and the MAP provider. The services provided by the MAP are based on a number of application contexts 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 specifications also define a set of local management functions that apply to all application contexts. These services have local significance only. Tables 1 and 2 summarizes the MAPI service primitives by their state and service. 2.2.2 Common Services

Table X. Common Services Service MAP OPEN MAP DELIM MAP CLOSE MAP UABORT MAP PABORT MAP NOTICE MAP STC1 MAP STC2 MAP STC3 MAP STC4 2.2.3 Specific Services Invoker Performer

User Provider

User User

Table 3. Specific Services Service MAP ACTSS MAP ACTTM MAP ALERTSC MAP ANYMOD MAP ANYSUB Invoker MSC VLR HLR HLR SCF PNA SCF Performer VLR HLR VLR or SGSN SMS-IWMSC HLR VLR or SGSN HLR

10

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

MAP MAP MAP MAP

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 MAP MAP MAP MAP MAP ISTALERT ISTCMD MMEVENT MSGPRSPRES SUBSDATAMOD PREPGC PREPHO PREPSH PROCAS PROCGC PROCUSS PROVRN PROVSLOC PROVSUBI PURGEMS RDYSM

MAP REGCC

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 VLR VLR or SGSN MSC VLR or SGSN MSC VLR

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 SGSN HLR VLR HLR VLR HLR

2011-10-28

11

Chapter 2: The Mobile Application Layer

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

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

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 MAP MMEVENT 2.3.1.2 Paging and Search Service MAP PAGE Invoker VLR Performer MSC Invoker VLR HLR VLR VLR or SGSN SGSN VLR or SGSN Performer HLR VLR or SGSN old VLR HLR HLR SCF

12

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

MAP SEARCH 2.3.1.3 Access Management Services Service MAP PROCAS 2.3.1.4 Handover Services Service MAP PREPHO MAP SENDEND MAP PROCAS MAP FAS MAP PREPSH MAP ALLOCHN MAP SENDHOREP

VLR

MSC

Invoker MSC

Performer VLR

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 2.3.1.7 IEMI Managment Services Service MAP CKIEMI MAP GETIEMI Invoker VLR MSC or SGSN VLR Performer MSC EIR MSC Invoker VLR Performer 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 MAP PROVIMSI MAP FNEWIMSI 2.3.1.10 Fault Recovery Services Service Invoker Performer Invoker VLR VLR Performer MSC MSC

2011-10-28

13

Chapter 2: The Mobile Application Layer

MAP RESET MAP FCKSSIND MAP RESTORE

HLR HLR VLR

VLR or SGSN VLR HLR

2.3.1.11 Subscriber Information Services Service MAP ANYQRY MAP PROVSUBI MAP ANYSUB MAP ANYMOD MAP SUBSDATAMOD 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 Invoker SCF VLR SCF SCF PNA HLR Performer HLR or GMLC or NPLR SGSN HLR HLR VLR or SGSN SCF

2.3.2.2 Miscellaneous Operation and Maintenance Services Service MAP SENDIMSI 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 MAP-ISTCMD 2.3.4 Supplementary Service Invoker GMSC or SCF HLR VMSC Anchor MSC Relay MSC Anchor MSC Relay MSC HLR VLR HLR VMSC or GMSC HLR Performer HLR or NPLR VLR GMSC Relay MSC Anchor MSC Relay MSC Anchor MSC VLR HLR VLR HLR VMSC or GMSC Invoker VLR Performer MSC

14

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

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 MAP SENDMOSMSI MAP MTFSMS Invoker SMS-GMSC MSC SMS-GMSC MSC VLR or SGSN HLR HLR MSC MSC SMS-GMSC Performer HLR SMS-IWMSC HLR VLR HLR SMS-IWMSC SMS-GMSC VLR VLR MSC or SGSN

2011-10-28

15

Chapter 2: The Mobile Application Layer

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 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 Invoker GGSN GGSN HLR Performer HLR HLR GGSN

2.4 MAP User Entities


2.4.1 Mobile Switching Centre (MSC) Service Sets

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

Table X. MSC performed services. 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

Service

Table X. MSC invoked services. Invoker

Performer

16

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

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

PROCAS CKIEMI ALLOCHN RESUME ISTALERT REGSS ERASESS ACTSS DEACTSS INTERGSS REGPW PROCUSS SSINV REGCC ERASECC MOFSMS RDYSM SENDMTSMSI SENDMOSMSI SUBLOCREP

MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC MSC

VLR EIR VLR GMSC HLR VLR VLR VLR VLR VLR VLR VLR SCF VLR VLR SMS-IWMSC VLR VLR VLR GMLC

Service MAP PREPHO MAP SENDEND MAP PROCAS MAP FAS MAP PREPSH MAP PREPGC MAP PROCGC MAP FGRCSIG MAP SENDGCEND

Table X. MSC peer services. 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

Service MAP UDLOC MAP PURGEMS MAP UDGPRSLOC MAP SENDAUTHI MAP AUTHFAIL MAP RESTORE

Table 1. HLR performed services. Invoker VLR VLR or SGSN SGSN VLR or SGSN VLR or SGSN VLR

Performer HLR HLR HLR HLR HLR HLR

2011-10-28

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

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

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

Table 2. HLR invoked services. 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 MAP ALERTSC MAP INFORMSC MAP MSGPRSPRES Invoker HLR HLR HLR 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 SMS-IWMSC SMS-GMSC GGSN

18

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

2.4.3 Visitor Location Register (VLR) Service Sets Table 3. VLR performed services. 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 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 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

Table 4. VLR invoked services. Service MAP UDLOC MAP SENDID MAP PURGEMS MAP MMEVENT MAP PAGE MAP SEARCH Invoker VLR VLR VLR VLR VLR VLR Performer HLR old VLR HLR SCF MSC MSC

2011-10-28

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

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

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

Service MAP CKIEMI

Table X. EIR performed services. Invoker MSC or SGSN

Performer EIR

2.4.5 Serving GPRS Support Node (SGSN) Service Sets

Service MAP CANCLOC MAP INSSUBSD MAP DELSUBD MAP RESET MAP PROVSUBI MAP ANYMOD

Table X. SGSN performed services. Invoker HLR HLR HLR HLR VLR PNA

Performer SGSN SGSN SGSN SGSN SGSN SGSN

20

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

The Mobile Application Layer

MAP MAP MAP MAP

ACTTM DEACTTM MTFSMS PROVSLOC

HLR HLR SMS-GMSC GMLC

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 Invoker MSC HLR Performer SMS-IWMSC SMS-IWMSC

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

Table X. SMS-GMSC performed services. Service MAP INFORMSC Invoker HLR Performer SMS-GMSC

2011-10-28

21

Chapter 2: The Mobile Application Layer

Service MAP SENDSMSRI MAP SMDELIVSTAT MAP MTFSMS

Table X. SMS-GMSC invoked services. Invoker SMS-GMSC SMS-GMSC SMS-GMSC

Performer HLR HLR MSC or SGSN

2.4.9 Gateway Mobile Location Center (GMLC) Service Sets

Service MAP ANYQRY MAP SUBLOCREP

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

Performer GMLC GMLC

Service MAP SENDLCSRI MAP PROVSLOC

Table X. GMLC invoked services. Invoker GMLC GMLC

Performer HLR VMSC or SGSN

22

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Services Definition

3 MAPI Services Definition


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

3.1 Local Management Services Definition


The services defined in this section are outside the scope of the international standards. These services apply to all applications contexts and specific 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 defines 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 specified 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.  Figure 2. Sequence of Primitives; MAP User Bind Service 

2011-10-28

23

Chapter 3: MAPI Services Definition

3.1.3 MAP User Unbind Service This service allows the MAP user to be unbound from a network address and application context. MAP_UNBIND_REQ: This primitive requests that the MAP user be unbound from the 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. 

3.2 Dialogue Handling Definition


This section describes the required MAP service primitives that define 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 flow. Each 24 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Services Definition

queue represents a flow control function in one direction of transfer. The ability of a user to add objects to a queue will be determined by the behaviour of 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 defined to be able to advance ahead of the preceding object (however, no object is defined to be able to advance ahead of another object of the same type), or if the following object is defined 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 defined to be destructive with respect to all other objects. Table Y shows the ordering relationships among the queue model objects. Table Y. Ordering Relationship Between Queue Model Objects. Object X Object Y Open Components Deilmiter Close Abort AA DES N/A 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 defined to be able to advance ahead of preceding Object Y. Indicates that Object X is defined to be destructive with respect to the preceding Object Y. 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 2011-10-28 25

Chapter 3: MAPI Services Definition

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 specified 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 specified source address. MAP_OPEN_CON: This primitive indicates to the MAP user that a dialogue request has been confirmed on the specified responding address. The sequence of primitives for a successful MAP dialogue establishment is defined 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  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 26 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. Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Services Definition

No

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

3.2.2.1 User Primitives for Component Transfer Service Specific Requests: These primitives request that the MAP provider invoke a service and transfer the specified (and any subsequent) components. Service Specific Responses: These primitives request that the MAP provider return result for a service invocation and transfer the specified (and any subsequent) components. MAP_DELIM_IND: This primitive requests that the MAP provider deliver any accumulated components from previous service specific request or response primitives. 3.2.2.2 Provider Primitives for Component Transfer Service Specific Indications: These primitives indicate to the MAP user an invocation and the indicated (and any subsequent) components. Service Specific Confirmations: 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 specific indication or confirmation 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 defined in the time sequence diagram as shown in Figure 10.  Figure 10. Sequence of Primitives; Successful Confirmation of Receipt.  The sequence of primitives as shown above may remain incomplete if a MAP_UABORT, MAP_PABORT or MAP_CLOSE primitive occurs (see Table 3). A MAP user must not issue a Service Specific Response primitive if no Service Specific Indication primitive for a confirmed service has been received, or if all such Service Specific Indication primitives have been previously confirmed. Following a MAP_UABORT or MAP_PABORT, a MAP user may not issue a Service Specific Response to confirm outstanding Service Specific Indication primitives received before the abort procedure was signalled. Note The witholding of confirmation of a service by a MAP user can have an effect on 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. 

2011-10-28

27

Chapter 3: MAPI Services Definition

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.  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. 28 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI) 

MAPI Services Definition

 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. 

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

2011-10-28

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 defined in 3GPP TS 29.002 and ANSI41-D). Also, it discusses the states in which the primitive is valid, the resulting state and the 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 Information Reporting Bind Unbind Error Success PRIMITIVE MAP_INFO_REQ MAP_INFO_ACK MAP_BIND_REQ MAP_BIND_ACK MAP_UNBIND_REQ MAP_ERROR_ACK MAP_OK_ACK PARAMETERS

Tables 5, 6 and 7 provide a summary of the MAP primitives and their parameters. Table 5. Association Establishment MAP Service Primitives. SERVICE Association PRIMITIVE MAP_OPEN_REQ PARAMETERS (Application context name, Destination address, Destination reference, Originating address, Originating reference, Specific information) (Application context name, Destination address, Destination reference, Originating address, Originating reference, Specific information) (Application context name, Responding address, Result, Refuse-reason, Specific information) (Application context name, Responding address, Result, Refuse-reason, Specific information, Provider-error)

Establishment

MAP_OPEN_IND

MAP_OPEN_RES

MAP_OPEN_CON

Table 6. Component Transfer Service Primitives. SERVICE Service Specific Primitives Delimitation PRIMITIVE MAP_XXX _REQ MAP_XXX _IND MAP_XXX _RES MAP_XXX _CON MAP_DELIM_REQ PARAMETERS (Specific information) (Specific information) (Specific information) (Specific information) (none)

2011-10-28

31

Chapter 4: MAPI Primitives

MAP_DELIM_IND

(none)

SERVICE Association Termination Assocation Abort Abort Notice

Table 7. Association Termination MAP Service Primitives. PRIMITIVE PARAMETERS MAP_CLOSE_REQ (Release method, Specific information) MAP_CLOSE_IND (Specific information) MAP_ABORT_REQ (User reason, Diagnostic information, Specific information) MAP_UABORT_IND (User reason, Diagnostic information, Specific 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 1.1 Rel. 1.20110510

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 effect on the state of the MAP provider and do not appear in the state tables in Appendix B [State/Event Tables], page 393.

2011-10-28

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 Specifies the maximum size (in octets) of Transaction Service User Data supported by the MAP provider. ETSDU size Specifies the maximum size (in octets) of Expedited Transaction Service User Data supported by the MAP provider. CDATA size Specifies 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 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

DDATA size Specifies 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 Specifies the maximum size (in decimal digits) of a network address. ADDR length, ADDR offset Specifies the length in bytes and offset 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 offset QOS range length, QOS range offset OPTIONS flags 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 field specified 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 field specifies additional properties specific 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 specified below. The following flags may be set by the provider: SENDZERO This flag indicates that the MAP provider support the sending of zerolength (component-less) TSDUs. This indicates that the MAP provider conforms to XTI in XPG4 and supports primitives MAP_ADDR_REQ and MAP_ADDR_ACK.

XPG4_1

TODU size PROTOID length, PROTOID offset MAPI version Flags Valid States New State
2

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

2011-10-28

35

Chapter 4: MAPI Primitives

Rules The following rules apply when the type of service is operations class 4: The ETSDU size, CDATA size and DDATA size fields should be -2. The TSDU size should be equal to the TIDU size.

36

Version 1.1 Rel. 1.20110510

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 specified 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 offset The offset from the beiginning of the M_PROTO block where the protocol address begins. The address in the M_PROTO message block is however, aligned the same as it 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 specified 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, offsets and sizes in all structures refer to the number of bytes. This field 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.

2011-10-28

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 TNOADDR TACCES TOUTSTATE TSYSERR TADDRBUSY 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. A system error has occured and the UNIX System error in indicated in the primitive. This indicated that the requested address is already in use.

38

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.1.4 Bind Application Context Acknowledgement MAP BIND ACK This primitive indicates to the MAP user that the specified protoocl address has been bound to the stream, that the specified number of dialogue open indications are allowed to be queued by the MAP provider for th specified protocol address, and that the stream associated with the specified protocol address has ben activated. Format The format of the message is one M_PCPROTO message block. The format of the M_PCPROTO message block is as follows:
typedef struct { long PRIM_type; 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 offset DIAIND number Flags Valid States New State Rules The following rules apply to the binding of the specified protocol address to the stream: If the ADDR length

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occurred and the UNIX system error is indicated in the primitive.

40

Version 1.1 Rel. 1.20110510

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 offset The offset from the beginning of the M_PROTO message block where the options begin. The proper alignment of options is not guaranteed. The options are, however, aligned the same as they were received from the MAP user. MGMT flags The flags which define the request made by the MAP user. Flags T_NEGOTIATE Negotiate and set the options with the MAP provider. T_CHECK T_CURRENT T_DEFAULT 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 2011-10-28 41 Check the validity of the specified options. Return the options currently in effect. Return the default options.

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 TBADOPT TBADFLAG TSYSERR TNOTSUPPORT This MAP provider does not support the requested flag (T_CHECK or T_CURRENT). This indicates that the user did not have proper permissions for the use of the requested options. The primitive would place the MAP interface out of state. This indicates that the options as specified were in an incorrect format, or they contained illegal information. This indicates that the flags as specified were incorrect or illegal. A system error has occured and the UNIX system error is indicated in the primitive.

42

Version 1.1 Rel. 1.20110510

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.

2011-10-28

43

Chapter 4: MAPI Primitives

4.1.8 Get Protocol Address Acknowledgement MAP ADDR ACK Format Parameters Flags Valid States New State

44

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.1.9 Options Management Acknowledgement MAP OPTMGMT ACK Format Parameters Flags Valid States New State

2011-10-28

45

Chapter 4: MAPI Primitives

4.1.10 Error Acknowledgement MAP ERROR ACK Format Parameters Valid Error Codes Valid States New State

46

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.1.11 Successful Receipt Acknowledgement MAP OK ACK Format Parameters Valid States New State

2011-10-28

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 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.2.2 Association Establishment Indication MAP OPEN IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

50

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.2.4 Association Establishment Confirmation MAP OPEN CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

52

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.3.2 Component Delimitation Indication MAP DELIM IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

54

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.4.2 Association Release Indication MAP CLOSE IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

56

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.4.4 Association User Abort Indication MAP UABORT IND Format Parameters Flags Valid States New State

2011-10-28

57

Chapter 4: MAPI Primitives

4.4.5 Association Provider Abort Indication MAP PABORT IND Format Parameters Flags Valid States New State

58

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.4.6 Association Notice Indication MAP NOTICE IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

60

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

62

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

64

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

66

Version 1.1 Rel. 1.20110510

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

2011-10-28

67

Chapter 4: MAPI Primitives

4.6 Service Specific Primitives


4.6.1 Activate Supplementary Service Request MAP ACTSS REQ Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

68

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.2 Activate Supplementary Service Indication MAP ACTSS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

70

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.4 Activate Supplementary Service Confirmation MAP ACTSS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

72

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.6 Activate Traceec Mode Indication MAP ACTTM IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

74

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.8 Activate Traceec Mode Confirmation MAP ACTTM CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

76

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.10 Alert Service Center Indication MAP ALERTSC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

78

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.12 Alert Service Center Confirmation MAP ALERTSC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

80

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.14 Allocate Handover Number Indication MAP ALLOCHN IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

82

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

83

Chapter 4: MAPI Primitives

4.6.17 Any Time Modification Request MAP ANYMOD REQ Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

84

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

85

Chapter 4: MAPI Primitives

4.6.19 Any Time Modification Response MAP ANYMOD RES Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

86

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.20 Any Time Modification Confirmation MAP ANYMOD CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

88

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.22 Any Time Interrogation Indication MAP ANYQRY IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

90

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.24 Any Time Interrogation Confirmation MAP ANYQRY CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

92

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

94

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.28 Any Time Subscription Interrogation Confirmation MAP ANYSUB CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

96

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.30 Authentication Failure Report Indication MAP AUTHFAIL IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

98

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.32 Authentication Failure Report Confirmation MAP AUTHFAIL CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

100

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.34 Authenticate Indication MAP AUTH IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

102

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.36 Authenticate Confirmation MAP AUTH CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

104

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.38 Cancel Location Indication MAP CANCLOC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

106

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.40 Cancel Location Confirmation MAP CANCLOC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

108

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.42 Reset Indication MAP RESET IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

110

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.44 Reset Confirmation MAP RESET RES Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

112

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.46 Restore Indication MAP RESTORE IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

114

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.48 Restore Confirmation MAP RESTORE RES Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

116

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.50 Resume Call Handling Indication MAP RESUME IND Format Parameters Flags Valid States New State

2011-10-28

117

Chapter 4: MAPI Primitives

4.6.51 Resume Call Handling Confirmation MAP RESUME RES Format Parameters Flags Valid States New State

118

Version 1.1 Rel. 1.20110510

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

120

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.54 Search for MS Indication MAP SEARCH IND Format Parameters Flags Valid States New State

2011-10-28

121

Chapter 4: MAPI Primitives

4.6.55 Search for MS Confirmation MAP SEARCH RES Format Parameters Flags Valid States New State

122

Version 1.1 Rel. 1.20110510

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

124

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.58 Check IEMI Indication MAP CKIEMI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

126

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.60 Check IEMI Confirmation MAP CKIEMI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

128

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.62 Deactivate Supplementary Service Indication MAP DEACTSS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

130

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.64 Deactivate Supplementary Service Confirmation MAP DEACTSS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

132

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.66 Deactivate Trace Mode Indication MAP DEACTTM IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

134

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.68 Deactivate Trace Mode Confirmation MAP DEACTTM CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

136

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.70 Delete Subscriber Data Indication MAP DELSUBD IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

138

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.72 Delete Subscriber Data Confirmation MAP DELSUBD CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

140

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.74 Erase CC Entry Indication MAP ERASECC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

142

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.76 Erase CC Entry Confirmation MAP ERASECC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

144

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.78 Erase Supplementatry Service Indication MAP ERASESS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

146

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.80 Erase Supplementatry Service Confirmation MAP ERASESS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

148

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.82 Failure Report Indication MAP FAILURE IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

150

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.84 Failure Report Confirmation MAP FAILURE CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

152

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.86 Forward Access Signalling Indication MAP FAS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

154

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.88 Forward Access Signalling Confirmation MAP FAS CON Format Parameters Flags Valid States New State

2011-10-28

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 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

158

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.92 Forward Check SS Indication Confirmation MAP FCKSSIND CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

160

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

162

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.96 Forward Group Call Signalling Confirmation MAP FGRCSIG CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

164

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.98 Forward New IMSI Indication MAP FNEWIMSI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

166

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.100 Forward New IMSI Confirmation MAP FNEWIMSI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

168

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.102 Obtain IEMI Indication MAP GETIEMI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

170

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.104 Obtain IEMI Confirmation MAP GETIEMI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

172

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.106 Get Password Indication MAP GETPASS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

174

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.108 Get Password Confirmation MAP GETPASS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

176

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.110 Inform Service Center Indication MAP INFORMSC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

178

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.112 Inform Service Center Confirmation MAP INFORMSC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

180

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.114 Insert Subscriber Data Indication MAP INSSUBSD IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

182

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.116 Insert Subscriber Data Confirmation MAP INSSUBSD CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

184

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.118 Iterrogate Supplementary Service Indication MAP INTERGSS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

186

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.120 Iterrogate Supplementary Service Confirmation MAP INTERGSS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

188

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.122 IST Alert Indication MAP ISTALERT IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

190

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.124 IST Alert Confirmation MAP ISTALERT CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

192

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.126 IST Command Indication MAP ISTCMD IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

194

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.128 IST Command Confirmation MAP ISTCMD CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

196

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.130 Note MM Event Indication MAP MMEVENT IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

198

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.132 Note MM Event Confirmation MAP MMEVENT CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

200

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

202

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.136 Mobile Originated Forward Short Message Confirmation MAP MOFSMS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

204

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

206

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.140 Note MS Present for GRPS Confirmation MAP MSGRPSPRES CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

208

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

210

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.144 Mobile Terminated Forward Short Message Confirmation MAP MTFSMS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

212

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.146 Page Indication MAP PAGE IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

214

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.148 Page Confirmation MAP PAGE CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

216

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.150 Prepare Group Call Indication MAP PREPGC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

218

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.152 Prepare Group Call Confirmation MAP PREPGC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

220

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.154 Prepare Handover Indication MAP PREPHO IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

222

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.156 Prepare Handover Confirmation MAP PREPHO CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

224

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.158 Prepare Subsequent Handover Indication MAP PREPSH IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

226

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.160 Prepare Subsequent Handover Confirmation MAP PREPSH CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

228

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.162 Process Access Signalling Indication MAP PROCAS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

230

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.164 Process Access Signalling Confirmation MAP PROCAS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

232

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

234

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.168 Process Group Call Signalling Confirmation MAP PROCGC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

236

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.170 Process Unstructured SS Indication MAP PROCUSS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

238

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.172 Process Unstructured SS Confirmation MAP PROCUSS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

240

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.174 Provide IMSI Indication MAP PROVIMSI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

242

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.176 Provide IMSI Confirmation MAP PROVIMSI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

244

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.178 Provide Roaming Number Indication MAP PROVRN IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

246

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.180 Provide Roaming Number Confirmation MAP PROVRN CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

248

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.182 Provide Subscriber Location Indication MAP PROVSLOC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

250

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.184 Provide Subscriber Location Confirmation MAP PROVSLOC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

252

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.186 Provide Subscriber Information Indication MAP PROVSUBI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

254

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.188 Provide Subscriber Information Confirmation MAP PROVSUBI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

256

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.190 Purge MS Indication MAP PURGEMS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

258

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.192 Purge MS Confirmation MAP PURGEMS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

260

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.194 Ready for SM Indication MAP RDYSM IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

262

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.196 Ready for SM Confirmation MAP RDYSM CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

264

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.198 Register CC Entry Indication MAP REGCC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

266

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.200 Register CC Entry Confirmation MAP REGCC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

268

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.202 Register Password Indication MAP REGPW IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

270

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.204 Register Password Confirmation MAP REGPW CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

272

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.206 Register Supplementary Service Indication MAP REGSS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

274

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.208 Register Supplementary Service Confirmation MAP REGSS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

276

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.210 Remote User Free Indication MAP REMUSRFREE IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

278

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

279

Chapter 4: MAPI Primitives

4.6.213 Send Identification Request MAP SENDID REQ Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

280

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

281

Chapter 4: MAPI Primitives

4.6.215 Send Identification Response MAP SENDID RES Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

282

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.216 Send Identification Confirmation MAP SENDID CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

284

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.218 Set Ciphering Mode Indication MAP SETCM IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

286

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.220 Set Ciphering Mode Confirmation MAP SETCM CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

288

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.222 Set Reporting State Indication MAP SETREP IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

290

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.224 Set Reporting State Confirmation MAP SETREP CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

292

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

294

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.228 Report Short Message Delivery Status Confirmation MAP SMDELIVSTAT CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

296

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.230 Send Authentication Information Indication MAP SENDAUTHI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

298

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.232 Send Authentication Information Confirmation MAP SENDAUTHI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

300

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.234 Send End Signal Indication MAP SENDEND IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

302

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.236 Send End Signal Confirmation MAP SENDEND CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

304

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

306

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.240 Send Group Call End Signal Confirmation MAP SENDGCEND CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

308

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

310

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.244 Send Routing Information for GPRS Confirmation MAP SENDGPRSRI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

312

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.246 Send Handover Report Indication MAP SENDHOREP IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

314

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.248 Send Handover Report Confirmation MAP SENDHOREP CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

316

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.250 Send IMSI Indication MAP SENDIMSI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

318

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.252 Send IMSI Confirmation MAP SENDIMSI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

320

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

322

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.256 Send Routing Information for LCS Confirmation MAP SENDLCSRI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

324

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

326

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.260 Send Mobile Originated SMS Information Confirmation MAP SENDMOSMSI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

328

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

330

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.264 Send Mobile Terminated SMS Information Confirmation MAP SENDMTSMSI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

332

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.266 Send Routing Information Indication MAP SENDRI IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

334

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.268 Send Routing Information Confirmation MAP SENDRI CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

336

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

338

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

339

Chapter 4: MAPI Primitives

4.6.273 SS Invocation Notification Request MAP SSINV REQ Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

340

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

341

Chapter 4: MAPI Primitives

4.6.275 SS Invocation Notification Response MAP SSINV RES Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

342

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.276 SS Invocation Notification Confirmation MAP SSINV CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

344

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.278 Status Report Indication MAP STATUS IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

346

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.280 Status Report Confirmation MAP STATUS CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

348

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.282 Subscriber Location Report Indication MAP SUBLOCREP IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

350

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

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

2011-10-28

351

Chapter 4: MAPI Primitives

4.6.285 Note Subscriber Data Modified Request MAP SUBSDATAMOD REQ Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

352

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.286 Note Subscriber Data Modified Indication MAP SUBSDATAMOD IND Format Parameters Flags Valid States New State

2011-10-28

353

Chapter 4: MAPI Primitives

4.6.287 Note Subscriber Data Modified Response MAP SUBSDATAMOD RES Format Parameters Flags Valid States New State Acknowledgements This primitive requires the MAP provider to generate one of the following 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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

354

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.288 Note Subscriber Data Modified Confirmation MAP SUBSDATAMOD CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

356

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.290 Trace Subscriber Activity Indication MAP TRACESA IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

358

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.292 Trace Subscriber Activity Confirmation MAP TRACESA CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

360

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.294 Update GPRS Location Indication MAP UDGRPSLOC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

362

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.296 Update GPRS Location Confirmation MAP UDGRPSLOC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

364

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.298 Update Location Indication MAP UDLOC IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

366

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.300 Update Location Confirmation MAP UDLOC CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

368

Version 1.1 Rel. 1.20110510

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

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

370

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.304 Unstructured Supplementary Service Notify Confirmation MAP USSDNTFY CON Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

372

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.306 Unstructured Supplementary Service Indication MAP USSDREQ IND Format Parameters Flags Valid States New State

2011-10-28

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 TSYSERR The primitive would place the MAP interface out of state. A system error has occured and the UNIX System error in indicated in the primitive.

374

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

MAPI Primitives

4.6.308 Unstructured Supplementary Service Confirmation MAP USSDREQ CON Format Parameters Flags Valid States New State

2011-10-28

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 specification. 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 files associated with the stream, and then reopening them for processing.

2011-10-28

377

Mobile Application Part Interface (MAPI)

References

6 References
1. CCITT X.213, (Geneva, 1986), Network Service Definition for Open Systems Interconnection (OSI) for CCITT Applications, (Grey Book). 2. ISO 8348 Information Processing Systems Data Communications Newtork Service Definition, 4/15/87 3. ISO 8348/AD Information Processing Systems Data Communications Newtork Service Definition 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 Definition, Issue 2 Volume 3 8. CCITT X.210, (Geneva 1984), Open Systems Interconnection (OSI) Layer Service Definition Conventions, (Red Book)

2011-10-28

379

Mobile Application Part Interface (MAPI)

Addendum for 3GPP Conformance

Addendum for 3GPP Conformance

2011-10-28

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 definition 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

2011-10-28

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 1.1 Rel. 1.20110510

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

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

2011-10-28

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 1.1 Rel. 1.20110510

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

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

2011-10-28

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 1.1 Rel. 1.20110510

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

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

2011-10-28

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 sendIdentification prepareHandover, forwareAccessSignalling, sendEndSignal, processAccessSignalling, prepareSubsequentHandover readyForSM purgeMS alertServiceCentre reset processUnstructuredSS-Request, unstructuredSS-Request, unstructuredSS-Notify activateTraceMode, deactivateTraceMode

v3 v3 v2 v2 v2

mwdMngtContext msPurgingContext shortMsgAlertContext resetContext networkUnstructuredSsContext

v3

tracingContext

390

Version 1.1 Rel. 1.20110510

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-InvocationNotificationContext 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, anyTimeModification ss-InvocationNotification prepareGroupCall, processGroupCallSignalling, forwardGroupCallSignalling, sendGroupCallEndSignal setReportingState, statusReport, remoteUserFree registerCC-Entry, eraceCC-Entry isAlert istCommand

2011-10-28

391

Appendix A: Mapping MAPI Primitives to 3GPP TS 29.002

v3 v3 v3 v3 v3 v3

locationSvcEnquiryContext locationSvcGatewayContext mm-EventReportingContext subscriberDataModificationNotificationContext authenticationFailureReportContext secureTransportHandlingContext

provideSubscriberLocation, subscriberLocationReport sendRoutingInfoForLCS noteMM-Event noteSubscriberDataModified authenticationFailureReport secureTransportClass1, secureTransportClass2, secureTransportClass3, secureTransportClass4

392

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

State/Event Tables

Appendix B State/Event Tables

2011-10-28

393

Mobile Application Part Interface (MAPI)

Primitive Precedence Tables

Appendix C Primitive Precedence Tables

2011-10-28

395

Mobile Application Part Interface (MAPI)

MAPI Header File Listing

Appendix D MAPI Header File Listing

2011-10-28

397

Mobile Application Part Interface (MAPI)

Licenses

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

GNU Affero General Public License

The GNU Affero General Public License. Version 3, 19 November 2007 Copyright c 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a programto make sure it remains free software for all its users. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. A secondary benefit of defending all users freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. 2011-10-28 399

Licenses

texi/agpl3.texi

An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. The precise terms and conditions for copying, distribution and modification follow.

Terms and Conditions


0. Definitions. This License refers to version 3 of the GNU Affero General Public License. Copyright also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. The Program refers to any copyrightable work licensed under this License. Each licensee is addressed as you. Licensees and recipients may be individuals or organizations. To modify a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a modified version of the earlier work or a work based on the earlier work. A covered work means either the unmodified Program or a work based on the Program. To propagate a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To convey a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays Appropriate Legal Notices to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The source code for a work means the preferred form of the work for making modifications to it. Object code means any non-source form of a work. A Standard Interface means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The System Libraries of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A Major Component, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system 400 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

(if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The Corresponding Source for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the works System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the works users, your or third parties legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Programs source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms 2011-10-28 401

Licenses

texi/agpl3.texi

added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a. The work must carry prominent notices stating that you modified it, and giving a relevant date. b. The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to keep intact all notices. c. You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d. If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an aggregate if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilations users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. 402 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

c. Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A User Product is either (1) a consumer product, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, normally used refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. Installation Information for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the 2011-10-28 403

Licenses

texi/agpl3.texi

operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. Additional permissions are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b. Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or e. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f. Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered further restrictions within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. 404 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An entity transaction is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the partys predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for 2011-10-28 405

Licenses

texi/agpl3.texi

exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A contributor is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributors contributor version. A contributors essential patent claims are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, control includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributors essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a patent license is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To grant such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. Knowingly relying means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipients use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is discriminatory if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies 406 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Remote Network Interaction; Use with the GNU General Public License. Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License or any later version applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxys public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 2011-10-28 407

Licenses

texi/agpl3.texi

15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS

408

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the copyright line and a pointer to where the full notice is found.
one line to give the programs name and a brief idea of what it does. Copyright (C) year name of author This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Also add information on how to contact you by electronic and paper mail. If your software can interact with users remotely through a network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a Source link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. You should also get your employer (if you work as a programmer) or school, if any, to sign a copyright disclaimer for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see http://www.gnu.org/licenses/.

2011-10-28

409

Licenses

texi/fdl13.texi

GNU Free Documentation License

GNU FREE DOCUMENTATION LICENSE Version 1.3, 3 November 2008 Copyright c 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document free in the sense of freedom: to assure everyone the effective 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 modifications 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. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The Document, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as you. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A Modified Version of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A Secondary Section is a named appendix or a front-matter section of the Document 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. (Thus, if the Document is in part a 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 410 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. 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 Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A Transparent copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document 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 file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not Transparent is called Opaque. Examples of suitable formats for Transparent copies include plain ascii without markup, Texinfo input format, LaTEX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include 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 machinegenerated HTML, PostScript or PDF 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. The publisher means any person or entity that distributes copies of the Document to the public. A section Entitled XYZ means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as Acknowledgements, Dedications, Endorsements, or History.) To Preserve the Title of such a section when you modify the Document means that it remains a section Entitled XYZ according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. 2. VERBATIM COPYING 2011-10-28 411

Licenses

texi/fdl13.texi

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. 3. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) 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 fit legibly, you should put the first ones listed (as many as fit 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 computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. 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 Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History 412 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

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 modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified 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, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified 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 Modified 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. For any section Entitled Acknowledgements or Dedications, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements 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 Modified Version. N. Do not retitle any existing section to be Entitled Endorsements or to conflict in title with any Invariant Section. O. Preserve any Warranty Disclaimers. If the Modified 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 Modified Versions license notice. These titles must be distinct from any other section titles. 2011-10-28 413

Licenses

texi/fdl13.texi

You may add a section Entitled Endorsements, provided it contains nothing but endorsements of your Modified Version by various partiesfor example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be 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 Modified Version. 5. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. 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 different 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 Acknowledgements, 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, is called an aggregate if the copyright resulting from the compilation is not used to limit the legal rights of the compilations users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. 414 Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Documents Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. 8. TRANSLATION Translation is considered a kind of modification, 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, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. If a section in the Document is Entitled Acknowledgements, Dedications, or History, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License. However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it. 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. Each version of the License is given a distinguishing version number. If the Document specifies 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 specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If 2011-10-28 415

Licenses

texi/fdl13.texi

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. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxys public statement of acceptance of a version permanently authorizes you to choose that version for the Document. 11. RELICENSING Massive Multiauthor Collaboration Site (or MMC Site) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A Massive Multiauthor Collaboration (or MMC) contained in the site means any set of copyrightable works thus published on the MMC site. CC-BY-SA means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization. Incorporate means to publish or republish a Document, in whole or in part, as part of another Document. An MMC is eligible for relicensing if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008. The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.

416

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Licenses

ADDENDUM: How to use this License for your documents


To use this License in a document you have written, include a copy of the License in the 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.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the with. . . Texts. line with this:
with the Invariant Sections being list their titles , with the Front-Cover Texts being list , and with the Back-Cover Texts being list .

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. 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.

2011-10-28

417

Mobile Application Part Interface (MAPI)

Index

Index
A
ADDR_length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39 ADDR_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37, 39 MAP_AUTH_RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 MAP_AUTHFAIL_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 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

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

L
license, license, license, license, AGPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GNU Affero General Public License . . . GNU Free Documentation License . . . . 399 410 399 410

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

2011-10-28

419

Index

MAP_FCKSSIND_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 MAP_FCKSSIND_RES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 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

420

Version 1.1 Rel. 1.20110510

Mobile Application Part Interface (MAPI)

Index

MAP_PURGEMS_CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP_PURGEMS_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . .

259 257 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

MAP_SENDHOREP_CON . . . . . . . . . . . . . . . . . . . . . . . . . . 315 MAP_SENDHOREP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 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

2011-10-28

421

Index

MAP_STC3_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 MAP_STC3_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 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

422

Version 1.1 Rel. 1.20110510