IPX

Internetwork Packet Exchange

Interface →
Introduced in Rel-4 Also in: Services, Security

IPX is a standardized, secure, and QoS-enabled IP-based interconnect framework for exchanging traffic between mobile operators and service providers to enable global roaming and reliable service delivery.

Category
Interface
Introduced
Rel-4
Where
Core Network › 5G Core
Also touches
2 segments
Specifications
12 specs
IPX Description Purpose Related Classification Detected Changes Specifications

Description

The Internetwork Packet Exchange (IPX) is a critical architectural framework defined by the GSM Association (GSMA) and adopted within 3GPP standards for interconnecting different IP-based service provider networks. It is not a single protocol but a comprehensive set of commercial and technical principles built on top of IP networks. The primary goal is to provide a trusted, managed backbone for the exchange of packet-switched traffic, replacing older, less efficient circuit-switched interconnects. It establishes a multi-service IP network that interconnects mobile network operators (MNOs), fixed operators, application service providers, and content providers globally.

Architecturally, IPX is based on a hub-and-spoke model where IPX Providers act as hubs, connecting multiple client networks (spokes). An IPX Provider is a carrier that meets stringent GSMA specifications for security, quality of service (QoS), and service level agreements (SLAs). The framework mandates the use of private IP addressing (e.g., within the 10.0.0.0/8 range) and IPsec tunnels or MPLS VPNs to create a secure, closed user group. This isolates the traffic from the public internet, ensuring confidentiality, integrity, and predictable performance. Key interfaces within the IPX ecosystem include the Network-to-Network Interface (NNI) between an IPX Provider and a client network, and the Inter-IPX Provider Interface (IPI) for interconnection between different IPX Providers.

From a functional perspective, IPX supports multiple services simultaneously over a single interconnect. This includes GRX (GPRS Roaming Exchange) for data roaming, voice over IP (VoIP) for IMS-based services like VoLTE and VoWiFi, SMS over IP (SMSoIP), and rich communication services (RCS). A core technical mechanism is the use of Diameter and SIP signaling proxies within the IPX network to route control-plane messages correctly between home and visited networks. The IPX framework enforces strict QoS classification, typically using DiffServ Code Points (DSCP), to prioritize real-time traffic like voice over less time-sensitive data. It also incorporates comprehensive transit and roaming billing models, settlement, and detailed traffic reporting, which are essential for commercial interoperability between operators.

Purpose & Motivation

IPX was created to solve the critical business and technical challenges of interconnecting disparate operator networks in the evolving all-IP landscape. Prior to IPX, international roaming and interconnect relied heavily on circuit-switched technologies like SS7 for voice and SMS, and the GRX—a best-effort IP network—for GPRS data roaming. As operators migrated core networks to IP-based architectures like IMS, a new, more robust interconnect was needed. The public internet was unsuitable due to its lack of security, unpredictable latency, jitter, packet loss, and absence of commercial settlement models. Operators required a carrier-grade alternative that could guarantee the performance and security necessary for real-time, revenue-generating services.

The introduction of IPX provided this managed, multi-service IP backbone. It solved the problem of service fragmentation by allowing voice, messaging, and data services to be delivered over a single, secure interconnection with end-to-end QoS guarantees. This was particularly vital for the launch of high-definition voice services like VoLTE, where consistent low latency and high audio quality are paramount. Furthermore, IPX established a standardized commercial framework with clear roles (IPX Provider, Customer Network), SLAs, and billing mechanisms, which reduced complexity and fostered global service interoperability. It enabled the scalable and efficient rollout of new IP-based services across operator boundaries, forming the backbone of modern global telecommunications.

Classification

Specific typesGRXRI
Related approachesIMSGPRSQoSSIP

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change

In Release 15, the primary new introduction for the IPX function was the formalization of security mechanisms between the SEPP and the IPX network. This enhancement specifically addressed the security of inter-operator connections when utilizing an IP-Interconnection Intermediate Carrier like IPX, as an alternative to direct connections or the public internet. The update reinforced the IPX's role in providing a secure, private network for multi-service support across various interconnection scenarios.

  • Security between SEPP and IPX TS 33.501CR0468
Rel-16 1 change

In Release 16, the new work for the IPX function introduced a standardized method for the exchange of IPX security information between providers. This enhancement built upon the IPX's established role as a secure, private interconnection carrier for multi-service support, moving beyond basic transport to address specific security parameters within its operational framework.

  • Exchange IPX security information lists TS 29.573CR0020
Rel-17 1 change

In Release 17, the enhancement for the IPX function centered on updating its modification policy. This provided a clearer governance framework for the IPX network, which serves as a private, multi-service interconnection carrier offering an alternative to the public Internet for quality and security. The update helps maintain the efficiency of supporting multiple services over a single connection under one agreement.

Rel-18 2 changes

In Release 18, the primary update for the IPX function was a significant terminology shift, replacing "IPX" with the more general term "Roaming Intermediary" across the specifications. This change also encompassed related terms like "roaming hub" to reflect a broader conceptual scope beyond just packet exchange. The core technical capabilities of the IP-Interconnection Intermediate Carrier, such as providing private network quality, security, and multi-service support over a single connection, remained the foundational context for this renamed function.

  • Replacing IPX with Roaming Intermediary TS 29.573CR0191
  • Modification on the name of IPX, roaming intermediary, Roaming Hub, etc. TS 33.501CR2008
Rel-19 2 changes

In Release 19, the primary update for the IPX function was a significant terminology change, replacing the term "IPX" (Internetwork Packet Exchange) with "RI" (Roaming Intermediary). This change also involved modifying the names of the "IPX" and "roaming intermediary" concepts themselves. The underlying technical function of the RI, as an IP-Interconnection Intermediate Carrier providing a private, multi-service alternative to the Internet for inter-operator connections, remained consistent with the previous release's description.

  • Replacing IPX with RI TS 29.573CR0211
  • Modification on the names of IPX and roaming intermediary TS 29.573CR0213

Explore further

Broader topics and technologies where IPX plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 22.893 va00 IP Service Interconnection Requirements Study Rel-10
TS 22.894 vb00 IMS Network-Independent Public User Identities Study Rel-11
TR 22.980 vj00 Network Composition Feasibility Study Rel-19
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TR 23.794 vh00 Study on enhanced IMS to 5GC integration Rel-17
TS 29.573 vj50 PLMN/SNPN Interconnection Interface Stage 3 Rel-19
TS 29.809 vc00 Diameter Overload Control Study Rel-12
TS 29.819 vd00 Diameter Base Protocol Update Analysis Rel-13
TS 32.808 v1800 Common User Profile Storage Framework Rel-8
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 33.517 vk00 5G Security Assurance Specification (SCAS) Rel-20
TR 33.841 vg10 Security aspects; Study on 256-bit algorithms for 5G 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.