MPQUIC over QSOCKS Protocol for Wireless Multipath Handover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current SOCKS protocol is not compatible with QUIC, leading to increased round-trip times (RTTs) for connection establishment, which affects user experience, especially for applications with short-lived connections, and lacks multipath capabilities to efficiently utilize multiple wireless interfaces in mobile devices.
Innovation Solution
The development of Multipath Quick User Datagram Protocol Internet Connections (MPQUIC) over Quick SOCKS (QSOCKS) enables zero-RTT connections and multipath capabilities, allowing for efficient stream multiplexing and authentication, reducing initial handshake overhead and enabling seamless handovers between different wireless interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If SOCKSv5 is used to proxy MPTCP, then server-agnostic routing is achieved, but connection establishment time increases by multiple RTTs
Solution Approach 1:
The patent performs SOCKS protocol negotiation and authentication in advance during the QUIC handshake process, so that when data transmission begins, the connection is already established. This preliminary action eliminates the need for separate SOCKS handshakes during data transfer, reducing connection establishment time while maintaining server-agnostic routing capability.
Solution Approach 2:
The patent merges the QUIC handshake process with the SOCKS protocol negotiation by integrating SOCKS authentication into the QUIC 0-RTT handshake. This combination allows both protocols to be completed simultaneously in a single connection establishment phase, eliminating multiple RTTs and achieving fast connection setup while preserving routing flexibility.
2Speed
If traditional QUIC is used, then low latency and encryption are achieved, but multipath capabilities are missing
Solution Approach 1:
The patent extends QUIC to provide multiple path management capabilities while maintaining its original low-latency and encrypted characteristics. The enhanced QUIC protocol can operate over a single path or aggregate multiple paths (Wi-Fi, LTE, 5G) depending on availability, making it universally applicable to various network scenarios without sacrificing performance.
Solution Approach 2:
The patent implements dynamic path selection and switching capabilities that allow the system to adaptively choose between different network interfaces based on real-time conditions. The multipath QUIC can dynamically add or remove paths during operation, enabling flexible adaptation to changing network availability while maintaining optimized latency performance.
3Productivity
If multiple wireless interfaces are combined, then bandwidth aggregation is achieved, but protocol complexity increases
Solution Approach 1:
The patent segments the data transmission into independent streams that can be distributed across multiple network interfaces. Each interface operates as a separate path with its own congestion control and loss recovery mechanisms, allowing straightforward aggregation of bandwidth from Wi-Fi, LTE, and 5G without requiring complex coordination between interfaces.
Solution Approach 2:
The patent implements self-managing multipath capabilities where the QUIC protocol automatically detects available network interfaces and assigns data streams to appropriate paths based on local conditions. The system performs autonomous path selection, failure detection, and load balancing without requiring complex external control or manual configuration, reducing overall system complexity.
Data Source
Figure 1~2
Figure 3A
Figure 3B
AI summary
A method for Multipath Quick User Datagram Protocol (UDP) Internet Connections (MPQUIC) over Quick SOCKS (QSOCKS) in a wireless network is provided. The method includes receiving, by a QSOCKS server, a Client Hello (CHLO) message from a QSOCKS client device using a QSOCKS method tag, wherein the CHLO message comprises a plurality of client-supported SOCKS Authentication (AUTH) procedures, selecting, by the QSOCKS server, a candidate client-supported SOCKS AUTH procedure from the plurality of client-supported SOCKS AUTH procedures, and transmitting, by the QSOCKS server, a reject packet using the QSKM tag to the QSOCKS client device, wherein the reject packet includes information indicating the selected candidate client-supported SOCKS AUTH procedure.