SEALDD Server Relocation for Seamless Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network technologies face challenges in ensuring seamless service continuity during application server relocation due to UE mobility and load balancing, leading to service disruptions and loss of transport layer connections.
Innovation Solution
Implementing a Service Enabler Architecture Layer Data Delivery (SEALDD) server to manage transport layer connections, ensuring seamless relocation and lossless data delivery by maintaining connections between source and target application servers, even in scenarios where real-time transport layer relocation is not supported.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application server relocation is performed during UE mobility or load balancing, then service continuity is improved, but transport layer connection stability deteriorates causing service interrupts
Solution Approach 1:
The patent introduces an intermediary mechanism at the application layer that maintains the transport layer connection while enabling server relocation. The source application server continues to hold the transport layer connection, acting as a mediator that forwards data through the target application server, thus preventing connection disruption during relocation.
Solution Approach 2:
The patent performs preliminary context and data transfer from the source application server to the target application server before the actual relocation is completed. This preliminary action ensures that the target server is ready to take over seamlessly, minimizing service interruption while maintaining connection stability.
2Adaptability or versatility
If real-time transport layer relocation is not supported, then device compatibility is improved, but service continuity deteriorates due to connection re-establishment requirements
Solution Approach 1:
The patent uses the application layer as an intermediary that compensates for the lack of transport layer relocation support. By implementing context transfer and data forwarding at the application layer, the system achieves seamless relocation functionality without requiring changes to the transport layer, thus maintaining compatibility while ensuring service continuity.
Solution Approach 2:
The patent segments the relocation process into distinct phases: context information transfer, data transfer, and connection maintenance. This segmentation allows each phase to be handled independently at the application layer, enabling relocation support without modifying the transport layer protocol.
3Reliability
If application layer context transfer is implemented, then service continuity is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal context transfer mechanism that can be applied to different application servers and scenarios. The same application layer procedures are used for both UE mobility and load balancing cases, reducing the need for scenario-specific complexity while maintaining service continuity across diverse situations.
Data Source
AI summary
Embodiments of the present disclosure provide method and apparatus for service continuity. A method performed by a first service enabler server comprises receiving context information of a second service enabler server from the second service enabler server. The method further comprises storing the context information of the second service enabler server. The method further comprises sending endpoint information of the first service enabler server to a service enabler client and/or initiating a traffic influence procedure with a network to request replacement of endpoint information of the second service enabler server with the endpoint information of the first service enabler server.