{"id":2154,"date":"2026-06-17T08:00:00","date_gmt":"2026-06-17T07:00:00","guid":{"rendered":"https:\/\/ic-services.io\/?p=2154"},"modified":"2026-10-21T14:11:47","modified_gmt":"2026-10-21T13:11:47","slug":"x1-x2-x3-schnittstellen-5g-li","status":"publish","type":"post","link":"https:\/\/ic-services.io\/de\/resources\/blog\/x1-x2-x3-interfaces-5g-li\/","title":{"rendered":"X1\/X2\/X3-Schnittstellen in 5G: Die 3GPP LI-Architektur wird erkl\u00e4rt"},"content":{"rendered":"

The X1 X2 X3 5G interface architecture represents a fundamental evolution in lawful interception design. The arrival of 5G has brought fundamental changes to how telecommunications networks are designed, deployed, and operated. For lawful interception, these changes are equally profound. The 3GPP LI architecture for 5G builds on the X1, X2 and X3 interfaces already known from 3G and 4G, but now with standardised protocols (ETSI TS 103 221-1 and TS 103 221-2) instead of the vendor-specific implementations used in previous network generations. For operators deploying 5G networks, understanding the X1\/X2\/X3 architecture is essential to building LI capabilities that meet regulatory requirements and function effectively in the new network environment.<\/p>\n\n\n\n

Dieser Artikel enth\u00e4lt eine ausf\u00fchrliche Erl\u00e4uterung der 3GPP-LI-Architektur f\u00fcr 5G, wobei der Schwerpunkt auf den Schnittstellen X1, X2 und X3, deren Beziehung zu den ETSI-HI-Schnittstellen sowie den praktischen Auswirkungen f\u00fcr Netzbetreiber und LI-L\u00f6sung<\/a> Anbieter.<\/p>\n\n\n\n

Die X1-, X2- und X3-5G-Architektur<\/h2>\n\n\n\n

Das von 3GPP definierte 5G-Kernnetz nutzt eine dienstbasierte Architektur (SBA), die sich grundlegend von den knotenbasierten Architekturen von 3G und 4G unterscheidet. Anstelle dedizierter Netzwerkelemente, die bestimmte Funktionen ausf\u00fchren, besteht das 5G-Kernnetz aus einer Reihe von Netzwerkfunktionen (NFs), die \u00fcber dienstbasierte Schnittstellen miteinander kommunizieren. Zu den wichtigsten Netzwerkfunktionen z\u00e4hlen die Access and Mobility Management Function (AMF), die Session Management Function (SMF), die User Plane Function (UPF) und viele andere.<\/p>\n\n\n\n

Dieser architektonische Wandel hat erhebliche Auswirkungen auf die LI. In fr\u00fcheren Generationen wurde die \u00dcberwachung in der Regel an bestimmten Netzwerkknoten umgesetzt \u2013 dem MSC f\u00fcr Sprache in 3G, dem P-GW f\u00fcr Daten in 4G \u2013, bei denen es sich um klar definierte Punkte handelte, an denen der Signalisierungs- und der Nutzer-Ebenen-Verkehr der Zielperson zusammenliefen. In 5G erfordert der verteilte und virtualisierte Charakter der Netzwerkfunktionen einen anderen Ansatz f\u00fcr die \u00dcberwachung. Die 3GPP-LI-Architektur l\u00f6st dieses Problem, indem sie standardisierte Schnittstellen zwischen dem LI-System und den Netzwerkfunktionen definiert, anstatt sich auf knotenspezifische \u00dcberwachungsmechanismen zu verlassen.<\/p>\n\n\n\n

Die LI-Architektur in 3GPP TS 33.127 und TS 33.128<\/h2>\n\n\n\n

The 3GPP LI architecture for 5G is defined primarily in three specifications: TS 33.126 (Lawful Interception requirements), TS 33.127 (Lawful Interception architecture and functions) and TS 33.128 (Lawful Interception protocols and procedures, stage 3). These specifications define the functional components of the LI system within the 5G network, the interfaces between them, and the interfaces to the law enforcement domain.<\/p>\n\n\n\n

The key functional components defined in TS 33.127 are the Administration Function (ADMF), which receives warrants (in its LI Control Function, LICF) and provisions the LI system (through its LI Provisioning Function, LIPF); the Points of Interception (POIs) inside or alongside the network functions, split into IRI-POIs and CC-POIs; Triggering Functions (TFs), which activate interception at POIs such as the UPF on demand; and the Mediation and Delivery Function (MDF), split into MDF2 for IRI and MDF3 for content, which delivers the result to law enforcement.<\/p>\n\n\n\n

The interfaces between these components are designated X1, X2, and X3. These interfaces are internal to the operator’s domain \u2014 they connect the LI management and delivery functions to the network functions \u2014 and are distinct from the ETSI HI interfaces, which connect the operator to the LEMF. In practice, X2 and X3 feed the handover interfaces: the MDF2 turns xIRI received over X2 into IRI for HI2, and the MDF3 turns xCC received over X3 into CC for HI3. X1 has no HI counterpart: it is the operator’s internal provisioning channel, while HI1 carries the warrant from the authority to the operator.<\/p>\n\n\n\n

X1: Die Verwaltungsschnittstelle<\/h2>\n\n\n\n

X1 is the interface over which the ADMF provisions and manages the POIs, the triggering functions and the MDF. Through X1, the ADMF sends instructions to the POIs to activate, modify, or deactivate interceptions. The X1 interface carries the target identification parameters, the scope of the interception, and any technology-specific configuration information needed by the POI.<\/p>\n\n\n\n

X1 uses ETSI TS 103 221-1: XML messages sent as HTTP POST requests over HTTPS (HTTP\/1.1 or HTTP\/2), with mutual TLS authentication using X.509 certificates. X1, X2 and X3 are not new as concepts (3GPP TS 33.107 already used them for 3G and 4G), but in previous generations their protocols were left to vendors. For 5G, TS 33.128 mandates the standardised ETSI protocols TS 103 221-1 (X1) and TS 103 221-2 (X2\/X3), which can also be used for 4G and IMS.<\/p>\n\n\n\n

The X1 interface supports various target identification methods, including SUPI (Subscription Permanent Identifier), GPSI (Generic Public Subscription Identifier), PEI (Permanent Equipment Identifier), and IP addresses. Because 5G conceals the permanent identifier on the radio interface (SUCI, 5G-GUTI), TS 33.127 adds identifier-association functions (IEF, ICF and IQF) that let the operator and the LEA map temporary identifiers to the target’s SUPI.<\/p>\n\n\n\n

X2: Die IRI-\u00dcbertragungsschnittstelle<\/h2>\n\n\n\n

X2 is the interface for delivering intercept-related information from the Points of Interception to the LI Mediation and Delivery Function. When a target’s communications trigger events at the POI \u2014 such as registration, session establishment, mobility events, or session termination \u2014 the IRI-POI generates xIRI records and sends them to the MDF2 over X2.<\/p>\n\n\n\n

The X2 IRI records in the 5G architecture are significantly richer than those in previous generations, reflecting the more complex signalling and session management in 5G networks. X2 records may include information about PDU (Protocol Data Unit) session establishment, QoS (Quality of Service) flow creation and modification, handover events, network slice selection, and service-specific parameters. The X2 records (xIRI) are defined in TS 33.128 as BER-encoded ASN.1 and carried in the binary X2 PDU format of ETSI TS 103 221-2.<\/p>\n\n\n\n

The X2 interface operates in a push model \u2014 the POI generates and sends xIRI records to the MDF2 as events occur, without waiting for a request. The delivery must be timely and reliable, as the IRI forms a critical part of the intercepted material delivered to law enforcement. The MDF2 receives X2 records from potentially multiple POIs across the network, correlates them, and formats them for delivery to the LEMF over the HI2 interface.<\/p>\n\n\n\n

X3: Die CC-\u00dcbertragungsschnittstelle<\/h2>\n\n\n\n

X3 carries content (xCC) from the CC-POIs to the MDF3. For 5G data sessions the CC-POI is in the UPF: when the target’s PDU session is set up, the triggering function in the SMF instructs the UPF over LI_T3 to duplicate the session’s user-plane packets \u2014 IP packets carrying voice, data, messaging, and other services \u2014 and send them over X3.<\/p>\n\n\n\n

The X3 interface handles potentially large volumes of data, particularly for data-heavy targets. The interface must be dimensioned to handle the throughput requirements without packet loss, and the delivery mechanism must maintain the integrity and ordering of the intercepted packets. The MDF3 receives the X3 traffic, processes it as needed, and delivers it to the LEMF over the HI3 interface.<\/p>\n\n\n\n

In the 5G architecture, the UPF is the primary POI for user-plane interception. However, the UPF may be deployed in different locations within the network \u2014 at the edge, in regional data centres, or in central facilities \u2014 depending on the network architecture and the services being provided. The LI system must be capable of interacting with UPFs wherever they are deployed, which may require distributed X3 collection points and centralised processing at the MDF3.<\/p>\n\n\n\n

Network Slicing verleiht der X3-Abfangfunktion eine zus\u00e4tzliche Dimension. Der Datenverkehr eines einzelnen Ziels kann \u00fcber mehrere Netzwerk-Slices flie\u00dfen, von denen jedes \u00fcber eine eigene UPF-Instanz verf\u00fcgt. Das LI-System muss den Datenverkehr des Ziels \u00fcber alle relevanten Slices hinweg identifizieren und abfangen, um eine l\u00fcckenlose Erfassung der Kommunikation des Ziels zu gew\u00e4hrleisten.<\/p>\n\n\n\n

Zusammenhang zwischen X1\/X2\/X3 und HI1\/HI2\/HI3<\/h2>\n\n\n\n

The X interfaces and the HI interfaces serve different but complementary roles in the overall LI architecture. The X interfaces operate within the operator’s domain, connecting the LI management and delivery functions to the network infrastructure. The HI interfaces operate at the boundary between the operator and law enforcement: HI1 carries the warrant to the operator, and HI2 and HI3 deliver the intercepted IRI and content to the LEMF.<\/p>\n\n\n\n

The LI Mediation and Delivery Function serves as the bridge between these two interface sets. It receives X2 IRI records from the POIs, processes and formats them, and delivers the resulting ETSI-compliant IRI over the HI2 interface to the LEMF. Similarly, it receives X3 content (xCC) from the CC-POIs, such as the UPF, processes it, and delivers it over the HI3 interface. On the administration side, the ADMF receives the warrant over HI1 (typically ETSI TS 103 120), and its provisioning function sends X1 messages (ETSI TS 103 221-1) to the POIs, the triggering functions and the MDF itself.<\/p>\n\n\n\n

This layered architecture provides a clean separation between the internal network interception mechanisms and the external handover to law enforcement. It allows the network functions to implement interception using standardised X interfaces without needing to understand the specific requirements of the national HI interface implementation, and it allows the MDF to adapt between different internal and external interface versions as standards evolve.<\/p>\n\n\n\n

Praktische Auswirkungen f\u00fcr die Betreiber<\/h2>\n\n\n\n

For operators deploying 5G networks, the X1\/X2\/X3 architecture has several practical implications. First, LI must be considered from the earliest stages of 5G network design. The POI interfaces within the network functions must be planned and provisioned, the MDF must be dimensioned for the expected interception volumes, and the connectivity between the POIs and the MDF must be established.<\/p>\n\n\n\n

Second, operators must ensure that their 5G network function vendors support the X1, X2, and X3 interfaces as defined in TS 33.127 and TS 33.128 (ETSI TS 103 221-1\/-2 as profiled by TS 33.128). TS 33.128 also makes ETSI TS 103 120 the HI1 protocol and ETSI TS 102 232-1\/-7 the HI2\/HI3 transport for 5G. Vendor support for the LI interfaces has historically been uneven, and operators should include LI interface compliance as a requirement in their procurement specifications.<\/p>\n\n\n\n

Third, the virtualised and cloud-native nature of 5G networks introduces new challenges for LI deployment. The MDF and POIs may need to operate in containerised environments, scale dynamically, and maintain performance and reliability across distributed deployments. Operators must ensure that their LI solutions are designed for cloud-native operation and can keep pace with the dynamic nature of the 5G network.<\/p>\n\n\n\n

Schlussfolgerung<\/h2>\n\n\n\n

Die Schnittstellen X1\/X2\/X3 stellen eine bedeutende Weiterentwicklung der 3GPP-LI-Architektur dar und spiegeln die grundlegenden Ver\u00e4nderungen wider, die 5G f\u00fcr den Aufbau und Betrieb von Netzwerken mit sich bringt. X1 dient als Verwaltungskanal f\u00fcr die Steuerung von \u00dcberwachungsma\u00dfnahmen, X2 liefert die umfangreichen Metadaten, die Strafverfolgungsbeh\u00f6rden f\u00fcr ihre Ermittlungen ben\u00f6tigen, und X3 \u00fcbermittelt den Inhalt der ausgeleiteten Kommunikation. Zusammen mit den ETSI-HI-Schnittstellen bilden sie eine umfassende, mehrschichtige Architektur, die eine Telekommunikations\u00fcberwachung in den modernsten Telekommunikationsnetzen erm\u00f6glicht. F\u00fcr Netzbetreiber ist das Verst\u00e4ndnis und die Implementierung dieser Schnittstellen unerl\u00e4sslich, um ihren gesetzlichen Verpflichtungen nachzukommen und sicherzustellen, dass ihre 5G-Netze effektive und konforme Funktionen zur Telekommunikations\u00fcberwachung unterst\u00fctzen.<\/p>\n\n\n\n

Mit der zunehmenden Verbreitung von 5G-Standalone-Netzwerken gewinnen die 5G-Schnittstellen X1, X2 und X3 zunehmend an Bedeutung. Netzbetreiber m\u00fcssen sicherstellen, dass ihre 5G-Implementierungen f\u00fcr X1, X2 und X3 den neuesten 3GPP-Spezifikationen entsprechen.<\/p>\n\n\n\n

Verwandte Artikel<\/h2>\n\n\n\n

Weitere Informationen zu verwandten Themen finden Sie in diesen Artikeln:<\/p>\n\n\n\n