Method for reducing packet loss in session slow start stage
By selecting multiple tunnels in the network device to transmit original and repeated packaged packets in parallel, the problems of packet loss and transmission efficiency in wireless connections are solved, and higher network performance and data transmission rate are achieved.
Patent Information
- Application Number
- CN202280095465.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-29
- Publication Date
- 2024-12-06
AI Technical Summary
The connectivity of wireless connections is unpredictable, resulting in packet loss problems from time to time. The traditional TCP congestion control algorithm has problems such as packet loss and low transmission efficiency during the slow startup and congestion avoidance stages.
Data transmission is transmitted by selecting multiple tunnels in network devices, and the original package packet (OEP) and repeated package packets (DEP) are transmitted in parallel, and the transmission method is adjusted according to specific time periods and selection strategies to improve the success rate of data packet transmission and Network performance.
Effectively reduce packet loss, extend the duration of exponential increase, and improve network performance and optimization of data transmission rate, latency and bandwidth utilization.
Smart Images

Figure CN119096527A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates generally to mobile wireless networks and, more particularly, to systems and methods for modifying network protocol performance using mobile wireless network information. Background Art
[0002] The connectivity of wireless connections is unpredictable, and packet loss problems occur from time to time. The Transmission Control Protocol (TCP) is designed to assume that packet loss is the result of network congestion. In order to prevent network congestion, a series of congestion control algorithms are introduced, including a slow start phase and a congestion avoidance phase. According to the algorithm, in the slow start phase, the congestion window will increase exponentially. When packet loss occurs, the congestion control process will enter the congestion avoidance phase, and the congestion window will increase linearly rather than exponentially. In order to accelerate TCP, the present invention adopts a solution of utilizing multiple tunnels to increase the probability of successful data transmission at the beginning of establishing a TCP session, which can be achieved by using duplicate data packets.
[0003] Thereby, a large amount of packet loss can be avoided and the duration of the exponential increase can be maximized. SUMMARY OF THE INVENTION
[0004] The present invention discloses a method and system for transmitting data packets on a network device. According to the disclosure of the present invention, the network device determines whether the received data packet belongs to a new session. When the data packet belongs to a new session, the network device selects a first connection according to a first selection strategy, and selects at least one second connection according to a second selection strategy. Afterwards, the network device transmits an original encapsulation packet (OEP) through the first connection. The network device also transmits at least one duplicate encapsulation packet (DEP) corresponding to each OEP through at least one second connection until a specific time period is reached. When the specific time period is reached, each OEP is transmitted through a third connection, and the transmission of at least one DEP is stopped.
[0005] The data packet received by the network device of the present invention may be originally from a host connected to the network device. In one implementation of the present invention, the specific time period may be a time period in a slow start phase of a TCP data session establishment phase.
[0006] For each of the OEPs, there is no limit on the number of DEPs transmitted. Likewise, there is no limit on the number of connections used by the network device to transmit DEPs. In one variant, the OEPs and the DEPs are transmitted via an aggregated connection. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] Figure 1 is a schematic block diagram of an exemplary network device 100 according to an embodiment of the present invention.
[0008] Figure 2 is a network diagram according to various embodiments of the present invention.
[0009] Figure 3 is a network diagram illustrating tunnels established between network devices according to various embodiments of the present invention.
[0010] Figure 4 is a flow chart illustrating a process performed at the network device during the slow start phase according to an embodiment of the present invention.
[0011] Figure 5A The relationship between the congestion window size and the time to transmit a data packet of a TCP session implemented according to a conventional congestion control process is shown.
[0012] Figure 5B The relationship between the congestion window size and the time to transmit a data packet for a TCP session implemented according to the congestion control process is shown.
[0013] Fig. 6A The structure of the OEP according to various embodiments of the present invention is shown.
[0014] Figure 6B The structure of a DEP according to various embodiments of the present invention is shown. Specific embodiments
[0015] The present invention provides the system and method for reducing packet loss in the slow start phase to improve network performance, which is conducive to solving the above-mentioned needs.
[0016] The following description provides only preferred exemplary embodiments and exemplary embodiments, and is not intended to limit the scope, applicability or configuration of the present invention. On the contrary, the following description of preferred exemplary embodiments and exemplary embodiments will provide a feasible description of implementing the preferred exemplary embodiments of the present invention for those skilled in the art. It will be understood that various changes may be made to the functions and arrangements of the elements without departing from the spirit and scope of the present invention described in the appended claims.
[0017] The processing unit executes program instructions or code segments for implementing embodiments of the present invention. In addition, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. When embodiments are to be implemented by software, firmware, middleware, or microcode, program instructions for performing the necessary tasks may be stored in a computer-readable storage medium. The processing unit may be implemented by virtualization and may be a virtual processing unit, including a virtual processing unit in a cloud-based instance.
[0018] The program instructions constituting the various embodiments may be stored in a storage medium. In addition, as disclosed herein, the term "computer-readable storage medium" may represent one or more devices for storing data, including read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), random access memory (RAM), magnetic RAM, core memory, floppy disk, flexible disk, hard disk, tape, CD-ROM, flash memory device, memory card and / or other machine-readable medium for storing information. The term "computer-readable storage medium" may also include, but is not limited to, portable or fixed storage devices, optical storage media, magnetic media, memory chips or cassettes, wireless channels, and various other media capable of storing, containing or carrying instructions and / or data. The computer-readable storage medium may be implemented through virtualization and may be a virtual computer-readable storage medium, including a virtual computer-readable storage medium in a cloud-based instance.
[0019] Embodiments of the present invention relate to using a computer system to implement the techniques described herein. In one embodiment, the processing unit of the present invention may reside on a machine such as a computer platform. According to one embodiment of the present invention, the techniques described herein are performed by a computer system in response to the processing unit executing one or more sequences of one or more instructions contained in the volatile memory. Such instructions may be read into the volatile memory from another computer-readable medium. The execution of the sequence of instructions contained in the volatile memory causes the processing unit to perform the processing steps described herein. In alternative embodiments, hard-wired circuits may be used instead of or in combination with software instructions to implement the present invention. Therefore, embodiments of the present invention are not limited to any specific combination of hardware circuits and software.
[0020] In addition, it is worth noting that the embodiments can be described as processes shown in flow charts, data flow diagrams, structure diagrams or block diagrams. Although flow charts can describe the operations as sequential processes, many of the operations can be performed in parallel or simultaneously. In addition, the order of the operations can be rearranged. When the operations are completed, the process terminates, but may have additional steps not included in the figure. A process can correspond to a method, function, process, subroutine, subprogram, etc. When a process corresponds to a function, its termination corresponds to the function returning to the calling function or the main function.
[0021] Furthermore, as disclosed herein, the terms "secondary memory" and "primary memory" may refer to one or more devices for storing data, including ROM, RAM, magnetic RAM, core memory, magnetic disk storage media, optical storage media, flash memory devices, and / or other machine-readable media for storing information. The term "machine-readable medium" includes, but is not limited to, portable or fixed storage devices, optical storage devices, wireless channels, and various other media capable of storing, containing, or carrying instructions and / or data. The machine-readable medium may be implemented through virtualization and may be a virtual machine-readable medium, including a virtual machine-readable medium in a cloud-based instance.
[0022] In addition, embodiments can be implemented by hardware, software, firmware, middleware, microcode, hardware description language or any combination thereof. When implemented by software, firmware, middleware or microcode, the program code or code segment for performing the necessary tasks can be stored in a machine-readable medium, such as a storage medium. The processing unit can perform the necessary tasks. The processing unit can be a CPU, an ASIC semiconductor chip, a semiconductor chip, a logic unit, a digital processor, an analog processor, an FPGA or any processor capable of performing logical and arithmetic functions. The code segment can represent any combination of a process, a function, a subroutine, a program, a routine, a subroutine, a module, a software package, a class or an instruction, a data structure or a program statement. The code segment can be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, parameters, parameters or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded or transmitted in any suitable manner, including memory sharing, message passing, token passing, network transmission, etc. The processing unit can be implemented by virtualization, and can be a virtual processing unit, including a virtual processing unit in a cloud-based instance.
[0023] The end-to-end connection may use a connection-oriented protocol, such as TCP, or a connectionless protocol, such as the User Datagram Protocol (UDP), to transmit data packets. Well-known protocols for deploying end-to-end connections include Layer 2 Tunneling Protocol (L2TP), Secure Shell (SSH) Protocol, Multiprotocol Label Switching (MPLS), and Microsoft's Point-to-Point Tunneling Protocol (PPTP). The connection to the network interface takes the form of fiber, Ethernet, ATM, Frame Relay, T1 / E1, IPv4, IPv6, wireless technology, Wi-Fi, WiMax, High Speed Packet Access (HSPA) technology, 3GPP, Long Term Evolution (LTE), etc.
[0024] Figure 11 is a schematic block diagram of an exemplary network device 100 according to an embodiment of the present invention. The network device 100 includes at least one storage unit 101, at least one I / O interface 102, at least one memory 103, at least one processing unit 104, and multiple network interfaces 105. The storage unit 101 may contain computer program instructions that can be executed by the processing unit 104 to implement one or more aspects of the present disclosure. The processing unit 104 and the memory 103 are directly connected to each other. The system bus 106 directly or indirectly connects the processing unit 104 to the at least one storage unit 101, the at least one I / O interface 102, and the multiple network interfaces 105.
[0025] In another embodiment, the network device 100 may further include at least one SIM interface 107 and at least one wireless communication module (WCM) 108 with at least one antenna 109. A SIM or an electronic SIM can be received in or coupled to a SIM interface of the at least one SIM interface 107 and establish a wide area network (WAN) connection through at least one WCM 108 with at least one antenna 109.
[0026] The network device 100 can be connected to a wired or wireless access network through at least one network interface 105. The wired or wireless access network can carry one or more network protocol data. The wired access network can be implemented using Ethernet, optical fiber, cable, DSL, frame relay, token ring, serial bus, USB, FireWire, PCI or any material that can transmit information. The wireless access network can be implemented using infrared, LTE, 5G, low earth orbit (LEO) satellite, HSPA, HSPA+, WiMax, GPRS, EDGE, GSM, CDMA, Wi-Fi, CDMA2000, WCDMA, TD-SCDMA, Bluetooth, WiBRO, Evolution Data Optimized (EV-DO); Digital Enhanced Cordless Telecommunications (DECT); Digital AMPS (IS-136 / TDMA); Integrated Digital Enhanced (iDEN) or any other wireless technology. A WAN connection can be established on the access network to connect two networks.
[0027] Figure 2 2 is a network diagram according to various embodiments of the present invention. Network device 200 and network device 202 are similar to Figure 12. Network device 200 and network device 202 are located at site 205 and site 206, respectively. Network devices 200 and 202 may be embodied as multi-WAN network devices that support aggregating the bandwidth of multiple WAN-to-WAN connections. Network devices 200 and 202 are connected via an interconnection network 204. Interconnection network 204 is an interconnected network that may include a local area network (LAN), such as a company intranet, a metropolitan area network (MAN), or a WAN, such as the Internet or the World Wide Web.
[0028] At site 205, laptop computer 201a and desktop computer 201b are connected to network device 200 via a first network interface of network device 200. At site 206, server 203 is connected to network device 202 via a first network interface of network device 202.
[0029] In one embodiment, site 205 and site 206 are located in the same region or country, such as the United States.
[0030] In another embodiment, site 205 and site 206 are located in different regions or countries, such as the United States and Singapore, respectively.
[0031] The network device 200 includes at least one network interface that can be connected to an access network, and the network device 202 includes at least one network interface that can be connected to an access network. The access network is a network that can achieve access to the interconnected network 204. The laptop 201a and the desktop 201b can be connected to the network device 200 through the first network interface of the network device 200. Similarly, the server 203 can be connected to the network device 202 through the first network interface of the network device 202. The server 203 can be located in the LAN of the network device 202.
[0032] In one embodiment, each of the at least one network interface of the network device 200 and each of the at least one network interface of the network device 202 may be a WAN interface. In one embodiment, the WAN interface may be implemented using a WCM and an antenna, which may be connected to a base station of the Internet service provider.
[0033] In one variation, the antenna is a non-omnidirectional antenna for a LEO satellite.
[0034] In another embodiment, each of the at least one network interface of the network device 200 and each of the at least one network interface of the network device 202 may be a LAN interface. Each of the network devices 200 and 202 can be connected to the interconnected network through the LAN interface by configuring the LAN interface as a WAN interface.
[0035] Network device 200 may include three network interfaces capable of connecting to three access networks 207a-c, while network device 202 may include two network interfaces capable of connecting to two access networks 208a-b. Thus, six connections may be created through access networks 207a-c and 208a-b. However, these configurations may vary depending on the desired network devices and configurations. There is no limit to the number of network interfaces of network devices 200 and 202, and the three network interfaces of network device 200 and the two network interfaces of network device 202 are specified for illustration purposes only. Figure 3 As shown, the connection is established between network device 200 and network device 202.
[0036] Figure 3 FIG. 1 shows the connection established between two network devices according to an exemplary embodiment of the present invention. Figure 2 Come and view Figure 3 Through at least one connection established between network devices 200 and 202, at least one end-to-end connection can be established between a host in the same LAN of network device 200 and a host in the same LAN of network device 202. Each connection can be established through a network interface of network device 200 and a network interface of network device 202. If network device 200 includes M network interfaces and network device 202 includes N network interfaces, M*N connections are established between network devices 200 and 202.
[0037] For example, if network device 200 includes three network interfaces and network device 202 includes two network interfaces, when a connection is established between the network interfaces of network devices 200 and 202, six connections 209a-f may be created, such as: Figure 3 The at least one end-to-end connection established between the notebook computer 201a and the server 203 may be established through at least one of the six connections.
[0038] The values of M and N can vary depending on the desired device and configuration. There is no limit to the number of M and N, and M and N can be any positive integers such that the sum of M and N is equal to or greater than three. In another example, M is equal to one and N is equal to two, thereby creating two connections.
[0039] The access network of network devices 200 and 202 is an access connection used to pass information within the interconnected network 204 between sites 205 and 206.
[0040] Connections 209a-f may have similar or different bandwidth capabilities. In addition, the access networks of network devices 200 and 202 may include different types of WAN connections, such as Wi-Fi, cable, DSL, 3G, 4G, LTE, 5G, satellite connections, etc. It is also noted that sites 205 and 206 can be considered as the sender and the receiver, and the discussion of the functionality of either site can be implemented on the other site. Connections 209a-f correspond to unique permutations of the access network of site 205 and the access network of site 206.
[0041] In one embodiment, an aggregated connection is formed between network devices 200 and 202. The multiple connections can be aggregated, combined, or bound together to form an aggregated connection. Those skilled in the art will appreciate that there are numerous ways to aggregate, combine, or bind multiple connections to form an aggregated connection. The aggregated connection is viewed as a single connection by the session or application using it. The aggregated connection can be viewed as a tunnel, a virtual private network (VPN) connection, or a connection-oriented connection.
[0042] For example, the aggregated connection is an aggregation of multiple connections (e.g., connections 209a-f) established between network devices 200 and 202. The aggregated connection can be created when a TCP session is created. For example, when laptop 201a attempts to connect to server 203, the aggregated connection is established between laptop 201a and server 203 through network devices 200 and 202.
[0043] In another example, the aggregate connection is a VPN tunnel including a plurality of tunnels, each tunnel being established between network interfaces of network devices 200 and 202 .
[0044] In one example, the aggregated connection is a TCP connection.
[0045] In another example, the aggregated connection is a UDP connection.
[0046] For ease of explanation, when the laptop 201a attempts to establish a connection with the server 203 through the network devices 200 and 202, a TCP session is created. After the TCP session is created, the network device 200 can transmit data packets through the connection through the network interface of the network device 200 and the network interface of the network device 202. At this point, the congestion control process begins.
[0047] In one embodiment, packets are transmitted through connections in the aggregated connection according to the weight assigned to each connection of the aggregated connection, and a default weight is determined for each connection of the aggregated connection. The default weight is initially assigned to each connection by default before any modification or change to the weight of the connection.
[0048] In one example, a default weight is determined and / or assigned for each of the access networks based on the exchanged uplink and downlink bandwidth data of each of the access networks.
[0049] In another example, a default weight is determined and / or assigned to each of the access networks based on criteria that may affect the performance of the access networks.
[0050] Assume that the downlink bandwidth of access network 1 to a of site 205 is d1, d2, ..., dm, and the uplink bandwidth of access network 1 to b of site 206 is u1, u2, ..., un; the default weight of the connection between access network x of site 205 and access network y of site 104 can be defined as DW(x,y), where DW(x,y) = dx·uy.
[0051] The above method can be used to calculate the default weight. If the up / downlink bandwidths of the three access networks of the network device 200 are 10M / 6M, 8M / 4M, and 6M / 6M, respectively, and the up / downlink bandwidths of the two access networks of the network device 202 are 7M / 5M and 9M / 3M, respectively, then the default weight of each connection is: Network device 200 Network equipment 202 DW(1,1)=6M*7M=42M DW(1,1)=5M*10M=50M DW(1,2)=6M*9M=54M DW(1,2)=5M*8M=40M DW(2,1)=4M*7M=28M DW(1,3)=5M*6M=30M DW(2,2)=4M*9M=36M DW(2,1)=3M*10M=30M DW(3,1)=6M*7M=42M DW(2,2)=3M*8M=24M DW(3,2)=6M*9M=54M DW(2,3)=3M*6M=18M
[0052] There are many ways to calculate the default weights, and the above method is for illustration purposes only.
[0053] In another embodiment, a data packet is transmitted over a group of connections of the aggregated connection. Each connection of the aggregated connection is classified into a different connection group, and data is transmitted over the connection based at least in part on the group into which the connection is classified. There is no limit to the number of groups into which a connection is classified, and a connection can be classified into multiple connection groups based on the criteria of each connection group.
[0054] Two parameters are mainly used to control the congestion of an established connection, namely the congestion window size (cwnd) and the slow start threshold (ssthresh). The established connection is controlled by the network device by controlling the packet transmission rate of the connection in four stages of the congestion control process, namely: (i) Slow start phase, (ii) Congestion avoidance phase, (iii) Fast retransmit phase, and (iv) Fast recovery phase.
[0055] In a preferred embodiment, after the session is established, the congestion control process starts before the three-way handshake.
[0056] In another embodiment, after the session is established, the congestion control process starts after a three-way handshake.
[0057] When the network device 200 receives the first data packet to be transmitted to the server 203 from the laptop 201a, the server 203 is locally connected to the network device 202 via the LAN. The network device 200 can send the data packet to the network device 202 via the established aggregate connection. At this time, the size of the congestion window becomes 1. Those skilled in the art will understand that after receiving the first data packet, the network device 200 can receive more data packets. If the network device 200 receives more data packets from the laptop 201a to the server 203, the network device 200 can send the subsequent data packets after receiving the confirmation of the previous data packet according to the size of the congestion window.
[0058] When server 203 successfully receives the first data packet, network device 200 may then receive an acknowledgment of the first data packet from server 203 via network device 202, and the size of the congestion window increases until the slow start threshold is reached. For ease of explanation, after receiving the acknowledgment, the size of the congestion window is increased by doubling the original size (new cwnd = cwnd*2).
[0059] When the network device 200 successfully receives the confirmation of the first data packet from the server 203 through the network device 202, the network device 200 may attempt to transmit the second and third data packets to the server 203 through the network device 202, and the size of the congestion window becomes 2. The second and third data packets are received from the laptop 201a. When the network device 200 successfully receives the confirmation of the second and third data packets from the server 203 through the network device 202, the network device 200 may attempt to transmit the fourth, fifth, sixth, and seventh data packets to the server 203 through the network device 202, and the size of the congestion window becomes 4, so that the size of the congestion window increases exponentially until the slow start threshold (i.e., cwnd=ssthresh) is reached.
[0060] The congestion window size does not have to be increased exponentially, and any other suitable algorithm for increasing the congestion window size may be applied. For another example, after receiving the confirmation, the congestion window size is increased by 2 (new cwnd=cwnd+2).
[0061] When the congestion window size reaches the slow start threshold, the packet transmission enters the congestion avoidance phase from the slow start phase to repair the network crash. In the congestion avoidance phase, the congestion window size no longer increases in the above exponential manner, but increases linearly. After a period of time, the TCP transmission rate exceeds the network connection capacity, resulting in packet loss. However, before the congestion avoidance phase, that is, in the slow start phase, packet loss or timeout may occur.
[0062] Figure 4 is a flow chart illustrating a process performed at the network device during the slow start phase according to an embodiment of the present invention.
[0063] When the network device receives data packets from a host, such as laptop 201a, the process will begin for each received data packet.
[0064] In process 401, the network device 200 may determine whether a new session is established. The session may be a TCP session or a UDP session.
[0065] In one embodiment, the network device determines whether a new session is established by identifying whether the received data packet belongs to a new session. For example, in order to determine whether the received data packet is the first data packet of a new session, the processing unit of the network device 200 may read one or more of the following information contained in the header of the received data packet: source address, source port, destination address, destination port, and protocol.
[0066] When the received data packet is not the first data packet of a new session, the network device will route the received data packet through the preselected connection and continue to apply the determination process 401 to the next received data packet. When the first data packet of the data session to which the received data packet belongs is determined, the selection of the preselected connection can be started. In a variant, when the received data packet is not the first data packet of a new session, the network device determines whether the received data packet is the last data packet of an existing session. If the received data packet is the last data packet of the existing session, it is obvious that the next data packet to be received will be the first data packet of the new session. Therefore, the network device can perform processes 402 and 403 in advance before receiving the first data packet of the new session. Therefore, when the next data packet is received, the network device will not need to perform processes 401-403, but can jump to process 404. This will significantly promote the present invention to accelerate the establishment of data sessions and reduce the processing load of the new data session establishment stage. Whether the received data packet is the last data packet of the active session can be determined based on one or more of the source address, source port, destination address, destination port and / or protocol of the received data packet.
[0067] On the other hand, when the data packet is the first data packet of a new session, the network device may perform process 402 and subsequent processes.
[0068] In one variation, the network device 200 may determine whether the received data packet is the second data packet or the third data packet of the new session, rather than the first data packet. When the received data packet is the second or third data packet of the new session, the network device may perform process 402 and subsequent processes.
[0069] In process 402, network device 200 may select a first connection to transmit data packets belonging to a new session. The first connection is a connection established between a network interface of network device 200 and a network interface of network device 202. The first connection is selected according to a first selection policy.
[0070] In process 403, network device 200 may select at least one second connection according to a second selection policy. The at least one second connection is at least one connection established between the network interface of network device 200 and the network interface of network device 202 except the first connection.
[0071] The first selection and the second selection strategies are selected from one or more of: weighted balance, least used, lowest delay, and priority. Thus, data packets can be transmitted in a manner that reduces the possibility of packet loss during the slow start.
[0072] In one embodiment, the first selection strategy is the same as the second selection strategy.
[0073] In another embodiment, the first selection strategy is different from the second selection strategy.
[0074] In one example, if "weight balancing" is applied at the network device 200 to select the connection, the data packets to be transmitted through the connection are allocated according to the weight of each connection in the aggregated connection. The weight may be the default weight calculated for each connection as described above. For illustrative purposes, the weight of each connection in the aggregated connection is related to bandwidth, and the default weight is calculated based on the bandwidth of each connection. During the transmission of data packets from the network device 200 to the network device 202 through multiple connections, the bandwidth of each connection in the multiple connections may be different, and therefore the weight may also be different. The network device may transmit data packets through various connections according to the change of the weight of each connection in the multiple connections.
[0075] In another example, if "least used" is applied to select the connection at the network device 200, the data packets to be transmitted through the connection are allocated according to the traffic of each connection in the aggregated connection. If there are multiple available connections, the connection with the smallest traffic in the aggregated connection is preferentially selected to transmit more data packets.
[0076] In another example, if "latency" is used to select the connection at the network device 200, the data packets to be transmitted through the connection are allocated according to the latency of each connection in the aggregated connection. If there are two available connections, and the latency is 100ms and 40ms respectively, the connection with 40ms latency is preferentially selected, that is, the connection with lower latency transmits more data packets.
[0077] In another example, if "priority" is used to select the connection at the network device 200, the data packets to be transmitted through the connection are allocated according to the priority of each connection in the aggregated connection. The priority can be allocated by the user or administrator according to requirements or actual needs. During the transmission of data packets from the network device 200 to the network device 202 through the multiple connections, the connection with the highest priority is preferentially selected to transmit the data packets. If the connection with the highest priority is not available at a certain moment, the connection with the second highest priority is preferentially selected.
[0078] The user or administrator may configure the first selection policy and the second selection policy of the network device 200 by sending configuration locally or remotely through a Web interface, an application programming interface (API), a command line interface, or a console.
[0079] In one variant, multiple first selection strategies and / or multiple second selection strategies may be provided simultaneously. For example, when the data packet is transmitted to a specific destination port, a priority is applied to select a connection, and when the data packet is transmitted from another specific destination port, a weight balance is applied. The user or administrator can configure the priority of the strategy to be applied so that there is no conflict between the applied strategies.
[0080] In process 404, the network device 200 may transmit an original encapsulation packet (OEP) through the first connection. The OEP encapsulates the data packet, and each of the OEPs has an original encapsulation packet global sequence number (OEP-GSN).
[0081] In process 405, the network device 200 may transmit at least one duplicate encapsulation packet (DEP) through at least one second connection within a specific time period. The at least one DEP encapsulates at least one of the data packets. Each DEP has a duplicate encapsulation packet global sequence number (DEP-GSN), which is stored in a header of the DEP. Details of the OEP and the DEP will be discussed below.
[0082] Those skilled in the art will appreciate that in wireless communications, the quality of data packet transmission may be unpredictable and in some cases latency may be high. The packet loss rate may also be high. Transmitting the DEP increases the chances of the data being received by the network device 202 in case the OEP is lost. However, the transmission of the DEP may significantly increase bandwidth usage. Therefore, the data packets are only copied and transmitted during a specific time period.
[0083] In process 406, after a certain period of time, the network device 200 may continue to transmit the OEP through the third connection, but no longer transmit the at least one DEP through the at least one second connection.
[0084] Typically, process 404 and process 405 are performed after the slow start phase begins. During the slow start phase, the number of data packets transmitted through the connection increases exponentially. By transmitting the data packets through the connection of the aggregated connection during the slow start phase, the possibility of packet loss and delay can be reduced, and the rate at which data packets are transmitted through the aggregated connection established between network devices 200 and 202 can be maximized.
[0085] However, if packet loss occurs during the slow start phase, the exponential increase in the number of packets whose transmission may be interrupted during a specific time period may occur, and the congestion control process moves to the congestion avoidance phase, such as Figure 5B shown.
[0086] After a specific period of time calculated from the start of the slow start phase, the first selection strategy and / or the second selection strategy is no longer used to transmit the data packet through the one or more connections established between network device 200 and network device 202, but the data packet is transmitted through a third connection established between network device 200 and network device 202.
[0087] In one embodiment, the third connection is the same as the first connection selected in step 402 .
[0088] In another embodiment, the third connection is different from the first connection selected in step 402. The network device 200 may select another connection to transmit the data packet in any manner, such as the second selection strategy.
[0089] The factors determining the specific time period include one or more of the following: duration of the slow start phase, bandwidth, delay, and any factors that may affect data transmission. There is no limitation on how to determine the specific time period. The specific time period may be any time between the start and end of the slow start phase.
[0090] In one example, the specific time period is 2 seconds to 4 seconds calculated from the start of the slow start phase.
[0091] In another example, the specific time period is 3 seconds counted from the slow start phase.
[0092] Figure 5A FIG. 2 shows the relationship between the congestion window size and the time to transmit a data packet of a TCP session according to a conventional congestion control process. The data packet is transmitted through a connection in the plurality of connections established between network devices 200 and 202. No policy is applied to control the transmission of the data packet through the aggregated connection, and the data packet can be transmitted through the connection of the aggregated connection. As described above, the congestion control process includes four stages, but for the purpose of illustrating an embodiment of the present invention, Figure 5A Only the slow start phase 501a and the congestion avoidance phase 502a are shown.
[0093] During the slow start phase 501a, the size of the congestion window continues to grow exponentially from the initial size of the congestion window. For ease of illustration, when the packet transmission time of the TCP session reaches 505a, the size of the congestion window continues to grow exponentially from the initial size of the congestion window 503a to a slow start threshold 504a. However, packet loss may occur during the slow start phase.
[0094] When packet loss occurs in the slow start phase, the congestion control process moves from the slow start phase 501a to the congestion avoidance phase 502a due to the detection of congestion, even if the congestion window size does not reach the slow start threshold 504a. For example, when packet loss occurs at 507a, the congestion control process moves from the slow start phase 501a to the congestion avoidance phase 502a, even if the congestion window size only reaches 508a instead of 504a.
[0095] During the congestion avoidance phase 502a, the congestion window size can only be increased linearly until there is evidence that duplicate acknowledgments (ACKs) have been received. In one embodiment, a congestion avoidance algorithm may be applied to control the congestion.
[0096] Therefore, the network device 200 may send out subsequent data packets based on the applied congestion avoidance algorithm. The congestion avoidance algorithm may be selected from one or more of the following: TCP Reno, TCP Vegas, TCP-Fast, CompoundTCP, TCP Veno, TCP Westwood, TCP Cubic, and TCP BIC.
[0097] There is no limitation on the congestion avoidance algorithm used to control the congestion, and any congestion avoidance algorithm including aspects of an additive increase / multiplicative decrease (AIMD) scheme may be applied.
[0098] For ease of explanation, at 506a, the network device 200 has received a duplicate ACK. Therefore, the size of the congestion window is reset to the initial size of the congestion window 503a, and the process of increasing the congestion window size is started again (e.g., the size of the congestion window is reset to 1), and the slow start threshold is reduced (e.g., ssthresh=current cwnd / 2). There is no limit to the size of the congestion window after reset, and it may vary according to the congestion avoidance algorithm applied.
[0099] To reduce Figure 5A According to an embodiment of the present invention, the method proposed in the present invention is applied during the slow start phase. Figure 5B The relationship between the congestion window size and the packet transmission time of a TCP session shown in Figure 5A The difference shown in .
[0100] Figure 5B The relationship between the congestion window size and the data packet transmission time of the TCP session implemented according to the congestion control process is shown in the case where packet loss occurs in the slow start phase. Figure 5B Should be combined Figure 2 View and connect with Figure 5A The data packet is transmitted through the multiple connections established between the network devices 200 and 202. Figure 5A similar, Figure 5B Only the slow start phase 501b and the congestion avoidance phase 502b are shown to illustrate the embodiment of the present invention.
[0101] In one variant, the plurality of connections are aggregated into one aggregate connection.
[0102] When the data packets of the session begin to be transmitted, the congestion control process begins and enters the slow start phase 501b. Once the first data packet of the session is determined, the network device 200 can transmit the OEP and the DEP through the multiple connections established between the network devices 200 and 202.
[0103] During the slow start phase 501b, the size of the congestion window continues to grow exponentially from the initial size of the congestion window, similar to Figure 5A The slow start phase 501a is shown in FIG.
[0104] For ease of explanation, when the time to transmit a data packet of a TCP session reaches 505b, the size of the congestion window continues to grow exponentially from the initial size of the congestion window 503b to a slow start threshold 504b. However, packet loss may occur during the slow start phase.
[0105] because Figure 4 The method shown is applied through the multiple connections established between the network devices 200 and 202, so that packet loss can be reduced. For example, when a data packet is transmitted through the multiple connections at the network device 200, the data packet is encapsulated as an OEP and at least one DEP, respectively. The network device 200 can transmit the OEP through the first connection within a specific time period and transmit the at least one DEP through the at least one second connection. Therefore, by transmitting the OEP and the DEP simultaneously through the multiple connections, the chance of data being received by the network device 202 can be increased.
[0106] For example, when transmitting an OEP via connection 209a and a DEP via connection 209c, and transmitting a data packet from laptop 201a to server 203, packet loss may occur when transmitting the OEP via connection 209a. It is possible that network device 202 successfully receives the DEP via connection 209c. Therefore, an acknowledgment of the data packet is received from server 203 via network device 202. As a result, the size of the congestion window will continue to grow exponentially, and the congestion control process will not switch from slow start phase 501b to congestion avoidance phase 502b. This will extend the duration of slow start phase 501b.
[0107] Therefore, with Figure 5A Compared with the conventional technology disclosed in Figure 5B According to the technology disclosed in , the congestion avoidance phase will start with a higher congestion window size. Achieving a higher congestion window size in the slow start phase will increase the probability that the congestion window size reaches the slow start threshold; and according to Figure 5A According to the conventional technique shown in , the congestion control process may trigger a congestion avoidance phase before the slow start threshold is reached.
[0108] When the congestion window size reaches the slow start threshold 504b, the congestion control process switches from the slow start phase 501b to the congestion avoidance phase 502b. Since a higher congestion window size can be achieved according to the present invention, the slow start threshold 504b can also be set at a higher level. This will help to increase the data transmission bandwidth very quickly.
[0109] During the congestion avoidance phase 502b, the congestion window size increases linearly until there is evidence that a duplicate ACK has been received. Figure 5A In comparison, more data packets can be transmitted during the congestion avoidance phase.
[0110] In order to monitor the bandwidth of the various connections 209a-f, some embodiments of the present invention encapsulate each transmitted IP packet with various information.
[0111] Fig. 6A The structure of the OEP according to various embodiments is shown. The OEP 600 is an encapsulation packet that encapsulates an encapsulated data packet with various information for data packet transmission. The OEP 600 includes an IP header 601, an OEP-GSN 602, a sequence number for each tunnel 603, other information 604, and an encapsulated data packet 605. The OEP-GSN 602 stores the OEP-GSN of the OEP 600.
[0112] Each tunnel sequence number 603 can be a 32-bit field representing the sequence number assigned to each data packet routed to a particular tunnel. The payload field can be encrypted using the Advanced Encryption Standard (AES) to transmit the payload of the IP data packet. AES encryption can be applied to increase the security of the payload to prevent attacks by third parties.
[0113] The IP header 601 may include one or more of the following: a version field, a protocol type field, a tunnel ID field, and a global sequence number field. Other information 604 may include an AES initialization vector field and a tunnel ID field.
[0114] The version field may contain information about the protocol version being used, and the protocol type field may contain the protocol type of the payload packet. Typically, the value of this field will correspond to the Ethernet protocol type of the packet. However, other values may be defined in other documents. The tunnel ID field may be a 32-bit field and may contain an identifier for identifying the current tunnel for the IP packet.
[0115] The AES initialization vector field may be a 32-bit field and may contain an initialization vector for AES encryption. The global sequence number field may be a 32-bit field and may contain a sequence number used to reorder each of the packets of each session into the correct order as they emerge from their respective tunnels.
[0116] In one variation, each tunnel sequence number 603 and the tunnel ID field may be used to compare tunnel performance and reallocate packets based on the tunnel performance.
[0117] In another variation, each tunnel sequence number 603 may be a session number or a flow number.
[0118] In another variation, each tunnel sequence number 603 may be optional. When each tunnel sequence number 603 and the tunnel ID field are not included, it may be necessary to maintain a database to store information about which tunnel is used to transmit encapsulated packets for which GSN. By performing a lookup in the database, tunnel performance can be compared. Therefore, including each tunnel sequence number 603 and the tunnel ID field in the OEP can help determine latency without maintaining and looking up a database of all GSNs.
[0119] In one variation, the OEP-GSN 602, the sequence number for each tunnel 603, and the other information 604 are included in the options field of the IP header 601, and the encapsulated data packet 605 is included in the AES encrypted payload field. The benefit of including the OEP-GSN 602, the sequence number for each tunnel 603, and the other information 604 in the options field of the IP header 601 is that the information contained in these fields can be retrieved without decapsulating the OEP 600, which can significantly reduce the processing time. However, as the OEP 600 is transmitted through the tunnels, routers, and devices, the IP header 601 may change, so if the information in these fields is included in the options field of the IP header 601, they may be lost. Therefore, another option is that the OEP-GSN 602, the sequence number for each tunnel 603, the other information 604, and the encapsulated data packet 605 can all be included in the AES encrypted payload field 612 so that the information is preserved when the OEP 600 passes through routers and devices that may change the IP header 601.
[0120] Figure 6B The structure of the DEP according to various embodiments is shown. The DEP 610 is an encapsulation data packet, which encapsulates the encapsulated data packet with various information for data packet transmission. Similar to the OEP 600, the DEP 610 includes an IP header 611, a DEP-GSN 612, a sequence number for each tunnel 613, other information 614, and an encapsulation data packet 615.
[0121] OEP-GSN 602 and DEP-GSN 612 may be the same. Encapsulation packets 605 and 615 may be the same, so that OEP 600 and DEP 610 encapsulate the same packet, which become encapsulation packets 605 and 615, respectively. When network device 200 generates at least one DEP 610 for transmission, the payload, i.e., the encapsulation packet, is the same as the payload of the OEP 600. Since OEP 600 and DEP 610 have the same content, their global sequence numbers are also the same. Since DEP 610 contains the same encapsulation packet as OEP 600, if OEP 600 is lost, discarded, or delayed during transmission, and DEP 610 is received before OEP 600 is received, DEP 610 can be used to recreate the information in OEP 600.
Claims
1. A method for transmitting data packets on a network device, include: a. Determine whether a data packet belonging to a new session has been received; b. Selecting the first connection according to the first selection strategy; c. Selecting at least one second connection according to a second selection strategy; d. transmitting each original encapsulation packet (OEP) via the first connection; e. transmitting at least one duplicate encapsulation packet (DEP) via the at least one second connection within a specific time period; and f. transmitting each OEP via a third connection and no longer transmitting the at least one DEP; wherein the data packet is one of the data packets received from a host; and The specific time period is a time period within the slow start phase. The method of claim 1 , wherein the OEP encapsulates the data packet.
3. The method according to claim 1, wherein each of the OEPs has an Origin Encapsulation Packet Global Sequence Number (OEP-GSN). The method according to claim 1 , wherein the specific time period is 3 seconds counted from the slow start phase.
5. The method of claim 1, wherein the at least one DEP encapsulates packet information based on at least one of the packets.
6. The method of claim 1, wherein each of the at least one DEP has a DEP-Global Sequence Number (DEP-GSN). 7 . The method of claim 1 , wherein the OEP-GSN is stored in a header of each of the OEPs, and the DEP-GSN is stored in a header of each of the at least one DEP.
8. The method of claim 1, wherein the first selection strategy and the second selection strategy are selected from one or more of: weighted balance, least used, and lowest delay and priority.
9. The method of claim 1, wherein the third connection is the same as the first connection.
10. The method of claim 1, wherein the third connection is different from the first connection.
11. A network device, include: Processing unit; at least one storage unit; Multiple network interfaces; at least one non-transitory computer-readable storage medium; wherein the at least one non-transitory computer-readable storage medium is used to store program instructions executable by the at least one processing unit for: a. Determine whether a data packet belonging to a new session has been received; b. Selecting the first connection according to the first selection strategy; c. Selecting at least one second connection according to a second selection strategy; d. transmitting each original encapsulation packet (OEP) via the first connection; e. transmitting each of at least one duplicate encapsulation packet (DEP) via said at least one second connection within a specific time period; and f. transmitting each OEP via a third connection and no longer transmitting the at least one DEP; wherein the data packet is one of the data packets received from a host; and The specific time period is a time period within the slow start phase.
12. The network device of claim 11, wherein the OEP encapsulates the data packet.
13. The network device according to claim 11, wherein each of the OEPs has an Origin Encapsulation Packet Global Sequence Number (OEP-GSN).
14. The network device according to claim 11, wherein the specific time period is 3 seconds counted from the slow start phase.
15. The network device of claim 11, wherein each of the at least one DEP encapsulates packet information based on at least one of the packet encapsulation 16. The network device of claim 11, wherein each of the at least one DEP has a Deduplicated Encapsulation Packet Global Sequence Number (DEP-GSN). 17 . The network device according to claim 11 , wherein the OEP-GSN is stored in a header of each of the OEPs, and the DEP-GSN is stored in a header of each of the at least one DEP.
18. The network device of claim 11, wherein the first selection strategy and the second selection strategy are selected from one or more of: weighted balance, least used, and lowest delay and priority.
19. The network device of claim 11, wherein the third connection is the same as the first connection.
20. The network device of claim 11, wherein the third connection is different from the first connection.
