ADMF

Administration Function

Security →
Introduced in Rel-8

ADMF is the central administrative interface in the 3GPP Lawful Interception architecture where authorized law enforcement agencies manage interception requests to ensure proper authorization and control.

Category
Security
Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
5 specs
ADMF Description Purpose Detected Changes Specifications

Description

The Administration Function (ADMF) is a standardized, secure network element defined within the 3GPP Lawful Interception (LI) framework. It acts as the sole, centralized point of contact for Law Enforcement Agencies (LEAs) to interface with the telecommunications network for interception purposes. The ADMF is responsible for receiving, validating, and securely forwarding lawful interception warrants or orders from the LEA to the relevant network elements that perform the actual interception, such as the Intercepting Control Element (ICE) in the core network or the Intercepting Access Point (IAP) in the access network. Its primary role is administrative control and command distribution, ensuring that interception commands are only executed upon proper legal authorization.

Architecturally, the ADMF resides in the Lawful Interception Domain, which is logically and often physically separated from the Public Network Domain where user traffic flows. It communicates with the LEA via the Handover Interface (HI), specifically the HI1 interface, which is used for the exchange of interception-related administrative information (e.g., warrant details, target identities). Internally, the ADMF communicates with the network's interception points (e.g., ICEs) via the Internal Network Interface (INI), specifically the X1 interface. This separation of interfaces (HI for external LEA communication and X1/INI for internal network communication) is a fundamental security principle, preventing the LEA from having direct access to network equipment.

The ADMF's operation involves several key processes. Upon receiving an interception request via HI1, it authenticates the LEA and validates the legal authorization. It then translates the high-level warrant (containing target identifiers like MSISDN or IMSI) into specific, technical interception commands tailored for the relevant network nodes (e.g., a Serving GPRS Support Node (SGSN) or Mobility Management Entity (MME)). These commands, sent via the X1 interface, instruct the ICE to begin intercepting the specified target's communication content (CC) and intercept-related information (IRI). The ADMF also manages the lifecycle of the interception, handling modifications, renewals, and deactivations, and it may provide status reports back to the LEA.

A critical aspect of the ADMF is its role in maintaining mediation and isolation. It mediates between the legal/administrative world of the LEA and the technical world of the network, ensuring commands are properly formatted and targeted. It also isolates the LEA from the network's internal topology and configuration, providing a layer of abstraction for security and simplicity. The ADMF does not handle the intercepted data itself; that is delivered separately by the ICE/IAP to the LEA via the HI2 (for IRI) and HI3 (for CC) interfaces. This architecture ensures a clear separation of duties: administration (ADMF), interception (ICE/IAP), and delivery (Mediation Function for HI2/HI3).

Purpose & Motivation

The ADMF was created to address the critical need for a standardized, secure, and legally compliant method for Lawful Interception (LI) within 3GPP mobile networks. Prior to standardization, interception capabilities were often vendor-specific, non-interoperable, and lacked a clear separation between law enforcement access and network operations, posing risks to network integrity and user privacy. The proliferation of digital mobile communications necessitated a framework that could be uniformly implemented across different network operators and equipment vendors worldwide, ensuring that law enforcement agencies could effectively execute legally mandated interceptions regardless of the underlying network technology.

The primary problem the ADMF solves is the secure and controlled administration of interception warrants. Without a centralized administrative function, LEAs might need to interact directly with various network elements, which is insecure, inefficient, and could expose sensitive network infrastructure. The ADMF provides a single, controlled gateway. It ensures that every interception action is preceded by a validated legal process, preventing unauthorized surveillance. This is crucial for maintaining the rule of law, protecting subscriber privacy, and building trust in digital communications systems.

Furthermore, the ADMF enables scalability and manageability. As networks evolved from 2G/GSM to 3G/UMTS and beyond, the complexity of network architecture increased. The ADMF, introduced in 3GPP Release 8 as part of a refined LI architecture, provided a future-proof model. It abstracts the network complexity from the LEA, allowing new network functions (like the MME in LTE or the AMF in 5G) to be integrated into the LI system simply by having the ADMF communicate with their corresponding ICE. This design addressed the limitations of earlier, more ad-hoc approaches by establishing a clear, modular, and standards-based interface for lawful interception administration.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-16.

Rel-16 3 changes

In Release 16, the ADMF function was enhanced with more descriptive details, explicit functional requirements for logging at the ADMF, and expanded capabilities for LI function targeting, including provisioning target identities to network functions like the LMISF and the independent provisioning of P-CSCFs and S-CSCFs.

  • ADMF descriptive details TS 33.127CR0060
  • ADMF LI Function Targeting TS 33.127CR0094
  • Missing functional requirements on logging at ADMF TS 33.127CR0092

Explore further

Broader topics and technologies where ADMF plays a role.

Defining Specifications

3GPP specifications that define or reference ADMF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.126 vj30 Lawful Interception Requirements Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.128 vj50 3GPP TS 33.128: Lawful Interception Protocols Rel-19
TS 43.033 vd00 Lawful Interception Stage 2 for GSM/GPRS Rel-13