1. Field
This disclosure generally relates to automatic data collection (ADC) devices, methods and articles.
2. Description of the Related Art
The ADC field is generally directed to the use of devices and methods for automatically capturing data typically encoded in media such as a machine-readable symbol or tag carried by the item to which the data relates. A variety of ADC devices and ADC media are ubiquitous and well-known.
For example, a machine-readable data carrier may take the form of a machine-readable symbol, which may be selected from a variety of symbologies and which take the form of a bar code. Some bar coding systems employ standard message channel techniques, such as Basic Channel Model (BCM) techniques, to convey a message between components. Information describing the meaning of the data such as a serial number can be conveyed in the channel using standard techniques such as application identifiers, data identifiers, and text element identifiers. Some bar coding systems may employ out of channel techniques to convey additional information about the message, such as extended channel information (ECI) techniques, including the industry standard Extended Channel Model (ECM), which adds a layer to the BCM to convey additional information about the graphical representation of the data characters or whether the data characters have been compacted.
In another example, a machine-readable data carrier may take the form of a radio-frequency identification (RFID) device or tag, which may take the form of a card or a label. Such tags typically include an RFID substrate carrying circuitry such as a semiconductor device including memory and one or more conductive traces that form an antenna. Typically, RFID tags act as transponders, providing information stored in the semiconductor device in response to a radio-frequency (RF) signal, commonly referred to as an interrogation signal, received at the antenna from a reader or interrogator. Some RFID tags include security measures, such as passwords and/or encryption, which may be added at the system level. Many RFID tags also permit information to be stored in a semiconductor memory via an RF signal.
Due to the proliferation of RFID devices, methods and articles, and the frequent use of RFID devices in close proximity to each other, performance issues have arisen.
As mentioned above, the proliferation of RFID devices, methods and articles has led to performance issues. Some of these issues can be addressed through user intervention, but this approach is time consuming and expensive and raises compatibility issues.
Instead of passing commands manually, commands may be encoded into the message or into the message signal of the data carrier. Alternatively, commands may be passed out of the message signal channel. Moreover, existing symbol techniques can be modified to pass commands and/or additional information about the message out of the message signal channel. Currently there is no means of transporting commands to an RFID device through the use of another data carrier.
In one embodiment, a first machine-readable data carrier comprises an embedded command to control communication with a second machine-readable data carrier. An automatic data collection system is configured to extract the embedded command from the first data carrier and to execute the command to communicate with the second data carrier.
In one embodiment, a method of operating an automatic data collection system comprises extracting a command encoded in a first machine-readable data carrier, associating the command with a data payload of a second machine-readable data carrier and executing the command. In one embodiment, the method further comprises encoding the command in an out-of-channel message of the first data carrier. In one embodiment, extracting the command comprises reading a machine-readable symbol. In one embodiment, extracting the command comprises interpreting an extended-channel portion of the machine-readable symbol. In one embodiment, extracting the command comprises interpreting a character in the extended-channel portion of the machine-readable symbol. In one embodiment, extracting the command comprises interpreting a character in the machine-readable symbol. In one embodiment, the machine-readable symbol is a bar code. In one embodiment, executing the command comprises forwarding the command to a radio-frequency interrogator. In one embodiment, the method further comprises extracting information related to the second machine-readable data carrier from the first machine-readable data carrier. In one embodiment, the command comprises a read command, the information includes a radio-frequency identification device identifier, associating the command with the data payload of the second machine-readable data carrier comprises activating a reader to identify a radio-frequency identification device associated with the radio-frequency identification device identifier, and executing the command comprises reading the data payload of the identified radio-frequency identification device. In one embodiment, the command comprises a private/public keyed write command, the information includes a public key, and executing the command comprises retrieving a private key and writing data to the data payload of the second machine-readable data carrier. In one embodiment, the command comprises a retrieve a private key command. In one embodiment, the command comprises a write command.
In one embodiment, a first machine-readable data carrier comprises a machine-readable data payload and an embedded command to control communication with a second machine-readable data carrier. In one embodiment, the first machine-readable data carrier further comprises an extended-channel portion and the command is embedded in a character in the extended-channel portion. In one embodiment, the extended-channel portion comprises a different character identifying the second machine-readable data carrier. In one embodiment, a format of the first machine-readable data carrier comprises a machine-readable symbol format. In one embodiment, the format is a bar code format. In one embodiment, the command is embedded in the machine-readable data payload of the first machine-readable data carrier. In one embodiment, the first machine-readable data carrier further comprises a memory and the machine-readable data payload of the first machine-readable data carrier is stored in the memory. In one embodiment, the embedded command is a read command. In one embodiment, the embedded command is a write command. In one embodiment, the embedded command comprises a retrieve a private key command.
In one embodiment, an automatic data collection system comprises means for extracting from a first machine-readable data carrier a command to control communication with a second machine-readable data carrier, and means for executing the extracted command communicatively coupled to the means for extracting the command. In one embodiment, the automatic data collection system further comprises means for embedding the command in the first machine-readable data carrier. In one embodiment, the means for extracting comprises a symbol reader. In one embodiment, the symbol reader is a bar code reader. In one embodiment, the means for executing comprises a radio-frequency interrogator communicatively coupled to the symbol reader. In one embodiment, the means for extracting comprises a radio-frequency interrogator. In one embodiment, the means for executing comprises a symbol reader.
In one embodiment, a computer-readable memory medium stores instructions for causing a processor to operate an automatic data collection system by extracting a command encoded in a first machine-readable data carrier, associating the command with a data payload of a second machine-readable data carrier, and executing the command. In one embodiment, the instructions cause the processor to extract information identifying the second machine-readable data carrier from the first machine-readable data carrier. In one embodiment, the instructions cause the processor to extract the command from a portion of the first machine-readable data carrier. In one embodiment, the instructions cause the processor to extract the command from an out-of-channel portion of the machine-readable data carrier.
In one embodiment, a method of tracking an object comprises storing, in a first machine-readable data carrier, a command related to a data payload of a second machine-readable data carrier, and storing, in the second machine-readable data carrier, a first message related to the object. In one embodiment, the method further comprises storing, in the first machine-readable data carrier, a second message related to the object. In one embodiment, storing the command comprises printing a bar code symbol. In one embodiment, storing the first message comprises programming a radio-frequency identification device. In one embodiment, the method further comprises storing, in the first machine-readable data carrier, additional information related to the command. In one embodiment, storing the command comprises programming a radio-frequency identification device. In one embodiment, the method further comprises extracting the command from the first machine-readable data carrier, and executing the command. In one embodiment, executing the command comprises reading the first message. In one embodiment, storing the command comprises storing the command in an out-of-channel portion of the first machine-readable data carrier.
In one embodiment, a method of operating an automatic data collection system comprises extracting a command encoded in a machine-readable data carrier, associating the command with a data payload of the machine-readable data carrier and executing the command.
The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements and angles are not drawn to scale, and some of these elements are arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of the elements as drawn are not necessarily intended to convey any information regarding the actual shape of particular elements, and have been selected solely for ease of recognition in the drawings.
In the following description, certain details are set forth in order to provide a thorough understanding of various embodiments of devices, methods and articles. However, one of skill in the art will understand that other embodiments may be practiced without these details. In other instances, well-known structures and methods associated with automatic data collection devices, methods and articles, such as readers, labels, printers, machine-readable symbols and portions thereof, RFID interrogators, RFID tags, RFID chips, semiconductor devices, RF signals, and antennas have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments.
Unless the context requires otherwise, throughout the specification and claims which follow, the word “comprise” and variations thereof, such as “comprising,” and “comprises,” are to be construed in an open, inclusive sense, that is as “including, but not limited to.”
Reference throughout this specification to “one embodiment,” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases “in one embodiment,” or “in an embodiment” in various places throughout this specification are not necessarily referring to the same embodiment, or to all embodiments. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
The headings are provided for convenience only, and do not interpret the scope or meaning of this disclosure or the claims.
The RFID system 116, the symbol system 118 and the command extractor 120 may be implemented in a variety of ways, including as a combined control system or as separate subsystems. The RFID system 116, the symbol system 118 and the command extractor 120 may be implemented as one or more microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), or the like, or as a series of instructions stored in a memory, such as the memory 114, and executed by a controller, such as the processor 112, or various combinations of the above. Thus, software modifications to existing hardware may allow the implementation of the ADC system 100. Various subsystems, such as the command extractor 120, are identified as separate blocks in the functional block diagram of
While the illustrated embodiment denotes a single processor 112 in the interrogator 102, other embodiments may comprise multiple processors. The memory 114 may comprise, for example, registers, read only memory (“ROM”), random access memory (“RAM”), flash memory and/or electronically erasable programmable read only memory (“EEPROM”), and may provide instructions and data for use by the interrogator 102 and/or the RFID and symbol sub-systems 116, 118.
Several illustrative embodiments of systems and machine-readable data carriers will be described with reference to
Several examples will be described in more detail for illustration purposes. In one example embodiment, a command may be extracted from information stored in a machine-readable data carrier, such as the symbol 122, for use by the system 100 to initiate and/or control interaction between the RFID system 116 and an RFID device, such as the RFID device 126. For example, with reference to
For example, the Extended Channel Interpretation (ECI) format employs transformation ECIs, which encode encryption or transformation information. ECI also employs transformation prefixes to encode random data, such as a reference to a regulation (e.g., “See EPA document 1234 for toxicity information”). In one example embodiment in the ECI format, a transformation prefix ECI (e.g., character 206) is used in conjunction with a transformation ECI (e.g., character 208) and a null-encryption scheme to communicate RFID instructions to a receiving system, such as the interrogator 102. For example, the symbol 200 of
In another example embodiment in the ECI format, a transformation ECI (e.g., character 208) in a symbol (e.g., symbol 200) may comprise a command to read or write to an RFID tag identified in a message portion (e.g., message portion 226 of the symbol 200). The extended channel portion 228 is out of the symbol data channel, and thus avoids confusion between the data and the command.
In another example embodiment in an ECI format, a character (e.g. character 206) may comprise a transformation prefix ECI comprising an indication that a following transformation ECI (e.g., character 208) is a range of an RFID tag with a unique RFID tag identifier that is identified in a message portion (e.g., character 212 of message portion 226) of a symbol (e.g., symbol 200).
Other out-of-channel communication methods may be employed. Out-of-channel methods may be interpreted by a reader (such as the interrogator 102) after, before, during and/or without processing of the data payload, which can be advantageous because it can lead to reduced processing demands and faster system performance. For example, interpretation of the data payload may be performed by a host system. In another example, a reader may execute a command before the data payload is interpreted.
The commands may be embedded in the data payload in some embodiments. For example, with reference to
For example, the message portion 226 may employ identifiers that contain information about the data, such as industry standard identifiers, including data identifiers, application identifiers, and text element identifiers. These identifiers can be modified to include commands and/or data related to commands, either in addition to, or instead of, the usual labels or information contained in the identifiers. For example, with reference to symbol 200 of
In another example, with reference to
In one embodiment, a machine-readable data carrier, such as, for example, the bar code 200 illustrated in
When the system 100 determines that the portion contains a command or an indication of a command related to another data carrier, the method 400 proceeds from 408 to 410. At 410, the system 100 executes the command, such as a command to read an RFID device associated with a symbol. The method 400 proceeds from 410 to 412.
When the system 100 determines that the portion read does not contain a command or an indication of a command, the method 400 proceeds from 408 to 412. At 412, the system 100 performs further processing of the first data carrier, if appropriate, such as transmitting the data payload and associated encryption information to a host system. In another example, an interrogator may be configured to decrypt a data payload and transmit the decrypted payload to a host system. The method 400 proceeds from 412 to 414, where the method returns the value of any desired information and may perform other processing.
Embodiments of the method discussed in
The host 504, symbol printer 506, first RFID system 508, the symbol reader 510 and the second RFID system 512 may be implemented in a variety of ways, including as a combined system or as separate subsystems. The host 504, symbol printer 506, first RFID system 508, the symbol reader 510 and the second RFID system 512 may be implemented using one or more microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), or the like, or as a series of instructions stored in one or more memories (see memory 114 in
The method 600 initializes at 602 and proceeds to 604. At 604, the system 500 prints a symbol associated with an object. The symbol includes an out-of-channel command, such as a read command associated with an RFID identifier, which may be unique. For this description of an example embodiment, the command is assumed to be a read command associated with a unique RFID identifier. Other commands may be included in the symbol with or instead of the read command. The symbol may typically take the form of a bar code symbol, which is typically affixed to the object or to a container for the object. The method 600 proceeds from 604 to 606.
At 606, the system 500 programs an RFID device associated with the object. The programming may include programming the unique RFID identifier, or the unique identifier may already be programmed into the RFID device. The RFID device may typically take the form of an RFID tag, which is typically affixed to the object or to a container for the object. The method 600 proceeds from 606 to 608.
At 608, the object is moved to a new location. Typically, the object, which may be inside a container, is shipped to a new location. The method 600 proceeds from 608 to 610. At 610, the object is received at the new location. The method 600 proceeds from 610 to 612.
At 612, the system 500 reads the symbol. Typically, the symbol is read by a bar code reader. The method proceeds from 612 to 614. At 614, the system 500 interprets the out-of-channel command contained within the symbol. In this example, the system 500 interprets the command as a command to read an RFID tag with the unique RFID identifier. The method 600 proceeds from 614 to 616.
At 616, the system 500 causes an RFID system (e.g., the second RFID system 512 in
At 622, the system 500 returns any desired data. For example, the system 500 may provide data read by the symbol reader 510 and the second RFID system 512 to the host 504. The method 600 proceeds from 622 to 624, where the method 600 may perform other processing.
The method 600 illustrated in
Embodiments of the method discussed in
The method 700 initializes at 702 and proceeds to 704. At 704, the system 500 prints a symbol associated with an object. The symbol includes an out-of-channel command, such as a public/private key write command. The symbol may typically take the form of a bar code symbol, which is typically affixed to the object or to a container for the object. For this example embodiment, the command is assumed to be a public/private key write command associated with a unique RFID identifier, a public key and a private key. The unique identifier may be embedded in an out-of-channel or an in-channel character. Similarly, the public key may be embedded in an out-of-channel message and/or an in-channel message. Alternatively, the public key may be known to a receiving system, such as the second RFID system 512. The private key will typically not be included in the symbol, but will need to either be known to a receiving system, or retrievable by a receiving system. The symbol may include out-of-channel or in-channel information identifying where or how to retrieve the private and/or the public keys. The method 700 proceeds from 704 to 706.
At 706, the system 500 programs an RFID device associated with the object. In this example, the programming includes programming a public key and a private key. The programming may include programming the unique RFID identifier, or the unique identifier may already be programmed into the RFID device. The RFID device may be configured to respond to an interrogation signal only when the signal includes the public key and the private key. The RFID device may typically take the form of an RFID tag, which is typically affixed to the object or to a container for the object. The method 700 proceeds from 706 to 708.
At 708, the object is moved to a new location. Typically, the object is shipped to a new location. The method 700 proceeds from 708 to 710. At 710, the object is received at the new location. The method 700 proceeds from 710 to 712.
At 712, the system 500 reads the symbol. Typically, the symbol is read by a bar code reader. The method proceeds from 712 to 714. At 714, the system 500 interprets the out-of-channel command contained within the symbol. In this example, the system 500 interprets the command as a write command associated with the public/private key and the RFID identifier, and causes the command to be executed. This may be done, for example, by generating a signal to cause an RFID system, such as the second RFID system 512 illustrated in
At 716, the system 500 causes an RFID system (e.g., the second RFID system 512 in
The method 700 illustrated in
When the system 100 determines that the portion contains an embedded command or an embedded indication of a command related to the data carrier, the method 800 proceeds from 810 to 812. At 812, the system 100 executes the embedded command, such as, for example, a kill command instructing the RFID device 126 to no longer respond to interrogation signals. In another example, the indication of the command may be an indication that the RFID device 126 will turn itself off after transmitting the payload, and the command may be a command to cause the system 100 to advise a host that the RFID device 126 has turned itself off. In another example, the embedded command may be a command to change the password of the RFID device 126. The method 800 proceeds from 812 to 814, where the method returns the value of any desired information and terminates or continues with other processing.
When the system 100 determines that the portion does not contain an embedded command or an indication of a command, the method 800 proceeds from 810 to 814, where the method returns the value of any desired information and terminates or continues with other processing.
Embodiments of the method discussed in
Although specific embodiments of and examples for the ADC devices, methods, and articles are described herein for illustrative purposes, various equivalent modifications can be made without departing from the spirit and scope of this disclosure, as will be recognized by those skilled in the relevant art. The various embodiments described above can be combined to provide further embodiments. All of the above U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet, including, but not limited to: U.S. Pat. No. 6,371,375, entitled MEMORY AND APPARATUS FOR ASSOCIATING DATA WITH A WIRELESS MEMORY DEVICE, and issued to Ackley, et al. (“the '375 patent”); U.S. patent application Ser. No. 11/191,616, entitled AUTOMATIC DATA COLLECTION DEVICE, METHOD AND ARTICLE, and filed by Nikitin, et al.; “International Technical Standard: Extended Channel Interpretations: Identification Schemes and Protocols,” AMI Publication ITS/04-001 (May 24, 2004); “International Symbology Specification—93i,” AMI Publication ITS/99-004 (Nov. 5, 1999); “Information Technology—Automatic Identification and Data Capture Techniques—Bar Code Symbology Specifications,” International Standard ISO/IEC15438, First Edition PDF417 (Sep. 15, 2001); “Transfer Syntax for High Capacity Media,” International Standard ISO 15434 FDIS (Feb. 5, 1999); and ISO/PDTS 21849, Second Edition (Mar. 27, 2002), are incorporated herein by reference, in their entirety. Aspects of the disclosure and embodiments can be modified, if necessary, to employ systems, circuits and concepts of the various patents, applications, and publications to provide yet further embodiments.
These and other changes can be made to the invention in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the invention to the specific embodiments disclosed in the specification and the claims. Accordingly, the invention is not limited by the disclosure, but instead its scope is to be determined entirely by the following claims.
This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Patent Application No. 60/830,020 filed Jul. 11, 2006, and U.S. Provisional Patent Application No. 60/834,314 filed Jul. 28, 2006, the contents of which are both incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
836531 | Pickard | Nov 1906 | A |
837616 | Dunwoody | Dec 1906 | A |
3710337 | Grant | Jan 1973 | A |
3852755 | Works et al. | Dec 1974 | A |
3949403 | Yoshida et al. | Apr 1976 | A |
4056710 | Shepardson et al. | Nov 1977 | A |
4079482 | Yeh | Mar 1978 | A |
4080603 | Moody | Mar 1978 | A |
4307293 | Lazzarotti et al. | Dec 1981 | A |
4344184 | Edwards | Aug 1982 | A |
4354101 | Hester et al. | Oct 1982 | A |
4385231 | Mizutani et al. | May 1983 | A |
4443794 | Sakurai | Apr 1984 | A |
4523087 | Benton | Jun 1985 | A |
4562102 | Rabuse et al. | Dec 1985 | A |
4567361 | Rosenthal | Jan 1986 | A |
4575621 | Dreifus | Mar 1986 | A |
4589144 | Namba | May 1986 | A |
4728784 | Stewart | Mar 1988 | A |
4742567 | Ohe et al. | May 1988 | A |
4782221 | Brass et al. | Nov 1988 | A |
4785451 | Sako et al. | Nov 1988 | A |
4786792 | Pierce et al. | Nov 1988 | A |
4792910 | Lange | Dec 1988 | A |
4794239 | Allais | Dec 1988 | A |
4810867 | Speicher | Mar 1989 | A |
4816839 | Landt | Mar 1989 | A |
4823311 | Hunter et al. | Apr 1989 | A |
4827395 | Anders et al. | May 1989 | A |
4841128 | Gröttrup et al. | Jun 1989 | A |
4853705 | Landt | Aug 1989 | A |
4855581 | Mertel et al. | Aug 1989 | A |
4915519 | Afzali-Ardakani et al. | Apr 1990 | A |
4916296 | Streck | Apr 1990 | A |
4980544 | Winter | Dec 1990 | A |
5047860 | Rogalski | Sep 1991 | A |
5075691 | Garay et al. | Dec 1991 | A |
5095382 | Abe | Mar 1992 | A |
5097263 | Delpech et al. | Mar 1992 | A |
5097484 | Akaiwa | Mar 1992 | A |
5101200 | Swett | Mar 1992 | A |
5128526 | Yoshida | Jul 1992 | A |
5142292 | Chang | Aug 1992 | A |
5160023 | Adams et al. | Nov 1992 | A |
5184005 | Ukai et al. | Feb 1993 | A |
5204515 | Yoshida | Apr 1993 | A |
5216233 | Main et al. | Jun 1993 | A |
5216419 | Fujisaka et al. | Jun 1993 | A |
5218689 | Hotle | Jun 1993 | A |
5220335 | Huang | Jun 1993 | A |
5243655 | Wang | Sep 1993 | A |
5267800 | Petteruti et al. | Dec 1993 | A |
5278395 | Benezet | Jan 1994 | A |
5280159 | Schultz et al. | Jan 1994 | A |
5298731 | Ett | Mar 1994 | A |
5300761 | Kasahara et al. | Apr 1994 | A |
5315511 | Matsuura et al. | May 1994 | A |
5324922 | Roberts | Jun 1994 | A |
5324927 | Williams | Jun 1994 | A |
5341381 | Fuller | Aug 1994 | A |
5380998 | Bossen et al. | Jan 1995 | A |
5382778 | Takahira et al. | Jan 1995 | A |
5382784 | Eberhardt | Jan 1995 | A |
5387783 | Mihm et al. | Feb 1995 | A |
5389770 | Ackley | Feb 1995 | A |
5420403 | Allum et al. | May 1995 | A |
5430441 | Bickley et al. | Jul 1995 | A |
5434401 | Bauser | Jul 1995 | A |
5434572 | Smith | Jul 1995 | A |
5448110 | Tuttle et al. | Sep 1995 | A |
5463643 | Gaskins et al. | Oct 1995 | A |
5466501 | Logan et al. | Nov 1995 | A |
5479515 | Longacre, Jr. | Dec 1995 | A |
5484997 | Haynes | Jan 1996 | A |
5489908 | Orthmann et al. | Feb 1996 | A |
5497701 | Uland | Mar 1996 | A |
5499397 | Wadin et al. | Mar 1996 | A |
5514858 | Ackley | May 1996 | A |
5521601 | Kandlur et al. | May 1996 | A |
5521815 | Rose, Jr. | May 1996 | A |
5528222 | Moskowitz et al. | Jun 1996 | A |
5536924 | Ackley | Jul 1996 | A |
5539191 | Ackley | Jul 1996 | A |
5548110 | Storch et al. | Aug 1996 | A |
5550365 | Klancnik et al. | Aug 1996 | A |
5550547 | Chan et al. | Aug 1996 | A |
5552591 | Bossen et al. | Sep 1996 | A |
5553041 | Inagawa et al. | Sep 1996 | A |
5553084 | Ackley et al. | Sep 1996 | A |
5554974 | Brady et al. | Sep 1996 | A |
5557092 | Ackley et al. | Sep 1996 | A |
5560293 | Boreali et al. | Oct 1996 | A |
5563402 | Reddersen et al. | Oct 1996 | A |
5565847 | Gambino et al. | Oct 1996 | A |
5566441 | Marsh et al. | Oct 1996 | A |
5588005 | Ali et al. | Dec 1996 | A |
5594228 | Swartz et al. | Jan 1997 | A |
5612531 | Barkan | Mar 1997 | A |
5619027 | Ackley | Apr 1997 | A |
5629508 | Findley, Jr. et al. | May 1997 | A |
5640002 | Ruppert et al. | Jun 1997 | A |
5659431 | Ackley | Aug 1997 | A |
5673037 | Cesar et al. | Sep 1997 | A |
5712643 | Skladany | Jan 1998 | A |
5723853 | Longacre, Jr. et al. | Mar 1998 | A |
5729201 | Jahnes et al. | Mar 1998 | A |
5761219 | Maltsev | Jun 1998 | A |
5761529 | Raji et al. | Jun 1998 | A |
5763867 | Main et al. | Jun 1998 | A |
5767498 | Heske, III et al. | Jun 1998 | A |
5777310 | Liu et al. | Jul 1998 | A |
5777561 | Chieu et al. | Jul 1998 | A |
5782496 | Casper et al. | Jul 1998 | A |
5786626 | Brady et al. | Jul 1998 | A |
5788796 | Look et al. | Aug 1998 | A |
5805082 | Hassett | Sep 1998 | A |
5811781 | Ackley | Sep 1998 | A |
5812065 | Schrott et al. | Sep 1998 | A |
5818031 | Endoh | Oct 1998 | A |
5840657 | Mehta et al. | Nov 1998 | A |
5842118 | Wood, Jr. | Nov 1998 | A |
5874896 | Lowe et al. | Feb 1999 | A |
5874902 | Heinrich et al. | Feb 1999 | A |
5923305 | Sadler et al. | Jul 1999 | A |
5942987 | Heinrich et al. | Aug 1999 | A |
5972156 | Brady et al. | Oct 1999 | A |
5973598 | Beigel | Oct 1999 | A |
5973600 | Mosher, Jr. | Oct 1999 | A |
5979773 | Findley, Jr. et al. | Nov 1999 | A |
5982904 | Eghtesadi et al. | Nov 1999 | A |
5993093 | Schoennauer et al. | Nov 1999 | A |
6003775 | Ackley | Dec 1999 | A |
6012638 | Ackley et al. | Jan 2000 | A |
6019865 | Palmer et al. | Feb 2000 | A |
6024289 | Ackley | Feb 2000 | A |
6025784 | Mish | Feb 2000 | A |
6076064 | Rose, Jr. | Jun 2000 | A |
6078259 | Brady et al. | Jun 2000 | A |
6081718 | Ando et al. | Jun 2000 | A |
6092133 | Erola et al. | Jul 2000 | A |
6097301 | Tuttle | Aug 2000 | A |
6104311 | Lastinger | Aug 2000 | A |
6118379 | Kodukula et al. | Sep 2000 | A |
6123796 | Kathmann et al. | Sep 2000 | A |
6149059 | Ackley | Nov 2000 | A |
6180198 | Bond | Jan 2001 | B1 |
6210515 | Boreali et al. | Apr 2001 | B1 |
6243013 | Duan et al. | Jun 2001 | B1 |
6246326 | Wiklof et al. | Jun 2001 | B1 |
6259372 | Taranowski et al. | Jul 2001 | B1 |
6272242 | Saitoh et al. | Aug 2001 | B1 |
6278413 | Hugh et al. | Aug 2001 | B1 |
6285342 | Brady et al. | Sep 2001 | B1 |
6286763 | Reynolds et al. | Sep 2001 | B1 |
6321986 | Ackley | Nov 2001 | B1 |
6327972 | Heredia et al. | Dec 2001 | B2 |
6360208 | Ohanian et al. | Mar 2002 | B1 |
6371375 | Ackley et al. | Apr 2002 | B1 |
6409401 | Petteruti et al. | Jun 2002 | B1 |
6422476 | Ackley | Jul 2002 | B1 |
6512482 | Nelson et al. | Jan 2003 | B1 |
6570386 | Goldstein | May 2003 | B2 |
6585159 | Meier et al. | Jul 2003 | B1 |
6585437 | Wiklof et al. | Jul 2003 | B1 |
6593853 | Barrett et al. | Jul 2003 | B1 |
6664897 | Pape et al. | Dec 2003 | B2 |
6677852 | Landt | Jan 2004 | B1 |
6707376 | Patterson et al. | Mar 2004 | B1 |
6899476 | Barrus et al. | May 2005 | B1 |
6933848 | Stewart et al. | Aug 2005 | B1 |
6967577 | Taylor et al. | Nov 2005 | B2 |
7323977 | Kodukula et al. | Jan 2008 | B2 |
7423539 | Hyde et al. | Sep 2008 | B2 |
7528728 | Oliver et al. | May 2009 | B2 |
7546955 | Marty et al. | Jun 2009 | B2 |
7579955 | Pillai | Aug 2009 | B2 |
7667589 | Desmons et al. | Feb 2010 | B2 |
20030218069 | Meier et al. | Nov 2003 | A1 |
20050120260 | Suzuki et al. | Jun 2005 | A1 |
20050212674 | Desmons et al. | Sep 2005 | A1 |
20060022801 | Husak et al. | Feb 2006 | A1 |
20060028343 | Taylor et al. | Feb 2006 | A1 |
20060267731 | Chen | Nov 2006 | A1 |
20070024423 | Nikitin et al. | Feb 2007 | A1 |
20070081671 | Ross et al. | Apr 2007 | A1 |
20070194929 | Wagner et al. | Aug 2007 | A1 |
20070296582 | Rofougaran | Dec 2007 | A1 |
20070296583 | Rofougaran | Dec 2007 | A1 |
20080188209 | Dorogusker et al. | Aug 2008 | A1 |
20080231451 | Kamel | Sep 2008 | A1 |
20090272812 | Marty et al. | Nov 2009 | A1 |
Number | Date | Country |
---|---|---|
33 30 261 | Mar 1985 | DE |
0 595 549 | May 1994 | EP |
0 667 592 | Aug 1995 | EP |
0 718 912 | Jun 1996 | EP |
2 760 209 | Sep 1998 | FR |
3113673 | May 1991 | JP |
1040329 | Feb 1998 | JP |
11-221948 | Aug 1999 | JP |
WO 9512863 | May 1995 | WO |
WO 9613803 | May 1996 | WO |
WO 9847101 | Oct 1998 | WO |
WO 2007035863 | Mar 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20080011822 A1 | Jan 2008 | US |
Number | Date | Country | |
---|---|---|---|
60830020 | Jul 2006 | US | |
60834314 | Jul 2006 | US |