Commit e8cf6370 authored Jun 21, 2021 by Mike Roy

fix typos

parent 68c72e11

Macro-Network-Scenario/use-case3.md

+2 −2

Original line number	Diff line number	Diff line
		@@ -16,8 +16,8 @@ Objective:
		\| --------- \| ------ \|
		\| 1. Login via the frontend & select Sandbox tab \| \|
		\| 2. Select a network to deploy in the user sandbox \| \|
		\| 3a. Pre-configure MEC Applicationlication with Application Enablement service endpoints \| Endpoints: <br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_app_support/v1`<br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_service_mgmt/v1` \|
		\| 3b. Pre-configure MEC Applicationlication 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 \|
		\| 3a. Pre-configure MEC Application with Application Enablement service endpoints \| Endpoints: <br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_app_support/v1`<br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_service_mgmt/v1` \|
		\| 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 \|
		\| 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 services availability via Mp1 interface \|
		\| 5. `GET .../services` \| MEC Application discovers there are 3 services available (Location/RNIS/WAIS) with their respective URIs <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> MEC Application stores the returned subscription id for future subscription management

Macro-Network-Scenario/use-case4.md

+2 −2

Original line number	Diff line number	Diff line
		@@ -15,8 +15,8 @@ Objective:
		\| --------- \| ------ \|
		\| 1. Login via the frontend & select Sandbox tab \| \|
		\| 2. Select a network to deploy in the user sandbox \| \|
		\| 3a. Pre-configure MEC Applicationlication with Application Enablement service endpoints \| Endpoints: <br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_app_support/v1`<br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_service_mgmt/v1` \|
		\| 3b. Pre-configure MEC Applicationlication 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 \|
		\| 3a. Pre-configure MEC Application with Application Enablement service endpoints \| Endpoints: <br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_app_support/v1`<br>- `https://try-mec.etsi.org/<my-sandbox-key>/mec_service_mgmt/v1` \|
		\| 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 \|
		\| 4. Start MEC Application or environment \| In the following steps, MEC Application will register a service via Mp1 interface \|
		\| 5. `POST .../applications/{appInstanceId}/confirm_ready` \| MEC Application indicates readiness to the MEC platform \|
		\| 6. `POST .../applications/{appInstanceId}/services` \| MEC Application creates its service resource on the MEC platform \|