| 1. Login via the frontend & select Sandbox tab | _See [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#sbox01)_ |
| 1. Login via the frontend & select Sandbox tab | _See [frontend](../Sandbox-User-Interface#sbox01)_ |
| 2. Select the `dual-mep` network to deploy in the user sandbox | `dual-mep` scenario has `mep1` for Zone 1, 2 & 3 locality and `mep2` for Zone 4 locality <br><br> Each node runs an instance of Location service with its own dataset; RNIS & WAIS are MEC system wide services.
| 3b. Pre-configure MEC Application with an Application Instance ID (e.g. `appInstanceId`) | MEC Platform Manager (MEPM) usually assigns `appInstanceId` to running applications <br><br> To support external user applications, the `appInstanceId` has to be generated from the [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#SBox04)<br><br> Generating the `appInstanceId` asks for the locality of the MEC Application (e.g. `mep1` or `mep2`)|
| 3b. Pre-configure MEC Application with an Application Instance ID (e.g. `appInstanceId`) | MEC Platform Manager (MEPM) usually assigns `appInstanceId` to running applications <br><br> To support external user applications, the `appInstanceId` has to be generated from the [frontend](../Sandbox-User-Interface#sbox04)<br><br> Generating the `appInstanceId` asks for the locality of the MEC Application (e.g. `mep1` or `mep2`)|
| 4. Start MEC Application or environment | MEC Application knows nothing about available MEC services <br><br> In the following steps, MEC Application will learn MEC available services via Mp1 interface |
| 5. `GET .../services` | MEC Application discovers there are 3 services available (Location/RNIS/WAIS) with their respective URIs <br><br> Location service URI corresponds to the locality of the MEC Application<br><br> MEC Application starts using discovered Location service. |
| 6. `POST .../applications/{appInstanceId}/subscriptions` | MEC Application wants to learn about service availability changes for Location service <br><br> The subscription filter has `isLocal=true`, indicating same locality service events only <br><br> MEC Application stores the returned subscription id for future subscription management
| 7a. Disable Location (the one with same locality as MEC Application) from the frontend | _See [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#SBox04)_ <br><br> MEC Application is notified of Location service un-availability and stops using it |
| 7b. Disable Location (the one with different locality as MEC Application) from the frontend | _See [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#SBox04)_ <br><br> MEC Application is not notified of Location service un-availability |
| 8. Enable Location service (the one with same locality as MEC Application) from the frontend | _See [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#SBox04)_ <br><br> MEC Application is notified of Location service availability and starts using it
| 7a. Disable Location (the one with same locality as MEC Application) from the frontend | _See [frontend](../Sandbox-User-Interface#sbox04)_ <br><br> MEC Application is notified of Location service un-availability and stops using it |
| 7b. Disable Location (the one with different locality as MEC Application) from the frontend | _See [frontend](../Sandbox-User-Interface#sbox04)_ <br><br> MEC Application is not notified of Location service un-availability |
| 8. Enable Location service (the one with same locality as MEC Application) from the frontend | _See [frontend](../Sandbox-User-Interface#sbox04)_ <br><br> MEC Application is notified of Location service availability and starts using it