Primary Network Operator

Description

The Primary Network Operator (PNO) is a conceptual entity within 3GPP specifications that identifies the principal operator responsible for a user's subscription and primary network access. It is not a physical network node but a logical designation used in network policies, subscription data, and inter-operator agreements. The PNO is typically the user's home network operator, which holds the subscription and provides the core service profile, authentication credentials, and billing relationship. This concept is crucial for defining the 'home' network in contrast to visited networks during roaming.

Architecturally, the PNO's identity is embedded within the user's subscription profile stored in the Home Subscriber Server (HSS) or Unified Data Management (UDM). When a User Equipment (UE) attempts to attach to a network, the network discovery and selection procedures (governed by specifications like TS 22.912 and TS 22.937) use the PNO information to prioritize network selection. The UE's Universal Subscriber Identity Module (USIM) contains the Home Public Land Mobile Network (HPLMN) identifier, which directly corresponds to the PNO. The network selection algorithms ensure the UE attempts to register with the PNO's network first whenever it is available, guaranteeing service continuity and adherence to contractual agreements.

The role of the PNO extends into core network functions such as authentication, authorization, and policy control. During initial registration, the serving network contacts the PNO's home network to authenticate the user via the Authentication and Key Agreement (AKA) protocol. The PCF (Policy Control Function) in the PNO's network may apply specific policy and charging rules based on the user's subscription. In roaming scenarios, the PNO maintains the ultimate responsibility for the subscriber, even though the Visited Public Land Mobile Network (VPLMN) provides the radio access and local breakout services. The PNO concept is also integral to network sharing architectures like Multi-Operator Core Network (MOCN) and Gateway Core Network (GWCN), where multiple operators share radio access network resources but maintain separate core networks; in such cases, each operator acts as the PNO for its own subscribers.

In advanced deployments, including 5G Non-Public Networks (NPNs) and network slicing, the PNO concept adapts. For an enterprise deploying a private network, the enterprise itself can be considered the PNO for its closed user group. Within network slicing, a slice may be instantiated and managed by a specific PNO, even in a shared physical infrastructure environment. The PNO remains a key anchor point for service level agreements (SLAs), regulatory compliance, and end-to-end service management across increasingly complex and disaggregated network architectures.

Purpose & Motivation

The Primary Network Operator concept was introduced to provide a clear, unambiguous anchor point for subscriber ownership and network responsibility in a multi-operator ecosystem. Prior to its formalization, network selection and roaming relied heavily on the HPLMN identifier, but the evolving complexity of network sharing, national roaming agreements, and mobile virtual network operators (MVNOs) required a more robust logical framework. The PNO designation solves the problem of identifying 'who is ultimately responsible for the subscriber' in scenarios where network infrastructure is shared or where a user roams onto a partner network.

Historically, as GSM evolved into 3G and LTE, operators began sharing infrastructure (like cell towers and radio equipment) to reduce deployment costs, especially in rural areas. This created scenarios where a user's device might detect multiple Public Land Mobile Network (PLMN) IDs from a single radio tower. The PNO concept, formalized in Release 8 alongside early LTE work, provided the necessary logic for the UE and network to determine the correct 'home' operator for registration, authentication, and policy enforcement. It addressed limitations where simple PLMN-based selection was insufficient for complex commercial and operational models like network-as-a-service.

Furthermore, the PNO framework is essential for regulatory compliance, particularly for emergency services (e.g., E911), lawful interception, and number portability. Regulators need to identify the responsible operator for a subscriber call or data session. The PNO serves as that definitive entity, ensuring accountability. Its creation was motivated by the need for a scalable, future-proof model that could accommodate not only traditional MNOs but also MVNOs, private network operators, and neutral hosts, all while maintaining seamless user experience and clear operational boundaries.

Key Features

• Defines the home operator responsible for a subscriber's subscription and primary service delivery.
• Anchors network selection procedures, ensuring UEs prioritize connecting to the PNO's network when available.
• Serves as the root of trust for authentication, authorization, and policy control in home and roaming scenarios.
• Provides a clear entity for regulatory accountability, billing, and service level agreements.
• Adapts to modern network architectures including network sharing (MOCN/GWCN), MVNOs, and Non-Public Networks.
• Embedded within subscription data on the HSS/UDM and the UE's USIM as the Home PLMN (HPLMN).

Evolution Across Releases

Defining Specifications