Virtual network state management in mobile edge computing
In an embodiment a method is provided for processing a computational task using a network node available on a network processing. The method including the network node performing the steps of processing a computational task, and transmitting at least one snapshot of state data related to the computational task to a UE associated with that computational task. The at least one snapshot of state data enables the UE to resume processing of the computational task from a snapshot point represented by the state data.
1. A method comprising:
transmitting, by a user equipment (UE) to a mobility management/session management entity, a mobile edge computing (MEC) session request message;
receiving, by the UE, a MEC session response message sent by the mobility management/session management entity, the MEC session response message including UE configuration information, the UE configuration comprising including an identifier of a MEC node assigned to the MEC session request and MEC hand-off trigger information;
transmitting, by the UE to the MEC node identified by the identifier included in the UE configuration information, a software image of an application to be executed as a network function at the MEC node and data associated with the application;
determining, by a UE, whether to send a hand-off request to the mobility management/session management entity based on the MEC hand-off trigger information and a location of the UE
transmitting, by a UE, the handoff request to the mobility management/session management entity in response to determining to send the hand-off request to the mobility management/session management entity based on the MEC hand-off trigger information and a location of the UE; and
receiving, by the UE, current state data sent by the MEC node, state data indicating a current state of the application being executed as a network function at the MEC node.
2. The method of claim 1 , further comprising:
continuing, by the UE, execution of the application from the current state using the state data.
3. The method of claim 2 , wherein the MEC hand-off trigger information includes an identifier of a new MEC node, and wherein the method further comprises, transmitting, by the UE to the mobility management/session management entity, a new MEC session request including the identifier of the new MEC node.
4. The method of claim 1 , further comprising transmitting, by the UE to the MEC node identified by the MEC node identification information, one or more of: binaries, libraries, pointers to binaries, and pointers to libraries associated with the application to be used by network function at the MEC node.
5. The method of claim 1 , wherein the data associated with the network function is transmitted as data flow comprising a plurality of data flow segments.
6. The method of claim 1 , wherein the MEC node is operated by a first MEC service provider and a second MEC node is operated by a second MEC service provider.
7. The method of claim 1 , wherein the state data includes at least one of a state chronology identifier and a state identifier.
8. The method of claim 1 , wherein the MEC session request includes estimated work load, required resources, and buffer size for the application.
9. The method of claim 1 , wherein the UE configuration information included in the MEC session response message further includes: at least one of: a tracking area list (TAL) that includes access points (APs) that are proximate to a current location of the UE, and tracking area update (TAU) periodic timer.
10. A user equipment (UE) comprising:
a processor;
a non-transitory memory storing computer-readable instructions which, when executed by the processor, cause the UE to:
transmit to a mobility management/session management entity, a mobile edge computing (MEC) session request message;
receive a MEC session response message sent by the mobility management/session management entity, the MEC session response message including UE configuration information, the UE configuration information comprising an identifier of a MEC node assigned to the MEC session request and MEC hand-off trigger information;
transmit to the MEC node identified by the identifier included in the UE configuration information, a software image of an application to be executed as a network function at the MEC node and data associated with the application;
determine whether to send a hand-off request to the mobility management/session management entity based on the MEC hand-off trigger information and a location of the UE
transmit the handoff request to the mobility management/session management entity in response to determining to send the hand-off request to the mobility management/session management entity based on the MEC hand-off trigger information and a location of the UE; and
receive current state data sent by the MEC node, state data indicating a current state of the application being executed as a network function at the MEC node.
11. The UE of claim 10 , wherein the memory stores further computer-readable instructions which, when executed by the processor, cause the UE to continue execution of the application from the current state using the state data.
12. The method of claim 11 , wherein the MEC hand-off trigger information includes an identifier of a new MEC node, and wherein the memory stores further computer-readable instructions which, when executed by the processor, cause the UE to transmit to the mobility management/session management entity, a new MEC session request including the identifier of the new MEC node.
13. The UE of claim 10 , wherein the memory stores further computer-readable instructions which, when executed by the processor, cause the UE to transmit to the MEC node identified by the MEC node identification information, one or more of: binaries, libraries, pointers to binaries, and pointers to libraries associated with the application to be used by network function at the MEC node.
14. The UE of claim 10 , wherein the data associated with the network function is transmitted as data flow comprising a plurality of data flow segments.
15. The UE of claim 10 , wherein the MEC node is operated by a first MEC service provider and a second MEC node is operated by a second MEC service provider.
16. The UE of claim 10 , wherein the state data includes at least one of a state chronology identifier and a state identifier.
17. The UE of claim 10 , wherein the MEC session request includes estimated work load, required resources, and buffer size for the application.
18. The UE of claim 10 , wherein the MEC session response message further comprises: at least one of: a tracking area list (TAL) that includes access points (APs) that are proximate to a current location of the UE, and tracking area update (TAU) periodic timer.