Receiver independent scheme for reliably transmitting data through multiple paths
By adjusting the path and judging packet loss in real time by sending the device, the problem of disorderly reception of the receiver device in multi-path transmission is solved, efficient multi-path reliable packet transmission is achieved, and the reliability and throughput of packet transmission is improved. .
Patent Information
- Application Number
- CN202280090421.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-20
- Publication Date
- 2024-11-08
AI Technical Summary
In multipath transmission, the receiver device may receive packets in an out-of-order manner, making it difficult for the sender device to decide which packet is retransmission, and multipath transmission does not always improve throughput, and the impact depends on path selection and load conditions.
The sender device determines the addition or deletion path in real time, selects the retransmission path, maintains the path information, judges packet loss based on feedback messages, and dynamically adjusts the path according to path availability and congestion control, supports selection of retransmission, independent of the receiver device.
It realizes multi-path reliable packet transmission independent of the receiver device, improves the reliability and throughput of packet transmission, simplifies path management, and avoids packet delay or loss on the path.
Smart Images

Figure CN118923068A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a receiver-independent scheme for reliably transmitting data from a sender device to a receiver device through multiple paths. The sender device of the present invention can select one of multiple paths for each of multiple data packets to be sent to the receiver device to send the data packet. The sender device of the present invention can also apply a transmission protocol using selective retransmission to perform multipath transmission of data packets. Background Art
[0002] In modern data centers, packets may be lost due to congestion. Therefore, a protocol is needed to reliably transmit packets. Examples of such protocols are transmission control protocol (TCP) and remote direct memory access (RDMA). In these protocols, the receiving device notifies the sending device which packets have been received, and the sending device decides which packets must be retransmitted. In some cases, to increase throughput and reduce latency, the sending device can split its traffic to the receiving device over multiple paths, which is called "multipath transmission".
[0003] However, when using this multipath transmission, packets may be received out of order at the receiving device, which complicates the decision of which packet to retransmit and when to retransmit it. Therefore, multipath transmission does not always improve throughput, and its impact on throughput depends on which paths are used, how loaded those paths are, and how loaded alternative paths are. Summary of the invention
[0004] The present invention and its solutions are further based on the following considerations.
[0005] The sending device can determine in real time whether it is beneficial to add a path or remove a path in order to use multipath transmission in an optimal manner. It may be more efficient to have the sending device make such decisions without involving the receiving device, in which case the receiving device is agnostic about whether to use one path or multiple paths and which paths to use.
[0006] The present invention aims to propose a scheme combining reliable transmission of data packets with multipathing, so that the receiving device does not have to know whether the sending device uses one path or multiple paths. The goal is that the receiving device can work in the same way in both cases. Therefore, the present invention relates to scenarios in which the sending device and the receiving device support selective retransmission. Another goal is to enable the sending device to decide how many paths to use without having to coordinate with the receiving device. Furthermore, the present invention aims to enable the sending device to dynamically change the path used, for example, based on the availability of the path and congestion control considerations.
[0007] This is achieved by the measures of the invention described in the independent claim. Advantageous implementations are defined in the dependent claims.
[0008] A first aspect of the present invention provides a sending device for sending a data packet to a receiving device, wherein the sending device is used to: determine a set of one or more paths between the sending device and the receiving device; for each data packet, select a path in the path set for sending the data packet to the receiving device; for each data packet, maintain path information, the path information indicating the selected path used to send the data packet to the receiving device; receive a feedback message from the receiving device, wherein the feedback message includes status information of each of the one or more data packets; based on the feedback message, determine whether a missing data packet should be considered lost; based on the path information of the missing data packet and the status information of one or more other data packets transmitted to the receiving device on the same path as the missing data packet, determine whether to retransmit the missing data packet.
[0009] The sending device is used to determine whether the missing data packet should be considered lost based on the path information of the missing data packet and the status information of the one or more other data packets included in the feedback message for transmission on the same path as the missing data packet. The sending device decides whether and when to retransmit the missing data packet based on the rules of the underlying single-path transmission protocol. It should be noted that the missing data packet may be a data packet that has not been received at the receiving device despite the fact that a data packet with a higher sequence number has been received. The missing data packet may be considered lost by the sending device, in which case the sending device may retransmit the missing data packet. However, due to the possibility of one or more data packet transmission paths, the sending device does not necessarily have to consider every missing data packet at the receiving device as lost.
[0010] Thus, the sender device of the first aspect may support multipath selective retransmission, which involves retransmitting missing packets that are considered lost, and thus provides a scheme for reliably transmitting packets over multiple paths. The receiver device in the present invention may be independent of the selected path, and need not know whether the sender device uses a single path or multiple paths. In both cases, the functionality of the receiver device may be the same, and the receiver device may be a conventional receiver device supporting a protocol based on standard (single path) selective retransmission.
[0011] The sender device can decide how many paths to use without coordinating with the receiver device. In addition, the sender device can dynamically change the set of paths used based on the availability of the paths and based on one or more congestion control considerations. The sender device can decide which data packet to send on which path in the set of paths based on path-by-path congestion control or in any other way. Only one set of sequence number spaces can be used, i.e., each data packet can only have one sequence number. This may mean that only one data packet is assigned a specific sequence number, i.e., a specific sequence number will not be assigned to more than two data packets. This may be different from other multipath transport protocols (such as multipath TCP), which use two sequence number spaces, i.e., each data packet has two sequence numbers, one sequence number for each path and one sequence number for the entire connection.
[0012] In an implementation manner of the first aspect, the status information of each data packet indicates whether the data packet has been received by the receiving device or lost at the receiving device.
[0013] Therefore, the sending device may determine the missing data packets that are considered lost based on the state information, and may also decide whether to retransmit the data packets that are considered lost based on the state information.
[0014] In an implementation of the first aspect, if the feedback message indicates that a data packet with a sequence number greater than the sequence number of the missing data packet has been received at the receiving device, the sending device is used to: if the received data packet is sent to the receiving device on a different path from the missing data packet, the missing data packet is not considered lost and the missing data packet is not retransmitted.
[0015] Although the missing data packets are only temporarily lost (not completely lost), this can prevent the missing data packets from being retransmitted because the missing data packets are sent over a different path.
[0016] In one implementation of the first aspect, if the received data packet is sent to the receiving device on the same path as the missing data packet, and if the underlying transmission protocol used to send the data packet requires retransmission, the sending device is used to: treat the missing data packet as lost and retransmit the missing data packet.
[0017] In this case, the missing packets are considered lost and retransmitted for reliability reasons.
[0018] In an implementation of the first aspect, the sending device is configured to retransmit the missing data packet on a path that is the same as a path used to transmit the data packet to the receiving device.
[0019] This simplifies tracking packets sent over different paths.
[0020] In an implementation of the first aspect, the sending device is used to: receive another feedback message from the receiving device, wherein the other feedback message indicates that another received data packet with a sequence number greater than the sequence number of the missing data packet has been received at the receiving device; if the other received data packet is sent to the receiving device on the same path as the missing data packet, and if the underlying transmission protocol used to send the data packet requires retransmission, then the missing data packet is regarded as lost and the missing data packet is retransmitted.
[0021] That is, for each received feedback message, which may be received from the receiving device periodically or after certain events, the sending device may re-evaluate whether to consider the missing data packets as lost and retransmit the missing data packets accordingly.
[0022] In an implementation manner of the first aspect, the sending device is configured to: in order to determine the path set, select the one or more paths from all available paths between the sending device and the receiving device.
[0023] In an implementation manner of the first aspect, the sending device is configured to determine the path set based on a result of performing path-by-path congestion control on available paths between the sending device and the receiving device.
[0024] This prevents packets sent on these paths from being delayed or lost due to congestion.
[0025] In an implementation of the first aspect, the sending device is configured to: select, for each data packet, a path for sending the data packet to the receiving device based on one or more congestion control considerations.
[0026] For example, the sending device may determine which path to send a particular data packet on based on considerations about the particular data packet (e.g., priority) and / or considerations about the path (e.g., current congestion, time required to traverse the path, etc.).
[0027] In an implementation manner of the first aspect, the sending device is used to add a new path to the path set.
[0028] In an implementation manner of the first aspect, the sending device is used to delete a path from the path set.
[0029] In an implementation of the first aspect, the sending device is used to: in order to delete the path from the path set: stop sending data packets on the path to be deleted; retransmit any missing data packets on the path to be deleted; if all data packets transmitted or retransmitted on the path to be deleted are received at the receiving device, delete the path to be deleted from the path set.
[0030] This allows the path to be deleted without affecting the transmission of the data packet.
[0031] In an implementation of the first aspect, the sending device is configured to: if a path used to retransmit one or more missing data packets fails, retransmit the one or more missing data packets on one or more other paths in the path set.
[0032] Therefore, the reliability of sending the data packet is improved.
[0033] In an implementation manner of the first aspect, the feedback message is an acknowledgment (ACK) message, a negative ACK (NACK) message, or a selective ACK (SACK) message.
[0034] A second aspect of the present invention provides a method and device for sending a data packet from a sending device to a receiving device, the method comprising: determining a set of one or more paths between the sending device and the receiving device; for each data packet, selecting a path in the path set for sending the data packet to the receiving device; for each data packet, maintaining path information, the path information indicating the selected path used to send the data packet to the receiving device; receiving a feedback message from the receiving device, wherein the feedback message includes status information of each of the one or more data packets; based on the feedback message, determining whether a missing data packet should be considered lost; and determining whether to retransmit the missing data packet based on the path information of the missing data packet and the status information of one or more other data packets transmitted to the receiving device on the same path as the missing data packet.
[0035] In an implementation manner of the second aspect, the status information of each data packet indicates whether the data packet has been received by the receiving device or lost at the receiving device.
[0036] The method may include determining missing packets based on the status information, and may also determine whether to consider the missing packets lost and retransmit the missing packets accordingly based on the status information.
[0037] In an implementation of the second aspect, if the feedback message indicates that a data packet with a sequence number greater than the sequence number of the missing data packet has been received at the receiving device, the method includes: if the received data packet is sent to the receiving device on a different path from the missing data packet, the missing data packet is not considered lost, and the missing data packet is not retransmitted.
[0038] In an implementation of the second aspect, if the received data packet is sent to the receiving device on the same path as the missing data packet, and if the underlying transport protocol used to send the data packet requires retransmission, the method includes: treating the missing data packet as lost and retransmitting the missing data packet.
[0039] In an implementation of the second aspect, the method includes retransmitting the missing data packet over the same path as the path used to first transmit the data packet to the recipient device.
[0040] In an implementation of the second aspect, the method includes: receiving another feedback message from the receiving device, wherein the other feedback message indicates that another received data packet with a sequence number greater than the sequence number of the missing data packet has been received at the receiving device; if the other received data packet is sent to the receiving device on the same path as the missing data packet, and if the underlying transmission protocol used to send the data packet requires retransmission, then the missing data packet is regarded as lost and the missing data packet is retransmitted.
[0041] In an implementation manner of the second aspect, the method includes: in order to determine the path set, selecting the one or more paths from all available paths between the sender device and the receiver device.
[0042] In an implementation manner of the second aspect, the method includes: determining the path set based on a result of performing path-by-path congestion control on available paths between the sender device and the receiver device.
[0043] In an implementation of the second aspect, the method includes: selecting, for each data packet, a path for sending the data packet to the recipient device based on one or more congestion control considerations.
[0044] In an implementation of the second aspect, the method includes adding a new path to the path set.
[0045] In an implementation of the second aspect, the method includes deleting a path from the path set.
[0046] In an implementation of the second aspect, the method includes: in order to delete the path from the path set, stopping sending data packets on the path to be deleted; retransmitting any missing data packets on the path to be deleted; if all data packets transmitted or retransmitted on the path to be deleted are received at the receiving device, deleting the path to be deleted from the path set.
[0047] In an implementation of the second aspect, the method includes: if a path used to retransmit one or more missing data packets fails, retransmitting the one or more missing data packets on one or more other paths in the path set.
[0048] In an implementation manner of the second aspect, the feedback message is an acknowledgment (ACK) message, a negative ACK (NACK) message, or a selective ACK (SACK) message.
[0049] The method of the second aspect and its implementation method achieve the same advantages as the sending device of the first aspect and its various implementation methods.
[0050] A third aspect of the present invention provides a computer program, which includes instructions. When the program is executed by a computer, the instructions cause the computer to execute the method according to the second aspect or any one of its implementations.
[0051] A fourth aspect of the present invention provides a storage medium storing executable program code, which, when executed by a processor, enables the method according to the second aspect or any one of its implementations to be executed.
[0052] It should be noted that all devices, elements, units and devices described in this application can be implemented in software or hardware elements or any type of combination thereof. All steps performed by various entities described in this application and the functions to be performed by various entities described are intended to refer to the corresponding entities for performing the corresponding steps and functions. Although in the description of the following specific embodiments, the specific functions or steps performed by external entities are not reflected in the description of the specific detailed elements of the entities performing the specific steps or functions, it should be clear to the technician that these methods and functions can be implemented by corresponding hardware or software elements or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] In conjunction with the accompanying drawings, the following description of specific embodiments will illustrate the above aspects and their implementation methods. In the drawings:
[0054] Figure 1 shows a sender device according to the present invention;
[0055] Figure 2 An exemplary flow chart showing a retransmission scheme used by a sending device according to the present invention;
[0056] Figure 3 A method for sending a data packet according to the present invention is shown. DETAILED DESCRIPTION
[0057] Figure 1A sender device 100 according to the present invention is shown. The sender device 100 is used to send a data packet 101 on a connection with a receiver device 110. The sender device 100 is used to use one or more paths 102 for the connection, that is, to send the data packet 101 on a path 102 or multiple paths 102. The sender device 100 can be used to select a path 101, and can change the connection from a path 102 (until the change, the data packet is sent to the receiver device 110 on this path) to a new path 102 (from the change, the data packet is sent to the receiver device 110 on this path). This change of connection can also be called rerouting of the connection. In addition, the sender device 100 can also be used to send the data packet 101 to the receiver device 110 by using an underlying transport protocol involving selective retransmission.
[0058] The sender device 100 is configured to determine a set of one or more paths 102 between the sender device 100 and the receiver device 110. For example, the sender device 100 may determine the set of paths 102 based on a result of performing path-by-path congestion control on available paths 102 between the sender device 100 and the receiver device 110. The sender device 100 may perform path-by-path congestion control.
[0059] In addition, the sender device 100 is configured to select, for each data packet 101, one of the determined set of paths 102 for sending the data packet 101 to the receiver device 110. For example, the sender device may select, for each data packet 101, a path 102 for sending the data packet 101 to the receiver device 110 based on one or more congestion control considerations. The sender device 100 may then send each data packet 101 on the respectively selected path 102.
[0060] In addition, the sender device 100 can also be used to maintain path information 103 for each data packet 101, and the path information 103 indicates the selected path 102 used to send the data packet 101 to the receiving device 110. The path information 103 can be a variable stored at the sender device 100. The path information 103 of a specific data packet 101 can associate the sequence number of the specific data packet 101 with information about the path 102 on which the specific data packet is sent or has been sent. The information can be a path number of the selected path 102, or a path index or path ID of the selected path 102.
[0061] The sender device 100 may also receive a feedback message 111 from the receiver device 110. The feedback message 111 may be an ACK message, a NACK message, or a SACK message. The feedback message 111 includes status information of each of the one or more data packets 101. For example, the status information 103 of each data packet 101 may indicate whether the data packet 101 has been received by the receiver device 110 or lost at the receiver device 110. The feedback message 111 may include a bitmap for indicating status information. For example, the bitmap may indicate which one or more sequence numbers have been received at the receiver device 110, and / or which sequence numbers of the one or more sequence numbers of the data packets have not been received, or have been received out of order.
[0062] Then, the sender device 100 is used to determine whether to regard the missing data packet as lost and whether to retransmit the missing data packet 101 according to the feedback message 111. The sender device 100 makes this decision based on at least the path information 103 of the missing data packet 101 and the state information of one or more other data packets 101 transmitted to the receiver device 110 on the same path 102 as the missing data packet 101. For example, the sender device 100 can determine that the missing data packet 101 is lost based on the path information 103 and the state information, and further determine to retransmit the missing data packet 101 based on the rules of the underlying transmission protocol.
[0063] The sender device 100 may include a processor or processing circuit (not shown) for performing, carrying out or initiating various operations of the sender device 100 described herein. The processing circuit may include hardware and / or the processing circuit may be controlled by software. The hardware may include analog circuits or digital circuits, or both analog circuits and digital circuits. The digital circuit may include components such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP) or a multi-purpose processor. The sender device 100 may also include a memory circuit for storing one or more instructions that can be executed by the processor or processing circuit (specifically, executed under the control of software). For example, the memory circuit may include a non-transitory storage medium storing executable software code that, when executed by the processor or processing circuit, causes the sender device 100 to perform various operations. In one embodiment, the processing circuit includes one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code that, when executed by one or more processors, may cause the sender device 100 to perform, implement, or initiate the operations or methods described herein.
[0064] In the present invention, the goal is to reliably transmit data divided into data packets 101 from a sender device 100 to a receiver device 110. Each data packet 101 may be assigned a sequence number, just like conventional single-path transmission.
[0065] The sender device 100 can determine the number of paths 102 used to send the data packets 101, and which paths 102 are used by each data packet 101. There are many ways to send this information to the network. For example, by changing the source port number in the user datagram protocol (UDP) header, or by adding a routing header to the data packet 101.
[0066] The sender device 100 may run a path-by-path congestion control protocol. The receiver device 110 may participate in the congestion control protocol without knowing how many paths the sender device 100 uses. For example, the receiver device 110 may send a response control packet, such as a SACK, for each received data packet 101. In addition, the receiver device 110 may indicate whether the data packet 101 has experienced congestion. Another example is that the receiver device 110 sends a control packet after having received a plurality of data packets 101, and indicates in the control packet which path each data packet 101 has been received, and optionally whether these data packets 101 have experienced congestion.
[0067] The data packets 101 may be sent on any available path 102 that the sender device 100 desires. The decision may be made at the sender device based on one or more congestion control considerations. The sender device 100 may remember the path 102 that each outstanding data packet was transmitted on via the path information 103.
[0068] For example, the receiving device 110 may only send a SACK message as the feedback message 111, for example, periodically send the SACK message, or send the SACK message after receiving N data packets, where N≥1. The SACK message may indicate congestion control information. In addition, the SACK message may indicate which data packets 101 have been received by the receiving device 110 so far. For example, the SACK message may indicate that all data packets 101 up to a certain sequence number (e.g., 120) have been received, except for data packets 101 with certain other sequence numbers (e.g., 115 and 118).
[0069] When the sender device 100 receives the SACK message, it can decide for each incomplete data packet 101 whether to regard the data packet 101 as lost and whether to retransmit the data packet 101. The decision can be made based on (a) the path 102 through which the data packet 101 is sent, (b) the state of the data packet 101 transmitted on the path 102 (indicated by the state information in the feedback message 111), and (c) the rules of the underlying transmission protocol regarding retransmission. For example, different transmission protocols may have different retransmission strategies. Missing data packets 101 can be regarded as lost by the sender device 100 and retransmitted accordingly according to the retransmission strategy of the transmission protocol used. In addition, missing data packets 101 can also be regarded as lost by the sender device 100, but are not retransmitted due to the retransmission strategy of the transmission protocol used. Alternatively, missing data packets 101 may not be regarded as lost, at least not lost, and therefore are not retransmitted.
[0070] Figure 2A flow chart showing an example of a retransmission scheme used by the sender device 100 as described above in the present invention. In the example shown, data packets 101 with sequence numbers 1 and 3 are sent via the path 102 numbered #0, and data packets 101 with sequence numbers 2 and 4 are sent via the path 102 numbered #1. In this example, if two data packets 101 are transmitted on the same path 102, the underlying transport protocol expects the two data packets to be received in the same order unless one of them is lost.
[0071] In this example, the feedback message 111 (e.g., a SACK message) indicates that all packets 101 before the packet 101 with the sequence number 1 have been correctly received. In addition, the second feedback message 111 (e.g., a second SACK message) notifies that the packet 101 with the sequence number 3 has been correctly received, but the packet 101 with the sequence number 2 has been lost. However, the sender device 100 does not retransmit the packet 101 with the sequence number 2 because the packet is transmitted on a different path, so the packet may be correctly received after the packet 101 with the sequence number 3, and thus will not be considered as lost by the sender device at this time.
[0072] However, when the third feedback message 111 (e.g., the third SACK message) notifies that the data packet with sequence number 4 is also received, but the data packet 101 with sequence number 2 is still lost, the sending device 100 regards the missing data packet 101 with sequence number 2 as lost, and retransmits the data packet 101 with sequence number 2. The retransmission is performed on the same path as the path used to transmit the original data packet 101 with sequence number 2 (for the first time).
[0073] Another feature of the present invention is that the sender device 100 can add and / or delete one or more paths 102 from the set of paths 102. For example, the sender device 100 can add and / or delete one or more paths 102 dynamically and optionally without coordination with the receiver device 110. This can be achieved in the following way.
[0074] To delete a path 102, the sender device 100 may first stop using the path 102 for new data packets 101. The sender device 100 may put the path 102 in a "suspended" state and may wait until all data packets 101 transmitted through the path 102 are correctly received. If some of the data packets 101 are considered lost, the data packets are retransmitted through the path 102. When there are no more outstanding data packets 101 belonging to the path 102, the sender device 100 may delete the path 102 from the list of active paths 102. If a path 102 fails when there are some outstanding data packets 101, the sender device 100 may stop using the path and may retransmit all outstanding data packets 101 through other paths 102. To add a path 102, the sender device 100 may use the path 102 for new data packets 101.
[0075] In the conventional multipath TCP (MP-TCP) transport protocol, the receiving device and the sending device must agree on each path 102 (called a microflow) added to a connection (called a flow). This is done using a microflow connection setup. This is different from the scheme of the present invention, where the sending device 100 and the receiving device 110 do not have to agree. Therefore, the advantage of the present invention over MP-TCP is that no such agreement and negotiation is required.
[0076] Moreover, in MP-TCP, each data packet has two sequence numbers. The first sequence number indicates the order of the data packet in its microflow, and the second sequence number indicates the order of the data packet in the entire flow. In the present invention, only one sequence number (corresponding to the first sequence number) is used for each data packet. Therefore, the present invention implements a simpler protocol.
[0077] Figure 3 A method 300 according to the present invention is shown. The method 300 may be used to send a data packet 101 from a sender device 100 to a receiver device 110. The method 300 may be performed by the sender device 100 described above.
[0078] The method 300 comprises step 301 of determining a set of one or more paths 102 between a sender device 100 and a receiver device 110. The method 300 further comprises step 302 of selecting, for each data packet 101, one path 102 from the set of paths 102 to send the data packet 101 to the receiver device 110. The method 300 comprises step 303 of maintaining (303) path information 103 for each data packet 101, the path information 103 indicating the selected path 102 used to send the data packet 101 to the receiver device 110.
[0079] In addition, the method 300 includes step 304: receiving a feedback message 111 from the receiving device 110. The feedback message 111 includes status information of each of the one or more data packets 101. The status information 103 of each data packet 101 may indicate whether the data packet 101 has been received by the receiving device 110, or whether it is lost at the receiving device 100. The method 300 also includes step 304: determining whether to regard the missing data packet 101 as lost based on the feedback message; determining whether to retransmit the missing data packet 101 based on the path information of the missing data packet and the status information of one or more other data packets transmitted to the receiving device on the same path as the missing data packet. In addition, whether to retransmit the missing data packet 101 may also be determined based on the rules of the underlying transmission protocol used to send the data packet 101. The protocol may be a single-path transmission protocol.
[0080] The invention has been described in conjunction with various embodiments as examples and implementations. However, from a study of the drawings, the invention and the independent claims, other variations will be understood and implemented by those skilled in the art in implementing the claimed subject matter. In the claims and in the specification, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" does not exclude a plurality. A single element or other unit may fulfil the functions of several entities or items described in the claims. The listing of certain measures in mutually different dependent claims does not indicate that a combination of these measures cannot be effectively used.
Claims
1. A sending device (100) for sending a data packet (101) to a receiving device (110), characterized in that The sending device (100) is used for: Determining a set of one or more paths (102) between the sender device (100) and the receiver device (110); For each data packet (101), selecting a path (102) from the set of paths (102) for sending the data packet (101) to the receiving device (110); For each data packet (101), maintaining path information (103), the path information indicating the selected path (102) used to send the data packet (101) to the recipient device (110); receiving a feedback message (111) from the receiving device (110), wherein the feedback message (111) includes status information of each of the one or more data packets (101); Based on the feedback message (111), determine whether to regard the missing data packet (101) as lost; based on the path information (103) of the missing data packet (101) and the status information (103) of one or more other data packets (101) transmitted to the receiving device (110) on the same path (102) as the missing data packet (101), determine whether to retransmit the missing data packet (101).
2. The sender device (100) according to claim 1, characterized in that: The status information (103) of each data packet (101) indicates whether the data packet (101) has been received by the receiving device (110) or lost at the receiving device (110).
3. The sender device (100) according to claim 1 or 2, characterized in that: The sending device (100) is configured to: if the feedback message (111) indicates that a data packet (101) having a sequence number greater than the sequence number of the missing data packet (101) has been received at the receiving device (110), then: If the received data packet (101) is sent to the recipient device (110) on a different path (102) than the missing data packet (101), the missing data packet (101) is not considered lost and is not retransmitted.
4. The sender device (100) according to claim 3, characterized in that: The sending device (100) is used for: If the received data packet (101) is sent to the receiving device (110) over the same path (102) as the missing data packet (101), and if the underlying transport protocol used to send the data packet (101) requires retransmission, the missing data packet (101) is considered lost and the missing data packet (101) is retransmitted.
5. The sender device (100) according to claim 4, characterized in that: The sending device (100) is also used for: The missing data packet (101) is retransmitted over the same path (102) as the path used to first transmit the data packet (101) to the recipient device (110).
6. The sender device (100) according to claim 3, characterized in that: The sending device (100) is also used for: receiving another feedback message (111) from the receiver device (110), the another feedback message (111) indicating that another received data packet (101) having a sequence number greater than the sequence number of the missing data packet (101) has been received at the receiver device (110); If the other received data packet (101) is sent to the recipient device (110) on the same path (102) as the missing data packet (101), and if the underlying transport protocol used to send the data packet (101) requires retransmission, the missing data packet (101) is considered lost and the missing data packet (101) is retransmitted.
7. The sender device (100) according to any one of claims 1 to 6, characterized in that: The sender device (100) is configured to select the one or more paths (102) from all available paths (102) between the sender device (100) and the receiver device (110) in order to determine the set of paths (102).
8. The sender device (100) according to any one of claims 1 to 7, characterized in that: The sender device (100) is further configured to determine the path (102) set based on a result of performing path-by-path congestion control on available paths (102) between the sender device (100) and the receiver device (110).
9. The sender device (100) according to any one of claims 1 to 8, characterized in that: The sender device (100) is further configured to select, for each data packet (101), a path (102) for sending the data packet (101) to the receiver device (110) based on one or more congestion control considerations.
10. The sender device (100) according to any one of claims 1 to 9, characterized in that: The sender device (100) is also used to add a new path (102) to the set of paths (102).
11. The sender device (100) according to any one of claims 1 to 10, characterized in that: The sender device (100) is further configured to delete a path (102) from the set of paths (102).
12. The sender device (100) according to claim 11, characterized in that: The sending device (100) is used to: in order to delete the path from the path (102) set: Stop sending data packets (101) on the path (102) to be deleted; retransmitting any missing data packets (101) on the path (102) to be deleted; If all data packets (101) transmitted or retransmitted on the to-be-deleted path (102) are received at the receiving device (110), the to-be-deleted path (102) is deleted from the path (102) set.
13. The sender device (100) according to any one of claims 1 to 12, characterized in that: The sending device (100) is also used to retransmit the one or more missing data packets (101) on one or more other paths (102) in the path (102) set if a path (102) used to retransmit the one or more missing data packets (101) fails.
14. The sender device (100) according to any one of claims 1 to 11, characterized in that: The feedback message (111) is an acknowledgment (ACK) message, a negative ACK (NACK) message, or a selective ACK (SACK) message.
15. A method (300) for sending a data packet (101) from a sender device (100) to a receiver device (110), characterized in that: The method (300) comprises: Determining (301) a set of one or more paths (102) between the sender device (100) and the receiver device (110); For each data packet (101), selecting (302) a path (102) from the set of paths (102) for transmitting the data packet (101) to the receiving device (110); For each data packet (101), maintaining (303) path information (103), the path information (103) indicating the selected path (102) used to send the data packet (101) to the recipient device (110); receiving (304) a feedback message (111) from the receiving device (110), the feedback message (111) comprising status information of each of the one or more data packets (101); Based on the feedback message (111), determine (305) whether to regard the missing data packet (101) as lost; based on the path information (103) of the missing data packet (101) and the status information of one or more other data packets (101) transmitted to the receiving device (110) on the same path (102) as the missing data packet (101), determine whether to retransmit the missing data packet (101).
16. A computer program, characterized in that The computer program comprises instructions which, when the program is executed by a computer, cause the computer to perform the method (300) according to claim 15.
