OPG.02-要求和架构，版本10.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.4Abbreviations111.5References131.6Conventions14 2High-Level Architectural Requirements 14 2.1General142.2Functionality offered to OP Ecosystem Party152.2.1Functionality offered to Application Providers152.2.2Functionality offered to Aggregators162.2.3Functionality offered to End-Users/Devices162.2.4Functionality offered to Operators162.2.5Functionality offered to other OPs172.3Exposure requirements182.3.1High-Level requirements182.3.2Capability Management requirements192.3.3Privacy Requirements212.3.4Mobility Requirements222.4High-Level Security Requirements23 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.4General Onboarding Workflow4.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 Requirements414.3Southbound Interface414.3.1SBI-CR424.3.2SBI-NR424.3.3SBI-CHF464.3.4SBI-EIN554.3.5SBI-OAM564.3.6SBI-AAPrM564.4User to Network Interface595Detailed Requirements on functional elements595.1.1Exposure Functions595.1.2Federation Functions605.1.3Transformation Functions625.1.4Integration Functions625.1.5User Client72AnnexADeployment Scenario73A.1Relationship with OP and Operator73A.2Relationship with hyperscalers from a single Operator perspective73AnnexBAggregation / Marketplace Platform74AnnexCOperator Platform Security75C.1Guidance for the implementation, deployment andoperation75AnnexD5G Core Network Application Session Continuity Enabler Services76AnnexEService and capability exposure charging concepts78E.1Network capabilities exposure services: with no impact on device’s datausage79E.2Network capabilities exposure services: with impact on device’s data usage80E.3Network provisioning services81E.4Edge Application management services82E.5Charging factors summary83AnnexFPrivacy Management considerations85F.1General85F.2Requirements for supporting relevant End-User rights86F.3Considerations from the architecture perspective87AnnexGService 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 Network94G.2Charging Concepts95G.2.1Charging for Service API Invocation96G.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 Usage102 GSMANon-confidentialOfficial DocumentOPG.02-Operator Platform: Requirements and Architecture G.4Privacy Management103G.4.1Consent capture: use cases and flows103G.4.2Relevant information117 AnnexHDocument Management120H.1Document History120H.2Other Information120 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