MPTCP Subflow Establishment via Source Port Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Multipath TCP (MPTCP) specifications lack mechanisms for enabling aggregation of multiple network paths over a single IP address, making it difficult to identify and separate MPTCP data related to different subflows.
Innovation Solution
A method is introduced to establish a multipath TCP connection by initiating additional subflows for an existing TCP connection, using a single IP-address source node, which receives an MPTCP trigger to activate the connection, selects source TCP ports, and sends notifications to the destination node, allowing for the association of each MPTCP subflow with a respective wireless link and the use of Traffic Flow Templates for mapping and communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If MPTCP is implemented over a single IP address, then resource pooling and throughput are increased, but difficulty in identifying and separating MPTCP data related to different subflows increases
Solution Approach 1:
The patent segments MPTCP data by associating each subflow with a specific wireless link identifier. This segmentation approach allows the system to maintain multiple subflows over a single IP address while uniquely identifying and separating data from different subflows through the wireless link identifier, resolving the contradiction between resource pooling and data identification.
Solution Approach 2:
The patent introduces a wireless link identifier as an intermediary element that mediates between the single IP address and multiple subflows. This identifier acts as a mediator that enables the system to track and separate data from different subflows without requiring multiple IP addresses, thus maintaining throughput while enabling data identification.
2Productivity
If multiple TCP connections are established to maximize resource usage, then bandwidth and redundancy are increased, but device complexity increases
Solution Approach 1:
The patent merges multiple TCP connections by implementing MPTCP over a single IP address. Instead of managing separate IP addresses and connections, the system combines multiple subflows under a single IP address while maintaining their individual identities through wireless link identifiers, reducing device complexity while preserving bandwidth benefits.
Solution Approach 2:
The patent makes the single IP address multi-functional by allowing it to serve as the endpoint for multiple subflows simultaneously. This universal approach enables the single IP address to handle multiple wireless links and subflows, reducing the complexity of managing multiple IP addresses while maintaining the bandwidth advantages of multiple connections.
3Reliability
If MPTCP subflows are pre-established in coverage of multiple accesses, then failover capability is improved, but loss of time for connection setup increases
Solution Approach 1:
The patent applies preliminary action by pre-establishing MPTCP subflows while the user is in coverage of multiple accesses. The system proactively sets up subflows on available wireless links before failover is needed, so that when a link fails, the transition to alternative subflows is immediate without requiring new connection setup, thus improving reliability while minimizing time loss.
Data Source
Figure 1~6
Figure 2a~2b
Figure 3
AI summary
The present disclosure relates to a method, performed in a single IP-address source node in a wireless communication network, of establishing a multipath TCP, MPTCP, connection for transfer of TCP datain MPTCP subflows to a destination node. The single IP-address source node receives (S31) an MPTCP trigger to activate a multipath TCP connection. One or more source TCP ports are selected(S32), wherein each source TCP port is selected to constitute a starting point of an MPTCP subflow. One or more MPTCP notifications are sent (S33) to the destination node. Each MPTCP notification includes information on a selected source TCP port. The single IP-address source node receives (34) an acknowledgment of each MPTCP notification from the destination node. The present disclosure also relates to corresponding method performed in a destination node and a wireless device configured for establishing an MPTCP connection.