Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

Hosting RAN Operator

Hosting RAN Operator

Radio Access Network →

Hosting RAN Operator is the operator that has operational control of a shared NG-RAN, shared E-UTRAN, shared GERAN, or UTRAN, and provides shared RAN resources to participating operators.

Introduced
Rel-13
Where
Services
Specifications
2 specs
Hosting RAN Operator Description Purpose What changed Neighbours Specifications

Description

The Hosting RAN Operator (H-RAN-Op) is a role in 3GPP network sharing specifications that denotes the operator with operational control over a shared radio access network. This includes Shared NG-RAN (5G), Shared E-UTRAN (LTE), Shared GERAN (2G), or UTRAN (3G). The Hosting RAN Operator is responsible for the deployment, management, and operation of the shared RAN infrastructure, which is then used by one or more Participating Operators to provide services to their subscribers.

The concept was introduced in Release 13, initially covering Shared E-UTRAN, UTRAN, or GERAN. In Release 15, the definition was updated to include Shared NG-RAN, reflecting the emergence of 5G and the need to address sharing in the new radio access technology. The Hosting RAN Operator is distinct from the Hosting RAN Provider, which may be a third-party infrastructure provider; the Hosting RAN Operator is specifically an operator with operational control, meaning it holds the necessary licenses, spectrum, and management responsibilities.

Architecturally, the Hosting RAN Operator owns or controls the shared RAN elements, such as base stations and associated network functions. It interfaces with the core networks of Participating Operators, typically via standardized interfaces like S1 (for E-UTRAN) or N2/N3 (for NG-RAN). The Hosting RAN Operator ensures that the shared RAN resources are allocated according to sharing agreements, which may include radio resource partitioning, quality of service (QoS) differentiation, and security isolation. In MOCN, the shared RAN broadcasts multiple PLMN IDs, and the Hosting RAN Operator coordinates the routing of traffic to the appropriate core network based on the selected PLMN.

The role is defined in 3GPP TS 22.101 and TS 22.261. These specifications outline the service requirements for network sharing, including the responsibilities of the Hosting RAN Operator and the interactions with Participating Operators. The Hosting RAN Operator must support capabilities such as network selection, access control, and charging differentiation for each Participating Operator.

The Hosting RAN Operator concept is essential for enabling flexible and cost-effective network sharing across multiple generations of technology. It allows operators to share the high costs of RAN deployment and operation while maintaining competitive differentiation at the service level. The inclusion of NG-RAN in Rel-15 ensures that the concept remains relevant for 5G networks, where sharing is expected to be even more prevalent due to densification and high infrastructure costs.

Purpose & Motivation

The Hosting RAN Operator role was established to provide a clear definition of the operator responsible for shared RAN infrastructure. Before its introduction, network sharing arrangements lacked a standardized terminology for the entity controlling the shared RAN, leading to ambiguity in responsibilities and interfaces. The Hosting RAN Operator solves this by identifying the operator with operational control, which is crucial for regulatory compliance, spectrum licensing, and operational management. The extension to NG-RAN in Rel-15 ensures that the concept evolves with technology, supporting 5G network sharing and enabling new business models such as neutral host networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define Hosting RAN Operator. Each summary describes the whole specification, not only this term.

TS 22.101Rel-16 → Rel-17

Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.

Full comparison in TS 22.101 →
TS 22.261Rel-18 → Rel-19

Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.

Full comparison in TS 22.261 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-13 Initial

Introduced as 'The Operator that has operational control of a Shared E-UTRAN, UTRAN or GERAN', covering 2G, 3G, and 4G RAN sharing.

Definition carried over unchanged from Rel-13.

Wording changed to 'The Operator that has operational control of a Shared NG-RAN, Shared E-UTRAN, Shared GERAN or UTRAN.' This added Shared NG-RAN to the scope, reflecting the introduction of 5G.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Defining Specifications

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

SpecificationTitleRelease
TS 22.101 vl00 3GPP Service Principles for PLMNs Rel-21 read
TS 22.261 vk81 5G Service and Operational Requirements Rel-20 read