MPTCP Proxy IP Address Conservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Multipath TCP (MPTCP) solutions face challenges in efficiently managing IP addresses, particularly for wireless devices with a single LTE PDN connection, as they require multiple IP addresses for optimal functionality, leading to scarcity and inefficiency.
Innovation Solution
A method utilizing a unique IP address for an MPTCP proxy to establish and manage multiple MPTCP subflows over different network paths, allowing data to be relayed between a wireless device and a server using a combination of MPTCP and TCP sessions, thereby conserving IP addresses and enabling multipath connections with a single IP address.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple IP addresses are assigned to wireless devices for MPTCP functionality, then MPTCP connection capability and network path diversity are improved, but IP address scarcity and resource inefficiency worsen
Solution Approach 1:
The patent introduces an MPTCP proxy as an intermediary entity that terminates MPTCP connections from wireless devices and establishes separate TCP connections to servers. The proxy maintains state information about multiple network paths and performs packet routing, enabling MPTCP functionality without requiring end devices to have multiple IP addresses. This mediator approach resolves the contradiction by providing MPTCP capability through infrastructure support rather than device-level IP address multiplication.
Solution Approach 2:
The MPTCP proxy is designed to handle multiple functions: it acts as an MPTCP endpoint for wireless devices, a TCP endpoint for servers, a packet router for different network paths, and a connection state manager. By consolidating these multiple functions into a single proxy entity, the system enables MPTCP functionality for multiple devices without requiring each device to have dedicated multiple IP addresses, thus improving IP address efficiency while maintaining versatility.
2Adaptability or versatility
If MPTCP proxy uses multiple IP addresses for different network paths, then multipath routing capability is improved, but device complexity and configuration requirements worsen
Solution Approach 1:
The patent employs parameter changes by dynamically adjusting routing decisions based on network conditions, connection state, and path characteristics. The proxy monitors parameters such as path availability, transmission quality, and congestion levels to make intelligent routing decisions. This dynamic parameter-based approach enables flexible multipath routing without requiring complex static configuration, resolving the contradiction between routing capability and configuration complexity.
3Device complexity
If MPTCP is deployed as an end-to-end protocol requiring both hosts to support it, then protocol simplicity is improved, but deployment compatibility worsens
Solution Approach 1:
The MPTCP proxy serves as a mediator that bridges MPTCP-capable devices and traditional TCP-only servers. The proxy terminates the MPTCP connection from the device side and establishes standard TCP connections to servers, effectively translating between MPTCP and TCP protocols. This intermediary approach maintains protocol simplicity on the device side while achieving broad deployment compatibility with existing TCP infrastructure, resolving the contradiction between implementation simplicity and deployment compatibility.
Data Source
AI summary
The present disclosure relates to methods and arrangements for multipath traffic aggregation using a multipath Transmission Control Protocol, MPTCP, proxy. A method of relaying data between an MPTCP capable wireless device and a server is performed in a multipath Transmission Control Protocol, MPTCP, proxy, configured with a unique Internet Protocol, IP, address. The comprises establishing (S33) an MPTCP session between the MPTCP proxy and the wireless device, the MPTCP session comprising a first MPTCP subflow mapped on a first network path for the wireless device using a default traffic flow tuple, and establishing (S35) a TCP session with the server. The method further comprises initiating (S37) a further MPTCP subflow in the MPTCP session between the MPTCP proxy and the wireless device based on a mapping of the further MPTCP subflow to a second network path for the wireless device using a filtering traffic flow tuple comprising the unique IP-address configured for the MPTCP proxy. Data is relayed (S39) between the wireless device and the server, wherein data between the MPTCP proxy and the wireless device is exchanged in the MPTCP session comprising the first MPTCP subflow on the first network path and the further MPTCP subflow on the second network path and wherein data between the MPTCP proxy and the server is exchanged in the TCP session.