The GSMA Operator Platform Group (OPG) has released an updated collection of specifications. The updates to these documents encompass requirements and architectural guidelines capturing consent and for managing privacy for cases where the subscriber is roaming and/or the Operator Platform’s (OP) federation capabilities are used. Next to that, they also bring requirements and architectural enhancements for exposing the capabilities exposed through the OP to AI applications and for using AI to deliver part of the Operator Platform functionality itself. Furthermore terminology has been aligned across the different specifications. They also bring enhancements to the OP’s East/Westbound interface clarifying how to identify the Partner OPs on that interface and how TLS would be used. Also guidance on the realisation of that interface using Kubernetes Operators has been provided.
For the realisation of Open Gateway, updated guidance has been provided on the adoption of updates to the Service and Operate APIs and the handling of API requests in roaming. Also guidance on upfront and delegated consent capture has been included as well as guidance on the alignment of QoS profiles and on the realisation of the vetting process of Applications and Application Providers. Also improved guidance on the realisation of the Operate APIs has been provided, including the optionality of the use of hub functionality and initial guidance on the TM Forum APIs for product catalogue exposure and product usage data.
Finally, also for the use of the Operator Platform to offer Edge Compute capabilities, there have been updates. These include guidance on when to use the OP’s East/Westbound interface for the interaction between networks and when the lower-level interconnection of for example the packet core networks is more appropriate. Also requirements on the Application-level interconnection between Edge Sites has been provided.