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

Glossary term · Services

OP

Operator Platform

Services →

OP is a standardized 3GPP framework that enables network operators to securely expose network capabilities and data to trusted third parties for creating new services and applications.

Introduced
Rel-5
Where
Services › Codecs
Specifications
8 specs
Also in
Security
OP Description Purpose What changed Neighbours Specifications

Description

The Operator Platform (OP) is a service architecture defined by 3GPP that provides a managed interface between a mobile network operator's (MNO's) internal network capabilities and external application providers. It acts as a gateway, abstracting the complexity of the underlying network and exposing a set of Application Programming Interfaces (APIs) that are standardized, secure, and billable. The core architectural components include the Operator Platform itself (the logical entity implementing the APIs), the Network Exposure Function (NEF) in the 5G Core, and the backend systems of the MNO.

How it works involves several layers. Third-party Application Providers (e.g., a cloud gaming company, an IoT service provider) register with and are authenticated by the Operator Platform. They then use the published APIs to request specific network services. For example, an API call might request enhanced uplink bandwidth for a specific user device for a video upload session. The Operator Platform receives this request, validates it against the provider's service level agreement (SLA) and security policies, translates it into internal network commands, and interacts with core network functions like the Policy Control Function (PCF) or Session Management Function (SMF) via the NEF to enact the requested service. The platform also handles charging records, ensuring the third party is billed for the network resources consumed.

Its role in the network is pivotal for monetization and innovation. It shifts the operator's role from being a pure connectivity pipe to becoming an enabler of differentiated services. By exposing capabilities such as quality of service (QoS) management, location information, network status, and device triggering, the OP allows enterprises and developers to build applications that are tightly integrated with the network's performance and intelligence. This creates new revenue streams for operators and fosters an ecosystem of network-aware applications.

Purpose & Motivation

The Operator Platform concept was introduced to solve the problem of 'walled gardens' and limited service innovation in traditional telecom networks. Before its standardization, exposing network capabilities was done in a proprietary, ad-hoc manner, making it difficult for third-party developers to create services that worked across different operators' networks. This stifled innovation and limited the value derived from network investments.

Historically, with the rise of Over-The-Top (OTT) applications, operators saw their networks being used as dumb bit-pipes while value was captured by application providers. The OP, particularly as evolved through releases like Rel-15 and Rel-16 with the introduction of the NEF, was motivated by the need for operators to regain a role in the service value chain. It addresses the limitations of previous approaches by providing a standardized, scalable, and secure framework for service exposure. This enables operators to offer Network as a Service (NaaS), participate in vertical markets (like automotive, healthcare, and Industry 4.0), and dynamically tailor network behavior to the needs of specific applications, thereby creating new business models beyond simple data subscriptions.

What changed in its specifications

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

TS 23.048Rel-4 → Rel-5

Rel-5 added applet management commands, minimum security level specification, and a security layer relation to Open Platform architecture.

Full comparison in TS 23.048 →
TS 23.558Rel-18 → Rel-19

Rel-19 adds common EAS removal and update procedures, ACR event subscription, bundle EAS discovery, and federation and roaming to TS 23.558. It also adds application group handling with group-level EAS discovery and ACR for UE groups, plus ADAE edge load analytics for EES selection.

Full comparison in TS 23.558 →

Release Timeline

Evolution Across Releases

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

Rel-5 Initial

Initial concepts of service capability exposure emerged with the IP Multimedia Subsystem (IMS) and the Open Service Access (OSA) framework. This release laid the groundwork for exposing basic telephony and messaging capabilities to third-party applications, though in a relatively complex and limited manner compared to later platforms.

Enhanced service exposure with the Service Capability Exposure Function (SCEF), primarily for Machine-Type Communication (MTC) in the Evolved Packet Core (EPC). The SCEF provided a standardized way for IoT service providers to access network services like device triggering and monitoring, marking a significant step towards the Operator Platform concept for non-voice services.

A major architectural leap with the definition of the 5G Core and the Network Exposure Function (NEF). The NEF became the central node for capability exposure, superseding and expanding upon the SCEF. The Operator Platform concept matured, with the NEF providing the standardized southbound interface to network functions and the OP providing the business and management layer on top.

Enhanced the NEF and OP framework with support for verticals like V2X and industrial IoT. Introduced more granular APIs for network slicing management, edge computing service exposure, and enhanced location services. This release solidified the OP's role in enabling network slicing as a service.

Further expansion into new domains, including exposure of advanced analytics (via NWDAF - Network Data Analytics Function), enhanced support for private and non-public networks, and refinement of APIs for edge application orchestration. The platform's scope grew to encompass AI/ML-driven network insights as a service.

Defining Specifications

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

SpecificationTitleRelease
TS 22.895 vc00 3GPP SSO Framework Integration Study Rel-12 read
TS 23.048 v590 Secured Packets Structure for SMS and UICC Management Rel-5 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.862 vc00 Interworking Solutions for Mobile Operators & Data Apps Rel-12 read
TR 23.958 vj00 EDGEAPP alignment with ETSI MEC and GSMA OP Rel-19 read
TS 26.119 vj10 Device Media Capabilities for AR Services Rel-19 read
TS 33.804 vc00 Non-UICC SSO using SIP Digest credentials Rel-12 read
TR 33.924 vj00 GBA-OpenID Interworking Specification Rel-19 read