Method for application context transfer between edge servers in 5G networks
A method of transferring application context over a fifth-generation (5G) edge network, including: receiving, by a source edge enabler server (EES) from a source edge application server (EAS), a request to exchange application context data with a target EAS, wherein the application context data relates to an application which is to be transferred from the source EAS to the target EAS; transmitting the request from the source EES to a target EES; receiving, by the source EES from the target EES, a response including connection information for transferring the application context data; and transmitting the response to the source EAS, wherein the application context data is exchanged directly between the source EAS and the target EAS based on the connection information.
1 . A method of transferring application context with a fifth- generation (5G) edge network, the method being performed by at least one processor and comprising:
receiving, by a source edge enabler server (S-EES) from a source edge application server (S-EAS), a request to exchange application context data with a target EAS (T-EAS); and application context data relates to an application which is to be transferred from the S-EAS to the T-EAS;
transmitting the request from the S-EES to a T-EES;
receiving, by the S-EES from the T-EES, a response including information for transferring the application context data;
transmitting the response to the source EAS; and
exchanging the application context data directly from the S-EAS and to the T-EAS, the .
2 . The method of claim 1 , wherein exchanging the application context data is based on the connection information.
3 . The method of claim 2 , wherein the request and the response are transmitted using the 5G edge network, and
wherein the application context data is not exchanged over the 5G edge network.
4 . The method of claim 2 , wherein the request is transmitted from the S-EES to the T-EES using an EDGE interface, and
wherein the response is transmitted from the T-EES to the S-EES using the EDGE interface.
5 . The method of claim 2 , wherein the request includes at least one from among a source address for a storage corresponding to the application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the S-EAS, an expiration time associated with the request, and security information associated with the request.
6 . The method of claim 2 , wherein the connection information includes at least one from among a target address for a storage corresponding to the application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the T-EAS, an expiration time associated with at least one of the request and the response, and security information associated with the at least one of the request and the response.
7 . The method of claim 2 , wherein at least one of the request and the response includes a scheme identifier which is used to signal a scheme corresponding to the application context data.
8 . The method of claim 2 , wherein the connection information is stored in a RESTFUL resource, and
wherein the RESTFUL resource includes hypertext transfer protocol (HTTP) information for exchanging the application context data,
wherein the RESTFUL resource further includes URL information, authentication information, encryption/decryption information, an expiration time, a capture time of the application context, and an ID of the application context.
9 . A device for transferring application context with a fifth-generation (5G) edge network, the device comprising:
at least one memory configured to store program code; and
at least one processor configured to read the program code and operate as instructed by the program code, the program code including:
first receiving code configured to cause the at least one processor to receive, by a source edge enabler server (S-EES) from a source edge application server (S-EAS), a request to exchange application context data with a target EAS (T-EAS)), the application context data relates to an application which is to be transferred from the S-EAS to the T-EAS;
first transmitting code configured to cause the at least one processor to transmit the request from the S-EES to a T-EES;
second receiving code configured to cause the at least one processor to receive, by the S-EES from the T-EES, a response including connection information for transferring the application context data; and
second transmitting code configured to cause the at least one processor to transmit the response to the S-EAS;
exchanging code configured to cause the at least one processor to exchange the application context data directly from the S-EAS and to the T-EAS.
10 . The device of claim 9 , wherein exchanging the application context data is based on the connection information.
11 . The device of claim 10 , wherein the request and the response are transmitted using the 5G edge network, and
wherein the application context data is not exchanged over the 5G edge network.
12 . The device of claim 10 , wherein the request is transmitted from the S-EES to the T-EES using an EDGE interface, and
wherein the response is transmitted from the T-EES to the S-EES using the EDGE interface.
13 . The device of claim 10 , wherein the request includes at least one from among a source address for a storage corresponding to the application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the S-EAS, an expiration time associated with the request, and security information associated with the request.
14 . The device of claim 10 , wherein the connection information includes at least one from among a target address for a storage corresponding to the application context data, an application context identifier corresponding to the application context data, at least one protocol supported by the T-EAS, an expiration time associated with at least one of the request and the response, and security information associated with the at least one of the request and the response.
15 . The device of claim 10 ,
wherein at least one of the request and the response includes a scheme identifier which is used to signal a scheme corresponding to the application context data, wherein the connection information is stored in a RESTFUL resource, and
wherein the RESTFUL resource includes hypertext transfer protocol (HTTP) information for exchanging the application context data.
16 . A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a device for transferring application context with a fifth-generation (5G) edge network, cause the one or more processors to:
receive, by a source edge enabler server (S-EES) from a source edge application server (S-EAS), a request to exchange application context data with a target EAS (T-EAS), wherein the application context data relates to an application which is to be transferred from the S-EAS to the T-EAS, the application context data relates to an application which is to be transferred from the S-EAS to the T-EAS;
transmit the request from the S-EES to a T-EES;
receive, by the S-EES from the T-EES, a response including information for transferring the application context data;
transmit the response to the source EAS; and
exchange the application context data directly from the S-EAS and to the T-EAS.