WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
This section describes a use case that the user can accomplish using the MEC Sandbox APIs from a MEC application
Objective:
* As a MEC Sandbox User, I have an MEC Application that does not have any prior knowledge or configuration information of the Sandbox Macro Network.
* As a MEC Sandbox User, I have a MEC Application that does not have any prior knowledge or configuration information of the Sandbox Macro Network.
* MEC Application learns the layout of the network: zones, access points, terminals, etc.
* MEC Application can select a terminal of interest and start tracking its location via both queries and notifications: connected zone, connected access point, and geo-location.
This section describes a use case that the user can accomplish using the MEC Sandbox browser client
Objective:
* Sandbox User can learn about MEC Service APIs without having to build an MEC Application or specialized environment external to the Sandbox, exploring the APIs in a friendly manner such as Swagger.
* Sandbox User can learn about MEC Service APIs without having to build a MEC Application or specialized environment external to the Sandbox, exploring the APIs in a friendly manner such as Swagger.
* All API returned data is consistent with the External MEC Client endpoints.
* They can both be called simultaneously.
* Try both queries and subscriptions / notifications.
This section describes a use case that the user can accomplish using the MEC Sandbox APIs from a MEC application
Objective:
* As a MEC Sandbox User, I have an MEC Application that does not have any prior knowledge or configuration information of the MEC services offered by the MEC platform.
* As a MEC Sandbox User, I have a MEC Application that does not have any prior knowledge or configuration information of the MEC services offered by the MEC platform.
* MEC Application learns which services are available
* MEC Application starts using the MEC service
* MEC Application subscribes to changes in MEC service state
# Use case for MEC application using "scope of locality"
# Use case for MEC application using "scope of locality" - multiple MEC platform or host locations within the MEC Sandbox
This section describes a use case that the user can accomplish using the MEC Sandbox APIs from a MEC application
Objective:
* As a MEC Sandbox User, I have an MEC Application that can execute in different MEC platforms with different localities.
*`mep1` locality is Zone 1,2,3
*`mep2` locality is Zone 4
* MEC Application can register in one of the MEC platform to discover available MEC services
* MEC Application learns that
* As a MEC Sandbox User, I have a MEC Application that can execute in different MEC platforms with different localities within the Sandbox emulated edge network.
* Location service is available at the _ZONE_GROUP_ level
* total of 2 instances; 1 instance per MEC platform
* RNIS, WAIS are available at the _MEC_SYSTEM_ level
