MAP

Mobile Application Protocol

Protocol →
Introduced in R99 Also in: Core Network

MAP is a core network signaling protocol used for communication between elements like HLRs and MSCs to enable subscriber data management, mobility services, and supplementary services in GSM, UMTS, and early LTE networks.

Category
Protocol
Introduced
R99
Where
Services › Codecs
Also touches
1 segments
Specifications
28 specs
MAP Description Purpose Related Classification Specifications

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

Part ofSS7
Related approachesHLRVLRIMS

Release Timeline

Evolution Across Releases

R99 Initial

Introduced as the core signaling protocol for GSM networks, defining interfaces like MAP-D (HLR-VLR) and MAP-C (HLR-MSC) for circuit-switched mobility management and basic supplementary services. It operated over the SS7 protocol stack and established the foundational operations for location updating, handover, and subscriber data retrieval.

Enhanced MAP to support the UMTS core network architecture, including the separation of the MSC into MSC Server and Media Gateway (MGW). Introduced MAP interfaces for the IP Multimedia Subsystem (IMS) early considerations and improved support for CAMEL (Customized Applications for Mobile Network Enhanced Logic) for intelligent network services.

Further evolved to integrate with the initial IMS architecture, defining MAP interactions for user authentication and service provisioning. Supported the transition towards all-IP networks by allowing MAP to operate over SIGTRAN (e.g., M3UA, SUA) in addition to traditional SS7, facilitating transport over IP networks.

Added support for interworking with the Evolved Packet Core (EPC) in LTE, particularly for CS Fallback (CSFB) scenarios. Defined MAP procedures to allow the MME to retrieve CS domain information from the HLR via the SGs interface, enabling voice services in early LTE deployments without IMS-based VoLTE.

Introduced enhancements for Machine-Type Communication (MTC) and IoT, including optimizations for low-complexity devices. Supported features like extended wait time for devices in enhanced coverage, requiring updates to MAP procedures for subscriber data handling between HLR and MME/SGSN.

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.

SpecificationTitleRelease
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
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.