|Publication number||US20050135227 A1|
|Application number||US 11/049,333|
|Publication date||Jun 23, 2005|
|Filing date||Feb 1, 2005|
|Priority date||Apr 29, 1999|
|Also published as||DE60007684D1, DE60007684T2, EP1049089A2, EP1049089A3, EP1049089B1, EP1327983A2, EP1327983A3, EP1575049A2, EP1575049A3, EP1830359A2, EP1830359A3, US6330210, US7657943, US7911906, US20010048659, US20050135226, US20070153643, US20090282190|
|Publication number||049333, 11049333, US 2005/0135227 A1, US 2005/135227 A1, US 20050135227 A1, US 20050135227A1, US 2005135227 A1, US 2005135227A1, US-A1-20050135227, US-A1-2005135227, US2005/0135227A1, US2005/135227A1, US20050135227 A1, US20050135227A1, US2005135227 A1, US2005135227A1|
|Inventors||Charles Weirauch, Joel Larner|
|Original Assignee||Weirauch Charles R., Larner Joel B.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (13), Referenced by (2), Classifications (56)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application is a divisional application of Ser. No. 09/921,024 filed on Aug. 2, 2001. application Ser. No. 09/921,024 is hereby incorporated herein by reference. application Ser. No. 09/921,024 is a divisional application of Ser. No. 09/301,880 filed on Apr. 29, 1999 now issued as U.S. Pat. No. 6,330,210. application Ser. No. 09/301,880 is hereby incorporated herein by reference.
This invention relates generally to data storage media and more specifically to data structures used for various identification and control attributes for a rewriteable medium.
A data storage medium typically includes an area for storage of various administration and control information, such as an identification of the medium, perhaps information regarding how the medium is partitioned into various separate sections, a directory or table of file names and dates, and perhaps information regarding access control. Administration and control information may reside in a particular physical location on a medium separate from a general data storage area. For example, compact discs (CD) used for data storage have a single spiral track, with an area near the start of the track called a lead-in area, and an area near the end of the track called a lead-out area. The information in the lead-in area and the lead-out area contains administration and control information used only by drives and operating systems, and is separate from the area used for data storage.
Sometimes, a data storage medium has a format that is specific to a proprietary drive mechanism, or specific to one computer operating system. Alternatively, some formats are defined by standards, so that a medium can be exchanged among drives from multiple manufacturers and may be used by multiple computer operating systems. Standards are useful in eliminating unnecessary variation, but standards may also inhibit change, even when change is needed. For example, CD's were originally developed for read-only digital audio. As the CD technology was extended to general data, and write-once media, and rewriteable media, accommodation of new features with backwards compatibility was always an issue. There is a need for a standard way of recording administration and control information, for interchangeable rewriteable media, that can accommodate unforseen needs for changes in the future.
One goal of the invention is to provide a standard, but very general and flexible, data structure for recording administration and control information for a rewriteable storage medium, particularly when drives and media may be provided by many different manufacturers. Accordingly, a data structure, called a Disk Control Block (DCB), is defined. One medium may contain multiple different DCB's, each addressing a different function. Several examples of DCB's are provided. One example is called a General Media (GM) DCB. The GM DCB contains information such as a counter that counts how many times the medium has been loaded, control information for formatting of the medium by the drive, and power calibration information. Another example DCB is called an Access Control (AC) DCB. An AC DCB may be used to partition a disk into multiple sections, and for each section the DCB defines an access attribute such as write-once, or read only with password, or other similar access control. Another example is a DCB for updating firmware.
Another goal of the invention is to provide a data structure such that if a drive encounters an unrecognized DCB, the drive can still decode an essential set of standard control parameters in the unrecognized DCB, so that the drive behavior is not inconsistent with the requirements of the unrecognized DCB. Each DCB includes a control block identifier that specifies the function of the DCB. Each DCB also includes an area called Unknown Content Descriptor Actions (UCDA), which specifies certain actions a drive must take if the drive does not recognize the identifier for the DCB.
An additional goal of the invention is to ensure the reliability of DCB's even if the disk is defective, or even if power is interrupted during writing of a DCB. In an example embodiment, redundant DCB's are provided, and each DCB has a sequence number. Identical identifiers with identical sequence numbers indicate identical (deliberately redundant) DCB's. If one copy is invalid, the invalid copy is replaced by the valid copy. Identical identifiers with different sequence numbers indicate that writing of a DCB was interrupted, and the DCB having the oldest (lowest) sequence number, for the particular identifier, is used.
In the following discussion, a proposed standard for optical disk media is used to illustrate a specific example embodiment of the invention. However, the invention is equally applicable to any interchangeable rewriteable data storage medium. For example, the invention is equally applicable to tapes, removable magnetic disks or cards, or removable semiconductor memory.
The proposed standard specifies a rewriteable interchangeable optical disk. A data structure called a Disk Control Block (DCB) is defined. There may be many types of DCB's; some may be defined by the proposed standard, and others may be defined by individual manufacturers. One type of DCB, called a General Media (GM) DCB is defined by the proposed standard. The proposed standard specifies that every compatible medium must write one GM-DCB. All other types of DCB's are optional, and are in addition to the GM-DCB.
The proposed optical disk medium is formatted into sectors, and sectors are logically grouped into blocks. In the proposed standard, each sector is 2 Kbytes (2,048 bytes) and each block is 16 sectors. A block is the smallest unit of data that can be written. Error correction is performed on a block by block basis. In the proposed standard, a DCB is one block. In the specific example embodiment, DCB's reside within the lead-in and lead-out areas of an optical disk.
One important feature of a DCB is the second header entry, Unknown Content Descriptor Actions (UCDA) 204. The UCDA is used to ensure that even if a drive does not recognize a DCB ID, the drive does not permit disk access actions that are inconsistent with the access control requirements of the unknown DCB. This provides some backwards compatibility, a capability that is lacking in many current proposed standards. The UCDA will be discussed in more detail below. The third and final entry in DCB header is a vendor ID (206).
Some present optical disk technologies require that the laser writing power be calibrated before writing can occur. In general, the power required is a function of the specific medium and the particular electronic components in the drive. In general, power calibration is time consuming. Another proposed variable (not illustrated) in the GM DCB is at least one entry for a drive identification and a number designating the laser power resulting when the laser power was calibrated using the specific medium in the identified drive. A drive recognizing its own ID in the GM-DCB can then simply read the required laser power without having to recalibrate.
Operating systems may control whether or not a file can be read or written by a user. Some files may be password protected by the operating system. Alternatively, write protect for an entire medium may be controlled mechanically. For example, a sliding tab on a flexible disk cartridge, or a ring inserted into a tape reel may be used to prevent writing to a medium. In general, if an interchangeable medium is placed into a computer system using an incompatible operating system, access control specified by the operating system may be bypassed. For example, if one operating system write protects a file, a different operating system may permit the file to be overwritten. Moving control of access into the drive provides some additional protection. Access control within a drive is not new. For example, U.S. Pat. No. 5,233,576 (Curtis et al.) describes an optical disk medium in which the medium can be partitioned into different portions, and each portion can be defined as writable, or read-only. One attractive feature of Curtis et al. is that the method of write protection works even for legacy drives that were manufactured before the new access control method was available. One example DCB for use by the present invention takes this general concept even further. One example optional DCB is an Access Control (AC) DCB. An access control DCB divides the disk into regions, by specifying starting and ending logical block address or by specifying starting block address and number of blocks. Each region, as seen by the operating system, may represent a file, a directory, the entire disk, or any other logical storage construct. Each region has an associated access control specification, where the access control specifications include the following, as examples:
The above list is just a list of examples, and other access controls may be desirable. For example, one issue is whether a control attribute specifying a write-once region can ever be reversed. The proposed standard specifies that controls can be changed, so there are controls on controls. For example, an access control, within a AC DCB, may itself be password protected.
Now return to the UCDA (
Another proposed DCB type is a firmware update DCB. Typically, drive firmware is updated by connecting a drive to a computer and having the computer send a new version of firmware. Often, it is more convenient if a firmware update can occur without involvement by a host computer. It is known for a drive to recognize a special medium having a new version of firmware for the drive. The drive replaces its existing firmware with the new firmware read from the special medium. A DCB may be defined that identifies a medium as a firmware update medium, and contains information describing the firmware update, version information, back version compatibiity, and so forth.
Since DCB's are so critical to the proposed standard, it is important to provide some protection against a loss-of-power during writing of a DCB, or protection against some other corruption of a DCB. As stated above, one redundant DCB is written for each DCB. The first word of each DCB-specific data area is a sequence number (
From the above, it can be seen that DCB's provide a flexible and standard way of providing administration and control information for a data storage medium, particularly when drives and media may be provided my many different manufacturers. In addition, the use of UCDA's provides a standard way of ensuring that a drive does not perform an access that is inconsistent with a DCB, even if the DCB is not recognized. Finally, redundancy and sequence numbers provide some protection against corrupted DCB's.
The foregoing description of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and other modifications and variations may be possible in light of the above teachings. The embodiment was chosen and described in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and various modifications as are suited to the particular use contemplated. It is intended that the appended claims be construed to include other alternative embodiments of the invention except insofar as limited by the prior art.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4827462 *||Mar 26, 1987||May 2, 1989||International Business Machines Corporation||Modular data storage directories for large-capacity data storage units|
|US5170385 *||Oct 25, 1990||Dec 8, 1992||Sony Corporation||Recording medium with unembossed area indicating sector divisions|
|US5233576 *||Nov 15, 1991||Aug 3, 1993||Hewlett-Packard Company||Multi-function optical disk drive and media|
|US5237553 *||May 24, 1991||Aug 17, 1993||Matsushita Electric Industrial Co.||Data recording and reproducing apparatus having a plurality of operating modes|
|US5446724 *||Jun 5, 1992||Aug 29, 1995||Kabushiki Kaisha Toshiba||Information storage medium with first and second recording regions each having a predetermined recording density|
|US5568467 *||Apr 28, 1994||Oct 22, 1996||Matsushita Electric Industrial Co., Ltd.||Information recording format having a plurality of bands with independent read and write control data|
|US5617407 *||Sep 20, 1996||Apr 1, 1997||Bareis; Monica M.||Optical disk having speech recognition templates for information access|
|US5752009 *||Dec 2, 1996||May 12, 1998||Fujitsu Limited||Recording medium for electronic publications including multiple format emulation|
|US5805564 *||May 29, 1996||Sep 8, 1998||Sony Corporation||Optical disk capable of detecting errors in address area and correcting errors in data area and recording method and apparatus therefor|
|US6130867 *||Sep 15, 1999||Oct 10, 2000||Matsushita Electric Industrial Co., Ltd.||Optical disc, optical disc device, and method for recording an optical disc|
|US6201784 *||Dec 10, 1999||Mar 13, 2001||Sharp Kabushiki Kaisha||Disk type recording medium having zones with address information recorded in grooves and recording and reproducing device therefor|
|US6385744 *||Dec 3, 1998||May 7, 2002||Kabushiki Kaisha Toshiba||Data recording medium, data recording method and data reproducing method|
|US7082092 *||Apr 24, 2002||Jul 25, 2006||Koninklijke Philips Electronics N.V.||Device and method for recording information|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7487178 *||Oct 5, 2005||Feb 3, 2009||International Business Machines Corporation||System and method for providing an object to support data structures in worm storage|
|US8140602||Oct 21, 2008||Mar 20, 2012||International Business Machines Corporation||Providing an object to support data structures in worm storage|
|U.S. Classification||369/275.3, 369/59.25, G9B/27.043, G9B/27.05, G9B/19.014, G9B/19.005, G9B/27.012|
|International Classification||G06F3/06, G11B27/19, G11B27/00, G11B23/28, G11B19/06, G11B20/18, G11B20/00, G11B7/0037, G11B19/04, G11B27/32, G11B20/12, G11B27/034|
|Cooperative Classification||G11B2020/1278, G11B20/1803, G11B27/329, G11B20/00152, G11B20/1816, G11B2020/1265, G11B20/1252, G11B27/32, G11B19/06, G11B7/00745, G11B2220/216, G11B27/19, G11B23/28, G11B19/04, G11B7/0037, G11B20/00086, G11B20/00702, G11B27/322, G11B2220/20, G11B20/00695, G11B2220/2537, G11B27/034, G11B23/284, G11B20/1217|
|European Classification||G11B20/12D, G11B20/00P9C, G11B20/00P9B, G11B7/007S, G11B27/32, G11B27/19, G11B20/00P2B, G11B20/12D6, G11B27/32B, G11B27/32D2, G11B19/06, G11B27/034, G11B19/04|