MATF

MAP Application Terminating Function

Core Network
Introduced in Rel-4
A core network function in legacy GSM/UMTS networks that terminates the Mobile Application Part (MAP) protocol. It handles signaling for mobility management and subscriber services, acting as a gateway or endpoint for MAP-based communication between network elements like HLRs and VLRs.

Description

The MAP Application Terminating Function (MATF) is a critical signaling component within the Core Network (CN) of legacy 2G GSM and 3G UMTS systems. It operates as a functional entity that terminates the Mobile Application Part (MAP) protocol, which is the primary signaling protocol used for communication between core network nodes such as the Home Location Register (HLR), Visitor Location Register (VLR), Mobile Switching Center (MSC), and Gateway MSC (GMSC). The MATF is responsible for processing, interpreting, and responding to MAP messages, ensuring the correct execution of procedures related to mobility management, call handling, and supplementary services.

Architecturally, the MATF is not a standalone physical node but a logical function that can be implemented within various network elements. For instance, an MSC contains a MATF to handle MAP dialogues with the HLR for tasks like updating the subscriber's location or retrieving routing information for mobile-terminated calls. Similarly, a VLR incorporates a MATF to communicate with the HLR for subscriber data management. The function encapsulates the application-layer logic for MAP, managing transaction identifiers, handling errors, and ensuring the reliable exchange of information over the underlying Signaling System No. 7 (SS7) transport layers.

Its role is fundamental to the circuit-switched domain, facilitating key operations like location updating, handover, subscriber authentication, and short message service (SMS) delivery. By providing a standardized termination point for MAP signaling, the MATF enables interoperability between network elements from different vendors, which was a cornerstone for the global success of GSM and UMTS. As networks evolved towards the All-IP architecture of 4G LTE and 5G, the significance of MATF diminished with the phasing out of circuit-switched core and the replacement of MAP with the Diameter-based S6a/S6d interfaces and later the HTTP/2-based service-based interfaces.

Purpose & Motivation

The MATF was created to provide a standardized, reliable endpoint for the MAP signaling protocol, which was essential for automating mobility management and subscriber service provisioning in 2G and 3G networks. Before its formalization, the need for seamless communication between disparate network registers (like HLR and VLR) to track mobile subscribers and route calls motivated the development of a robust application-layer protocol. The MATF solved the problem of interoperability by defining a clear functional boundary where MAP dialogues could be initiated, maintained, and terminated, ensuring that critical procedures such as location updates and call setup could occur reliably across multi-vendor network deployments.

Historically, the introduction of MAP and its terminating functions marked a significant evolution from earlier, more manual or proprietary mobile network architectures. It addressed the limitations of previous approaches that lacked a unified, international standard for non-call-related signaling between network databases. By encapsulating this complexity, the MATF allowed network equipment manufacturers and operators to develop and deploy scalable, automated systems that could support the rapid growth of mobile subscribers and the introduction of advanced services like roaming and SMS, which were heavily dependent on real-time database queries and updates.

Key Features

  • Terminates the Mobile Application Part (MAP) signaling protocol
  • Enables mobility management procedures like location updating and handover
  • Facilitates subscriber data retrieval and management between HLR and VLR
  • Supports call routing and delivery for mobile-terminated calls
  • Handles supplementary service activation and interrogation
  • Provides a standardized interface for interoperability between core network nodes

Evolution Across Releases

Rel-4 Initial

Introduced as a defined functional entity within the 3GPP specifications, formalizing its role in the UMTS Core Network architecture. It was specified to terminate MAP signaling for both circuit-switched and packet-switched domains in the initial 3GPP Release 99/4 network model, supporting procedures between MSC/VLR, SGSN, and HLR.

Defining Specifications

SpecificationTitle
TS 23.066 3GPP TS 23.066