Description
MOCN is a standardized 3GPP network sharing architecture defined to allow two or more mobile network operators (MNOs) to share a common Radio Access Network (RAN). In this model, the shared RAN, comprising NodeBs in UMTS or eNodeBs/gNBs in LTE/5G, is connected to the separate core networks of each participating operator. The shared RAN broadcasts multiple Public Land Mobile Network (PLMN) identities, allowing User Equipment (UE) to discover and select their home operator's network. A key architectural component is the RAN node's ability to route initial UE access requests to the correct core network based on the selected PLMN ID, typically using mechanisms like RAN-based Network Node Selection Function (RAN-NNSF) or core network assistance.
The operational flow begins when a UE, capable of network selection, identifies the available PLMNs from the system information broadcast by the shared cell. Upon selecting its home PLMN, the UE initiates a connection. The RAN node (e.g., a gNB in 5G) uses the selected PLMN ID, often in conjunction with the Network Slice Selection Assistance Information (NSSAI) in 5G, to determine the appropriate core network operator and route the Non-Access Stratum (NAS) signaling accordingly. This routing is critical and is managed over shared interfaces like the N2 (NG-C) interface in 5G, where a single RAN node maintains separate logical connections to the Access and Mobility Management Functions (AMFs) of different operators.
MOCN involves several key technical components: the shared RAN hardware and software, the broadcast of multiple PLMN IDs in system information blocks (SIBs), and the RAN's PLMN-aware routing function. It also requires support in the UE for multi-PLMN selection. The shared RAN must manage radio resources (like carriers and cells) in a way that can serve subscribers from all sharing operators, potentially with agreed-upon service level agreements (SLAs) on capacity partitioning or prioritization. From a core network perspective, each operator's network remains entirely independent, handling subscriber authentication, policy control, charging, and data routing separately. This separation ensures operational autonomy and security while maximizing the efficiency of the expensive RAN infrastructure.
Purpose & Motivation
MOCN was created to address the high capital expenditure (CAPEX) and operational expenditure (OPEX) associated with deploying and maintaining dense radio access networks, especially as mobile data demand exploded. Historically, each operator deployed its own exclusive RAN, leading to infrastructure duplication, increased site acquisition costs, and higher energy consumption. For new market entrants or smaller operators, these costs presented a significant barrier to entry and competitive service rollout. MOCN provides a standardized solution for RAN sharing, enabling operators to pool their resources.
The primary problems MOCN solves are inefficient spectrum utilization and redundant infrastructure. By sharing physical sites, antennas, and baseband units, operators can significantly reduce deployment and maintenance costs. It also allows for faster network rollout, particularly in rural or underserved areas where the business case for a single operator might be weak. Furthermore, in scenarios where spectrum is scarce, MOCN can enable operators to share licensed spectrum bands, leading to better overall spectral efficiency and improved user experience through combined coverage and capacity.
Before MOCN, operators could engage in site sharing (sharing physical mast and power) but lacked a standardized method for deep RAN sharing, including shared radio equipment and spectrum. Proprietary solutions existed but led to vendor lock-in and interoperability issues. 3GPP's standardization of MOCN, starting in Release 6, provided a vendor-neutral, interoperable framework. This was crucial for regulatory acceptance and for enabling complex operational models like national roaming or joint ventures, ensuring fair competition while promoting network densification and overall industry sustainability.
Key Features
- Shared RAN infrastructure broadcasting multiple PLMN IDs
- PLMN-aware routing of initial UE access to the correct core network
- Support for independent core networks per operator
- Standardized interfaces (Iu, S1, N2) for multi-operator connectivity
- UE capability for network selection from shared cells
- Flexible resource management and potential SLA-based partitioning
Evolution Across Releases
Introduced the initial MOCN architecture for UMTS, defining how a shared Radio Network Controller (RNC) and NodeB could connect to multiple core networks (MSCs/SGSNs). Specified the broadcasting of multiple PLMN IDs in system information and the RNC's role in routing initial signaling (RANAP) to the correct core network node based on the selected PLMN.
Extended MOCN principles to the Evolved Packet System (EPS/LTE). Defined shared eNodeB architecture supporting connections to multiple MMEs and S-GWs belonging to different operators over the S1 interface. Enhanced system information (SIB1) to broadcast multiple PLMN identities.
Integrated MOCN into the 5G System (5GS) architecture. Defined support for shared gNBs connecting to multiple operator core networks via the NG-C (N2) interface. Enhanced the mechanism to work in conjunction with Network Slicing, where the PLMN ID and NSSAI are used together for routing to the appropriate AMF.
Further enhanced MOCN for 5G, including improvements for mobility procedures between shared and non-shared cells, and clarified resource management and load balancing aspects in a multi-operator shared RAN context.
Ongoing studies and enhancements for advanced network sharing scenarios, potentially integrating with AI/ML for dynamic resource optimization and exploring MOCN implications for non-terrestrial networks (NTN).
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.261 | 3GPP TS 22.261 |
| TS 22.278 | 3GPP TS 22.278 |
| TS 22.803 | 3GPP TS 22.803 |
| TS 22.805 | 3GPP TS 22.805 |
| TS 22.851 | 3GPP TS 22.851 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.236 | 3GPP TS 23.236 |
| TS 23.251 | 3GPP TS 23.251 |
| TS 23.737 | 3GPP TS 23.737 |
| TS 23.768 | 3GPP TS 23.768 |
| TS 23.851 | 3GPP TS 23.851 |
| TS 23.889 | 3GPP TS 23.889 |
| TS 24.007 | 3GPP TS 24.007 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.410 | 3GPP TS 25.410 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.704 | 3GPP TS 25.704 |
| TS 28.825 | 3GPP TS 28.825 |
| TS 28.878 | 3GPP TS 28.878 |
| TS 29.280 | 3GPP TS 29.280 |
| TS 32.130 | 3GPP TR 32.130 |
| TS 33.883 | 3GPP TR 33.883 |
| TS 33.969 | 3GPP TR 33.969 |
| TS 38.401 | 3GPP TR 38.401 |
| TS 44.064 | 3GPP TR 44.064 |
| TS 45.820 | 3GPP TR 45.820 |
| TS 48.018 | 3GPP TR 48.018 |