...
| Use Case | API Call Sequence | EMCO Involvement |
|---|---|---|
| App Orchestrator registers a 'service profile' with VZ for application to be launched. | See Create-service-profile API. Service Profile will take in the resource needs of the application such as CPUs, memory, GPU needs & performance needs of the application such as latency. NOTE: CPUs are not mentioned in the API. Needs clarification. | EMCO will do this. EMCO's HPA intents provide only the |
Determine the 'best' MEC cluster | Task 1: Case A. The app provider only knows which region to deploy, but not the location of the clients. Query available regions with Get-Regions API and then the MEC clusters within those regions with Get-MEC-Platforms API. | Some agent, such as a workflow, could call these APIs and onboard the discovered clusters into EMCO. Also, EMCO intents, such as cluster labels and HPA, could be used to further narrow the candidate clusters. We need a way to get the cluster candidates returned by 5GFF APIs into EMCO DIG intents. |
Task 1: Case B. The app provider knows the location of their clients. Get list of Public MEC zones for those locations and desired UE density using Get-MEC-Platforms API. | ||
| Task 2: Launch app in the selected clusters. | EMCO will do this. | |
Task 3: Update the service registry with the service endpoints of each app instance. Invoke | EMCO will do this. | |
'Optimize' the application deployment, i.e., Edge Relocation. | (These are the tasks from the Architecture section above.) Task A: Measure application performance issues and/or listen for 5G user mobility. | A workflow will do this. |
| Task B: Determine whether to relocate the app. | A workflow will do this. | |
Task C1: Get a new list of suitable MEC clusters. Invoke Get-MEC-Platforms API with region name, service profile ID, subscriber density and/or UE identity. | A new EMCO controller will do this. | |
| Tasks C2, C3: Narrow the list of MEC cluster candidates using other criteria, and pick one target cluster. | EMCO controllers will do this. | |
Task D: Perform the relocation. After each operation (move, terminate, create new app instance), update the Service Registry using | A workflow will call EMCO to do this and then call the 5GFF APIs. | |
Discover the 'closest' app instance to a client/UE. | The app orchestrator can determine the closes MEC cluster for the client and tell the client which app instance to talk to. (Or the client can call the 5GFF APIs too.) Invoke Get-MEC-Platforms API with UE identity. The identity types can be IP Address, MSISDN, IMEI, MDN, or GPSI. | EMCO can do this. |
...