MP-TCP Proxy Tunneling for WAN Path Diversity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In SD-WAN scenarios, traditional MP-TCP proxies prevent clients from utilizing path diversity across multiple WAN links due to blocked MP-TCP information, limiting network performance and resiliency.
Innovation Solution
The MP-TCP proxy encapsulates the client's MP-TCP option header into its own session, allowing the proxy to carry and manage MP-TCP information across multiple subflows, enabling clients to exploit local and WAN path diversity while maintaining network integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional MP-TCP proxies are used to manage multiple WAN links, then network security and traffic management are improved, but path diversity utilization is blocked and network performance is limited
Solution Approach 1:
The patent implements nesting by encapsulating the client's MP-TCP option header within the proxy's own MP-TCP session. The proxy maintains an internal representation of the client's MP-TCP state nested within its session context, allowing the proxy to forward MP-TCP information to multiple subflows while preserving the original client-session association. This enables path diversity exploitation without breaking the proxy's security management function.
Solution Approach 2:
The patent uses the MP-TCP proxy as an intermediary that mediates between the client and multiple subflows. The proxy receives MP-TCP information from the client, processes it through its own session context, and then distributes appropriate information to multiple subflows. This intermediary role allows the proxy to maintain security control while enabling path diversity, resolving the contradiction between security management and performance optimization.
2Ease of operation
If MP-TCP information is blocked at the proxy for security management, then network control is improved, but resiliency and connectivity are reduced
Solution Approach 1:
The patent segments the MP-TCP information handling into distinct components: the client's original MP-TCP option header is separated and encapsulated within the proxy's session, while the proxy simultaneously manages its own MP-TCP state. This segmentation allows the proxy to maintain control over the overall connection while enabling individual subflows to carry necessary MP-TCP information for resiliency and failover capabilities.
Solution Approach 2:
By nesting the client's MP-TCP information within the proxy's session context, the system preserves the hierarchical control structure. The proxy maintains ultimate control (ease of operation) by managing the outer session layer, while the nested inner layer carries the client's original MP-TCP state information needed for resiliency and path management. This nested structure resolves the contradiction between control and reliability.
3Device complexity
If a single WAN link is used for simplicity, then device complexity is reduced, but network performance and path diversity are limited
Solution Approach 1:
The patent enables self-service by allowing the client's MP-TCP information to automatically propagate through the proxy's session to multiple subflows without requiring manual configuration. The proxy automatically manages the encapsulation and distribution of MP-TCP options, and the system self-adapts to utilize available paths based on the embedded client state. This reduces configuration complexity while enabling multi-path transmission for improved performance.
Data Source
AI summary
Various aspects of the subject technology relate to methods, systems, and machine-readable media for multi-path transmission control protocol (MP-TCP) proxy tunneling. The method includes reading a first multi-path transmission control protocol (MP-TCP) information from at least one first MP-TCP header, the at least one first MP-TCP header included in a first MP-TCP subflow, the first MP-TCP subflow included in a first MP-TCP session. The method also includes encapsulating the first MP-TCP information in a second MP-TCP session, the second MP-TCP session different from the first MP-TCP session. The method also includes sending the first MP-TCP information through the second MP-TCP session.