MPTCP Sub-Flow Mobility for Reliable Mobile Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems struggle to maintain ultra-reliable and low latency connections (URLLC) for devices in motion, particularly in 5G networks, as they face challenges in managing mobility and connectivity during handovers.
Innovation Solution
Implementing a method for Multi-Path Transmission Control Protocol (MPTCP) with enhanced capabilities to manage mobility and maintain connections by using modified sub-flow priority options, join connection protocols, and network address translation for pre-allocated sub-flows, ensuring seamless handovers and efficient resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional TCP protocols are used for mobile devices, then connection establishment is simple, but connection reliability deteriorates during handovers and mobility events
Solution Approach 1:
The patent segments the TCP connection into multiple independent sub-flows, each traversing different network paths. This allows individual sub-flows to be established and maintained independently, improving connection reliability during handovers while keeping each sub-flow's management relatively simple.
Solution Approach 2:
The patent establishes multiple sub-flows in advance before mobility events occur. By pre-configuring alternative paths and sub-flows, the system prepares for potential handovers proactively, ensuring connection reliability without adding complex real-time decision-making during mobility events.
2Reliability
If multiple sub-flows are established for mobility support, then connection reliability improves, but latency increases due to additional protocol overhead
Solution Approach 1:
The patent merges multiple sub-flows at the MPTCP layer to present a single unified connection interface to the application. This consolidation allows the benefits of multiple redundant paths while minimizing protocol overhead by handling sub-flow management at a lower layer, thus reducing latency impact.
Solution Approach 2:
The MPTCP protocol acts as an intermediary layer between the application and individual TCP sub-flows. It manages the complexity of multiple sub-flows transparently, allowing applications to use simple TCP-like interfaces while benefiting from the reliability of multiple paths without the full latency overhead of managing each sub-flow separately.
3Stability of the object's composition
If MPTCP with pre-allocated sub-flows is implemented, then handover seamlessness improves, but resource allocation complexity increases
Solution Approach 1:
The patent pre-allocates sub-flow resources before mobility events occur. By establishing alternative paths and reserving resources in advance, the system ensures seamless handovers without requiring complex real-time resource allocation decisions during actual mobility events.
Solution Approach 2:
The MPTCP protocol automatically manages sub-flow allocation, establishment, and teardown based on network conditions and mobility events. This self-service mechanism reduces the burden on external resource management systems by handling resource allocation internally through standardized MPTCP procedures.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A client application running on a WTRU is configured to communicate data traffic over a TCP session with an MPTCP stack running on the WTRU. The data traffic is exchanged with a server application over a first MPTCP sub-flow with a first mobile edge (ME) host device. The WTRU is anchored to a second ME anchor node. The WTRU receives a first message from a second ME host device indicating that the WTRU should join a second MPTCP sub-flow with the second ME host device. The WTRU joins the second MPTCP sub-flow, responsive to the first message, wherein the second sub-flow is configured not to exchange data traffic. The WTRU receives a second message from the second ME host device configuring the second MPTCP sub-flow to exchange data traffic. The WTRU exchanges the data traffic with the server application over the second MPTCP sub-flow with the second ME host device.