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.
# 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 ME App that can execute in different MEC platforms with different localities.
* As a MEC Sandbox User, I have an MEC App that can execute in different MEC platforms with different localities within the Sandbox emulated edge network.
*`mep1` locality is Zone 1 & 2
*`mep2` locality is Zone 3 & 4
* ME App can register in one of the MEC platform to discover available MEC services
* ME App learns that
* MEC App can register in one of the MEC platform to discover available MEC services available via the local MEP
* MEC App learns that
* 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
* total of 1 instance of each; available in all zones
* ME App uses the discovered services
* MEC App uses the discovered services
*See [user interface wireframes](../Sandbox-User-Interface#mec-sandbox-wireframe) for frontend details*