LEA

Law Enforcement Agency

Security →
Introduced in Rel-8 Also in: Security

LEA is the authorized government or law enforcement body for which 3GPP defines standardized interfaces and procedures to request and receive lawful interception data from telecommunications operators.

Category
Security
Introduced
Rel-8
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
8 specs
LEA Description Purpose Related Classification Detected Changes Specifications

Description

Within the 3GPP architecture, a Law Enforcement Agency (LEA) is not a network function but an external administrative and legal entity. It is the government-authorized body (e.g., police, intelligence services) that, under a specific legal warrant or order, is permitted to intercept telecommunications traffic and related information. The 3GPP system defines the functional requirements, interfaces, and data formats necessary for a network operator's Lawful Interception (LI) system to deliver intercepted content and intercept-related information (IRI) to one or more LEAs. The LEA itself resides outside the trusted boundary of the 3GPP network.

Architecturally, the interaction with an LEA is mediated through several standardized points. The network operator deploys internal interception functions: the Administration Function (ADMF), which manages interception warrants and LEA identities, and the Delivery Functions (DF2 and DF3). The DF2 delivers Intercept Related Information (IRI—data about the call/communication such as parties, time, location), and the DF3 delivers the Content of Communication (CC—the actual voice, video, or data payload). These Delivery Functions connect to one or more Mediation Functions (MF), which adapt the internal 3GPP formats (e.g., based on 3GPP TS 33.108) into a standardized handover interface format (HI2 for IRI, HI3 for CC) specified for delivery to the LEA. The LEA operates a Collection Function (CF) that receives these HI2 and HI3 flows.

How this works in practice involves a secure and auditable process. When a valid interception warrant is activated in the ADMF, it configures the relevant network nodes (e.g., MSC, SGW, PGW, AMF, SMF) to duplicate the target subscriber's traffic. The internal LI system collects this data, packages it with metadata, and the Mediation/Delivery Functions securely transmit it to the LEA's premises. The 3GPP specifications, such as the 33.1xx series, meticulously define the protocols (e.g., ETSI-standardized handover interfaces), data models, and security requirements (encryption, authentication) for this exchange to ensure integrity, confidentiality, and that only authorized data is delivered. The role of the LEA in the 3GPP context is thus as the defined endpoint for a complex, regulated data delivery pipeline that balances legal obligations with subscriber privacy.

Purpose & Motivation

The formal definition and architectural consideration of the Law Enforcement Agency within 3GPP standards exist to fulfill legal obligations imposed on network operators in most countries. These obligations require operators to have the technical capability to assist law enforcement with authorized interception of communications. Prior to standardization, each country or operator might develop proprietary interfaces, leading to interoperability problems, high costs for equipment vendors, and potential inconsistencies in fulfilling legal orders. The purpose of 3GPP's LI work is to create a unified, technology-agnostic framework that can be implemented globally, ensuring networks are 'interception-ready' by design.

The motivation for its creation, particularly from Rel-8 onwards with increased focus, was the evolution of network technology from circuit-switched voice to packet-based all-IP networks (IMS, LTE). Traditional interception methods tied to circuit switches were becoming obsolete. 3GPP needed to define how to intercept VoIP, messaging, and data sessions in a consistent manner across diverse network architectures (GSM, UMTS, EPS, 5GS). This addressed the limitation of previous ad-hoc approaches and ensured that lawful interception capabilities kept pace with service innovation, preventing communication services from becoming 'dark' to law enforcement.

Furthermore, standardizing the LEA interface provides clear separation of concerns. It defines a strict boundary between the operator's network and the government agency. This protects the operator's internal network details and other subscribers' data while providing the LEA with a predictable, secure feed. It also enables a multi-vendor environment where LEA-side collection equipment from one vendor can interoperate with mediation systems from another, fostering competition and reducing costs for governments. The evolution through releases continually adapts these interfaces to new services like VoLTE, RCS, and 5G network slicing.

Classification

Part ofADMF
Related approachesIRI

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, enhancements for the Law Enforcement Agency (LEA) function included providing more descriptive details for the ADMF and introducing ADMF LI Function Targeting. These changes aimed to improve the administration of interception, such as the activation and delivery of IRI and CC based on a warrant, and addressed missing functional requirements for logging at the ADMF.

  • 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 LEA plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 33.106 vj00 Lawful Interception Requirements (Pre-Rel-15) Rel-19
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification 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 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14
TS 43.033 vd00 Lawful Interception Stage 2 for GSM/GPRS Rel-13