Provides an API for the MAP protocol.


This package provides a machine-generated API for the 3GPP Mobile Application Part (MAP). It is a standalone protocol that does not inherit operations from a parent protocol. However, the API for a later version of an operation extends the API for an earlier version of the same operation.

Protocol compliance

This API and underlying implementation is based on MAP Release 10: 3GPP TS 29.002 V10.0.0 (2010-09). It supports not only the latest version of the application contexts, as defined directly in Release 10, but also the operations and errors of all earlier versions of those application contexts. The following earlier releases have been consulted to determine when each operation, each error, and each parameter thereof was added to the MAP protocol.

  • Release 9: 3GPP TS 29.002 V9.3.0 (2010-09)
  • Release 8: 3GPP TS 29.002 V8.10.0 (2009-06)
  • Release 7: 3GPP TS 29.002 V7.15.0 (2010-06)
  • Release 6: 3GPP TS 29.002 V6.17.0 (2010-06)
  • Release 5: 3GPP TS 29.002 V5.13.0 (2007-09)
  • Release 4: 3GPP TS 29.002 V4.18.0 (2007-09)
  • Release 99: 3GPP TS 29.002 V3.20.0 (2004-06)
  • Release 98: 3GPP TS 09.02 V7.15.0 (2004-03)
  • Release 97: 3GPP TS 09.02 V6.14.0 (2003-09)
  • Release 96: 3GPP TS 09.02 V5.19.0 (2003-09)
  • Phase 2: GSM 09.02 V4.19.1 (2000-12)
  • Phase 1: GSM 09.02 V3.11.0 (1995-04)

API packages and identifier prefix

The MAP API is divided into these subpackages:

  • - contains datatype classes and misc helper classes such as MAPDialog;
  • - contains metadata classes defining application contexts, operations, and errors;
  • - contains the wrapper SLEE event classes used for notifying services of operation invokes and results;
  • - provides conversion between CGIN data objects of this protocol and Google protobuf (GPB) messages.

In general, all top-level classes and interfaces in these packages begin with a common prefix, MAP, so it is safe to use a wildcard package import without colliding with other protocols.

Dialog Extension Interface

This API defines MAPDialog that adds convenience methods for dealing with MAP-specific operations, results, and errors. This interface is implemented only on dialogs that actually use MAP as their network protocol. Like CGIN APIs for other protocols, this interface corresponds directly with the TCAP layer. The MAP-specific dialogue structuring defined in MAP's ASN.1 module MAP-DialogueInformation has nothing specific corresponding to it in this API, though methods dealing with the userInformation field of a TCAP dialogue portion provide access to its representation.