This guide contains all the steps that need to be taken for introducing a MEC service as a new feature in the MEC Sandbox frontend and the AdvantEDGE backend.
@@ -73,11 +71,5 @@ In that case, there are some aspects that need to be taken into consideration wh
See [Service Upgradation Guide](./service-upgradation.md) for details on how to upgrade an existing MEC service.
## UE Application Creation
UE application are application running on a UE terminal. See [UE Scenarios](./ue-application-scenarios.md) for details on how to develop it.
## MEC Application Creation
MEC application are onboarded application on MEC platform (see MEC-016). See [UE Scenarios](./ue-application-scenarios.md) for details on how to develop it.
@@ -5,6 +5,13 @@ This section describes how MEC016, DAI operations within the MEC Sandbox.
Query endpoints and subscriptions that are not supported in the MEC Sandbox are noted in tables below.
|Supported | Endpoint | Notes: |
| --------| -------- | -------- |
| Yes | `/app_list` | To retrieve information on available application information |
| Yes | `/app_contexts` | To create a new application context. Upon success, the response contains entity body describing the created application context |
| Yes | `/app_contexts/{contextId}` | To update an existing apllication context |
| Tes | `/obtain_app_loc_availability` | To allow a device application to obtain information on locations available for instantiation of a specific user application in the MEC system |
| Yes | `/app_list` | To retrieve information on available application information |
| Yes | `/app_contexts` | To create a new application context. Upon success, the response contains entity body describing the created application context |
| Yes | `/app_contexts/{contextId}` | |
| No | `/obtain_app_loc_availability` | To allow a device application to obtain information on locations available for instantiation of a specific user application in the MEC system |
| [/app_list](https://forge.etsi.org/rep/mec/gs016-dev-app-api/-/blob/master/UEAppInterfaceApi.yaml#/app_list) | GET - Retrieve information about a list of onboerded MEC applications | As a MEC Sandbox user, I use this endpoint to list down all the bandwidth allocation resource allocation with/without using query parameters |
| [/app_contexts](https://forge.etsi.org/rep/mec/gs016-dev-app-api/-/blob/master/UEAppInterfaceApi.yaml#/app_contexts) | POST - Creation of a new application context | As a MEC Sandbox user, I use this endpoint to instanciate an onboarded MEC application |
| [/app_contexts/{contextId}](https://forge.etsi.org/rep/mec/gs016-dev-app-api/-/blob/master/UEAppInterfaceApi.yaml#/app_contexts/{contextId}) | PUT - Updating the callbackReference and/or appLocation of an existing application context <br><br> DELETE - Deletion of an existing application context | As a MEC Sandbox user, I use this endpoint to update the callback reference and/or application location constraints of an existing instance of an onboarded MEC application <br><br> As a MEC Sandbox user, I use this endpoint terminate an existing instance of an onboarded MEC application |
| [/obtain_app_loc_availability](https://forge.etsi.org/rep/mec/gs016-dev-app-api/-/blob/master/UEAppInterfaceApi.yaml#/obtain_app_loc_availability) | GET - Obtain the location constraints for a new application context | As a MEC Sandbox user, I use this endpoint to obtain the locations available for instantiation of a specific user application in the MEC system |
