Edge Application Context Relocation for Mobile Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods fail to provide continuous service to mobile communication terminals when they move from one edge data network area to another, leading to service disruptions and network overhead due to the need for network function intervention.
Innovation Solution
A method and apparatus that utilize an edge enabler client (EEC) and source edge enabler server (S-EES) to detect the need for application context relocation, allowing direct negotiation with the 3GPP system for seamless service continuity without additional overhead, enabling rapid transfer of application data traffic to new edge application servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the terminal moves from one EDN area to another, then the terminal can maintain mobility freedom, but the service continuity is disrupted
Solution Approach 1:
The source EES proactively initiates application context relocation before the terminal completely leaves the current EDN area. The S-EES detects the terminal's movement status and triggers the relocation procedure in advance, ensuring that the target EAS is prepared to continue service without interruption when the terminal arrives in the new area.
Solution Approach 2:
The EES acts as an intermediary between the terminal and the EAS during EDN transitions. It manages the application context relocation process, coordinates with both source and target EAS, and ensures seamless service handover, allowing the terminal to move freely while maintaining continuous service through the mediator's coordination.
2Reliability
If network function intervention is used to maintain service continuity, then service can be continuously provided, but network overhead increases
Solution Approach 1:
The S-EES autonomously detects terminal movement and initiates application context relocation without requiring external network function intervention. The system performs self-service by automatically managing the relocation process, reducing the need for complex network-wide coordination and minimizing signaling overhead while maintaining service continuity.
Solution Approach 2:
The patent extracts the service continuity management function from the general network function and places it specifically at the EES level. This localized approach allows the S-EES to handle relocation independently, removing the burden of complex network-wide intervention and reducing overall network overhead while maintaining reliability.
3Productivity
If application context relocation is detected quickly, then service transfer is rapid, but detection complexity increases
Solution Approach 1:
The EES utilizes existing multi-functional mechanisms already present in the edge computing architecture, such as the EEC-EEC communication interface and existing context management capabilities. By leveraging these universal components, the system achieves rapid detection and initiation of application context relocation without requiring complex specialized detection mechanisms.
Solution Approach 2:
The EES employs feedback mechanisms where the EEC reports terminal status and location information to the EES. This continuous feedback loop enables the S-EES to quickly detect when relocation is needed based on simple threshold conditions (such as EDN area changes), achieving rapid detection with minimal complexity through straightforward feedback monitoring.
Data Source
Figure 1
Figure 2
Figure 3a
AI summary
A method performed by an edge enabler client (EEC) included in a user equipment (UE) in an edge computing system comprises: determining to request an application context relocation by detecting, by the EEC that the application context relocation is required for a predicted or expected UE location; determining a target edge enabler server (T-EES), by using T-EES information received from an edge data network (EDN) configuration server; transmitting, to a source edge enabler server (S-EES), an application context relocation request to start the application context relocation; receiving, from the S-EES, an application context relocation response, in response to the application context relocation request; and receiving, from the S-EES, an application context relocation notification of completion of the application context relocation.