MOCN

Multiple Operator Core Network

Radio Access Network →
Introduced in Rel-6 Also in: Radio Access Network, Services, Management, Security

MOCN is a network sharing architecture where multiple mobile network operators share the same radio access network infrastructure while maintaining independent core networks.

Category
Radio Access Network
Introduced
Rel-6
Where
Core Network › Evolved Packet Core
Also touches
4 segments
Specifications
28 specs
MOCN Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofPLMN
Related approachesAMF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 3 changes

In Release 17, 3GPP introduced new management support requirements for 5G MOCN network sharing. These enhancements specifically address both scenarios where operators share a network using a single, common Cell Identity and scenarios where they use multiple distinct Cell Identities. Furthermore, the release provided the corresponding solution description for managing the shared NG-RAN network elements within these MOCN configurations.

  • 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
  • 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 enhancements for MOCN focused on its management support within the NG-RAN sharing scenario. The updates introduced new requirements and examples, specifically addressing configurations involving multiple Cell Identity broadcast. Furthermore, the release added descriptive examples for the service-based management architecture applicable to MOCN.

  • 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 3 changes

In Release 19, the enhancements for MOCN specifically targeted its Service-Based Management Architecture (SBMA). The changes included correcting an existing SBMA example and providing clarifications on the descriptions for both MOCN and GWCN deployment scenarios.

  • 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 MOCN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 22.261 vk30 5G System Service Requirements Rel-20
TS 22.278 vj00 Evolved Packet System Service Requirements Rel-19
TS 22.803 vc20 Proximity Services (ProSe) Study Rel-12
TS 22.805 vc10 RAN User Plane Congestion Management Rel-12
TR 22.851 vj10 Feasibility Study on Network Sharing Aspect Rel-19
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19
TR 23.737 vh20 Satellite Access in 5G Architecture Study Rel-17
TS 23.768 vc10 Group Communication System Enablers for LTE Rel-12
TS 23.851 v1600 Network Sharing Architecture for 3G Systems Rel-6
TS 23.889 va00 Local Call Local Switch Core Network Impact Study Rel-10
TS 24.007 vj40 GSM Um Interface Layer 3 Architecture Rel-19
TS 25.401 vj00 UTRAN Overall Architecture Rel-19
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.704 vc00 Study on Enhanced Broadcast of System Information Rel-12
TR 28.825 vh00 5G Network Sharing Management Study Rel-17
TS 28.878 vj00 Study on Management of Network Sharing Phase3 Rel-19
TS 29.280 vj00 Sv Interface Specification for SRVCC Rel-19
TS 32.130 vj20 Network Sharing OAM&P Requirements Rel-19
TR 33.883 vi01 Technical Report on 5G Multicast-Broadcast Services Security Rel-18
TR 33.969 vj00 Security for Public Warning System (PWS) Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 44.064 vj00 GPRS Logical Link Control (LLC) Protocol Rel-19
TS 45.820 vd10 CIoT for Internet of Things Rel-13
TS 48.018 vj00 BSS-SGSN Interface for GPRS Control Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.