Operator Identifier

Description

The Operator Identifier (OI) is a fundamental component within the 3GPP network architecture, specifically within the realm of packet data connectivity. It is a string of characters that uniquely identifies a mobile network operator (MNO) or a mobile virtual network operator (MVNO) on a global scale. Its primary technical role is as a constituent part of the Access Point Name (APN), which is the fully qualified domain name (FQDN) used by a User Equipment (UE) to establish a data connection to a specific Packet Data Network (PDN), such as the internet or an operator's IMS service.

An APN is structured with two main parts: the Network Identifier (NI), which specifies the external PDN (e.g., 'internet'), and the Operator Identifier (OI), which specifies the network to which the PDN connection is anchored. The OI itself has a defined format, typically consisting of two or three labels. For a home network, it often takes the form 'mnc<MNC>.mcc<MCC>.gprs', where MNC is the Mobile Network Code and MCC is the Mobile Country Code assigned to the operator. This structure ensures global uniqueness. When a UE requests a PDN connection, it may provide an APN to the network. The serving network (SGSN in GPRS/UMTS, MME in LTE, AMF in 5G) parses this APN to extract the OI.

The parsing and interpretation of the OI are critical for routing decisions. If the OI in the requested APN matches the home network's identifier, the connection is established locally. If it matches a roaming partner's identifier, the serving network may route the connection request to that partner's network via the appropriate inter-operator interfaces (e.g., GTP-C tunnels). This mechanism is essential for enabling seamless roaming data services. The OI is also used in network-internal processes, such as APN resolution within the Domain Name System (DNS) of the operator's network, where it helps translate the APN into the IP address of the corresponding Gateway GPRS Support Node (GGSN), Packet Data Network Gateway (PGW), or User Plane Function (UPF).

Beyond basic connectivity, the OI plays a role in service differentiation and policy enforcement. Network policies, defined in systems like the Policy and Charging Rules Function (PCRF), can be keyed off the APN (and thus the OI) to apply specific quality of service (QoS), charging, and access control rules. This allows an operator to offer distinct service profiles for different partner networks or for its own branded services. In 5G, the concept evolves with the Data Network Name (DNN), but the principle of identifying the network operator for routing and policy purposes remains fundamentally important.

Purpose & Motivation

The Operator Identifier was created to solve the fundamental problem of unambiguously identifying a mobile operator's network in a globally interconnected ecosystem, particularly for packet-switched data services. Prior to standardized data services, circuit-switched voice roaming relied on the International Mobile Subscriber Identity (IMSI), which contains the MCC and MNC. However, the rise of GPRS and packet data introduced the need for a logical name-based routing system—the APN—to direct data sessions to specific service networks (e.g., corporate intranet, WAP portal, public internet). The OI provides the essential 'operator' part of this name.

Its creation was motivated by the need for scalable and flexible data roaming. Without a standardized operator identifier within the APN, it would be impossible for a visited network to determine where to route a data session request initiated by a roaming subscriber. The OI, based on the globally unique MCC/MNC pair, provides this deterministic routing key. It allows any network in the world to identify the home operator (or a specific partner operator) associated with a requested data service and to establish the appropriate tunnel to that operator's gateway.

Furthermore, the OI enables operator control over service exposure. It allows an operator to host multiple, logically separate packet data networks (e.g., 'internet.mnc01.mcc234.gprs' and 'ims.mnc01.mcc234.gprs') while using the same core network infrastructure. This facilitates service differentiation and the creation of dedicated APNs for enterprise customers or IoT services. In essence, the OI is a cornerstone of the APN architecture that enables the commercial and technical agreements between operators to be executed technically in the network, supporting both roaming and complex service offerings.

Key Features

• Globally unique identifier for a mobile network operator based on MCC and MNC
• Mandatory component of the Access Point Name (APN) structure
• Used for routing PDN connection requests in home and roaming scenarios
• Facilitates APN resolution in the operator's DNS infrastructure
• Enables policy and charging rule selection based on the destination network
• Supports service differentiation through operator-specific APNs

Evolution Across Releases

Defining Specifications