Edge Context Transfer for Continuous Application Server Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing edge application server switching processes result in temporary suspension or interruption of application services due to the failure of context relocation between edge enabler servers, affecting service continuity.
Innovation Solution
A context transfer method that includes subscribing to edge enabler server capability exposure information and coordinating the transfer of application and edge enabler client contexts to avoid re-execution of relocation procedures, ensuring seamless service continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new edge application server is selected to replace the current one, then service optimization is achieved, but application service suspension or interruption occurs
Solution Approach 1:
The system performs preliminary context transfer from the source EES to the target EES before the actual server switching occurs. This includes transferring application context and EEC context in advance, so that when the server replacement happens, the target server is already prepared with all necessary context information, thereby avoiding service interruption.
2Ease of operation
If context relocation is performed between edge enabler servers, then service transfer is enabled, but transfer duration increases
Solution Approach 1:
The system initiates context transfer operations in advance before the actual server switching is needed. The source EES starts transferring application context and EEC context to the target EES proactively, reducing the actual transfer duration when switching occurs.
Solution Approach 2:
The system maintains continuous context transfer operations throughout the server switching process. Instead of performing discrete transfer steps, the context transfer is ongoing and coordinated, ensuring that the service can be resumed immediately when switching occurs without waiting for complete transfer cycles.
3Reliability
If EEC context transfer fails, then relocation procedure must be re-executed, but service suspension duration increases
Solution Approach 1:
The system implements feedback mechanisms where the target EES notifies the source EES about the success or failure of context transfer. When transfer fails, the system receives failure notification and can take corrective actions such as retransmission or alternative procedures, preventing complete procedure re-execution and reducing service suspension time.
Solution Approach 2:
The system prepares compensatory measures in advance for potential transfer failures. This includes having fallback procedures ready and maintaining the ability to retransmit context information without complete procedure restart, cushioning against the impact of transfer failures on service continuity.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
This application provides a context transfer method and a communication apparatus. The method includes: When an edge enabler client context fails to be relocated from a second edge enabler server to a first edge enabler server, a first apparatus sends first information to a first edge application server corresponding to the first edge enabler server, where the first information is used by the first edge application server to subscribe to edge enabler server capability exposure information from the first edge enabler server. In the foregoing technical solution, when an edge enabler client context fails to be transferred, the first apparatus may indicate a target edge application server to subscribe to edge enabler server capability exposure information from a target edge enabler server, so that re-execution of an entire edge enabler client context relocation procedure can be avoided, and duration of suspension or interruption of an application service in an edge application server switching process can be reduced, thereby improving transfer continuity of the application service.