S-RAN

Shared Radio Access Network

Radio Access Network →
Introduced in Rel-12

S-RAN is an architectural and operational model where radio access network infrastructure is shared among multiple mobile network operators to enable cost reduction, faster deployment, and efficient spectrum utilization.

Category
Radio Access Network
Introduced
Rel-12
Where
Management
Specifications
4 specs
S-RAN Description Purpose Related Classification Detected Changes Specifications

Description

A Shared Radio Access Network (S-RAN) refers to a deployment scenario where the Radio Access Network (RAN) infrastructure—including base stations (gNBs in 5G, eNBs in 4G), antennas, and sometimes backhaul—is used by multiple Mobile Network Operators (MNOs) or Mobile Virtual Network Operators (MVNOs). This is a form of network sharing that goes beyond core network sharing. In an S-RAN setup, the participating operators share the physical RAN elements while maintaining independent core networks, subscriber databases, and service platforms. This allows each operator to provide its own services and maintain control over its subscribers while drastically reducing capital and operational expenditures on the radio layer.

The technical implementation of S-RAN can follow different models as defined by 3GPP, primarily Multi-Operator Core Network (MOCN) and Gateway Core Network (GWCN). In the MOCN model, the shared RAN node broadcasts the Public Land Mobile Network (PLMN) IDs of all sharing operators. A User Equipment (UE) camping on the cell can select its home PLMN, and the RAN routes the signaling and user data to the respective operator's core network based on the selected PLMN. The RAN must support separate configuration contexts for each operator, including distinct cell identities, tracking areas, and potentially radio resource management policies. The GWCN model is a variant where operators also share certain core network elements like the Mobility Management Entity (MME) in 4G.

Key architectural components enabling S-RAN include the shared base station hardware, shared or partitioned radio spectrum, and the transport network that connects the RAN to each operator's core. The RAN must implement robust isolation mechanisms to ensure that traffic and signaling for one operator do not interfere with another, and to prevent unauthorized access between operators. This involves logical separation at the data plane and careful management of operational support systems (OSS). S-RAN is particularly valuable for covering high-cost areas (e.g., rural), indoor venues (airports, stadiums), or for new market entrants who wish to launch services without the prohibitive cost of building a full RAN footprint from scratch.

Purpose & Motivation

S-RAN was developed to address the economic and practical challenges of deploying dense radio access networks, especially as mobile data demand skyrocketed and network upgrades to 4G and later 5G required significant investment. Building duplicate RAN infrastructure by multiple operators in the same geographical area is often economically inefficient, leads to visual pollution, and can face regulatory hurdles regarding site acquisition. S-RAN provides a solution by allowing operators to share the most expensive part of the network—the radio infrastructure—thereby reducing capital expenditure (CAPEX) and operational expenditure (OPEX) while still competing on services and core network features.

The concept gained formal specification in 3GPP around Release 12, evolving from earlier, more limited sharing concepts. It was motivated by the need to improve coverage, especially in rural and underserved areas where the business case for a single operator is weak. Sharing makes deployment viable. Furthermore, for 5G deployments, which require a denser network of cells, S-RAN is seen as a key enabler for rapid and cost-effective rollout. It also supports the neutral host model, where a third party builds and operates a RAN that is leased to multiple MNOs, commonly used in large indoor venues or private networks. S-RAN thus balances competition and collaboration in the telecommunications industry, promoting infrastructure efficiency without sacrificing service differentiation.

Classification

Part ofMOCN
Related approachesPLMN

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-12, normative work from Rel-17.

Rel-17 4 changes

In Release 17, the S-RAN (Secondary RAN) function was introduced to enable redundant data transmission for enhanced reliability, specifically for URLLC scenarios. The solution establishes that a UE can connect simultaneously to both an M-RAN and an S-RAN node, where the UE and network replicate packets and use identical PDCP sequence numbers for transmission over these separate nodes, with duplication eliminated at the PDCP or GTP-U layer. Furthermore, the release specified handover procedures for the S-RAN node, involving a Secondary Node Change as defined in TS 37.340, ensuring service continuity during mobility events.

  • Add requirememts for management support for 5G MOCN network sharing scenario with same Cell Identity TS 32.130CR0011
  • Add requirememts for management support for 5G MOCN network sharing scenario with multiple Cell Identity TS 32.130CR0012
  • Add missing use case and requirements for radio resources partitioning between POPs TS 32.130CR0018
  • Solution description for the requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario TS 32.130CR0019
Rel-18 4 changes

In Release 18, the S-RAN (Shared Radio Access Network) function was enhanced with new management requirements and architectural examples specifically for the NG-RAN MOCN (Multi-Operator Core Network) sharing scenario. The updates introduced support for configurations where multiple Cell Identities are broadcast from a shared RAN node. Furthermore, the specification added a service-based management architecture example to illustrate how these MOCN network sharing scenarios can be implemented and managed.

  • Add new requirements for management support for NG-RAN MOCN network sharing scenario TS 32.130CR0024
  • Rel-18 CR TS 32.130 Add requirements for NG-RAN MOCN network sharing scenario with multiple Cell Identity broadcast TS 32.130CR0026
  • Rel-18 CR TS 32.130 Add an example for management support for NG-RAN MOCN network sharing scenario TS 32.130CR0029
  • Rel-18 CR TS 32.130 Add an example of service -based management architecture for MOCN TS 32.130CR0033
Rel-19 5 changes

In Release 19, the S-RAN (Shared Radio Access Network) function introduced enhanced service-based management architecture for MOCN (Multi-Operator Core Network) and added new performance measurement requirements at PLMN granularity for Indirect Network Sharing. The release also clarified the descriptions of MOCN and GWCN (Gateway Core Network) scenarios and added specific access requirements for managing a shared NG-RAN.

  • Rel-19 CR TS 32.130 Add access requirements for management of shared NG-RAN TS 32.130CR0040
  • Rel-19 CR TS 32.130 Add PLMN granularity performance measurement requirements for Indirect Network Sharing TS 32.130CR0052
  • Rel-19 CR TS 32.130 Enhance the service-based management architecture for MOCN TS 32.130CR0044
  • Rel-19 CR TS 32.130 Correct the example of SBMA for MOCN TS 32.130CR0056
  • Rel-19 CR TS 32.130 Clarify MOCN and GWCN scenarios description TS 32.130CR0046

Explore further

Broader topics and technologies where S-RAN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.725 vg20 Study on URLLC Architecture Enhancements Rel-16
TS 32.130 vj20 Network Sharing OAM&P Requirements Rel-19
TS 32.851 vc20 Network Sharing OAM Requirements Rel-12
TS 33.825 vg01 Security for 5G URLLC Services Rel-16