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

Glossary term · Network Slicing

Indirect Network Sharing

Indirect Network Sharing

Network Slicing →

Indirect Network Sharing is a type of NG-RAN sharing in which a shared NG-RAN connects to a participating operator's core network through the hosting operator's core network, enabling cost-efficient sharing while keeping the shared radio access logically separated.

Introduced
Rel-19
Where
Services
Specifications
2 specs
Indirect Network Sharing Description Purpose What changed Detected Changes Specifications

Description

Indirect Network Sharing is a network sharing architecture defined in 3GPP specifications for NG-RAN sharing. In this model, the Shared NG-RAN is deployed and operated by a Hosting Operator, and one or more Participating Operators use the shared radio access network. The key characteristic of indirect sharing is that the communication between the Shared NG-RAN and the Participating Operator's core network is not direct; instead, it is routed through the Hosting Operator's core network. This contrasts with direct network sharing, where the Shared NG-RAN connects directly to each Participating Operator's core network.

Architecturally, the Shared NG-RAN consists of gNBs or ng-eNBs that are shared among operators. The Hosting Operator's core network, typically including AMF, SMF, UPF, and related functions, acts as an intermediary for signaling and user plane traffic between the Shared NG-RAN and the Participating Operator's core. The Participating Operator's core network connects to the Hosting Operator's core network through inter-core-network interfaces, which may involve roaming-like or dedicated interconnect arrangements. This means that the Shared NG-RAN's N2 and N3 interfaces terminate at the Hosting Operator's core, and the Participating Operator's traffic is carried across the hosting core to reach the participating core.

The main advantage of indirect network sharing is that it simplifies the Shared NG-RAN configuration because the RAN only needs to connect to a single core network, namely the Hosting Operator's core. This reduces the number of interfaces and the complexity of multi-operator connectivity at the RAN. It also allows the Hosting Operator to manage the shared RAN more efficiently and to provide a managed service to Participating Operators. However, it introduces additional latency and dependency on the Hosting Operator's core network, and it requires robust inter-core-network security and policy enforcement.

Indirect Network Sharing is specified in the context of 5G network sharing in TS 22.261 (Service requirements for the 5G system) and TS 22.851 (Study on network sharing). These specifications define the requirements and architectural options for NG-RAN sharing, including both direct and indirect models. The indirect model is particularly relevant for scenarios where a neutral host or a large operator provides shared RAN infrastructure to smaller operators, or where operators want to reduce the cost of connecting multiple core networks to a shared RAN.

The term was introduced in Rel-19, indicating that indirect network sharing was formalized as a distinct concept in the 5G era. In Rel-20, the definition remained unchanged, showing stability in the concept. The architecture relies on the separation of hosting and participating roles, and it must handle aspects such as network selection, slice availability, security, and charging across the two core networks. It is closely related to NG-RAN sharing, hosting operator, participating operator, and direct network sharing.

Purpose & Motivation

Indirect Network Sharing exists to provide a cost-effective and operationally simple way for multiple operators to share a 5G radio access network. Building and operating a nationwide NG-RAN is expensive, and sharing infrastructure can significantly reduce capital and operational expenditures, especially for smaller operators or in rural areas. The indirect model addresses the complexity of connecting a shared RAN to multiple core networks by funneling all RAN connectivity through a single hosting core network.

Before this concept was formalized, network sharing architectures often required the shared RAN to connect directly to each participating operator's core network, which increased the number of interfaces, complicated configuration, and raised security and policy challenges. The indirect model simplifies the RAN side by making the Shared NG-RAN appear as if it serves only the Hosting Operator's core, while the hosting core takes on the responsibility of interconnecting with participating cores. This can be attractive when the hosting operator already has robust core network infrastructure and interconnect agreements.

The introduction in Rel-19 reflects the growing interest in neutral host and multi-operator sharing models for 5G, particularly for indoor, rural, and enterprise deployments. It provides a standardized way to describe and implement sharing arrangements that were previously handled through proprietary or bilateral agreements. By defining indirect network sharing in 3GPP specifications, the industry gains a common vocabulary and architectural reference that supports interoperability and regulatory compliance.

What changed in its specifications

The latest release-to-release comparison of specifications that define Indirect Network Sharing. Each summary describes the whole specification, not only this term.

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

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-19 4 changes
  • Add Indirect Network Sharing to TS 22.261 TS 22.261CR0682
  • Add definitions for Indirect Network Sharing TS 22.261CR0684
  • Correction to the requirements of Indirect Network Sharing TS 22.261CR0794
  • CR on Indirect Network Sharing cleanup TS 22.261CR0748
Rel-20 1 change
  • New requirements for satellite access network sharing via Indirect Network Sharing TS 22.261CR0795

Defining Specifications

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

SpecificationTitleRelease
TS 22.261 vk81 5G Service and Operational Requirements Rel-20 read
TR 22.851 vj10 Feasibility Study on Network Sharing Aspect Rel-19 read