Description
The Mobile Network Code (MNC) is a critical identifier within the 3GPP system, forming part of the International Mobile Subscriber Identity (IMSI). The IMSI is a globally unique number stored on a subscriber's SIM card and in the operator's Home Location Register (HLR) or Home Subscriber Server (HSS). The IMSI structure is defined as MCC-MNC-MSIN, where MCC is the Mobile Country Code, MNC is the Mobile Network Code, and MSIN is the Mobile Subscriber Identification Number. The MNC specifically identifies the mobile network operator (e.g., Vodafone, AT&T) within the country defined by the MCC. Its length is either two or three digits, as defined by the national regulatory authority, and this length must be consistent for all operators within that country.
Architecturally, the MNC is used at multiple points in the network. During initial network attachment, a mobile device presents its IMSI. The serving network (e.g., a Visitor Location Register - VLR, or Mobility Management Entity - MME) extracts the MCC and MNC to identify the subscriber's home network. This triggers the authentication and authorization procedures, where the serving network contacts the subscriber's home network (identified by the MCC+MNC) to verify credentials and retrieve the subscriber's profile. The MNC is also essential for routing signaling and user data, especially in roaming scenarios. When a subscriber is roaming, the visited network uses the MNC (in conjunction with the MCC) to route signaling messages to the correct home network for service authorization and billing.
Beyond core network procedures, the MNC is broadcast by cells as part of the Public Land Mobile Network (PLMN) identity (MCC+MNC). Mobile devices use this broadcast information to identify available networks for cell selection, reselection, and handover. The device's SIM contains a list of preferred PLMNs (home and roaming partners), which are prioritized based on their MCC-MNC combinations. This ensures the device connects to the most appropriate network. The MNC's role extends into network management and lawful interception, where it is used to filter and identify traffic belonging to specific operators. Its consistent definition across all 3GPP releases ensures backward and forward compatibility in multi-vendor, multi-operator environments.
Purpose & Motivation
The MNC was created to solve the fundamental problem of uniquely identifying a mobile network operator on a global scale. Prior to standardized numbering plans, proprietary identification schemes would have made international roaming impossible, as a visiting network would have no way to identify and route queries to a subscriber's home network. The MNC, as part of the IMSI defined in the GSM era (Release 99), established a universal addressing scheme.
This addressing is crucial for enabling automated roaming, billing, and service delivery. When a subscriber travels abroad, the visited network reads the MNC from the IMSI and uses it, along with the MCC, to determine the home operator. This allows the visited network to establish a secure signaling connection to the correct home network's HLR/HSS to authenticate the user and retrieve subscription data. Without this standardized code, seamless global mobility would not be feasible. The MNC also allows regulatory bodies to manage the radio spectrum and license operators within a country, assigning each a unique code to avoid conflicts.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, a key enhancement for the MNC function was the formal **Definition of the Primary PLMN ID**. This provides a clearer and more structured identification of the home network for a UE, directly impacting PLMN selection procedures. The definition reinforces that the **Home PLMN** is identified where the MCC and MNC match those of the IMSI, as defined in the core network specifications.
- Definition of Primary PLMN ID TS 23.251CR0108
In Release 16, the MNC function was enhanced to support non-IMSI based subscription identifiers, as indicated by the introduction of a dedicated AID for USIM applications with non-IMSI based SUPI types. Furthermore, new USIM configuration capabilities were added, specifically for managing a list of allowable PLMNs. These updates provided more flexibility in subscriber identity management and network selection procedures.
- Support for USIM configuration of RLOS PLMN list TS 31.102CR0847
- Either IMSI or NSI - Report of SA3 S3-194455 Tdocs recommendation (in Rel16) TS 31.102CR0884
- Dedicated AID for USIM Applications with non-IMSI based SUPI Types TS 31.102CR0897
- Serving PLMN Rate Control in List of Traffic Data Volumes TS 32.298CR0729
In Release 17, the MNC function was updated to explicitly include support for satellite networks within PLMN selection procedures, as indicated by the introduction of "Satellite E-UTRAN in PLMN selector" and "Satellite RATs for PLMN selection." Furthermore, clarifications were made regarding the storage of PLMN-related URSP rules, both generically and specifically for rules stored on the USIM. The release also introduced a mechanism to adjust timers for high-priority PLMN searches using a multiplier coefficient.
- Introducing multiplier coefficient to adjust high priority PLMN search timer TS 31.102CR0948
- Satellite E-UTRAN in PLMN selector TS 31.102CR0956
- Clarifications on PLMN and SNPN URSP storage - 24.526 part TS 24.526CR0112
- Clarifications on PLMN URSP stored in USIM TS 24.526CR0113
- Satellite RATs for PLMN selection TS 31.102CR0908
- Removal of IMSI in clause 5.2.33 TS 31.102CR0924
In Release 18, enhancements were made to the MNC function within PLMN selection and network identification procedures. Specifically, updates were introduced for URSP (UE Route Selection Policy) re-evaluation upon a PLMN change, ensuring policies are dynamically updated when the mobile station selects a new network. Additionally, the PLMN ID configuration was extended for the Home N3IWF (Non-3GPP InterWorking Function), refining the identification of non-3GPP access networks within the PLMN architecture.
In Release 19, the MNC function was enhanced through the introduction of an Operator-controlled-LSP-PLMN capability and a PeriodicSearchTimerNonLSP procedure. These new features provide the network with greater control over PLMN selection parameters for the Mobile Station in idle mode. Specifically, they allow the operator to manage the list of allowable PLMNs and the timing of searches for non-LSP networks.
- Introducing Operator-controlled-LSP-PLMN and PeriodicSearchTimerNonLSP TS 31.102CR1081
Explore further
Broader topics and technologies where MNC plays a role.
Defining Specifications
3GPP specifications that define or reference MNC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.022 vj00 | ME Personalisation Features for GSM/3G | Rel-19 |
| TR 22.975 v1310 | UMTS Numbering and Addressing Requirements | Rel-4 |
| TS 23.251 vj00 | Network Sharing Stage 2 Specification | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 23.782 vf00 | Interworking between LTE MC and non-LTE MC systems | Rel-15 |
| TS 23.851 v1600 | Network Sharing Architecture for 3G Systems | Rel-6 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.235 vc10 | I-WLAN Interworking Management Object | Rel-12 |
| TS 24.305 vj00 | Selective Disabling of 3GPP UE Capabilities | Rel-19 |
| TS 24.526 vj30 | UE Policies for 5GS; Stage 3 | Rel-19 |
| TS 25.304 vj00 | UTRA Idle Mode Procedures Specification | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.367 vj00 | Home NodeB Mobility Procedures | Rel-19 |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 |
| TR 26.939 vj00 | Framework for Live Uplink Streaming (FLUS) | Rel-19 |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 |
| TS 31.102 vj40 | USIM Application Specification | Rel-19 |
| TS 31.121 vi50 | UICC-terminal interface test specification | Rel-18 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | Rel-19 |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 |
| TS 32.298 vj30 | Charging Data Record (CDR) Parameter Specification | Rel-19 |
| TS 32.849 vd00 | IMS Roaming Charging Study | Rel-13 |
| TS 36.304 vj00 | UE Idle Mode Procedures in E-UTRA | Rel-19 |