Datasets:

GSMA
/

camara

Item	Details
Summary	As an application developer, I need to discover the optimal Edge Cloud Zones for deploying my application instances, ensuring my users get the best performance by connecting to edge resources with minimal latency. The Optimal Edge Discovery API allows me to find the Edge Cloud Zones that are closest to a specific device, providing information about their locations, capabilities, and network characteristics. This helps me make informed decisions about where to deploy my application instances to ensure optimal performance for users across different geographical areas.
Roles, Actors and Scope	Roles: API Consumer:Developer Actors: Application service providers, hyperscalers, application developers. Currently the API does not explicitly handle consent management (expects that the API consumer either owns the device subscriptions or has agreed to manage consent as a part of general Terms and Conditions) and hence end users are not included as Actors. As this changes, the actor list will be extended with end users. Scope: Discover optimal Edge Cloud Zones for specific devices Retrieve information about available Edge Cloud Zones and their capabilities Make informed decisions about application deployment locations
Pre-conditions	The preconditions are listed below: The API Consumer:BusinessManager and API Consumer:Administrator have been onboarded to the API Exposure Platform. The API Consumer:BusinessManager has successfully subscribed to the Optimal Edge Discovery product from the product catalog. The API Consumer:Administrator has onboarded the developer:User to the platform. The API Consumer either owns the device subscriptions or has agreed to the terms and conditions of the CSP for managing consent of subscription owners. The means to get the access token are known to the API Consumer:User to ensure secure access of the API.
Activities/Steps	Starts when: 1. The API consumer application makes a request to discover the optimal Edge Cloud Zones for a specific device, optionally providing filter parameters to narrow down the results. Ends when: 1. The API endpoint returns information about available Edge Cloud Zones ordered by their proximity to the device.
Post-conditions	1. The API consumer has information about optimal Edge Cloud Zones for deploying their application instances. 2. The API consumer can use this information to make decisions about application deployment or to register application endpoints in these zones.
Exceptions	Several exceptions might occur - Unauthorized: Not valid credentials (e.g. use of already expired access token). - Invalid input: Not valid input data to invoke operation (e.g. IP address format not as expected). - Invalid filter: The filter parameters provided are not valid or cannot be applied. - Not Found: No Edge Cloud Zones are available that match the specified criteria. - Identifier Not Found: The device identified in the request cannot be found in the network.