Description
The Mobile Application Protocol (MAP) is a critical signaling protocol within the Core Network (CN) of GSM, UMTS, and early LTE systems, operating over the SS7 (Signaling System No. 7) and later SIGTRAN (Signaling Transport) protocol stacks. It facilitates communication between various network nodes in the circuit-switched (CS) and packet-switched (PS) domains, primarily for mobility management, subscriber data handling, and service provisioning. MAP is an application-layer protocol that uses the Transaction Capabilities Application Part (TCAP) for its transport, enabling structured dialogues between network entities. Its operations are defined through a set of MAP services and associated Application Service Elements (ASEs), which are invoked using specific MAP operations and parameters carried within TCAP components.
Architecturally, MAP interfaces are defined between key network elements. The most significant is the MAP-D interface between the Home Location Register (HLR) and the Visitor Location Register (VLR), which handles location updates, subscriber data retrieval, and authentication. The MAP-C interface connects the HLR to the Mobile Switching Center (MSC) for routing information during mobile-terminated calls. The MAP-G interface between VLRs supports inter-VLR location updates when a subscriber roams between different VLR areas. In the packet-switched domain, the MAP-Gr interface between the HLR and the Serving GPRS Support Node (SGSN) manages GPRS subscriber data and location information. MAP messages carry critical information such as the International Mobile Subscriber Identity (IMSI), Mobile Station Integrated Services Digital Network Number (MSISDN), and various subscriber service profiles.
MAP's role is central to enabling core network functions. For mobility management, it supports procedures like location updating, which informs the HLR of a subscriber's current serving VLR or SGSN, and handover, where it may be involved in transferring subscriber context. For subscriber data management, it allows the VLR or SGSN to fetch authentication triplets and subscriber service profiles from the HLR. For supplementary services, it supports the activation, deactivation, and interrogation of services like call forwarding and barring. The protocol's design is stateful and transaction-oriented, ensuring reliable exchange of information critical for network operation and subscriber experience. While largely superseded by Diameter-based protocols in the 4G EPC and 5G Core for native functions, MAP remains vital for interworking with legacy 2G/3G networks and for certain services.
Purpose & Motivation
MAP was created to provide a standardized, robust signaling mechanism for mobility and service management in digital cellular networks, starting with GSM. Prior to its introduction, cellular systems lacked a unified, interoperable protocol for communication between different vendors' network elements, hindering large-scale deployment and roaming. MAP solved this by defining a comprehensive set of operations for critical functions like tracking subscriber location, authenticating users, and managing call routing, which are essential for enabling automatic roaming and nationwide (and later international) cellular service.
The protocol addressed the fundamental need for a network to maintain a coherent view of a mobile subscriber's state and location as they move. It allowed the home network's HLR to be the central repository of subscriber data, while visited network elements (VLR, MSC) could temporarily cache necessary information to serve the subscriber. This separation of home and visited network responsibilities was key for enabling roaming agreements between operators. MAP also provided the framework for introducing advanced supplementary services (like call waiting, forwarding) in a standardized way across different network implementations.
As networks evolved from GSM to UMTS and early LTE, MAP's purpose expanded to support packet-switched services through interfaces to GPRS network nodes. It became the glue connecting the circuit-switched and packet-switched cores, allowing for coordinated mobility and service management. However, its reliance on the SS7 stack presented limitations in an IP-centric world, leading to its eventual phase-out in favor of Diameter in the Evolved Packet Core (EPC). Nonetheless, MAP's design principles for subscriber mobility and data management profoundly influenced later protocols.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the Mobile Application Protocol (MAP) function was updated with a reference to the HTTP/1.1 protocol. This change aligns the application protocol procedures with current web standards. The update ensures the defined set of procedures for the application interface utilizes the modern HTTP/1.1 specification.
- Reference update for HTTP/1.1 protocol TS 24.259CR0055
In Release 18, enhancements to the Mobile Application Protocol (MAP) function focused on improvements for Data Channel (DC) applications. Specifically, the updates introduced new procedures for binding DC application information and managing application lists based on UE DC capabilities. The release also provided clarifications and updates to the bootstrap, application data channel setup, and DC QoS handling procedures.
- Binding information of DC Application with DC - 23.228 TS 23.228CR1266
- Provide application list based on UE DC capabilities TS 23.228CR1294
- Update of Bootstrap and application data channel setup procedures TS 23.228CR1301
- Clarification on DC QoS Handling in Application Data Channel Setup Procedures TS 23.228CR1391
In Release 19, the MAP function was enhanced to support multiplexing multiple Data Connection (DC) applications over a single SCTP transport connection, improving transport efficiency. The release also introduced updates and corrections to related signalling procedures, including the Application Data Channel Interworking via the Mediation Function (MF), and clarified the roles of the DC Application Server and Proxy. Furthermore, it added provisions for correlating an application's dedicated Data Connection with its bootstrap Data Connection.
- Support of multiplexing multiple DC applications over single SCTP connection TS 23.228CR1511
- Updates to support multiplexing multiple DC applications over single SCTP connection TS 23.228CR1552
- Service updates to support multiplexing multiple DC applications over single SCTP connection TS 23.228CR1586
- Corrections to Signalling Procedure of Application Data Channel Interworking via MF TS 23.228CR1659
- Add DC Application Server Description TS 23.228CR1682
- Correction on the usage of DC Application Proxy TS 23.228CR1686
+ 1 more changes
Explore further
Broader topics and technologies where MAP plays a role.
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 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 21.978 v1300 | CAMEL Control of VoIP Services Feasibility Study | Rel-4 |
| TS 22.121 v1400 | Virtual Home Environment Requirements | Rel-5 |
| TS 23.127 v1600 | Virtual Home Environment Stage 2 Specification | Rel-6 |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 |
| TS 23.171 v1300 | LCS Stage 2 Specification for UMTS | Rel-4 |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 23.806 v1700 | Voice Call Continuity between CS and IMS | Rel-7 |
| TR 23.910 v1400 | UMTS Circuit Switched Bearer Services Overview | Rel-5 |
| TS 24.206 v1700 | Voice Call Continuity Between CS and IMS | Rel-7 |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 |
| TS 26.565 vj00 | Split Rendering Media Service Enabler | Rel-19 |
| TS 29.013 vj00 | MAP-SSAP Interworking for CCBS Service | Rel-19 |
| TS 29.198 v1900 | OSA API Overview Specification | Rel-9 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 |
| TS 33.204 vj00 | TCAP Security (TCAPsec) Stage 2 Specification | Rel-19 |
| TR 38.812 vg00 | Study on NOMA for NR | Rel-16 |