Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Identifier

MNC

Mobile Network Code

Identifier →

MNC is a two- or three-digit code that uniquely identifies a mobile network operator within a country and is a core component of the IMSI for subscriber identification, roaming, and routing.

Introduced
R99
Where
Services › IMS
Specifications
28 specs
Also in
Core Network, User Equipment, Management, Radio Access Network
MNC Description Purpose What changed Neighbours Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define MNC. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.251Rel-18 → Rel-19

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 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

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

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.022 vj00 ME Personalisation Features for GSM/3G Rel-19 read
TR 22.975 v310 UMTS Numbering and Addressing Requirements R99 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.782 vf00 Interworking between LTE MC and non-LTE MC systems Rel-15 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.235 vc10 I-WLAN Interworking Management Object Rel-12 read
TS 24.305 vj00 Selective Disabling of 3GPP UE Capabilities Rel-19 read
TS 24.526 vk00 5GS UE Policies Rel-20 read
TS 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.367 vj00 Home NodeB Mobility Procedures Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TR 26.939 vj00 Framework for Live Uplink Streaming (FLUS) Rel-19 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.270 vj00 MMS Charging Management Specification Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.277 vj20 Charging Management for Proximity Services (ProSe) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.849 vd00 IMS Roaming Charging Study Rel-13 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read