运营商平台：SBI 4.0版本中NBI API的实现

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. GSMAOfficial Document OPG.09–NBI APIs realisation in the SBI Table of Contents 1Introduction 1.1Overview1.2Scope1.3Definitions1.4Abbreviations1.5References1.6Conventions 555792Northbound CAMARA APIs Analysis102.1UE identification102.2Authorization and authentication102.3Generic error codes102.4CarrierBilling API112.4.1Description112.4.2SBI Realisation122.4.3Charging Aspects122.4.4Roaming (Home Routed scenario) Aspect122.4.5Federation Aspects122.5Device Location APIs122.5.1Location Retrieval API122.5.2Location Verification API152.5.3Device Geofencing API192.6Number Verification API232.6.1Description232.6.2SBI Realisation242.6.3Charging Aspects252.6.4Roaming (Home Routed scenario) Aspect252.6.5Federation Aspects252.6.6Error codes252.7QualityOnDemand API252.7.1Quality-On-Demand API252.7.2QoS Profiles API392.7.3QoD Provisioning API412.8Traffic Influence API412.8.1Description422.8.2SBI Realization442.8.3Charging Aspects482.8.4Roaming (Home Routed scenario) Aspect482.8.5Federation Aspects482.9KYC Match API482.9.1Description482.9.2SBI Realization492.9.3Charging Aspects492.9.4Roaming (Home Routed scenario) Aspect49 2.9.5Federation Aspects2.10KYC Fill-in API2.10.1Description2.10.2SBI Realization2.10.3Charging Aspects2.10.4Roaming (Home Routed scenario) Aspect2.10.5Federation Aspects2.11OTP SMS API2.11.1Description2.11.2SBI Realization2.11.3Charging Aspects2.11.4Roaming (Home Routed scenario) Aspect2.11.5Federation Aspects2.11.6Error codes2.12Device Status API2.12.1Device Reachability Status2.12.2Device Reachability Status Subscription API2.12.3Device Roaming Status Subscription API2.12.4Connected Network Type API2.12.5Connected Network Type Subscription API2.12.6Charging Aspects2.12.7Roaming (Home Routed scenario) Aspect2.12.8Federation Aspects2.13Edge Cloud Discovery APIs2.13.1Simple Edge Discovery API2.14Call Forwarding Signal API2.14.1Description2.14.2SBI Realization2.14.3Charging Aspects2.14.4Roaming (Home Routed scenario) Aspect2.14.5Federation Aspects2.15Connectivity Insights2.15.1Description2.15.2SBI Realisations2.15.3Charging Aspects2.15.4Roaming (Home Routed scenario) Aspect2.15.5Federation Aspects2.15.6Error codes2.16SIM Swap API2.16.1SIM Swap2.16.2SIM Swap Subscriptions2.16.3Charging Aspects2.16.4Roaming (Home Routed scenario) Aspect2.16.5Federation AspectsAnnexADocument Management 495050505151515252525353535354555959595960606060606767686868686869707676767678798083838384 GSMAOfficial Document OPG.09–NBI APIs realisation in the SBI A.1Document HistoryA.2Other Information 8484 1Introduction 1.1Overview The idea of this document is creating a baseline for the realisation of Service APIs at lowerlevels in the OParchitecture. This way partners and operators can use it as a referenceimplementation covering aspects such as charging, federation, gaps and recommendedenablers to fill those service gaps. 1.2Scope This document provides guidelines to operators on how Service APIs should beimplemented in the network identifying missing interfaces or enablers and aligning SDOsand the wider industry to the needs for service development. 1.3Definitions 1.4Abbreviations 1.5References 1.6Conventions “The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to beinterpreted as described in RFC 2119[1]and clarified by RFC8174[2], when, and onlywhen, they appear in all capitals, as shown here.” 2Northbound CAMARA APIs Analysis 2.1UE identification Different solutions needed by several CAMARA APIs for the API invoker to identify the UEare described by CAMARA Commonalities group in[3]. To identify the UE addressed by a CAMARA API, an application provider shou