---

4.2.8 UE application interface

版权声明: 转载请注明出处 http://www.codingsoho.com/

In the MEC reference architecture there is one additional reference point of interest that has not been addressed in the previous sections of this white paper. The Mx2 reference point is between the device application and the User Application Lifecycle Management proxy. ETSI ISG MEC has defined a UE Application API over Mx2 reference point in [9]. This API allows the device application to request certain application lifecycle management actions in the MEC system, such as requesting a list of available MEC applications, and instantiation and termination of a new MEC application. Similarly, the API allows the device application to receive notifications of the change of the MEC application’s IP address. The MEC applications that have been instantiated in a MEC host in response to a request of a user via a device application are referred to as user applications. In the context of this white paper, the assumption is that the deployment of the user application lifecycle management proxy does not directly impact the rest of the MEC system integration into the 5G system architecture, and any procedures resulting from requests over UE Application API get routed by the Operations Support System (OSS) towards the MEC system level management.

Figure 7. UE application API over Mx2 reference point

For MEC application mobility the UE Application API may be used to assist the MEC system in application/context relocation, as well as in application relocation between different MEC systems or between the MEC system and another cloud system. All these considerations are work in progress in ETSI ISG MEC.