5G Edge Application Context Transfer via Direct EAS Links
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G edge architecture defined in 3GPP TS23.558 inefficiently transfers application context data through multiple hubs, which can be burdensome for large data transfers.
Innovation Solution
Directly exchange connection information between source and target edge application servers using edge enabler servers, allowing the actual data transfer to occur directly between these servers, using a RESTFUL resource with HTTP methods for efficient data exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application context data is transferred through multiple hubs in the 5G edge architecture, then the transfer follows the standard architecture protocol, but the transfer efficiency decreases and overhead increases for large data transfers
Solution Approach 1:
The patent uses edge enabler servers as intermediary entities to facilitate direct peer-to-peer data transfer between source and target edge application servers. The intermediaries (edge enabler servers) enable the bypass of multiple hubs by establishing direct connections while maintaining architecture compliance through standardized interface protocols.
Solution Approach 2:
The patent segments the data transfer process into two distinct phases: (1) control plane signaling through edge enabler servers to exchange connection information, and (2) data plane direct transfer between edge application servers. This segmentation allows the system to maintain architectural compliance for control functions while optimizing data transfer efficiency through direct peer-to-peer connections.
2Reliability
If application context data is transferred through multiple hubs, then the transfer follows the defined architecture, but the transfer time increases for large data sets
Solution Approach 1:
The patent performs preliminary actions by having the source edge application server send connection information to the target server through edge enabler servers before the actual data transfer begins. This preliminary exchange of connection information (IP addresses, ports, etc.) enables the subsequent direct data transfer to occur without routing delays, significantly reducing transfer time while maintaining architecture compliance.
3Productivity
If direct connection information is exchanged between source and target edge application servers, then data transfer efficiency improves, but the complexity of the transfer mechanism increases
Solution Approach 1:
The patent leverages the existing multi-functional edge enabler servers to handle both control plane functions (exchanging connection information) and facilitate data plane functions (enabling direct transfer). By reusing existing network entities for multiple purposes, the patent avoids introducing dedicated new components, thereby managing complexity while achieving efficient direct transfer.
4Productivity
If direct data transfer is implemented between edge application servers, then overhead is reduced, but the need for intermediate coordination increases
Solution Approach 1:
The patent extracts the data transfer function from the hub-based routing path and creates a separate direct transfer channel between edge application servers. By taking out the data plane from the traditional hubbed path while keeping the control plane through edge enabler servers, the system reduces transfer overhead for large data sets while maintaining necessary coordination through the extracted control functions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
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.