Participating Operator

Description

A Participating Operator (POP) is a fundamental business and operational role defined within 3GPP management and charging frameworks. It refers to a telecommunications network operator that is actively involved in a collaborative service offering, network sharing arrangement, or federation with one or more other operators. The POP is not just a passive peer but an entity with defined rights, obligations, and interfaces within the multi-operator ecosystem. This concept is crucial for scenarios like roaming, mobile virtual network operator (MVNO) hosting, service federation (e.g., for IoT or 5G slicing across operators), and various forms of infrastructure sharing including MORAN (Multi-Operator Radio Access Network) and MOCN (Multi-Operator Core Network).

Within the 3GPP architecture, the POP is represented in management systems (e.g., Network Management, Element Management) and charging systems. Specifications like TS 28.541 (5G Management) and TS 32.130 (Charging) detail how a POP is identified, authenticated, and authorized. Each POP has a unique identifier within the context of the agreement. The management interfaces allow a POP to view and manage its share of resources, receive performance reports, and be notified of faults affecting its services. In charging, the POP is a central entity in settlement processes; detailed accounting records are generated to track resource usage attributable to each POP, enabling accurate billing and revenue sharing between partners.

The technical implementation involves specific reference points and information models. For instance, in a network slicing scenario spanning multiple operators, each operator acting as a POP would expose a slice management sub-domain. The coordinating entity (which could be one of the POPs or a third party) uses standardized interfaces to compose an end-to-end slice using resources from each POP. Security specifications (e.g., TS 33.310) define how trust is established between POPs, often relying on a federation framework where a root certificate authority issues certificates to each participating operator.

Purpose & Motivation

The concept of a Participating Operator was formalized to support the complex commercial and technical partnerships required in modern telecommunications. As services evolved beyond simple bilateral roaming, operators began engaging in deep network sharing to reduce deployment costs, and in service federations to offer seamless cross-border IoT or enterprise solutions. These collaborations required a clear, standardized definition of each operator's role to enable automated provisioning, management, and settlement.

Prior to this formalization, multi-operator arrangements were often handled through bespoke bilateral agreements and manual processes, which were not scalable. The POP model addresses this by providing a standardized 'actor' within the 3GPP system architecture. This allows for the automation of key processes: a POP can be automatically granted access to a management system to monitor its slice, charging data records can be automatically tagged with the correct POP identifier for settlement, and security credentials can be automatically validated. This standardization lowers the barrier to forming partnerships, accelerates service deployment, and reduces operational costs, which is essential for the success of 5G network slicing and large-scale IoT deployments that inherently cross operator boundaries.

Key Features

• Defines an operator's role in multi-operator agreements and federations
• Has a unique identifier within management and charging systems
• Enables automated resource provisioning and service management across operators
• Central to inter-operator charging settlement and revenue sharing
• Integrates with 3GPP security frameworks for federated trust
• Supports various models like network sharing, roaming, and slice federation

Evolution Across Releases

Defining Specifications