Using error checking bits to communicated an address or other bits

Information

  • Patent Grant
  • 7281187
  • Patent Number
    7,281,187
  • Date Filed
    Thursday, November 20, 2003
    21 years ago
  • Date Issued
    Tuesday, October 9, 2007
    17 years ago
Abstract
A method of operating in a network in which a plurality of stations communicate over a shared medium. The method comprises transmitting a group of bits from a transmitting station to a receiving station, wherein the group of bits comprises information bits and error checking bits, and communicating additional bits from the transmitting station to the receiving station without transmitting the additional bits. Communicating the additional bits comprises, at the transmitting station, deriving the error checking bits from the additional bits using an error checking process; and at the receiving station, using the same or a related error checking process to process candidate bits known to the receiving station, and comparing the output of the error checking process to the error checking bits received from the transmitting station to determine if the candidate bits correspond to the additional bits.
Description
TECHNICAL FIELD

This invention relates to network communications.


BACKGROUND

Networks where multiple stations share a common medium require stations to coordinate access to the medium. A variety of protocols like Carrier Sense Multiple Access (CSMA), Token passing and Polling are used to achieve coordinate medium access. Stations in multiple access networks exchange data using structured protocol entities called packets. These packets carry addressing information required to identify the source and destination of the transmission. Typically, each station in the network is identified by a unique address. These addresses are sent in packets to uniquely identify the source and destination.


Certain network situations may require stations to broadcast these addresses. This can be costly in some networks where broadcasting is inefficient and the addresses are large.


SUMMARY

In one aspect, the invention features a method of operating in a network in which a plurality of stations communicate over a shared medium. The method comprises transmitting a group of bits from a transmitting station to a receiving station, wherein the group of bits comprises information bits and error checking bits, and communicating additional bits from the transmitting station to the receiving station without transmitting the additional bits. Communicating the additional bits comprises, at the transmitting station, deriving the error checking bits from the additional bits using an error checking process; and at the receiving station, using the same or a related error checking process to process candidate bits known to the receiving station, and comparing the output of the error checking process to the error checking bits received from the transmitting station to determine if the candidate bits correspond to the additional bits.


Embodiments may include one or more of the following. The communicating of the additional bits may further comprise, at the transmitting station, deriving the error checking bits from the additional bits and the information bits using the error checking process, and at the receiving station, using the same or a related error checking process to process the candidate bits and the information bits received from the transmitting station, comparing the output of the error checking process result to the error checking bits received from the first station to determine if the candidate bits correspond to the additional bits. The additional bits may comprise an address identifying one or both of the transmitting and receiving stations. The group of bits may constitute a packet, the information bits may comprise a source address and data, and the additional bits may comprise a destination address identifying the receiving station. The group of bits may constitute a packet, the information bits may comprise a source address and data, and the additional bits may comprise at least a portion of a destination address at least partially identifying the receiving station. The group of bits may constitute a Request To Send (RTS), the information bits may comprise a source address and data, with the source address identifying the transmitting station, and the additional bits may comprise a destination address identifying the receiving station. The group of bits may constitute a RTS, the information bits may comprise a source address and data, with the source address identifying the transmitting station, and the additional bits may comprise at least a portion of a destination address at least partially identifying the receiving station. The group of bits may constitute a Clear To Send (CTS) transmitted in response to an RTS, and the additional bits may comprise one or both of the following: (1) a destination address identifying the receiving station and (2) a source address identifying the transmitting station. The group of bits may constitute an acknowledgement and the additional bits may comprise one or both of the following: (1) a source address identifying the transmitting station and (2) a destination address identifying the receiving station. The group of bits may constitute an acknowledgement and the additional bits may comprise one or both of the following: (1) at least a portion of a source address at least partially identifying the transmitting station and (2) at least a portion of a destination address at least partially identifying the receiving station. The group of bits may constitute an acknowledgement transmitted in response to a receipt of a packet, and the additional bits may comprise a set of bits from the packet that is sufficiently unique as to associate the acknowledgement with the packet. The information bits may comprise bits indicating which portions of a previously transmitted packet need to be retransmitted. The error checking process may comprise a cyclic redundancy check, and the error checking bits may comprise frame check sequence (FCS) bits associated with the cyclic redundancy check.


and the error checking bits may comprise frame check sequence (FCS) bits associated with the cyclic redundancy check.


In another aspect, the invention features a method of operating in a network in which a plurality of stations communicate over a shared medium that includes transmitting a group of bits from a transmitting station to a receiving station, wherein the group of bits comprises information bits and a substantially unique number. The method also includes acknowledging receipt of the group of bits at the receiving station by transmitting an acknowledgement containing the substantially unique number or number or containing data from which the substantially unique number can be derived.


Embodiments may include one or more of the following. The group of bits may include a destination address identifying the receiving station, and the acknowledgement may include the same destination address. The transmitting station may receive the acknowledgement and may determine whether it contains the same destination address and the same substantially unique number as included in the transmitted group of bits. The group of bits may constitute an RTS and the acknowledgement may constitute a CTS. The substantially unique number may comprise a pseudorandom number.


These and other embodiments may have one or more of the following advantages. Packets may be transmitted and received by the intended destinations without requiring the transfer of complete source and destination addresses. This can be used to improve packet efficiency. For example, standard error checking techniques can be used to encode source and destination address information in packets without explicitly transmitting the source and destination address information. Various types of error checking techniques may be used, including cyclic redundancy code checking as well as checksum. For Request to Send (RTS) and Clear to Send (CTS), the communication overhead is reduced by not requiring transferring both source and destination addresses in the RTS message.


The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.





DESCRIPTION OF DRAWINGS


FIG. 1 is a schematic of a network configuration.



FIGS. 2–5 are data structure diagrams of transmitted and received data.





DETAILED DESCRIPTION

There are a great many possible implementations of the invention, too many to describe herein. Some possible implementations that are presently preferred are described below and in the Appendix. It cannot be emphasized too strongly, however, that these are descriptions of implementations of the invention, and not descriptions of the invention, which is not limited to the detailed implementations described in this section but is described in broader terms in the claims.


As shown in FIG. 1, network configuration 2 includes communications medium 3 and network 4 in which electronic devices 6, 8, and 10 (e.g., audiovisual equipment) communicate over medium 3. Electronic devices 6, 8, and 10 include media access controllers (MAC) 12, 14, and 16 that manage communication access to the network 4 for electronic devices 6, 8, and 10, respectively. MACs 12, 14, and 16 implement the data link layer and connect to the physical layer of the Open Systems Interconnection (OSI) network architecture standard. In a general sense, MACs 12, 14, and 16 represent stations on network 4 that send messages to one another over medium 3. Communications medium 3 is a physical communication link between electronic devices 6, 8, and 10, and may include optical fiber, coaxial cable, unshielded twisted pair, in addition to other media such as power lines. Electronic devices 6, 8, and 10 communicate with one another based on requirements of software applications running on electronic devices 6, 8, and 10. This communication creates traffic of messages on network 4.


In some examples, medium 3 has a limited bandwidth due to limited physical capacity or electronic noise. Messages (e.g., groups of bits such as packets or ACKs) sent between MACs include at least some information bits (e.g., packet body, payload, frame control information, addresses). Some messages between MACs 12, 14, and 16 also convey additional bits of information (e.g., a destination address) without sending the additional bits. The additional bits are conveyed by deriving error checking bits (e.g., CRC or checksum) from the additional bits at the transmitting station, transmitting the error checking bits with the information bits, and then using an error checking process at a receiving station to derive error checking bits from candidate bits (e.g. the receiving station's address). If the error checking bits derived at the receiving station compare favorably (e.g., match) to the received error checking bits, then the receiving station can safely conclude that the candidate bits are the same as the additional bits used by the transmitter (e.g., that the destination address is the receiver's address).


Communication error checking can be done in various ways. E.g., a transmitting station may use an error checking process to encode a block of data to be transmitted into a substantially unique code (which could be termed error checking bits) that is substantially unique to the communication and send the unique code along with the block of data to a receiving station. The receiving station then processes the received block of data and unique code using the same or related error checking process to determine whether the received block of data has been received without error. Common error checking processes include cyclic redundancy code (CRC) checking and checksum.


Cyclic redundancy code (CRC) checking is a method of checking for errors in data that have been transmitted on a communications link. For example, a transmitting station (e.g., MAC 12) in network configuration 2 typically applies a 8-, 16- or 32-bit polynomial to a block of data that is to be transmitted to a receiving station (e.g., MAC 14) and appends the resulting cyclic redundancy code to the block. The receiving station (e.g., MAC 14) applies the same polynomial to the data and each receiving station compares its result with the result appended by the transmitting station. If the result matches with the appended CRC, the receiving station can assume that the block of data has been received successfully.


Another typical error detection method for communication is the checksum method. A sum of data in a transmitted block (the checksum) is transmitted with the block of data so that the receiving station can compare a sum of the received block data with the received sum. If the sums match, then the receiving station can assume that the transmission of the block of data was correctly received.


MACs 12, 14, and 16 convey a block of data (information bits, e.g., a packet body or payload) as well as extra information (additional bits, e.g., a destination address) without using substantially more bandwidth than would have been necessary for conveying the block of data. This is accomplished by deriving error checking bits from the extra information and the block of data but actually transmitting only the block of data and the error checking bits (alternatively, some portion, but not all, of the extra information might be transmitted). Although the extra information is not transmitted, each station (e.g., MACs 14 and 16) receiving the message can perform an error checking process using candidate bits (e.g., the receiving station's address) to test whether the candidate bits correspond to the extra information (e.g., whether the receiving station's address matches the destination address). The receiving station may accomplish this by appending the candidate bits (e.g., its address) to the received block of data message, and then applying the error checking process (the same one as used in the transmitter, or a related on that should produce a result from which it can be determined whether the candidate bits compare favorably to the additional bits). Various types of extra information (additional bits) can be conveyed in this manner, e.g., destination or source addresses, identification of a packet, or other information from a finite universe of information known to the receiving station.


As shown in FIG. 2, MAC 12 has a task of sending a message frame 102 with a block of data 104 to MAC 14 via medium 3 without directly specifying a destination address 108 for MAC 14. Both MAC 14 and MAC 16 will receive the message and MAC 14 should behave as if the message 102 is intended for MAC 14 while MAC 16 should function as if the message frame 102 is not intended for MAC 16. In the message frame 102, MAC 12 sends block of data 104 and error checking code 106. MAC 12 generates the error checking code 106 as if the block of data 104 were sent with the address 108 for MAC 14. Upon receipt of the message frame 102, MAC 14 determines that the message frame 102 is intended for MAC 14, and MAC 16 determines that the message is not intended for MAC 16. MAC 14 and MAC 16 make this determination by inserting each receiving station's address 112 into an augmented message 110 (containing the received block of data and the receiving station's address) and using error checking code 106 against the augmented message 110 to check for errors. If there are no errors using this augmented message 110, then the inserted address 112 is assumed to be the destination address 108. In this example, MAC 14 has no errors and MAC 16 has errors.


Another example of matching some information in the message with an address of the receiving MAC occurs when MACs 12, 14, and 16 send Request to Send/Clear to Send (RTS/CTS) message pairs between each other. RTS/CTS is used when a MAC (e.g., 12) needs to know that another MAC (e.g., 14) is listening before sending data. As shown in FIG. 3, MAC 12 sends a RTS message frame 202 to medium 3 to check if MAC 14 is listening before MAC 12 sends data to MAC 14. In this example, the RTS message frame 202 includes a data portion 204 and an error code 206 for error checking at the receiving station (e.g., MAC 14). In one example, the error code 206 is a CRC resulting from applying a 8-, 16- or 32-bit polynomial to the data portion 204. The data portion 204 includes a source address 210 of MAC 12, but not a destination address 208. MACs 14 and 16 receive the RTS message on medium 3. Both MAC 14 and 16 read the data portion 204 and the error code 206 of the message 202. In the example where error code 206 is a CRC, both MAC 14 and 16 apply the 8-, 16- or 32-bit polynomial to an augmented message 212 representing the combination of the received data portion 204 and address 214 of either MAC 14 or 16. Both MAC 14 and 16 check for errors using the augmented message 212. MAC 14 finds no error in the augmented message 212 so MAC 14 detects that the RTS message is intended for MAC 14. By making this successful match, MAC 14 not only knows that the RTS message 202 is intended for MAC 14 but also that the message was received without transmission errors. MAC 14 responds to the RTS by sending a CTS message to medium 3 with MAC 12 as its intended recipient without including address 210 of MAC 12 in the message body. The CTS message has an error code that is derived from the data portion of the CTS message in addition to the destination address 210 of MAC 12. Alternatively, the CTS message can use one or both of the source address (address of station generating the CTS) and destination address (address of station that is the intended recipient of the CTS) in the CRC computation. MACs 12 and 16 receive the CTS message on medium 3 and MAC 12 detects that the CTS message is intended for MAC 12 by augmenting the message with its address 210 and calculating that the augmented message is error free as described previously.


Other applications of this messaging technique include packet acknowledgement so that a transmitting station knows when its packets have been received or not. As shown in FIG. 4, MAC 12 sends a message frame 302 containing an acknowledgement of a receipt of a packet. MAC 14 originally sent the packet to MAC 12 so the packet acknowledgement conveys a source address identification 310 for MAC 12. Upon receipt of this acknowledgement, MAC 14 can match the acknowledgement to a packet sent by MAC 14 to MAC 12. The acknowledgement message 302 is intended for MAC 14 but both MAC 14 and 16 receive the message 302 on medium 3. MAC 12 generates the message 302 by generating error code 306 as if the source address 310 (address of MAC 12) and the destination address 308 (address of MAC 14) were part of a block of data for the message 302 without transmitting the source address 310 and the destination address 308. Alternatively, the acknowledgement can also use only the destination address or only the source address in the CRC computation. The intended receiver knows the address of the station that is supposed to send the response, and thus the acknowledgment mechanism can use one or both of the destination address and source address. Upon receipt of the message, both MAC 14 and MAC 16 insert their addresses into an augmented message 312 as potential destination address 316. Both MAC 14 and MAC 16 also insert addresses into an augmented message 312 of stations where MAC 14 and 16 previously sent unacknowledged packets as potential source addresses 314. MAC 14 and 16 then check their augmented messages 312 against the received error code 306 in the message to see if there is a match. In this case, MAC 14 has a match for the destination address 316 and a source address 314 for the packet previously sent to MAC 12.



FIG. 5 shows one possible implementation of a communication method in which a substantially unique number (e.g., a pseudorandom number) is transmitted along with block of data, and a receiving station acknowledges receipt of the block of data by transmitting an acknowledgement containing the substantially unique number or containing data from which the substantially unique number can be derived. As described previously, MAC 12 wishes to determine if data can be sent to MAC 14. As shown in FIG. 5, MAC 12 sends a RTS message 402 to MAC 14 with a substantially unique number 406, such as a pseudorandomly generated number, along with an address 408 of MAC 14 and other data 404. In response, MAC 14 sends back a CTS message 420 to MAC 12 with the same substantially unique number 406 and the address 408 of MAC 14 along with other data. Upon receipt of the CTS message 420, MAC 12 knows that it has received a CTS message corresponding to its RTS message 402 by a correct match of its original substantially unique number 406 and the received substantially unique number as well as the address 408 of MAC 12. Subsequently, MAC 12 can send data to MAC 14. In an alternative implementation a different number is returned, one that is derived by transforming number 406, but MAC 12 is aware of the transformation, and is able to ascertain that the returned number was derived from the number 406.


The normal cyclic redundancy code algorithm is typically as follows. First, a CRC is determined to be some number n bits long. To generate the CRC for a block of data, a transmitting station (e.g., MAC 12) left shifts the frame representing the block of data by n bits and then divides it by a predefined polynomial P. P is n+1 bits long. The remainder of the division is the FCS. MAC 12 appends the FCS to the frame representing the block of data. The result is the final frame forming the message body to transmit. On the receiving side, a receiving station (e.g., MAC 14) receives the frame. MAC 14 then divides the frame by the predefined polynomial P. If the remainder of the division is zero then the transmission is error free. If the transmission is not zero then there is an error in the transmission.


Several different length CRCs are used in network configuration 2 by MACs 12, 14, and 16 to match destination addresses and check for errors using correct demodulation or decryption of data. Different lengths of these CRCs include CRC-8, CRC-16, and CRC-24.


The CRC-8 is calculated using the following standard generator polynomial of degree 8: G(x)=x8+x2+x+1. The CRC-8 is the one's complement of the (modulo-2) sum of the following:

    • The remainder of xk×(x7+ . . . +x2+x+1) divided (modulo-2) by G(x), where k is the number of bits in the calculation fields, and
    • The remainder after multiplication of the contents (treated as a polynomial) of the calculation fields by x8 and then division by G(x).


      The CRC-8 field is transmitted commencing with the coefficient of the highest-order term.


As a typical implementation, at the transmitter, the initial remainder of the division is preset to all ones and is then modified by division of the calculation fields by the generator polynomial G(x). The one's complement of this remainder is transmitted, with the high-order bits first, as the CRC-8 field.


At the receiver, the initial remainder is preset to all ones and the serial incoming bits of the calculation fields and CRC-8, when divided by G(x) in the absence of transmission errors, results in a unique nonzero remainder value. The unique remainder value is the polynomial: x7+x6+x5+x4+X+1.


The CRC-16 is computed using the following standard generator polynomial of degree 16: G(x)=x16+x12+x5+1. The CRC-16 is the one's complement of the (modulo-2) sum of the following:

    • The remainder of xk×(x15+x14+ . . . +x2+x+1) divided (modulo-2) by G(x), where k is the number of bits in the calculation fields, and
    • The remainder after multiplication of the contents (treated as a polynomial) of the calculation fields by x16 and then division by G(x).


The CRC-16 field is transmitted commencing with the coefficient of the highest-order term.


As a typical implementation, at the transmitter, the initial remainder of the division is preset to all ones and is then modified by division of the calculation fields by the generator polynomial G(x). The one's complement of this remainder is transmitted, with the high-order bits first, as the CRC-16 field.


At the receiver, the initial remainder is preset to all ones and the serial incoming bits of the calculation fields and CRC-16, when divided by G(x) in the absence of transmission errors, results in a unique nonzero remainder value. The unique remainder value is the polynomial: x12+x11+x10+x8+x3+x2+x+1


The CRC-32 is computed using the following standard generator polynomial of degree 32: G(x)=x32+x26+x23+x22+x16+x12+x11+x10+x8+x7+x5+x4+x2+x+1. The CRC-32 is the one's complement of the (modulo-2) sum of the following:

    • The remainder of xk×(x31+x30+ . . . +x2+x+1) divided (modulo-2) by G(x), where k is the number of bits in the calculation fields, and
    • The remainder after multiplication of the contents (treated as a polynomial) of the calculation fields by X32 and then division by G(x).


The CRC-32 field is transmitted commencing with the coefficient of the highest-order term. As a typical implementation, at the transmitter, the initial remainder of the division is preset to all ones and is then modified by division of the calculation fields by the generator polynomial G(x). The one's complement of this remainder is transmitted, with the high-order bits first, as the CRC-16 field.


At the receiver, the initial remainder is preset to all ones and the serial incoming bits of the calculation fields and CRC-16, when divided by G(x) in the absence of transmission errors, results in a unique nonzero remainder value. The unique remainder value is the polynomial: x12+x11+x10+x8+x3+x2+x+1.


Many other implementations of the invention other than those described above are within the invention, which is defined by the following claims.

Claims
  • 1. A method of operating in a network in which a plurality of stations communicate over a shared medium, comprising transmitting a group of bits from a transmitting station to a receiving station, wherein the group of bits comprises information bits and error checking bits;communicating additional bits from the transmitting station to the receiving station without transmitting the additional bits, the communicating of the additional bits comprises at the transmitting station, deriving the error checking bits from the additional bits using an error checking process; andat the receiving station, using the same or a related error checking process to process candidate bits known to the receiving station, and comparing the output of the error checking process to the error checking bits received from the transmitting station to determine if the candidate bits correspond to the additional bits.
  • 2. The method of claim 1 wherein the communicating of the additional bits further comprises at the transmitting station, deriving the error checking bits from the additional bits and the information bits using the error checking process; andat the receiving station, using the same or a related error checking process to process the candidate bits and the information bits received from the transmitting station, comparing the output of the error checking process result to the error checking bits received from the first station to determine if the candidate bits correspond to the additional bits.
  • 3. The method of claim 1 wherein the additional bits comprise an address identifying one or both of the transmitting and receiving stations.
  • 4. The method of claim 3 wherein the group of bits constitutes a packet, the information bits comprise a source address and data, and the additional bits comprise a destination address identifying the receiving station.
  • 5. The method of claim 3 wherein the group of bits constitutes a packet, the information bits comprise a source address and data, and the additional bits comprise at least a portion of a destination address at least partially identifying the receiving station.
  • 6. The method of claim 3 wherein the group of bits constitutes a Request To Send (RTS), the information bits comprise a source address and data, with the source address identifying the transmitting station, and the additional bits comprise a destination address identifying the receiving station.
  • 7. The method of claim 3 wherein the group of bits constitutes a RTS, the information bits comprise a source address and data, with the source address identifying the transmitting station, and the additional bits comprise at least a portion of a destination address at least partially identifying the receiving station.
  • 8. The method of claim 3 wherein the group of bits constitutes a Clear To Send (CTS) transmitted in response to an RTS, and the additional bits comprise one or both of the following: (1) a destination address identifying the receiving station and (2) a source address identifying the transmitting station.
  • 9. The method of claim 3 wherein the group of bits constitutes an acknowledgement, and the additional bits comprise one or both of the following: (1) a source address identifying the transmitting station and (2) a destination address identifying the receiving station.
  • 10. The method of claim 3 wherein the group of bits constitutes an acknowledgement and the additional bits comprise one or both of the following: (1) at least a portion of a source address at least partially identifying the transmitting station and (2) at least a portion of a destination address at least partially identifying the receiving station.
  • 11. The method of claim 3 wherein the group of bits constitutes an acknowledgement transmitted in response to a receipt of a packet, and the additional bits comprise a set of bits from the packet that is sufficiently unique as to associate the acknowledgement with the packet.
  • 12. The method of claim 6 wherein the information bits comprise bits indicating which portions of a previously transmitted packet need to be retransmitted.
  • 13. The method of claim 1 wherein the error checking process comprises a cyclic redundancy check, and the error checking bits comprise frame check sequence (FCS) bits associated with the cyclic redundancy check.
US Referenced Citations (188)
Number Name Date Kind
3806885 Moore Apr 1974 A
4569044 Tao et al. Feb 1986 A
4581734 Olson et al. Apr 1986 A
4630261 Irvin Dec 1986 A
4677612 Olson et al. Jun 1987 A
4682324 Ulug Jul 1987 A
4720850 Oberlander et al. Jan 1988 A
4726018 Bux et al. Feb 1988 A
4792947 Takiyasu et al. Dec 1988 A
4819229 Pritty et al. Apr 1989 A
4881241 Pommier et al. Nov 1989 A
4943959 Arnold Jul 1990 A
5001472 Fischer et al. Mar 1991 A
5003539 Takemoto et al. Mar 1991 A
5046069 Calvignac et al. Sep 1991 A
5081678 Kaufman et al. Jan 1992 A
5105423 Tanaka et al. Apr 1992 A
5121396 Irvin et al. Jun 1992 A
5140584 Suzuki Aug 1992 A
5157659 Schenkel Oct 1992 A
5197061 Halbert-Lassalle et al. Mar 1993 A
5214646 Yacoby May 1993 A
5228025 Le Floch et al. Jul 1993 A
5231634 Giles et al. Jul 1993 A
5274629 Helard et al. Dec 1993 A
5280480 Pitt et al. Jan 1994 A
5307376 Castelain et al. Apr 1994 A
5339313 Ben-Michael et al. Aug 1994 A
5343473 Cidon et al. Aug 1994 A
5384777 Ahmadi et al. Jan 1995 A
5416801 Chouly et al. May 1995 A
5426646 Slack Jun 1995 A
RE35001 Grow Jul 1995 E
5432848 Butter et al. Jul 1995 A
5436905 Li et al. Jul 1995 A
5448565 Chang et al. Sep 1995 A
5452288 Rahuel et al. Sep 1995 A
5452322 Lauer Sep 1995 A
5473602 McKenna et al. Dec 1995 A
5481535 Hershey Jan 1996 A
5483529 Baggen et al. Jan 1996 A
5488632 Mason et al. Jan 1996 A
5504747 Sweazey Apr 1996 A
5515379 Crisler et al. May 1996 A
5524027 Huisken Jun 1996 A
5537414 Takiyasu et al. Jul 1996 A
5541922 Pyhalammi Jul 1996 A
5548649 Jacobson Aug 1996 A
5555268 Fattouche et al. Sep 1996 A
5561770 de Bruijn et al. Oct 1996 A
5563883 Cheng Oct 1996 A
5563897 Pyndiah et al. Oct 1996 A
5568476 Sherer et al. Oct 1996 A
5610908 Shelswell et al. Mar 1997 A
5612975 Becker et al. Mar 1997 A
5615212 Ruszczyk et al. Mar 1997 A
5619651 Young Apr 1997 A
5623512 Sasaki Apr 1997 A
5627829 Gleeson et al. May 1997 A
5629948 Hagiwara et al. May 1997 A
5636230 Marturano et al. Jun 1997 A
5644576 Bauchot et al. Jul 1997 A
5651009 Perreault et al. Jul 1997 A
5694389 Seki et al. Dec 1997 A
5706348 Gray et al. Jan 1998 A
5717689 Ayanoglu Feb 1998 A
5732113 Schmidl et al. Mar 1998 A
5737330 Fulthorp et al. Apr 1998 A
5745769 Choi Apr 1998 A
5757766 Sugita May 1998 A
5757770 Lagoutte et al. May 1998 A
5764931 Schmahl et al. Jun 1998 A
5771235 Tang et al. Jun 1998 A
5787071 Basso et al. Jul 1998 A
5790541 Patrick et al. Aug 1998 A
5793307 Perreault et al. Aug 1998 A
5799033 Baggen Aug 1998 A
5812599 Van Kerckhove Sep 1998 A
5818821 Schurig Oct 1998 A
5818826 Gfeller et al. Oct 1998 A
5825807 Kumar Oct 1998 A
5828677 Sayeed et al. Oct 1998 A
5841778 Shaffer et al. Nov 1998 A
5841873 Lockhart et al. Nov 1998 A
5884040 Chung Mar 1999 A
5886993 Ruszczyk et al. Mar 1999 A
5892769 Lee Apr 1999 A
5896561 Schrader et al. Apr 1999 A
5903614 Suzuki et al. May 1999 A
5914932 Suzuki et al. Jun 1999 A
5914959 Marchetto et al. Jun 1999 A
5940399 Weizman Aug 1999 A
5940438 Poon et al. Aug 1999 A
5948060 Gregg et al. Sep 1999 A
5956338 Ghaibeh Sep 1999 A
5966412 Ramaswamy Oct 1999 A
5970062 Bauchot Oct 1999 A
5987011 Toh Nov 1999 A
6005894 Kumar Dec 1999 A
6006017 Joshi et al. Dec 1999 A
6041063 Povlsen et al. Mar 2000 A
6041358 Huang et al. Mar 2000 A
6044154 Kelly Mar 2000 A
6044482 Wong Mar 2000 A
6052377 Ohmi et al. Apr 2000 A
6076115 Sambamurthy et al. Jun 2000 A
6092214 Quoc et al. Jul 2000 A
6097703 Larsen et al. Aug 2000 A
6098179 Harter, Jr. Aug 2000 A
6108713 Sambamurthy et al. Aug 2000 A
6125150 Wesel et al. Sep 2000 A
6130887 Dutta Oct 2000 A
6130894 Ojard et al. Oct 2000 A
6151296 Vijayan et al. Nov 2000 A
6169744 Grabelsky et al. Jan 2001 B1
6182147 Farinacci Jan 2001 B1
6188717 Kaiser et al. Feb 2001 B1
6192397 Thompson Feb 2001 B1
6202082 Tomizawa et al. Mar 2001 B1
6215792 Abi-Nassif Apr 2001 B1
6216244 Myers et al. Apr 2001 B1
6222851 Petry Apr 2001 B1
6243386 Chan et al. Jun 2001 B1
6243449 Margulis et al. Jun 2001 B1
6246770 Stratton et al. Jun 2001 B1
6252849 Rom et al. Jun 2001 B1
6259696 Yazaki et al. Jul 2001 B1
6263445 Blumenau Jul 2001 B1
6278685 Yonge, III et al. Aug 2001 B1
6278716 Rubenstein et al. Aug 2001 B1
6279716 Kayatani et al. Aug 2001 B1
6289000 Yonge, III Sep 2001 B1
6295296 Tappan Sep 2001 B1
6334185 Hansson et al. Dec 2001 B1
6343083 Mendelson et al. Jan 2002 B1
6363052 Hosein Mar 2002 B1
6370156 Spruyt et al. Apr 2002 B2
6385672 Wang et al. May 2002 B1
6397368 Yonge, III et al. May 2002 B1
6421725 Vermilyea et al. Jul 2002 B1
6430192 Creedon et al. Aug 2002 B1
6430661 Larson et al. Aug 2002 B1
6434153 Yazaki et al. Aug 2002 B1
6442129 Yonge, III et al. Aug 2002 B1
6445717 Gibson et al. Sep 2002 B1
6456649 Isaksson et al. Sep 2002 B1
6466580 Leung Oct 2002 B1
6469992 Schieder Oct 2002 B1
6473435 Zhou et al. Oct 2002 B1
6480489 Muller et al. Nov 2002 B1
6487212 Erimli et al. Nov 2002 B1
6501760 Ohba et al. Dec 2002 B1
6519263 Huth Feb 2003 B1
6526451 Kasper Feb 2003 B2
6538985 Petry et al. Mar 2003 B1
6553534 Yonge, III et al. Apr 2003 B2
6567914 Just et al. May 2003 B1
6654410 Tzannes Nov 2003 B2
6667991 Tzannes Dec 2003 B1
6671284 Yonge, III et al. Dec 2003 B1
6747976 Bensaou et al. Jun 2004 B1
6765885 Jiang et al. Jul 2004 B2
6778507 Jalali Aug 2004 B1
6782503 Dawson Aug 2004 B1
6789128 Harrison et al. Sep 2004 B1
6882637 Le et al. Apr 2005 B1
7047453 Lappin, Jr. May 2006 B2
20010012319 Foley Aug 2001 A1
20010043576 Terry Nov 2001 A1
20010048692 Karner Dec 2001 A1
20020001314 Yi et al. Jan 2002 A1
20020012320 Ogier et al. Jan 2002 A1
20020042836 Mallory Apr 2002 A1
20020048368 Gardner Apr 2002 A1
20020065047 Moose May 2002 A1
20020131591 Henson et al. Sep 2002 A1
20020191533 Chini et al. Dec 2002 A1
20030006883 Kim et al. Jan 2003 A1
20030079169 Ho et al. Apr 2003 A1
20030174664 Benveniste Sep 2003 A1
20030217182 Liu et al. Nov 2003 A1
20030231652 Sprague et al. Dec 2003 A1
20030231658 Liang et al. Dec 2003 A1
20040001499 Patella et al. Jan 2004 A1
20040008728 Lee Jan 2004 A1
20040184481 Lee Sep 2004 A1
20050122994 Manglin et al. Jun 2005 A1
20060041734 Lim et al. Feb 2006 A1
Foreign Referenced Citations (4)
Number Date Country
3413144 Oct 1985 DE
9857440 Dec 1998 WO
WO200072495 Nov 2000 WO
0241598 May 2002 WO
Related Publications (1)
Number Date Country
20050114749 A1 May 2005 US