Networking products such as routers use high-speed components for packet movement, i.e., collecting packet data from incoming network device ports and queuing the packet data for transmission to appropriate forwarding device ports. The networking products may also use high-speed special controllers for processing the packets and making forwarding decisions.
Referring to
Each of the ports 104(1)-104(N) has a maximum bit rate at which it can accept and buffer packets. The router 102 can be configured to know the maximum bit rate of the ports 104(1)-104(N), but the router 102 may not know if any of a port's bandwidth is being used for purposes other than receiving packets from the router 102. The ports 104(1)-104(N) can be bi-directional and use bandwidth for receiving and for transmitting packets.
If the router 102 transmits packets to one of the ports 104(1)-104(N) beyond the port's maximum bit rate, then the port's buffer can overflow. Overflow can result in decreased network performance, lost packets, delayed transmission of packets, and/or other similar effects. Furthermore, as the ports 104(1)-104(N) buffer data, the available bit rates of the ports 104(1)-104(N) (the actual, real time bit rates acceptable to the ports 104(1)-104(N) without causing overflow) becomes less than their maximum bit rates. The available bit rates for each of the ports 104(1)-104(N) may unpredictably change with network conditions such as with data sent by devices other than the router 102 and buffered by the ports 104(1)-104(N) and with other bit patterns associated with the multiplexer 108.
The multiplexer 108 can provide the router 102 with information about each port's available bit rate, e.g., by assembling and sending a ready vector 112 on the physical port 106 to the router 102. The router 102 can store the ready vector 112 and read the ready vector 112 before sending data to one of the ports 104(1)-104(N). In this way, the router 102 can know to which of the ports 104(1)-104(N), if any, the router 102 may transmit packets to without causing overflow. The ready vector 112 can also inform the router 102 as to the bit rate the router 102 may use to transmit packets to different ones of the ports 104(1)-104(N).
The ready vector 112 may be a go/no-go vector including multiple bits, where each bit is associated with one of the ports 104(1)-104(N) and indicates whether that port can accept data or not. Either a “one” or a “zero” can indicate that a port has room for more data while the opposite state can indicate that the port is fully buffered and cannot accept more data without overflowing.
Alternatively, the ready vector 112 may be a rate control vector including multiple bits, where two bits are associated with each of the ports 104(1)-104(N). The two bits can indicate four encodings: zero/zero, zero/one, one/zero, and one/one. These encodings can indicate that the port associated with those bits can accept data at a faster bit rate than the current bit rate (a speed-up encoding), can accept data at the current bit rate (a constant encoding), can accept data at a slower bit rate than the current bit rate (a slow-down encoding), and cannot accept any data at all (a no-transmission encoding). The speed-up encoding, the constant encoding, the slow-down encoding, and the no-transmission encoding can each be associated with any of the four bit position encodings. For simplicity in programming, the encoding is typically the same for each of the ports 104(1)-104(N) represented in the ready vector 112, e.g., the code zero/zero always indicates speed-up.
Whether the multiplexer 108 sends the router 102 a go/no-go vector or a rate control vector, the ready vector 112 can indicate the status of multiple ports in one ready vector. For example, a 128-byte ready vector can carry up to 512 port indications using a rate control vector or up to 1024 port indications using a go/no-go vector. In this way, the amount of bandwidth used on the physical port 106 for flow control can be less than that used for sending individual flow-control messages or packets for each of the ports 104(1)-104(N).
Furthermore, the multiplexer 108 may transmit the ready vector 112 in one or more packets, the packets forming a segment. By using a packet-based ready vector, the multiplexer 108 can transmit the status for a large number of ports in one data transmission. For example, the ready vector may include segments 114a, 114b, 114c, etc., each segment including (in this example) sixteen bits of information that may be transmitted as one or more packets or frames. The multiplexer 108 may assemble the ready vector 112 based on information (typically header information) included with the segments 114a, 114b, 114c, etc. indicating the proper order of the segments.
Referring to
In the flow control process 200, the router 102 receives data at block 202 on the physical port 106 from the multiplexer 108. On the physical port 106, the router 102 can receive both ordinary data packets for routing to one of the ports 104(1)-104(N) and ready vectors. Thus, an encapsulation at the front of the data includes a bit that specifies whether the data received by the router 102 includes ordinary packet data or a ready vector by using a “one” for one type of data and a “zero” for the other. The data received by the router 102 could otherwise be identified, e.g., by another encapsulation or header technique, by sending different types of data on different communication links between the router 102 and the multiplexer 108, or by another similar technique.
The router 102 determines at block 204 what type of data it received from the multiplexer 108, e.g., by reading the encapsulation bit. If the data includes a ready vector, then the router 102 handles the data as explained further below.
If the data includes packet data, then the router 102 selects at block 206 one of the ports 104(1)-104(N) for data transmission. The router 102 chooses one of the ports 104(1)-104(N) based on any routing technique. For example, the router 102 may look up a next-hop destination of the packet in a router look-up table included in or accessible to the router 102 and select one of the ports 104(1)-104(N) that services that destination. In this example, assume that the router 102 selects the first port, port 104(1) (“selected port 104”).
The router 102 also reads at block 208 the ready vector 112, or part of the ready vector 112, from a previous test of received data. The router 102 uses the ready vector 112 to determine whether and/or how to transmit the packet to the selected port 104. (That is, the router 102 previously received the ready vector 112 and stored it locally or in an accessible storage mechanism, as described further below.) The router 102 may read the ready vector 112 a certain number of bits at a time. In this example, the router 102 can read thirty-two bits of the ready vector 112 at a time, which corresponds to reading information for thirty-two ports (for a go/no-go ready vector) or for sixteen ports (for a rate control ready vector) at a time.
One way that the router 102 may access the part of the ready vector 112 that includes information on the selected port 104 includes reading thirty-two bits of the ready vector 112 at a base storage address of the ready vector 112 plus the port number of the selected port 104 shifted by five. In this way, the router can obtain a ready vector for thirty-two ports, including the selected port 104.
The router 102 may not read the ready vector 112 after every received packet but rather at a certain rate. The rate at which the router 102 reads the ready vector 112 may depend on a response requirement in transmitting the packets to the ports 104(1)-104(N).
For example, if transmission of data from the router 102 to the multiplexer 108 occurs every fifty cycles, it takes the router 102 sixteen hundred cycles to transmit data to thirty-two ports. If a cycle time equals five nanoseconds, then such transmission can incur a latency of eight microseconds (us). Accounting for reading and, if necessary, assembling the ready vector 112 and for gating data for transmission to the multiplexer 108, this latency could increase from 8 us to 10 us. Adding network latency to this 10 us provides the total bit response latency. Multiplying the total bit response latency by the port rate results in the buffering needed at the ports 104(1)-104(N). This computation may be run in reverse order: given a fixed buffering at the ports 104(1)-104(N), the router 102 can calculate the required ready bit response latency, subtract the network latency, and calculate the number of port ready bits needed to read in one cycle.
For simplicity in this example, assume that the router 102 reads the ready vector 112 after receiving each packet received from the multiplexer 108.
From the ready vector 112 (or the part of the ready vector 112 read that includes information on the selected port 104), the router 102 tests at block 210 the ready vector 112 to determine the readiness of the selected port 104 to receive data from the router 102. If the ready vector 112 is a go/no-go vector, then the router 102 performs a go/no-go process 212, while if the ready vector 112 is a rate control vector, then the router 102 performs a rate control process 214.
In the go/no-go process 212, the router 102 determines if the router 102 may transmit data to the selected port 104 by checking the bit included in the ready vector 112 that corresponds to the selected port 104. The router 102 determines at block 216 if the selected port's ready bit is on or off. Typically, a “one” indicates that a port is on and can accept data while a “zero” indicates that a port is off and cannot accept any more data without overflowing.
If the selected port 104 is on, then the router 102 transmits at block 218 the packet to the selected port 104. Generally, a port is “on” or “off” depending on the one or zero bit state associated with the selected port in the ready vector 112 where one state corresponds to on and the other state corresponds to off. If the selected port 104 is off, then the router 102 skips at block 220 the selected port, either selecting another one of the ports 104(1)-104(N) to transmit the packet to or waiting to transmit the packet to the selected port 104 until a later time, e.g., after a subsequent check of the ready vector 112 reveals that the selected port 104 is on.
Another way that the router 102 may determine if the ready bit for the selected port 104 is on or off includes performing a logic operation on bits of the ready vector 112. In one example, the router 102 performs a logical AND operation on the thirty-two bit ready vector 112 (where a “one” indicates that a port is on) read from storage and a thirty-two bit string of ones. Every “one” in the resulting bit string indicates that the port associated with that bit position can accept data. In this way, the router 102 can identify on and off positions for multiple ports with one operation. The operation may be more efficient than individually checking each bit included in the ready vector 112.
In the rate control process 214, the router 102 determines at block 222 from the ready vector 112 (or a portion of the ready vector 112) if the encoding for the selected port 104 indicates permissibility of transmission to the selected port 104 and, if so, what bit rate to use in the transmission. If the ready vector 112 includes a speed-up encoding, a constant encoding, or a slow-down encoding for the selected bit 104, then the selected port 104 can accept data. The router 102 transmits at block 224 the packet to the selected port 104 at the bit rate indicated by the encoding.
More specifically, the router 102 may increase the current bit rate (for speed-up encoding) or decrease the current bit rate (for slow-down encoding) by a fixed amount or by an amount determined on the fly (e.g., in real time). For example, if the encoding indicates speed-up encoding, then the router 102 can transmit data to the selected port 104 at an “x+1” rate. For every “x” transmissions to the selected port 104, the router 102 can perform another transmission to the selected port 104. Similarly, if the encoding indicates slow-down encoding, then the router 102 can transmit data to the selected port 104 at an “x−−1” rate where for every “x” transmissions to the selected port 104, the router 102 can skip the selected port 104 for transmission one time. (In these examples, “x” represents any positive whole number.)
If the selected port 104 indicates no-transmission encoding, then the selected port 104 cannot accept any more data without possibly overflowing the port buffer, so the router 102 skips at block 226 the selected port 104. The router 102 may select another one of the ports 104(1)-104(N) or wait as described above.
If the router 102 determines at block 204 that the data it received from the multiplexer 108 includes a ready vector, then the router 102 determines 228 if it received a vector subset. A vector subset is, for example, a portion of the ready vector 112 that includes information for some but not all of the ports 104(1)-104(N). The router 102 may store vector subsets differently than a full ready vector.
If the router 102 did not receive a vector subset, then the router 102 stores 230 the received ready vector 112 at a storage location. The storage location may be internal to the router 102, e.g., include temporary or local memory such as a memory cache, a collection of data such as a database, random access memory (RAM), or other similar memory mechanism, or otherwise be accessible to the router 102, e.g., include a collection of data such as a database, a fast memory mechanism such as static RAM (SRAM), a memory cache, or other similar memory mechanisms. The router 102 may then read the ready vector 112 from this storage location as necessary.
If the router 102 did receive a vector subset, then the router 102 assembles 232 the vector subset with other vector subsets. This assembling can include storing the vector subset at a storage location so that the vector subset is stored at an address contiguous to an address including other vector subsets at the storage location that make up the ready vector 112.
Including a segment index with the ready vector 112 sent by the multiplexer 108 to the router 102 can help the router 102 assemble the vector subsets in correct contiguous order. For example, if a full ready vector includes 512 bits, each vector subset sent by the multiplexer 108 could include thirty-six bits: a four bit segment index and a thirty-two bit vector subset. The segment index can indicate the position of the vector subset in the sixteen vector subsets included in the full ready vector, from first (bit indicator 0000) to sixteenth (bit indicator 1111). Using the segment index may be particularly helpful if the router 102 receives vector subsets out of order, i.e., receives a vector subset for bits thirty-three to sixty-four before a vector subset for bits one to thirty-two.
The router 102 may include mechanisms configured to aid in the receipt and transmission of packets. One mechanism can receive, assemble, and classify packets from the multiplexer 108 while the other can transmit the packets to the multiplexer 108 after the router 102 has selected one of the ports 104(1)-104(N).
Referring to
The router 102 receives data, e.g., packets and ready vectors from the multiplexer 108 (see
The receive processor 304 and the transmit processor 304 may use an arbitration system in receiving and transmitting packets that include the ready vector to and from ports such that receiving and/or transmitting may be decided with arbitration, such as through a round robin technique, priority queuing, weighted fair queuing, or other similar type of arbitration technique. In another example, the receive processor 304 and the transmit processor 304 may receive and/or transmit packets to and from the ports based on service rates and maximum port rates. Examples of service rates include constant bit rate (CBR), real-time and non-real-time variable bit rate (rt-VBR and nrt-VBR, respectively), unspecified bit rate (UBR), and other similar types of rates.
The router 102 may include both the inter-chip high bandwidth bus 306 and the dedicated ready bus 308 or the router 102 may include only one of the buses 306, 308. The receive processor 302 may transmit ready vectors to the transmit processor 304 as individual ready vectors or as an assembled ready vector. Sending an assembled ready vector to the transmit processor 304 may enable the transmit processor 304 to more efficiently locate information for particular packet destinations, e.g., ports.
Upon receiving and identifying a packet, the receive processor 302 assembles the packet with other packets included in the same packet stream (if the packet is a packet segment) and classifies the packet. Classifying the packet can include identifying transmission requirements for the packet, such as Quality of Service (QoS) terms, necessary bandwidth, etc. The receive processor 302 transmits the packet (alone or as part of an assembled packet stream) and any associated classification information to the transmit processor 304 on the high bandwidth bus 306 or on the ready bus 308. Typically, the receive processor 302 transmits ready vectors and packets to the transmit processor 304 on the same bus.
The transmit processor 304 can receive ready vectors and packets on the high bandwidth bus 306 and/or the ready bus 308. The transmit processor 304 determines where and how to transmit the packets, e.g., as described in the flow control process 200 (see
Referring to
The receive processor 402 receives and identifies ready vectors and packets and transmits them to the transmit processor 404 or to the dual-port SRAM 406. The receive processor 402 transmits packets (and any associated classification information) to the transmit processor 404 on an inter-chip bus 408.
The receive processor 402 transmits ready vectors to the dual-port SRAM 406 either as assembled vector arrays or as individual ready vectors (vector subsets). If the receive processor 402 transmits individual ready vectors, the receive processor 402 may transmit the individual ready vectors for storage at particular storage locations in the dual-port SRAM 406 so that the dual-port SRAM 406 consecutively stores ready vectors, e.g., the ready vector for bits one to thirty-two at location X 410, the ready vector for bits thirty-three to sixty-four at location X plus thirty-two bits 412, the ready vector for bits sixty-five to ninety-six at location X plus sixty-four bits 414, etc. Such consecutive storage can help the transmit processor 404 more efficiently locate information for particular packet destinations.
The dual-port SRAM 406 stores the ready vectors, and the transmit processor 404 reads the ready vectors from the dual-port SRAM 406. The transmit processor 404 can use data from the ready vectors in determining where and how to transmit packets.
Referring to
In the network configuration 500, the multiplexer 506 can transmit a ready vector 514 on the ready bus 510. The ready vector 514 can be implemented as described for the ready vector 112 of
The router 502 periodically reads the ready bus 510, by issuing select signals (not shown) to the multiplexer 506 in response to fetching data, such as by executing a get command. In response to the select signals, the multiplexer 506 returns the ready vector 514 from a selected one of the ports 504(1)-504(M) to the router 502 over the ready bus 510. The ready vector 514 may include a full ready vector or multiple sixteen-bit ready vector subsets (although the subsets may be of any bit size).
If the multiplexer 506 transmits vector subsets, after a series of get commands and multiplexer responses, the router 502 can receive all of the ready bits for a full ready vector. For example, if M equals 256, there are 256 ports 504(1)-504(256), and sixteen get commands would return all ready bits if each get command response sends sixteen bits of data on the ready bus 510 from the multiplexer 506 to the router 502. Typically, the multiplexer 506 sends consecutive vector subsets, e.g., a vector subset for bits one to thirty-two, then for bits thirty-three to sixty-four, etc., although vector subsets may be transmitted and/or received out of sequence.
Furthermore, the reading sequence on the ready bus 510 typically repeats. After the router 502 issues get commands for the full ready vector, the router 502 typically issues a get command starting over with bits for the first port or ports 504(1)-504(M), e.g., after issuing a get command for bits 251-256 of a 256 bit ready vector, the next get command would be for bits one to sixteen.
After receiving and assembling the ready vector 514, the router 502 can write the ready vector 514 to SRAM 516. The SRAM 516 may serve as the dual-port SRAM 406 of
The elements described with reference to
The routers 102 and 502 can each include a device capable of directing information to and/or from the physical ports 106 and 508, respectively. Examples of the routers 102 and 502 include devices capable of forwarding network traffic and/or making decisions on where to send network traffic on its way to its destination such as router devices, traffic shapers, combination router and traffic shapers, and other similar devices.
The ports 104(1)-104(N) and 504(1)-504(M) can each include any mechanism capable of accepting and buffering data for transmission to another mechanism or device. Examples of the ports 104(1)-104(N) and 504(1)-504(M) include sockets, logical channels, channel endpoints, and other similar mechanisms.
The networks 110 and 512 can each include any kind and any combination of networks such as an Internet, a local area network (LAN), a wide area network (WAN), a private network, a public network, or other similar network. The networks 110 and 512 may each include a LAN set up as an Ethernet. Examples of an Ethernet include a 10BaseT Ethernet, a Fast Ethernet, a Gigabit Ethernet, a ten Gigabit Ethernet, and other similar faster and slower Ethernets. A 10BaseT Ethernet generally refers to an Ethernet setup that transmits information at ten Megabits per second (Mbps). A Fast Ethernet generally refers to an Ethernet setup using a 100BaseT Ethernet, also called the Fast Ethernet standard (Institute of Electrical and Electronics Engineers (IEEE) standard 802.3u, adopted 1995), that transmits information at one hundred Mbps. A Gigabit Ethernet generally refers to an Ethernet setup that transmits information at 1000 Mbps using IEEE standard 802.3z (adopted 1998). A ten Gigabit Ethernet generally refers to an Ethernet setup that transmits information ten times as fast as a Gigabit Ethernet using IEEE standard 802.3ae (first draft adopted 2000).
The multiplexers 108 and 506 can each include any device capable of combining multiple transmissions into a single transmission and/or vice versa. The multiplexers 108 and 506 are shown as digital subscriber links access multiplexers (DSLAM), but other similar devices (with or without DSL capabilities) may be used.
The dual-port SRAM 406 and the SRAM 516 can each include any memory mechanism capable of storing data, usually at a relatively fast access rate, without needing to be refreshed.
Information transmitted between elements may be transmitted as blocks of data generally referred to as packets. The unit of packet data could include an entire network packet (e.g., an Ethernet packet) or a portion of such a packet. The packets may have a variable or a fixed size. Packets with a fixed size are called cells. Each sent packet may be part of a packet stream, where each of the packets, called a segment, included in the packet stream fits together to form a contiguous stream of data.
Data can be communicated between elements on communication links. The communication links can include any kind and any combination of communication links such as buses, physical ports, modem links, Ethernet links, cables, point-to-point links, infrared connections, fiber optic links, wireless links, cellular links, Bluetooth, satellite links, and other similar links. Additionally, each of the communication links may include one or more individual communication links. For bus communication links, the buses can have any width, e.g., sixteen bits, thirty-two bits, sixty-four bits, etc, and may run at any speed, e.g., thirty-three Mega Hertz (MHz), 100 MHz, etc. A bus may have a sideband feature in which the bus includes parallel channels that can each simultaneously carry data and/or address information.
Furthermore, the network configurations 100 and 500 are simplified for ease of explanation. The network configurations 100 and 500 may each include more or fewer additional elements such as networks, communication links, proxy servers, hubs, bridges, switches, routers, processors, storage locations, firewalls or other security mechanisms, Internet Service Providers (ISPs), and other elements.
The techniques described here are not limited to any particular hardware or software configuration; they may find applicability in any computing or processing environment. The techniques may be implemented in hardware, software, or a combination of the two. The techniques may be implemented in programs executing on programmable machines such as mobile or stationary computers, personal digital assistants, and similar devices that each include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code is applied to data entered using the input device to perform the functions described and to generate output information. The output information is applied to one or more output devices.
Each program may be implemented in a high level procedural or object oriented programming language to communicate with a machine system. However, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language.
Each such program may be stored on a storage medium or device, e.g., compact disc read only memory (CD-ROM), hard disk, magnetic diskette, or similar medium or device, that is readable by a general or special purpose programmable machine for configuring and operating the machine when the storage medium or device is read by the computer to perform the procedures described in this document. The system may also be considered to be implemented as a machine-readable storage medium, configured with a program, where the storage medium so configured causes a machine to operate in a specific and predefined manner.
Furthermore, elements of the processes presented may be executed in a different order than that shown to produce an acceptable result.
Other embodiments are within the scope of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
3373408 | Ling | Mar 1968 | A |
3478322 | Evans | Nov 1969 | A |
3623001 | Kleist et al. | Nov 1971 | A |
3736566 | Anderson et al. | May 1973 | A |
3792441 | Wymore et al. | Feb 1974 | A |
3889243 | Drimak | Jun 1975 | A |
3940745 | Sajeva | Feb 1976 | A |
4016548 | Law et al. | Apr 1977 | A |
4032899 | Jenny et al. | Jun 1977 | A |
4075691 | Davis et al. | Feb 1978 | A |
4130890 | Adam | Dec 1978 | A |
4400770 | Chan et al. | Aug 1983 | A |
4514807 | Nogi | Apr 1985 | A |
4523272 | Fukunaga et al. | Jun 1985 | A |
4658351 | Teng | Apr 1987 | A |
4709347 | Kirk | Nov 1987 | A |
4745544 | Renner et al. | May 1988 | A |
4788640 | Hansen | Nov 1988 | A |
4831358 | Ferrio et al. | May 1989 | A |
4858108 | Ogawa et al. | Aug 1989 | A |
4866664 | Burkhardt, Jr. et al. | Sep 1989 | A |
4890218 | Bram | Dec 1989 | A |
4890222 | Kirk | Dec 1989 | A |
4991112 | Callemyn | Feb 1991 | A |
5115507 | Callemyn | May 1992 | A |
5140685 | Sipple et al. | Aug 1992 | A |
5142683 | Burkhardt, Jr. et al. | Aug 1992 | A |
5155831 | Emma et al. | Oct 1992 | A |
5155854 | Flynn et al. | Oct 1992 | A |
5168555 | Byers et al. | Dec 1992 | A |
5173897 | Schrodi et al. | Dec 1992 | A |
5251205 | Callon et al. | Oct 1993 | A |
5255239 | Taborn et al. | Oct 1993 | A |
5263169 | Genusov et al. | Nov 1993 | A |
5313454 | Bustini et al. | May 1994 | A |
5347648 | Stamm et al. | Sep 1994 | A |
5367678 | Lee et al. | Nov 1994 | A |
5379295 | Yonehara | Jan 1995 | A |
5379432 | Orton et al. | Jan 1995 | A |
5390329 | Gaertner et al. | Feb 1995 | A |
5392391 | Caulk, Jr. et al. | Feb 1995 | A |
5392411 | Ozaki | Feb 1995 | A |
5392412 | McKenna | Feb 1995 | A |
5404464 | Bennett | Apr 1995 | A |
5404469 | Chung et al. | Apr 1995 | A |
5404482 | Stamm et al. | Apr 1995 | A |
5432918 | Stamm | Jul 1995 | A |
5448702 | Garcia, Jr. et al. | Sep 1995 | A |
5450351 | Heddes | Sep 1995 | A |
5452437 | Richey et al. | Sep 1995 | A |
5452452 | Gaetner et al. | Sep 1995 | A |
5459842 | Begun et al. | Oct 1995 | A |
5459843 | Davis et al. | Oct 1995 | A |
5463625 | Yasrebi | Oct 1995 | A |
5467452 | Blum et al. | Nov 1995 | A |
5475856 | Kogge | Dec 1995 | A |
5485455 | Dobbins et al. | Jan 1996 | A |
5515296 | Agarwal | May 1996 | A |
5517648 | Bertone et al. | May 1996 | A |
5539737 | Lo et al. | Jul 1996 | A |
5542070 | LeBlanc et al. | Jul 1996 | A |
5542088 | Jennings, Jr. et al. | Jul 1996 | A |
5544236 | Andruska et al. | Aug 1996 | A |
5550816 | Hardwick et al. | Aug 1996 | A |
5557766 | Takiguchi et al. | Sep 1996 | A |
5568476 | Sherer et al. | Oct 1996 | A |
5568617 | Kametani | Oct 1996 | A |
5574922 | James | Nov 1996 | A |
5581729 | Nistala et al. | Dec 1996 | A |
5592622 | Isfeld et al. | Jan 1997 | A |
5613071 | Rankin et al. | Mar 1997 | A |
5613136 | Casavant et al. | Mar 1997 | A |
5617327 | Duncan | Apr 1997 | A |
5623489 | Cotton et al. | Apr 1997 | A |
5627829 | Gleeson et al. | May 1997 | A |
5630074 | Beltran | May 1997 | A |
5630130 | Perotto et al. | May 1997 | A |
5633865 | Short | May 1997 | A |
5644623 | Gulledge | Jul 1997 | A |
5649110 | Ben-Nun et al. | Jul 1997 | A |
5649157 | Williams | Jul 1997 | A |
5651002 | Van Seters et al. | Jul 1997 | A |
5659687 | Kim et al. | Aug 1997 | A |
5680641 | Sidman | Oct 1997 | A |
5689566 | Nguyen | Nov 1997 | A |
5692126 | Templeton et al. | Nov 1997 | A |
5699537 | Sharangpani et al. | Dec 1997 | A |
5701434 | Nakagawa | Dec 1997 | A |
5717898 | Kagan et al. | Feb 1998 | A |
5721870 | Matsumoto | Feb 1998 | A |
5724574 | Stratigos et al. | Mar 1998 | A |
5740402 | Bratt et al. | Apr 1998 | A |
5742587 | Zornig et al. | Apr 1998 | A |
5742782 | Ito et al. | Apr 1998 | A |
5742822 | Motomura | Apr 1998 | A |
5745913 | Pattin et al. | Apr 1998 | A |
5751987 | Mahant-Shetti et al. | May 1998 | A |
5754764 | Davis et al. | May 1998 | A |
5761507 | Govett | Jun 1998 | A |
5761522 | Hisanaga et al. | Jun 1998 | A |
5764915 | Heimsoth et al. | Jun 1998 | A |
5768528 | Stumm | Jun 1998 | A |
5781551 | Born | Jul 1998 | A |
5781774 | Krick | Jul 1998 | A |
5784649 | Begur et al. | Jul 1998 | A |
5784712 | Byers et al. | Jul 1998 | A |
5796413 | Shipp et al. | Aug 1998 | A |
5797043 | Lewis et al. | Aug 1998 | A |
5805816 | Picazo, Jr. et al. | Sep 1998 | A |
5809235 | Sharma et al. | Sep 1998 | A |
5809237 | Watts et al. | Sep 1998 | A |
5809530 | Samra et al. | Sep 1998 | A |
5812868 | Moyer et al. | Sep 1998 | A |
5828746 | Ardon | Oct 1998 | A |
5828863 | Barrett et al. | Oct 1998 | A |
5828881 | Wang | Oct 1998 | A |
5828901 | O'Toole et al. | Oct 1998 | A |
5832215 | Kato et al. | Nov 1998 | A |
5835755 | Stellwagen, Jr. | Nov 1998 | A |
5838988 | Panwar et al. | Nov 1998 | A |
5850399 | Ganmukhi et al. | Dec 1998 | A |
5850530 | Chen et al. | Dec 1998 | A |
5854922 | Gravenstein et al. | Dec 1998 | A |
5857188 | Douglas | Jan 1999 | A |
5860138 | Engebretsen et al. | Jan 1999 | A |
5860158 | Pai et al. | Jan 1999 | A |
5886992 | Raatikainen et al. | Mar 1999 | A |
5887134 | Ebrahim | Mar 1999 | A |
5890208 | Kwon | Mar 1999 | A |
5892979 | Shiraki et al. | Apr 1999 | A |
5898686 | Virgile | Apr 1999 | A |
5898701 | Johnson | Apr 1999 | A |
5905876 | Pawlowski et al. | May 1999 | A |
5905889 | Wilhelm, Jr. | May 1999 | A |
5909686 | Muller et al. | Jun 1999 | A |
5915123 | Mirsky et al. | Jun 1999 | A |
5918235 | Kirshenbaum et al. | Jun 1999 | A |
5933627 | Parady | Aug 1999 | A |
5937187 | Kosche et al. | Aug 1999 | A |
5938736 | Muller et al. | Aug 1999 | A |
5940612 | Brady et al. | Aug 1999 | A |
5940866 | Chisholm et al. | Aug 1999 | A |
5946487 | Dangelo | Aug 1999 | A |
5948081 | Foster | Sep 1999 | A |
5953336 | Moore et al. | Sep 1999 | A |
5958031 | Kim | Sep 1999 | A |
5961628 | Nguyen et al. | Oct 1999 | A |
5968169 | Pickett | Oct 1999 | A |
5970013 | Fischer et al. | Oct 1999 | A |
5974518 | Nogradi | Oct 1999 | A |
5978838 | Mohamed et al. | Nov 1999 | A |
5983274 | Hyder et al. | Nov 1999 | A |
5995513 | Harrand et al. | Nov 1999 | A |
6012151 | Mano | Jan 2000 | A |
6014729 | Lannan et al. | Jan 2000 | A |
6023742 | Ebeling et al. | Feb 2000 | A |
6032190 | Bremer et al. | Feb 2000 | A |
6032218 | Lewin et al. | Feb 2000 | A |
6047002 | Hartmann et al. | Apr 2000 | A |
6049867 | Eickemeyer et al. | Apr 2000 | A |
6058168 | Braband | May 2000 | A |
6061710 | Eickemeyer et al. | May 2000 | A |
6067300 | Baumert et al. | May 2000 | A |
6067585 | Hoang | May 2000 | A |
6070231 | Ottinger | May 2000 | A |
6072781 | Feeney et al. | Jun 2000 | A |
6073215 | Snyder | Jun 2000 | A |
6079008 | Clery, III | Jun 2000 | A |
6085215 | Ramakrishnan et al. | Jul 2000 | A |
6085248 | Sambamurthy et al. | Jul 2000 | A |
6085294 | Van Doren et al. | Jul 2000 | A |
6092127 | Tausheck | Jul 2000 | A |
6092158 | Harriman et al. | Jul 2000 | A |
6104700 | Haddock et al. | Aug 2000 | A |
6111886 | Stewart | Aug 2000 | A |
6112016 | MacWilliams et al. | Aug 2000 | A |
6122251 | Shinohara | Sep 2000 | A |
6128669 | Moriarty et al. | Oct 2000 | A |
6134665 | Klein et al. | Oct 2000 | A |
6141677 | Hanif et al. | Oct 2000 | A |
6141689 | Yasrebi | Oct 2000 | A |
6141765 | Sherman | Oct 2000 | A |
6144669 | Williams et al. | Nov 2000 | A |
6145054 | Mehrotra et al. | Nov 2000 | A |
6157955 | Narad et al. | Dec 2000 | A |
6160562 | Chin et al. | Dec 2000 | A |
6170051 | Dowling | Jan 2001 | B1 |
6175927 | Cromer et al. | Jan 2001 | B1 |
6182177 | Harriman | Jan 2001 | B1 |
6195676 | Spix et al. | Feb 2001 | B1 |
6199133 | Schnell | Mar 2001 | B1 |
6201807 | Prasanna | Mar 2001 | B1 |
6212542 | Kahle et al. | Apr 2001 | B1 |
6212544 | Borkenhagen et al. | Apr 2001 | B1 |
6212604 | Tremblay | Apr 2001 | B1 |
6212611 | Nizar et al. | Apr 2001 | B1 |
6216220 | Hwang | Apr 2001 | B1 |
6223207 | Lucovsky et al. | Apr 2001 | B1 |
6223238 | Meyer et al. | Apr 2001 | B1 |
6223243 | Ueda et al. | Apr 2001 | B1 |
6223274 | Catthoor et al. | Apr 2001 | B1 |
6223279 | Nishimura et al. | Apr 2001 | B1 |
6247025 | Bacon | Jun 2001 | B1 |
6256713 | Audityan et al. | Jul 2001 | B1 |
6269391 | Gillespie | Jul 2001 | B1 |
6272109 | Pei et al. | Aug 2001 | B1 |
6272520 | Sharangpani et al. | Aug 2001 | B1 |
6272616 | Fernando et al. | Aug 2001 | B1 |
6275505 | O'Loughlin et al. | Aug 2001 | B1 |
6279113 | Vaidya | Aug 2001 | B1 |
6282169 | Kiremidjian | Aug 2001 | B1 |
6286083 | Chin et al. | Sep 2001 | B1 |
6289011 | Seo et al. | Sep 2001 | B1 |
6295600 | Parady | Sep 2001 | B1 |
6298370 | Tang et al. | Oct 2001 | B1 |
6307789 | Wolrich et al. | Oct 2001 | B1 |
6311261 | Chamdani et al. | Oct 2001 | B1 |
6320861 | Adam et al. | Nov 2001 | B1 |
6324624 | Wolrich et al. | Nov 2001 | B1 |
6335932 | Kadambi et al. | Jan 2002 | B2 |
6338078 | Chang et al. | Jan 2002 | B1 |
6345334 | Nakagawa et al. | Feb 2002 | B1 |
6347344 | Baker et al. | Feb 2002 | B1 |
6349331 | Andra et al. | Feb 2002 | B1 |
6356962 | Kasper et al. | Mar 2002 | B1 |
6359911 | Movshovich et al. | Mar 2002 | B1 |
6360262 | Guenthner et al. | Mar 2002 | B1 |
6360277 | Ruckley et al. | Mar 2002 | B1 |
6366998 | Mohamed | Apr 2002 | B1 |
6373848 | Allison et al. | Apr 2002 | B1 |
6377998 | Noll et al. | Apr 2002 | B2 |
6389031 | Chao et al. | May 2002 | B1 |
6389449 | Nemirovsky et al. | May 2002 | B1 |
6393026 | Irwin | May 2002 | B1 |
6393483 | Latif et al. | May 2002 | B1 |
6404737 | Novik et al. | Jun 2002 | B1 |
6415338 | Habot | Jul 2002 | B1 |
6418488 | Chilton et al. | Jul 2002 | B1 |
6424657 | Voit et al. | Jul 2002 | B1 |
6424659 | Viswanadham et al. | Jul 2002 | B2 |
6426940 | Seo et al. | Jul 2002 | B1 |
6426943 | Spinney et al. | Jul 2002 | B1 |
6427196 | Adiletta et al. | Jul 2002 | B1 |
6430626 | Witkowski et al. | Aug 2002 | B1 |
6434145 | Opsasnick et al. | Aug 2002 | B1 |
6438132 | Vincent et al. | Aug 2002 | B1 |
6438134 | Chow et al. | Aug 2002 | B1 |
6448812 | Bacigalupo | Sep 2002 | B1 |
6453404 | Bereznyi et al. | Sep 2002 | B1 |
6457015 | Eastham | Sep 2002 | B1 |
6463035 | Moore | Oct 2002 | B1 |
6463072 | Wolrich et al. | Oct 2002 | B1 |
6463480 | Kikuchi et al. | Oct 2002 | B2 |
6463527 | Vishkin | Oct 2002 | B1 |
6466898 | Chan | Oct 2002 | B1 |
6477562 | Nemirovsky et al. | Nov 2002 | B2 |
6484224 | Robins et al. | Nov 2002 | B1 |
6501731 | Chong et al. | Dec 2002 | B1 |
6507862 | Joy et al. | Jan 2003 | B1 |
6522188 | Poole | Feb 2003 | B1 |
6526451 | Kasper | Feb 2003 | B2 |
6526452 | Petersen et al. | Feb 2003 | B1 |
6529983 | Marshall et al. | Mar 2003 | B1 |
6532509 | Wolrich et al. | Mar 2003 | B1 |
6535878 | Guedalia et al. | Mar 2003 | B1 |
6552826 | Adler et al. | Apr 2003 | B2 |
6553406 | Berger et al. | Apr 2003 | B1 |
6560667 | Wolrich et al. | May 2003 | B1 |
6570850 | Gutierrez et al. | May 2003 | B1 |
6577542 | Wolrich et al. | Jun 2003 | B2 |
6584522 | Wolrich et al. | Jun 2003 | B1 |
6587906 | Wolrich et al. | Jul 2003 | B2 |
6604125 | Belkin | Aug 2003 | B1 |
6606704 | Adiletta et al. | Aug 2003 | B1 |
6625654 | Wolrich et al. | Sep 2003 | B1 |
6628668 | Hutzli et al. | Sep 2003 | B1 |
6629147 | Grow | Sep 2003 | B1 |
6629236 | Aipperspach et al. | Sep 2003 | B1 |
6631422 | Althaus et al. | Oct 2003 | B1 |
6631430 | Wolrich et al. | Oct 2003 | B1 |
6631462 | Wolrich et al. | Oct 2003 | B1 |
6657963 | Paquette et al. | Dec 2003 | B1 |
6658551 | Berenbaum et al. | Dec 2003 | B1 |
6661774 | Lauffenburger et al. | Dec 2003 | B1 |
6661794 | Wolrich et al. | Dec 2003 | B1 |
6665699 | Hunter et al. | Dec 2003 | B1 |
6665755 | Modelski et al. | Dec 2003 | B2 |
6667920 | Wolrich et al. | Dec 2003 | B2 |
6668317 | Bernstein et al. | Dec 2003 | B1 |
6671827 | Guilford et al. | Dec 2003 | B2 |
6675190 | Schabernack et al. | Jan 2004 | B1 |
6675192 | Emer et al. | Jan 2004 | B2 |
6678746 | Russell et al. | Jan 2004 | B1 |
6680933 | Cheesman et al. | Jan 2004 | B1 |
6681300 | Wolrich et al. | Jan 2004 | B2 |
6684326 | Cromer et al. | Jan 2004 | B1 |
6694380 | Wolrich et al. | Feb 2004 | B1 |
6697379 | Jacquet et al. | Feb 2004 | B1 |
6721325 | Duckering et al. | Apr 2004 | B1 |
6724767 | Chong et al. | Apr 2004 | B1 |
6728845 | Adiletta et al. | Apr 2004 | B2 |
6732187 | Lougheed et al. | May 2004 | B1 |
6754211 | Brown | Jun 2004 | B1 |
6754222 | Joung et al. | Jun 2004 | B1 |
6768717 | Reynolds et al. | Jul 2004 | B1 |
6775284 | Calvignac et al. | Aug 2004 | B1 |
6792488 | Wolrich et al. | Sep 2004 | B2 |
6798744 | Loewen et al. | Sep 2004 | B1 |
6826615 | Barrall et al. | Nov 2004 | B2 |
6834053 | Stacey et al. | Dec 2004 | B1 |
6850521 | Kadambi et al. | Feb 2005 | B1 |
6856622 | Calamvokis et al. | Feb 2005 | B1 |
6873618 | Weaver | Mar 2005 | B1 |
6876561 | Wolrich et al. | Apr 2005 | B2 |
6895457 | Wolrich et al. | May 2005 | B2 |
6925637 | Thomas et al. | Aug 2005 | B2 |
6931641 | Davis et al. | Aug 2005 | B1 |
6934780 | Modelski et al. | Aug 2005 | B2 |
6934951 | Wilkinson et al. | Aug 2005 | B2 |
6938147 | Joy et al. | Aug 2005 | B1 |
6944850 | Hooper et al. | Sep 2005 | B2 |
6947425 | Hooper et al. | Sep 2005 | B1 |
6952824 | Hooper et al. | Oct 2005 | B1 |
6959002 | Wynne et al. | Oct 2005 | B2 |
6967963 | Houh et al. | Nov 2005 | B1 |
6976095 | Wolrich et al. | Dec 2005 | B1 |
6981077 | Modelski et al. | Dec 2005 | B2 |
6983350 | Wheeler et al. | Jan 2006 | B1 |
7006495 | Hooper | Feb 2006 | B2 |
7065569 | Teraslinna | Jun 2006 | B2 |
7069548 | Kushlis | Jun 2006 | B2 |
7096277 | Hooper | Aug 2006 | B2 |
7100102 | Hooper et al. | Aug 2006 | B2 |
7111296 | Wolrich et al. | Sep 2006 | B2 |
7124196 | Hooper | Oct 2006 | B2 |
7126952 | Hooper et al. | Oct 2006 | B2 |
7149786 | Bohringer et al. | Dec 2006 | B1 |
7181742 | Hooper | Feb 2007 | B2 |
7191321 | Bernstein et al. | Mar 2007 | B2 |
7206858 | Hooper et al. | Apr 2007 | B2 |
7248584 | Hooper | Jul 2007 | B2 |
7305500 | Adiletta et al. | Dec 2007 | B2 |
7328289 | Wolrich et al. | Feb 2008 | B2 |
7352769 | Hooper et al. | Apr 2008 | B2 |
20010023487 | Kawamoto | Sep 2001 | A1 |
20020027448 | Bacigalupo | Mar 2002 | A1 |
20020041520 | Wolrich et al. | Apr 2002 | A1 |
20020075878 | Lee et al. | Jun 2002 | A1 |
20020118692 | Oberman et al. | Aug 2002 | A1 |
20020150047 | Knight et al. | Oct 2002 | A1 |
20020181194 | Ho et al. | Dec 2002 | A1 |
20030043803 | Hooper | Mar 2003 | A1 |
20030067934 | Hooper et al. | Apr 2003 | A1 |
20030086434 | Kloth | May 2003 | A1 |
20030105901 | Wolrich et al. | Jun 2003 | A1 |
20030105917 | Ostler et al. | Jun 2003 | A1 |
20030110166 | Wolrich et al. | Jun 2003 | A1 |
20030115347 | Wolrich et al. | Jun 2003 | A1 |
20030115426 | Rosenbluth et al. | Jun 2003 | A1 |
20030131198 | Wolrich et al. | Jul 2003 | A1 |
20030140196 | Wolrich et al. | Jul 2003 | A1 |
20030145159 | Adiletta et al. | Jul 2003 | A1 |
20030147409 | Wolrich et al. | Aug 2003 | A1 |
20030161303 | Mehrvar et al. | Aug 2003 | A1 |
20030161337 | Weinman | Aug 2003 | A1 |
20030196012 | Wolrich et al. | Oct 2003 | A1 |
20030210574 | Wolrich et al. | Nov 2003 | A1 |
20030231635 | Kalkunte et al. | Dec 2003 | A1 |
20040039895 | Wolrich et al. | Feb 2004 | A1 |
20040052269 | Hooper et al. | Mar 2004 | A1 |
20040054880 | Bernstein et al. | Mar 2004 | A1 |
20040059828 | Hooper et al. | Mar 2004 | A1 |
20040071152 | Wolrich et al. | Apr 2004 | A1 |
20040073728 | Wolrich et al. | Apr 2004 | A1 |
20040073778 | Adiletta et al. | Apr 2004 | A1 |
20040098496 | Wolrich et al. | May 2004 | A1 |
20040109369 | Wolrich et al. | Jun 2004 | A1 |
20040148382 | Narad et al. | Jul 2004 | A1 |
20040162933 | Adiletta et al. | Aug 2004 | A1 |
20040252686 | Hooper et al. | Dec 2004 | A1 |
20050033884 | Wolrich et al. | Feb 2005 | A1 |
20050149665 | Wolrich et al. | Jul 2005 | A1 |
20060007871 | Welin | Jan 2006 | A1 |
20060069882 | Wheeler et al. | Mar 2006 | A1 |
20060156303 | Hooper et al. | Jul 2006 | A1 |
Number | Date | Country |
---|---|---|
0 379 709 | Aug 1990 | EP |
0 464 715 | Jan 1992 | EP |
0 633 678 | Jan 1995 | EP |
0 745 933 | Dec 1996 | EP |
0 773 648 | May 1997 | EP |
0 809 180 | Nov 1997 | EP |
0 959 602 | Nov 1999 | EP |
59-111533 | Jun 1984 | JP |
WO 9415287 | Jul 1994 | WO |
WO 9738372 | Oct 1997 | WO |
WO 9820647 | May 1998 | WO |
WO 0038376 | Jun 2000 | WO |
WO 0056024 | Sep 2000 | WO |
WO 0116718 | Mar 2001 | WO |
WO 0116769 | Mar 2001 | WO |
WO 0116770 | Mar 2001 | WO |
WO 0116782 | Mar 2001 | WO |
WO 0117179 | Mar 2001 | WO |
WO 0131856 | May 2001 | WO |
WO 0148596 | Jul 2001 | WO |
WO 0148606 | Jul 2001 | WO |
WO 0148619 | Jul 2001 | WO |
WO 0150247 | Jul 2001 | WO |
WO 0150679 | Jul 2001 | WO |
WO 03030461 | Apr 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20040085901 A1 | May 2004 | US |