Seamless edge application handover
An edge application handover client in a user equipment may use application client information, such as type service, provider, location, context, and sendee requirements, to assist seamless edge application handovers of application clients between edge application servers. For example, a handover client may use context information to determine an anticipated route of the user equipment, and thereby determine a next, edge application server for a handoff. The handover client may weigh the needs of multiple application clients m selecting servers for handovers. The handover client may issue requests to servers requesting assistance in handover operations, and may issue subscription requests to servers, and further may determine the success of handovers by monitoring application state synchronization or migration between edge application handover servers.
1 . A user equipment, UE, hosting an Edge Application Handover Client, EAHC, the UE comprising a processor, a memory, and communication circuitry, the UE being connected to a first network via the communication circuitry, the UE further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the EAHC to:
receive, from an application client, AC a first request comprising AC context information, wherein the AC context information comprises, for a service from a first Edge Application Server, EAS, an expected location or an anticipated route of the UE where the service provided by the EAS will be required, and wherein the AC context information further comprises a schedule of times during which the service provided by the EAS will be required;
send, to an Edge Application Handover Server, EAHS, based on the AC context information, a second request comprising the AC context information; and
receive, from the EAHS, an acknowledgement of the second request.
2 . The UE of claim 1 , wherein the AC context information further comprises an identifier of the AC.
3 . The UE of claim 1 , wherein the AC context information further comprises a required rate of requests when accessing the first EAS.
4 . The UE of claim 1 , wherein the AC context information further comprises a current location of the AC.
5 . The UE of claim 1 , wherein the AC context information further comprises an identifier of the first EAS.
6 . The UE of claim 1 , wherein the AC context information further comprises a service continuity requirement.
7 . The UE of claim 6 , wherein the service continuity requirement comprises a service continuity mode.
8 . A network apparatus hosting an Edge Application Handover Server, EAHS, the apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a first network via the communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the EAHS to:
receive, from a first Edge Application Handover Client, EAHC, hosted on a first User Equipment, UE, a request comprising Application Client, AC, context information pertaining to an AC, wherein the AC context information comprises an expected location or an anticipated route for which a service provided by a first Edge Application Server, EAS, is required to be accessible by the AC, and wherein the AC context information further comprises a schedule comprising times when the AC requires access to the service provided by the EAS;
send, to the first EAHC, a response indicating the AC context information was received;
trigger, based on the schedule and the expected location or the anticipated route, a handover of the AC from the first EAS to a second EAS.
9 . The EAHS of claim 8 , wherein the instructions further cause the EAHS to:
support an interface to a 3GPP entity in a 3GPP system;
receive a current location of the first UE from the 3GPP entity;
determine, by comparing the current location of the first UE to the expected location or anticipated route, timing of when to trigger the handover of the AC from the first EAS to the second EAS.
10 . The EAHS of claim 8 , wherein the instructions further cause the EAHS to trigger the first EAHC, to perform edge application handover operations on behalf of an AC to assist the AC in performing an edge application handover.
11 . The EAHS of claim 8 , wherein the instructions further cause the EAHS to receive, from a second EAHC hosted on a second UE, a subscription request pertaining to receiving notifications from the EAHS.
12 . The EAHS of claim 11 , wherein the instructions further cause the EAHS to send, to second EAHC, a notification responsive the subscription request.
13 . The EAHS of claim 8 , wherein the instructions further cause the EAHS to support an interface to a management function and, via the interface, trigger the management function to instantiate the first EAS.
14 . The EAHS of claim 8 , wherein the instructions further cause the EAHS to:
send, to a 3GPP network, a request that the 3GPP network track movement of the first UE along the anticipated route; and
receive, from the 3GPP network, a notification regarding the movement of the first UE, the notification comprising either an indication of an arrival of the first UE within proximity of a way point along the anticipated route or an indication that the first UE has deviated from the anticipated route.