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

Glossary term · Radio Access Network

Hosting RAN

Hosting RAN

Radio Access Network →

Hosting RAN is a set of RAN resources provided by a Hosting RAN Provider for use by a Participating Operator, potentially including GERAN, UTRAN, or E-UTRAN, to enable infrastructure sharing among operators.

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

Description

The Hosting RAN (H-RAN) is a concept in 3GPP network sharing specifications that refers to the radio access network resources provided by a Hosting RAN Provider to a Participating Operator. It was introduced in Release 12 and originally defined as E-UTRAN resources, but was later expanded to include any combination of GERAN, UTRAN, or E-UTRAN, depending on which radio access technologies (RATs) are shared. The Hosting RAN is essentially the shared portion of the RAN that is owned or controlled by the Hosting RAN Operator and used by one or more Participating Operators.

In a network sharing arrangement, the Hosting RAN Provider deploys and operates the RAN infrastructure, which may consist of base stations (e.g., eNodeBs for E-UTRAN, NodeBs for UTRAN, or BTSs for GERAN) and associated equipment. The Participating Operator then uses these shared resources to provide services to its subscribers, while maintaining its own core network. The sharing can be implemented through various architectures, such as Multi-Operator Core Network (MOCN) or Multi-Operator RAN (MORAN). In MOCN, multiple core networks connect to the same shared RAN, and the RAN broadcasts multiple PLMN IDs to indicate the availability of different operators. In MORAN, the RAN equipment is logically partitioned, with each operator having its own dedicated carriers or sectors.

The Hosting RAN concept is defined in 3GPP TS 22.101 (Service aspects; Service principles) and TS 22.852 (Study on Radio Access Network (RAN) sharing enhancements). These specifications outline the requirements and architectural options for RAN sharing. The Hosting RAN can be provided by a third-party service provider or by one of the participating operators themselves. The key aspect is that the Hosting RAN Provider has operational control of the shared RAN, while the Participating Operators use it to serve their subscribers.

The evolution of the definition reflects the broadening scope of network sharing. Initially, in Rel-12, it was limited to E-UTRAN, but Rel-13 expanded it to include GERAN and UTRAN, acknowledging that operators might share multi-RAT networks. In Rel-14, the definition was rephrased to focus on the ownership/control aspect: 'The Shared RAN that is owned or controlled by the Hosting RAN Operator.' This wording remained stable through subsequent releases, indicating a mature understanding of the concept.

The Hosting RAN is a fundamental building block for network sharing, enabling operators to reduce costs, extend coverage, and accelerate deployment. It is particularly relevant in scenarios where building separate RANs is economically challenging, such as rural areas or indoor environments. The concept also supports regulatory mandates for infrastructure sharing in some countries.

Purpose & Motivation

The Hosting RAN concept was created to formalize the sharing of radio access network infrastructure among mobile operators. Before its introduction, network sharing was often ad-hoc and not standardized, leading to interoperability issues and inefficiencies. The Hosting RAN provides a clear definition of the shared RAN resources and the roles of the Hosting RAN Provider and Participating Operators. It solves the problem of high deployment costs and limited coverage by allowing operators to share RAN infrastructure while maintaining separate core networks and service offerings. The evolution from E-UTRAN-only to multi-RAT sharing reflects the growing need for flexible sharing arrangements as networks evolved.

What changed in its specifications

The latest release-to-release comparison of specifications that define Hosting RAN. 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.852Rel-12 → Rel-13

Rel-13 added GUSH use cases for multi-operator 2G sharing, UE moves between shared RATs, dynamic allocation, and minimum capacity requirements.

Full comparison in TS 22.852 →

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-12 Initial

Introduced as 'E-UTRAN resources provided by a Hosting RAN Provider for use by a Participating Operator.' Initially focused on LTE RAN sharing.

Wording changed to 'RAN resources provided by a Hosting RAN Provider for use by a Participating Operator. The RAN could be any combination of GERAN, UTRAN or E-UTRAN depending on which RATs are shared.' This expanded the scope to include 2G and 3G RATs.

Wording changed to 'The Shared RAN that is owned or controlled by the Hosting RAN Operator.' This rephrased the definition to emphasize ownership/control and introduced the term 'Hosting RAN Operator'.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Definition carried over unchanged from Rel-14.

Defining Specifications

3GPP specifications that define or reference Hosting RAN, 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.852 vd10 RAN Sharing Scenarios & Requirements Rel-13 read