Traffic distribution approaches in multipath tcp with monetary link-cost awareness

Patent metadata

Field	Value
Publication number	US-2020374216-A1
Application number	US-201916418051-A
Country	US
Kind code	A1
Filing date	May 21, 2019
Priority date	May 21, 2019
Publication date	Nov 26, 2020
Grant date	—

Abstract

Systems, methods, and computer-readable media for controlling data transmission in TCP subflows of a MPTCP connection based on monetary cost. A low cost link and a high cost link of TCP subflows of a MPTCP connection formed between a first MPTCP peer and a second MPTCP peer can be identified. A congestion level on the low cost link can be determined based on feedback from a TCP congestion control mechanism for the MPTCP connection. Further, whether to send a data packet over the low cost link of the high cost link based on the congestion level on the low cost link can be determined. As follows, the data packet can be sent over the low cost link connection if it is determined to send the data packet over the low cost link.

First claim

What is claimed is:

1 . A method comprising:
identifying a low cost link and a high cost link of transmission control protocol (TCP) subflows of a multipath TCP (MPTCP) connection formed between a first MPTCP peer and a second MPTCP peer; determining a congestion level on the low cost link based on feedback from a TCP congestion control mechanism for the MPTCP connection; determining whether to send a data packet in the MPTCP connection over the low cost link or the high cost link based on the congestion level on the low cost link and a lower cost of the low cost link compared to a cost of the high cost link; and sending the data packet over the low cost link as part of the MPTCP connection if it is determined to send the data packet over the low cost link.

2 . The method of claim 1 , further comprising sending the data packet over the high cost link instead of the low cost link if it is determined to send the data packet over the high cost link based on the congestion level on the low cost link.

3 . The method of claim 1 , further comprising:
identifying a plurality of low cost links including the low cost link of the TCP subflows of the MPTCP connection; and selecting the low cost link from the plurality of low cost links for transmitting the data packet based on network throughput requirements of a scheduler associated with the MPTCP connection.

4 . The method of claim 1 , wherein the low cost link and the high cost link of the TCP subflows of the MPTCP connection are identified through exchange of information between the first MPTCP peer and the second MPTCP peer to tag the high cost link as a cost link.

5 . The method of claim 1 , further comprising:
identifying that the low cost link and the high cost link do not exist in the MPTCP connection; and sending the data packet over a backup link of the MPTCP connection.

6 . The method of claim 1 , wherein the TCP congestion control mechanism is a loss sensitive control mechanism that controls congestion in the MPTCP connection based on packet loss.

7 . The method of claim 6 , further comprising:
determining, based on an amount of space in a packet congestion window associated with the low cost link, as indicated by the feedback from the TCP congestion control mechanism, whether to send the data packet over the low cost link as part of the MPTCP connection; and sending the data packet over the low cost link if it is determined to send the data packet over the low cost link based on the amount of space in the packet congestion window associated with the low cost link.

8 . The method of claim 1 , wherein the TCP congestion control mechanism is a loss insensitive congestion control mechanism that controls congestion in the MPTCP connection based on actual congestion in the MPTCP connection.

9 . The method of claim 8 , wherein the TCP congestion control mechanism is a bottleneck bandwidth and round-trip propagation time (RTT) (BBR) congestion control mechanism.

10 . The method of claim 8 , further comprising:
determining, based on a RTT and a pacing gain associated with the low cost link, as indicated by the feedback from the TCP congestion control mechanism, whether to send the data packet over the low cost link as part of the MPTCP connection; and sending the data packet over the low cost link if it is determined to send the data packet over the low cost link based on the RTT and the pacing gain associated with the low cost link.

11 . The method of claim 10 , further comprising:
identifying whether the low cost link is in a drain mode based on the pacing gain associated with the low cost link; and determining that the low cost link is unsuitable for transmitting the data packet through the MPTCP connection if the low cost link is operating in the drain mode.

12 . The method of claim 8 , further comprising:
identifying a bandwidth cap rate for transmitting data, including the data packet, through the TCP subflows over the multipath TCP connection; determining whether to send the data packet in the MPTCP connection over the low cost link based on the bandwidth cap rate and the congestion level on the low cost link; and sending the data packet over the low cost link if it is determined to send the data packet over the low cost link based on the bandwidth cap rate and the congestion level on the low cost link.

13 . The method of claim 12 , further comprising sending the data packet over the high cost link if it is determined to refrain from sending the data packet over the low cost link based on the bandwidth cap rate and the congestion level on the low cost link, wherein the data packet is sent over the high cost link at a pacing rate set to a bandwidth difference between the congestion level on the low cost link and the bandwidth cap rate.

14 . The method of claim 13 , wherein the high cost link is selected from a plurality of high cost links of the TCP subflows of the MPTCP based on the bandwidth cap rate.

15 . A system comprising:
one or more processors; and at least one computer-readable storage medium having stored therein instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising: identifying a low cost link and a high cost link of transmission control protocol (TCP) subflows of a multipath TCP (MPTCP) connection formed between a first MPTCP peer and a second MPTCP peer; determining a congestion level on the low cost link based on feedback from a TCP congestion control mechanism for the MPTCP connection; determining whether to send a data packet in the MPTCP connection over the low cost link or the high cost link based on the congestion level on the low cost link and a lower cost of the low cost link compared to a cost of the high cost link; sending the data packet over the low cost link as part of the MPTCP connection if it is determined to send the data packet over the low cost link; and sending the data packet over the high cost link instead of the low cost link if it is determined to send the data packet over the high cost link based on the congestion level on the low cost link and the lower cost of the low cost link compared to the cost of the high cost link.

16 . The system of claim 15 , wherein the TCP congestion control mechanism is a loss sensitive control mechanism that controls congestion in the MPTCP connection based on packet loss.

17 . The system of claim 16 , wherein the instructions which, when executed by the one or more processors, further cause the one or more processors to perform operations comprising:
determining, based on an amount of space in a packet congestion window associated with the low cost link, as indicated by the feedback from the TCP congestion control mechanism, whether to send the data packet over the low cost link as part of the MPTCP connection; and sending the data packet over the low cost link if it is determined to send the data packet over the low cost link based on the amount of space in the packet congestion window associated with the low cost link.

18 . The system of claim 15 , wherein the TCP congestion control mechanism is a loss insensitive congestion control mechanism that controls congestion in the MPTCP connection based on actual congestion in the MPTCP connection and the instructions which, when executed by the one or more processors, further cause the one or more processors to perform operations comprising:
determining, based on a RTT and a pacing gain associated with the low cost link, as indicated by the feedback

Assignees

• Cisco Tech Inc

Inventors

• Ganesh Nandini
• Gundavelli Sri
• Kathail Pradeep Kumar

Classifications

• H04L69/14

  Multichannel or multilink protocols · CPC title

• H04L47/193

  at the transport layer, e.g. TCP related · CPC title

• H04L47/125

  by balancing the load, e.g. traffic engineering · CPC title

• H04L45/24 Primary

  Multipath · CPC title

• H04L45/125

  based on throughput or bandwidth · CPC title