Memory device activation and deactivation

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to, claims the earliest available effective filing date(s) from (e.g., claims earliest available priority dates for other than provisional patent applications; claims benefits under 35 USC §119(e) for provisional patent applications), and incorporates by reference in its entirety all subject matter of the following listed application(s) (the “Related Applications”) to the extent such subject matter is not inconsistent herewith; the present application also claims the earliest available effective filing date(s) from, and also incorporates by reference in its entirety all subject matter of any and all parent, grandparent, great-grandparent, etc. applications of the Related Application(s) to the extent such subject matter is not inconsistent herewith. The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation or continuation in part. The present applicant entity has provided below a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant entity understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization such as “continuation” or “continuation-in-part.” Notwithstanding the foregoing, applicant entity understands that the USPTO's computer programs have certain data entry requirements, and hence applicant entity is designating the present application as a continuation in part of its parent applications, but expressly points out that such designations are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).

RELATED APPLICATIONS

1. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of currently United States patent application entitled METHOD AND SYSTEM FOR FLUID MEDIATED DISK ACTIVATION AND DEACTIVATION, naming Bran Ferren, Eleanor V. Goodall, and Edward K. Y. Jung as inventors, U.S. Ser. No. 11/124,924, filed May 9, 2005.

2. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of currently United States patent application entitled FLUID MEDIATED DISK ACTIVATION AND DEACTIVATION MECHANISMS, naming Bran Ferren, Eleanor V. Goodall, and Edward K. Y. Jung as inventors, U.S. Ser. No. 11/124,923, filed May 9, 2005.

3. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of currently United States patent application entitled ROTATION RESPONSIVE DISK ACTIVATION AND DEACTIVATION MECHANISMS, naming Bran Ferren, Edward K. Y. Jung, and Clarence T. Tegreene as inventors, U.S. Ser. No. 11/150,823 filed Jun. 9, 2005.

4. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of currently United States patent application entitled METHOD AND SYSTEM FOR ROTATIONAL CONTROL OF DATA STORAGE DEVICES, naming Bran Ferren, Edward K. Y. Jung, and Clarence T. Tegreene as inventors, U.S. Ser. No. 11/150,837 filed Jun. 9, 2005.

5. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation in part of currently United States patent application entitled LIMITED USE MEMORY DEVICE WITH ASSOCIATED INFORMATION, naming Bran Ferren and Edward K. Y. Jung as inventors, U.S. Ser. No. 11/198,938, filed contemporaneously herewith.

BACKGROUND

Various methods have been used to control access to information stored on data storage devices such as CDs, DVDs, floppy disks, and so forth. Methods of controlling access to information are utilized for various reasons including, for example, to limit unauthorized access to copyrighted information. Such methods may involve requiring the use of access codes provided, e.g., on data storage device packaging in order to read information from a data storage device, or erasing data or preventing reading of data from a data storage device following reading of the device.

SUMMARY

Embodiments of devices, methods and systems relating to retrieval of information from deactivated, expired or disabled memory or data storage devices are disclosed. Features of various embodiments will be apparent from the following detailed description and associated drawings.

BRIEF DESCRIPTION OF THE FIGURES

Features of the invention are set forth in the appended claims. The exemplary embodiments may best be understood by making reference to the following description taken in conjunction with the accompanying drawings. In the figures, like referenced numerals identify like elements.

FIG. 1 is a block diagram of a system including a data storage device;

FIG. 2 illustrates a computer system;

FIG. 3 illustrates a disk including stored machine readable data and index information;

FIG. 4 illustrates a disk including stored machine readable data and key information;

FIG. 5 is a schematic diagram of an embodiment of a system for activation of a deactivated data storage device;

FIG. 6 is a schematic diagram of another embodiment of a system for activation of a deactivated data storage device;

FIG. 7 is a flow diagram of a process including retrieval of read support information;

FIG. 8 is a schematic diagram illustrating exemplary processes for reading data from a data storage device;

FIG. 9A illustrates an original set of machine readable data;

FIGS. 9B-9H illustrate different degraded forms of the machine readable data depicted in FIG. 9A;

FIG. 10A depicts in schematic form data stored in a data storage medium on a substrate;

FIG. 10B depicts the embodiment of FIG. 10A following degradation of the substrate;

FIG. 10C depicts the embodiment of FIG. 10A following degradation of the data;

FIG. 10D depicts the embodiment of FIG. 10A following degradation of the data storage medium;

FIG. 11 illustrates a data storage device with read support information;

FIG. 12 illustrates a data storage device with degraded read support information;

FIG. 13 illustrates a data storage device with partially degraded read support information;

FIG. 14 illustrates a data storage device with partially degraded read support information;

FIG. 15A illustrates a data storage device including primary and second read support information;

FIG. 15B illustrates the device of FIG. 15A following degradation of the primary read support information;

FIG. 16 depicts a data storage device including read support information dispersed in the data of interest;

FIG. 17 is a flow diagram of a method of retrieving information from a deactivated memory device;

FIG. 18 depicts a further exemplary method of retrieving information from a deactivated memory device;

FIG. 19 depicts another exemplary method of retrieving information from a deactivated memory device;

FIG. 20 depicts another exemplary method of retrieving information from a deactivated memory device;

FIG. 21 depicts an embodiment of a method of reactivating a deactivated memory device, including variations thereof;

FIG. 22 is a flow diagram of a method of retrieving data from an expired limited use memory device;

FIG. 23 depicts a further embodiment of a method of retrieving data from an expired limited use memory device;

FIG. 24 depicts another embodiment of a method of retrieving data from an expired limited use memory device;

FIG. 25 is a flow diagram of an embodiment of a method of manufacturing a limited use memory device;

FIG. 26 is a flow diagram of a further embodiment of a method of manufacturing a limited use memory device;

FIG. 27 is a flow diagram of a further embodiment of a method of manufacturing a limited use memory device;

FIG. 28 depicts an example of multiple batches of data storage devices and associated data storage device identification codes;

FIG. 29 depicts a further variant of a method of manufacturing a limited use memory device;

FIG. 30 depicts another variant of a method of manufacturing a limited use memory device;

FIG. 31 is a flow diagram of a method of manufacturing a limited use memory device, including variants thereof;

FIG. 32 is a flow diagram of an exemplary method of configuring a limited use memory device; and

FIG. 33 is a flow diagram showing variants of a method of configuring a limited use memory device.

DETAILED DESCRIPTION

Data storage devices may be used to store a wide variety of types of data of interest including audio data files, video data files, and software code, to name only a few examples. In some cases, it may be desired to permit reading of data from a data storage device for a limited period of time or for a limited number of uses or reads of the device. Such cases arise, for example, when a copyright holder wishes to limit access to copyrighted data, e.g. to permit software to be installed on a limited number of computer systems, or to permit a ‘rented’ movie to be viewed over the course of a few days and not longer. Limiting number of reads or duration of access to information may be of utility in various other applications as well, including, but not limited to, the distribution of information that is confidential or information that is valid for only a limited period of time. As used herein, the term “data of interest” refers to some portion of the data stored on a data storage device that is of interest with regard to controlling access to the data. It is not intended that the data of interest must include all data on the data storage device that might be of use or of interest to a user of the data storage device. In some embodiments, the data of interest may include all or the majority of useable data on the data storage device, while in others it may include only a subset of the useable data on the data storage device. In some embodiments, the data of interest may include selected modules of computer program code, or selected portions of a video or audio recording, so that access to certain portions of the program, video, or audio recording (for example) may be restricted, while other portions may remain accessible, or become accessible.

In some cases it may be desirable to provide the user of a data storage device the possibility of regaining access to information on the data storage device after deactivation of the data storage device. According to various embodiments as exemplified herein, methods, systems and devices are provided for retrieving information from degraded or deactivated data storage devices. Examples of data storage devices that may be usable for a limited number of uses (or reads) or for a limited period of time and subsequently modified, degraded or deactivated to destroy or render inaccessible or unusable some or all data on the data storage device are disclosed and described in U.S. patent application Ser. No. 11/124,924, filed May 9, 2005, entitled METHOD AND SYSTEM FOR FLUID MEDIATED DISK ACTIVATION AND DEACTIVATION; U.S. patent application Ser. No. 11/124,923, filed May 9, 2005, entitled FLUID MEDIATED DISK ACTIVATION AND DEACTIVATION MECHANISMS; U.S. patent application Ser. No. 11/150,823 filed Jun. 9, 2005, entitled ROTATION RESPONSIVE DISK ACTIVATION AND DEACTIVATION MECHANISMS; and U.S. patent application Ser. No. 11/150,837, filed Jun. 9, 2005, entitled METHOD AND SYSTEM FOR ROTATIONAL CONTROL OF DATA STORAGE DEVICES, to which the present application claims priority, and which are incorporated herein by reference in their entirety, and U.S. Pat. Nos. 6,011,772; 6,228,440; 6,709,802; 6,780,564; 6,838,144; 6,839,316; all of which are incorporated herein by reference in their entirety.

FIG. 1 illustrates a system 10, which may be a computer system or other system that includes a read device 12 adapted for reading machine readable data from data storage device 14. Data storage device 14 may include a modifiable or degradable portion 17 that prior to degradation or modification contains information that supports reading of information from a portion of data storage device 14. As will be discussed herein, and as discussed in various references incorporated herein by reference, data storage devices according to various embodiments may include features that render at least portions of the data storage device degradable under certain conditions. In addition to computers, exemplary embodiments of systems that may include read devices for reading data from a data storage device included DVD players, CD players, card readers, and various special purpose devices for reading any sort of image, audio, text, software, or other data from a data storage device. System 10 may include a processor 16, system memory 18, one or more I/O devices 20, and data bus 22. Data and control signals may be transferred between system components via data bus 22. System memory 18 may include read-only memory (ROM) 24 and random access memory (RAM) 26. During use, device driver software 30 may be stored in RAM 26. System 10 may also include a power supply, not shown. Processor 16 may be a microprocessor, for example. Data storage device 14 may be a CD, DVD, floppy disk, smart card, magnetic stripe card, magnetic tape, or any of various other data storage devices capable of storing machine readable data. In this and other embodiments, data storage devices may take the form of disks, cards, or microchips, for example. System 10 may include a read device interface 32 operatively connected between read device 12 and system bus 22.

FIG. 2 depicts a specific example of a system as depicted in FIG. 1. FIG. 2 illustrates a computer system 50. Computer system 50 may include a microprocessor 52, system memory 54, system bus 56, output device 58, and input device 60. In this example output device 58 is a monitor. One or multiple output devices of other types may be used in various embodiments, including but not limited to speakers, printers, data storage devices, and audio, video, or tactile displays of various types. Similarly, input device 60 in the present example is a keyboard, but other types of input devices, including but not limited to, computer mice, track balls, touch screens, microphones, scanners, may be used instead, either singly or in combination. System memory 54 includes read-only memory 62 and random-access memory 64. Device driver 66 may be stored in random-access memory 64. Device driver 66 is used to control disc drive 70. Interface 72 provides an interface between the computer system 50 and disk drive 70. Control line 74 and data line 76 provide for the transfer of control and data signals between system 50 and disk drive 70. Disk drive 70 includes receptacle 78, which is adapted to receive disk 80. Disc 80 is rotated by motor 82. Positioner 84 adjusts the position of the read head 86 with respect to disk 80.

Systems for reading data from such data storage devices may include general-purpose computing devices and other systems having the capability of reading data from data storage devices. Such features may include, for example, hardware or software that cause light of a particular intensity or wavelength to be directed to a particular region of a data storage device when it is in the read device, cause the data storage device to be subjected to a spin of a specified intensity or duration by the read device, or cause the data storage device to be exposed to a particular electrical field or magnetic field strength. In some embodiments, the data storage device (e.g., disk 80) may be configured so that it will be modified or inactivated following a selected number of uses. In some embodiments, components of system 50 may operate in a conventional manner. In other embodiments, selected components of system 50 may include features that are specialized to produce modification or degradation of the data storage device. For example, if a portion of disk 80 is degraded by exposure to high intensity light, disk drive 70 may be modified to direct high intensity light onto an appropriate portion of disk 80 to cause deactivation of disk 80. System 50 may be modified at the level of drive 70, drive interface 72, or program code 66 residing in RAM 64. Drive 70 or drive interface 72 may be modified at the hardware, firmware, or software level. Program code 66 may be system software or application program software. System 50 may be configured to detect prior activation of a rotation activatable mechanism on data storage device 80 based upon detection of a modification to data storage device 80. Modifications to data storage device 80 associated with prior activation may be detected by various means. If the modification includes modification of data or modification of accessibility of a particular portion of data, the modification may be detected when an attempt is made to read data from data storage device 80, e.g. by failure of reading. Such modifications may be manifested as modifications of data or accessibility of data, but are not limited to modification of data or data accessibility. In some embodiments, modifications may be detectable by optical, electrical, magnetic, or other means, and the presence of the modification may serve as an instruction to the system to discontinue reading of the disk, or to operate in a specified manner (e.g., by increasing the speed of rotation of the disk, delivering light to a selected region of the disk, etc.). Combinations of data read devices and data storage devices that may be used to produce data storage device deactivation are described, for example, in U.S. Pat. Nos. 6,011,772; 6,228,440; 6,709,802; 6,744,551; 6,780,564; 6,838,144; 6,839,316; FIG. 3 depicts an exemplary data storage device.

As depicted in FIG. 3, data of interest (which might be, for example, a computer program or an audio or video digital recording) may be distributed to multiple locations on data storage device 100 (which in this example is depicted as a disk, but which may take other forms, as well). In order to retrieve the data of interest in usable form, it may be from the appropriate location in the appropriate order, as specified by index information stored in index region 102. In the present exemplary embodiment, index region 102 may specify that data may be read from first data region 104, second data region 106, third data region 108, fourth data region 110, fifth data region 112 and sixth data region 114, in that sequence. Thus, in order to render the data stored in first through sixth data regions 104 through 114 unusable, it may be sufficient to render data stored in index region 102 inaccessible, even though the data contained in data segments 104, 106, 108, 110, 112, and 114 may still be intact and otherwise readable. Therefore, according to certain embodiments, a data storage device deactivated in this way can be ‘reactivated’ by providing the index information from another source.

A further exemplary data storage device is depicted in FIG. 4. In FIG. 4, a data storage device 150 may include data of interest in data region 152 stored in encrypted or encoded form, and key information stored in key region 154. Key information stored in key region 154 is used to decode or decrypt data of interest stored in data region 152. As described in connection with the embodiment shown in FIG. 3, if key information in key region 154 is destroyed, modified, or rendered inaccessible, the data of interest contained in data region 152 may be rendered inaccessible even though the data is still intact and readable. Thus, a data storage device deactivated in this way can be ‘reactivated’ by providing the data read device with key information from another source.

Both index information used in the embodiment of FIG. 3 and key information used in the embodiment of FIG. 4 may be classified generally as ‘read-support information’. Other forms of ordering, encoding, encrypting or otherwise structuring data so that it is readable only with the use of some form of read-support information may be used in various embodiments as disclosed herein, and the term read-support information is not intended to be limited only to key and index information as illustrated in FIGS. 3 and 4. Methods of encoding or encrypting data are known or may be developed by those of skill in the relevant arts, and the embodiments described herein are not limited to use with any particular data indexing, encoding or encryption scheme.

FIG. 5 is a schematic diagram of an embodiment of a system 158 for activation of a data storage device 160. System 158 includes read device containing system 168 (which may be, for example, a computer system, a DVD player, a CD player, or various other system that include a read device capable of reading data from a data storage device) and remote system 170. Data storage device 160 includes data storage device identification code 162, data of interest 164, and, prior to modification of the device (e.g., in connection with use of the device), read support information 166. Read device containing system 168 makes use of read support information 166 on data storage device 160 to read data of interest 164 from data storage device 160. Following degradation or modification of data storage device 160, in which read support information 166 is degraded, modified, or otherwise rendered inaccessible, data of interest 164 remains intact but cannot be read (or cannot be read in a useful format) from data storage device 160. According to use of system 158, read device containing system 168 may send a request to remote system 170, the request including at least data storage device identification code 162. The data storage device identification code 162 is matched to a device ID code 172 with remote system 170, and a corresponding override code 173 is identified. The override code is then provided to read device containing system 168 by remote system 170. Device ID code 172 and override code 173 are associated, linked, or correlated with each other in remote system 170. Remote system 170 may be a hardware and/or software based system, and the request and override code may be transmitted between read device containing system 168 and remote system 170 in electronic format, via a wireless transmission, or via other methods for machine communication. Transfer of request and the override code may be performed in an automated fashion under hardware or software control, or under the direction of a user of a read device containing system 168. The override code may contain any data or information sufficient to override the deactivation of data storage device 160 to enable reading of data of interest 164 from data storage device 160. Override code 173 may include read support information necessary to permit data to be read from a deactivated memory or data storage device. Override code 173 may be a backup copy of some or all of read support information 166. In some embodiments, override code 173 may be an analog of read support information 166, i.e., it may be functionally equivalent to read support information 166 with regard to enabling reading of data of interest from data storage device 160, but it may not be exactly the same as read support information 166. Remote system 170 may be at a location distinct from read device containing system 168. In some embodiments, remote system 170 may be operated by a third party or service provider.

FIG. 6 is a schematic diagram of another embodiment of a system for activation of a deactivated data storage device 160. In the embodiment of FIG. 6, as in the embodiment of FIG. 5, data storage device 160 is used in connection with read device containing system 168. Similarly, a remote system 170 includes linked or associated device ID 172 and override code 173. In the embodiment of FIG. 6, however, communication between read device containing system 168 and remote system 170 is performed via user 174 of data storage device 160 and a human operator 175 of remote system 170. Communication between user 174 and operator 175 may be carried out in-person, via telephone, e-mail, or by various other forms of human communication as are well-known or as may be developed in the future. User 174 may be the usual user (e.g. the owner or licensee) of data storage device 160, or user 174 may be a representative of the usual user of data storage device 160, including, but not limited to, an employee of a service shop. Operator 175 may be an employee of a service shop, an employee or contractor of the seller of the data storage device or data stored on the data storage device, for example. Remote system 170 may be a computer-based system, in which operator 175 may access an override code stored in a machine readable format accessible to remote system 170. Alternatively, remote system 170 may include various other systems for storing an override code 173 in association with a device ID code 172, including, for example alphanumeric codes stored in a table printed on a sheet of paper in a format readable by operator 175.

Either an automated system including remote system 170, as shown in FIG. 5, or a system that includes a human intermediary, as shown in FIG. 6, may be considered a support entity. Accessing of read support information may be handled automatically by the system reading the data and thus be transparent to the user of the system unless the device is deactivated to prevent reading of data.

FIG. 7 is a flow diagram of a process including retrieval of read support information. The process of FIG. 7 may occur at the initial reading of data from a data storage device, or subsequent to reading of some or all of the data from the data storage device. At step 177, data is read from the data storage medium. At step 178 at least a portion of data on the data storage medium is degraded. It is presumed that the degraded data portion includes read support information needed for decoding data that is encoded, encrypted, or ordered in some manner. Step 178 may take place subsequent to, at the same time as, or at least in part prior to reading of data from the data storage medium in step 177. A data decoding step is performed at 179. At decision point 180, the quality of the data reading is assessed. If a good read of data has been obtained, flow control moves to step 184, and the process ends. If a good read of data has not been obtained, flow control moves to decision point 181, and it is determined whether recovery of read support information is permitted. If recovery of read support information is not permitted, the read fails and the process ends. If however, recovery of read support information is permitted, read-support information may be recovered at step 182, and if a information retrieval is determined to be satisfactory (at step 183) process control returns to step 179, and data is decoded utilizing the retrieved read support information. Whether or not recovery of read support information is permitted may depend on the particular data storage device and surrounding circumstances. For example, if the data storage device contains a movie to be viewed or a music recording that has expired following a certain number/duration of uses, permission to recover read support information (e.g., from a support entity) may be contingent on verification of payment of an additional rental/subscription fee. If the data storage device contains confidential information, permission to recover read support information after a limited use period has expired may be granted to a user who provided an appropriate security password or the like. These are only a few of many possible examples.

FIG. 8 is a schematic diagram illustrating exemplary systems and processes for reading data from a data storage device. A read device containing system is indicated generally by reference number 1399, and may be a system including hardware, firmware, and software. An application program may transmit read request 1402 to operating system 1404, which transmits read request 1410 to device driver 1408. Alternately, application program 1400 may send a read request 1406 directly to device driver 1048. Device driver 1408 then submits read request 1412 to device interface 1414, which subsequently submits read request 1416 to data storage device reader 1418. Read requests may be in optical, electrical, or other formats and generated and transmitted through the use of hardware, firmware, software, and combinations thereof. In response to read request 1416, data storage device reader 1418 may send a probe signal 1420 (e.g., on optical interrogation signal) to data storage device 1422. Data storage device reader 1418 then reads data from data storage device 1422. In some embodiments, data storage device reader 1418 may transmit a degradation signal 1426 (which could be an electrical, magnetic, optical, or other signal) designed to produce or initiate degradation of some or all of the data stored in data storage device 1422. Data signals 1424, 1426, 1428, and 1430 may be transmitted to data storage device reader 1418, device interface 1414, device driver 1408, and finally to application program 1400. Alternatively, a data signal 1432 may be transmitted from device driver 1408 to operating system 1404 and then be transmitted to application program 1400 as data signal 1434. At some point between data storage device 1422 and the final recipient of the data (e.g. application program 1400 or operating system 1404), encoded data 1436 may be sent to data decoding module 1438, where it may be decoded with the use of read support information 1437. Prior to deactivation of data storage device 1422, read support information 1437 may be read from data storage device 1422. Following deactivation of data storage device 1422, read support information may 1437 may not be obtainable from data storage device 1422. In such cases, a request 1442 may be sent to data recovery module 1444, which may include software, hardware, or firmware components of the data storage device reading system. Data recovery module 1444 may retrieve an override code as described previously, by sending a request 1446 to a user 1448, who then sends a request 1450 to a support entity 1452. In some embodiments, requests may be transmitted directly to support entity 1452 without user 1448 as intermediary. In other embodiments, a request 1460 may be transmitted to special purpose data retrieval hardware/software 1462, that may be adapted to retrieve read support information directly from a degraded or modified data storage device. An override code 1454 may be transmitted to user 1448 and then to data recovery module 1444 (at reference number 1456). Retrieved read support information 1464 may be transmitted back to data recovery module 1444. In other embodiments, suitable for cases where a secondary copy or read support information is stored on data storage device 1422, a request 1466 may be sent from data recovery module 1444 to a secondary key retrieval module 1468 configured to retrieve a secondary copy of read support information from data storage device 1422, where it may be stored in a secondary location. Data decoding operations may be handled at the hardware or software level in read device containing system 1399. Recovered read support information 1458 is transmitted from data recovery module 1444 to data decoding module 1438, where it may be used in reading or decoding of data.

Degrading or otherwise rendering inaccessible portions of data on a data storage device may be performed by various methods, the choice of which may be based on the particular data storage device and read device used. In various embodiments described herein, data storage devices may contain machine readable data. Machine readable data is commonly stored in a binary code, which may be stored in various data storage media capable of existing in at least two different states for binary encoding. For example, data may be stored in patterns of electrical potentials, magnetized regions, optically transmissive regions, or optically reflective regions, among others, as known or as may be devised by those of skill in the relevant arts. In some embodiments, data storage media capable of existing in more than two states may be used, and encoding schemes other than binary code may be used. Examples of data storage media include optical and magnetic data storage media, as are well known for use in CDs or DVDs, and floppy disks and magnetic tapes.

In some embodiments of data storage devices suitable for use in methods and systems described herein, a data storage medium may be carried on a substrate. The substrate may be a structure or layer that underlies or supports the data storage medium, or a structure or layer that overlies or coats the data storage medium. The substrate may provide structural stability or protect the data storage medium. In some embodiments, the substrate material may be interspersed with or formed integrally with the data storage medium. As used herein, the term substrate refers to a material that does not itself store the data, but performs a structural or protective function relative to the data storage medium. Data stored in the data storage medium may be read through the substrate in some embodiments of data storage devices, for example, by an interrogating light beam shining through a substrate layer of an optical disk to read data from the disk. A degradation-sensitive region of a data storage device may include any portion of the data storage device that may be modified in some way to render information stored in the region inaccessible or unusable in some way. ‘Degradation’ may include modification of data stored in a data storage medium, as well as modification or damage to the substrate or data storage medium.

FIGS. 9A-9H illustrate a number of exemplary forms of degradation of data. FIG. 9A depicts an exemplary portion of data stored in a binary format, as represented by data string 200. A first state of a data storage medium may be represented by a ‘1’, while a second state may be represented by a ‘0’ in data string 200. Degradation of data may include setting all data values to a ‘0’, as represented by data string 202 in FIG. 9B, or setting all data values to a ‘1’, as represented by data string 204 in FIG. 9C. Degradation of data may include resetting data values to random values or to some pattern (e.g., alternating ‘1’s and ‘0’s) as represented by data string 206 in FIG. 9D. In each of the examples shown in FIGS. 9B-9D, the data strings contain readable data values, but the data values are not ‘correct’, i.e., the read data values do not match the original data values. In other embodiments, following degradation, data may no longer be readable. As depicted in FIG. 9E, in some embodiments it may be the case that no data can be read at all, e.g., an attempt to read data produces a signal that cannot be recognized as either a ‘1’ or a ‘0’. In other embodiments, partial data degradation may be obtained. Reduced signal-to-noise ratio, as shown in FIG. 9F may be considered a form of partial data degradation; the data is present but accompanied by a higher than usual level of noise. Partial degradation may also include the case where a portion of machine readable data in the second data portion is unreadable. FIG. 9G depicts an example in which data string 212 is partially degraded. First data portion 214 and third data portion 218 contain the original data values, but in second data portion 216, all data values have been set to ‘0’. FIG. 9H depicts another example of partial data degradation in data string 220. In FIG. 9H, first data portion 222 and third data portion 226 contain original data values, but no data values can be read at all from second data portion 224.

FIGS. 9A-9H illustrate different forms of data degradation that may be manifested in data read from a data storage device by a read device. FIGS. 10A-10D illustrate how different forms of data degradation may be obtained. FIG. 10A is a cross-sectional view of a portion of a data storage device 250, including substrate 252, data storage medium 254, and digital data 256 stored in data storage medium 254. Data storage medium 254 may be a material that can exist in two different states, one of which is represented by the black rectangles, and the other of which is represented by the shaded portion of data storage medium 254. Deactivation of a data storage device may include destruction or modification of the data storage medium so that no data may be stored therein, modification of data stored in a data storage medium, destruction or modification of a substrate or coating located adjacent or near a data storage medium considered to include destruction or modification of data, as shown in various examples herein, or various other modifications to the data storage device that in some way render data inaccessible. FIGS. 10B-10D illustrate possible modifications to data, data storage media, and substrate that may produce the different forms of degradation illustrated in FIGS. 9B-9H.

In FIG. 10B, data storage medium 254 and stored data 256 are unmodified, but the substrate has been changed to a modified form 252′, which prevents reading of stored data 256. For example, if data is read optically, with the use of light transmitted through a transparent substrate, reading of data may be blocked, for example, by modifying or degrading substrate 256 to block or hinder transmission of light through the substrate. Examples of such mechanisms are described, for example, in U.S. Pat. Nos. 6,839,316, 6,780,564, and 6,709,802, which are incorporated herein by reference. Modification of substrate 252′ may completely block reading of data, as depicted generally in FIG. 9E, or may produce a reduced signal-to-noise ratio as depicted in FIG. 9F. Depending on the particular read system used, a modified substrate may lead to reading of data that are interpreted as all ‘0’s or all ‘1’s, as depicted in FIGS. 9B and 9C, respectively.

In FIG. 10C, substrate 252 and data storage medium 254 are unmodified, but data stored in data storage medium 254 is changed to modified form 256′, so that the data storage medium contains data values that differ from the originally stored data 256 as shown in FIG. 10A are. Data may be modified by writing or erasing of data, as is known in the art. The data modification represented in FIG. 10C could lead to complete or partial data ‘degradation’, as depicted in FIG. 9B, 9C, 9D, or 9G.

FIG. 10D depicts a portion of data storage device 250 including substrate 252, and data storage medium 254′, which has been modified so that it is no longer capable of storing data. Data storage 254′ may be modified or degraded in various ways, depending upon the type of data storage medium. This may produce data degradation as depicted in FIG. 9E, for example.

Machine readable data may be degradable by exposure to one of light, heat, moisture, chemicals, an electrical field, or a magnetic field, or it may be degradable by exposure to a combination of at least two of light, heat, moisture, chemicals, mechanical damage, an electrical field, or a magnetic field. In some embodiments, machine readable data may be degradable in response to a single reading of the memory device, while in other embodiments, it may be degradable in response to between about one and about 10 readings of the memory device. In still other embodiments, machine readable data may be degradable by other numbers of readings of the memory device, and the numbers of readings specified herein are merely exemplary, rather than limiting. The machine readable data may be stored in a data storage medium that includes at least one of a magneto-optic material, a thermo-optic material, or an electro-optic material. In some embodiments, machine readable data may be stored in a data storage medium that includes at least one of a photochromic dye, a photopolymer, or a photorefractive ferroelectric material.

The substrate of the memory device may take various forms, for example the substrate may be a disk shaped substrate, a card, or microchip, for example. In some embodiments, the substrate may include a rigid material, while in others it may include a flexible material.

All or portions of data on a data storage device may be rendered inaccessible by degrading a subset of data on the data storage device that contains information necessary for reading data stored on other parts of the data storage device. In embodiments as exemplified in FIGS. 3 and 4, modification or destruction of portions of a data storage device containing index or key information may render data of interest stored in other portions of the data storage device inaccessible or unreadable. Degradation of the data storage medium may include one or more of destruction of the data storage medium, modification of the data storage medium, modification of data stored in the data storage medium, and modification of signal-to-noise ratio of data stored in the data storage medium. Degradation may take place directly in response to a degradation inducing influence, or it may be initiated by a degradation inducing influence but continue to completion after removal of the degradation inducing influence. This may be the case, for example, if the degradation inducing influence provides input of an activation energy sufficient to overcome an energetic barrier and set off a chemical process that proceeds without further input of energy once initiated. A degradation inducing influence may produce degradation directly, or may function as an intermediary to enable or initiate action by a direct degradation inducing influence. Degradation may include various combinations of two or more degradation mechanisms, and in some embodiments may be produced by synergistic or cooperative effects of two or more degradation inducing or producing factors or influences. Examples of modifiable features include, but are not limited to, mechanical properties, optical properties, electrical properties, magnetic properties, or chemical properties.

Degradation of the substrate may include a change in a material property of the substrate or a change in shape or conformation of the substrate material, such as thickness or surface texture. Material properties may include optical properties such as reflectivity, index of refraction, transmissivity, light scattering, electrical properties, magnetic properties, and so forth. Modifications to material properties, shape, or conformation may be caused by a phase change, chemical reaction, melting, etching, corrosion, etc. of the substrate material due to exposure to a degradation inducing influence. Examples of degradation inducing influences or factors include, for example, heat, light, other forms of electromagnetic radiation, pressure, a magnetic field, or an electrical field.

FIG. 11 depicts a data storage device 300 containing machine readable data that may include a first data portion that is non-degradable by a limited number of readings, and a second data portion that is degradable by the limited number of readings, the second data portion comprising read-support information necessary for reading data of interest from the first data portion, the memory device having associated therewith a copy or analog of the read-support information retained by a third party. The first data portion contains stored data of interest 302 having and second data portion 304 containing read support information 306. Read support information 306 may be index information, key information, or other types of information needed to support reading of data of interest 302. Region 304 containing read support information 306 may be a degradation-sensitive region. The override code may include a full copy of the read-support information, as depicted in FIG. 11, which may be used to enable reading of data of interest 302 from first data portion 300. Deactivation of the memory device may include degradation of the degradation-sensitive region. For example, the degradation-sensitive region may be degraded by exposure to a degradation-inducing influence to render the data of interest inaccessible to a user of the memory device. Data storage device 300 may also include device identification code 308. Device identification code 308 may be stored in a machine readable format that can be read by a device used to read data from data storage device 300. Alternatively, device identification code 308 may be in a machine readable format that is readable by a different reader, of the same or different type. For example, device identification code 308 may be readable by an optical reader, a magnetic reader, or various other readers. Device identification code 308 may be stored an electronic, magnetic or optical format, as found on magnetic or optical data storage media, or an optically readable format such as a bar code, for example. In some embodiments, a device identification code may be a human-readable code that may be read by a human user of the device, for example an alphanumeric code printed or embossed on data storage device 300 directly or on a label affixed to data storage device 300. FIG. 11 also depicts a data storage location 310 that is distinct from data storage device 300, in which is stored data storage device identification code 312. Data storage device identification code 312 contains the same information as data storage device identification code 308. Data storage device identification code 312 may be stored in the same or a different format than data storage device identification code 308. For example, data storage device identification code 312 may be stored in an electronic, optical, or magnetic machine-readable format, or it may be stored in a human-readable format (for example, an alphanumeric code printed on a sheet of paper). Override code 314 may be stored in data storage location 310 in association with data storage device identification code 312.

FIG. 12 depicts data storage device 300 following degradation of second data portion 304. Stored data of interest 302 is retained, but read support information is fully degraded (degraded read support information is indicated by reference number 318). A backup copy of read support information 314 is stored in data storage location 310 and associated with data storage device 300 by means of data storage device identification code 312 stored in data storage location 310. Following deactivation (e.g., by degradation of second data portion 304), data storage device 300 may be reactivated by retrieving read support information 314 from data storage location 310 according to a method as depicted in FIGS. 8 and 9.

In some embodiments, as illustrated in FIG. 13, override code 322 may include a portion of the read-support information from second data portion 304. FIG. 13 depicts data storage device 300 as shown in FIG. 11 following a degradation process that left partial read support information 320 in second data portion 304. Data storage location 310 includes data storage device identification code 312 which matches data storage device identification code 308 on data storage device 300, as before. Data storage location 310 includes override code 322 that includes a portion of read support information. For example, the portion of the read support information may supplement information that can be read from the data storage device to enable reading of data of interest from the data storage device. Alternatively, the original read support information may include redundancies such that an override code that includes only a portion of the read support information may contain sufficient information to enable reading of data of interest.

As illustrated in FIG. 14, in some embodiments data storage location 310 may include override code 328 that includes an analog of the degraded read-support information 326, which may differ from the read support information that was originally stored in second data portion 304 on the data storage device 300 in some aspect, but which is functionally equivalent to the read support information with respect to enabling reading of data of interest. The copy or analog of the read-support information 328 may be associated with the memory device 300 through the use of device identification codes 308 and 312. The copy or analog of the read-support information may be functionally analogous to the read support information. In some embodiments, as depicted in FIG. 14, the analog may be functionally equivalent but different from the read support information. In some embodiments, the copy or analog of the read-support information may include a full copy of the read-support information, while in other embodiments the copy or analog of the read-support information may include a partial copy of the read-support information.

As shown in FIGS. 15A and 15B and discussed previously in connection with FIG. 8, in some embodiments, a backup copy 408 of read-support information 406 may be stored in a secondary location on the data storage or memory device 400. FIG. 15A depicts data storage device 400 prior to deactivation, in which data of interest is stored in region 402 and read support information 406 is stored in degradable second data portion 404. Backup copy 408 of read support information 406 is stored in a secondary location in data storage device 400, e.g., in region 402. Backup copy 408 may be read by special purpose software, discussed in connection with FIG. 8. A method of reactivating the device may then include obtaining the backup copy 408 of the read support information by reading the backup copy 408 from a secondary location on the memory device 400 as shown in FIG. 15B. The backup copy of the read-support information may contain complete information necessary for reading the data of interest, or it may be a subset of information necessary for reading the data of interest. In some cases, the backup copy may be stored in the secondary location of the memory device in encoded or encrypted form. For example, as shown in data storage device 450 in FIG. 16, the backup copy 458 of read support info 456 stored in location 454 may be dispersed among the data of interest 452. Such dispersed read support information may be distributed so that it can be retrieved only with the use of special-purpose software.

As outlined in FIG. 17, a method of retrieving information from a deactivated memory device may include providing an identification code to a support entity at step 502 and receiving an override code from the support entity, the override code containing alternative information sufficient to permit reading of the data of interest from the deactivated memory device, at step 504. As shown in step 502, the identification code may be associated with a deactivated memory that includes at least one region from which read-support information sufficient to support reading of data of interest from the memory device could be read prior to deactivation but not after deactivation.

FIG. 18 further elaborates on the method of retrieving information from a deactivated memory device outlined in FIG. 17. Step 552 includes providing an identification code to a support entity, the identification code associated with a deactivated memory device that includes at least one region from which read-support information sufficient to support reading of data of interest from the memory device could be read prior to deactivation but not after deactivation. Three alternative methods of providing the identification code are depicted. Step 558 includes providing the identification to the support entity via a telephone, step 562 includes providing the identification code to the support entity via the internet, and step 560 includes providing the identification to the support entity via a wireless transmission. Step 554 includes receiving an override code from the support entity, the override code containing alternative information sufficient to permit reading of the data of interest from the deactivated memory device.

In another embodiment of a method of retrieving information from a deactivated memory device, as shown in FIG. 19, at 602, an identification code is provided to a support entity, the identification code associated with a deactivated memory device comprising at least one region from which read-support information sufficient to support reading of data of interest from the memory device could be read prior to deactivation but not after deactivation. At step 604, an override code is received from the support entity, the override code containing alternative information sufficient to permit reading of the data of interest from the deactivated memory device. At step 606, the alternative information is used as a key to decode data of interest stored in the deactivated memory device.

FIG. 20 depicts a further variant in which at step 652, an identification code is provided to a support entity, the identification code associated with a deactivated memory device comprising at least one region from which read-support information sufficient to support reading of data of interest from the memory device could be read prior to deactivation but not after deactivation. At step 654, an override code is received from the support entity, the override code containing alternative information sufficient to permit reading of the data of interest from the deactivated memory device. At step 656, alternative information is used as index information for reading data of interest stored in two or more locations of the deactivated memory device in a correct sequence.

FIG. 21 depicts a further method of reactivating a deactivated memory device, which includes receiving an identification code associated with a deactivated memory device, the memory device including at least one degraded degradation-sensitive region that prior to degradation permitted access to machine readable information necessary for reading data of interest from the memory device, as shown at step 702, identifying an override code associated with the identification code, wherein the override code contains read-support information necessary to permit data to be read from the deactivated memory device, as shown at step 704, and providing the override code to a receiving entity at step 706. Step 702, which includes receiving an identification code associated with a deactivated memory device may be performed by a number of different methods, several of which are indicated in FIG. 21. Receiving an identification code may include receiving the identification code from a user of the memory device at step 710. Alternatively, the method may include receiving the identification code from a representative of a user of the memory device at step 712. For example, if the method is performed at a repair shop, the user of the device may present the device and the identification code information to an employee of the repair shop, who may carry out the steps of the reactivation method. As a further alternative, the identification code may be received in the form of an electronic data transmission as shown at 714, or in the form of a wireless data transmission, as shown at 716. The step of providing the override code to a receiving entity is also subject to variation: the method may include providing the override code to a user of the memory device as indicated at 720, or a representative of a user of the memory device as indicated at 722. The method may include providing the override code in the form of an electronic data transmission at step 724 or in the form of a wireless data transmission at step 726. Electronic data transmissions may include data sent in the form of emails or attachments thereto, or various electronic data transfer protocols as are known or may be developed by those of skill in the art. The method of FIG. 21 may be performed in connection with a deactivated memory device in which the degradation-sensitive region has been degraded by exposure to a degradation-inducing influence to render the data of interest inaccessible to the user. The override code may include at least a portion of a decryption key or at least a portion of an index table. The override code may include complete read-support information sufficient for reading the data of interest from the memory device, or it may include partial read-support information necessary for reading the data of interest from the memory device. For example, the partial read-support information in the override code may be sufficient for reading the data of interest from the memory device when used in combination with partial read-support information stored on the memory device.

According to certain embodiments, as outlined in FIG. 22, a method of retrieving data from an expired limited use memory device may include obtaining a backup copy of read-support information necessary for reading machine readable data of interest from the expired limited use memory device, as shown at step 752, where the expired limited use memory device comprises a first portion containing the data of interest and a degraded degradation-sensitive second portion, and the backup copy comprises a copy of read-support information stored in the undegraded degradation-sensitive second portion prior to expiration of the limited use memory. At step 754, based upon the read-support information, data of interest may be read from the first portion of the expired limited use memory device.

FIG. 23 further details the method of FIG. 22, which includes obtaining a backup copy of read-support information necessary for reading machine readable data of interest from the expired limited use memory device at step 802, where the expired limited use memory device comprises a first portion containing the data of interest and a degraded degradation-sensitive second portion, and the backup copy comprises a copy of read-support information stored in the undegraded degradation-sensitive second portion prior to expiration of the limited use memory. At step 804, based upon the read-support information, data of interest may be read from the first portion of the expired limited use memory device. As shown at 808, the method further may include obtaining the backup copy of the read-support information from a third party by providing an identification code associated with the limited use memory device to the third party. The third party may be a support entity, for example, that uses the identification code to determine the read support information that is obtained in step 802.

FIG. 24 further elaborates on the method of FIG. 23. A backup copy of read-support information necessary for reading machine readable data of interest from the expired limited use memory device is obtained at step 852. The expired limited use memory device comprises a first portion containing the data of interest and a degraded degradation-sensitive second portion, and the backup copy comprises a copy of read-support information stored in the undegraded degradation-sensitive second portion prior to expiration of the limited use memory. At step 854, based upon the read-support information, data of interest may be read from the first portion of the expired limited use memory device. As shown at 858, the method may include obtaining the backup copy of the read-support information from a third party by providing an identification code associated with the limited use memory device to the third party. This may involve, for example, receiving the backup copy of the read support information in an electronic format, as indicated at 860. In some embodiments, obtaining the backup copy of the read support information may include receiving the backup copy of the read support information in a digital format, as indicated at 862. In other embodiments, the method may include receiving the backup copy of the read support information in the form of an alphanumeric code, as indicated at step 864, or a bar code, as indicated at step 866.

According to certain embodiments, as shown in FIG. 25, a method of manufacturing a limited use memory device may include providing a substrate (step 902); providing a data storage medium on the substrate (step 904); forming a first data storage region on the substrate, the first data storage region including a substantially non-degradable material (step 906); forming a second data storage region on the substrate, the second data storage region including a degradable material (step 908); and storing a data storage device identification code associated with the data storage device in a data storage location distinct from the data storage device (step 910). The degradable material that is included in the second data storage region may include a degradable data storage medium, or it may include a degradable portion of the substrate.

The method depicted in FIG. 25 may be expanded as shown in FIG. 26. Steps 952-960 include providing a substrate (step 952); providing a data storage medium on the substrate (step 954); forming a first data storage region on the substrate, the first data storage region including a substantially non-degradable material (step 956); forming a second data storage region on the substrate, the second data storage region including a degradable material (step 958); and storing a data storage device identification code associated with the data storage device in a data storage location distinct from the data storage device (step 960). The method illustrated in FIG. 26 also includes storing an override code associated with the data storage device in the data storage location distinct from the data storage device in association with the data storage device identification code at step 962.

FIG. 27 depicts a further elaboration on the method of FIG. 25, including the steps of providing a substrate (step 1002); providing a data storage medium on the substrate (step 1004); forming a first data storage region on the substrate, the first data storage region including a substantially non-degradable material (step 1006); forming a second data storage region on the substrate, the second data storage region including a degradable material (step 1008); and storing a data storage device identification code associated with the data storage device in a data storage location distinct from the data storage device (step 1010). The method may include storing a unique data storage device identification code for individual data storage devices (step 1014), or it may include storing a unique data storage device identification code for one or more individual batches of data storage devices (step 1016).

Storing a unique data storage device identification code for one or more individual data storage devices may be used when each data storage device has a unique identification code. Storing unique data storage device identification code for one or more individual batches of data storage devices may be used in cases where data storage devices within a batch of data storage devices (e.g., a batch being all data storage devices manufactured on one day, all data storage devices of a particular type, or any other selected grouping of data storage devices) have the same device identification code, but data storage devices in different batches of data storage devices have different device identification codes. Storing different data storage device identification codes for individual batches as opposed to individual devices may provide a lower level of security, but may be sufficient for many applications. FIG. 28 illustrates a first batch 1050 including data storage devices 1054a-1054c and a second batch 1052 including data storage devices 1056a-1056c. Each of data storage devices 1054a-1054c includes data of interest 1058a-1058c, respectively, data storage device identification code 1062a-1062c, respectively, and read support information 1060a-1060c, respectively. Similarly, in second batch 1052, each of data storage devices 1056a-1056c includes data of interest 1066a-1066c, respectively, data storage device identification code 1070a-1070c, respectively, and read support information 1068a-1068c, respectively. Data storage devices in first batch 1050 have data storage device identification codes 1062a-1062c each with a value of DSD0001, and corresponding read support information 1060a-1060c with a value of XXXXX. Data storage devices in second batch 1052 have data storage device identification codes 1070a-1070c each with a value of DSD002, and corresponding read support information 1068a-1068c with a value of ZZZZZ. Data storage location 1072, which is a data storage location distinct from the data storage devices (e.g., at a remote location, and/or retained by a third party) includes data storage device identification code 1074 having value DSD0001 associated with override code 1078, containing read-support information of value XXXXX for reading data from data storage devices 1054a-1054c in first batch 1050. Data storage location 1072 also includes data storage device identification code 1076 having value DSD002 associated with override code 1080, containing read-support information of value ZZZZZ for reading data from data storage devices 1056a-1056c in first batch 1052.

FIG. 29 depicts a further variant of the method of FIG. 25, including providing a substrate (step 1152); providing a data storage medium on the substrate (step 1154); forming a first data storage region on the substrate, the first data storage region including a substantially non-degradable material (step 1156); forming a second data storage region on the substrate, the second data storage region including a degradable material (step 1158); and storing a data storage device identification code associated with the data storage device in a data storage location distinct from the data storage device (step 1160). The method includes the additional step of storing read-support information in the second data storage region (step 1162). The method of FIG. 29 may be performed, for example, in situations where the initial manufacture of the data storage device and storage of read support information on the data storage device are performed by the same party. In some previous embodiments (e.g., as shown in FIG. 25) manufacture of the data storage device may sometimes be performed by a different party than storage of read support information and/or data on the data storage device.

FIG. 30 depicts a method including steps 1202-1212, which are the same as step 1152-1162 in FIG. 29, with the additional step of storing a copy of the read support information in the data storage location distinct from the data storage device, as indicated at 1214.

FIG. 31 depicts a further embodiment of a method of manufacturing a data storage device which includes providing a substrate at 1252, providing a data storage medium on the substrate at 1254, forming a first data storage region on the substrate at 1256, where the first data storage region includes a substantially non-degradable material, and forming a second data storage region on the substrate at 1258, where the second data storage region includes a degradable material, and storing a data storage device identification code associated with the data storage device in a data storage location distinct from the data storage device at 1260. Substrates may take various forms and be constructed from various materials. Providing a substrate may include providing a disk shaped substrate (as indicated at 1264) or a card shaped substrate (as indicated at 1266), for example. Providing a substrate may include providing a silicon-based substrate (as indicated at 1268), a polymer-based substrate (as indicated at 1270), or a ceramic-based substrate (as indicated at 1272), for example. Providing a data storage medium may include providing at least one of a magneto-optic material, a thermo-optic material, or an electro-optic material (as indicated at 1274). Providing a data storage medium may include providing at least one of a photochromic dye, a photopolymer, or a photorefractive ferroelectric material (as indicated at 1276).

As shown in FIG. 32, a method of configuring a limited use memory device may include storing a first data portion including data of interest in a first data storage region of a limited use memory device (step 1302), the first data storage region including a relatively non-degradable material; storing a second data portion including read-support, information necessary for reading the data of interest from the first data storage region in a second data storage region of the limited use memory device (step 1304), the second data storage region including a relatively degradable material; and saving an identification code associated with the limited use memory device in a data storage location distinct from the limited use memory device (step 1306).

FIG. 33 illustrates a further expansion on the method shown in FIG. 32. As in FIG. 32, the method may include storing a first data portion including data of interest in a first data storage region of a limited use memory device (step 1352), the first data storage region including a relatively non-degradable material; storing a second data portion including read-support information necessary for reading the data of interest from the first data storage region in a second data storage region of the limited use memory device (step 1354), the second data storage region including a relatively degradable material; and saving an identification code associated with the limited use memory device in a data storage location distinct from the limited use memory device (step 1356). The method further may include saving an override code associated with the limited use memory device in association with the identification code in a data storage location distinct from the limited use memory device, the override code containing information necessary to read data of interest from the first data portion following degradation of read-support information stored in the second data storage region (step 1358). Saving the override code may be performed in several different ways, including storing a copy of the read-support information stored in the second data storage region (step 1362), storing a copy of a portion of the read-support information stored in the second data storage region (step 1364), or saving information different from the read-support information stored in the second data storage region (step 1366).

According to various embodiments as describe herein, methods of obtaining read support information in order to retrieve data of interest from, or ‘reactivate’, a deactivated memory device may be performed completely under microprocessor control. In other embodiments, retrieval of information from a deactivated memory device may be performed with certain intermediate steps performed with human intervention or involvement. Various method steps as describe herein may be performed by hardware, software, firmware, or combinations thereof, as is well known to those of skill in the arts of hardware and software design.

Although discussion herein focuses on ‘reactivation’ of data storage devices that have been deactivated by the degradation (or other modification) of read support information, which blocks access to data stored in portion of a data storage device, in related embodiments, in other embodiments the blocking and unblocking effect obtained by degradation and subsequent retrieval of read support information may be used to activate or deactivate selected portions of the data storage device, so that (for example) different data may be read from the data storage device on the first reading than on the subsequent readings. It will be appreciated that the general approach described herein for obtaining a backup copy of read-support information may similarly be applied to blocking information, in order to activate or deactivate ‘blocking’ of reading, or to activate or deactivate selected portions of a data storage device.

With regard to the hardware and/or software used in the control of devices and systems for reading from data storage devices according to the present embodiments, those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of such systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency or implementation convenience tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems described herein can be effected (e.g., hardware, software, and/or firmware), and that the preferred vehicle will vary with the context in which the processes are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a solely software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. Hence, there are several possible vehicles by which the processes described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary.

In some embodiments, portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and/or firmware would be well within the capabilities of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that certain mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of a signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory; and transmission type media such as digital and analog communication links using TDM or IP based communication links (e.g., links carrying packetized data).

In a general sense, those skilled in the art will recognize that the various aspects described herein which can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof can be viewed as being composed of various types of “electrical circuitry.” Consequently, as used herein “electrical circuitry” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory or an optical or ferromagnetic memory structure), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment).

The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be implicitly understood by those with skill in the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof.

Those skilled in the art will recognize that it is common within the art to describe devices for data storage and reading in the fashion set forth herein, and thereafter use standard engineering practices to integrate such described devices and/or processes into systems including data storage devices as exemplified herein. That is, at least a portion of the devices and/or processes described herein can be integrated into a system including a data storage device via a reasonable amount of experimentation. Those having skill in the art will recognize that such systems generally include one or more of a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational-supporting or associated entities such as operating systems, user interfaces, drivers, sensors, actuators, applications programs, one or more interaction devices, such as data ports, control systems including feedback loops and control implementing actuators (e.g., devices for sensing position and/or velocity and/or acceleration or time-rate-of-change thereof, control motors for moving and/or adjusting components and/or quantities). A typical system may be implemented utilizing any suitable available components, such as those typically found in appropriate computing/communication systems and/or data storage and reading systems, combined with standard engineering practices.

The foregoing-described aspects depict different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality.

While particular aspects of the present subject matter described herein have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this subject matter described herein. Furthermore, it is to be understood that the invention is defined by the appended claims. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should NOT be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” and/or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense of one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense of one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together).

Although the methods, devices, systems and approaches herein have been described with reference to certain preferred embodiments, other embodiments are possible. As illustrated by the foregoing examples, various choices of system configuration may be within the scope of the invention. As has been discussed, the choice of system configuration may depend on the intended application of the system, the environment in which the system is used, cost, personal preference or other factors. Data storage device design, manufacture, and control processes may be modified to take into account choices of system components and configuration, and such modifications, as known to those of skill in the arts of data storage and retrieval structures and systems, fluid control structures, and electronics design and construction, may fall within the scope of the invention. Therefore, the full spirit or scope of the invention is defined by the appended claims and is not to be limited to the specific embodiments described herein.

Claims

1. A method performed by a microprocessor for retrieving information from a deactivated memory device, comprising: providing, over the Internet, an identification code to a support entity, the identification code uniquely associated with a specific deactivated memory device, the deactivated memory device including at least one region from which read-support information sufficient to support reading of data of interest from the memory device is readable prior to deactivation but not after deactivation; andreceiving, over the Internet, a unique override code from the support entity, the override code unique to the specific deactivated memory device and containing alternative information sufficient to permit reading of the data of interest from the deactivated memory device.
2. The method of claim 1, including using the alternative information as a key to decode data of interest stored in the deactivated memory device.
3. The method of claim 1, including using the alternative information as index information for reading data of interest stored in two or more locations of the deactivated memory device in a correct sequence.
4. The method of claim 1, wherein the at least one region is a degradation-sensitive region, and wherein deactivation of the memory device includes degradation of the degradation-sensitive region.
5. The method of claim 4, wherein the degradation-sensitive region has been degraded by exposure to a degradation-inducing influence to render the data of interest inaccessible to a user of the memory device.
6. The method of claim 1, wherein the region from which read-support information sufficient to support reading of data of interest from the memory device is readable prior to deactivation but not after deactivation includes: a degradation-sensitive region has been degraded by exposure to a degradation-inducing influence to render the data of interest inaccessible to the user.
7. The method of claim 1, wherein the unique override code includes complete read-support information sufficient for reading the data of interest from the memory device.
8. The method of claim 1, wherein the unique override code includes partial read-support information necessary for reading the data of interest from the memory device.
9. The method of claim 8, wherein the partial read-support information in the override code is sufficient for reading the data of interest from the memory device when used in combination with partial read-support information stored on the memory device.
10. The method of claim 1, wherein the receiving, over the Internet, a unique override code from the support entity, the override code unique to the specific deactivated memory device and containing alternative information sufficient to permit reading of the data of interest from the deactivated memory device includes: receiving a backup copy of the read-support information sufficient to support reading of the data of interest from the memory device.
11. The method of claim 10, wherein the receiving a backup copy of the read-support information sufficient to support reading of the data of interest from memory device includes: receiving the backup copy of the read-support information from a third party by providing an identification code associated with the memory device to the third party.
12. The method of claim 10, wherein the receiving a backup copy of the read-support information sufficient to support reading of the data of interest from memory device includes: receiving the backup copy of the read support information in an electronic format.
13. The method of claim 10, including receiving the backup copy of the read support information by reading the backup copy from a secondary location on the memory device.
14. The method of claim 13, wherein the backup copy is stored in the secondary location of the memory device in encoded or encrypted form.
15. The method of claim 10, wherein the receiving a backup copy of the read-support information sufficient to support reading of the data of interest from memory device includes: receiving the backup copy of the read support information in at least one of a digital format, an alphanumeric code, or a bar code.
16. The method of claim 10, wherein the receiving a backup copy of the read-support information sufficient to support reading of the data of interest from memory device includes: receiving at least one of complete information necessary for reading the data of interest or a subset of information necessary for reading the data of interest.
17. The method of claim 1, wherein the receiving, over the Internet, a unique override code from the support entity includes: receiving the override code including at least one of a full copy of the read-support information, a portion of the read-support information, or an analog of the read-support information.
18. The method of claim 1, wherein the providing, over the Internet, an identification code to a support entity includes: providing the identification code from at least one of a user of the memory device or a representative of a user of the memory device.
19. The method of claim 1, wherein the providing, over the Internet, an identification code to a support entity includes: providing the identification code in the form of an electronic data transmission or a wireless data transmission.
20. The method of claim 1, wherein the receiving, over the Internet, a unique override code from the support entity includes: receiving the override code from at least one of a user of the memory device or representative of a user of the memory device.
21. The method of claim 1, wherein the receiving, over the Internet, a unique override code from the support entity includes: receiving the override code in the form of an electronic data transmission or a wireless data transmission.
22. The method of claim 1, wherein the override code includes at least a portion of a decryption key or at least a portion of an index table.

US Referenced Citations (199)

Number	Name	Date	Kind
4237211	Fanselow	Dec 1980	A
4434337	Becker	Feb 1984	A
4490767	Neuman et al.	Dec 1984	A
4625359	Egner-Walter et al.	Dec 1986	A
4743989	Bauck et al.	May 1988	A
5014311	Schrenk	May 1991	A
5162989	Matsuda	Nov 1992	A
5182742	Ohmori et al.	Jan 1993	A
5302898	Pethig et al.	Apr 1994	A
5309301	Gregory et al.	May 1994	A
5319481	Fergason	Jun 1994	A
5337180	Woods et al.	Aug 1994	A
5394367	Downs et al.	Feb 1995	A
5450489	Ostrover et al.	Sep 1995	A
5465381	Schmidt et al.	Nov 1995	A
5483596	Rosenow et al.	Jan 1996	A
5507545	Krysiak	Apr 1996	A
5521140	Matsuda et al.	May 1996	A
5567512	Chen et al.	Oct 1996	A
5590381	Mourad	Dec 1996	A
5602820	Wickramasinghe et al.	Feb 1997	A
5625690	Michel et al.	Apr 1997	A
5652838	Lovett et al.	Jul 1997	A
5708652	Ohki et al.	Jan 1998	A
5734823	Saigh et al.	Mar 1998	A
5736777	Shield et al.	Apr 1998	A
5751074	Prior et al.	May 1998	A
5755942	Zanzucchi et al.	May 1998	A
5785831	Bek	Jul 1998	A
5796706	Shintani et al.	Aug 1998	A
5815434	Hasbun et al.	Sep 1998	A
5815484	Smith et al.	Sep 1998	A
5878203	Matsumoto et al.	Mar 1999	A
5880523	Candelore	Mar 1999	A
5960398	Fuchigami et al.	Sep 1999	A
6000030	Steinberg et al.	Dec 1999	A
6006328	Drake	Dec 1999	A
6011772	Rollhaus et al.	Jan 2000	A
6030581	Virtanen	Feb 2000	A
6041412	Timson et al.	Mar 2000	A
6044046	Diezmann et al.	Mar 2000	A
6103454	Dhar et al.	Aug 2000	A
6131165	Lipkin et al.	Oct 2000	A
6151262	Haroun et al.	Nov 2000	A
6157559	Yoo	Dec 2000	A
6160734	Henderson et al.	Dec 2000	A
6226747	Larsson et al.	May 2001	B1
6228440	Dailey et al.	May 2001	B1
6230244	Kai	May 2001	B1
6278679	Weiss et al.	Aug 2001	B1
6296020	McNeely et al.	Oct 2001	B1
6303886	Stoughton	Oct 2001	B1
6314518	Linnartz	Nov 2001	B1
6320830	Tsukamoto et al.	Nov 2001	B1
6322682	Arvidsson et al.	Nov 2001	B1
6338933	Lawandy et al.	Jan 2002	B1
6389701	Friedland	May 2002	B1
6410103	Kasamatsu et al.	Jun 2002	B1
6427140	Ginter et al.	Jul 2002	B1
6434109	Rollhaus et al.	Aug 2002	B2
6449651	Dorfman et al.	Sep 2002	B1
6454173	Graves	Sep 2002	B2
6454970	Öhman et al.	Sep 2002	B1
6465369	Teng et al.	Oct 2002	B1
6511728	Bakos et al.	Jan 2003	B1
6512600	Kawai et al.	Jan 2003	B1
6513060	Nixon et al.	Jan 2003	B1
6535858	Blaukovitsch et al.	Mar 2003	B1
6537635	Bakos et al.	Mar 2003	B1
6563506	Wang	May 2003	B1
6587429	Conturie et al.	Jul 2003	B1
6589626	Selinfreund et al.	Jul 2003	B2
6591852	McNeely et al.	Jul 2003	B1
6601613	McNeely et al.	Aug 2003	B2
6620478	Öhman	Sep 2003	B1
6632656	Thomas et al.	Oct 2003	B1
6633877	Saigh et al.	Oct 2003	B1
6640305	Kocher et al.	Oct 2003	B2
6641886	Bakos et al.	Nov 2003	B1
6646967	Garcia	Nov 2003	B1
6651149	Iwasaki	Nov 2003	B1
6653625	Andersson et al.	Nov 2003	B2
6654797	Kamper	Nov 2003	B1
6662262	Kasa et al.	Dec 2003	B1
6663003	Johnson et al.	Dec 2003	B2
6678239	Clemens	Jan 2004	B2
6684199	Stebbings	Jan 2004	B1
6684310	Anzai et al.	Jan 2004	B2
6709802	Lawandy et al.	Mar 2004	B2
6715116	Lester et al.	Mar 2004	B2
6717136	Andersson et al.	Apr 2004	B2
6721889	Jaegtnes et al.	Apr 2004	B1
6728644	Bielik et al.	Apr 2004	B2
6744551	Chao	Jun 2004	B1
6747930	Weldon et al.	Jun 2004	B1
6748485	Yokota et al.	Jun 2004	B1
6748537	Hughes	Jun 2004	B2
6751716	Sumitani et al.	Jun 2004	B2
6756103	Thompson et al.	Jun 2004	B2
6764758	Grunze et al.	Jul 2004	B1
6772340	Peinado et al.	Aug 2004	B1
6775655	Peinado et al.	Aug 2004	B1
6780564	Lawandy et al.	Aug 2004	B2
6782190	Morito	Aug 2004	B1
6785185	Sumitani et al.	Aug 2004	B2
6788443	Ayres et al.	Sep 2004	B2
6793753	Unger et al.	Sep 2004	B2
6802489	Marr et al.	Oct 2004	B2
6811736	Ohman et al.	Nov 2004	B1
6812456	Andersson et al.	Nov 2004	B2
6812457	Andersson et al.	Nov 2004	B2
6826700	Germscheid et al.	Nov 2004	B1
6837476	Cabuz et al.	Jan 2005	B2
6838144	Bakos et al.	Jan 2005	B2
6839316	Bakos et al.	Jan 2005	B2
6852851	Tooke et al.	Feb 2005	B1
6854005	Thiele	Feb 2005	B2
6878555	Andersson et al.	Apr 2005	B2
6915398	Matsubara et al.	Jul 2005	B2
6948071	Schneider et al.	Sep 2005	B2
7027384	Ohbi et al.	Apr 2006	B2
7177261	Thompson et al.	Feb 2007	B2
7210137	Tamma	Apr 2007	B1
7215779	Go et al.	May 2007	B2
7343330	Boesjes et al.	Mar 2008	B1
7369471	Ferren et al.	May 2008	B2
7451344	Rothberg	Nov 2008	B1
7496765	Sengoku	Feb 2009	B2
7505264	Hall et al.	Mar 2009	B2
7596073	Ferren et al.	Sep 2009	B2
7668068	Ferren et al.	Feb 2010	B2
7725614	Jogand-Coulomb et al.	May 2010	B2
7730033	Mohamed	Jun 2010	B2
7916615	Ferren et al.	Mar 2011	B2
8140745	Ferren et al.	Mar 2012	B2
20010018741	Hogan	Aug 2001	A1
20010037452	Go et al.	Nov 2001	A1
20010055702	Wang et al.	Dec 2001	A1
20020051536	Shirakawa et al.	May 2002	A1
20020076647	Lawandy et al.	Jun 2002	A1
20020137218	Mian et al.	Sep 2002	A1
20020142099	Dubs	Oct 2002	A1
20020166061	Falik et al.	Nov 2002	A1
20030002431	Breitung et al.	Jan 2003	A1
20030018905	Schneider et al.	Jan 2003	A1
20030028820	Takashi et al.	Feb 2003	A1
20030031115	Constantinou et al.	Feb 2003	A1
20030043710	Shelton et al.	Mar 2003	A1
20030044322	Andersson et al.	Mar 2003	A1
20030051148	Garney	Mar 2003	A1
20030053934	Andersson et al.	Mar 2003	A1
20030054563	Ljungstrom et al.	Mar 2003	A1
20030126391	Neufeld et al.	Jul 2003	A1
20030131255	Shim	Jul 2003	A1
20030156763	Soderman	Aug 2003	A1
20030174616	Constantinou et al.	Sep 2003	A1
20030202452	Mishima et al.	Oct 2003	A1
20030217241	Chong et al.	Nov 2003	A1
20030223100	Anderson	Dec 2003	A1
20040004932	Inoue et al.	Jan 2004	A1
20040008613	Beckwith et al.	Jan 2004	A1
20040016879	Andersson et al.	Jan 2004	A1
20040037208	Chen et al.	Feb 2004	A1
20040037994	Bakos et al.	Feb 2004	A1
20040058408	Thomas et al.	Mar 2004	A1
20040088479	Hall	May 2004	A1
20040121268	Conroy et al.	Jun 2004	A1
20040152013	Olson et al.	Aug 2004	A1
20040152015	Lawandy et al.	Aug 2004	A1
20040191125	Kellogg et al.	Sep 2004	A1
20040209034	Tompson et al.	Oct 2004	A1
20040215909	Imai et al.	Oct 2004	A1
20040255145	Chow	Dec 2004	A1
20050002302	Sugimura	Jan 2005	A1
20050005142	Fontijn	Jan 2005	A1
20050013232	Sivakumar et al.	Jan 2005	A1
20050015609	Delorme	Jan 2005	A1
20050031777	Hayashi et al.	Feb 2005	A1
20050042770	Derand et al.	Feb 2005	A1
20050050571	Wisnudel et al.	Mar 2005	A1
20050069913	Mian et al.	Mar 2005	A1
20050094516	Morimoto et al.	May 2005	A1
20050105885	Lee	May 2005	A1
20050141351	Yamanaka	Jun 2005	A1
20050195728	Larroche	Sep 2005	A1
20060056815	Sutardja	Mar 2006	A1
20060069945	Takashi et al.	Mar 2006	A1
20060071795	Benedikt	Apr 2006	A1
20060104172	Grampel et al.	May 2006	A1
20060224611	Dunn et al.	Oct 2006	A1
20060262928	Bar-El et al.	Nov 2006	A1
20060265598	Plaquin et al.	Nov 2006	A1
20070061893	Black et al.	Mar 2007	A1
20070074126	Fisher et al.	Mar 2007	A1
20070162978	Watanabe et al.	Jul 2007	A1
20080159109	Ferren et al.	Jul 2008	A1
20080252463	Andrechak et al.	Oct 2008	A1
20090034384	Geelen	Feb 2009	A1
20090122666	Ferren et al.	May 2009	A1

Foreign Referenced Citations (9)

Number	Date	Country
1585980	Feb 2005	CN
2 443 998	May 2008	GB
WO 9807019	Feb 1998	WO
WO 9811539	Mar 1998	WO
WO 9841979	Sep 1998	WO
WO 9853311	Nov 1998	WO
WO 9967085	Dec 1999	WO
WO 2007019473	Feb 2007	WO
WO 2007030808	Mar 2007	WO

Non-Patent Literature Citations (49)

Entry
U.S. Appl. No. 11/504,547, Ferren et al.
U.S. Appl. No. 11/499,395, Ferren et al.
U.S. Appl. No. 11/471,970, Ferren et al.
U.S. Appl. No. 11/471,284, Ferren et al.
U.S. Appl. No. 11/223,899, Ferren et al.
U.S. Appl. No. 11/223,898, Ferren et al.
U.S. Appl. No. 11/223,888, Ferren et al.
U.S. Appl. No. 11/223,829, Ferren et al.
Adelstein, Peter Z.; “Permanence of Digital Information”; International Conference of the Round Table on Archives: XXIV—CITRA Budapest 1999, Access to Information and Preservation Issues; bearing a date of 1999; pp. 1-7.
“An Overview of the Field of Optical Disk Data Storage”; WTEC Hyper- Librarian; bearing a date of Jun. 1999; pp. 1-13; located at: http://www.wtec.org/loyola/hdmem/05—02.htm; printed on Apr. 20, 2005.
Bertram, Neal H.; Cuddihy, Edward F.; “Kinetics of the Humid Aging of Magnetic Recording Tape”; IEEE Transactions on Magnetics; pp. 993-999; vol. Mag-18, No. 5, Sep. 1982.
Bogart, John W.C. Van; “Magnetic Tape Storage and Handling: A Guide for Libraries and Archives—4. Life Expectancy: How Long Will Magnetic Media Last?”; National Media Laboratory; bearing a date of Jun. 1995; pp. 1-2; located at: http://www.clir.org/pubs/reports/pub54/4life—expectancy.html; printed on Apr. 22, 2005.
Bogart, John W.C. Van; “Magnetic Tape Storage and Handling: A Guide for Libraries and Archives—5. How Can You Prevent Magnetic Tape from Degrading Prematurely?”; National Media Laboratory; bearing a date of Jun. 1995; pp. 1-8; located at: http://www.clir.org/pubs54/5premature—degrade.html; printed on Apr. 22, 2005.
Bogart, John W.C. Van; “Mag Tape —Life Expectancy 10-30 years: A Letter to the Editor of the Scientific American”; National Media Lab; bearing dates of Mar. 13, 1995, Jan. 1995, Aug. 3, 2004; pp. 1-2; located at: http://palimpsest.stanford.edu/bytopic/electronic-records/electronic-storage-media/bogart.html; printed on Apr. 22, 2005.
Bogart, John Van; “Storage Media Life Expectancies”; Digital Archive Directions (DADs) Workshop; Jun. 22, 1998; pp. 1-17; National Media Laboratory located at : http://ssdoo.gsfc.nasa.gov/nost/isoas/dads/presentations/VanBogart/VanBogart.ppt; printed on Apr. 22, 2005.
“Flexplay: How Flexplay® Works”; Howstuffworks.com; bearing dates of Dec. 2, 2004, 2000, 2005; pp. 1-2; Convex Group; located at: http://www.flexpay.com/how-flexplay-works.htm; printed on Feb. 11, 2005.
Fuentes-Hernandez, Canek; Thomas, Jayan; Termine, Roberto; Meredith, Gerald; Peyghambarian, Nasser; Kippelen, Bernard; Barlow, Steve; Walker, Gregory; Marder, Seth R.; Yamamoto, Michiharu; Cammack, Kevin; Matsumoto, Kenji; “Video-rate compatible photorefractive polymers with stable dynamic properties under continuous operation”; Applied Physics Letters; bearing dates of 2004, and Feb. 24, 2005; pp. 1877-1879; vol. 85, No. 11, Sep. 13, 2004; American Institute of Physics.
Garfinkel, Simson; “The Myth of Doomed Data”; TechnologyReview.com; bearing a date of Dec. 3, 2003; pp. 1-2; located at: http://www.technologyreview.com/articles/03/12/wo—garfinkel120303.asp?p=0; printed on Apr. 25, 2005.
Hadenius, Patric; “Holostorage for the Desktop”; Technology Review: Innovation News—Hardware; bearing a date of May 2004; p. 22; Courtesy of Inphase Technologies.
“Hard disk drive design and technology: Magnetic Hard Disk Drive”; USByte.com; bearing dates of 1999-2002; pp. 1-2; located at: http://www.usbyte.com/common/HDD.htm; printed on Apr. 20, 2005.
Hunt, Jim; “Fend Off Data Degradation”; Quality Online, Quality Computing; bearing a date of May 1999; pp. 1-5; located at: http://www.qualitymag.com/articles/1999/may99/0599qc.html; printed on Nov. 12, 2001.
Jonietz, Erika; “Magnetic Future: Isolating bits on a disk drive could shatter storage limits”; Technology Review; p. 23; Jul./Aug. 2002; Courtesy of IBM Research; located at: www.technologyreview.com.
Judge, J.S.; Schmidt, R.G.; Weiss, R.D.; Miller, G; “Media Stability and Life Expectancies of Magnetic Tape for Use with IBM 3590 and Digital Linear Tape Systems”; pp. 1-4.
Kuhn, Kelin J.; “CD/ROM—An extension of the CD audio standard”; pp. 1-8; located at: http://www.ee.washington.edu/conselec/CE/kuhn/cdrom/95x8.htm; printed on Sep. 22, 2004.
Kuhn, Kelin J.; “Other disk formats of interest”; pp. 1-6; located at: http://www.ee.washington.edu/conselec/CE/kuhn/otherformats/95x9.htm; printed on Apr. 22, 2005.
Latorre, Laurent; Kim, Joonwon; Lee, Junghoon; De Guzman, Peter-Patrick; Lee, Hyesog J.; Nouet, Pascal; Kim, Chang-Jin; Electrostatic Actuation of Microscale Liquid-Metal Droplets; Journal of Microelectromechanical Systems; vol. 11; No. 4; Aug. 2002; pp. 302-308; IEEE.
Madou, Marc J.; Lee, L. James; Koelling, Kurt W; Daunert, Sylvia; Lai, Siyi; Koh, Chee Guan; Juang, Yi-Je; Yu, Liyong; Lu, Yumin; “Design and Fabrication of Polymer Microfluidic Platforms for Biomedical Applications”; ANTEC; bearing a date of 2001; pp. 2534-2538.
“6. Magnetic Materials”; pp. 1-9; located at: http://www.unesco.org/webworld/mdm/administ/en/guide/guide008.htm; printed on Apr. 22, 2005.
Novack, Wesley; “ASUS DRW-1604P DVD±RW drive—Reading Performance”; CD Freaks.com; bearing a date of Feb. 12, 2005; pp. 1-9; located at: http://www.cdfreaks.com/article/179/3; printed on Apr. 22, 2005.
Peiker, E.J.; “Flash Memory—A Primer”; NatureScapes.Net; pp. 1-3; located at: http://www.naturescapes.net/112003/ej1103.htm; printed on Apr. 22, 2005.
Sadashige, Koichi; “Data Storage Technology Assessment—2002 Projections through 2010”; National Media Laboratory and National Technology Alliance; bearing a date of Mar. 2003; pp. 1-80.
“STMicroelectronics Advances in Development of Future Non-Volatile Memory Technology”; STMicroelectronics; bearing dates of Jun. 16, 2004, 2005; pp. 1-2; located at: http://www.st.com/stonline/press/news/year2004/t1480h.htm; printed on Apr. 22, 2005.
Thompson, D.A.; Best, J.S.; “The future of magnetic data storage technology”; IBM Journal of Research and Development; bearing dates of Jul. 9, 1999, Nov. 9, 1999; pp. 1-9;vol. 44, No. 3, 2000; located at: http://www.research.ibm.com/journal/rd/443/thompson.html; printed on Apr. 20, 2005.
Trock, Jacob; “18. Litteraturliste”; pp. 1-23; located at: http://home3.inet.tele.dk/jtrock/2del/kap18.htm; printed on Apr. 22, 2005.
Tyson, Jeff; “How Flash Memory Works”; howstuffworks; bearing dates of 1998-2005; pp. 1-6; HowStuffWorks, Inc.; located at: http://computer.howstuffworks.com/flash-memory.htm/printable; printed on Apr. 28, 2005.
Vos, Martin; Ashton, Gary; Bogart, John Van; Ensminger, Ron; “Heat and Moisture Diffusion in Magnetic Tape Packs”; National Media Laboratory; bearing a date of Mar. 1994; pp. 1-15; vol. 30, No. 2; IEEE Transactions on Magnetics.
Zeng, Jun; Banerjee, Deb; Deshpande, Manish; Gilbert, John R.; “Design Analyses of Capillary Burst Valves in Centrifugal Microfluidics”; UTAS; pp. 1-4; 2000; located at: www.coventor.com/media/papers/uTAS2000—burst.pdf.
U.S. Appl. No. 12/583,859, Ferren et al.
U.S. Appl. No. 12/583,399, Ferren et al.
UK Intellectual Property Office Examination Report Under Section 18(3); App. No. GB0806367.9; Jun. 11, 2010; pp. 1-3.
UK Intellectual Property Office Examination Report Under Section 18(3); App. No. GB0806366.1; Jun. 11, 2010; pp. 1-3.
The State Intellectual Property Office of the People's Republic of China Notice on the First Office Action; App. No. 200680036503.8; Jan. 26, 2011; pp. 1-3.
UK Intellectual Property Office Combined Search and Examination Report under Sections 17 and 18(3); App. No. GB1019876.0; Feb. 14, 2011; pp. 1-5.
The State Intellectual Property Office of the People's Republic of China Notice on the First Office Action; App. No. 200680039257.1; Jul. 14, 2011; pp. 1-3.
The State Intellectual Property Office of The People's Republic of China; Notice on the Second Office Action; App. No. 2006/80036503.8 (Based on PCT Patent Application No. PCT/US06/030805); Feb. 28, 2012; pp. 1-7 (translation provided, includes 3 page coversheet).
The State Intellectual Property Office of the People's Republic of China; Notice on the Second Office Action; App. No. 2006/80039257.1; Jun. 4, 2012; pp. 1-10 (translation provided, 6 pages).
The State Intellectual Property Office of the People's Republic of China; Notice on the Third Office Action; Application No. 200680036503.8; Oct. 26, 2012; pp. 1-7 (English Machine Translation Provided, 10 pages total).
The Patent Office of the State Intellectual Property Office of the People's Republic of China—Decision on Rejection; App. No. 200680036503.8; May 20, 2013; 24 pages (including machine translation).
The State Intellectual Property Office of the People's Republic of China; Notice on the Third Office Action; Application No. 200680039257.1; Feb. 1, 2013; pp. 1-5; (Machine translation to English provided, 6 pages).

Related Publications (1)

	Number	Date	Country
	20070041231 A1	Feb 2007	US

Memory device activation and deactivation

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications