US8072886B2

Method and system for transmission control protocol (TCP) traffic smoothing

Summary by NHIP

TCP Traffic Smoothing

The method controls data transmission from a TCP offload engine by scheduling packet timing based on a token count value. The system suspends transmission when the token count meets criteria, decreases the value after sending a packet, and increases it based on a determined time rate.

Claim Score by NHIP

Read claim 1, the broadest

Abstract

Various aspects of a method and system for transmission control protocol (TCP) traffic smoothing are presented. Traffic smoothing may comprise a method for controlling data transmission in a communications system that further comprises scheduling the timing of transmission of information from a TCP offload engine (TOE) based on a traffic profile. Traffic smoothing may comprise transmitting information from a TOE at a rate that is either greater than, approximately equal to, or less than, the rate at which the information was generated. Some conventional network interface cards (NIC) that utilize TOEs may not provide a mechanism that enables traffic shaping. By not providing a mechanism for traffic shaping, there may be a greater probability of lost packets in the network.

US8072886B2, drawing sheet 1 — Sheet 1 of 19

Term

Term ended

Expired 21 July 2025, 1.2 years ago.

20 claims: 2 independent, 18 dependent

1
Broadest claimClaim Score 86, broad(NHIP)A method, comprising:in a network interface chip: determining a token count value associated with said network interface chip;and scheduling based on said token count value, transmission of a packet to be transmitted via said network interface chip, wherein said scheduling comprises suspending said transmission when said token count value meets one or more criteria.
11
A system, comprising:one or more circuits that are operable to determine a token count value associated with a network interface chip;and said one or more circuits are operable to schedule based on said token count value transmission of a packet to be transmitted via said network interface chip, wherein said scheduling comprises suspending said transmission when said token count value meets one or more criteria.

Independent claims2

88 paragraphs in 6 sections, as filed

0001This application is a continuation of U.S. application Ser. No. 11/187,404 filed Jul. 21, 2005, which makes reference to, claims priority to, and claims the benefit of U.S. Provisional Application Ser. No. 60/673,898 filed on Apr. 22, 2005.

0002The application makes reference to:

0000U.S. application Ser. No. 10/651,459 filed Aug. 29, 2003; and

0000U.S. Provisional Application Ser. No. 60/661,064 filed Mar. 11, 2005.

0003The above referenced applications are hereby incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

0004Certain embodiments of the invention relate to communication networks. More specifically, certain embodiments of the invention relate to a method and system for transmission control protocol (TCP) traffic smoothing.

BACKGROUND OF THE INVENTION

0005In some conventional network interface cards (NIC) installed in end stations, applications that utilize long lived information flows may transmit information for extended periods of time. An end station may also be referred to as a terminal. The information may be transmitted, via a network, between a transmitting terminal and a receiving terminal. The network may comprise a plurality of communications media and communications devices that facilitate the transfer of information between a transmitting terminal and a receiving terminal. Information may be transmitted via a network in structures that may be variously referred to as messages, packets, or frames. The method for transmitting the structure, that comprises the information, may be referred to as a protocol. Some transport layer data protocols may control the amount of information that may be transmitted during a time interval. The transmission control protocol (TCP) may be considered to be an example of one such protocol. TCP may limit the amount of information that is transmitted during a time interval based on a congestion window and slow start. At the beginning of transmission of an information flow, the congestion window may be set to an initial value. This may result in a relatively small amount of information being transmitted from a transmitting terminal to a receiving terminal. The receiving terminal may subsequently communicate an acknowledgement upon receipt of the information that was transmitted by the transmitting terminal.

0006Upon receipt of the acknowledgement, the transmitting terminal may increase the value associated with the congestion window to a number larger than the initial value, and transmit subsequent information based on the larger value that is associated with the congestion window. This may result in a larger amount of information being transmitted than during a comparable time interval in which the value associated with the congestion window is smaller. The size of the congestion window may increase with the increase in the value associated with the congestion window. A larger congestion window may also result in a higher information transfer rate between the transmitting terminal and the receiving terminal. The receiving terminal may communicate subsequent acknowledgements upon receipt of subsequent information. The transmitting terminal may continue to increase the size of the congestion window upon receipt of a subsequent acknowledgement.

0007In an instance in which the transmitting terminal does not receive a corresponding acknowledgement to previously transmitted information, the transmitting terminal may determine that the receiving terminal did not receive the previously transmitted information. The transmitting terminal may retransmit, or resend, previously transmitted information for which a corresponding acknowledgement was not received. In addition, the transmitting terminal may determine that congestion may exist in the network resulting in the previously transmitted information not being received by the receiving terminal. The previously transmitted information may be considered by the transmitting terminal to be “lost” in the network. In response to a determination of congestion in the network, or network congestion, the transmitting terminal may also reduce the size of the congestion window. The reduction in the size of the congestion window may result in a reduction in the information transfer rate between the transmitting terminal and the receiving terminal. Once reduced, the size of the congestion window may subsequently begin to increase once again. A maximum information transfer rate for a terminal may be determined by the speed of the NIC, which may represent the maximum rate at which the NIC may transmit or receive information via a communications media to a network.

0008As NIC speeds increase, the processing demands required to receive and transmit information at those speeds may also increase. For example, when a frame is received at receiving terminal, the NIC card in the receiving terminal may send a notification to the central processing unit (CPU) in the receiving terminal. The CPU may perform protocol related processing tasks related to the processing of received or transmitted packets. As the NIC speed increases, the number of such notifications, or interrupts, in a time interval may also increase. The volume of such interrupts may increase to the extent that the CPU is not able to perform other tasks. A user of the receiving terminal may observe degraded performance in applications, and/or in response to user input.

0009A TCP offload engine, or TOE, may comprise a technology for a TCP/IP (Internet Protocol) optimized NIC that processes TCP packets. This may result in an offload of these tasks from the CPU. An example of an application of the TOE may be in 10 Gigabit Ethernet NICs. 10 Gigabit Ethernet may comprise a standard that is specified in IEEE 802.3ae, and may define an information transfer rate of 10 gigabits per second. This rate may also be referred to as the “line rate”. In some applications, 10 Gigabit Ethernet may be utilized to provide high speed interconnection between terminals, such as personal computers and computer workstations, and computer storage devices, such as disk drives, based on the Internet small computer systems interface (iSCSI). In addition, iSCSI may be utilized to provide high speed interconnect between various devices in a network comprising end stations, such as personal computers and computer workstations, and server devices, such as world wide web (WWW) servers, email servers, and streaming media servers. In some of these applications, information may be transmitted between, for example, a computer storage device, and a computer workstation, for a time duration that is long in comparison to a typical duration of an information transfer over the network. These long time duration information transfers may be referred to as “long lived” information flows, or long lived flows.

0010A plurality of devices that are connected to a network may transmit information. The aggregate quantity of traffic generated by the plurality of devices may exceed the capacity of the network for transporting information between a transmitting terminal or end station and a receiving terminal or end station. A portion of the quantity of traffic generated may be discarded by a device within the network. Packets that comprise information that is discarded may be regarded as lost packets. As interface speeds at NICs increase, the likelihood of congestion in the network may also increase. In addition, as the number of long lived flows increases, the likelihood of network congestion may also increase.

0011Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.

BRIEF SUMMARY OF THE INVENTION

0012A system and/or method is provided for TCP traffic smoothing, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

0013These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref>a is a diagram of an exemplary network and end stations that may be utilized in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 1</figref>b is a block diagram of an exemplary end station that may be utilized for transmission control protocol (TCP) traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 1</figref>c is a block diagram of an exemplary end station comprising a network interface card that may be utilized for transmission control protocol (TCP) traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 2</figref>a illustrates an exemplary packet transmission via a TCP network that may be utilized in connection with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 2</figref>b illustrates an exemplary subsequent packet transmission via a TCP network that may be utilized in connection with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 2</figref>c illustrates an exemplary packet discard in a TCP network that may be utilized in connection with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 3</figref>a illustrates information transmission that is compliant with a traffic profile in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 3</figref>b illustrates information transmission that is noncompliant with a traffic profile, and with token bucket fill in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 3</figref>c illustrates information transmission that is noncompliant with a traffic profile, and with a full token bucket in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 3</figref>d illustrates information transmission that is compliant with a traffic profile, and with token bucket emptying in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of an exemplary system that may be utilized to perform traffic smoothing on a per information flow basis, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 5</figref>a is a block diagram of an exemplary system that may be utilized to perform traffic smoothing on a per class of service (COS) basis, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 5</figref>b is a block diagram of an exemplary system that may be utilized to perform traffic smoothing on aggregate NIC traffic, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 6</figref>a is a flow chart illustrating steps that may be utilized in an exemplary system for token bucket fill, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 6</figref>b is a flow chart illustrating steps that may be utilized in an exemplary system for token bucket based TCP traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram illustrating ingress switch traffic smoothing, in accordance with an embodiment of the invention.

<figref idref="DRAWINGS">FIG. 8</figref> is a block diagram illustrating egress switch traffic smoothing, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

0031Certain embodiments of the invention may be found in a method and system for TCP traffic smoothing. Traffic smoothing may comprise a method for controlling data transmission in a communications system that further comprises scheduling the timing of transmission of information from a TCP offload engine (TOE) based on a traffic profile. Traffic smoothing may comprise transmitting information from a TOE at a rate that is either greater than, approximately equal to, or less than, the rate at which the information was generated. Some conventional network interface cards (NIC) that utilize TOEs may not provide a mechanism that enables traffic shaping. By not providing a mechanism for traffic shaping, there may be a greater probability of lost packets in the network.

0032<figref idref="DRAWINGS">FIG. 1</figref>a is a diagram of an exemplary network and end stations that may be utilized in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 1</figref>a there is shown a network comprising a plurality of Ethernet switches 10, 20, 30, 40, and 50, an external network 60, and a plurality of end stations comprising computer workstations and servers. In <figref idref="DRAWINGS">FIG. 1</figref>a, there is shown a plurality of computer workstations 22, 24, 26, 32, 34, and 36, in addition to a plurality of servers, comprising a database server 12, a streaming media server 14, a file server 16, and a network management server 52. Also shown is a plurality of end station to network interfaces, 11, 13, 15, 21, 23, 25, 31, 33, 35, and 50, and a plurality of network device to network device interfaces 41, 51, 53, 55, 57, and 59.

0033The computer workstations 22, 24, 26, 32, 34, and 36 may comprise end stations that may be utilized by a user to execute programs and applications, for example, email, World Wide Web (WWW) browsers, database access programs, and media players. Computer workstation 22 may comprise a NIC that is coupled to interface 21. Computer workstation 22 may utilize a TOE to transmit information to, or receive information from, the network, via interface 21. Similarly, computer workstations 24, 26, 32, 34, and 36 may utilize interfaces 23, 25, 31, 33, and 35 respectively.

0034The database server 12 may store information in one or more databases. Database server 12 may comprise a NIC that is coupled to interface 13. One or more records comprising information may be retrieved from a database and subsequently transmitted to the network via interface 13. One or more records may be received from the network, via interface 13, and stored in a database.

0035The streaming media server 14 may store one or more video, audio, or multimedia programs. Streaming media server 14 may comprise a NIC that is coupled to interface 15. At least a portion of a program may be retrieved from secondary storage, and/or buffered in primary storage, and transmitted to the network via interface 15. The time duration of the transmission via the network may be greater than, approximately equal to, or less than the time duration of the program. A program may be received from the network, via interface 15, and stored.

0036The file server 16 may store information in one or more files. File server 16 may comprise a NIC that is coupled to interface 11. Files may be retrieved and subsequently transmitted to the network via interface 11. One or more files may be received from the network via interface 11, and stored.

0037The network management server 52 may store information pertaining to the configuration and/or availability of various network communication devices and/or interfaces within the network. The network management server 52 may also store information pertaining to the configuration and/or availability of end stations and interfaces connected to those end stations. Network management server 52 may comprise a NIC that is coupled to interface 51. The network management server 52 may be utilized to set configuration parameters that control the performance and/or behavior of network communication devices, interfaces, and/or end stations. The server 52 may utilize manage a network by utilizing a protocol such as the simple network management protocol (SNMP). The server 52 may transmit information comprising commands to set configuration parameters, or information comprising a report of current values of configuration parameters to the network via interface 51. The server 52 may also receive information comprising requests for configuration parameters from the network via interface 51.

0038The Ethernet switches 10, 20, 30, 40, and 50 may comprise exemplary network communications devices that may be utilized to facilitate the transfer of information between end stations that are coupled to the network. The switch 10 may comprise one or more line cards that are coupled to interfaces 11, 13, 15, and 53. The switch 10 may communicate with server 12 via interface 13, with server 14 via interface 10, with server 16 via interface 11, and with switch 50 via interface 53. The switch 10 may facilitate the transfer of information from any of the group comprising end stations 12, 14, and 16, and the switch 50, to any other end station or switch among this group.

0039The switch 20 may comprise one or more line cards that are coupled to interfaces 21, 23, 25, and 55. The switch 20 may communicate with workstation 22 via interface 21, with workstation 24 via interface 23, with workstation 26 via interface 25, and with switch 50 via interface 55. The switch 20 may facilitate the transfer of information from any of the group comprising end stations 22, 24, and 26, and the switch 50, to any other end station or switch among this group.

0040The switch 30 may comprise one or more line cards that are coupled to interfaces 31, 33, 35, and 41. The switch 30 may communicate with workstation 32 via interface 31, with workstation 34 via interface 35, with workstation 36 via interface 33, and with switch 40 via interface 41. The switch 30 may facilitate the transfer of information from any of the group comprising end stations 32, 34, and 36, and the switch 40, to any other end station or switch among this group.

0041The switch 30 may comprise one or more line cards that are coupled to interlaces 31, 33, 35, and 41. The switch 30 may communicate with workstation 32 via interface 31, with workstation 34 via interface 35, with workstation 36 via interface 33, and with switch 40 via interface 41. The switch 30 may facilitate the transfer of information from any of the group comprising end stations 32, 34, and 36, and the switch 40, to any other end station or switch among this group.

0042The switch 40 may comprise one or more line cards that are coupled to interfaces 41, and 57. The switch 40 may communicate with switch 30 via interface 41, and with switch 50 via interface 57. The switch 30 may facilitate the transfer of information from either of the group comprising switches 30 and 50, to either other switch among this group.

0043The switch 50 may comprise one or more line cards that are coupled to interfaces 51, 53, 55, 57 and 59. The switch 50 may communicate with server 52 via interface 51, with switch 10 via interface 53, with switch 20 via interface 55, with switch 40 via interface 57, and with the external network 60 via interface 59. The switch 50 may facilitate the transfer of information from any of the group comprising end station 52, switches 10, 20, 40, external network 60 to any other end station, switch, or external network among this group.

0044The external network 60 may comprise one or more networks that may be coupled, directly or indirectly, to interface 59. One or more end stations may be coupled to the external network 60.

0045In operation, the network shown in <figref idref="DRAWINGS">FIG. 1</figref>a may comprise a communications system that enables a transmission of information between end stations that are coupled to the network. The network may also enable the end stations to transmit information to, or receive information from, an external network 60. Network congestion may occur that may result in packets being lost. For example, the plurality of servers 12, 14, and 16, and the plurality of workstations 22, 24, 26, 32, 34, and 36 may transmit information to the external network 60 during approximately overlapping time intervals. If the aggregate line rate of interfaces 11, 13, and 15 is greater than the line rate of interface 53, network congestion may occur at switch 10. If the aggregate line rate of interfaces 21, 23, and 25 is greater than the line rate of interface 55, network congestion may occur at switch 20. If the aggregate line rate of interfaces 31, 33, and 35 is greater than the line rate of interface 41, network congestion may occur at switch 30. If the aggregate line rate of interfaces 53, 55, and 57 is greater than the line rate of interface 59, network congestion may occur at switch 50.

0046<figref idref="DRAWINGS">FIG. 1</figref>b is a block diagram of an exemplary end station that may be utilized for transmission control protocol (TCP) traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 1</figref>b there is shown an end system 100, and a network interface 160. The end system 100 may comprise a central processing unit (CPU) 110, a memory controller 120, a host memory 130, a host interface 140, and a NIC 150. The NIC 150 may comprise a TOE or a TCP-enabled Ethernet controller (TEEC) 170.

0047The CPU 110 may be coupled to the memory controller 120, and to host memory 130. The CPU 110 may comprise suitable logic, circuitry, and/or code to communicate commands and/or information packets to the memory controller 120 or to host memory 130. The host memory 130 may be coupled to the CPU 110, the memory controller 120, and the host interface 140. The host memory 130 may comprise suitable logic, circuitry, and/or code to be utilized to store, or write, and retrieve, or read, information. It may comprise a plurality of memory technologies such as random access memory (RAM). The memory controller 120 may be coupled to the CPU 110, the host memory 130, and to the host interface 140. The memory controller 120 may comprise suitable logic, circuitry, and/or code to communicate commands to the host memory 130 to control writes to and/or reads from host memory 130. The effect of control of reads from host memory may schedule the timing of reads from and/or writes to host memory 130. The memory controller 130 may be a component in a chip set that comprises a plurality of integrated circuit devices. The host interface 140 may be coupled to the memory controller 120, to the host memory 130, and to the NIC 150. The host interface 140 may comprise suitable logic, circuitry, and/or code to be utilized to communicate information being read, from host memory 130, to the NIC 150. The host interface 140 may also be utilized to communicate information being received, from the NIC 150, to the host memory 130 where the information may be written. The NIC 150 may be coupled to the host interface 140 and to the network interface 160. The NIC 150 may comprise suitable logic, circuitry, and/or code to be utilized to transmit information from the host interface 140 to a network via the interface 160. The NIC 150 may be utilized to receive information from the network via the interface 160, and to communicate the received information to the host interface 140. The TOE 170 may comprise suitable logic, circuitry, and/or code to perform protocol processing and to construct one or more packets and/or one or more frames that may be utilized to transmit information to the network via the interface 140.

0048In operation, the CPU 110 may execute steps in an application program that utilizes the TOE 170 in the NIC 150 to transmit information to a network via the interface 160. The CPU 110 may communicate instructions that cause a computer storage device, such as a disk drive, to transfer data to the host memory 130. The CPU 110 may subsequently communicate instructions to the memory controller 120 that causes host memory 130 to transfer the data to the host interface 140. The host interface 140 may communicate the data to the NIC 150. The TOE 170 within the NIC may perform protocol processing on the data to construct one or more packets and/or one or more frames that may be utilized to transmit the data across the network to a receiving terminal. The memory controller 120 may schedule the timing of reading of data from host memory 130 such that the memory controller may also schedule the timing of transmission of packets comprising the data from the TCP offload engine to the network. The memory controller 120 may utilize a traffic profile to determine a schedule. For example, a traffic profile may specify a rate at which information is to be transmitted from the TOE to the network. That rate may be greater than, approximately equal to, or less than a rate at which information is transferred from the CPU 110 to the host memory 130. The rate may also be greater than, approximately equal to, or less than a rate at which information is transferred from a computer storage device to the host memory 130. The rate at which information is transferred to the host memory 130 for subsequent transmission to the network via an interface 160, may be referred to as the rate at which information was generated.

0049<figref idref="DRAWINGS">FIG. 1</figref>c is a block diagram of an exemplary end station comprising a network interface card that may be utilized for transmission control protocol (TCP) traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 1</figref>c there is shown an end system 105, and a network interface 160. The end system 105 may comprise a central processing unit (CPU) 110, a host memory 130, and a NIC 155. The NIC 155 may comprise a memory controller 120, a dedicated memory 135, and a TOE or a TEEC 170.

0050In comparison to <figref idref="DRAWINGS">FIG. 1</figref>b, the memory controller 120 may be resident on the NIC in the exemplary end system illustrated in <figref idref="DRAWINGS">FIG. 1</figref>c. This may enable at least a portion of traffic shaping to be performed by the NIC 155. The CPU 110, memory controller 120, host memory 130, and TOE 170 may be as described in connection with <figref idref="DRAWINGS">FIG. 1</figref>b. The memory controller 120 may be coupled to the TOE 170 in <figref idref="DRAWINGS">FIG. 1</figref>c. The dedicated memory 135 may comprise suitable logic, circuitry, and/or code to be utilized to store, or write, and retrieve, or read, information. In operation the memory controller 120 and/or TOE 170 may utilize the dedicated memory 135 to perform tasks related to traffic smoothing.

0051<figref idref="DRAWINGS">FIG. 2</figref>a illustrates an exemplary packet transmission via a TCP network that may be utilized in connection with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 2</figref>a there is shown an Ethernet switch 202, a plurality of end stations 210, and 220, a plurality of interfaces 211, 221, 231, a plurality of packets 216, 226, and an external network 234. The Ethernet switch 202 may comprise memory 204. The end station 210 may comprise a NIC 212, and a CPU 214. The end station 220 may comprise a NIC 222, and a disk drive 224.

0052The NIC 212 may utilize a protocol, such as TCP, to transmit packet 216 via interlace 211. The NIC 222 may utilize a protocol, such as TCP, to transmit packet 226 via interface 221. The packet 216 may comprise information that is generated by CPU 214. The packet 226 may comprise information that is generated by disk drive 224. The NIC 212 may be coupled to interface 211. The NIC 222 may be coupled to interface 221. The Ethernet switch 202 may be coupled to interfaces 211, 221, and 231.

0053In operation, the end station 210 may transmit a packet 216 to a receiving end station attached to the external network 234. The Ethernet switch 202 may receive the packet 216 via interface 221. The Ethernet switch 202 may subsequently transmit the packet 216, via interface 231, to the external network 234. Similarly, the end station 220 may transmit a packet 226 to a receiving end station attached to the external network 234 via Ethernet switch 202. The interlaces 211, and 221, and 231 may be characterized by a line rate of approximately 10 gb/s. The packet 216 may comprise a plurality of binary bits that may be transmitted via interface 211 at a rate of 10 gb/s. The packet 216 may comprise a plurality of binary bits that may be transmitted via interface 221 at a rate of 10 gb/s. The packet 216 may be transmitted from the end station 210 to the Ethernet switch 202. The received packet 216 may be stored in memory 204 at the Ethernet switch 202 prior to being forwarded to the external network 234 via interface 231. The packet 226 may be transmitted from the end station 220 to the Ethernet switch 202. The received packet 226 may be stored in memory 204 at the Ethernet switch 202 prior to being forwarded to the external network 234 via interface 231.

0054<figref idref="DRAWINGS">FIG. 2</figref>b illustrates an exemplary subsequent packet transmission via a TCP network that may be utilized in connection with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 2</figref>b there is shown an Ethernet switch 202, a plurality of end stations 210, and 220, a plurality of interfaces 211, 221, 231, a plurality of packets 216, 217, 226, 227 and an external network 234. The Ethernet switch 202 may comprise memory 204. The end station 210 may comprise a NIC 212, and a CPU 214. The end station 220 may comprise a NIC 222, and a disk drive 224.

0055In comparison to <figref idref="DRAWINGS">FIG. 2</figref>a, <figref idref="DRAWINGS">FIG. 2</figref>b may illustrate packet transmission at a subsequent time instant. In <figref idref="DRAWINGS">FIG. 2</figref>b, the packets 216 and 226 may have been received by the Ethernet switch 202, and stored in memory 204. The packets 216 and 226 may utilize the full storage capacity of the memory 204. The NIC 212 may not utilize traffic smoothing. After transmitting packet 216, end station 210 may continue to transmit information at a 10 gb/s rate, subsequently transmitting packet 217 via interface 211. The NIC 222 may not utilize traffic smoothing. After transmitting packet 226, end station 220 may continue to transmit information at a 10 gb/s rate, subsequently transmitting packet 227 via interface 221.

0056<figref idref="DRAWINGS">FIG. 2</figref>c illustrates an exemplary packet discard in a TCP network that may be utilized in connection with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 2</figref>c there is shown an Ethernet switch 202, a plurality of end stations 210, and 220, a plurality of interfaces 211, 221, 231, a plurality of packets 216, 217, 226, 227 and an external network 234. The Ethernet switch 202 may comprise memory 204. The end station 210 may comprise a NIC 212, and a CPU 214. The end station 220 may comprise a NIC 222, and a disk drive 224.

0057In comparison to <figref idref="DRAWINGS">FIG. 2</figref>b, <figref idref="DRAWINGS">FIG. 2</figref>c may illustrate packet transmission and discard. Traffic received by the Ethernet switch 202 via interfaces 211 and 221 may be transmitted via interface 231. The aggregate line rate of the interfaces 211 and 221 may equal approximately 20 gb/s. This aggregate line rate may be greater than the approximately 10 gb/s line rate of the interface 231. As a result, packets may arrive at the Ethernet switch 202, and be stored in memory 204, at a rate that is greater than the rate at which packets may be transmitted by the Ethernet switch 202, and retrieved from memory 204. <figref idref="DRAWINGS">FIG. 2</figref>c may illustrate that the packet 226 has been retrieved from memory 204 and transmitted via interface 231. The retrieval of packet 226 from memory 204 may free space in memory for a subsequent packet. Packet 217 may be stored in memory 204. The memory 204 may not comprise free space to receive a subsequent packet 227. Consequently, the Ethernet switch 202 may discard packet 227.

0058<figref idref="DRAWINGS">FIG. 3</figref>a illustrates information transmission that is compliant with a traffic profile in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 3</figref>a there is shown a NIC 302. The NIC 302 may comprise a token bucket 304, a token 305, a TOE 350, and a plurality of packets 306, 308, . . . , 310. The packets 306, 308, . . . , 310 may be generated by the TOE 350.

0059The NIC 302 may utilize a traffic profile that specifies a rate of transmission of information that is approximately equal to R bytes/second. The rate of R bytes/second may be less than the line rate for the NIC 302. As long as the rate at which traffic was generated is approximately equal to R bytes/second, the traffic smoothing may comprise scheduling the transmitting information in packets 306, 308, . . . , 310 from the TOE 350 at a rate that is approximately equal to the rate at which the information was generated. At a given time instant, the state of the token bucket 304 may comprise a token 305. Tokens may arrive in the token bucket 304 at a rate, for example a rate of R. With each arrival a corresponding token count associated with the token bucket 304 may increase. The token count may increase to a maximum value, Tmax. The token bucket 304 may be considered to be in a full state, or full, when the current token count value is Tmax. Subsequent to the transmission of the packet 306 by the TOE 350, the number of tokens contained in the token bucket 304 may decrease. This decrease may change a corresponding token count associated with the token bucket 304. If a current value of the token count is less than or equal to 0, the traffic shaping algorithm may inhibit the NIC 302 from transmitting a subsequent packet 308 until the token count achieves a value greater than 0. The token bucket 304 may be considered to be in an empty state, or empty, when the current token count is less than or equal to 0. If the rate at which information is generated is approximately equal to R bytes/second, then the token count associated with the token bucket 304 may be greater than 0 at time instants when packets 306, 308, and 310 are transmitted by the TOE 350.

0060<figref idref="DRAWINGS">FIG. 3</figref>b illustrates information transmission that is noncompliant with a traffic profile, and with token bucket fill in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 3</figref>b there is shown a NIC 302. The NIC 302 may comprise a token bucket 304, a plurality of tokens 305, 307, 309, and 311, a TOE 350, and a plurality of packets 316, 318, 320, . . . , 322. The packets 316, 318, 320, . . . , 322 may be generated by the TOE 350.

0061The NIC 302 may utilize a traffic profile that specifies a rate of transmission of information that is approximately equal to R bytes/second. The rate of R bytes/second may be less than the line rate for the NIC 302. If the rate at which traffic was generated is approximately equal to Q bytes/second, where the rate Q is greater than the rate R, the traffic smoothing may comprise scheduling the transmitting information in packets 316, 318, 320, . . . , 322 from the TOE 350 at a rate that is approximately equal to the rate at which the information was generated for a limited period of time. That period of time may be determined based on the state of the token bucket 304. If packets are transmitted at the rate Q>R for a time increment, the token count may be reduced at a rate that exceeds the rate at which tokens may be replenished. At the start of transmission at the rate Q>R, the token count associated with the token bucket 304 may have achieved a value of Tmax. This may indicate that the token bucket 304 is full and can accept no more token arrivals. The time interval during which information may be transmitted at a rate Q>R, tburst, may be less than or equal to Tmax/(Q−R), for example.

0062<figref idref="DRAWINGS">FIG. 3</figref>c illustrates information transmission that is noncompliant with a traffic profile, and with a full token bucket in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 3</figref>c there is shown a NIC 302. The NIC 302 may comprise a token bucket 304, a TOE 350, and a plurality of packets 318, 320, . . . , 322, 324. The packets 318, 320, . . . , 322, 324 may be generated by the TOE 350.

0063Continuing from the discussion of <figref idref="DRAWINGS">FIG. 3</figref>b, if the token count associated with the token bucket 304 reaches a value that is less than or equal to 0 while the rate at which traffic is generated continues at a rate approximately equal to Q bytes/second, where the rate Q is greater than the rate R, the traffic smoothing may comprise scheduling the transmitting information in packets 318, 320, . . . , 322, 324 from the TOE 350 at a rate that is less than the rate at which the information was generated. When the token bucket 304 is in an empty state, traffic smoothing may no longer permit information to be transmitted by the TOE 350 at the rate of approximately Q bytes/second. In this case, information generated for inclusion in packet 324 may not be transmitted by the TOE 350 in accordance with the schedule in which the packet 324 was generated. As a result of traffic smoothing, the transmission of packet 324 may be blocked in <figref idref="DRAWINGS">FIG. 3</figref>c. The end system 105 that comprises the NIC 302 may be required to buffer the information in host memory 130 until it is allowed to be scheduled for transmission. The packet 324 may not be allowed to be scheduled for transmission by the TOE 350 until the token count associated with the token bucket 304 reaches a value greater than 0, and is no longer in an empty state.

0064<figref idref="DRAWINGS">FIG. 3</figref>d illustrates information transmission that is compliant with a traffic profile, and with token bucket emptying in an exemplary NIC that may be utilized for TCP traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 3</figref>d there is shown a NIC 302. The NIC 302 may comprise a token bucket 304, a plurality of tokens 305, 307, 309 and 311, and a plurality of packets 336, 338, . . . , 340. The packets 336, 338, . . . , 340 may be generated by the TOE 350.

0065Continuing from the discussion of <figref idref="DRAWINGS">FIG. 3</figref>c, if the rate at which traffic was generated is reduced to a rate of approximately T bytes/second, where the rate T is less than the rate R for a decrementing time increment, the rate at which tokens arrive in the token bucket 304 may be greater than the rate at which tokens are removed. As transmission continues at the rate T<R the token count associated with the token bucket 304 may increase. If at the start of a time interval, the token bucket 304 is empty, over a time interval during which the rate T<R, the state of the token bucket 304 may change as a result of the addition of a token 305. If transmission continues at this rate for a subsequent time interval, the state of the token bucket 304 may subsequently change due to the arrival of token 307. As transmission continues at this rate, the state of the token bucket 304 may change by the addition of token 309, and afterwards, token 311. With addition of tokens 305, 307, 309, and 311 to the token bucket 304, the associated token count may also increase. In various embodiments of the invention, the token count may increase until it reaches a maximum value, Tmax. At that point, the token bucket 304 may be full and no further token arrivals may occur while the token bucket 304 remains in a full state.

0066<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of an exemplary system that may be utilized to perform traffic smoothing on a per information flow basis, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 4</figref> there is shown a NIC 402. The NIC 402 may comprise a traffic shaper 404. The traffic shaper may perform traffic shaping on at least a portion of the aggregate of information flows 406 that may be transmitted by the NIC 402. The aggregate of flows 406 may comprise a plurality of individual information flows 408, 410, . . . , 412, and a plurality of traffic shapers 414, 416, . . . , 418. The traffic shaper 414 may perform traffic shaping on the individual information flow 408. The traffic shaper 416 may perform traffic shaping on the individual information flow 410. The traffic shaper 418 may perform traffic shaping on the individual information flow 412.

0067An information flow may be uniquely identified based on information contained in header information contained in frames and/or packets that may be generated by the TOE or higher layer protocols. The information flow may, for example, be uniquely identified based on a protocol, a source address, a destination address, a source port, a destination port and/or header fields found in higher layer protocols. A protocol may identify a protocol being utilized to transmit a packet via a network. Examples of protocol may comprise TCP, or the user datagram protocol (UDP), or iSCSI, which operates above TCP. An example of source and/or destination address is an internet protocol (IP) address. A source and/or destination port may identify an application being utilized by the transmitting end station and receiving end station that are engaged in a communication. Examples of ports may represent the hypertext transfer protocol (HTTP), the file transfer protocol (FTP), or the simple mail transfer protocol (SMTP).

0068In various embodiments of the invention, a traffic shaper 414 may utilize a traffic profile to perform traffic shaping on information transmitted in association with an information flow 408. A subsequent traffic shaper 416 may utilize a traffic profile that is different from that of traffic shaper 414. Traffic shaper 416 may perform traffic shaping on information transmitted in associated with an information flow 410. For some information flows among the plurality of information flows 408, 410, . . . , 412, no traffic shaping may be performed.

0069<figref idref="DRAWINGS">FIG. 5</figref>a is a block diagram of an exemplary system that may be utilized to perform traffic smoothing on a per class of service (COS) basis, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 5</figref>a there is shown a NIC 502. The NIC 502 may comprise a traffic shaper 524. The traffic shaper may perform traffic shaping on at least a portion of the aggregate of information flows 526 that may be transmitted by the NIC 502. The aggregate of flows 526 may comprise a plurality of individual classes of service 528, . . . , 528a. The class of service 528 may comprise a plurality of individual information flows 508, 510, . . . , 512, and a traffic shaper 530. The class of service 528a may comprise a plurality of individual information flows 508a, 510a, . . . , 512a, and a traffic shaper 530a.

0070The traffic shaper 530 may perform traffic shaping on the information transmitted among an aggregate of individual information flows 508, 510, . . . , 512. The traffic shaper 530a may perform traffic shaping on the information transmitted among an aggregate of individual information flows 508a, 510a, . . . , 512a.

0071An information flow may be associated with a specific COS based on information contained in header information contained in frames and/or packets that may be generated by the TOE. The COS may be uniquely identified based on a type of service (TOS) field, for example contained in header information. A plurality of information flows may be associated with a common COS. A COS may identify information flows with common transmission characteristics. For example, a COS may identify information flows for which information is transmitted at a rate that is approximately constant. Another example of a COS may identify information flows for which information is transmitted at a rate that varies but with a specified maximum rate. A COS may also be utilized to identify information flows that utilize one or more protocols. A COS may also identify information flows for which the rate at which information is transmitted is not specified, for example.

0072In various embodiments of the invention, a traffic shaper 528 may utilize a traffic profile to perform traffic shaping on information transmitted in association with a COS 528. The information transmitted in association with COS 528 may comprise an aggregate of the information transmitted in a plurality of information flows 508, 510, . . . , 512. A subsequent traffic shaper 530a may utilize a traffic profile that is different from that of traffic shaper 530. The information transmitted in association with COS 528a may comprise an aggregate of the information transmitted in a plurality of information flows 508a, 510a, . . . , 512a. For some COSs among the plurality of COSs 528, . . . , 528a, no traffic shaping may be performed.

0073<figref idref="DRAWINGS">FIG. 5</figref>b is a block diagram of an exemplary system that may be utilized to perform traffic smoothing on aggregate NIC traffic, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 5</figref>b there is shown a NIC 502. The NIC 502 may comprise a traffic shaper 544. The traffic shaper may perform traffic shaping on the aggregate of information flows 546 that may be transmitted by the NIC 502. The aggregate of flows 546 may comprise a traffic shaper 548, a plurality of individual classes of service 552, . . . , 552a. The class of service 552 may comprise a plurality of individual information flows 508, 510, . . . , 512, and a traffic aggregator 550. The traffic aggregator 550 may aggregate information transmitted among a plurality of information flows 508, 510, . . . , 512. The class of service 552a may comprise a plurality of individual information flows 508a, 510a, . . . , 512a, and a traffic aggregator 550a. The traffic aggregator 550a may aggregate information transmitted among a plurality of information flows 508a, 510a, . . . , 512a.

0074The traffic shaper 548 may perform traffic shaping on the aggregate of information transmitted by the NIC 502 comprising an aggregate among individual COSs 552 and 552a, and among individual information flows 508, 510, . . . , 512, 508a, 510a, . . . , 512a. In various embodiments of the invention, a traffic shaper 548 may utilize a traffic profile to perform traffic shaping on the aggregate of information transmitted by a NIC 502.

0075<figref idref="DRAWINGS">FIG. 6</figref>a is a flow chart illustrating steps that may be utilized in an exemplary system for token bucket fill, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 6</figref>a, in step 602 state variable, Tmax, may be set to a determined value. The state variable Token_Cnt=0, and Token_Fill_Rate=R. The variable Tmax may be utilized to determine a maximum number of tokens that may be stored in the token bucket 304. The variable Token_Cnt may be utilized to determine the current number of tokens contained in the token bucket. The variable Token_Fill_Rate may be utilized to determine a rate at which tokens may be added to the token bucket 304.

0076At step 604 may indicate an elapse of one time unit. Step 606 may determine if the current token count value, token_cnt, has reached a maximum value, Tmax, for the token bucket 304. If the current token count value, token_cnt, has reached the maximum value, Tmax, then step 604 may be next. If the current token count value has not reached the maximum value, Tmax, then the token count value, token_cnt, may be increased by a determined rate, for example, R. Thus, the token count value, token_cnt, may be increased according to: Token—Cnt=Token—Cnt+R equation[1] Step 604 may follow.

0077<figref idref="DRAWINGS">FIG. 6</figref>b is a flow chart illustrating steps that may be utilized in an exemplary system for token bucket based TCP traffic smoothing, in accordance with an embodiment of the invention. The process flow illustrated in <figref idref="DRAWINGS">FIG. 6</figref>b may be performed concurrently with the process flow illustrated in <figref idref="DRAWINGS">FIG. 6</figref>a, in various embodiments of the invention. Referring to <figref idref="DRAWINGS">FIG. 6</figref>b, step 604 may determine whether a packet has arrived at the TOE 350 for transmission, or whether a packet previously arrived packet has been suspended due to traffic smoothing, in accordance with an embodiment of the invention. If not, the process flow may wait at step 612 until a packet has arrived. If step 612 determines that a packet has arrived or that a packet is currently suspended, step 614 may determine if the current token count value, token_cnt, is greater than 0. If not, then the token bucket may be empty. Consequently, transmission of the packet may be suspended, due to TCP traffic shaping, in step 620. Step 612 may follow. If the token count value, token_cnt, is greater than 0, then step 616 may transmit the packet. Step 618 may decrease the of the token count value, token_cnt, in accordance with the number of binary octets contained in the data frame that may have been transmitted, for example. For example, if the transmitted packet comprises a plurality of octets, LEN, then the token count value, token_cnt, may be decreased according to: Token—Cnt=Token—Cnt−LEN equation[2] Step 612 may follow.

0078Various embodiments of the invention may provide a method and a system for TCP traffic smoothing. By performing traffic smoothing, large bursts of traffic into a switching device within a network may be averted. This may further result in improved performance for applications that execute at devices, such as computer workstations, personal computers, and servers, which connect to the network. This may also result in lower cost switching devices by enabling a reduction in the amount of memory storage required.

0079Various embodiments of the invention may not be limited to performing traffic shaping for information transmitted utilizing the transmission control protocol (TCP). Traffic smoothing may comprise the scheduled timing of transmission of information, and may be applied to information transmitted by a TCP offload engine (TOE) for at least one class of service, or on one or more information flows. An information flow may be identified based on a protocol, a source address, a destination address, a source port, a destination port and/or at least one header field associated with higher layer protocols layers 5 through 7 of the OSI protocol reference model. A class of service may comprise one or more information flows. Traffic smoothing may also be applied to an aggregate quantity of information transmitted by a TOE comprising one or more information flows, and/or one or more classes of service. Traffic smoothing also be applied in combinations. For example, traffic smoothing may be applied to one or more information flows, and/or applied to one or more classes of service, and/or applied to an aggregate quantity of information transmitted by a TOE.

0080Various embodiments of the invention may perform traffic smoothing by determining a quantity of information transmitted by a NIC. The quantity of information transmitted may be measured based on at least a portion of the total number of bits of information that are transmitted by the NIC. For example, traffic smoothing may be performed on a quantity of information comprising one or more entire frames or packets that are transmitted by the NIC, or on a quantity of information comprising a payload portion of each of one or more entire frames or packets.

0081<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram illustrating ingress switch traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 7</figref>, there is shown an Ethernet switch 702, an ingress port 704, a plurality of buffer fill levels 706, 708, 710, 712, an interface 715, and a NIC 722. The NIC 722 may transmit information via interface 715 to the ingress port 704. The ingress port 704 may determine a fill level, comprising buffer fill levels 706, 708, 710, or 712, for example, based upon reception the information from the NIC 722. The fill levels 706, 708, 710, and 712 may indicate corresponding buffer fill levels of ¼, ½, ¾ and FULL respectively, for example. Based on a traffic profile, and on a value of the buffer fill level, the Ethernet switch 702 may communicate a rate control message to the NIC 722. The rate control message may instruct the NIC to reduce a rate at which information is transmitted via the interface 715. The rate control message may instruct the NIC to reduce the rate at which information is transmitted by a rate that corresponds to the buffer fill level. For example for a buffer fill level of 706, 708, 710, or 712, the rate control message may correspondingly instruct the NIC 722 to reduce the rate at which information is transmitted by ¼, ½, ¾ or halt transmission, respectively. For buffer fill levels below buffer fill level 706, no rate control message may be sent. For buffer fill levels between 706 and 708, the rate control message may correspond to the fill level 706. For buffer fill levels between 708 and 710, the rate control message may correspond to the fill level 708. For buffer fill levels between 710 and 712, the rate control message may correspond to the fill level 710. The Ethernet switch 702 may comprise a plurality of ingress ports 704. The Ethernet switch 702 may utilize a traffic profile for one or more ingress ports 704. The Ethernet switch 702 may comprise a plurality of ingress ports, and utilize a corresponding plurality of traffic profiles. The Ethernet switch 702 may utilize a traffic profile in conjunction with information received at the ingress port 704 in association with one or more information flows.

0082<figref idref="DRAWINGS">FIG. 8</figref> is a block diagram illustrating egress switch traffic smoothing, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 8</figref>, there is shown an Ethernet switch 708, a plurality of ingress ports 814, 816, 818, an egress port 804 a plurality of buffer fill levels 806, 808, 810, 812, a plurality of interfaces 815, 817, 819, and a plurality of NICs 822, 824, 826. The NIC 822 may transmit information via interface 815 to the ingress port 814. The NIC 824 may transmit information via interface 817 to the ingress port 816. The NIC 826 may transmit information via interface 819 to the ingress port 818. The Ethernet switch 802 may direct information received via any of ingress ports 814, 816, 818, to be transmitted via the egress port 804. The Ethernet switch 802 may transmit information from the egress port 804 via interface 821. The egress port 804 may determine a buffer fill level, comprising fill levels 806, 808, 810, or 812, for example, based upon reception the information from any of the ingress ports 814, 816, 818. The buffer fill levels 806, 808, 810, and 812 may represent buffer fill levels corresponding to the buffer fill levels 706, 708, 710, and 712 respectively, for example. Based on a traffic profile, and on a value representative of the buffer fill level, the Ethernet switch 802 may communicate a rate control message to any of the NICs 822, 824, 826. The rate control message may instruct the NIC to reduce a rate at which information is transmitted to the Ethernet switch via the corresponding interface. The rate control message may instruct the NIC to reduce the rate at which information is transmitted by a rate that corresponds to the buffer fill level. For example, for a buffer level of 806, 808, 810, or 812, the rate control message may correspondingly instruct a NIC to reduce the rate at which information is transmitted by ¼, ½, ¾, or halt transmission, respectively. For buffer fill levels below buffer fill level 806, no rate control message may be sent. For buffer fill levels between 806 and 808, the rate control message may correspond to the fill level 806. For buffer fill levels between 808 and 810, the rate control message may correspond to the fill level 808. For buffer fill levels between 810 and 812, the rate control message may correspond to the fill level 810. The rate control message may be sent to one NIC or to a plurality of NICs based on the degree to which information transmitted by the NIC, and received at the corresponding ingress port, has contributed to the level of buffer fill at the egress port 804.

0083The Ethernet switch 802 may comprise a plurality of egress ports 804. The Ethernet switch 802 may utilize a traffic profile in association with one or more ingress ports 814, 816, 818. The Ethernet switch 802 may comprise a plurality of ingress ports and egress ports, and utilize a corresponding plurality of traffic profiles based on combinations of ingress and egress ports. The Ethernet switch 802 may utilize a traffic profile in conjunction with information received at of the ingress ports 814, 816, 818, and transmitted via an egress port 804. The Ethernet switch 802 may utilize a traffic profile in association with one or more information flows received via an ingress port, and transmitted via an egress port.

0084Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

0085The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.

0086While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.

Contents6

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US2022021618A1	Cited by	United States of America	Search report
US11552894B2	Cited by	United States of America	Search report
WO0192997A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
WO0219604A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
EP1469853A1	Cites	European Patent Office (EPO)	Applicant
US2002034182A1	Cites	United States of America	Applicant
US2002191604A1	Cites	United States of America	Applicant
US2002194445A1	Cites	United States of America	Applicant
US2003046330A1	Cites	United States of America	Applicant
US2004037319A1	Cites	United States of America	Applicant
US2004042458A1	Cites	United States of America	Applicant
US2006203728A1	Cites	United States of America	Applicant
US5541995A	Cites	United States of America	Applicant
US5588000A	Cites	United States of America	Applicant
US6167027A	Cites	United States of America	Search report
US6411621B1	Cites	United States of America	Applicant
US6434620B1	Cites	United States of America	Applicant
US6496481B1	Cites	United States of America	Applicant
US6522628B1	Cites	United States of America	Search report
US6965941B2	Cites	United States of America	Applicant
US6996070B2	Cites	United States of America	Applicant
US7162630B2	Cites	United States of America	Applicant
US7373500B2	Cites	United States of America	Applicant
US7376755B2	Cites	United States of America	Applicant
US7411959B2	Cites	United States of America	Applicant
US7460473B1	Cites	United States of America	Applicant
US7643420B2	Cites	United States of America	Applicant
US20020034182A1	Cites	United States of America	Third party observation
US20020191604A1	Cites	United States of America	Third party observation
US20020194445A1	Cites	United States of America	Third party observation
US20030046330A1	Cites	United States of America	Third party observation
US20040037319A1	Cites	United States of America	Third party observation
US20040042458A1	Cites	United States of America	Third party observation
US20060203728A1	Cites	United States of America	Third party observation
EP1469853A2	Cites	European Patent Office (EPO)	Third party observation
WO0192997	Cites	World Intellectual Property Organization (WIPO)	Third party observation
WO0219604	Cites	World Intellectual Property Organization (WIPO)	Third party observation
Senapathi et al, Introduction to TCP Offload Engines, downloadable at www.dell.com/powersolutions, 5 pages, 2004.	Non-patent	–	Search report
Boon S. Ang, "An Evaluation of an Attempt at Offloading TCP/IP Protocol Processing onto an i690RN-based iNIC", Hewlett-Packard, 33 pages, Jan. 2001.	Non-patent	–	Applicant
Communication with European Search Report relating to European Application No. 06003525, mailed Jul. 12, 2006.	Non-patent	–	Applicant
International Search Report relating to International Application No. PCT/US03/27129, Mar. 25, 2004.	Non-patent	–	Applicant
W. Stevens, TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms, RFC 2001 (RFC2001), (www.faqs.org.rfcs/rfc2001.html), Jan. 1997.	Non-patent	–	Applicant
Senapathi et al, Introduction to TCP Offload Engines, downloadable at www.dell.com/powersolutions, 5 pages, 2004.	Non-patent	–	Search report
Boon S. Ang, “An Evaluation of an Attempt at Offloading TCP/IP Protocol Processing onto an i690RN-based iNIC”, Hewlett-Packard, 33 pages, Jan. 2001.	Non-patent	–	Third party observation
Communication with European Search Report relating to European Application No. 06003525, mailed Jul. 12, 2006.	Non-patent	–	Third party observation
International Search Report relating to International Application No. PCT/US03/27129, Mar. 25, 2004.	Non-patent	–	Third party observation
W. Stevens, TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms, RFC 2001 (RFC2001), (www.faqs.org.rfcs/rfc2001.html), Jan. 1997.	Non-patent	–	Third party observation

196 members in 6 offices

This recordMember, by publication datePriority claim

Priority claims12

Priority claims
Document	Office	Kind	Date
66106405	United States of America	P	2005-03-11
66106405	United States of America	P	2005-03-11
67389805	United States of America	P	2005-04-22
67389805	United States of America	P	2005-04-22
18740405	United States of America	A	2005-07-21
18740405	United States of America	A	2005-07-21
65240210	United States of America	A	2010-01-05
11187404	–	–	–
US20050187404	–	–	–
US20050661064P	–	–	–
US20050673898P	–	–	–
US20100652402	–	–	–

Members196

Family members, oldest first
Document	Office	Kind
US2003172342A1	United States of America	A1	2003-09-11
EP1345382A2	European Patent Office (EPO)	A2	2003-09-17
EP1357721A2	European Patent Office (EPO)	A2	2003-10-29
EP1385313A1	European Patent Office (EPO)	A1	2004-01-28
US2004019689A1	United States of America	A1	2004-01-29
US2004034725A1	United States of America	A1	2004-02-19
WO2004017173A2	World Intellectual Property Organization (WIPO)	A2	2004-02-26
WO2004017220A1	World Intellectual Property Organization (WIPO)	A1	2004-02-26
US2004042412A1	United States of America	A1	2004-03-04
US2004042458A1	United States of America	A1	2004-03-04
US2004042464A1	United States of America	A1	2004-03-04
US2004042483A1	United States of America	A1	2004-03-04
US2004044798A1	United States of America	A1	2004-03-04
EP1396977A2	European Patent Office (EPO)	A2	2004-03-10
US2004049591A1	United States of America	A1	2004-03-11
WO2004021143A2	World Intellectual Property Organization (WIPO)	A2	2004-03-11
WO2004021150A2	World Intellectual Property Organization (WIPO)	A2	2004-03-11
WO2004021626A2	World Intellectual Property Organization (WIPO)	A2	2004-03-11
WO2004021627A2	World Intellectual Property Organization (WIPO)	A2	2004-03-11
WO2004021628A2	World Intellectual Property Organization (WIPO)	A2	2004-03-11
US2004054814A1	United States of America	A1	2004-03-18
EP1401172A2	European Patent Office (EPO)	A2	2004-03-24
US2004073622A1	United States of America	A1	2004-04-15
WO2004036381A2	World Intellectual Property Organization (WIPO)	A2	2004-04-29
WO2004036387A2	World Intellectual Property Organization (WIPO)	A2	2004-04-29
WO2004036805A2	World Intellectual Property Organization (WIPO)	A2	2004-04-29
US2004085984A1	United States of America	A1	2004-05-06
US2004093411A1	United States of America	A1	2004-05-13
WO2004021626A3	World Intellectual Property Organization (WIPO)	A3	2004-05-13
EP1420561A2	European Patent Office (EPO)	A2	2004-05-19
US2004095949A1	United States of America	A1	2004-05-20
US2004098369A1	United States of America	A1	2004-05-20
WO2004017173A3	World Intellectual Property Organization (WIPO)	A3	2004-05-27
EP1420561A3	European Patent Office (EPO)	A3	2004-06-02
WO2004036387A3	World Intellectual Property Organization (WIPO)	A3	2004-06-10
WO2004036805A3	World Intellectual Property Organization (WIPO)	A3	2004-06-10
EP1345382A3	European Patent Office (EPO)	A3	2004-06-16
WO2004021628A3	World Intellectual Property Organization (WIPO)	A3	2004-06-17
WO2004036381A3	World Intellectual Property Organization (WIPO)	A3	2004-06-24
WO2004021143A3	World Intellectual Property Organization (WIPO)	A3	2004-07-01
US2004133713A1	United States of America	A1	2004-07-08
EP1357721A3	European Patent Office (EPO)	A3	2004-07-14
US2004153578A1	United States of America	A1	2004-08-05
WO2004021150A3	World Intellectual Property Organization (WIPO)	A3	2004-08-12
WO2004021627A3	World Intellectual Property Organization (WIPO)	A3	2004-09-16
EP1460804A2	European Patent Office (EPO)	A2	2004-09-22
EP1460805A2	European Patent Office (EPO)	A2	2004-09-22
EP1460806A2	European Patent Office (EPO)	A2	2004-09-22
EP1460818A1	European Patent Office (EPO)	A1	2004-09-22
US2004184459A1	United States of America	A1	2004-09-23
EP1396977A3	European Patent Office (EPO)	A3	2005-02-09
EP1513321A2	European Patent Office (EPO)	A2	2005-03-09
US2005105531A1	United States of America	A1	2005-05-19
EP1537695A2	European Patent Office (EPO)	A2	2005-06-08
EP1540473A2	European Patent Office (EPO)	A2	2005-06-15
EP1543658A2	European Patent Office (EPO)	A2	2005-06-22
EP1552408A2	European Patent Office (EPO)	A2	2005-07-13
EP1552409A1	European Patent Office (EPO)	A1	2005-07-13
EP1554842A2	European Patent Office (EPO)	A2	2005-07-20
EP1559022A2	European Patent Office (EPO)	A2	2005-08-03
EP1559222A2	European Patent Office (EPO)	A2	2005-08-03
EP1513321A3	European Patent Office (EPO)	A3	2005-09-14
CN1679015A	China	A	2005-10-05
CN1679282A	China	A	2005-10-05
US2005281261A1	United States of America	A1	2005-12-22
US2005281262A1	United States of America	A1	2005-12-22
US2005281280A1	United States of America	A1	2005-12-22
US2005283545A1	United States of America	A1	2005-12-22
EP1460804A3	European Patent Office (EPO)	A3	2006-01-04
EP1559022A4	European Patent Office (EPO)	A4	2006-01-04
WO2006002126A2	World Intellectual Property Organization (WIPO)	A2	2006-01-05
EP1543658A4	European Patent Office (EPO)	A4	2006-01-11
US2006007926A1	United States of America	A1	2006-01-12
US2006015655A1	United States of America	A1	2006-01-19
EP1540473A4	European Patent Office (EPO)	A4	2006-03-15
EP1559222A4	European Patent Office (EPO)	A4	2006-03-15
EP1460806A3	European Patent Office (EPO)	A3	2006-03-22
WO2006002126A3	World Intellectual Property Organization (WIPO)	A3	2006-03-23
CN1757016A	China	A	2006-04-05
EP1460805A3	European Patent Office (EPO)	A3	2006-05-17
EP1385313B1	European Patent Office (EPO)	B1	2006-07-26
DE60307000D1	Germany	D1	2006-09-07
CN1832483A	China	A	2006-09-13
EP1701506A1	European Patent Office (EPO)	A1	2006-09-13
US2006203728A1	United States of America	A1	2006-09-14
EP1345382B1	European Patent Office (EPO)	B1	2006-11-08
EP1734720A2	European Patent Office (EPO)	A2	2006-12-20
DE60309527D1	Germany	D1	2006-12-21
TW200708008A	Taiwan Province of China	A	2007-02-16
EP1759317A2	European Patent Office (EPO)	A2	2007-03-07
DE60307000T2	Germany	T2	2007-03-15
EP1734720A3	European Patent Office (EPO)	A3	2007-04-04
EP1396977B1	European Patent Office (EPO)	B1	2007-05-02
US7224692B2	United States of America	B2	2007-05-29
DE60313550D1	Germany	D1	2007-06-14
CN1985492A	China	A	2007-06-20
DE60309527T2	Germany	T2	2007-09-13
EP1543658B1	European Patent Office (EPO)	B1	2007-10-17
US7295555B2	United States of America	B2	2007-11-13
US2007263630A1	United States of America	A1	2007-11-15

Showing 100 of 196

55 transactions on the USPTO file

Allowed after 1 non-final rejection and 1 RCE.

Non-final rejections: 1
Final rejections: 0
RCEs: 1
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2024-01-08	Expire PatentEXP.	EXP.
2023-07-24	Maintenance Fee Reminder MailedREM.	REM.
2019-06-06	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2011-12-06	Recordation of Patent Grant MailedPGM/	PGM/
2011-12-06	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2011-11-18	Email NotificationEML_NTR	EML_NTR
2011-11-16	Issue Notification MailedAllowedWPIR	WPIR
2011-11-02	Dispatch to FDCD1935	D1935
2011-11-01	Email NotificationEML_NTR	EML_NTR
2011-11-01	Mail Response to 312 Amendment (PTO-271)MN271	MN271
2011-10-27	Response to Amendment under Rule 312N271	N271
2011-10-20	Application Is Considered Ready for IssuePILS	PILS
2011-10-10	Amendment after Notice of Allowance (Rule 312)AllowedA.NA	A.NA
2011-10-10	Issue Fee Payment VerifiedN084	N084
2011-10-10	Issue Fee Payment ReceivedIFEE	IFEE
2011-09-20	Email NotificationEML_NTR	EML_NTR
2011-09-20	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2011-09-19	Correspondence Address ChangeC.AD	C.AD
2011-07-19	Electronic ReviewELC_RVW	ELC_RVW
2011-07-19	Email NotificationEML_NTF	EML_NTF
2011-07-19	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2011-07-14	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2011-07-13	Reasons for AllowanceEX.R	EX.R
2011-06-16	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2011-06-13	Information Disclosure Statement consideredIDSC	IDSC
2011-06-13	Request for Continued Examination (RCE)RCEX	RCEX
2011-06-13	Electronic Information Disclosure StatementEIDS.	EIDS.
2011-06-13	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2011-06-13	Workflow - Request for RCE - BeginBRCE	BRCE
2011-03-11	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2011-03-07	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2011-03-07	Case Docketed to Examiner in GAUDOCK	DOCK
2011-01-16	Date Forwarded to ExaminerFWDX	FWDX
2011-01-10	Response after Non-Final ActionA...	A...
2011-01-10	Request for Extension of Time - GrantedXT/G	XT/G
2010-09-09	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2010-09-09	Non-Final RejectionNon-final rejectionCTNF	CTNF
2010-09-03	Case Docketed to Examiner in GAUDOCK	DOCK
2010-08-23	Case Docketed to Examiner in GAUDOCK	DOCK
2010-07-08	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2010-03-31	Application Dispatched from OIPEOIPE	OIPE
2010-03-26	Sent to Classification ContractorPGPC	PGPC
2010-03-26	Filing Receipt - UpdatedFLRCPT.U	FLRCPT.U
2010-03-24	Information Disclosure Statement consideredIDSC	IDSC
2010-03-24	Electronic Information Disclosure StatementEIDS.	EIDS.
2010-03-24	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2010-03-19	Additional Application Filing FeesADDFLFEE	ADDFLFEE
2010-03-19	Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW	CORRDRW
2010-01-19	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2010-01-19	Filing ReceiptFLRCPT.O	FLRCPT.O
2010-01-19	Corrected PaperCPAP	CPAP
2010-01-06	Cleared by OIPE CSRL194	L194
2010-01-05	Preliminary AmendmentA.PE	A.PE
2010-01-05	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2010-01-05	Initial Exam Team nnIEXX	IEXX

22 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2024-01-30	Lapsed due to failure to pay maintenance feeLapsedFP	FP
2024-01-08	Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS	LAPS
2024-01-08	Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH	STCH
2023-07-24	Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2019-06-06	Maintenance fee paymentMAFP	MAFP
2019-03-21	AssignmentAS	AS
2019-03-21	AssignmentAS	AS
2018-10-29	AssignmentAS	AS
2018-10-29	AssignmentAS	AS
2018-10-04	AssignmentAS	AS
2018-10-04	AssignmentAS	AS
2017-02-03	AssignmentAS	AS
2017-02-01	AssignmentAS	AS
2017-02-01	AssignmentAS	AS
2016-02-11	AssignmentAS	AS
2016-02-11	AssignmentAS	AS
2015-06-08	Fee paymentFPAY	FPAY
2011-11-16	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2011-07-19	Notice of allowance mailedORIGINAL CODE: MN/=.ZAAB	ZAAB
2011-07-18	Notice of allowance and fees dueORIGINAL CODE: NOAZAAA	ZAAA
2011-03-11	Notice of allowance mailedORIGINAL CODE: MN/=.ZAAB	ZAAB
2011-03-10	Notice of allowance and fees dueORIGINAL CODE: NOAZAAA	ZAAA

Method and system for transmission control protocol (TCP) traffic smoothing

Summary by NHIP

Claim Score by NHIP

Abstract