SEAL Data Delivery Flow Handover for UE Mobility Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 3GPP SEALDD systems lack support for real-time transport layer continuity during UE mobility, data transmission quality measurements, and data storage services, particularly for constrained devices that may be sleeping.
Innovation Solution
Implementing SEALDD flow management functionality that includes a SEALDD server and client to manage end-to-end flows, support data transmission quality measurements, and store data for sleeping devices, with features like message segmentation, caching, and redundant transport establishment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SEALDD systems use legacy 3GPP architecture with SEAL client and server grouped on UE and server respectively, then basic service enabler functionality is provided, but real-time transport layer continuity during UE mobility is not supported
Solution Approach 1:
The patent segments the SEALDD functionality into separate client and server components that can be independently managed and relocated. The SEALDD client on the UE and SEALDD server on the EAS can be independently configured and moved, enabling continuous service during mobility events by maintaining the logical connection while changing physical locations.
Solution Approach 2:
The patent introduces the SEALDD server as an intermediary component that manages the connection between the SEALDD client and the VAL server. This intermediary maintains the transport layer continuity by handling the handover process during UE mobility, ensuring that the VAL application layer experiences no disruption despite physical movement of the UE.
2Measurement precision
If SEALDD systems provide basic data delivery functionality, then simple data transmission is supported, but data transmission quality measurements and configuration capabilities are lacking
Solution Approach 1:
The patent implements multi-functionality in the SEALDD server and client, enabling them to perform both basic data delivery and quality measurement functions within the same architecture. The SEALDD server can simultaneously manage data transmission and collect quality metrics, while the SEALDD client can both send/receive data and configure measurement parameters, eliminating the need for separate measurement systems.
Solution Approach 2:
The patent establishes feedback mechanisms where the SEALDD server and client exchange quality measurement data and configuration information. The system collects transmission quality metrics, feeds them back to the application layer, and allows configuration adjustments based on measured performance, creating a closed-loop system that continuously optimizes data transmission quality.
3Duration of action of moving object
If SEALDD systems implement real-time data delivery, then immediate data transmission is achieved, but data storage service for sleeping constrained devices is not supported
Solution Approach 1:
The patent implements preliminary action by storing data in advance at the SEALDD server before the constrained device needs it. When a device is sleeping or unavailable, the data is prepared and held in the server's storage. Upon device awakening or availability, the pre-stored data is immediately delivered, combining advance preparation with efficient delivery without requiring the device to be continuously powered on.
Solution Approach 2:
The patent enables periodic data delivery patterns where data can be stored at the server and delivered at scheduled intervals or when specific conditions are met (such as device awakening). This periodic action allows the system to balance immediate delivery needs with energy conservation for constrained devices, delivering data periodically rather than requiring continuous real-time transmission.
Data Source
AI summary
A SEALDD server may receive a request to establish a SEALDD flow, wherein the SEALDD flow facilitates a transfer of VAL data between a VAL client endpoint and a first VAL server endpoint, and wherein the request comprises at least one of VAL client endpoint information and first VAL server endpoint information. The SEALDD server may establish a SEALDD flow associated with the first VAL server and associated with at least one VAL client endpoint. The SEALDD server may subscribe to a core network and receive a notification from the core network indicating a UE mobility event associated with a UE upon which the VAL client is hosted. The SEALDD server may determine to transfer the VAL client to a second VAL server. The SEALDD server may transfer the SEALDD flow to a different SEALDD server associated with the second VAL server.