RI

Roaming Intermediary

Services →
Introduced in R99 Also in: Services, Management

RI is a network entity that facilitates roaming services by acting as a mediator between home and visited networks for authentication, authorization, billing, and service delivery.

Category
Services
Introduced
R99
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
16 specs
RI Description Purpose Related Classification Detected Changes Specifications

Description

A Roaming Intermediary (RI) is a conceptual and functional entity within the 3GPP architecture that plays a crucial role in enabling and managing roaming relationships between mobile network operators (MNOs). It is not a single, monolithic network node but rather a set of functions that can be implemented by specialized service providers or within an operator's own infrastructure. The core purpose of the RI is to sit between the Home Public Land Mobile Network (HPLMN) and the Visited Public Land Mobile Network (VPLMN), streamlining the complex processes required for a subscriber to use services in a foreign network.

Architecturally, the RI interfaces with key network functions in both the home and visited networks. On the HPLMN side, it interacts with the Home Subscriber Server (HSS) or Authentication Centre (AuC) for credential verification and with billing systems. On the VPLMN side, it connects with the Visitor Location Register (VLR) in circuit-switched domains or the Mobility Management Entity (MME) in LTE/5G for packet-switched domains. The RI's operation begins when a roaming subscriber attempts to attach to a VPLMN. The VPLMN, instead of contacting the HPLMN directly, may route the authentication and authorization request through the RI. The RI then proxies the request to the appropriate HPLMN systems, relays the response, and may translate between different protocol versions or formats used by the two operators.

Beyond basic attachment, the RI facilitates several critical roaming processes. It is central to the Diameter-based roaming interfaces (e.g., S6a, S8, S9) in Evolved Packet Core (EPC) and 5G Core (5GC). It manages the secure exchange of authentication vectors, subscriber profile data, and policy information. Furthermore, the RI plays a pivotal role in financial settlement by collecting and correlating billing data records (CDRs/EDRs) from the VPLMN, applying agreed-upon tariffs, and presenting consolidated records to the HPLMN. In advanced scenarios, it can also enable value-added roaming services, such as steering of roaming (SoR) to preferred partner networks, or provide fraud detection by analyzing roaming traffic patterns across multiple VPLMNs. Its implementation abstracts the complexity of direct peer-to-peer connections, especially for operators with hundreds of roaming partners.

Purpose & Motivation

The Roaming Intermediary concept evolved to solve the significant scalability, complexity, and cost challenges associated with direct bilateral roaming agreements. In early cellular networks (GSM), roaming required a direct signaling connection (via SS7) and a financial agreement between every pair of operators. For an operator with a global footprint, this meant managing thousands of individual connections, each with its own technical integration, testing, and commercial contract—a highly inefficient model.

The RI addresses these limitations by acting as a hub. An operator only needs to establish one robust connection to an RI provider, which in turn is connected to hundreds of other operators. This hub-and-spoke model drastically reduces the number of required interconnects. From a technical perspective, it solves interoperability issues; the RI can perform protocol mediation between operators using different 3GPP releases or vendor-specific implementations. It also simplifies the introduction of new services (like 4G LTE roaming or VoLTE roaming) because the RI can be upgraded centrally to support new standards, rather than requiring every operator pair to coordinate upgrades simultaneously.

Historically, the need for such intermediaries became acute with the explosive growth of global mobile data roaming in the 3G and 4G eras. The volume of signaling and data traffic, coupled with the need for real-time policy control and charging, made direct peering untenable for many. The RI model, formalized and referenced across numerous 3GPP specifications over many releases, provided a standardized framework for these hub providers (often called GRX/IPX providers in the data roaming context) to operate. It enabled the seamless, secure, and commercially viable global roaming ecosystem we have today, supporting everything from voice and SMS to high-speed mobile broadband and IoT services.

Classification

Part ofIPX
Related approachesHPLMNVPLMN

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 8 changes

In Release 18, the Roaming Intermediary (RI) function was enhanced with specific procedures for managing N32 connections, including the ability for the RI to reject N32 connection establishment and to initiate the termination of an N32-f connection or context. It also introduced new error handling mechanisms, such as routing N32-c Error Reporting Requests from the RI and handling RI-generated N32-f related errors, and defined the capability for the RI to originate applicative request messages over the N32-f interface. Furthermore, the terminology was updated, formally replacing terms like "IPX" and "Roaming Hub" with the standardized "Roaming Intermediary (RI)".

  • Procedures for Roaming Intermediary to reject N32 connection establishment TS 29.573CR0156
  • Routing the N32-c Error Reporting Request from the Roaming Intermediary TS 29.573CR0173
  • Error Handling for Roaming Intermediary Generated N32-f Related Error Request TS 29.573CR0179
  • Applicative request message originated by roaming intermediary over N32-f TS 29.573CR0165
  • N32-f connection and/or N32-f context termination initiated by Roaming Intermediary TS 29.573CR0184
  • Replacing IPX with Roaming Intermediary TS 29.573CR0191

+ 2 more changes

Rel-19 3 changes

In Release 19, the primary updates to the Roaming Intermediary (RI) function included a modification to the naming conventions for the RI and IPX (IP Packet Exchange) entities. Furthermore, the release introduced updates to the specific Roaming Intermediary Procedures and ensured alignment by formally introducing RI requirements that had been established in the previous release.

  • Modification on the names of IPX and roaming intermediary TS 29.573CR0213
  • Updates of the Roaming Intermediary Procedures TS 29.573CR0222
  • Roaming intermediary requirements introduction in previous release - alignment TS 33.501CR2131

Explore further

Broader topics and technologies where RI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.172 vj00 Service Change and UDI Fallback (SCUDIF) Rel-19
TS 29.573 vj50 PLMN/SNPN Interconnection Interface Stage 3 Rel-19
TS 32.373 v1900 IRP Security Services CORBA Solution Rel-9
TS 32.376 vj00 Security services for IRP Solution Set Rel-19
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 36.212 vj10 LTE Multiplexing and Channel Coding Rel-19
TS 36.213 vj10 LTE Physical Layer Procedures Rel-19
TS 36.321 vj00 E-UTRA MAC Protocol Specification Rel-19
TS 36.867 vd00 LTE DL 4 Rx Antenna Port Study TR Rel-13
TS 36.871 vb00 Downlink MIMO Enhancement for LTE-Advanced Rel-11
TS 38.212 vj10 NR Multiplexing and Channel Coding Rel-19
TS 38.214 vj10 NR Physical Layer Procedures for Data Rel-19
TS 38.762 vj00 Dynamic MIMO OTA Test Methodology for NR FR1 Rel-19
TS 38.843 vj00 Study on AI/ML for NR Air Interface Rel-19
TR 38.889 vg00 NR-based access to unlicensed spectrum study 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.