操作员平台：要求和架构版本9.0

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 ©2025GSM 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 theaccuracy 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.4Abbreviations101.5References121.6Conventions13 2High-Level Architectural Requirements 13 2.1General142.2Functionality offered to OP Ecosystem Party142.2.1Functionality offered to Application Providers142.2.2Functionality offered to Aggregators152.2.3Functionality offered to End-Users/Devices152.2.4Functionality offered to Operators162.2.5Functionality offered to other OPs172.3Exposure requirements172.3.1High-Level requirements172.3.2Capability Management requirements182.3.3Privacy Requirements202.3.4Mobility Requirements212.4High-Level Security Requirements22 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 Functions3.3.7Federation Management3.3.8Routing of Requests 4.1Northbound Interface (NBI)4.1.1High-level requirements4.1.2Onboarding Profile4.1.3Management Profile4.1.4General Onboarding Workflow4.1.5Security Requirements4.2East/Westbound Interface GSMANon-confidentialOfficial DocumentOPG.02-Operator Platform: Requirements and Architecture 4.2.1High-levelrequirements384.2.2E/WBI Services384.2.3Security Requirements404.3Southbound Interface414.3.1SBI-CR414.3.2SBI-NR414.3.3SBI-CHF454.3.4SBI-EIN554.3.5SBI-OAM554.3.6SBI-PrM554.4User to Network Interface585Detailed Requirements on functional elements585.1.1Exposure Functions585.1.2Federation Functions595.1.3Transformation Functions615.1.4Integration Functions615.1.5User Client71AnnexADeployment Scenario72A.1Relationship with OP and Operator72A.2Relationship with hyperscalers from a single Operator perspective72AnnexBAggregation / Marketplace Platform73AnnexCOperator Platform Security74C.1Guidance for the implementation, deployment and operation74AnnexD5G Core Network Application Session Continuity Enabler Services75AnnexEService and capability exposure charging concepts77E.1Network capabilities exposure services: with no impact on device’s datausage77E.2Network capabilities exposure services: with impact on device’s data usage79E.3Network provisioning services80E.4Edge Application management services81E.5Charging factors summary82AnnexFPrivacy Management considerations84F.1General84F.2Requirements for supporting relevant end user rights85AnnexGService Flows86G.1Service delivery by the OP (without UNI)86G.1.1Service delivery to UE attached to the Home Network86G.1.2Service delivery to UE attached to a Visited Network88G.2Charging Concepts89G.2.1Charging for Service API Invocation90G.2.2Charging for Data Traffic Usage in Operator Network91G.2.3Charging for Edge Enabling Infrastructure Resource Usage93G.3Charging Concepts in Federated Scenarios93G.3.1Federated Service API Invocation94 GSMANon-confidentialOfficial DocumentOPG.02-Operator Platform: Requirements and Architecture G.3.2Federated Edge Enabling Infrastructure Resource Usage96G.4Privacy Management97G.4.1Explicit end useropt-in97G.4.2Consent Capture in federated environments99 H.1Document History101H.2Other Information101 1Introduction 1.1Overview Operators in the 5G era have a significant opportunity to monetise the capabilities of theirnetworks.Moreover, withthe existing relationshipsthat Operatorshavewith enterprises,theirvast local footprint, theirability to supportdigital sovereignty principles and theircompetence to provide high-reliability services, the missing piece is the ability to packageand expose their networks in a scalable fashion a