Description
Multi-Operator Core Network (MOCN) is a network-sharing configuration in which only the radio access network (RAN) is shared among multiple operators, while each participating operator keeps its own core network. It is defined in 3GPP specifications 23.251 (network sharing) and 25.413 (RANAP), and it is one of the two principal sharing architectures standardized by 3GPP, the other being the Gateway Core Network (GWCN) configuration in which core network elements are also shared.
In a MOCN deployment, a shared base station (eNodeB or gNB) or a shared radio access node serves cells that are available to subscribers of several operators. The key mechanism that makes this possible is the broadcasting of multiple Public Land Mobile Network (PLMN) identities in the shared cell. Each operator is identified by its own PLMN ID, and the shared RAN broadcasts the PLMN IDs of all participating operators so that UEs of each operator can select the shared cell as their serving cell. When a UE attaches, it indicates the selected PLMN, and the shared RAN routes the connection to the core network of the operator that owns that PLMN.
The routing of signaling and user data to the correct core network is a central aspect of MOCN. In 3G, RANAP messages carry the selected PLMN identity so that the RNC can direct the connection to the appropriate CN node. In LTE and 5G, the shared eNodeB/gNB uses the PLMN selection information from the UE and the network configuration to select the correct MME/AMF and, subsequently, the correct serving gateway or UPF. The shared RAN maintains mappings between PLMN IDs and core network nodes, and it may apply operator-specific configuration for parameters such as cell reselection, handover, and admission control.
MOCN offers significant advantages for operators. It allows cost sharing on the most expensive part of the network — the radio access infrastructure and spectrum — while preserving core network independence, which is attractive when operators want to keep their subscriber management, policy, and service platforms separate. It also enables rapid coverage expansion in rural or underserved areas where building parallel RANs would be uneconomical. Because only the RAN is shared, the operational and regulatory complexity of integrating core networks is avoided, and each operator retains full control over its core-domain services.
This stability reflects the maturity of the architecture and its continued relevance across 3G, LTE, and 5G deployments, where MOCN remains a common model for RAN sharing.
Purpose & Motivation
Network sharing emerged as operators faced the high capital and operational costs of deploying radio access networks, particularly for new technologies and in areas with limited revenue potential. Building and operating parallel RANs for each operator in the same geographic area is economically inefficient, especially in rural regions, along transport corridors, and during early phases of a new technology when coverage must be built quickly. MOCN was standardized to allow operators to share the RAN infrastructure and spectrum while keeping their core networks separate.
The MOCN model solves a specific problem: how to share the most costly network assets without requiring deep integration of core networks. Earlier or simpler sharing arrangements either did not allow multiple operators to be distinguished in a shared cell or required shared core elements, which raised concerns about competitive differentiation, subscriber data control, and regulatory compliance. By broadcasting multiple PLMN IDs and routing connections based on the selected PLMN, MOCN lets each operator's subscribers use the shared RAN transparently while each operator's core network remains fully independent.
The approach also supports regulatory and commercial goals: it can accelerate coverage obligations, enable new entrants to offer service without building a full RAN, and allow operators to pool resources in low-density areas. Its definition has remained unchanged since Release 8, demonstrating that the architecture has fully matured and continues to serve as the reference model for RAN-only sharing in 3GPP networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define Multi-Operator Core Network. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.251: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.251 →Release 12 adds LIPA and SIPTO procedural handling with new IEs, an MBMS Session Re-establishment Indicator IE, and BDS support including GANSS ID coding value 101.
Full comparison in TS 25.413 →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.
Defining Specifications
3GPP specifications that define or reference Multi-Operator Core Network, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.251 vj00 | Network Sharing Stage 2 Specification | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |