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.
Key Features
- Globally unique operator identifier within a country context (combined with MCC)
- Integral component of the IMSI and broadcast PLMN ID
- Used for network selection, routing, and subscriber authentication
- Length is 2 or 3 digits, standardized per country
- Fundamental for enabling national and international roaming
- Used in network management, provisioning, and lawful interception systems
Evolution Across Releases
Initially defined as a core component of the International Mobile Subscriber Identity (IMSI) for GSM. It established the PLMN identification structure (MCC+MNC) for network selection, routing, and roaming. The specification fixed its role in subscriber identification and authentication procedures within the circuit-switched core network.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.022 | 3GPP TS 22.022 |
| TS 22.975 | 3GPP TS 22.975 |
| TS 23.251 | 3GPP TS 23.251 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.782 | 3GPP TS 23.782 |
| TS 23.851 | 3GPP TS 23.851 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.235 | 3GPP TS 24.235 |
| TS 24.305 | 3GPP TS 24.305 |
| TS 24.526 | 3GPP TS 24.526 |
| TS 25.304 | 3GPP TS 25.304 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.367 | 3GPP TS 25.367 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.939 | 3GPP TS 26.939 |
| TS 29.949 | 3GPP TS 29.949 |
| TS 31.102 | 3GPP TR 31.102 |
| TS 31.121 | 3GPP TR 31.121 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.270 | 3GPP TR 32.270 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.277 | 3GPP TR 32.277 |
| TS 32.278 | 3GPP TR 32.278 |
| TS 32.293 | 3GPP TR 32.293 |
| TS 32.298 | 3GPP TR 32.298 |
| TS 32.849 | 3GPP TR 32.849 |
| TS 36.304 | 3GPP TR 36.304 |