Commit 67dac88f authored by Mike Roy's avatar Mike Roy
Browse files

Update user-case5.md

parent b407df07

Macro-Network-Scenario/user-case5.md

+2 −4
Original line number Diff line number Diff line
@@ -12,16 +12,14 @@ Objective: 
      * 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 use the discovered services



>_Note: The dataset available from Location service varies depending on its locality - each instance has a dataset covering its own locality only_

  * ME App uses the discovered services



*See [user interface wireframes](../Sandbox-User-Interface#mec-sandbox-wireframe) for frontend details*



| Operation: | Notes: |

| ---------  | ------ |

| 1. Login via the frontend & select Sandbox tab |  |

| 2. Select the `dual-mec-nodes` network to deploy in the user sandbox | `dual-mec-nodes` scenario has `mep1` for Zone 1 & 2 locality and `mep2` for Zone 3 & 4 locality <br><br> Each node runs an instance of Location service with its own dataset; RNIS & WAIS are MEC system wide services.

| 2. Select the `dual-mep` network to deploy in the user sandbox | `dual-mep` scenario has `mep1` for Zone 1 & 2 locality and `mep2` for Zone 3 & 4 locality <br><br> Each node runs an instance of Location service with its own dataset; RNIS & WAIS are MEC system wide services.

| 3a. Pre-configure ME Application with Application Enablement service endpoints | Endpoints: <li>`https://try-mec.etsi.org/<my-sandbox-key>/mec_app_support/v1`<li>`https://try-mec.etsi.org/<my-sandbox-key>/mec_service_mgmt/v1` <br><br>_Note: for readability, endpoint URIs are replaced by `.../`_|

| 3b. Pre-configure ME 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 <br><br> Generating the `appInstanceId` asks for the locality of the ME App (e.g. `mep1` or `mep2`)|

| 4. Start ME App or environment |  ME App knows nothing about available MEC services <br><br> In the following steps, ME App will learn MEC available services via Mp1 interface |