OPG.02-操作员平台：要求和架构

19February2026 Security Classification:Non-Confidential Access to and distribution of this document is restricted to the personspermitted by the securityclassification. This document is subject tocopyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not bedisclosed or in any other way made available, in whole or in part,to persons other than thosepermitted under the securityclassification withoutthe prior written approval of the Association. Copyright Notice Copyright ©2026GSM Association Disclaimer The GSMA makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, andhereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information containedin this document may be subject to change without prior notice. Compliance Notice The information contain herein is in full compliance with the GSMAAntitrustCompliancePolicy. This Permanent Reference Document is classified by GSMA as an Industry Specification, as such it has been developed and is maintained byGSMA in accordance with the provisions set out GSMA AA.35-Procedures for Industry Specifications. GSMANon-confidentialOfficial DocumentOPG.02-Operator Platform: Requirements and Architecture Table of Contents 1Introduction 1.1Overview51.1.1Relationship to existing standards51.2Scope and objectives51.3Definitions61.4Abbreviations121.5References141.6Conventions15 2High-Level Architectural Requirements 15 2.1General152.2Functionality offered to OP Ecosystem Party162.2.1Functionality offered to Application Providers162.2.2Functionality offered to Aggregators162.2.3Functionality offered to End-Users/Devices172.2.4Functionality offered to Operators182.2.5Functionality offered to other OPs192.3Exposure requirements192.3.1High-Level requirements192.3.2Capability Management requirements202.3.3Privacy Requirements222.3.4Mobility Requirements232.4High-Level Security Requirements24 3OP Architecture and interfaces 3.1Architecture3.2Interfaces3.3Functional Levels and Components3.3.1General3.3.2Common Functions3.3.3Exposure Functions3.3.4Federation Functions3.3.5Transformation Functions3.3.6Integration Functions 4.1Northbound Interface (NBI)4.1.1High-level requirements4.1.2Onboarding Profile4.1.3Management Profile4.1.4Void4.1.5Security Requirements4.2East/Westbound Interface4.2.1High-level requirements4.2.2E/WBI Services GSMANon-confidentialOfficial DocumentOPG.02-Operator Platform: Requirements and Architecture 4.2.3Security Requirements4.3Southbound Interface4.3.1SBI-CR4.3.2SBI-NR4.3.3SBI-CHF4.3.4SBI-EIN4.3.5SBI-OAM4.3.6SBI-AAPrM4.4User to Network Interface 444444454958585861 5Detailed Requirements on functional elements61 F.1General84F.2Requirements for supporting relevant End-User rights85 GSMANon-confidentialOfficial DocumentOPG.02-Operator Platform: Requirements and Architecture AnnexGService Flows92G.1Service delivery by the OP (without UNI)92G.1.1Service delivery to UE attached to the Home Network92G.1.2Service delivery to UE attached to a Visited Network93G.2Charging Concepts95G.2.1Charging for Service API Invocation95G.2.2Charging for Data Traffic Usage in Operator Network97G.2.3Charging for Edge Enabling Infrastructure Resource Usage99G.3Charging Concepts in Federated Scenarios99G.3.1Federated Service API Invocation100G.3.2Federated Edge Enabling Infrastructure Resource Usage101G.4Privacy Management103G.4.1Consent capture: use cases and flows103G.4.2Relevant information103G.5Vetting Process105G.5.1High-level flow for Vetting process105G.5.2Relevant information111AnnexHDocument Management113 H.1Document History113H.2Other Information113 1Introduction 1.1Overview Operators in the 5G era have a significant opportunity to monetise the capabilities of theirnetworks. Moreover, with the existing relationships that Operators have with enterprises,their vast local footprint, their ability to support digital sovereigntyprinciples and theircompetence to provide high-reliability services, the missing piece is the ability to packageand expose their networks in a scalable fashion across multiple Operators. The OperatorPlatform (OP) concept, as introduced in this document,described the architecture of ageneric platform to fill this gap, identifyingtechnical requirements, functional blocks andinterface characteristics. 1.1.1Relationship to existing standards 1.1.1.13GPP Unless otherwise stated, the requirements listed in this document are based on the openand published 3GPP specifications listed in Section1.5. 3GPP Release 17 is taken as thebasis. 1.2Scope and objectives This document covers requirements and architecture specifications that guide the entireindustry ecosystem to define a common solution for exposing network capabilities and edgecompute resources, referred to as Operator Platform. The ecosystem includes Operato