WO2014019528A1

WO2014019528A1 - Method, device and system for multipath tcp congestion control

Info

Publication number: WO2014019528A1
Application number: PCT/CN2013/080581
Authority: WO
Inventors: 何宁; 朱雷
Original assignee: 华为技术有限公司
Priority date: 2012-08-01
Filing date: 2013-08-01
Publication date: 2014-02-06
Also published as: CN103581035B; CN103581035A

Abstract

Embodiment of the present invention provides a method, device and system for multipath TCP congestion control, and belongs to the technical field of communication, in order to control congestion before congestion occurs and to improve data transmission efficiency. Said method includes: a receiver receives packets sent by the first access network node in at least one of multipath transport control protocol TCP sub-flows which have been established by a sender in the first access network. If it is detected that the said packet has ECT tag marked by a first flag which supports for explicit congestion notification ECN and has congestion alarm CE tag marked by a second flag, then the receiver does congestion control. Wherein, ECN echo ECE tag of the said packet is marked by a third flag and congestion window reduced CWR tag is marked by a fourth flag. The invention is used for congestion control.

Description

Method, device and system for multipath TCP congestion control

This application claims the priority of the Chinese Patent Application entitled "Method, Apparatus and System for Multipath TCP Congestion Control", filed on August 1, 2012 by the Chinese Patent Office, Application No. CN 201210271599. The content is incorporated herein by reference. TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for multipath TCP congestion control. Background technique

MPTCP (Multipath Transport Control Protocol) is based on TCP (Transport Control Protocol). It has two main functions: packet scheduling and path management. MPTCP is transparent to the application layer. The MPTCP distributes the data of the sender application layer to each substream transmission, and delivers the data transmitted by each substream received by the receiver to the application layer in order. MPTCP improves the utilization of resources by providing multi-path implementation, thereby increasing the capacity of the network.

MPTCP relies on substreams to send and receive data. When a substream is congested, MPTCP needs to perform congestion control on the substream. In the prior art, MPTCP realizes the substream by adjusting the size of the congestion window.

/ alpha * bytes a eked * MSS i line congestion control. Specifically, MPTCP adjusts the congestion window size by the formula min (― ~ ―, cwnd _ total bytes _ acked * MSS _ ! ₎ . Where _cwn d_i represents the cwnd _ i of the i-th sub-stream

Cwnd_total represents the sum of the congestion windows of all substreams, MSS_i represents the maximum segmentation value of the i-th substream; bytes_acked represents the size of the bytes that have been acknowledged by the receiver within a round-trip delay; alpha is the coefficient , calculated by the formula alpha=c wnd_total* 丽^{d —} id ² ); _rttJ

(SUM (cwnd _ i / rtt _ i)) ²

Indicates round trip delay.

In the process of implementing the above congestion control, the inventor finds that at least the following problems exist in the prior art: The transmitting end of the data can only perform congestion control after congestion occurs, and the network node may have discarded some data packets and reduced the data. The efficiency of the transmission. Summary of the invention Embodiments of the present invention provide a method, apparatus, and system for multipath TCP congestion control, which are used to perform congestion control before congestion occurs, thereby improving data transmission efficiency.

In order to achieve the above object, the embodiment of the present invention adopts the following technical solutions:

In a first aspect, the embodiment of the present invention provides a method for multipath TCP congestion control, including: receiving, by a receiving end, at least one multipath transmission control protocol TCP substream that has been established by the first access network, a data packet sent by a network node of the access network;

If the transmission ECT flag of the ECN is detected by the first identifier, the congestion warning CE flag is identified by the second identifier, and the receiving end performs congestion control; The ECN feedback ECE flag bit of the data packet is identified by a third identifier; the congestion window is halved and the CWR flag bit is identified by a fourth identifier.

In a first possible implementation manner, the performing congestion control includes: if the sending end accesses the receiving end by using a second access network, if the sending end and the receiving end are not in the first The second access network establishes a multipath TCP substream, and in the second access network, the receiving end sends a first synchronization sequence number SYN data packet to the sending end, where the first SYN data packet is The ECE flag is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; the first SYN packet further carries a multipath to add MPJOIN information. The MPJOIN indicates that a multipath TCP substream is added; the receiving end receives the first synchronization sequence number and the acknowledge SYN-ACK data packet sent by the sending end; and the foregoing in the first SYN-ACK data packet. The ECE flag is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag is different from the CE flag; the SYN-ACK packet carries MPJOIN information; Send to the sender Acknowledge ACK packet; the ACK packet carries MP_JOIN information.

With reference to the first aspect, in a second possible implementation, the performing congestion control includes: the receiving end sending a first response data packet to the sending end, so that the sending end performs congestion control; The ECT flag of the first response packet is identified by a first identifier, the CE flag is identified by a seventh identifier; the ECE flag is identified by a fifth identifier; and the C WR flag is identified by a fourth identifier Symbol.

With reference to the first aspect, in a third possible implementation manner, the performing congestion control includes: performing congestion control on the established multipath TCP substream, and sending a second response data packet to the sending end; The ECT flag of the response packet is identified by a first identifier, and the CE flag is identified by a seven identifier The identifier is identified by a third identifier; the C WR flag is identified by a sixth identifier.

In a second aspect, the embodiment of the present invention provides a method for multipath TCP congestion control, including: sending, by a sending end, a data packet to a receiving end in at least one multipath transmission control protocol TCP substream that has been established in the first access network. The data packet supports the explicit congestion notification ECN transmission ECT flag is identified by the first identifier, the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier; the congestion window The halving CWR flag is identified by the fourth identifier; so that the network node of the first access network notifies the receiving end by changing the identifier of the CE flag when detecting that the network is about to be congested, so that the receiving end is congested. Control; if the receiving end performs congestion control, the transmitting end performs corresponding congestion control.

In a first possible implementation manner, the transmitting end performing corresponding congestion control includes: if the sending end accesses the receiving end by using a second access network, if the sending end and the receiving end In the second access network, the transmitting end receives the first synchronization sequence number SYN data packet sent by the receiving end, where the first SYN is not established in the second access network. The ECE flag of the data packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; the first SYN packet is also carried Adding MPJOIN information to the multipath; the MPJOIN indicates adding a multipath TCP substream; the transmitting end sends a first synchronization sequence number and an acknowledge SYN-ACK packet to the receiving end; the first SYN-ACK packet The ECE flag bit is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag is different from the CE flag bit; the SYN-ACK packet carries MPJOIN information The transmitting terminal The reception confirmation ACK packet transmission end; the ACK packet carries MP_JOIN information.

With reference to the second aspect, in a second possible implementation manner, the transmitting end performing corresponding congestion control includes: the sending end receiving the first response data packet sent by the receiving end; the first response data packet The ECT flag is identified by a first identifier, the CE flag is identified by a seventh identifier; the ECE flag is identified by a fifth identifier; and the C WR flag is identified by a fourth identifier.

With the second aspect or the second possible implementation of the second aspect, in a third possible implementation, after the sending end receives the first response data sent by the receiving end, the method further includes: If the transmitting end accesses the receiving end through the second access network, if the transmitting end and the receiving end do not establish a multipath TCP substream in the second access network, then the second access network Medium, the transmitting end Transmitting, by the receiving end, the first SYN data packet; the sending end receiving the first SYN-ACK data packet sent by the receiving end; and sending, by the sending end, the ACK data packet to the receiving end .

With the second aspect or the second possible implementation of the second aspect, in a fourth possible implementation, after the sending end receives the first response data sent by the receiving end, the method further includes: The sender performs congestion control on the established multipath TCP substream.

With reference to the second aspect, in a fifth possible implementation manner, the transmitting end performing corresponding congestion control includes: receiving, by the sending end, a second response data packet sent by the receiving end; The ECT flag is identified by a first identifier, the CE flag is identified by a seven identifier; the ECE flag is identified by a third identifier; and the CWR flag is identified by a sixth identifier.

In a third aspect, the embodiment of the present invention provides an apparatus for multipath TCP congestion control, including: a receiving unit, configured to receive, in a TCP substream of at least one multipath transmission control protocol that the transmitting end has established in the first access network. a data packet sent by the network node of the first access network; a processing unit, configured to identify, by the first identifier, a transmission ECT flag bit that supports the explicit congestion notification ECN of the data packet; a congestion warning CE flag When the bit is identified by the second identifier, the receiving end performs congestion control; wherein, the ECN feedback ECE flag of the data packet is identified by the third identifier; the congestion window is halved, and the CWR flag is used with the fourth identifier Logo.

In a first possible implementation manner, the processing unit includes: a first sending module, a first receiving module, and the first sending module, configured to access, by using the second access network, the sending end In the case of the device, if the transmitting end and the device do not establish a multipath TCP substream in the second access network, in the second access network, send the first synchronization sequence number to the transmitting end. a SYN data packet; the ECE flag bit of the first SYN data packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag bit is different from the CE flag bit; The first SYN data packet further carries the multipath addition MP_JOIN information; the MPJOIN information indicates that a multipath TCP substream is added; the first receiving module is configured to receive the first synchronization sequence number sent by the sending end. And confirming the SYN-ACK data packet; the ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the C WR is identified by a fourth identifier; and the ECT flag bit is The CE mark is different; It said SYN-ACK packet carries information MP_J0IN; the first sending module is further configured to transmit an acknowledgment ACK packet to the sending end; the ACK packet carries MP_J0IN information.

With reference to the third aspect, in a second possible implementation, the processing unit is specifically configured to Transmitting, by the sending end, the first response data packet, so that the sending end performs congestion control; the ECT flag bit of the first response data packet is identified by a first identifier, and the CE flag bit is identified by a seventh identifier The ECE flag bit is identified by a fifth identifier; the C WR flag bit is identified by a fourth identifier.

With reference to the third aspect, in a third possible implementation, the processing unit is specifically configured to: perform congestion control on the established multipath TCP substream, and send a second response data packet to the sending end; The ECT flag of the second response packet is identified by a first identifier, the CE flag is identified by a seven identifier; the ECE flag is identified by a third identifier; the C WR flag is identified by a sixth identifier .

In a fourth aspect, the embodiment of the present invention provides an apparatus for multipath TCP congestion control, including: a sending unit, configured to: in a TCP substream of at least one multipath transmission control protocol that has been established in a first access network, to a receiving end Transmitting a data packet; the transmission ECT flag of the data packet supporting the explicit congestion notification ECN is identified by a first identifier, and the congestion warning CE flag is identified by a seventh identifier; the ECN feedback ECE flag is identified by a third identifier The congestion window is halved and the CWR flag is identified by the fourth identifier; so that the network node of the first access network notifies the receiving end by changing the identifier of the CE flag when detecting that the network is about to be congested, so that the receiving Congestion control is performed at the end; and the processing unit is configured to perform corresponding congestion control when the receiving end performs congestion control.

In a first possible implementation manner, the processing unit includes: a receiving module and a sending module, where the receiving module is configured to: when the sending end accesses the receiving end by using a second access network, The device and the receiving end do not establish a multipath TCP substream in the second access network, and in the second access network, receive the first synchronization sequence number SYN data packet sent by the receiving end; The ECE flag of the first SYN packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; the first SYN packet is And carrying the multipath to add the MPJOIN information; the MPJOIN is to add a multipath TCP substream; the sending module is configured to send the first synchronization sequence number and the acknowledge SYN-ACK data packet to the receiving end; The ECE flag in a SYN-ACK packet is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag is different from the CE flag; the SYN-ACK data The bag carries the MPJOIN letter The receiving module is further configured to receive an acknowledgement ACK packet sent by the receiving end, where the ACK packet carries MP_JOIN information.

With reference to the fourth aspect, in a second possible implementation, the processing unit is specifically configured to: receive a first response data packet sent by the receiving end; and use an ECT flag of the first response data packet An identifier identifier, the CE flag bit is identified by a seventh identifier; the ECE flag bit is identified by a fifth identifier; and the CWR flag bit is identified by a fourth identifier.

With the fourth aspect or the second possible implementation manner of the fourth aspect, in a third possible implementation, the sending unit is further configured to access, by using the second access network, the sending end In the case of the receiving end, if the transmitting end and the receiving end do not establish a multipath TCP substream in the second access network, in the second access network, send the first SYN to the receiving end. The device, the device further includes: a receiving unit, configured to receive the first SYN-ACK data packet sent by the receiving end, where the sending unit is further configured to send the ACK data to the receiving end package.

With reference to the fourth aspect, or the second possible implementation manner of the fourth aspect, in a fourth possible implementation manner, the processing unit is further configured to perform congestion control on the established multipath TCP substream.

With reference to the fourth aspect, in a fifth possible implementation, the processing unit is configured to: receive a second response data packet that is sent by the receiving end; and use the first ECT flag of the second response data packet An identifier identifier, the CE flag bit is identified by a seven identifier; the ECE flag bit is identified by a third identifier; and the CWR flag bit is identified by a sixth identifier.

According to a fifth aspect, an embodiment of the present invention provides a device for multipath TCP congestion control, including: a receiver, configured to receive, by a receiving end, at least one multipath transmission established by a network node of a first access network; Controlling the data packet sent in the TCP substream; the data packet supports the explicit congestion notification ECN transmission ECT flag is identified by the first identifier, and the congestion warning CE flag is identified by the second identifier; ECN feedback ECE flag The bit is identified by the third identifier; the congestion window is halved, and the CWR flag is identified by the fourth identifier; the processor is configured to: when detecting that the CE flag of the data packet is the second identifier, Congestion control.

In a sixth aspect, an embodiment of the present invention provides a device for multipath TCP congestion control, including: a transmitter, configured to send, by a sending end, at least one multipath transmission control protocol TCP substream established in a first access network The receiving end sends a data packet; the data packet supports the explicit congestion notification ECN. The transmission ECT flag is identified by the first identifier, and the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier. The congestion flag is halved. The CWR flag is identified by the fourth identifier; so that the network node of the first access network notifies the receiving end by changing the CE flag when detecting that the network is about to be congested, so that the receiving The terminal performs congestion control; and the processor is configured to perform corresponding congestion control in the case of congestion control at the receiving end.

In a seventh aspect, an embodiment of the present invention provides a system for multipath TCP congestion control, including: a transmitting end, a network node, and a receiving end; the transmitting end is a device for multipath TCP congestion control according to the above third aspect; the receiving end is a multipath TCP congestion control according to the fourth aspect s installation.

The eighth aspect of the present invention provides a system for multipath TCP congestion control, including: a transmitting end, a network node, and a receiving end; and the transmitting end is a multipath TCP congestion control according to the fifth aspect. The device is a device for multipath TCP congestion control according to the sixth aspect.

The embodiment of the present invention provides a method, device, and system for multipath TCP congestion control, where a sender sends a data packet in an established at least one multipath TCP substream of a first access network, if the first access network The network node detects that the network is about to be congested, and then identifies the ECT flag in the data packet with the first identifier, the CE flag is identified by the second identifier, the ECE flag is identified by the third identifier, and the CWR flag is used. The four identifier identifier is sent to the receiving end, and after receiving the data packet, the receiving end detects that the CE flag of the data packet is identified by the second identifier, and performs congestion control. In this way, congestion control is implemented before congestion occurs, and the efficiency of data transmission is improved.

BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below, and obviously, in the following description The drawings are only some of the embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work.

FIG. 1 is a schematic diagram of a method for multipath TCP congestion control according to an embodiment of the present invention; FIG. 2 is a schematic diagram of another method for multipath TCP congestion control according to an embodiment of the present invention; FIG. 4 is a schematic diagram of another method for multipath TCP congestion control according to an embodiment of the present invention; FIG. 5 is another multipath TCP congestion control according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another method for multipath TCP congestion control according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of an apparatus for multipath TCP congestion control according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of a processing unit of a device for multipath TCP congestion control according to FIG. 7; FIG. 9 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention; Figure

FIG. 10 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

13 is a schematic structural diagram of a processing unit of a multipath TCP congestion control apparatus shown in FIG. 12;

FIG. 14 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

FIG. 15 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

FIG. 16 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

FIG. 17 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

FIG. 18 is a schematic structural diagram of another apparatus for multipath TCP congestion control according to an embodiment of the present invention;

FIG. 19 is a schematic structural diagram of a system for multipath TCP congestion control according to an embodiment of the present invention; FIG. 20 is a schematic structural diagram of another system for multipath TCP congestion control according to an embodiment of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of them. Example. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

An embodiment of the present invention provides a method for multipath TCP congestion control, as shown in FIG. 1 , including: 101. The receiving end receives, by the sending end, a data packet sent by the network node of the first access network in the at least one multipath transmission control protocol TCP substream that has been established by the first access network.

Specifically, the sending end accesses the receiving end by using the first access network and the second access network, and in the first access network, at least one multipath TCP (Transport Control Protocol) is established between the transmitting end and the receiving end. a control flow), the transmitting end sends a data packet to the receiving end by using the at least one multipath TCP substream, and the receiving end receives the first access network in the at least one multipath TCP substream of the first access network A packet transmitted by a network node.

For example, if the first access network is a 3Gpp network, the network node is sent by an eNB (E-UTRAN Node B, an evolved UMTS terrestrial radio access network node) or an SGW (Serving Gateway), or a router in the network. The terminal establishes at least one multipath TCP substream with the receiving end through the 3Gpp network. The transmitting end sends the data packet to the receiving end through the at least one multipath TCP substream of the 3Gpp network, and the data packet is forwarded to the receiving end by the network node eNB and the SGW, and the receiving end receives the data packet. Wherein, when the network is about to be congested, the network node changes the CE flag bit in the data packet to the second identifier identifier; or when the access network link quality deteriorates, the eNB changes the CE flag bit in the data packet. Identifies the second identifier.

In addition, the first access network may also be a non-3Gpp network, such as a WLAN, where the network node is an AGW (Access Gateway) or a PDG (packet data gateway) or an ePDG (evolved packet data gateway). Packet data gateway), or a router in the network. The transmitting end establishes at least one multipath TCP substream with the receiving end through the non-3Gpp network. The transmitting end sends a data packet to the receiving end through at least one multipath TCP substream of the non-3Gpp network, and the data packet is forwarded to the receiving end by the network node, and the receiving end receives the data packet. When the network is about to become congested or when the access network link quality is degraded, the network node changes the CE flag bit in the packet to the second identifier.

102. If the detection of the data packet supports explicit congestion notification, the transmission of the ECN is marked by the first identifier; the congestion warning CE flag is identified by the second identifier, and the receiving end performs congestion control.

The ECN feedback ECE flag of the data packet is identified by a third identifier; the congestion window is halved. The CWR flag is identified by a fourth identifier.

Further, the ECT (ECN-Capable Transport) supports the ECN (Explicit Congestion Notification). Know). The CE (Congestion Experienced) flag is used to indicate if the network is about to become congested. ECE (ECN-Echo, ECN feedback) is used to indicate whether a CE packet has been received. C WR (Congestion Window Reduced) is used to indicate if the congestion window has been halved.

Optionally, the first identifier and the second identifier are represented by 1, and the third identifier and the fourth identifier are represented by 0.

It should be noted that the first identifier is used to indicate that the ECT flag is selected, that is, the ECN is supported; the second identifier is used to indicate that the CE flag is selected, that is, the network is about to be congested; the third identifier is used to indicate The ECE flag is not selected, indicating that a CE packet has not been received. The fourth identifier is used to indicate that the CWR is not selected, indicating that the congestion window has not been halved.

It should be noted that the first identifier, the second identifier, the third identifier, and the fourth identifier may also be represented by other characters, as long as the respective roles can be expressed, and the present invention does not limit this.

Specifically, after receiving the data packet, the receiving end detects each flag bit of the data packet to know whether congestion is to occur. If it is detected that the ECT flag is identified by the first identifier, it is known that the sender supports the ECN, and the CE uses the second identifier to identify that the network is about to be congested. At this time, the receiver needs to perform congestion control.

There are three methods for performing congestion control. The following three methods are described in detail.

In the first method, in the network where the transmitting end accesses the receiving end, in the network where the multipath TCP substream is not established, the receiving end creates a new multipath TCP substream, as shown in FIG. 2, which is specifically as follows.

In the case that the transmitting end accesses the receiving end through the second access network, if the transmitting end and the receiving end do not establish a multipath TCP substream in the second access network, then In the two access networks, the receiving end sends a first synchronization sequence number SYN data packet to the sending end.

The ECE flag of the first SYN packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; The SYN packet also carries multipath added MPJOIN information. The MPJOIN indicates that a multipath TCP substream is added.

Specifically, when the receiving end establishes the multipath TCP substream in the second access network, the ECN mechanism needs to be negotiated with the sending end, and the receiving end identifies the ECE flag of the first SYN packet by using the fifth identifier and the CWR. Using the sixth identifier, and the ECT flag is different from the CE flag, the ECN mechanism is negotiated with the sender. The first SYN data packet also carries MP_JOIN information, which is used to indicate that a multipath TCP substream is added to the second access network. Since the receiving end and the transmitting end are already built in the first access network The multipath TCP substream is established. Therefore, when the multipath TCP substream is established in the second access network, the MPJOIN information needs to be carried, indicating that the multipath TCP substream is established.

It should be noted that the fifth identifier is used to indicate that the ECE flag is selected; the sixth identifier is used to indicate that the CWR is selected. Optionally, the fifth identifier and the sixth identifier are represented by 1.

It should be noted that, in all embodiments of the present invention, the difference between the ECT flag and the CE flag means that the value of the ECT flag is different from the identifier of the CE flag. For example, the ECT flag is identified by 1. Then, the CE flag is marked with 0; or, the ECT flag is marked with 0, and the CE flag is identified by 1.

202. The receiving end receives the first synchronization sequence number and the acknowledge SYN-ACK data packet sent by the sending end.

The ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit. The SYN-ACK packet carries MPJOIN information.

Specifically, the ECE flag in the first SYN-ACK packet is identified by the fifth identifier, and the CWR is identified by the fourth identifier, and the ECT flag and the CE flag are different, indicating that the sender supports the ECN mechanism. The SYN-ACK packet carries the MP_JOIN information, indicating that the sender agrees to add the multipath TCP substream. The first SYN-ACK packet is a response packet of the first SYN packet.

203. The receiving end sends an acknowledgement ACK packet to the sending end.

The ACK packet carries MP_JOIN information.

Specifically, after receiving the first SYN-ACK data packet, the receiving end sends an ACK data packet to the transmitting end, and responds to the first SYN-ACK data packet. The establishment of a multipath TCP substream for performing a three-way handshake process in the second access network is completed.

It should be noted that in all embodiments of the invention, the second access network is a different network than the first access network. For example, the first access network is a 3Gpp network and the second access network is a non-3Gpp network.

In the second method, the receiving end notifies the transmitting end that a CE packet is received, and the transmitting end performs congestion control, as follows.

The receiving end sends a first response data packet to the sending end, so that the sending end performs congestion control.

The ECT flag of the first response data packet is identified by a first identifier, and the CE label The ambition is identified by a seventh identifier; the ECE flag is identified by a fifth identifier; and the C WR flag is identified by a fourth identifier.

Specifically, the CE flag indicates that the CE flag is not selected by the seventh identifier, and the ECE flag indicates that the ECE is selected by the fifth identifier, that is, a CE packet is received. The receiving end notifies the sending end that the network is about to be congested by identifying each flag bit of the first response data packet, so that the transmitting end performs congestion control.

There are two ways for the sender to perform congestion control. One is that the sender initiates the process of establishing a multipath TCP substream in the network where the multipath TCP substream is not established. The corresponding processing at the receiving end is as follows.

In the second access network, the receiving end receives the first SYN data packet sent by the sending end.

The receiving end sends the first SYN-ACK data packet to the sending end.

The ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit. The SYN-ACK packet carries the MP_JOIN information, indicating that the receiving end agrees to add the multipath TCP substream.

The receiving end receives an ACK data packet sent by the sending end; the ACK data packet carries MPJOIN information.

Specifically, the receiving end receives the response packet ACK packet of the first SYN-ACK packet sent by the sending end, indicating that the multipath TCP substream is established in the second access network, and the sending end can use the new The multipath TCP substream transmits data, thereby slowing down network congestion.

The second way is that the sender performs congestion control on the established multipath TCP substream, thereby slowing network congestion.

In the third method, the receiving end performs congestion control on the established multipath TCP substream, as follows. The receiving end performs congestion control on the established multipath TCP substream, and sends a second response data packet to the transmitting end. The ECT flag of the second response packet is identified by a first identifier, the CE flag is identified by a seven identifier; the ECE flag is identified by a third identifier; and the C WR flag is used by The sixth identifier is identified.

Specifically, the receiving end performs congestion control on the multipath TCP substream that has been established in the first access network, for example, halving the congestion window of the multipath TCP substream, and identifying the CWR flag by the sixth identifier. , indicating that the CWR flag is selected, that is, the congestion window has been halved. The sender identifies that the established multipath TCP subflow has congestion control by identifying each flag of the second response packet.

It should be noted that, in the case that the transmitting end accesses only the first access network to the receiving end, and does not access the receiving end through other networks, the method for the receiving end to perform congestion control may be the second notification sending end network. Congestion is imminent, causing the sender to perform congestion control. Or the third type, the receiving end performs congestion control on the established multipath TCP substream.

The embodiment of the present invention provides a method for multipath TCP congestion control. After receiving a data packet, if the ECT flag of the data packet is detected by the first identifier, the CE flag is identified by the second identifier. Then perform congestion control. In this way, congestion control is implemented before congestion occurs, and the efficiency of data transmission is improved.

The embodiment of the present invention provides a method for multipath TCP congestion control. As shown in FIG. 3, the method includes: 301: A sending end receives in a TCP substream of at least one multipath transmission control protocol that has been established in a first access network. The end sends a packet.

The transmission ECT flag of the data packet supporting the explicit congestion notification ECN is identified by the first identifier, and the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier; The window halving CWR flag is identified by the fourth identifier, so that the network node of the first access network detects the network to be congested or the quality of the first access network link deteriorates, and the network node passes the CE flag of the data packet. The bit is changed from the seventh identifier identifier to the second identifier identifier to notify the receiving end network that the network is about to be congested or the first access network link quality is deteriorated, so that the receiving end performs congestion control.

Further, the ECT (ECN-Capable Transport) flag is used to indicate whether ECN (Explicit Congestion Notification) is supported. The CE (Congestion Experienced) flag is used to indicate if the network is about to become congested. ECE (ECN-Echo, ECN feedback) is used to indicate whether a CE packet has been received. C WR (Congestion Window Reduced) is used to indicate if the congestion window has been halved. Optionally, the first identifier and the second identifier are represented by 1, and the seventh identifier, the third identifier, and the fourth identifier are represented by 0.

It should be noted that the first identifier is used to indicate that the ECT flag is selected, that is, the ECN is supported; the seventh identifier is used to indicate that the CE flag is not selected, that is, the network is not about to be congested; It is used to indicate that the ECE flag is not selected, that is, it does not receive a CE packet; the fourth identifier is used to indicate that the CWR is not selected, that is, the congestion window is not halved.

It should be noted that the first identifier, the second identifier, the seventh identifier, the third identifier, and the fourth identifier may also be represented by other characters, as long as they can express their respective roles, the present invention No restrictions.

Specifically, the sending end sends, by the network node of the first access network, the data packet to the receiving end in the at least one multipath transmission control protocol TCP substream that has been established by the first access network. When the sending end sends the data packet to the network node of the first access network, if the network node detects that the network is about to be congested, the CE flag bit in the data packet is modified from the seventh identifier identifier to the second identifier identifier. The data packet with the modified CE flag is sent to the receiving end to notify the receiving end that the network is about to be congested, so that the receiving end performs congestion control.

It should be noted that the CE flag indicates that the CE flag is selected by the second identifier, that is, the network is about to be congested.

302. If the receiving end performs congestion control, the sending end performs corresponding congestion control.

Specifically, in the case that the receiving end performs congestion control, the transmitting end performs congestion control according to congestion control performed by the receiving end. Since the receiving end performs congestion control in three ways, the method of performing congestion control on the transmitting end can be classified into three types. .

In the first method, in the network where the transmitting end accesses the receiving end, in the network where the multipath TCP substream is not established, the multipath TCP substream is newly established by the receiving end, as follows.

If the transmitting end accesses the receiving end through the second access network, if the transmitting end and the receiving end do not establish a multipath TCP substream in the second access network, the second connection is performed. In the network access, the sending end receives the first synchronization sequence number SYN data packet sent by the receiving end.

The ECE flag of the first SYN packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; The SYN data packet also carries multipath added MPJOIN information; the MPJOIN indicates that one is added. Multipath TCP subflow.

Specifically, when the receiving end establishes the multipath TCP substream in the second access network, the ECN mechanism needs to be negotiated with the sending end, and the receiving end identifies the ECE flag of the first SYN packet by using the fifth identifier and the CWR. Using the sixth identifier, and the ECT flag is different from the CE flag, the ECN mechanism is negotiated with the sender. The first SYN data packet also carries MPJOIN information, which is used to indicate that a multipath TCP substream is added to the second access network.

The transmitting end sends the first synchronization sequence number and the acknowledge SYN-ACK data packet to the receiving end. The ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; The SYN-ACK packet carries the MPJOIN information.

Specifically, if the sending end supports the ECN mechanism, the response packet of the first SYN, that is, the ECE flag of the first SYN-ACK packet is identified by the fifth identifier, the CWR is identified by the fourth identifier, and the ECT flag is used. The bit is different from the CE flag. The SYN-ACK packet carries the MPJOIN information indicating that the multipath TCP substream is established in the second access network.

The transmitting end receives an acknowledgement ACK packet sent by the receiving end; the ACK packet carries MPJOIN information.

Specifically, the sending end receives the response packet ACK packet of the first SYN-ACK packet sent by the receiving end, indicating that the multipath TCP substream is established in the second access network, and the newly created multipath can be utilized. The TCP substream transmits data, thereby reducing network congestion.

In the second method, the receiving end notifies the transmitting end that a CE data packet is received, and the transmitting end performs congestion control, as follows.

The transmitting end receives the first response data packet sent by the receiving end.

The ECT flag of the first response data packet is identified by a first identifier, and the CE flag bit is identified by a seventh identifier; the ECE flag bit is identified by a fifth identifier; the C WR flag bit Identified with the fourth identifier.

Specifically, the ECE flag bit indicates that the ECE is selected by using the fifth identifier, that is, a CE packet is received. The sender receives the first response packet, and detects that the ECE is identified by the fifth identifier, indicating that the network is about to be congested, and the sender performs congestion control. Optionally, the fifth identifier is represented by 1.

Further, the receiving end notifies the sending end that the network is about to be congested, and the sending end performs congestion control in two ways. One way is that the sending end initiates a process of establishing a multipath TCP substream in a network in which a multipath TCP substream is not established. The following is a detailed description, as shown in Figure 4, including:

401. If the sending end accesses the receiving end by using the second access network, if the sending end and the receiving end do not establish a multipath TCP substream in the second access network, In the second access network, the sending end sends the first SYN data packet to the receiving end.

The ECE flag of the first SYN packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; The SYN data packet also carries multipath added MPJOIN information; the MPJOIN indicates that a multipath TCP substream is added.

Specifically, when the sending end establishes the multipath TCP substream in the second access network, the ECN mechanism needs to be negotiated with the receiving end, and the sending end identifies the ECE flag of the first SYN packet with the fifth identifier and the CWR. Using the sixth identifier, and the ECT flag is different from the CE flag, the ECN mechanism is negotiated with the receiving end. The first SYN data packet also carries MPJOIN information, which is used to indicate that a multipath TCP substream is added to the second access network. Since the multipath TCP substream is established in the first access network by the transmitting end and the receiving end, when the multipath TCP substream is established in the second access network, the MPJOIN information needs to be carried, indicating that the multipath TCP is established. Subflow.

402. The sending end receives the first SYN-ACK data packet sent by the receiving end.

The ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the CWR is identified by a fourth identifier, and the ECT flag bit is different from the CE flag bit. The SYN-ACK packet carries MPJOIN information.

Specifically, the ECE flag bit in the first SYN-ACK data packet is identified by the fifth identifier, and the CWR is identified by the fourth identifier, and the ECT flag bit and the CE flag bit are different, indicating that the receiving end supports the ECN mechanism. The SYN-ACK packet carries the MP_JOIN message, indicating that the receiving end agrees to add multipath.

TCP subflow. The first SYN-ACK packet is a response packet of the first SYN packet.

403. The sending end sends the ACK data packet to the receiving end.

The ACK packet carries MP_JOIN information.

Specifically, after receiving the first SYN-ACK data packet, the sending end sends an ACK data packet to the receiving end, Response to the first SYN-ACK packet. The establishment of a multipath TCP substream that performs a three-way handshake process in the second access network is completed.

Alternatively, the transmitting end performs congestion control on the established multipath TCP substream, as follows. Specifically, the sending end performs congestion control on the multipath TCP substream that has been established in the first access network, for example, halving the congestion window of the multipath TCP substream, and the sending end is more according to the congestion window after the halving The data packet is transmitted in the TCP substream, thereby reducing the number of transmitted data packets and effectively alleviating network congestion.

It should be noted that, when the receiving end notifies the transmitting end that a CE data packet is received, and the transmitting end performs congestion control, if the transmitting end accesses the receiving end only through the first access network, it does not connect through other networks. When entering the receiving end, the sending end may first send a second access network connection message to the receiving end, so that the sending end accesses the receiving end through the second access network, and then performs corresponding congestion control, for example, the second congestion control method. The first way. The sender can also directly perform congestion control on the established multipath TCP substream, for example, the second mode of the second congestion control method.

In the third method, the transmitting end knows that the receiving end has halved the congestion window, as follows.

The transmitting end receives the second response data packet sent by the receiving end.

The ECT flag of the second response packet is identified by a first identifier, the CE flag is identified by a seven identifier; the ECE flag is identified by a third identifier; and the C WR flag is used by The sixth identifier is identified.

Specifically, the CWR is identified by the sixth identifier, indicating that the CWR is selected, that is, the receiving end has halved the congestion window of the established multipath TCP substream. The transmitting end transmits the data packet in the established multipath TCP substream according to the size of the congestion window of the established multipath TCP substream, thereby reducing the number of transmitting data packets, and effectively reducing network congestion.

An embodiment of the present invention provides a method for multipath TCP congestion control, where a sending end sends a data packet in at least one multipath TCP substream of the first access network, if the network node of the first access network detects When the network is about to be congested, the ECT flag in the data packet is identified by the first identifier, the CE flag is identified by the second identifier, the ECE flag is identified by the third identifier, and the C WR flag is identified by the fourth identifier. The identifier is sent to the receiving end, so that after receiving the data packet, the receiving end detects that the CE flag of the data packet is identified by the second identifier, and then performs congestion control. In this way, congestion control is implemented before congestion occurs, and the efficiency of data transmission is improved. The embodiment of the invention provides a method for multipath TCP congestion control. As shown in FIG. 5, the method includes:

501. The sending end sends a second SYN data packet to the receiving end, and the receiving end receives the second SYN data packet sent by the sending end in the first access network, and records related information of the MP_CAPABLE of the sending end. a port number, and an IP address; and forwarding the second SYN packet to the server of the communication peer.

The ECE flag bit in the second SYN data packet is identified by a fifth identifier, the CWR flag bit is identified by a six identifier; and the ECT flag bit is different from the CE flag bit; The second SYN packet carries the multipath capability MP_CAPABLE information; the MP_CAPABLE is used to identify that the sender supports multipath TCP.

Optionally, the fifth identifier and the sixth identifier are represented by 1.

Specifically, when the sending end initially establishes the multipath TCP substream in the first access network, the ECN mechanism needs to be negotiated with the receiving end, and the sending end identifies the ECE flag of the second SYN packet by using the fifth identifier. The CWR is identified by a sixth identifier, and the ECT flag is different from the CE flag, and the ECN mechanism is negotiated with the receiving end. The first SYN packet also carries MP_CAPABLE information, which is used to indicate that the sender supports multipath TCP, and establishes a multipath TCP substream in the first access network.

502. The receiving end receives a second SYN-ACK data packet sent by a server of the communication peer end. Specifically, the ECE flag of the second SYN-ACK packet is identified by a fifth identifier; the CWR flag is identified by a fourth identifier; and the ECT flag is different from the CE flag.

503. If the receiving end detects that the second SYN-ACK data packet does not carry the MP_CAPABLE information, add the MP_CAPABLE to the second SYN-ACK data packet, and identify the The P flag bit of the second SYN-ACK packet.

Specifically, the receiving end detects that the second SYN-ACK packet does not carry the MP_CAPABLE information, indicating that the server of the communication peer does not support the multipath TCP, and the receiving end adds the MP_CAPABLE to the second SYN-ACK packet. And identifying, by the eighth identifier, the P flag of the second SYN-ACK packet, so that the sending end learns, by using the P flag, that the server of the communication peer does not support multipath TCP, and the multipath TCP is established by the receiving end and the transmitting end. flow.

The receiving end records the port number, IP address, and MP_CAPABLE information of the sending end to facilitate the establishment of the multipath TCP substream.

Optionally, the eighth identifier is represented by 1. It should be noted that the eighth identifier is used to indicate that the P flag is selected, and the eighth identifier can also be represented by other characters, as long as the respective roles can be expressed, and the present invention does not limit this.

504. The receiving end sends the second SYN-ACK data packet to the sending end, where the sending end receives the second SYN-ACK data packet sent by the receiving end.

The ECE flag of the second SYN-ACK packet is identified by a fifth identifier; the CWR flag is identified by a fourth identifier; and the ECT flag is different from the CE flag; The second SYN-ACK packet also carries MP_CAPABLE information; the P flag of the second SYN-ACK packet is identified by an eighth identifier.

505. The sending end sends an ACK data packet to the receiving end, where the receiving end receives the ACK data packet sent by the sending end, and sends the ACK data packet to a server of the communication peer end.

Specifically, after receiving the second SYN-ACK packet, the sending end sends the response packet ACK packet to the receiving end, and the receiving end sends the ACK packet to the server of the communication peer, so that the sending end and the receiving end A multipath TCP substream is established in the first access network, and the receiving end establishes a TCP connection with the server of the communication peer.

506. The same as step 301, and details are not described herein again.

507. The same as step 101, and details are not described herein again.

508. The same as step 102, and details are not described herein again.

509. The same as step 302, and details are not described herein again.

It should be noted that the receiving end is a proxy server supporting multipath TCP, and the server of the transmitting end of the transmitting end does not support multipath TCP.

It should be noted that the congestion control of the server at the receiving end and the communication peer is the same as the method for performing congestion control on the TCP connection in the prior art, and will not be described in detail herein.

It should be noted that, in all embodiments of the present invention, when a multipath TCP substream has been established in the first access network, if a multipath TCP substream is created in the first access network, a new multipath is created. The method of the TCP substream is the same as the step of creating a multipath TCP substream in the second access network in the foregoing embodiment, and details are not described herein.

An embodiment of the present invention provides a method for multipath TCP congestion control, where a sending end sends a data packet in at least one multipath TCP substream of the first access network, if the network node of the first access network detects When the network is about to be congested, the ECT flag in the data packet is identified by the first identifier, the CE flag. The bit is identified by the second identifier, the ECE flag is identified by the third identifier, and the C WR flag is sent to the receiving end by the fourth identifier. After receiving the data packet, the receiving end detects the CE flag of the data packet. If the second identifier is identified, congestion control is performed, that is, a new multipath TCP substream is established in the second access network where the TCP substream is not established, or congestion control is performed on the established TCP substream. In this way, congestion control is implemented before congestion occurs, data transmission efficiency is improved, and network congestion in the first access network is slowed down by creating a multipath TCP substream in the second access network.

The embodiment of the invention provides a method for multipath TCP congestion control. As shown in FIG. 6, the method includes:

601. The sending end sends a second SYN data packet to the receiving end, where the receiving end receives the second SYN data packet sent by the sending end in the first access network.

The ECE flag bit in the second SYN data packet is identified by a fifth identifier, where

The CWR flag is identified by a six identifier; and the ECT flag is different from the CE flag; the second SYN packet carries multipath capability MP_CAPABLE information; and the MP_CAPABLE is used to identify that the transmitter supports multipath TCP.

Specifically, when the sending end initially establishes the multipath TCP substream in the first access network, the ECN mechanism needs to be negotiated with the receiving end, and the sending end identifies the ECE flag of the second SYN packet by using the fifth identifier. The CWR is identified by a sixth identifier, and the ECT flag is different from the CE flag, and the ECN mechanism is negotiated with the receiving end. The first SYN data packet also carries MP_CAPABLE information, which is used to indicate that a multipath TCP substream is established in the first access network.

Optionally, the fifth identifier and the sixth identifier are represented by 1.

602. The receiving end sends a third SYN-ACK data packet to the sending end, where the sending end receives the third SYN-ACK data packet sent by the receiving end.

The ECE flag bit in the third SYN-ACK data packet is identified by a fifth identifier, and the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; The third SYN-ACK packet also carries MP_CAPABLE.

603. The sending end sends an ACK data packet to the receiving end, and the receiving end receives an ACK data packet sent by the sending end.

Specifically, after receiving the second SYN-ACK data packet, the sending end sends the response packet ACK data packet to the receiving end, so that the multipath TCP substream is established in the first access network between the transmitting end and the receiving end.

604. The sending end sends, to the receiving end, an address letter that includes the added address ADD_ADDR information. And the receiving end is configured to obtain, according to the address information, an internet protocol IP address of the sending end in the second access network.

Specifically, the ADD_ADDR information has an Internet Protocol IP address of the transmitting end in the second access network.

605. The receiving end receives the address information that is sent by the sending end and includes the information about the added address ADD_ADDR, and obtains an Internet Protocol IP address of the sending end in the second access network according to the address information.

Specifically, the receiving end acquires an Internet Protocol IP address of the sending end in the second access network by using the ADD_ADDR information of the address information.

606. The same as step 301, and details are not described herein again.

607. The same as step 101, and details are not described herein again.

608. The same as step 102, and details are not described herein again.

609. The same as step 302, and details are not described herein again.

It should be noted that the receiving end is the server of the communication peer end, that is, the server of the communication peer end supports multipath TCP.

It should be noted that the order of step 605 before step 608 and the steps 606 and 607 are not limited.

An embodiment of the present invention provides a method for multipath TCP congestion control, where a sending end sends a data packet in at least one multipath TCP substream of the first access network, if the network node of the first access network detects When the network is about to be congested, the ECT flag in the data packet is identified by the first identifier, the CE flag is identified by the second identifier, the ECE flag is identified by the third identifier, and the C WR flag is identified by the fourth identifier. The identifier is sent to the receiving end. After receiving the data packet, the receiving end detects that the CE flag of the data packet is identified by the second identifier, and then performs congestion control, that is, newly established in the second access network where the TCP substream is not established. Multipath TCP subflow or congestion control of an established TCP subflow. In this way, congestion control is implemented before congestion occurs, data transmission efficiency is improved, and network congestion in the first access network is slowed down by newly building a multipath TCP substream in the second access network.

The embodiment of the present invention provides a device for multipath TCP congestion control. As shown in FIG. 7, the method includes: a receiving unit 701, configured to receive at least one multipath transmission control protocol TCP that the transmitting end has established in the first access network. In the substream, the data packet sent by the network node of the first access network. The processing unit 702 is configured to: when the transmission ECT flag of the ECN that supports the explicit congestion notification is detected by the first identifier, where the congestion warning CE flag is identified by the second identifier, the receiving The end performs congestion control.

Specifically, the processing unit 702, as shown in FIG. 8, specifically includes: a first sending module 7021, and a first receiving module 7022.

The first sending module 7021 is configured to: when the sending end accesses the device by using the second access network, if the sending end and the device do not establish multipath in the second access network The TCP substream, in the second access network, sends a first synchronization sequence number SYN data packet to the transmitting end.

The ECE flag of the first SYN packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; The SYN data packet also carries multipath added MPJOIN information; the MPJOIN information indicates that a multipath TCP substream is added.

The first receiving module 7022 is configured to receive the first synchronization sequence number and the acknowledge SYN-ACK data packet sent by the sending end.

The ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; The SYN-ACK packet carries the MPJOIN information.

The first sending module 7021 is further configured to send an acknowledgement ACK packet to the sending end. The ACK packet carries MP_JOIN information.

The receiving unit 701 is further configured to receive the address information that is sent by the sending end and includes the added address ADD_ADDR information.

The device, as shown in FIG. 9, further includes:

The obtaining unit 703 is configured to obtain, according to the address information received by the receiving unit 701, an Internet Protocol IP address of the sending end in the second access network.

Alternatively, the processing unit 702 is specifically configured to: send, to the sending end, a first response data packet, so that the sending end performs congestion control.

At this time, the receiving unit 701 is further configured to receive, in the second access network, the first SYN data packet sent by the sending end.

The device, as shown in FIG. 10, further includes:

The first sending unit 704 is configured to send the first SYN-ACK data packet to the sending end. The receiving unit 701 is further configured to receive an ACK packet sent by the sending end.

Alternatively, the processing unit 702 is specifically configured to perform congestion control on the established multipath TCP substream, and send a second response data packet to the sending end.

The receiving unit 701 is further configured to receive the second sent by the sending end in the first access network.

SYN packet.

The device, as shown in FIG. 11, further includes:

The recording unit 707 is configured to record information about the MP_CAPABLE of the sender, a port number, and an IP address.

The second sending unit 705 is configured to send the second SYN data packet to the server of the communication peer end. The receiving unit 701 is further configured to receive a second SYN-ACK data packet sent by the server of the communication peer end.

The ECE flag of the second SYN-ACK packet is identified by a fifth identifier;

The CWR flag is a fourth identifier identifier; and the ECT flag is different from the CE flag.

The device, as shown in FIG. 11, further includes:

The detecting unit 706 is configured to detect whether the second SYN-ACK packet carries the MP_CAPABLE information.

The processing unit 702 is further configured to detect the second SYN-ACK data at the detecting unit 706. When the MP_CAPABLE information is not carried in the packet, the MP_CAPABLE is added to the second SYN-ACK packet, and the P flag of the second SYN-ACK packet is identified by the eighth identifier.

The first sending unit 704 is further configured to send the second SYN-ACK data packet to the sending end.

The receiving unit 701 is further configured to receive an ACK packet sent by the sending end.

The second sending unit 705 is further configured to send the ACK data packet to a server of the communication peer end.

The receiving unit 701 is further configured to receive the second SYN data packet that is sent by the sending end in the first access network.

The first sending unit 704 is further configured to send a third SYN-ACK data packet to the sending end. among them. The ECE flag bit in the third SYN-ACK data packet is identified by a fifth identifier, the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; The three SYN-ACK packets also carry MP_CAPABLE.

An embodiment of the present invention provides a multipath TCP congestion control apparatus. After receiving a data packet, the receiving end detects that the CE flag of the data packet is identified by the second identifier, and performs congestion control, that is, the TCP is not established. A new multipath TCP substream is established in the second access network of the substream or congestion control is performed on the established TCP substream. In this way, congestion control is implemented before congestion occurs, data transmission efficiency is improved, and network congestion in the first access network is slowed down by creating a multipath TCP substream in the second access network.

An embodiment of the present invention provides a device for multipath TCP congestion control. As shown in FIG. 12, the method includes: a sending unit 111, configured to: in a TCP substream of at least one multipath transmission control protocol that has been established in the first access network. Send a packet to the receiver.

The transmission ECT flag of the data packet supporting the explicit congestion notification ECN is identified by the first identifier, and the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier; The window halving CWR flag is identified by the fourth identifier; so that the network node of the first access network detects the network to be congested or the quality of the first access network link deteriorates, the network node passes the CE flag of the data packet The bit is changed from the seventh identifier identifier to the second identifier identifier to notify the receiving end network that the network is about to be congested or the first access network link quality is deteriorated, so that the receiving end performs congestion control. The processing unit 112 is configured to perform corresponding congestion control when the receiving end performs congestion control. Specifically, the processing unit 112, as shown in FIG. 13, includes: a receiving module 1121 and a sending module 1122.

The receiving module 1121 is configured to: when the sending end accesses the receiving end by using the second access network, if the device and the receiving end do not establish multipath in the second access network The TCP substream receives the first synchronization sequence number SYN data packet sent by the receiving end in the second access network.

The sending module 1122 is configured to send the first synchronization sequence number and the acknowledge SYN-ACK data packet to the receiving end.

The receiving module 1121 is further configured to receive an acknowledgement ACK packet sent by the receiving end. The ACK packet carries MP_JOIN information.

At this time, the sending unit 111 is further configured to send the address information including the added address ADD_ADDR information to the receiving end, so that the receiving end acquires the Internet of the sending end in the second access network according to the address information. Protocol IP address.

Alternatively, the processing unit 112 is specifically configured to receive the first response data packet sent by the receiving end.

In this case, the sending unit 111 is further configured to: if the sending end accesses the receiving end by using the second access network, if the sending end and the receiving end are not in the second access network Establish multipath

The TCP substream, in the second access network, sends the first SYN data packet to the receiving end.

The device, as shown in FIG. 14, further includes: The receiving unit 113 is configured to receive the first SYN-ACK data packet sent by the receiving end. The sending unit 111 is further configured to send the ACK packet to the receiving end.

The processing unit 112 is further configured to perform congestion control on the established multipath TCP substream.

Alternatively, the processing unit 112 is specifically configured to receive the second response data packet sent by the receiving end.

The sending unit 111 is further configured to send the second SYN data packet to the receiving end.

The receiving unit 113 is further configured to receive a second SYN-ACK data packet or a third SYN-ACK data packet sent by the receiving end.

The ECE flag of the second SYN-ACK packet is identified by a fifth identifier; the CWR flag is identified by a fourth identifier; and the ECT flag is different from the CE flag; The second SYN-ACK packet carries the MP_CAPABLE information; the P flag of the second SYN-ACK packet is identified by a ground eight identifier; and the ECE flag in the third SYN-ACK packet is used by And the CWR is identified by the fourth identifier; and the ECT flag is different from the CE flag; the third SYN-ACK packet further carries the MP_CAPABLE information.

The sending unit 111 is further configured to send an ACK packet to the receiving end.

An embodiment of the present invention provides a multipath TCP congestion control apparatus, where a transmitting end sends a data packet in an established at least one multipath TCP substream of a first access network, if the network node of the first access network detects When the network is about to be congested, the ECT flag in the data packet is identified by the first identifier, the CE flag is identified by the second identifier, the ECE flag is identified by the third identifier, and the C WR flag is identified by the fourth identifier. The identifier is sent to the receiving end, so that after receiving the data packet, the receiving end detects that the CE flag of the data packet is identified by the second identifier, and then performs congestion control. In this way, it is achieved before the congestion occurs. Congestion control improves the efficiency of data transmission.

An embodiment of the present invention provides a device for multipath TCP congestion control, as shown in FIG. 15, including: a receiver 121, configured to receive, by a receiving end, at least one multipath transmission control established by a transmitting end in a first access network. In the protocol TCP substream, the data packet sent by the network node of the first access network.

The processor 122 is configured to: if the packet is detected, support an explicit congestion notification to transmit the ECN

The ECT flag is identified by the first identifier; the congestion warning CE flag is identified by the second identifier, and the receiving end performs congestion control.

Specifically, the processor is specifically configured to: if the sending end accesses the receiving end by using the second access network, if the sending end and the receiving end are not established in the second access network, In the multipath TCP substream, in the second access network, the first synchronization sequence number SYN data packet is sent to the transmitting end.

The receiver 121 is further configured to receive the first synchronization sequence number and the acknowledge SYN-ACK data packet sent by the sending end.

The processor 122 is further configured to send an acknowledgement ACK packet to the sending end.

The ACK packet carries MP_JOIN information.

The receiver 121 is further configured to receive address information that is sent by the sending end and includes the added address ADD_ADDR information.

The processor 122 is further configured to obtain an Internet Protocol IP address of the sending end in the second access network according to the address information received by the receiver 121.

Alternatively, the processor 122 is specifically configured to send, by the receiving end, the first response data packet to the sending end, so that the sending end performs congestion control. The ECT flag of the first response data packet is identified by a first identifier, and the CE flag bit is identified by a seventh identifier; the ECE flag bit is identified by a fifth identifier; the C WR flag bit Identified with the fourth identifier.

The receiver 121 is further configured to: in the second access network, receive the first SYN data packet sent by the sending end.

The processor 122 is further configured to send the first SYN-ACK data packet to the sending end. The receiver 121 is further configured to receive an ACK packet sent by the sending end.

Alternatively, the processor 122 is specifically configured to perform congestion control on the established multipath TCP substream, and send a second response data packet to the transmitting end.

The receiver 121 is further configured to receive the second SYN data packet sent by the sending end in the first access network.

The processor 122 is further configured to: record related information, a port number, and an IP address of the MP_CAPABLE of the sending end.

The above device, as shown in FIG. 16, further includes:

The sender 123 is configured to send the second SYN data packet to a server of the communication peer.

The receiver 121 is further configured to receive a second SYN-ACK packet sent by the server of the communication peer.

The ECE flag of the second SYN-ACK packet is identified by a fifth identifier;

The processor 122 is further configured to detect whether the second SYN-ACK packet carries MP_CAPABLE information.

The processor 122 is further configured to: when the second SYN-ACK packet is detected, not carried In the MP_CAPABLE message, the MP_CAPABLE is added to the second SYN-ACK packet, and the P flag of the second SYN-ACK packet is identified by the eighth identifier.

The transmitter 123 is further configured to send the second SYN-ACK data packet to the sending end. The receiver 122 is further configured to receive an ACK packet sent by the sending end.

The transmitter 123 is further configured to send the ACK packet to a server of the communication peer. The receiver 122 is further configured to receive the second SYN data packet sent by the sending end in the first access network.

The transmitter 122 is further configured to send a third SYN-ACK packet to the sending end.

The receiver 122 is further configured to receive an ACK packet sent by the sending end.

The embodiment of the present invention provides a device for multipath TCP congestion control. As shown in FIG. 17, the method includes: a transmitter 141, configured to: in a TCP substream of at least one multipath transmission control protocol that has been established in the first access network. Send a packet to the receiver.

The transmission ECT flag of the data packet supporting the explicit congestion notification ECN is identified by the first identifier, and the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier; The window halving CWR flag is identified by the fourth identifier; so that the network node of the first access network detects the network to be congested or the quality of the first access network link deteriorates, the network node passes the CE flag of the data packet The bit is changed from the seventh identifier identifier to the second identifier identifier to notify the receiving end network that the network is about to be congested or the first access network link quality is deteriorated, so that the receiving end performs congestion control.

The processor 142 is configured to perform corresponding congestion control when the receiving end performs congestion control. Specifically, the processor 142 is configured to: if the sending end accesses the receiving end by using the second access network, if the device and the receiving end are not established in the second access network, The path TCP substream receives the first synchronization sequence number SYN data packet sent by the receiving end in the second access network.

The processor 142 is further configured to send the first synchronization sequence number and the acknowledge SYN-ACK data packet to the receiving end.

The processor 142 is further configured to receive an acknowledgement ACK packet sent by the receiving end.

The ACK packet carries MP_JOIN information.

The transmitter 141 is further configured to send the address information including the added address ADD_ADDR information to the receiving end, so that the receiving end acquires the Internet Protocol IP address of the sending end in the second access network according to the address information.

Alternatively, the processor 142 is specifically configured to receive the first response data packet sent by the receiving end. The ECT flag bit of the first response data packet is identified by a first identifier, and the CE flag bit is identified by a seventh identifier; the ECE flag bit is identified by a fifth identifier; The fourth identifier is identified.

The transmitter 141 is further configured to: when the sending end accesses the receiving end by using the second access network, if the sending end and the receiving end do not establish multipath TCP in the second access network The substream, in the second access network, sends the first SYN data packet to the receiving end.

The device, as shown in FIG. 18, further includes:

The receiver 143 is configured to receive the first SYN-ACK data packet sent by the receiving end. The transmitter 141 is further configured to send the ACK packet to the receiving end.

The processor 142 is further configured to perform congestion control on the established multipath TCP substream.

Alternatively, the processor 142 is specifically configured to receive the second response data packet sent by the receiving end. The ECT flag of the second response packet is identified by a first identifier, the CE flag is identified by a seven identifier; the ECE flag is identified by a third identifier; and the C WR flag is used by The sixth identifier is identified.

The transmitter 141 is further configured to send the second SYN data packet to the receiving end.

The CWR flag is identified by a six identifier; and the ECT flag is different from the CE flag; the second SYN packet carries multipath capability MP_CAPABLE information; and the MP_CAPABLE is used to identify that the transmitter supports multipath TCP

The receiver 143 is further configured to receive a second SYN-ACK data packet or a third SYN-ACK data packet sent by the receiving end.

The ECE flag of the second SYN-ACK packet is identified by a fifth identifier; the CWR flag is identified by a fourth identifier; and the ECT flag is different from the CE flag; The second SYN-ACK packet also carries MP_CAPABLE information; the P flag of the second SYN-ACK packet is identified by a ground eight identifier. The ECE flag bit in the third SYN-ACK data packet is identified by a fifth identifier, the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; The three SYN-ACK packets also carry MP_CAPABLE information.

The transmitter 141 is further configured to send an ACK packet to the receiving end.

The embodiment of the present invention provides a system for multipath TCP congestion control. As shown in FIG. 19, the method includes: a transmitting end 161, a network node 162, and a receiving end 163.

The transmitting end 161 is configured to receive, by the receiving end 163, a device for multipath TCP congestion control provided by the foregoing embodiment, in a device for multipath TCP congestion control according to the foregoing embodiment. An embodiment of the present invention provides another system for multipath TCP congestion control. As shown in FIG. 20, the method includes: a transmitting end 201, a network node 202, and a receiving end 203.

The transmitting end 201 is another multipath TCP congestion control device according to the above embodiment. The receiving end 203 is another multipath TCP congestion control device according to the above embodiment. The embodiment of the invention provides a method, a device and a system for multipath TCP congestion control, where a sender sends a data packet in at least one multipath TCP substream of the first access network, if the first access network The network node detects that the network is about to be congested, and identifies the ECT flag in the data packet with the first identifier, the CE flag is identified by the second identifier, the ECE flag is identified by the third identifier, and the C WR flag is used. The fourth identifier is sent to the receiving end. After receiving the data packet, the receiving end detects that the CE flag of the data packet is identified by the second identifier, and performs congestion control, that is, the second connection of the TCP substream is not established. Add a new multipath TCP subflow to the network or perform congestion control on the established TCP subflow. In this way, congestion control is implemented before congestion occurs, data transmission efficiency is improved, and network congestion in the first access network is slowed down by creating a multipath TCP substream in the second access network. The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of protection of the claims.

Claims

Rights request

A method for multipath TCP congestion control, comprising:

Receiving, by the receiving end, a data packet sent by the network node of the first access network in the TCP substream of the at least one multipath transmission control protocol that the transmitting end has established in the first access network;

The method according to claim 1, wherein the performing congestion control comprises: if the transmitting end accesses the receiving end by using a second access network, if the sending end is The receiving end does not establish a multipath TCP substream in the second access network, and in the second access network, the receiving end sends a first synchronization sequence number SYN data packet to the sending end; the first SYN The ECE flag of the data packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; the first SYN packet is also carried Adding MPJOIN information to the multipath; the MPJOIN means adding a multipath TCP substream;

Receiving, by the receiving end, the first synchronization sequence number and the acknowledge SYN-ACK data packet sent by the sending end; the ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; Identifying with a fourth identifier; and the ECT flag is different from the CE flag; the SYN-ACK packet carries MPJOIN information;

The receiving end sends an acknowledgement ACK packet to the sending end; the ACK packet carries MPJOIN information.

The method according to claim 2, wherein before the receiving end sends the message for establishing the multipath TCP substream to the sending end, the method further includes:

The receiving end receives the address information that is sent by the sending end and includes the added address ADD_ADDR information, and obtains the Internet Protocol IP address of the sending end in the second access network according to the address information.

The method according to claim 1, wherein the performing congestion control comprises: the receiving end sending a first response data packet to the sending end, so that the sending end performs congestion control; The ECT flag of the first response packet is identified by a first identifier, the CE flag is identified by a seventh identifier; the ECE flag is identified by a fifth identifier; and the C WR flag is identified by a fourth identifier Identification mark.

The method according to claim 4, after the receiving end sends the first response data packet to the sending end, the method further includes:

In the second access network, the receiving end receives the first SYN data packet sent by the sending end;

Sending, by the receiving end, the first SYN-ACK data packet to the sending end;

The receiving end receives an ACK data packet sent by the sending end.

The method according to claim 1, wherein the performing congestion control comprises: performing congestion control on the established multipath TCP substream, and sending a second response data packet to the transmitting end; The ECT flag bit of the response data packet is identified by a first identifier, the CE flag bit is identified by a seven identifier; the ECE flag bit is identified by a third identifier; the C WR flag bit is identified by a sixth identifier.

The method according to any one of claims 1, 2, and 4-5, wherein at the receiving end, at least one multipath transmission control protocol TCP sub-network that the transmitting end has established in the first access network is received. In the stream, before the data packet sent by the network node of the first access network, the method further includes:

Receiving, by the receiving end, the second SYN data packet sent by the sending end in the first access network, recording related information, port number, and IP address of the MP_CAPABLE of the sending end; and forwarding the second SYN data packet a server to the opposite end of the communication; the ECE flag bit in the second SYN data packet is identified by a fifth identifier, the C WR flag bit is identified by a six identifier; and the ECT flag bit and the CE flag bit are Different; the second SYN data packet carries multipath capability MP_CAPABLE information; the MP_CAPABLE is used to identify that the sender supports multipath TCP;

Receiving, by the receiving end, a second SYN-ACK data packet sent by the server of the communication peer; the ECE flag bit of the second SYN-ACK data packet is identified by a fifth identifier; a fourth identifier of the CWR flag bit Identifying; and the ECT flag is different from the CE flag;

And if the receiving end detects that the second SYN-ACK data packet does not carry the MP_CAPABLE information, adding the MP_CAP ABLE to the second SYN-ACK data packet, and identifying the first The P flag of the second SYN-ACK packet;

The receiving end sends the second SYN-ACK data packet to the sending end;

The receiving end receives the ACK data packet sent by the sending end, and sends the ACK data packet to the server of the communication peer end.

The method according to any one of claims 1-6, wherein the receiving end receives at least one multipath transmission control protocol TCP substream that has been established by the transmitting end in the first access network, Before the data packet sent by the network node of the first access network, the method further includes:

Receiving, by the receiving end, the second SYN data packet sent by the sending end in the first access network; the receiving end sending a third SYN-ACK data packet to the sending end; the third SYN- The ECE flag bit in the ACK packet is identified by a fifth identifier, the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; the third SYN-ACK packet Also carries MP_CAPABLE;

The receiving end receives an ACK data packet sent by the sending end.

A method for multipath TCP congestion control, comprising:

The transmitting end sends a data packet to the receiving end in the at least one multipath transmission control protocol TCP substream that has been established in the first access network; the data packet supports the explicit identifier of the transmission ECT flag of the ECN by using the first identifier The identifier, the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier; the congestion window is halved, and the CWR flag is identified by the fourth identifier, so that the network node of the first access network is When detecting that the network is about to be congested or the quality of the first access network link is deteriorated, the network node notifies the receiving end network that the network is about to be congested by changing the CE flag of the data packet from the seventh identifier identifier to the second identifier identifier. The quality of the first access network link is deteriorated, so that the receiving end performs congestion control;

If the receiving end performs congestion control, the transmitting end performs corresponding congestion control.

The method according to claim 9, wherein the transmitting end performing corresponding congestion control includes: if the sending end accesses the receiving end through the second access network, if the sending And the receiving end does not establish a multipath TCP substream in the second access network, and in the second access network, the sending end receives the first synchronization sequence number SYN data packet sent by the receiving end; The ECE flag of the first SYN packet is identified by a fifth identifier; the CWR is identified by a sixth identifier; and the ECT flag is different from the CE flag; the first SYN data The packet further carries multipath added MPJOIN information; the MPJOIN indicates that a multipath TCP substream is added; the sending end sends a first synchronization sequence number and an acknowledge SYN-ACK data packet to the receiving end; The ECE flag bit in the SYN-ACK data packet is identified by a fifth identifier; the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; the SYN-ACK The data packet carries MP_JOIN information;

The method according to claim 10, further comprising: before the sending end receives the message of the multipath TCP substream sent by the receiving end, the method further includes:

The sending end sends the address information including the added address ADD_ADDR information to the receiving end, so that the receiving end acquires the Internet protocol IP address of the sending end in the second access network according to the address information.

The method according to claim 9, wherein the transmitting end performs corresponding congestion control, including:

Receiving, by the sending end, the first response data packet sent by the receiving end; the ECT flag bit of the first response data packet is identified by a first identifier, and the CE flag bit is identified by a seventh identifier; the ECE The flag bit is identified by a fifth identifier; the CWR flag bit is identified by a fourth identifier.

The method according to claim 12, after the receiving end receives the first response data sent by the receiving end, the method further includes: accessing, by the second access network, the sending end In the case of the receiving end, if the transmitting end and the receiving end do not establish a multipath TCP substream in the second access network, in the second access network, the transmitting end sends the receiving end to the receiving end. The first SYN data packet;

Receiving, by the sending end, the first SYN-ACK data packet sent by the receiving end;

The transmitting end sends the ACK data packet to the receiving end.

The method according to claim 12, after the receiving end receives the first response data sent by the receiving end, the method further includes:

The transmitting end performs congestion control on the established multipath TCP substream.

The transmitting end receives the second response data packet sent by the receiving end; the ECT flag bit of the second response data packet is identified by a first identifier, and the CE flag bit is identified by a seven identifier; the ECE flag The bit is identified by a third identifier; the CWR flag bit is identified by a sixth identifier.

The method according to any one of claims 9 to 15, wherein before the transmitting end sends a data packet to the receiving end in the TCP substream of the multipath transmission control protocol established by the first access network , Also includes:

The sending end sends a second SYN data packet to the receiving end; the ECE flag bit in the second SYN data packet is identified by a fifth identifier, and the C WR flag bit is identified by a six identifier; The ECT flag is different from the CE flag; the second SYN packet carries multipath capability MP_CAPABLE information; the MP_CAP ABLE is used to identify that the sender supports multipath TCP; and the sender receives the reception. a second SYN-ACK packet or a third SYN-ACK packet sent by the terminal; the ECE flag of the second SYN-ACK packet is identified by a fifth identifier; and the CWR flag is identified by a fourth identifier; And the ECT flag bit is different from the CE flag bit; the second SYN-ACK data packet further carries MP_CAPABLE information; and the P flag bit of the second SYN-ACK data packet is identified by a ground eight identifier; The ECE flag bit in the third SYN-ACK data packet is identified by a fifth identifier, the CWR is identified by a fourth identifier; and the ECT flag bit is different from the CE flag bit; SYN-ACK packet also carries MP_C AP ABLE Information; the sending end to the receiving end sends ACK packet.

17. A device for multipath TCP congestion control, comprising:

a receiving unit, configured to receive, by the sending end, a data packet sent by the network node of the first access network in the at least one multipath transmission control protocol TCP substream that has been established by the first access network;

a processing unit, configured to identify, by using a first identifier, a transmission ECT flag of the ECN that supports the explicit congestion notification of the data packet; where the congestion warning CE flag is identified by a second identifier, the receiving end Congestion control is performed; wherein the ECN feedback ECE flag of the data packet is identified by a third identifier; the congestion window is halved and the CWR flag is identified by a fourth identifier.

The device according to claim 17, wherein the processing unit specifically includes: a first sending module, a first receiving module;

The first sending module is configured to: when the sending end accesses the device by using the second access network, if the sending end and the device do not establish multipath TCP in the second access network a substream, in the second access network, sending a first synchronization sequence number SYN data packet to the transmitting end; the ECE flag bit of the first SYN data packet is identified by a fifth identifier; Identifying with the sixth identifier; and the ECT flag is different from the CE flag; the first SYN packet further carries multipath added MPJOIN information; the MPJOIN information indicates adding a multipath TCP substream The first receiving module is configured to receive the first synchronization sequence number and the acknowledgement sent by the sending end a SYN-ACK data packet; the ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; the C WR is identified by a fourth identifier; and the ECT flag bit and the CE The flag bits are different; the SYN-ACK data packet carries the MPJOIN information;

The first sending module is further configured to send an acknowledgement ACK packet to the sending end, where the ACK packet carries MP_JOIN information.

19. Apparatus according to claim 18 wherein:

The receiving unit is further configured to receive address information that is sent by the sending end and includes the added address ADD_ADDR information;

The device further includes:

And an obtaining unit, configured to acquire, according to the address information received by the receiving unit, an Internet Protocol IP address of the sending end in the second access network.

The device according to claim 17, wherein the processing unit is configured to: send, to the sending end, a first response data packet, so that the sending end performs congestion control; The ECT flag of the data packet is identified by a first identifier, the CE flag bit is identified by a seventh identifier; the ECE flag bit is identified by a fifth identifier; the CWR flag bit is identified by a fourth identifier.

The device according to claim 20, wherein the receiving unit is further configured to receive, in the second access network, the first SYN data packet sent by the sending end;

The device further includes:

a first sending unit, configured to send the first SYN-ACK data packet to the sending end, where the receiving unit is further configured to receive an ACK data packet sent by the sending end.

The device according to claim 17, wherein the processing unit is configured to: perform congestion control on the established multipath TCP substream, and send a second response data packet to the sending end; The ECT flag of the second response packet is identified by a first identifier, the CE flag is identified by a seven identifier; the ECE flag is identified by a third identifier; the C WR flag is identified by a sixth identifier .

The device according to any one of claims 17, 18, and 20-22, wherein the receiving unit is further configured to receive the second SYN data that is sent by the sending end in the first access network. a packet; the ECE flag bit in the second SYN data packet is identified by a fifth identifier, the CWR flag bit is identified by a six identifier; and the ECT flag bit is different from the CE flag bit; Two SYN data The packet carries the multipath capability MP_CAPABLE information; the MP_CAPABLE is used to identify that the sender supports multipath TCP;

The device further includes:

a recording unit, configured to record information about the MP_CAPABLE of the sender, a port number, and an IP address;

a second sending unit, configured to send the second SYN data packet to a server of the communication peer end; the receiving unit is further configured to receive a second SYN-ACK data packet sent by the server of the communication peer end; The ECE flag of the SYN-ACK packet is identified by a fifth identifier; the CWR flag is identified by a fourth identifier; and the ECT flag is different from the CE flag;

The device further includes:

a detecting unit, configured to detect whether the second SYN-ACK packet carries MP_CAPABLE information;

The processing unit is further configured to: when the detecting unit detects that the second SYN-ACK data packet does not carry the MP_CAPABLE information, add the MP_CAPABLE to the second SYN-ACK data packet, and use the eighth The identifier identifies a P flag of the second SYN-ACK packet; the first sending unit is further configured to send the second SYN-ACK data packet to the sending the receiving unit, and further Receiving an ACK packet sent by the sending end;

The second sending unit is further configured to send the ACK data packet to a server of the communication peer end.

The device according to any one of claims 17 to 22, further comprising: the receiving unit, further configured to receive the second SYN sent by the sending end in the first access network data pack;

The first sending unit is further configured to send a third SYN-ACK data packet to the sending end; the ECE flag bit in the third SYN-ACK data packet is identified by a fifth identifier, where the CWR is Identifying by the fourth identifier; and the ECT flag is different from the CE flag; the third SYN-ACK packet further carries MP_CAPABLE;

The receiving unit is further configured to receive an ACK data packet sent by the sending end.

A device for 25 types of multipath TCP congestion control, comprising:

a sending unit, configured to: at least one multipath transmission control protocol TCP sub-establishment established in the first access network Sending a data packet to the receiving end in the stream; supporting the explicit congestion notification of the data packet to notify the ECN of the transmission ECT flag is identified by the first identifier, and the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is used a third identifier identifier; a congestion window halving CWR flag is identified by a fourth identifier; so that the network node of the first access network detects a network to be congested or the first access network link quality deteriorates, the network node Changing the CE flag bit of the data packet from the seventh identifier identifier to the second identifier identifier to notify the receiving end network that the network is about to be congested or the quality of the first access network link is deteriorated, so that the receiving end performs congestion control. ;

The processing unit is configured to perform corresponding congestion control when the receiving end performs congestion control.

The device according to claim 25, wherein the processing unit comprises: a receiving module and a sending module;

The receiving module is configured to: when the sending end accesses the receiving end by using the second access network, if the apparatus and the receiving end do not establish a multipath TCP subflow in the second access network Receiving, in the second access network, a first synchronization sequence number SYN data packet sent by the receiving end; the ECE flag bit of the first SYN data packet is identified by a fifth identifier; a sixth identifier identifier; and the ECT flag bit is different from the CE flag bit; the first SYN data packet further carries multipath added MPJOIN information; the MPJOIN indicates that a multipath TCP substream is added; a sending module, configured to send a first synchronization sequence number and an acknowledge SYN-ACK data packet to the receiving end; the ECE flag bit in the first SYN-ACK data packet is identified by a fifth identifier; The CWR is identified by a fourth identifier; and the ECT flag is different from the CE flag; the SYN-ACK packet carries MPJOIN information;

The receiving module is further configured to receive an acknowledgement ACK packet sent by the receiving end, where the ACK packet carries MP_JOIN information.

27. Apparatus according to claim 26 wherein:

The sending unit is further configured to send the address information including the added address ADD_ADDR information to the receiving end, so that the receiving end acquires the Internet Protocol IP address of the sending end in the second access network according to the address information.

The device according to claim 25, wherein the processing unit is configured to: receive a first response data packet sent by the receiving end; and use the first ECT flag of the first response data packet An identifier identifier, the CE flag bit is identified by a seventh identifier; the ECE flag bit is identified by a fifth identifier; and the C WR flag bit is identified by a fourth identifier.

29. Apparatus according to claim 28 wherein:

The sending unit is further configured to: when the sending end accesses the receiving end by using the second access network, if the sending end and the receiving end do not establish multipath TCP in the second access network a substream, in the second access network, sending the first SYN data packet to the receiving end;

The device further includes:

a receiving unit, configured to receive the first SYN-ACK data packet sent by the receiving end, where the sending unit is further configured to send the ACK data packet to the receiving end.

30. Apparatus according to claim 28 wherein:

The processing unit is further configured to perform congestion control on the established multipath TCP substream.

The device according to claim 25, wherein the processing unit is configured to: receive a second response data packet sent by the receiving end; and use the first ECT flag of the second response data packet An identifier identifier, the CE flag bit is identified by a seven identifier; the ECE flag bit is identified by a third identifier; and the CWR flag bit is identified by a sixth identifier.

32. The method of any of claims 25-31, wherein

The sending unit is further configured to send a second SYN data packet to the receiving end; the ECE flag bit in the second SYN data packet is identified by a fifth identifier, and the CWR flag bit is identified by a six identifier And the ECT flag is different from the CE flag; the second SYN packet carries multipath capability MP_CAPABLE information; the MP_CAPABLE is used to identify that the sender supports multipath TCP;

The receiving unit is further configured to receive a second SYN-ACK data packet or a third SYN-ACK data packet sent by the receiving end, where the ECE flag bit of the second SYN-ACK data packet uses a fifth identifier a second identifier of the C WR flag; and the ECT flag is different from the CE flag; the second SYN-ACK packet further carries MP_CAPABLE information; the second SYN-ACK The P flag of the data packet is identified by a ground eight identifier; the ECE flag bit in the third SYN-ACK data packet is identified by a fifth identifier, the CWR is identified by a fourth identifier; and the ECT flag The bit is different from the CE flag bit; the third SYN-ACK packet further carries MP_CAPABLE information;

The sending unit is further configured to send an ACK packet to the receiving end.

33. A device for multipath TCP congestion control, comprising: a receiver, configured to receive, by the receiving end, a data packet sent by the network node of the first access network in the at least one multipath transmission control protocol TCP substream that the transmitting end has established in the first access network;

a processor, configured to: if the data packet supports the explicit congestion notification ECN, the transmission ECT flag is identified by the first identifier; the congestion warning CE flag is identified by the second identifier, and the receiving end performs congestion Control; wherein, the ECN feedback ECE flag of the data packet is identified by a third identifier; the congestion window is halved and the CWR flag is identified by a fourth identifier.

34. A device for multipath TCP congestion control, comprising:

a transmitter, configured to send, by the sending end, a data packet to the receiving end in at least one multipath transmission control protocol TCP substream that has been established in the first access network; the data packet supports an explicit congestion notification ECN transmission ECT flag bit With the first identifier, the congestion warning CE flag is identified by the seventh identifier; the ECN feedback ECE flag is identified by the third identifier; the congestion window is halved, and the CWR flag is identified by the fourth identifier; When detecting that the network is about to be congested, the network node of the network notifies the receiving end by changing the CE flag bit, so that the receiving end performs congestion control;

The processor is configured to perform corresponding congestion control when the receiving end performs congestion control.

35. A system for multipath TCP congestion control, comprising: a transmitting end, a network node, and a receiving end;

The transmitting end is a device for multipath TCP congestion control according to any one of claims 17-24;

The receiving end is a multipath TCP congestion control device according to any one of claims 25-32.

36. A system for multipath TCP congestion control, comprising: a transmitting end, a network node, and a receiving end;

The transmitting end is a device for multipath TCP congestion control according to claim 33; and the receiving end is a device for multipath TCP congestion control according to claim 34.