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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (26 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-17.
In Release 17, the "POP" (Participating Operator) function was newly introduced within the 5G MOCN (Multi-Operator Core Network) network sharing architecture for performance converged charging. Specifically, the PLMN Identifier field within the Network Sharing Charging Information was defined to carry the POP PLMN, allowing the Charging Enablement Function (CEF) to attribute performance measurement data to a specific participating operator. This enables the support of MOCN performance measurement charging scenarios where the tenant identifier in a charging data request can represent the participating operator.
- Update NR NRM to support MOCN network sharing scenario TS 28.541CR0468
- Add YAML solution set for NG-RAN MOCN network sharing scenarios TS 28.541CR0622
- Add requirememts for management support for 5G MOCN network sharing scenario with same Cell Identity TS 32.130CR0011
- Add requirememts for management support for 5G MOCN network sharing scenario with multiple Cell Identity TS 32.130CR0012
- Solution description for the requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario TS 32.130CR0019
- Add requirement about administrative management capability for operator specific cell TS 32.130CR0020
+ 1 more changes
In Release 18, the enhancements for the Participating Operator (POP) function specifically introduced new management and charging support for NG-RAN MOCN network sharing scenarios. This included adding requirements and examples for scenarios with multiple Cell Identity broadcast and defining an operator-specific QoS model for RAN sharing. Furthermore, the specifications detailed the structure of Network Sharing Charging Information, where the PLMN Identifier field explicitly holds the POP PLMN to which the performance information is related.
- Rel-18 CR TS 28.541 Add YAML solution set for NRM for operator specific QoS model for RAN sharing TS 28.541CR1029
- Rel-18 CR TS 28.541 Address EP_F1 issue for MOCN RAN sharing scenario TS 28.541CR1031
- Add new requirements for management support for NG-RAN MOCN network sharing scenario TS 32.130CR0024
- Rel-18 CR TS 32.130 Add requirements for NG-RAN MOCN network sharing scenario with multiple Cell Identity broadcast TS 32.130CR0026
- Rel-18 CR TS 32.130 Add an example for management support for NG-RAN MOCN network sharing scenario TS 32.130CR0029
- Rel-18 CR TS 32.130 Add an example of service -based management architecture for MOCN TS 32.130CR0033
+ 3 more changes
In Release 19, the new capabilities for the Participating Operator (POP) function specifically introduced performance converged charging for 5G MOCN network sharing. This included defining new Post Event Charging scenarios, message flows, and the necessary charging information and CDR fields to report performance analytics per POP. The enhancements also covered the service-based management architecture to support these new MOCN charging requirements.
- Rel-19 CR 28.201 Add charging architecture for MOCN TS 28.201CR0017
- Rel-19 CR 28.201 Add charging requirement for MOCN TS 28.201CR0018
- Rel-19 CR 28.201 Addition of message flow for MOCN TS 28.201CR0021
- Rel-19 CR 28.201 Addition of charging information for MOCN TS 28.201CR0023
- Rel-19 CR 28.201 Correction to information for MOCN TS 28.201CR0027
- Rel-19 CR 28.201 Addition of CDR information for MOCN TS 28.201CR0029
+ 4 more changes
Explore further
Broader topics and technologies where POP plays a role.
Defining Specifications
3GPP specifications that define or reference POP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.201 vj20 | 5G Network Slice Performance Analytics Charging | Rel-19 |
| TS 28.541 vk00 | 5G Network Resource Model (NRM) Stage 2/3 | Rel-20 |
| TR 28.813 vh00 | Study on New Energy Efficiency Aspects for 5G | Rel-17 |
| TR 28.825 vh00 | 5G Network Sharing Management Study | Rel-17 |
| TS 32.130 vj20 | Network Sharing OAM&P Requirements | Rel-19 |
| TS 32.291 vj40 | Charging Management: Service-Based Interface Protocol | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.310 vj50 | 3GPP Authentication Framework for Network Nodes | Rel-19 |
| TR 33.876 vi01 | Technical Report on Certificate Management | Rel-18 |