Description
The Mobile Application Part (MAP) is a transaction-oriented, TCAP-based application protocol within the SS7/C7 signaling suite, fundamental to the operation of 2G (GSM) and 3G (UMTS) circuit-switched and packet-switched core networks. It operates over the Signaling Connection Control Part (SCCP) and Transaction Capabilities Application Part (TCAP), providing a standardized language for network nodes to exchange information related to subscriber mobility and services. MAP defines a set of operations and parameters that enable various network entities to communicate. Key dialogues include location updating (between MSC/VLR and HLR), subscriber information retrieval during call setup (e.g., sending routing information from GMSC to HLR), and the management of supplementary services like call forwarding. The protocol is inherently stateful for the duration of a transaction, ensuring reliable execution of complex sequences like handovers between MSCs (using MAP-PREPARE-HANDOVER and MAP-SEND-END-SIGNAL operations). Its architecture is centered on key functional entities: the Home Location Register (HLR) as the central subscriber database, the Visitor Location Register (VLR) managing subscribers in a specific area, the Mobile Switching Center (MSC) handling call control, and the Gateway MSC (GMSC) interfacing with other networks. MAP's role extends into the GPRS core network via the SGSN, which uses MAP to communicate with the HLR for authentication and mobility updates. The protocol uses a rich set of error codes and result types, making it robust for handling various network and subscriber conditions.
Purpose & Motivation
MAP was developed to provide a standardized, robust signaling mechanism for mobility and service management in digital cellular networks, specifically GSM and its evolutionary paths. Before its adoption, proprietary signaling would have hindered interoperability between equipment from different vendors and between different network operators, limiting roaming and service portability. MAP solves the critical problem of enabling a mobile subscriber to move seamlessly across network coverage areas (managed by different MSCs/VLRs) while allowing the network to locate and deliver calls and messages to that subscriber. It handles essential functions like authenticating the subscriber, updating the network with the subscriber's current location, retrieving routing information for incoming calls, and managing value-added services. Its creation was motivated by the need for an open, extensible protocol that could support the complex, distributed nature of mobile networks, separating the call control signaling (ISUP) from the mobility and service control signaling (MAP). This separation of concerns allowed for more flexible network architectures and the introduction of new services without impacting the basic call setup protocol. MAP addressed the limitations of earlier, less structured approaches by providing a comprehensive set of defined operations, making network elements from different manufacturers interoperable and forming the backbone of global mobile roaming.
What changed in its specifications
The latest release-to-release comparison of specifications that define MAP. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-5 added IMS provisioning with new network element definitions (HSS, IMS, ISC, MRF). It also added OSA enhancements covering HE-VASP support, policy management, presence, and removing User Profile Management.
Full comparison in TS 23.127 →Technology family
Core signalling protocols · Core Network
- Phase 1 MAP
- Phase 2 ISUP
- R96 CAP
- R99 GTP-C, GTP-U, GTPv1-C
- Rel-4 BICC
- Rel-5 Diameter, SIP
- Rel-8 GTPv2-C
- Rel-14 PFCP
- Rel-15 HTTP/2 SBI
Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN
- MAP counterpart in another generation: Diameter
“an Interworking Function (IWF) may be used to convert Diameter S6a messages to MAP Gr messages and vice versa” TS 29.002
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 15 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Introduced in Phase 1 (release dating of the term; no individual change cited).
MAP in Release 99 gains new specified behaviour: SCCP version support, TC service mapping corrections, location services impacts, UMTS security on the B interface, and a new user error in Prepare Handover.
MAP gained new Rel-4 capabilities: secure transport of MAP messages with fallback to unsecured transport, LCS operations towards the GMLC, and revised handling of unknown operations in the protocol machine.
- “If secure transport is required and fallback to unsecured transport is acceptable, the dialogue machine retries the dialogue with unsecured transport.” TS 29.002 v4.18.0
- Changes to MAP for secure transport of MAP messages TS 29.002CR148
- “Unknown operations (i.e. a standard operation introduced in a later version of the MAP specification, or a private operation) can be introduced into MAP in a backwards compatible way.” TS 29.002 v4.18.0
MAP gained new Rel-5 content: Iu codec parameters and RAB Assign Modify signalling over MAP Forward/Process Access Signalling and Prepare Handover, plus service handover parameters in MAP Handover messages.
- “The MSC-A server shall include an Iu-Supported Codecs List and an Iu-Currently Used Codec in the MAP Prepare Handover request.” TS 23.153 v5.12.0
- “MSC-A' shall include in the MAP Prepare Handover response the Iu-Selected codec and the Iu-Available Codecs List” TS 23.153 v5.12.0
- Addition of Service Handover parameters to MAP Handover messages TS 29.002CR446
MAP gained a new MAP_RELEASE_RESOURCES service, supported at the VMSC and indicated in the Provide Roaming Number confirm, and the obsolete SIWFS services were removed; further CRs added MAP parameters.
- “10.15 MAP_RELEASE_RESOURCES service” TS 29.002 v6.17.0
- “This parameter indicates by its presence that the MAP_RELEASE_RESOURCES service is supported at the VMSC.” TS 29.002 v6.17.0
- Addition of LCS capability sets to MAP_SRI_for_LCS response TS 29.002CR608
MAP in TS 29.002 gained new content: authentication domains in MAP Send Authentication Info, a new MAP_SEND_GROUP_CALL_INFO service, and extra roaming restriction reason qualifications.
- “Addition of Authentication Domains in MAP Send Authentication Info” TS 29.002 v7.15.0
- “The MAP_SEND_GROUP_CALL_INFO service is a confirmed service using the service primitives given in table 10.7A/1.” TS 29.002 v7.15.0
- Accuracy Fulfillment Indicator parameter to MAP SLR for deferred MT-LR TS 29.002CR0834
In Rel-8 MAP was extended for EPS: an IWF converts between Diameter S6a/S13 and MAP Gr/Gf, MAP services are reused between HSS, IWF and EIR, and eMLPP priority was added to MAP SRI/PRN/PSI.
- “an Interworking Function (IWF) may be used to convert Diameter S6a messages to MAP Gr messages and vice versa” TS 29.002 v8.22.0
- “MAP services that are defined for use between HLR and SGSN are also used in an Evolved Packet System (EPS)” TS 29.002 v8.22.0
- eMLPP Priority in MAP SRI, PRN and PSI request TS 29.002CR0891
MAP gained new Rel-9 behaviour: AoIP codec negotiation parameters in handover signalling, MME Name and SGSN Number sent to the VLR during restoration, and an Initial Attach Indication in MAP_CANCEL_LOCATION.
- “the HLR shall send the MME Name to the VLR during the data restoration procedure if the 'Restoration Indicator' is set in the MAP_RESTORE_DATA request” TS 29.002 v9.13.0
- “then the Prepare Handover Response message shall contain the AoIP-Selected Codec (Target) (MAP) and AoIP-Available Codecs List (MAP).” TS 23.153 v9.3.0
- AoIP – MAP level codec negotiation for GSM codecs TS 29.002CR0928
MAP gained Mobile Terminating Roaming Forwarding procedures and extensions, with new flags in Update Location, Send Identification, Cancel Location and Provide Roaming Number, plus T-ADS retrieval via ATI and UE SRVCC capability in MAP messages.
- “The new terminating VLR shall include an MTRF Supported flag in the MAP Update Location message sent to the HLR.” TS 23.018 v10.4.0
- “The following MAP services are used for the Mobile Terminating Roaming Forwarding procedure:” TS 29.002 v10.11.0
- Retrieval of T-ADS data via MAP ATI TS 29.002CR1016
MAP gained new VCSG location services (MAP_UPDATE_VCSG_LOCATION, MAP_CANCEL_VCSG_LOCATION), MSISDN-less subscription rejection causes, and new parameters such as Initial Attach Indication in MAP_CANCEL_LOCATION.
- “8.1.9 MAP_UPDATE_VCSG_LOCATION service” TS 29.002 v11.12.0
- “The MAP_CANCEL_VCSG_LOCATION service is a confirmed service using the primitives defined in table 8.1/10.” TS 29.002 v11.12.0
- Initial Attach Indication in MAP_CANCEL_LOCATION TS 29.002CR1064
MAP gained new parameters and procedures in Rel-12: a mobile terminating call pending flag in Send Identification response, WLAN offloadability, and MME Name handling in restoration and update location.
- “Mobile Terminating call pending flag in MAP Send Identification response” TS 29.002 v12.9.0
- “WLAN offloadability for MAP” TS 29.002 v12.9.0
- “the old VLR indicated in the MAP Send Identification response that there is a pending mobile terminating call at the old VLR” TS 23.018 v12.2.0
MAP gained new behaviour in Rel-13: MT-SMS messages carry the SMS-GMSC supervision timer value, MSC/SGSN initiate Service Centre Alert for retransmission requests, and positioning data is handled in MAP messages.
- “The SGSN shall initiate the MAP Service Center Alert procedure to alert the SMS-GMSC when the UE, for which one or more MT SMS have been requested” TS 29.002 v13.6.0
- “The message should include the timer value used at the SMS-GMSC for the supervision of the MAP_MT_FORWARD_SHORT_MESSAGE_ACK.” TS 29.002 v13.6.0
- Positioning enhancement impacts on MAP protocol TS 29.002CR1196
MAP_RESET handling changed so VLR and SGSN use Reset-IDs, when supported and present, to identify IMSI records affected by an HLR restart, and T-ADS data retrieval via MAP ATI was added and enhanced.
- “When Reset-IDs are supported and present in the MAP_RESET indication, the VLR uses the Reset-IDs included in the MAP_RESET indication” TS 29.002 v14.5.0
- Retrieval of T-ADS data via MAP ATI TS 29.002CR1219
TS 29.002 gains support for a MAP interface at the 5GS UDM towards the SMS-GMSC/SMS-Router, with the UDM emulating HLR behaviour and using the HLR SSN value.
- “a UDM may support a MAP interface towards the SMS-GMSC/SMS-Router by emulating HLR behaviour” TS 29.002 v17.4.0
- “the UDM (with an integrated/collocated HLR) shall use the HLR SSN value.” TS 29.002 v17.4.0
- Support of MAP messages at the UDM for SMS in 5GS TS 29.002CR1259
Defining Specifications
3GPP specifications that define or reference MAP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 21.978 v300 | CAMEL Control of VoIP Services Feasibility Study | R99 read |
| TS 22.121 v531 | Virtual Home Environment Service Requirements | Rel-5 read |
| TS 23.127 v610 | Virtual Home Environment Stage 2 Specification | Rel-6 read |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 read |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 read |
| TS 23.228 vk10 | IP Multimedia Core Network Subsystem | Rel-20 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 23.806 v700 | Voice Call Continuity between CS and IMS | Rel-7 read |
| TR 23.910 v550 | CS Bearer Services in UMTS | Rel-5 read |
| TS 24.206 v750 | Voice Call Continuity Between CS and IMS | Rel-7 read |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 read |
| TS 26.565 vj00 | Split Rendering Media Service Enabler | Rel-19 read |
| TS 29.013 vj00 | MAP-SSAP Interworking for CCBS Service | Rel-19 read |
| TS 29.198 v340 | OSA R99 API Stage 3 Specification | R99 read |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 read |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 read |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 read |
| TS 33.204 vj00 | TCAP Security (TCAPsec) Stage 2 Specification | Rel-19 read |
| TR 38.812 vg00 | Study on NOMA for NR | Rel-16 read |