RI

Roaming Intermediary

Services
Introduced in R99
A network entity or function that facilitates roaming services between a home network and a visited network. It acts as a mediator for authentication, authorization, billing, and service delivery, ensuring seamless connectivity for subscribers outside their home operator's coverage.

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.

Key Features

  • Acts as a centralized hub for authentication and authorization signaling between home and visited networks.
  • Provides protocol translation and interoperability between different network generations and vendor implementations.
  • Aggregates and processes billing data records (CDRs/EDRs) for financial settlement between operators.
  • Enables steering of roaming (SoR) by influencing the network selection of roaming subscribers.
  • Supports value-added services like fraud management and real-time traffic analytics for roaming subscribers.
  • Reduces the operational complexity of managing a large number of direct bilateral roaming agreements.

Evolution Across Releases

R99 Initial

Conceptually referenced in early roaming architectures, primarily for circuit-switched voice and SMS roaming. The intermediary function was often performed by clearinghouses, focusing on billing settlement and basic SS7 signaling relay between HPLMN and VPLMN.

Gained increased relevance with the introduction of IMS and packet-switched roaming. Specifications began to more formally address the role of intermediaries in IP-based signaling (Diameter) and data traffic routing (GPRS Roaming Exchange - GRX).

Critical for LTE/EPC roaming, defining the role in Diameter-based interfaces like S6a (for HSS signaling) and S8 (for user plane tunneling). The IPX (IP eXchange) concept evolved from GRX, with the RI as a key functional entity within it.

Adapted for 5G System (5GS) roaming, supporting new interfaces like N32 (for security) and the Service-Based Interface (SBI) architecture. The RI's role expanded to handle HTTP/2-based signaling and more complex network slicing information exchange between PLMNs.

Continued enhancements for advanced 5G roaming scenarios, including support for network slicing in roaming, edge computing service exposure, and enhanced steering of roaming mechanisms with greater subscriber and service awareness.

Defining Specifications

SpecificationTitle
TS 21.905 3GPP TS 21.905
TS 23.172 3GPP TS 23.172
TS 29.573 3GPP TS 29.573
TS 32.373 3GPP TR 32.373
TS 32.376 3GPP TR 32.376
TS 33.501 3GPP TR 33.501
TS 36.212 3GPP TR 36.212
TS 36.213 3GPP TR 36.213
TS 36.321 3GPP TR 36.321
TS 36.867 3GPP TR 36.867
TS 36.871 3GPP TR 36.871
TS 38.212 3GPP TR 38.212
TS 38.214 3GPP TR 38.214
TS 38.762 3GPP TR 38.762
TS 38.843 3GPP TR 38.843
TS 38.889 3GPP TR 38.889