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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, the primary new introduction for the IPX function was the specification of security between the SEPP (Security Edge Protection Proxy) and the IPX network. This enhancement focused on securing the interconnection point against threats like volume-based attacks from untrusted sources by enabling static and dynamic control over which Service Providers can access the network. It reinforced the IPX's role as a secure, private interconnection alternative to the Internet for multi-service support.
- Security between SEPP and IPX TS 33.501CR0468
In Release 16, the IPX function was enhanced with new capabilities for exchanging IPX security information and modification policies between providers. These updates specifically introduced mechanisms for dynamically controlling which service providers can access a network's interconnection point to defend against attacks from untrusted sources. This allowed for a more secure and policy-governed interconnection environment beyond the basic transport and connectivity functions.
In Release 17, the IPX function was updated with a new modification policy and included a correction to the Parameter Exchange procedure. These changes refined the operational governance and technical signaling between interconnected networks. The enhancements support the IPX's role as a secure, multi-service IP-Interconnection Intermediate Carrier, maintaining efficient end-to-end connectivity between operators and third-party service providers.
In Release 18, the primary update for the IPX function was a significant nomenclature shift, moving away from the term "IPX" (Internetwork Packet Exchange) and its associated provider term "IPXP" in favor of the more descriptive concept of a "Roaming Intermediary" or "Roaming Hub." This change was accompanied by procedural corrections and clarifications, specifically regarding the parameter exchange procedure to avoid collisions and the protection mechanisms for data and analytics exchange in roaming scenarios.
- Parameter exchange procedure collision TS 29.573CR0160
- Replacing IPX with Roaming Intermediary TS 29.573CR0191
- Editorial change on procedure for protection of analytics exchange in roaming case TS 33.501CR1919
- Modification on the name of IPX, roaming intermediary, Roaming Hub, etc. TS 33.501CR2008
- Correction on Protection of Data and Analytics Exchange in Roaming Case TS 33.501CR1822
In Release 19, the key update for the IPX function was a significant terminology shift, replacing the term "IPX" (Internetwork Packet Exchange) with "RI" (Roaming Intermediary). This change also involved modifying the associated name "roaming intermediary" to align with the new nomenclature. The core technical function described in the specifications—acting as a trusted IP-Interconnection Intermediate Carrier for services like roaming and inter-operator connections—remains conceptually unchanged despite this rebranding.
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.
| Specification | Title | Release |
|---|---|---|
| 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 |