The invention relates to the collection and use of data using radio frequency identification tags.
Radio frequency identification (RFID) has been proposed for use in a number of applications in which an RFID tag is attached to an item and subsequently interrogated or read to obtain information regarding that item. For example, PCT Publication Nos. WO 00/10144 and WO 00/10122 describe various functions and applications for RFID systems, and exemplify the use of RFID tags in libraries. U.S. Pat. No. 5,963,134 also describes certain uses for RFID systems in libraries and for other applications. The present invention is related to the collection and management of data using RFID tags and systems.
The present invention relates to certain aspects of the collection and use of data obtained by interrogating RFID tags, each of which is associated with an item of interest, using an RFID reader. In some embodiments it is preferred to use a portable, and preferably, a handheld RFID reader to interrogate the RFID-tagged items. In general terms, the present invention relates to data collection and categories, notification during interrogation, inventory, background inventory, real-time inventory reconciliation, altering the permissible error tolerance, and conversion of non-RFID-tagged items to RFID-tagged items. The items may be, for example, assets, evidence, goods in warehouse, distribution, or commercial, retail, or storage facilities, pallets or storage containers, documents, files (including patient or client files and records), and mail (including envelopes and packages).
Certain embodiments of the present invention are illustrated in the appended Figures:
1. General RFID Information
RFID tags and readers for such tags are well known in the art. For example, RFID tags are available from Texas Instruments Company of Dallas, Tex. under the designation “Tag-It,” and readers are also available from Texas Instruments under the designation “Commander,” among others. One particularly useful embodiment of an RFID reader is described in U.S. Pat. No. 6,232,870 (Garber et al.), in which a portable integrated RFID reader includes an antenna, a computer, a display, and an RFID reader for interrogating RFID tags. The contents of U.S. Pat. No. 6,232,870, PCT Publication No. WO 00/10122, and PCT Publication No. WO 00/10144 are hereby incorporated by reference herein. The present invention is related to methods of using RFID readers to obtain information from RFID tags, and to methods of using that information once obtained. These and other aspects of the invention are described in more detail below.
One useful function of an RFID reader is for the collection of data. That is, when an RFID reader interrogates an RFID tag, information related to the item with which the tag is associated is collected and stored in a database. The database may reside in the memory of the RFID reader, in a removable data storage device (such as a flash memory card) associated with the RFID reader, in the memory of another device such as a computer, or in more than one of these locations. The RFID reader may be a portable reader of the type described above or in the '870 patent, or it may be a component of another device such as one that checks items into and out of inventory, or one that converts bar-coded or other identified items to RFID-tagged items by obtaining information about the item and then providing an RFID tag that is associated with that item.
Certain aspects of the present invention may be exemplified in a library environment, where RFID systems may be particularly useful. The scope of the invention is not limited to libraries, however, and can be used in other suitable environments including but not limited to the tracking of assets, evidence, goods in warehouse, distribution, commercial, retail, or storage facilities, pallets or storage containers, documents, files (including patient or client files and records), and mail (including envelopes and packages). In light of the disclosure of the invention provided herein, these and other uses of the invention will be apparent to persons of ordinary skill in the art.
2. Data Collection and Categories
In one aspect of the present invention, data can be collected and sorted into categories for storage in a database. A category, as that term is used herein, is a group of items that possess specified attributes, and represents only a portion (though perhaps a major portion) of an entire group of RFID-tagged items. The RFID reader may be provided with certain default categories believed to be of interest to the user, or the user may define the attributes of items that fall within a category or categories. For example, if the user uses the RFID reader in a library, the default categories may be locations within the library (reference, non-fiction, or fiction), or types of items (books, periodicals, audio/video, etc.). Defined or customized categories could include those for items that are believed to have been used in a certain manner (such as used inside the library but not checked out, or used for classroom or program purposes, or in connection with audio or video players), or other categories designed by a user for a specific application. These categories may be defined for or provided to the RFID reader through a user interface such as a display having data entry capabilities, or by uploading from a removable data storage medium, or by uploading from a computer database that is linked (for example by wire, docking station, or wirelessly) to the RFID reader.
Once certain categories have been selected or defined, the RFID reader may be used to interrogate RFID tags associated with items of interest. The categorization may be done in several ways. A first way of categorizing RFID-tagged items is to select (for example, from a list of categories displayed for the user) or define a category, interrogate RFID tags associated with items of interest, and then save the information obtained from those RFID tags within the selected or defined category in a database. This associates the RFID-tagged items with the category or categories. The user can then continue to interrogate RFID tags associated with items in that category, or switch to another category. As an example, a user in a library may select or define a category for “used inside library but not checked out,” then interrogate RFID tags associated with items left by users inside the library, and then save that information within the “in-house use” category on a database. If the user then wishes to change categories, the user may select or define another category (“used in children's reading room,” for example), and then interrogate items and save them within that category on a database. The database can be one stored within the memory of the RFID reader, on a removable data storage device (such as a flash memory card) associated with the RFID reader, within memory associated with a separate computer or other device, or the like.
One example of a method 10 of collecting information related to RFID tags associated with items of interest is illustrated in
A second way of categorizing RFID-tagged items is to select or define at least two categories, use an RFID reader to interrogate at least one RFID-tagged item, and then to associate that item with one or more of the categories. That is, categories may be created for different types of items, or for items having a different inventory status (present and absent, for example), or for items that have been recently interrogated (and thus may be a frequently used item) or not. The RFID-tagged items may be categorized in none, one, or more than one of the categories, depending on whether or not each item has the attributes of the items to be categorized in each respective category. The categories may be mutually exclusive (meaning that every RFID-tagged item may be categorized in only one category) or not.
A third way of categorizing RFID-tagged items is to select at least one category of items; interrogate RFID tags associated with items, at least one of which is within the category of items; and associate the RFID-tagged items with the appropriate category. That is, the RFID reader would associate items that have certain attributes with a certain category, and ignore any item that does not have those attributes. Thus if a user were only interested in items having certain characteristics, the RFID reader could create a list of only those items, without listing or categorizing any other items that didn't have the specified characteristics. For example, if a user in a library were only interested in obtaining information from items of a certain type, such as reference texts, a category for reference texts could be created, RFID-tagged items interrogated, and only reference texts categorized in that category. The information necessary to categorize each RFID-tagged item (in this and other embodiments) may be obtained from the RFID tag itself, or from a database that includes a record related to that RFID tag and/or the item, such as a database stored in memory associated with the RFID reader. That memory may be integral, or may be a removable data storage device, such as a flash memory card.
3. Notification During Interrogation
During data collection, the RFID reader may provide audible and/or visual feedback to indicate (a) when the RFID reader is reading tags, (b) when the RFID reader detects an item that is on a list of predetermined items, and/or (c) when the RFID reader detects an RFID tag that does not match an entry on an existing database. For example, a lighted indicator may indicate when RFID tags are being interrogated successfully, an audible signal may indicate that an item that is on a list of predetermined items has been detected, or a signal, such as a light or an audible sound, may also indicate that an RFID tag has been interrogated that does not match an entry on an existing database of items. The signal may also be provided on a user interface, such as a display, and that user interface may enable the user to create a database record for the item, and/or enter information related to the item. For example, the user interface may include a touch panel display and/or an actual or simulated keyboard, through which a user can create a database record for the item, and/or enter information through the user interface that describes the type of item, its name or title, an item identifier of some type, or other information.
One example of a method 20 of identifying items associated with RFID tags is illustrated in
4. Inventory
It may also be useful to conduct inventory using an RFID reader and RFID tags associated with items of interest. The RFID reader collects information related to the items by interrogating the RFID tags associated with the items. However, if this information is simply listed in a database in the order that the items were interrogated, then if a single item is out of place by, for example, 1000 items, then when that “interrogation list” is compared against a predetermined ordered list, the result may indicate that the intervening 1000 items are out of position by at least one place. For example, if in a library a book is out of position because it is 1000 books to the left of its proper position, then the interrogated list may indicate that the 1000 intervening books are all out of position. This may result in a paper printout or a data listing that is inconveniently large, and thus of little use to a user. Also, some users are not concerned about items that are out of position by only a few positions. This can be fairly common and doesn't typically present a problem for someone who is searching for the item, because the item is sufficiently near its expected location. A standard inventory report, however, may list all items that are out of position at all, even those only out of order by a small amount.
There are other devices, such as handheld RFID readers, that report errors in storage locations for items. For those who use such a device, an inventory report that describes errors in location as well as the presence or absence of items may not be useful. Those users may prefer to focus on other categories of information in their reports, such as items that are missing.
To overcome these potential difficulties, when an inventory report includes out-of-order information that is erroneous or not desired, a method is provided whereby the RFID tags associated with items of interest are interrogated, then the data is placed in order according to their expected order (which may be referred to as an algorithm order), and then compared against the ordered list of items (or a list of items in algorithm order). This comparison enables a processor to determine which items that the RFID reader was expected to interrogate are missing, and which items that the RFID reader was not expected to interrogate (because a database indicates that they were not present) are present. The resulting lists of (unexpectedly) missing and (unexpectedly) present items, for example, are typically of a usable length, and accordingly, overcome the difficulties described above.
In this and other applications, the order may be conventional in relationship to the items about which information is being sought (such as the Dewey Decimal system or the Library of Congress system for library materials), or may be designated by the user. Any or all of the lists described may be saved in a database, which may reside in the memory of a computer associated with the RFID reader, or on a removable data storage medium associated with the RFID reader, or in memory associated with a separate computer or device. Alternatively, the information from the RFID tags may simply be collected, and may be placed in the desired order at a later time or by a different computer, or both, either before or after the information has been stored in a database.
One example of a method 30 of obtaining information related to items associated with RFID tags is illustrated in
5. Background Inventory
In another embodiment of the present invention, inventory may be conducted simultaneously with other operations of the RFID system. That is, it is known to conduct inventory of RFID-tagged items by interrogating the items for that purpose. In this embodiment of the present invention, inventory is conducted as a background operation of the RFID system, using data acquired for a different purpose. For example, a portable RFID reader may be used to interrogate items in a storage area to determine whether they are located in the proper order, location, or both, or whether they are present on a list of items in which the user is interested. This would be the primary purpose of the RFID interrogation, but the information obtained regarding those items may also be used to conduct inventory. That is, each RFID-tagged item that is interrogated to determine whether it is in the proper order relative to adjacent items is necessarily also present in the storage area, and thus an inventory database can be consulted and updated, as needed, to reflect the fact that the item is present. This background inventory operation may also be used with other RFID hardware, such as check-in/check-out devices, conversion stations (for converting items without RFID tags to items with RFID tags, the tags being associated with the items), or other such devices. In those instances, the primary operation may be to check an item into or out of a storage area, or to convert an item to an RFID-tagged item, but inventory (the secondary operation) can also be conducted in the background, perhaps to notify a user if the items presented for conversion are not presented in the expected order according to an order list of items.
Although inventory has been described above as the second operation, the same principles apply to other combinations of first and second operations. For example, when determining whether items are in the proper order (the first operation), an RFID reader may also search for items on a predetermined list of items (the second operation), such as items that are thought to be missing, damaged, on hold for a patron, or the like. Alternatively, when an RFID reader is used to interrogate RFID tags associated with items and assist a user in determining where the item belongs in a storage location (the first operation), the RFID reader may also search for items on a predetermined list of items, as described above. The various functions described as being a first operation or a second operation could be exchanged or coupled in any desired and appropriate manner, so that information gathered for one purpose is used for another purpose without the need for re-interrogating the RFID tags. Additional operations of the type described elsewhere herein could also be performed at the same time as the first and second operations, as desired.
One example of a method 40 of obtaining information related to items of interest associated with RFID tags s is illustrated in
6. Real Time Inventory Reconciliation
In a related embodiment of the invention, a portable RFID reader performs real-time inventory reconciliation. That is, the portable RFID reader reads the RFID tags of items located in a storage area, such as on a shelf, and then compares the list of items detected with the expected contents of the storage area based on data stored in an inventory database. An inventory database may be stored on a removable data storage device, such as a flash memory card, or may be stored in memory that is part of the portable RFID reader, or in a database that is accessible by a wireless connection or otherwise in real time. These inventory databases may be separate from a master inventory database that is stored on a central computer, network, or the like, which can be updated by the real-time database continuously or intermittently. Real time inventory information can be provided to a user regarding items that should have been found but were not, items that should not have been found but were, or other discrepancies between the actual inventory and the inventory reflected on the database. The status of an item could be updated based on the information obtained from the interrogation, and the new status could be stored in the inventory database. A particularly useful feature of real-time inventory is for the RFID reader to enable the user to confirm, during interrogation, that a particular item that was not found (but was expected to have been found) is missing from the storage area. If the user confirms that the item is missing, then the RFID reader can correct the inventory database to indicate that the item is missing (that is, not present). The reverse may also be useful—enabling the user to confirm that a particular item that was found but was thought to be missing is actually present, and thus to correct the inventory database. The corrected inventory database may be stored wherever the original inventory database was stored. This real-time reconciliation of inventory saves time, and thus is a useful feature in inventory work. A user interface, such as one associated with a display, may enable the user to create or edit database records for any items that were interrogated but not found on the database, by prompting the user to input data associated with any required or optional fields in the database. This feature may enable a user to correct incomplete records in the database in real time as well.
One example of a method 50 of reconciling an inventory list of items associated with RFID tags is illustrated in
7. Sorting a Random Set
In libraries and other storage areas, considerable effort can be expended returning items to a storage area after use. These items generally must be put back into the proper location. Often this is done by manually sorting the items onto a cart, then traversing the storage area, taking the ordered items from the cart and replacing them on, for example, the shelves of the storage area. Automated assistance for this task is the purpose of the following embodiment of the present invention. In this embodiment, a portable RFID reader can be used to read the RFID tags associated with each of a set of randomly placed items and display a list of those items according to a predetermined order. The order may be a standard order for organizing items of that type (such as the Dewey Decimal system or the Library of Congress system for organizing materials in a library), or a customized order. When the RFID reader interrogates the random set of RFID-tagged items, the reader can organize information about those items in order, and then display either a part of or all of the list of ordered items. The information displayed in the list could be information obtained from the interrogated RFID tags, information obtained from a database, or a combination thereof. The list could be used to place the items in a storage area in the proper order, as with reshelving a group of library materials in their appropriate locations, or for placing the items on a cart for transportation to a storage area. The invention facilitates the placement of the items on the cart in the desired order, to make replacement of the items on the storage area shelves more efficient.
One example of a method 60 of collecting data related to items associated with RFID tags is illustrated in
Since all the amendments are inserting new paragraphs or sections, a version marked up to show changes made to the specification relative to the previous version of the specification is not attached.
8. Altering the Permissible Error Tolerance
Some RFID readers are capable of simultaneously interrogating several RFID tags that are within the “read range” of the reader. It can be difficult to determine or resolve the exact relative positions of multiple RFID tags when those tags respond to the RFID reader substantially simultaneously, particularly when the RFID reader bypasses the items rapidly. However, a portable RFID reader can determine an approximate order of the items whose RFID tags are interrogated. When such an RFID reader is used to report storage area location order errors (“shelf order” errors) to a user, this approximate order is compared to an expected order. Because of the errors involved in approximating the shelf order of the items, false shelf order errors may be detected, which may provide an error report that is annoying, rather than useful, to the user. If the permissible error tolerance is increased to minimize the errors reported, then some detectable and significant errors may go unreported. The allowed error size could be described as order tolerance, or shelf order tolerance. This aspect of the present invention relates specifically to this potential problem.
The RFID reader and method of the present invention may be adapted to alter the error reporting algorithm, and specifically to alter the permissible error tolerance. The permissible error tolerance is the range of locations apart from an expected location for an item that the item is permitted by the algorithm to be, while still being considered to have been at the correct location. That is, the permissible error tolerance may be 1 location, so that an item that is 1 location removed from its expected location will be considered by the error reporting algorithm (and thus the RFID reader) to have been in the proper location. Any item that is more than 1 location removed from its expected location will be considered by the algorithm to have been out of position or mislocated. Altering the permissible error tolerance thus enables a user to increase or decrease the range of “acceptable” locations for an item. This alteration may be based on whether the items being interrogated are thin, medium, or thick. That is, the resolution of the RFID reader is normally sufficiently accurate to enable the reader to reliably detect the relative locations of thick items, such as encyclopedias, reference texts, and the like. In those cases, the user specifies that thick items are being interrogated, and the error detection algorithm is modified to classify as errors even small discrepancies between the detected position and the expected position. For thin items such as children's books or magazines, the RFID reader resolution may not be sufficient to accurately detect the relative positions of closely-spaced items. In those cases, the user specifies that thin items are being interrogated, and the error detection algorithm is modified to classify as errors only those errors that are sufficiently significant to be reliably attributable to misplacement rather than poor resolution. Although the designations “thin,” “medium,” and “thick” may be used, and may be useful because users understand those terms easily, it is of course possible to use numerical designations (for example, from 1 to 30) or other designations. If a numeric tolerance is used, the number could approximate the number of items per unit measure, such as the number of items per inch, centimeter, or foot. Thus the algorithm may be modified based on a characteristic of the items that is correlated to the proximity of RFID tags in adjacent items; typically the width of the items. The alteration of the permissible error tolerance may be made through a user interface, including a display (such as a touch panel display), buttons, or the like.
The variable resolution feature described above may also be done automatically, rather than by a user. That is, the RFID reader is normally moved past items at a certain “normal” rate during interrogation, which in the context of library materials may be approximately 2 items per second. The RFID reader may be programmed to infer that when items are being interrogated at more than the normal rate, the reader is moving past a greater number of thinner items (that is, the user is moving the reader past the items at approximately the same rate, but there are more items per unit length of the storage area). The reader may then dynamically adjust the error tolerance for misplaced items. For example, if the normal rate at which the RFID reader interrogates items is 2 items per second, and the RFID reader begins interrogating 5 items per second, then the RFID reader may change the error tolerance so that items that are within 2 positions on either side of the expected location (+/−2 positions) to +/−5positions. The reverse may also be true, so that if the interrogation rate is 1 item per second, then the error tolerance may be automatically changed from +/−2 positions to +/−1 position. The change in the error tolerance may be proportional to the change in interrogation rate, or directly proportional, or geometrically proportional, or otherwise variable based on the interrogation rate.
The foregoing embodiment of the invention may be difficult to implement if the RFID reader cannot reliably interrogate RFID tags at the faster interrogation rate, as suggested in the example. That is, some RFID readers may not be able to interrogate 5 items per second, and instead may continue to read 2 items per second and simply fail to interrogate the other 3 items successfully. In that and other instances, the resolution may still be varied by a user or automatically. This can be done by measuring the number of RFID tags simultaneously located within the “read range” of the RFID reader. For example, if the read range of the RFID reader were sufficient to detect tags within, say, a six-inch zone of a shelf, centered about the reader, then in a section of “normal” books, the RFID reader might simultaneously detect six RFID tags. In an area of “thin” items, the RFID reader might simultaneously detect 24 tags, or in an area of “thick” items, the RFID reader might simultaneously detect only 3 tags. Based on this measure, the RFID reader can automatically, through an algorithm, adjust its shelf order tolerance separately for each shelf. As with the previous embodiment, the adjustment can even be made dynamically as the shelf is scanned, so that a shelf that contains thin items on one end and thick items on the other end might be processed with different tolerances for different portions of the shelf In either case, the change in the error tolerance may be proportional to the number of tags simultaneously detected, or directly proportional, or geometrically proportional, or otherwise variable based on the measured number of tags.
9. Conversion of Non-RFID-Tagged Items to RFID-Tagged Items
An additional aspect of the present invention may be referred to for convenience as exception finding during conversion. Conversion, as that term has been used herein, refers generally to the process of converting non-RFID tagged items to RFID-tagged items. In one useful embodiment of a conversion station, the bar-code or other item identifier used on an item may be scanned or input into a processor, and the processor may use that information to create an RFID tag that will be associated with that item in a database. Other information, such as information in an existing database that is related to that item, may also be used in the RFID tag created for that item. That information may include, for example, the type of item, whether or not that item may be circulated, the archive or destruction date for the item, or other such information. The RFID tag may then be placed in or on the item, and the item processed as desired. Depending on how many items must be converted, the conversion process can be expensive, though generally well worth the attendant benefits.
One method of minimizing unnecessary expense in converting a collection of items to RFID-tagged items is the subject of this aspect of the invention. In this embodiment, the conversion station implements the additional step of determining whether the non-RFID-tagged item is on a list of items, or in a category of items, that should not be converted (or alternatively whether the item that may be converted is on a list of items, or in a category of items, that should be converted). That is, the person or entity that controls the collection of non-RFID tagged items may decide that certain items need not be converted, perhaps because the benefits of conversion do not justify the expense. This may be the case for older items, items that are infrequently or never used, items that are damaged, multiple copies of the same item, items with a short shelf life (such as periodicals) or the like. These types of items may either be listed individually based on information in an existing database, or may be listed by class (“items older than 5 years,” or “damaged items,” for example). When the conversion station receives data (by scanning a bar-code, optically reading characters, receiving data entered by an operator, or otherwise obtaining the data) identifying an item that has been presented to the conversion station for conversion, it determines whether the item has been identified as one not suitable for conversion (or alternatively, whether the item has not been identified as one that is suitable for conversion). If so, then the conversion station sends a signal indicative of that status. If not, then conversion can proceed. In this manner, only the minimum number of items need to be converted to RFID-tagged items, which results in a savings of both time and money, particularly for items that would otherwise be RFID-tagged and then discarded from the collection shortly thereafter.
In a specific embodiment of the invention described above, a database may be created of items (either specific items or characteristics of items that can be determined from the information known about those items) that the user does not wish to convert to RFID-tagged items. Alternatively, the database may be created exclusively of items (either specific items or characteristics of items that can be determined from the information known about those items) that the user does wish to convert to RFID-tagged items. In either case, this database may be transferred to (by download, or by upload from a removable data storage device) or otherwise made accessible to the conversion station, and then the information obtained from the non-RFID identification system associated with each item can be compared to the database to determine whether that item should be converted to an RFID-tagged item or not.
Other operations may also be performed in the course of converting non-RFID-tagged items to RFID-tagged items. For example, an inventory of items may be taken while those items are being converted, by comparing a list of items that were presented for conversion to a list of items that are indicated in a database as present. From that information, a list of presumptively missing items may be generated for a user. Another operation that can be performed during conversion is that of determining whether the items presented for conversion are in the proper, expected, or algorithm order. This is possible because during conversion, a user typically selects a first item from a storage area, such as a library shelf, presents that item to the conversion station, and then receives and applies an RFID tag that is associated with the item to the item. The user then replaces that item in the appropriate location in the storage area, and selects the next item. If the user converts items in order, then the order of the items presented may be compared either exactly (each item in its exact location) or approximately (each item within a specified number of locations relative to its expected location) to a list of items in an expected, proper, or algorithm order. The conversion station may then notify the user when items presented for conversion are not in the exact or approximate order.
10. List Matching and Storage
The '870 patent discloses an RFID reader which can be used to search for RFID-tagged items within a storage area, if information about the items of interest is provided to the RFID reader. If information about a grouping of such items of interest is initially provided to the RFID reader, such as a group or list name or other identifier, then the RFID reader can interrogate RFID-tagged items, determine whether the interrogated items match any item on the list, and if so, store information related to the matching item. For example, a list of items of interest can be provided to the RFID reader and given an identifier such as “missing items” to identify items that should be present in the storage area but which cannot currently be found. In this instance, if the RFID reader encounters and interrogates an RFID tag associated with an item in the storage area, and that tag contains information which matches an entry in the “missing items” list, the RFID reader could store information retrieved from or related to the interrogated RFID tag to a data collection category called “missing items” in a database. This data storage operation could be performed automatically, or after prompting the user of the RFID reader, and an inventory database may be updated either continuously or periodically with the information obtained. Lists of items, which may be referred to as “search lists,” may be for items that a user or customer wishes to locate and check out, or use, or destroy, or archive, or transfer, for example. Since finding such items of interest in the storage area is useful to users of this type of system, if such an automatic data collection capability were unavailable the user might need to retain the item for later processing, or might need to make special efforts to “manually” store information about this item using some type of data collection capability, as described earlier. Thus embodiment of the invention saves time and effort by the user of the RFID reader.
Number | Name | Date | Kind |
---|---|---|---|
3593291 | Carter | Jul 1971 | A |
3747086 | Peterson | Jul 1973 | A |
3750167 | Gehman et al. | Jul 1973 | A |
3752960 | Walton | Aug 1973 | A |
3790945 | Fearon | Feb 1974 | A |
3816708 | Walton | Jun 1974 | A |
3893099 | Zoepfl | Jul 1975 | A |
4063229 | Welsh et al. | Dec 1977 | A |
4141078 | Bridges, Jr. et al. | Feb 1979 | A |
4153931 | Green et al. | May 1979 | A |
4183027 | Ehrenspeck | Jan 1980 | A |
4219296 | Fujii et al. | Aug 1980 | A |
4223830 | Walton | Sep 1980 | A |
4312003 | Robbins, Jr. | Jan 1982 | A |
4319674 | Riggs et al. | Mar 1982 | A |
4376936 | Kott | Mar 1983 | A |
4407000 | Sasaki et al. | Sep 1983 | A |
4413254 | Pinneo et al. | Nov 1983 | A |
4442507 | Roesner | Apr 1984 | A |
4457016 | Pfeffer | Jun 1984 | A |
4471345 | Barrett, Jr. | Sep 1984 | A |
4476469 | Lander | Oct 1984 | A |
4578654 | Tait | Mar 1986 | A |
4580041 | Walton | Apr 1986 | A |
4583083 | Bogasky | Apr 1986 | A |
4598276 | Tait | Jul 1986 | A |
4636634 | Harper et al. | Jan 1987 | A |
4636950 | Casewll et al. | Jan 1987 | A |
4656463 | Anders et al. | Apr 1987 | A |
4656592 | Spaanenburg et al. | Apr 1987 | A |
4658357 | Carroll et al. | Apr 1987 | A |
4673932 | Ekchian et al. | Jun 1987 | A |
4676343 | Humble et al. | Jun 1987 | A |
4688026 | Scribner et al. | Aug 1987 | A |
4745401 | Montean | May 1988 | A |
4746830 | Holland | May 1988 | A |
4746908 | Montean | May 1988 | A |
4785308 | Newcomb | Nov 1988 | A |
4796074 | Roesner | Jan 1989 | A |
4805232 | Ma | Feb 1989 | A |
4814742 | Morita et al. | Mar 1989 | A |
4827395 | Anders et al. | May 1989 | A |
4829297 | Lig et al. | May 1989 | A |
4831363 | Wolf | May 1989 | A |
4835372 | Gombrich et al. | May 1989 | A |
4837568 | Snaper | Jun 1989 | A |
4850009 | Zook et al. | Jul 1989 | A |
4857893 | Carroll | Aug 1989 | A |
4862160 | Ekchian et al. | Aug 1989 | A |
4870391 | Cooper | Sep 1989 | A |
4873193 | Jensen et al. | Oct 1989 | A |
4879756 | Stevens et al. | Nov 1989 | A |
4881061 | Chambers | Nov 1989 | A |
4924210 | Matsui et al. | May 1990 | A |
4924219 | Sato | May 1990 | A |
4952928 | Carroll et al. | Aug 1990 | A |
4964053 | Humble | Oct 1990 | A |
4967185 | Montean | Oct 1990 | A |
4973086 | Donnelly et al. | Nov 1990 | A |
4975828 | Wishneusky et al. | Dec 1990 | A |
5008661 | Raj | Apr 1991 | A |
5019815 | Lemelson et al. | May 1991 | A |
5030807 | Landt et al. | Jul 1991 | A |
5036308 | Fockens | Jul 1991 | A |
5059951 | Kaltner | Oct 1991 | A |
5063380 | Wakura | Nov 1991 | A |
5072222 | Fockens | Dec 1991 | A |
5079740 | Patel et al. | Jan 1992 | A |
5083112 | Piotrowski et al. | Jan 1992 | A |
5095362 | Roesner | Mar 1992 | A |
5099226 | Andrews | Mar 1992 | A |
5099227 | Geiszler et al. | Mar 1992 | A |
5103222 | Hogen Esch et al. | Apr 1992 | A |
5119070 | Matsumoto et al. | Jun 1992 | A |
5124699 | Tervoert et al. | Jun 1992 | A |
5151684 | Johnsen | Sep 1992 | A |
5153842 | Dlugos, Sr. et al. | Oct 1992 | A |
5164985 | Nysen et al. | Nov 1992 | A |
5204526 | Yamashita et al. | Apr 1993 | A |
5204670 | Stinton | Apr 1993 | A |
5214409 | Beigel | May 1993 | A |
5214410 | Verster | May 1993 | A |
5218343 | Stobbe et al. | Jun 1993 | A |
5218344 | Ricketts | Jun 1993 | A |
5218466 | Brooks | Jun 1993 | A |
5231273 | Caswell et al. | Jul 1993 | A |
5239167 | Kipp | Aug 1993 | A |
5253162 | Hassett et al. | Oct 1993 | A |
5260690 | Mann et al. | Nov 1993 | A |
5276431 | Piccoli et al. | Jan 1994 | A |
5280159 | Schultz et al. | Jan 1994 | A |
5287414 | Foster | Feb 1994 | A |
5288980 | Patel et al. | Feb 1994 | A |
5290066 | Mody | Mar 1994 | A |
5294781 | Takahashi et al. | Mar 1994 | A |
5296722 | Potash et al. | Mar 1994 | A |
5317309 | Vercellotti et al. | May 1994 | A |
5327115 | Swierczek | Jul 1994 | A |
5331313 | Koning | Jul 1994 | A |
5334822 | Sanford | Aug 1994 | A |
5339073 | Dodd et al. | Aug 1994 | A |
5339074 | Shindley et al. | Aug 1994 | A |
5347263 | Carroll et al. | Sep 1994 | A |
5347280 | Schuermann | Sep 1994 | A |
5353011 | Wheeler et al. | Oct 1994 | A |
5360967 | Perkin et al. | Nov 1994 | A |
5369699 | Page et al. | Nov 1994 | A |
5378880 | Eberhardt | Jan 1995 | A |
5382784 | Eberhardt | Jan 1995 | A |
5389919 | Warren et al. | Feb 1995 | A |
5392028 | Pichl | Feb 1995 | A |
5401584 | Minasy et al. | Mar 1995 | A |
5406263 | Tuttle | Apr 1995 | A |
5407851 | Roesner | Apr 1995 | A |
5420757 | Eberhardt et al. | May 1995 | A |
5424858 | Gillotte | Jun 1995 | A |
5426284 | Doyle | Jun 1995 | A |
5427640 | Daniels | Jun 1995 | A |
5430441 | Bickley et al. | Jul 1995 | A |
5432864 | Lu et al. | Jul 1995 | A |
5434775 | Sims et al. | Jul 1995 | A |
5444223 | Blama | Aug 1995 | A |
5446447 | Carney et al. | Aug 1995 | A |
5448110 | Tuttle et al. | Sep 1995 | A |
5448220 | Levy | Sep 1995 | A |
5448242 | Sharpe et al. | Sep 1995 | A |
5450070 | Massar et al. | Sep 1995 | A |
5450492 | Hook et al. | Sep 1995 | A |
5455410 | Schneider | Oct 1995 | A |
5459657 | Wynn et al. | Oct 1995 | A |
5461390 | Hoshen | Oct 1995 | A |
5469363 | Saliga | Nov 1995 | A |
5471203 | Sasaki et al. | Nov 1995 | A |
5477202 | Zarembo et al. | Dec 1995 | A |
5477215 | Mandelbaum | Dec 1995 | A |
5477863 | Grant | Dec 1995 | A |
5489908 | Orthmann et al. | Feb 1996 | A |
5490079 | Sharpe et al. | Feb 1996 | A |
5493392 | Cramer et al. | Feb 1996 | A |
5497140 | Tuttle | Mar 1996 | A |
5499017 | Beigel | Mar 1996 | A |
5500651 | Schuermann | Mar 1996 | A |
5517195 | Narlow et al. | May 1996 | A |
5519381 | Marsh et al. | May 1996 | A |
5521601 | Kandlur et al. | May 1996 | A |
5528222 | Moskowitz et al. | Jun 1996 | A |
5528251 | Frein | Jun 1996 | A |
5537105 | Marsh et al. | Jul 1996 | A |
5539193 | Gibbs et al. | Jul 1996 | A |
5539394 | Cato et al. | Jul 1996 | A |
5539775 | Tuttle et al. | Jul 1996 | A |
5541585 | Duhame et al. | Jul 1996 | A |
5541604 | Meier | Jul 1996 | A |
5550547 | Chan et al. | Aug 1996 | A |
5554974 | Brady et al. | Sep 1996 | A |
5565846 | Geiszler et al. | Oct 1996 | A |
5565858 | Guthrie | Oct 1996 | A |
5573611 | Koch et al. | Nov 1996 | A |
5574372 | Moritz et al. | Nov 1996 | A |
5581707 | Keucken | Dec 1996 | A |
5589820 | Robinson et al. | Dec 1996 | A |
5602527 | Suenaga | Feb 1997 | A |
5602538 | Orthmann et al. | Feb 1997 | A |
5604486 | Lauro et al. | Feb 1997 | A |
5610596 | Petitclerc | Mar 1997 | A |
5613228 | Tuttle et al. | Mar 1997 | A |
5616906 | Kumar | Apr 1997 | A |
5625341 | Giles et al. | Apr 1997 | A |
5629981 | Nerlikar | May 1997 | A |
5633678 | Parulski et al. | May 1997 | A |
5635693 | Benson et al. | Jun 1997 | A |
5635906 | Joseph | Jun 1997 | A |
5635917 | Todman | Jun 1997 | A |
5640002 | Ruppert et al. | Jun 1997 | A |
5646592 | Tuttle | Jul 1997 | A |
5648765 | Cresap et al. | Jul 1997 | A |
5651548 | French et al. | Jul 1997 | A |
5661473 | Paschal | Aug 1997 | A |
5668803 | Tymes et al. | Sep 1997 | A |
5673037 | Cesar et al. | Sep 1997 | A |
5682142 | Loosmore et al. | Oct 1997 | A |
5682143 | Brady et al. | Oct 1997 | A |
5686902 | Reis et al. | Nov 1997 | A |
5689238 | Cannon, Jr. et al. | Nov 1997 | A |
5689239 | Turner et al. | Nov 1997 | A |
5691724 | Aker et al. | Nov 1997 | A |
5694139 | Saito et al. | Dec 1997 | A |
5705818 | Kelbel et al. | Jan 1998 | A |
5708423 | Ghaffari et al. | Jan 1998 | A |
5717867 | Wynn et al. | Feb 1998 | A |
5729697 | Schkolnick et al. | Mar 1998 | A |
5739765 | Stanfield et al. | Apr 1998 | A |
5745036 | Clare | Apr 1998 | A |
5751221 | Stanfield et al. | May 1998 | A |
5751257 | Sutherland | May 1998 | A |
5768140 | Swartz et al. | Jun 1998 | A |
5769051 | Bayron et al. | Jun 1998 | A |
5771003 | Seymour | Jun 1998 | A |
5777884 | Belka et al. | Jul 1998 | A |
5780305 | Chisum | Jul 1998 | A |
5785181 | Quartararo, Jr. | Jul 1998 | A |
5786764 | Engellenner | Jul 1998 | A |
5793305 | Turner et al. | Aug 1998 | A |
5794213 | Markman | Aug 1998 | A |
5798693 | Engellenner | Aug 1998 | A |
5799302 | Johnson et al. | Aug 1998 | A |
5804810 | Woolley et al. | Sep 1998 | A |
5805065 | Schwarz et al. | Sep 1998 | A |
5808558 | Meek et al. | Sep 1998 | A |
5814797 | Rifkin | Sep 1998 | A |
5821513 | O'Hagan et al. | Oct 1998 | A |
5822714 | Cato | Oct 1998 | A |
5831533 | Kanno | Nov 1998 | A |
5842118 | Wood, Jr. | Nov 1998 | A |
5844523 | Brennan et al. | Dec 1998 | A |
5850187 | Carrender et al. | Dec 1998 | A |
5859587 | Alicot et al. | Jan 1999 | A |
5886634 | Muhme | Mar 1999 | A |
5887176 | Griffith et al. | Mar 1999 | A |
5907522 | Teodoridis et al. | May 1999 | A |
5920053 | DeBrouse | Jul 1999 | A |
5920261 | Hughes et al. | Jul 1999 | A |
5923001 | Morris et al. | Jul 1999 | A |
5929780 | Pagnol et al. | Jul 1999 | A |
5929801 | Aslanidis et al. | Jul 1999 | A |
5936527 | Isaacman et al. | Aug 1999 | A |
5938727 | Ikeda | Aug 1999 | A |
5939984 | Brady et al. | Aug 1999 | A |
5955951 | Wischerop et al. | Sep 1999 | A |
5959568 | Woolley | Sep 1999 | A |
5963134 | Bowers et al. | Oct 1999 | A |
5991742 | Tran | Nov 1999 | A |
5995017 | Marsh et al. | Nov 1999 | A |
6002344 | Bandy et al. | Dec 1999 | A |
6025780 | Bowers et al. | Feb 2000 | A |
6032127 | Schkolnick et al. | Feb 2000 | A |
6037879 | Tuttle | Mar 2000 | A |
6056199 | Wiklof et al. | May 2000 | A |
6057756 | Engellenner | May 2000 | A |
6074156 | Frich | Jun 2000 | A |
6075441 | Maloney | Jun 2000 | A |
6078251 | Landt et al. | Jun 2000 | A |
6078258 | Auerbach et al. | Jun 2000 | A |
6079890 | Gross et al. | Jun 2000 | A |
6084528 | Beach et al. | Jul 2000 | A |
6085907 | Hochmeister et al. | Jul 2000 | A |
6097301 | Tuttle | Aug 2000 | A |
6100804 | Bardy et al. | Aug 2000 | A |
6104311 | Lastinger | Aug 2000 | A |
6104333 | Wood, Jr. | Aug 2000 | A |
6107920 | Eberhardt et al. | Aug 2000 | A |
6127928 | Issacman et al. | Oct 2000 | A |
6137411 | Tyren | Oct 2000 | A |
6137928 | Issacman et al. | Oct 2000 | A |
6141649 | Bull | Oct 2000 | A |
6142375 | Belka et al. | Nov 2000 | A |
6148291 | Radican | Nov 2000 | A |
6150921 | Werb et al. | Nov 2000 | A |
6150948 | Watkins | Nov 2000 | A |
6154137 | Goff et al. | Nov 2000 | A |
D435557 | Eisenberg et al. | Dec 2000 | S |
6169483 | Ghaffari et al. | Jan 2001 | B1 |
6172608 | Cole | Jan 2001 | B1 |
6173900 | Yoshigi et al. | Jan 2001 | B1 |
6176425 | Harrison et al. | Jan 2001 | B1 |
6182053 | Rauber et al. | Jan 2001 | B1 |
6185165 | Jesionowski et al. | Feb 2001 | B1 |
6195006 | Bowers et al. | Feb 2001 | B1 |
6201474 | Brady et al. | Mar 2001 | B1 |
6203262 | Frich et al. | Mar 2001 | B1 |
6204764 | Maloney | Mar 2001 | B1 |
6218942 | Vega et al. | Apr 2001 | B1 |
6232870 | Garber et al. | May 2001 | B1 |
6232876 | Maloney | May 2001 | B1 |
6240091 | Ginzboorg et al. | May 2001 | B1 |
6244512 | Koenck et al. | Jun 2001 | B1 |
6260049 | Fitzgerald et al. | Jul 2001 | B1 |
6261247 | Ishikawa et al. | Jul 2001 | B1 |
6269572 | Forsythe et al. | Aug 2001 | B1 |
6317028 | Valiulis | Nov 2001 | B1 |
6318636 | Reynolds et al. | Nov 2001 | B1 |
6324437 | Frankel et al. | Nov 2001 | B1 |
6330971 | Mabry et al. | Dec 2001 | B1 |
6335686 | Goff et al. | Jan 2002 | B1 |
6338149 | Ciccone, Jr. et al. | Jan 2002 | B1 |
6342839 | Curkendall et al. | Jan 2002 | B1 |
6343695 | Petrick et al. | Feb 2002 | B1 |
6354493 | Mon | Mar 2002 | B1 |
6362738 | Vega | Mar 2002 | B1 |
6369709 | Larson et al. | Apr 2002 | B1 |
6400997 | Rapp, III | Jun 2002 | B1 |
6407669 | Brown et al. | Jun 2002 | B1 |
6411211 | Boley et al. | Jun 2002 | B1 |
6422457 | Frich et al. | Jul 2002 | B1 |
6424262 | Garber et al. | Jul 2002 | B2 |
6448886 | Garber et al. | Sep 2002 | B2 |
6456239 | Werb et al. | Sep 2002 | B1 |
6480100 | Frieden | Nov 2002 | B1 |
6486780 | Garber et al. | Nov 2002 | B1 |
6496806 | Horwitz et al. | Dec 2002 | B1 |
6535129 | Petrick | Mar 2003 | B1 |
6538623 | Pamian et al. | Mar 2003 | B1 |
6570492 | Peratoner | May 2003 | B1 |
6600418 | Francis et al. | Jul 2003 | B2 |
6600420 | Goff et al. | Jul 2003 | B2 |
6608551 | Anderson et al. | Aug 2003 | B1 |
6614721 | Bokhour | Sep 2003 | B2 |
6646554 | Goff et al. | Nov 2003 | B1 |
6704690 | Koh et al. | Mar 2004 | B2 |
6714121 | Moore | Mar 2004 | B1 |
6744367 | Forster | Jun 2004 | B1 |
6749116 | Massaro | Jun 2004 | B2 |
6753830 | Gelbman | Jun 2004 | B2 |
6774782 | Runyon et al. | Aug 2004 | B2 |
6819222 | Lin et al. | Nov 2004 | B2 |
6888509 | Atherton | May 2005 | B2 |
6934718 | Davidsson | Aug 2005 | B2 |
7044373 | Garber et al. | May 2006 | B1 |
7069100 | Monette et al. | Jun 2006 | B2 |
7270268 | Garber et al. | Sep 2007 | B2 |
20010000019 | Bowers et al. | Mar 2001 | A1 |
20010000958 | Ulrich et al. | May 2001 | A1 |
20010008390 | Berquist et al. | Jul 2001 | A1 |
20020008621 | Barritz et al. | Jan 2002 | A1 |
20020041234 | Kuzma et al. | Apr 2002 | A1 |
20020064776 | Liu | May 2002 | A1 |
20020070862 | Francis et al. | Jun 2002 | A1 |
20020083025 | Robarts et al. | Jun 2002 | A1 |
20020104013 | Ghazarian | Aug 2002 | A1 |
20020111819 | Li et al. | Aug 2002 | A1 |
20020113707 | Grunes et al. | Aug 2002 | A1 |
20020167406 | Garber et al. | Nov 2002 | A1 |
20020185532 | Berquist et al. | Dec 2002 | A1 |
20020188702 | Short, III et al. | Dec 2002 | A1 |
20020190862 | Berquist et al. | Dec 2002 | A1 |
20020194208 | Knoll et al. | Dec 2002 | A1 |
20020196126 | Eisenberg et al. | Dec 2002 | A1 |
20030018534 | Zack et al. | Jan 2003 | A1 |
20030206107 | Goff et al. | Nov 2003 | A1 |
Number | Date | Country |
---|---|---|
2003-244560 | Oct 2003 | AU |
2 205 213 | Nov 1997 | CA |
1265215 | Aug 2000 | CN |
1293732 | May 2001 | CN |
1315027 | Sep 2001 | CN |
43 19 878 | Dec 1993 | DE |
44 15 801 | Sep 1994 | DE |
43 41 880 | Jun 1995 | DE |
198 56 762 | May 2000 | DE |
198 56 763 | Jun 2000 | DE |
19844631 | Jun 2000 | DE |
200 13 622 | Jul 2000 | DE |
19921748 | Nov 2000 | DE |
199 21 748 | Nov 2003 | DE |
0 301 127 | Feb 1989 | EP |
0357309 | Mar 1990 | EP |
0 494 114 | Jul 1992 | EP |
0 526 038 | Feb 1993 | EP |
0 585 132 | Mar 1994 | EP |
0 598 624 | May 1994 | EP |
0 615 285 | Sep 1994 | EP |
0 637 093 | Feb 1995 | EP |
0 689 151 | Dec 1995 | EP |
0 689 161 | Dec 1995 | EP |
0 702 323 | Mar 1996 | EP |
0 710 853 | May 1996 | EP |
0 740 262 | Oct 1996 | EP |
0740262 | Oct 1996 | EP |
0 747 990 | Dec 1996 | EP |
0 762 535 | Mar 1997 | EP |
0 794 507 | Sep 1997 | EP |
0794507 | Sep 1997 | EP |
0 794 507 | Nov 1997 | EP |
0 805 507 | Nov 1997 | EP |
0 810 567 | Dec 1997 | EP |
0 825 672 | Feb 1998 | EP |
0 944 085 | Sep 1999 | EP |
0997842 | May 2000 | EP |
1 033 675 | Sep 2000 | EP |
1 139 278 | Oct 2001 | EP |
2 555 339 | May 1985 | FR |
2 701 146 | Aug 1994 | FR |
2 098 768 | Nov 1982 | GB |
2 186 467 | Aug 1987 | GB |
2 204 162 | Nov 1988 | GB |
2 204 162 | Nov 1988 | GB |
2 257 278 | Jan 1993 | GB |
2288299 | Nov 1995 | GB |
2 306 726 | May 1997 | GB |
2308947 | Jul 1997 | GB |
56-110193 | Sep 1981 | JP |
2-301893 | Dec 1990 | JP |
04047995 | Feb 1992 | JP |
4-255090 | Sep 1992 | JP |
5-20404 | Jan 1993 | JP |
5-55160 | Mar 1993 | JP |
5-266267 | Oct 1993 | JP |
05-336034 | Dec 1993 | JP |
6-84024 | Mar 1994 | JP |
7-13325 | Mar 1995 | JP |
7-110874 | Apr 1995 | JP |
7-150835 | Jun 1995 | JP |
07254092 | Oct 1995 | JP |
7-325870 | Dec 1995 | JP |
8-55160 | Feb 1996 | JP |
8054462 | Feb 1996 | JP |
8-108911 | Apr 1996 | JP |
8-153172 | Jun 1996 | JP |
8-180152 | Jul 1996 | JP |
10-024686 | Jan 1998 | JP |
10-181261 | Jul 1998 | JP |
63-200909 | Dec 1998 | JP |
11-39522 | Feb 1999 | JP |
2000306188 | Nov 2000 | JP |
2001-028510 | Jan 2001 | JP |
2001-31218 | Feb 2001 | JP |
2001-216546 | Aug 2001 | JP |
2001-229263 | Aug 2001 | JP |
9400091 | Sep 1995 | NL |
8904016 | May 1989 | WO |
WO 8904016 | May 1989 | WO |
9005968 | May 1990 | WO |
9422580 | Oct 1994 | WO |
9512870 | May 1995 | WO |
9641296 | Dec 1996 | WO |
9715031 | Apr 1997 | WO |
9729464 | Aug 1997 | WO |
9736270 | Oct 1997 | WO |
9750057 | Dec 1997 | WO |
WO 9749972 | Dec 1997 | WO |
9813800 | Apr 1998 | WO |
9813804 | Apr 1998 | WO |
9813805 | Apr 1998 | WO |
9816070 | Apr 1998 | WO |
9816849 | Apr 1998 | WO |
WO 9813800 | Apr 1998 | WO |
9827670 | Jun 1998 | WO |
WO 9835327 | Aug 1998 | WO |
9858238 | Dec 1998 | WO |
9859258 | Dec 1998 | WO |
9905659 | Feb 1999 | WO |
9905660 | Feb 1999 | WO |
WO 9905660 | Feb 1999 | WO |
9910839 | Mar 1999 | WO |
9964974 | Dec 1999 | WO |
9965006 | Dec 1999 | WO |
0010112 | Feb 2000 | WO |
0010144 | Feb 2000 | WO |
WO 0010122 | Feb 2000 | WO |
WO 0010144 | Feb 2000 | WO |
0016280 | Mar 2000 | WO |
0043805 | Jul 2000 | WO |
0065532 | Nov 2000 | WO |
0077704 | Dec 2000 | WO |
0103058 | Jan 2001 | WO |
0126048 | Apr 2001 | WO |
0152179 | Jul 2001 | WO |
0157807 | Aug 2001 | WO |
0190849 | Nov 2001 | WO |
02073512 | Sep 2002 | WO |
WO 02099715 | Dec 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20020185532 A1 | Dec 2002 | US |