Patent Application
20090237221
Data storage devices are employed in computer, audio, and video fields for storing large volumes of information for subsequent retrieval and use. Data storage devices include data storage tape cartridges, hard disk drives, micro disk drives, business card drives, and removable memory storage devices in general. The data storage devices are useful for storing data and for backing up data systems used by businesses and government entities. For example, businesses routinely back up important information such as human resource data, employment data, compliance audits, and safety/inspection data. Government sources collect and store vast amounts of data related to tax payer identification numbers, income withholding statements, and audit information. Congress has provided additional motivation for many publicly traded companies to ensure the safe retention of data and records related to government required audits and reviews after passage of the Sarbanes-Oxley Act (Pub. L. 107-204, 116 Stat. 745 (2002)).
Collecting and storing data has now become a routine good-business practice. The data is often saved to one or more data storage devices that is/are typically shipped or transferred to an offsite repository for safe/secure storage. The backup data storage devices are periodically retrieved from the offsite repository for review. The transit of data storage devices between various facilities introduces a possible risk of loss or theft of the devices and the data stored that is stored on the devices.
The issue of physical data security and provenance is a growing concern for users of data storage devices. Thus, manufacturers and users both are interested in systems and/or processes for keeping track of in-transit/in-storage data storage devices. Improvements to the tracing of data storage devices used to store data are desired by a wide segment of both the public and private business sectors.
One aspect provides a label programming system configured to initialize a radiofrequency (RF)-enabled label for attachment to a data storage device. The label programming system includes a platform, an RF read/write assembly disposed on a first side of the platform, and an optical reader assembly in electrical communication with the RF read/write assembly. The optical reader assembly is disposed on a second side of the platform opposite the first side. The optical reader assembly is configured to optically read information from the RF-enabled label and communicate the information to the RF read/write assembly that is configured to write the information to a chip of the RF-enabled label.
Another aspect provides a label programming system configured to initialize a label for attachment to a data storage device. The system includes a platform, an RF read/write assembly disposed on a first side of the platform, and an optical reader assembly in electrical communication with the RF read/write assembly. The platform includes a first shield and a second shield spaced from the first shield by a gap. The optical reader assembly is disposed on a second side of the platform opposite the first side. The optical reader assembly is configured to optically read information from an RF-enabled label presented in the gap and communicate the information to the RF read/write assembly that is configured to write the information to a chip of the RF-enabled label.
Another aspect provides a method of initializing a label for attachment to a data storage device. The method includes providing an array of radiofrequency (RF)-enabled labels. The method additionally includes optically reading information from one row or one column of the array of RF-enabled labels, and shielding all but the one row or column of the RF-enabled labels that was optically read. The method ultimately includes radiofrequency writing the optically read information to a chip in each RF-enabled label in the row or column of the RF-enabled labels that was not shielded.
The accompanying drawings are included to provide a further understanding of embodiments and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments and together with the description serve to explain principles of embodiments. Other embodiments and many of the intended advantages of embodiments will be readily appreciated as they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts.
In the following Detailed Description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. In this regard, directional terminology, such as “top,” “bottom,” “front,” “back,” “leading,” “trailing,” etc., is used with reference to the orientation of the Figure(s) being described. Because components of embodiments can be positioned in a number of different orientations, the directional terminology is used for purposes of illustration and is in no way limiting. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims.
It is to be understood that the features of the various exemplary embodiments described herein may be combined with each other, unless specifically noted otherwise.
Embodiments provide a label programming system that is configured to initialize a radiofrequency (RF)-enabled label for attachment to a data storage device. Embodiments of the system offer a turn-key solution for entities to trace and track the movement of data storage devices within and between physical locations.
Embodiments provide a label programming system configured to scan a barcode of a label that is attachable to a data storage device and convert and write the scanned information onto a chip of an RF-enabled inlay embedded within the label. Embodiments provide a label programming system enabled to verify/read RFID-enabled tags and ensure that the information written to the chip matches the barcode printed on the label prior to attaching the label to the data storage device. In one embodiment, the label programming system includes ultra high frequency (UHF) read/write components suited to UHF initialize RF-enabled labels.
In one embodiment, optical reader assembly 50 includes a pair of bases 52a, 52b each coupled to a respective one of the guides 48a, 48b, a U-arm 54 (e.g., an arch 54) coupled to the bases 52a, 52b, and a pair of optical scanners 56a, 56b secured to the arch 54. The arch 54 is elevated above the work surface 46 and is configured to enable a sheet of RF-enabled labels to traverse beneath the optical scanners 56a, 56b. In one embodiment, the optical scanners 56a, 56b are in electrical communication with the RF read/write assembly 42 via electrical cables 58, and the programmer 24 communicates with the controller 28 to individually initialize each label of the sheet of RF-enabled labels. Suitable optical scanners include one of the MS-series of scanners available from MICROSCAN, Renton, Wash. Other suitable optical scanners are also acceptable.
In one embodiment, an optional belt system 59 is provided to direct a sheet of RF-enable labels across the work surface 46. The belt system includes gears 61 and a belt 63 engaged over the gears 61. The belt is configured to ride over the platform 44 and move a sheet of labels along the work surface 46. Other means for moving a sheet of labels are also acceptable, including manually indexing the sheet or a pinch roller system suited to move the sheet carrying the labels.
The RF read/write assembly 42 includes a first reader/writer 70 electrically coupled to an RF multiplexer 80 having cables 74, 84 extending to RF antennas 72, 82, respectively. In one embodiment, the cables 74, 84 include ferrite cores 75, 85, respectively, disposed around the coaxial cables. The ferrite shielded cores 75, 85 of cables 74, 84 are configured to isolate the antennas 72, 82 from electrical disturbances from the reader 70 and other electronics, thus improving the reliability of the label programmer 24. In addition, the ferrite shielded cores 75, 85 of cables 74, 84 also isolate antennas 72, 82 from each other, thus reducing misreads. A signal converter 90 is disposed within the housing 40 and provides a universal serial bus port adapter.
In one embodiment, the RF reader/writer 70 includes SkyeTek SkyeModule M9 ultra high frequency (UHF) RFID reader available from SkyeTek, Westminster, Colo. In one embodiment, the RF antennas 72, 82 include ultra high frequency RF antennas identified as SIRIT part number H1483-351 antennas having an area of about 0.5 inch by 3 inches. Other suitable antennas include “miniature” patch antennas with impedance matching elements, zigzag monopole or dipole antennas, coiled monopole or dipole antennas, a Fractus FR05-S1-R-0-105 antenna, an Antenova 1020B5812-01 antenna, or a Tyco Electronics series 1513165 antenna, and other antennas having an operating frequency near 900 MHz.
Label programmer 24 also includes a power supply, a motor controller for the belt system 59 motor, interface cables, and USB, power jacks, and a belt position sensor suitably wired in a manner that those with skill in the art will understand.
In one embodiment, the first shield 100 includes a panel 110 that defines a leading end 112 and a trailing end 114 and includes a metal foil 116 extending between the leading end 112 and the trailing end 114. In one embodiment, the second shield 102 includes a panel 120 defining a leading end 122 opposite a trailing end 124 and a metal foil 126 extending between leading end 122 and trailing end 124. In one embodiment, the trailing ends 114, 124 each include an optional insulator 118, 128 disposed over the respective metal foils 116, 126 to minimize the possibility of electrical contact between a user and metallic (i.e., conductive) portions the trailing ends 114, 124. Suitable panels 110, 120 include plastic panels about 0.125 inches thick, although other panels of other thicknesses are also acceptable.
The antennas 72, 82 aligned in the gap G are positioned in a line-of-sight of the optical scanners 56a, 56b. In this manner, one or more RF-enabled tags traversing the gap G are aligned with the optical scanners 56a, 56b and the antennas 72, 82, such that the RF reader/writer 70 is enabled to read/write only to those tags that are in line with the optical scanners 56a, 56b. Moving a series of tags over the gap G results in one row of tags being positioned between the antennas 72, 82 and the RF reader/writer 70. In one embodiment, the work surface 46 (
In one embodiment, the gap G between the first shield 100 and the second shield 102 is adjustably maintained by an optional divider 104 coupled between the shields 100, 102.
It is desirable that the platform 44 be configured to prevent RF read/writing to tags that are not within the line-of-sight of the antennas 72, 82 (
In one embodiment, the divider 104 includes a first tab 130 and a flange 132 extending from the first tab 130, and a second tab 140 and a second flange 142 extending from the tab 140. The first flange 132 is coupled to the second flange 142 such that the divider 104 defines the gap distance G between the first shield 100 and the second shield 102. In one embodiment, the first flange 132 is slideably coupled to the second flange 142 such that the divider 104 is adjustable to enable adjustment of the gap G.
In one embodiment, the divider 104 is conductive and serves to further isolate the two sides 100, 102 of platform 44. For example, one embodiment provides the first tab 130 electrically coupled to the metal foil 116 of the first shield 100 by a conductor 134, and the second tab 140 electrically coupled to the metal foil 126 of the second shield 102 by a conductor 144. The conductors 134, 144 electrically couple to the shields 100, 102 to minimize the radiation of undesirable fields to the antennas 72, 82. The conductors 134, 144 include electrically conducting adhesive tape, although other forms of electrically coupling the metal foil 116, 126 to the divider 104 are also acceptable.
In alternative embodiments each of the first and second shields 100, 102 include a ferrite plate, or each of the first and second shields includes a carbon-filled foam plate. Other forms of shields 100, 102 configured to selectively impede the radiofrequency transmission between the antennas 72, 82 and labels that are not present in the gap G are also acceptable.
In one embodiment, the label antenna 174 is an ultra high frequency (UHF) antenna that is integrated within the chip 176 and the inlay 170. Other forms of the label antenna 174 are also acceptable. In general, the label antenna 174 is configured to electromagnetically interact with the RF reader/writer 70 (
In one embodiment, the chip 176 is a memory chip capable of recording and/or storing device information, such as a format of data stored on a storage device and a VOLSER number associated with the device. In one embodiment, the memory of the chip 176 stores the data that is visually present on the printed superstrate 172 in addition to other information such as whether the label 162 is affixed to a container of devices, or whether the label 162 is affixed to a data storage device, or other tracking related information.
In one embodiment, the VOLSER number is a unique value that is specific to each data storage device it is associated with. In this specification, unique means an item exists as the only one such item. Thus, in one embodiment the VOLSER number specific to each data storage device identifies one and only one such data storage device, and there are no other data storage devices having that VOLSER number. This is in contrast to retail inventories having product labels, where any one label is employed to identify multiple items, such as any one of three dozen long sleeved shirts, or any one of seven cases of wine, and the sale or transaction of a shirt or one or more bottles of wine updates the number of shirts or bottles of wine still in inventory.
The chip 176 is preferably an electronic RFID chip including memory, where the memory has at least the capacity to be written with device information. In one embodiment, the chip 176 is an electronic memory chip capable of retaining stored data even in a power “off” condition, and is, for example, an RFID chip with memory available from, for example, NXP, Eindhoven, The Netherlands. In another embodiment, the chip 176 is an Alien RF-enabled chip available from Alien Technology, Morgan Hill, Calif. Those with skill in the art of memory chips will recognize that other memory formats and sizes for the chip 176 are also acceptable.
The superstrate 172 includes a first optical field 178 and a barcode field 180. In one embodiment, at least one of the information field 178 and the barcode field 180 includes multiple bits of data encoded to include alphanumeric identifiers encoded in ASCII and configured to identify a data storage device to which the label 162 is attachable, container information indicating the label 162 is attached to a data storage device or affixed to a container of data storage devices, and other information useful in tracking data storage devices.
The chip 176 is programmed to have a specific content and format for the information stored in memory. In one embodiment, the chip 176 electronically stores all of the data printed on the superstrate 172 including the fields described above and additional tracking data not visually evident on the superstrate 172. Many chips have a check value used to check data transmission accuracy. Some chips 176 have password protection. Chips 176 used in other applications have hardware encryption.
The VOLSER number can be user-defined or assigned by a manufacturer according to specifications provided by a customer. In general, the VOLSER number includes a character within the 80 bit field to mark the end of the VOLSER number, which enables the reading and interpretation of variable length and/or unique VOLSER numbers. In one embodiment, the bit pattern of the VOLSER number is not encrypted when reading or writing the VOLSER number to enable easy decoding by an outside source, such as a customer or client. In other embodiments, the VOLSER number is encrypted in software before sending to the label (for example, by inverting the bits, or by a more complex encryption such as a variation of Data Encryption Standard (DES) or Advanced Encryption Standard (AES)) to prevent decoding by an outside source, or encoded to save space in the memory of the chip 82.
In one embodiment, a check value is computed, transmitted, and stored with the data sent to the label. A check value is a small, fixed number of bits that can be employed to detect errors after transmission or storage of data. For example, in one embodiment the check value is computed and appended before transmission or storage, and verified afterwards by a recipient to confirm that no changes occurred on transmission of the data. Advantages of check values are that they are easily implemented, they can be analyzed mathematically, and are useful in detecting common errors caused by noise in transmission channels. (For example, a cyclic redundancy check (CRC) such as CRC 8 ATM, or CRC 16, or CRC 32 IEEE 802.3.)
In other embodiments, a parity check or other function may be employed to generate the check value for the data. A parity check usually refers to a check value that is the exclusive-or of the data being checked.
The label programming system 20 including the label programmer 24 that is employed to read the information from the fields 178, 180 of the superstrate 172 and communicate the optically read information to the RF read/write assembly 42 that writes the information to the chip 176 as described below in
In one embodiment, the user types in the expected first number (a start number) and a last number (an expected end number) in each column of the labels 162 in the array 160. This is a useful option if the scanning process is expected to be interrupted, and/or if the operator is handling multiple arrays 160 of labels 162.
In one embodiment, the fields 210, 212 (
In one embodiment, the system 20 includes an auto verify feature that verifies initialization of initialized labels without having the operator initiate a second pass of the labels through the programmer. Other embodiments provide for one-pass label initialization and verification of label initialization. One exemplary flow chart includes:
Embodiments provide a label programming system configured to scan a barcode of a label that is attachable to a data storage device and convert and UHF write the scanned information onto a chip of an RF-enabled inlay embedded within the label. Other embodiments provide a label programming system enabled to verify RFID-enabled tags by verifying that the information written to the chip matches the barcode printed on the label prior to attaching the label to the data storage device.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the specific embodiments of a label programmer, a label programming system, and method of initializing radiofrequency (RF)-enabled labels for attachment to a data storage device as discussed herein. Therefore, it is intended that this invention be limited only by the claims and the equivalents thereof.
