|Publication number||USRE38621 E1|
|Application number||US 09/521,187|
|Publication date||Oct 12, 2004|
|Filing date||Mar 3, 2000|
|Priority date||Mar 19, 1994|
|Also published as||CN1101582C, CN1115076A, CN1197060C, CN1305183A, DE69531265D1, DE69531265T2, DE69535027D1, DE69535027T2, EP0673034A2, EP0673034A3, EP0673034B1, EP1336963A2, EP1336963A3, EP1336963B1, US5592450, US5596565, US5734787, USRE37327, USRE38481|
|Publication number||09521187, 521187, US RE38621 E1, US RE38621E1, US-E1-RE38621, USRE38621 E1, USRE38621E1|
|Inventors||Jun Yonemitsu, Ryuichi Iwamura, Shunji Yoshimura, Makoto Kawamura|
|Original Assignee||Sony Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (22), Classifications (107), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The invention relates to a novel optical disk and, more particularly, to that disk, to a method of recording and reading information on the disk and to apparatus for carrying out that method.
Optical disks have been used as mass storage devices for computer applications, and such optical disks are known as CD-ROMs. The disk which is used as the CD-ROM is modeled after the standard compact disk (CD) that has been developed for audio applications and is basically an audio CD with various improvements and refinements particularly adapted for computer applications. Using such a CD as a standard, the CD-ROM has a data storage capacity of about 600 Mbytes. By using audio CD technology at its basis, the, CD-ROM and its disk drive have become relatively inexpensive and are quite popular.
However, since conventional audio CDs with their inherent format and storage capacity have been adapted for CD-ROMS, it has heretofore been difficult to improve the data storage capacity. In typical computer applications, a capacity of 600 Mbytes has been found to be insufficient.
Also, the data transfer rate that can be obtained from audio CDs generally is less than 1.4 Mbits/sec (Mbps). However, computer applications generally require a transfer rate far in excess of 1.4 Mbps; but it is difficult to attain a faster transfer rate with conventional CD-ROMS.
Yet another disadvantage associated with conventional CD-ROMs, and which is due to the fact that the audio CD format has been adapted for computer applications, is the relatively long access time associated with accessing a particular location on the disk. Typically, relatively long strings of data are read from audio CDs, whereas computer applications often require accessing in arbitrary location to read a relatively small amount of data therefrom. For example, accessing a particular sector may take too much time for the CD controller to identify which sector is being read by the optical pick-up.
A still further difficulty associated with CD-ROMs, and which also is attributed to the fact that such CD-ROMs are based upon audio CD technology, is the error correcting ability thereof. When audio data is reproduced from an audio CD, errors that cannot be corrected nevertheless can be concealed by using interpolation based upon the high correlation of the audio information that is played back. However, in compute applications, interpolation often cannot be used to conceal errors because of the low correlation of such data. Hence, the data is recorded on a CD-ROM must be encoded and modulated in a form exhibiting high error correcting ability. Heretofore, data has been recorded on a CD-ROM in a conventional cross interleave. Reed-Solomon code (CIRC) plus a so-called block completion error correction code. However, the block completion code generally takes a relatively long amount of time to decode the data, and more importantly, its error correction ability is believed to be insufficient in the event that multiple errors are present in a block. Since two error correction code (ECC) techniques are used for a CD-ROM, whereas only one ECC technique is used for an audio CD (namely, the CIRC technique), a greater amount of non-data information must be recorded on the CD-ROM to effect such error correction, and this non-data information is referred to as a “redundant” data. In an attempt to improve the error correction ability of a CD-ROM, the amount of redundancy that must be recorded is substantially increased.
Also, it is desirable to provide a standardized optical disk with the additional capability of having digital video information recorded thereon in a data-compressed format, such as MPEG-compressed video data and compressed audio data (or PCM audio data) that can be used as a digital video disk (DVD). But there currently are different MPEG compression techniques, or formats, available and more may be developed in the future. It is difficult to play back a video program from a DVD if the MPEG format that had been used to record that video program is not readily determined; and this problem is compounded if one DVD has recorded thereon different video programs exhibiting different MPEG formats as well as different audio formats.
Therefor, it is an object of the present invention to provide an improved optical disk having particular use as a DVD or CD-ROM which overcomes the aforenoted difficulties and disadvantages associated with CD-ROMs for which similar uses have been attempted heretofore.
Another object of this invention is to provide an optical disk which exhibits a higher access speed, thereby permitting quick access of arbitrary locations, such as sectors, to be accessed quickly.
A further object of this invention is to provide an improved optical disk having a higher transfer rate than the transfer rate associated with CD-ROMs heretofore used.
A further object of this invention is to improve the accessibility of different segments of video information, such as chapters, recorded on an optical disk, thereby making it more advantageous for use as a CD-ROM or as a DVD.
An additional object is to provide an improved optical disk which stores data with reduced redundancy.
Still another object of this invention is to provide an improved recording format for an optical disk which enhances the ability to identify and access the video information recorded thereon.
Another object of this invention is to provide an optical disk having a substantially improved recording density, thereby facilitating use of the disk as a CD-ROM or a DVD.
A further object of this invention is to provide an improved optical disk having video and audio data recorded in chapters, with each chapter being uniquely identified for quick access thereto and with the particular format of the recorded data being identified to permit compatible data recovery.
Various other objects, advantageous and features of the present invention will become readily apparent from the ensuing detailed description, and the novel features will be particularly pointed out in the appended claims.
In accordance with this invention, an optical disk, a method and apparatus for recording that disk and a method and apparatus for reading data from that disk are provided. The disk has a diameter of less than 140 mm, a thickness of 1.2 mmħ0.1 mm, and a plurality of record tracks exhibiting a track pitch in the range between 0.646 μm and 1.05 μm with data recorded in those tracks as embossed pits. The tracks are divided into a lead-in area, a program area and a lead-out are, with table of content (TOC) information being recorded in at least one TOC track in the lead-in area and user information recorded in a plurality of user tracks in the program area. The user data preferably comprises MPEG-compressed video data and compressed audio data, encoded in any one of different MPEG formats and audio formats (such as PCM audio), and, advantageously, each track contains a chapter of user information. Application table of contents (ATOC) information is recorded in the program area to identify various parameters of the chapters of user information for accessing and using that information. The data (TOC, ATOC and user information) is encoded in a long distance error correction code having at least eight parity symbols, the encoded data being modulated and recorded on the disk. Preferably, the data is modulated as run length limited (RLL) data.
In the preferred embodiment, the data is recorded with a linear density in the range between 0.237 μm per bit and 0.378 μm per bit.
As one aspect of this invention, the ATOC information comprises fields of chapter data, each field being associated with a respective chapter and including information used to identify the location of that chapter, its name, the different formats of MPEG and audio compression exhibited by the video and audio data recorded in that chapter, and the locations in that chapter at which representative video pictures (useful for quick display) are recorded.
The error correction code used with the present invention preferably is a long distance code having at least eight parity symbols. ECC techniques which have been used heretofore have relied upon so-called short distance codes in which a block of data is divided into two sub-blocks, each sub-block being associated with a number of parity symbols, such as 4 parity symbols. It is known, however, that 4 parity symbols may be used to correct 4 data symbols, and if 4 data symbols in each sub-block are erroneous, the total number of 8 erroneous data symbols can be corrected. But, if one sub-block contains 5 erroneous data symbols, whereas the other sub-block contains 3 erroneous data symbols, use of the short distance code may be effective to correct only 4 data symbols in the one sub-block, thus permitting a total error correction of 7 data symbols. But, in the long distance code, the block of data is not sub-divided; and as a result, all 8 erroneous data symbols, if present in the long distance coded data, can be corrected.
As another feature, the RLL code that is used preferably converts 8 bits of input data into 16 bits of data for recording (referred to as 16 channel bits) with no margin bits provided between successive 16-bit symbols. In RLL codes used heretofore, 8 data bits are converted into 14 channel bits and three margin bits are inserted between successive 14-bit symbols. Thus, the present invention achieves a reduction in redundancy.
The following detailed description, given by way of example and not intended to limit the present invention solely thereto, will best understood in conjunction with the accompanying drawings in which:
FIG. 1 is a block diagram of the preferred technique by which optical disks are made in accordance with the present invention;
FIG. 2 is a block diagram of apparatus incorporated in the present invention for reproducing data from the optical disk that has been made in accordance with the technique shown in FIG. 1;
FIG. 3 is a schematic representation of the recording areas for the disk made by the technique shown in FIG. 1;
FIGS. 4A and 4B are schematic representations showing the recording areas of FIG. 3 in greater detail;
FIG. 5 is a schematic representation of another format of the recording areas;
FIG. 6 is a schematic representation of still another format of the recording areas;
FIG. 7 is a schematic representation of yet another format of the recording areas;
FIG. 8 is a tabular representation of a portion of the information recorded in the TOC region of the disk;
FIG. 9 is a tabular representation of another portion of the data recorded in the TOC region;
FIGS. 10A and 10B are schematic representations of a sector of data recorded on the disk;
FIGS. 11A-11E are tabular representations of different types of subcode data that may be recorded in a sector;
FIG. 12 is a tabular representation of copyright data that may be recorded as subcode information in a sector;
FIG. 13 is a tabular representation of application ID information that may be recorded as the subcode information in a sector;
FIG. 14 is a tabular representation of time-code data that may be recorded as the subcode information in a sector;
FIG. 15 is a tabular representation of picture-type data that may be recorded as the subcode information in a sector;
FIG. 16 is a tabular representation of ECC type data that may be included in the TOC information recorded in the TOC regions;
FIG. 17 is a schematic representation of one frame of error correction encoded data, identified as a C1 code word;
FIG. 18 is a schematic representation of the long distance error correction code format used with the present invention;
FIG. 19 is a schematic representation of a short distance error correction code format that could be used with the present invention;
FIG. 20 is a schematic representation of the sequential order of rearranged data symbols after those symbols have been played back from the disk;
FIG. 21 is a schematic representation of a sector of data that has been error correction encoded;
FIG. 22 is a schematic representation of a block code of error correction encoded data in the long distance format;
FIG. 23 is a schematic representation of a block code of error correction encoded data in the short distance format;
FIG. 24 is a schematic representation of a string of data symbols exhibiting EFM modulation;
FIG. 25 is a flowchart explaining how margin bits are selected in the EFM modulated data shown in FIG. 24;
FIG. 26 is a block diagram of an EFM modulator that can be used to produce the data string shown in FIG. 24;
FIG. 27 is a schematic representation of a frame of EFM modulated data;
FIG. 28 is a table which explains how margin bits are selected/inhibited when forming the string of EFM data shown in FIG. 24;
FIGS. 29A-29D are explanatory waveforms which are useful in understanding how margin bits are selected;
FIG. 30 is a block diagram of a modulator that may be used with the present invention;
FIG. 31 is a block diagram of a demodulator that may be used within the present invention;
FIG. 32 is a block diagram of apparatus which may be used to supply data for the recording technique shown in FIG. 1;
FIG. 33 is a block diagram of data recovery apparatus that may be used with the playback apparatus shown in FIG. 2;
FIG. 34 is a schematic representation of a format of the recording areas showing use of the optical disk as a DVD and also as a CD-ROM, with user data being recorded as chapter of, for example, video programs, and with application table of contents (ATOC) data related to those chapters being recorded in the program area of the disk;
FIG. 35 is a tabular representation of ATOC information recorded in an application TOC region in the program area of the disk;
FIG. 36 is a tabular representation of the “disc information” shown in FIG. 35;
FIG. 37 is a tabular representation of the “chapter information” shown in FIG. 35;
FIG. 38 is a tabular representation of the “name field” shown in FIG. 35;
FIG. 39 is a tabular representation of the “pool of stream parameters” shown in FIG. 35;
FIG. 40 is a tabular representation of the “pool of entry point information” shown in FIG. 35;
FIG. 41 is a tabular representation of each stream parameter field included in the pool of stream parameters shown in FIG. 39;
FIG. 42 is a tabular representation of each entry point field included in the pool of entry point information shown in FIG. 40;
FIG. 43 is a tabular representation of the stream type data that may be recorded in each stream parameter field shown in FIG. 41; and
FIG. 44 is a tabular representation of the chapter category data that may be recorded in the chapter information field shown in FIG. 37.
The present invention records different types of data on an optical disk, preferably for use as a CD-ROM but also adapted for use as a digital video disk (DVD). Such data may be file data or application data to be used by a computer, or it may comprise video data which sometimes is referred to herein as motion picture data which includes image information and audio information and which preferably is compressed in accordance with the various conventional video data compression standards, or formats such as those known MPEG-1, MPEG-2, or when still video pictures are recorded, JPEG. It will be appreciated, therefore, that the information on the disk admits of “multimedia” applications.
Before describing the technique used to record data on the optical disk, a brief description is provided of the disk itself. The physical parameters of the optical disk used with the present invention are quite similar to the conventional audio CD; and for this reason, a drawing figure of the disk is not provided. Nevertheless, it will be appreciated that the diameter of the disk is 140 mm or less, preferably 120 mm or 135 mm. Data is recorded in tracks; and will be described in greater detail, having a track pitch in the range between 0.646 μm and 1.05 μm, and preferably in the range of 0.7 to 0.9 μm. Like audio CD data, the data recorded on the optical disk is in the form of embossed pits having a linear density in the range between 0.237 μm per bit and 0.387 μm per bit, although this range could be in the range of 0.3 μm to 0.4 μm per bit. Data is recorded in that portion of the disk having a radius from 20 mm to 65 mm. The disk, whose thickness is 1.2 mmħ0.1 mm, is intended to be driven for a playback operation such that its linear velocity is in the range of 3.3 m to 5.3 m per second.
As a result of the linear density and track pitch of the disk, information is optically read from the disk by a pick-up head which projects a light beam of wavelength λ through a lens having a numerical aperture NA such that the projected beam exhibits a spatial frequency 1, where 1=λ/(2NA). The light source for the optical pick-up preferably is a laser beam whose wave length is λ=635 nm, this laser beam being projected through a lens whose numerical aperture is NA=0.52, resulting in the spatial frequency 1=611 nm.
Typical examples of the physical parameters associated with the optical disk are as following:
Disk diameter=120 mm.
Program area=23 mm to 58 mm.
Track pitch=0.84 μm.
Linear density=0.307 μm.
This results in a data storage capacity of 4.4 Gbytes.
One proposed structure for recording data on the optical disk is known as the EFM Plus frame (EFM refers to eight-to-fourteen modulation). An EFM Plus frame is formed of 85 data symbols (each symbols is a 16-bit representation of an 8-bit byte) plus two synchronizing symbols thus consisting of 87 16-bit symbols. One sector is comprised of 14×2 EFM plus frames. But, the amount of user information that is present in a sector, that is, the amount of information which contains useful data and thus exclude sector header information, error detection code (EPC) information, et cetera, is 2048 symbols. Accordingly, the efficiency of the EFM Plus format may be calculated as:
That is, the efficiency of the EFM Plus format is approximately 84%, which means that 84% of all of the data that is recorded in a sector is useful data. Therefore, if the storage capacity of the optical disk is 4.4 Gbytes, as mentioned above, the amount of user data that can be stored on the disk is 84%×4.4 Gbytes=3.7 Gbytes.
Of course, if the track pitch is varied and/or if the linear density of the embossed pits is varied, the storage capacity of the disk likewise is varied. For example, if the track pitch is on the order of about 0.646 μm, the storage capacity of the disk may be on the order of about 6.8 Gbytes, whereas if the track pitch is on the order of about 1.05 μm, the storage capacity is on the order of about 4.2 Gbytes. As a practical matter, however, the spatial frequency of the pick-up beam determines the minimum track pitch and minimum linear density because it is desirable that the track pitch be no less than the spatial frequency of the pick-up beam and the linear density be no less than one-half the spatial frequency of the pick-up beam.
When compared to the audio CD, the linear density of the recorded data of the optical disk used in the present invention is approximately 1.7 times the linear density of the audio CD and the recording capacity of the optical disk used with the present invention is approximately 5.5 times the recording capacity of the audio CD. The optical disk of the present invention is driven to exhibit a linear velocity of approximately four times the linear velocity of the audio CD and the data transfer rate of the optical disk of the present invention is approximately 9 Mbps, which is about six times the data transfer rate of the audio CD.
With the foregoing in mind, reference is made to FIG. 1 which is a block diagram of the technique used to make an optical disk of the type that has just been described. An input terminal 121 is supplied with user data to be recorded, this data being formed of, for example, multiplexed video and audio information, title data and sub-information such as, but not limited to, computer files, character data, graphic information, et cetera. The data supplied to input terminal 121 is produced by the apparatus shown in FIG. 32 and will be described below.
The user data is coupled to a change-over switch 124 which also is adapted to receive table of content (TOC) information supplied to the switch from an input terminal 122 via a TOC encoder 125. The TOC information identifies various parameters of the disk which are used for accurate reproduction of the user information recorded thereon; and the TOC information also includes data related to the user information per se, such as information that is helpful in rapidly accessing the user information recorded in particular tracks. The structure of the TOC information is described below.
Switch 124 selectively couples user data supplied at input terminal 121 and encoded TOC data supplied at input terminal 122 to an error detection code (EDC) adder 127. As will be described, TOC information is recorded on one portion of the disk and user data is recorded on another portion; and switch 124 selects either the TOC information or the user data at the appropriate times. As will be described below in conjunction with, for example, FIG. 21, the error detection code is added at the end of a sector of user data or TOC information; and adder 127 serves to produce the error detection code after a sector of data has been received and then adds the error detection code to the end of the sector of data. In the preferred embodiment, a sector is comprised of 2048 bits of useful data, plus parity bytes, plus sector header data, plus a number of “reserved” byes, plus the EDC code.
A sector header adder 128 is adapted to add a sector header to each sector of user information supplied thereto by way of EDC adder 127. As will be described below in conjunction with FIG. 10, a sector header includes a synchronizing pattern and information useful to rapidly identify access the sector. Such information, particularly in sectors containing user data, includes subcode information which is coupled to the sector header adder by way of a sector header encoder 129, the latter operating to encode subcode information supplied thereto by way of input terminal 123. Such subcode information is generated by a suitable source and, as will be described further below in conjunction with FIG. 11, is used to provide helpful identifying and control information related to the user data that is recorded on the disk. For example, the subcode information identifies the track number in which the sector which contains this subcode information is recorded, copyright management information which determines whether the data reproduced from the disk, such as video data, may be copied, application ID information which designates the particular user-application for the data recorded in the sector, time code data which represents time information at which the user data is recorded, and information relating to video pictures that may be recorded on the disk, such as the distance, or separation, between a video picture recorded in this sector and the next-following and the next-preceding video pictures. A system controller 110 controls sector header encoder 129 to make certain that the proper subcode information and other sector header information (as shown in FIG. 10) is placed in the proper data location for proper recording in a user track.
User data, including the sector header added thereto by reason of sector header adder 128, is subjected to error correction encoding carried out by an ECC circuit 132 in combination with a memory 131 and a memory control section 133, the latter being controlled by system controller 110. An example of ECC encoding that may be used with the present invention, subject to modification so as to be applicable to the data recorded on the optical data, is described in U.S. Pat. No. Re. 31,666. In one embodiment of the present invention, the ECC encoding produced by circuit 132 is convolution coding and is described in greater detail below in conjunction with FIG. 17. It is sufficient for an understanding of FIG. 1 simply to point out that the ECC encoding assembles a frame of data bytes or symbols, referred to as a C2 code word formed of, for example, 116 bytes or symbols, and generates C2 parity bytes as a function of a respective data byte or symbol in a predetermined number of C2 code words. For examples if the data bytes or symbols in each C2 code word exhibit the sequence 1, 2, . . . 116, a C2 parity byte, or symbol, may be produced by combining byte 1 from C2 code word C2 1 and byte 2 from C2 2. Another C2 parity byte may be produced by combining the third byte of C2 code word C2 3 and the fourth byte of C2 4. In this manner, the C2 parity bytes are generated by a cross-interleave technique; and as an example, 12 such C2 parity bytes are added to the C2 code word C2 1, even though such C2 parity bytes relative to data bytes included in other C2 words. Then, C1 parity bytes are generated for the C2 word (such as C2 1) to which has been added the C2 parity bytes, resulting in what is referred herein as a C1 code word (such as C1 1). The resultant C1 code word, consisting of 116 data bytes, plus 12 C2 parity bytes, plus 8 C1 parity bytes is stored in memory 131.
The sequential order of the data bytes in the C1 code words stored in memory 131 is rearranged by, for example, delaying the odd bytes so as to form an odd group of data bytes and an even group of data bytes. Since each group consists of only one-half of the data bytes included in the C1 code word, an odd group of data bytes of one C1 code word is combined with an even group of data bytes of the next-following C1 code word, thus forming a disarranged order of bytes. This disarranged order improves the burst error immunity of the ECC encoded data. The disarranged order of the ECC-encoder bytes is supplied from memory 131 to a modulator 140 which, preferably, carries out 8-to-16 modulation, although 8-to-14 (EFM) modulation could be used, if desired.
Memory controller 133 supplies to memory 131 the necessary read and write addresses to enable the generation of the C2 parity bytes in cross-interleaved form and also to rearrange the sequential order of the data bytes into the aforementioned disarranged order.
In the preferred embodiment of the ECC encoding technique, a long distance code, also known as the L format, is used. The L format results in C1 code words that are arranged as shown in FIG. 18, described further below. If desired, the ECC-encoded data may exhibit a short distance code or S format, such as is depicted in FIG. 19, described below. Depending upon whether the L format or the S format is selected, system controller 110 controls the memory controller 113 such that the read and write operations of memory 131 permit the data bytes to be ECC encoded in either the L format or the S format.
Modulator 140 serves to convert 8-bit bytes supplied thereto from memory 131 into 16-bit symbols. Each symbol is run length limited (RLL), as will be described. It will be appreciated that, by generating 16-bit symbols, the accumulated digital sum value (DSV), which is a function of the run length of the digital signal, that is, the number of consecutive 0s or the number of consecutive 1s, is limited to permit the DC component which is produced as a function of such consecutive 0s or 1s, to retain at or close to 0. By suppressing the DC, or lower frequency component of the digital signal that is recorded, errors that otherwise would be present when that digit signal is reproduced are minimized.
Modulator 140 thus produces a recording signal which is coupled to cutting apparatus 150. This apparatus is used to make an original disk from which one or more mother disks may be produced and from which copies may be stamped for distribution to end users. That is, such stamped disks constitute the CD ROMs.
In one embodiment, the cutting apparatus includes an electro-optical modulator 151 which relies upon the so-called Pockels effect to modulate a light beam that is used to “cut” an original disk. This original disk is used by a mastering apparatus 160 to produce a master of the original disk. The mastering apparatus relies upon conventional techniques, such as development and vacuum deposition, to produce a plurality of mother disks. Such mother disks are used in stampers which ejection mold copies that subsequently are packaged and distributed. Blocks 171 and 172 in FIG. 1 are intended to represent the injection molding and packaging apparatus in manufacturing such disks. The completed disk is depicted as disk 100.
The technique used to reproduce the information recorded on optical disk 100 now will be described in conjunction with the block diagram shown in FIG. 2. Here, the disk is optically read by an optical pickup 212 which projects a light beam, such as a laser beam having the spatial frequency 1=λ/2 na, this beam being reflected from the disk and detected by a conventional pickup detector. The detector converts the reflected light beam to a corresponding electrical signal which is supplied from pickup 212 to a waveform equalizer 213 and thence to a phase locked loop clock reproducing circuit 214 and to a demodulator 215. Transitions in the recovered electrical signal are used to synchronize the phase locked loop to extract therefrom the clock signal which was used to record data on the disk. The extracted clock is coupled to demodulator 215 which performs RLL demodulation that is described in greater detail below in conjunction with FIG. 31. Suffice it to say that if data is recorded on disk 100 as 16-bit symbols, demodulator 215 demodulates each 16-bit symbol to an 8-bit symbol or a byte.
The demodulated data reproduced from disk 100 is supplied to a ring buffer 217. The clock signal extracted by phase locked loop clock reproducing circuit 214 also is supplied to the ring buffer to permit the “clocking in” of the demodulated data. The demodulated data also is supplied from demodulator 215 to sector header detector 221 which functions to detect and separable the sector header from the demodulated data.
Ring buffer 217 is coupled to an error correcting circuit 216 which functions to correct errors that may be present in the data stored in the ring buffer. For example, when data is recorded in the long distance code formed of, for example, C1 code words, each comprised of 136 symbols including 116 symbols representing data (i.e. C2 data). 12 symbols representing C2 parity and 8 symbols representing C1 parity, error correcting circuit 216 first uses the C1 parity symbols to correct errors that may be present in the C1 word. A corrected C1 word is rewritten into ring buffer 217; and then the error correcting circuit uses the C2 parity symbols for further error correction. Those data symbols which are subjected to further error correction are rewritten into the ring buffer as corrected data. Reference is made to aforementioned U.S. Pat. No. Re. 31,666 for an example of error correction.
In the event that an error in the sector header is sensed, error correcting circuit 216 uses the C1 parity symbols to correct the sector header, and the correction sector header is rewritten into a sector header detector 221. Advantageously, the C2 parity symbols need not be used for sector header error correction.
As mentioned above, the input data symbols supplied for error correction encoding exhibit a given sequence, but the error correction encoded symbols are rearranged in a different sequence for recording. In one arrangement, the odd and even symbols are separated and the odd symbols of a C1 code word are recorded in an odd group while the even symbols of that C1 code word are recorded in an even group. Alternatively, odd and even symbols of different C1 code words may be grouped together for recording. Still further, other sequential arrangements may be used to record the data. During playback, error correcting circuit 216 and ring buffer 217 cooperate to return the recovered data symbols to their original, given sequence. That is, the data symbols may be thought of as being recorded in a disarranged order and the combination of the error correcting circuit and ring buffer operate to rearrange the order of the symbols in a C1 code word to its properly arranged sequence.
Error corrected data stored in ring buffer 217 is coupled to error detecting circuit 222 which uses the EDC bits added to the recorded data by EDC adder 127 (FIG. 1) to detect an uncorrectable error. In the event that data cannot be corrected, EDC detector 222 provides a suitable indication, such as an error flag in a particular uncorrectable byte or an error flag in an uncorrectable C1 code word, and the error corrected data, either with or without such error flags, as the case may be, is coupled to output terminal 224.
In addition, TOC information that is recovered from disk 100, after being error corrected by error correcting circuit 216 and error detected by EDC detector 222, is coupled to a TOC memory 223 for use in controlling a data playback operation and for permitting rapid access to user data. The TOC information stored in memory 223, as well as sector information separated from the reproduced data by sector header detector 221 are coupled to a system controller 230. The system controller responds to the user-generated instructions supplied thereto by a user interface 231 to control disk drive 225 so as to access desired tracks and desired sectors in those tracks, thereby reproducing user data requested by the user. For example, the TOC information stored in TOC memory 223 may include data representing the location of the beginning of each track; and system controller 230 responds to a user-generated request to access a particular track to control disk drive 225 such that the requirement track is located and accessed. Particular identifying information representing the data in the accessed track may be recovered and supplied to system controller 230 by sector header detector 221 so that rapid access to such data may be achieved. A further description of the TOC information and sector information useful for controlling the disk drive in the manner broadly mentioned above is discussed in greater detail below.
It will be appreciated from the ensuing discussion of FIGS. 10 and 21 that sector header information that is recovered from the disk may be error corrected by using the C1 parity symbols indicated in the same C1 code word as the sector header. There is a high probability that any errors that may be present in the sector header can be corrected by using the C1 parity symbols only. Since a C1 code word contains C2 parity symbols that are generated from the data symbols included in different C1 code words, sector information is quickly detected quickly by not waiting for all of the C2 parity symbols to be assembled before correcting the sector header. Thus, position information of a sector, which is included in the sector header as a sector address, is detected, thus facilitating rapid access to a desired sector. This is to be compared with a conventional CD-ROM wherein sector header information is interleaved in several C1 code words, thus requiring the recovery and error correction of all of those C1 code words before the sector header data can be assembled and interpreted.
FIG. 3 is a schematic representation of the manner in which the recording surface of disk 100 is divided into separate areas, referred to as the lead-in area, the program area and the lead-out area. FIG. 3 also identifies the lead sector addresses of the program area and the lead-out area. In the illustrated embodiment, the sectors included in the lead-in area exhibit negative sector addresses ending with the sector address −1 which, in hexadecimal notation is 0×FFFFFF. The sector address of the first sector in the program area is identified as address 0. As indicated, the length or duration of the program area is dependent upon the amount of data recorded therein and, thus, the address of the last sector recorded in the program area is variable. It is appreciated, therefore, that the first sector address of the lead-out area is variable and is dependent upon the length of the program area.
One embodiment of the disk configuration shown broadly in FIG. 3 is schematically illustrated in FIGS. 4A and 4B. Here, the TOC region, which is comprised of one or more TOC tracks, is disposed in the lead-in area and TOC information is recorded in sectors identified as −32 to −1 (FIG. 4A). These 32 sectors of TOC information occupy a fixed position, such as a single TOC track, in the lead-in area. In FIG. 4B duplicate TOC regions are disposed in the lead-in area, together with other data that may be used for different purposes. The program area shown in FIGS. 4A and 4B is comprised of N tracks, where N is variable. The sector address of the first track of the program area is identified as address 0; and the total number of tracks included in the program area is dependent upon the amount of information stored on the disk, and since the number of sectors included in each track likewise is variable, the sector addresses of the lead sectors of tracks 2, 3, . . . N are variable. Of course, the lead-out area commences after the Nth track is recorded.
In one embodiment, the data recorded on a given disk may admit of different applications. However, it is preferred that all of the data recorded in a respective track admit of the same application.
FIG. 5 illustrates another disk configuration wherein TOC information is recorded in the lead-in area from, for example, sector −32 to sector −1, as was the case in FIG. 4, and a copy of the TOC information is recorded in the program area. In the example shown in FIG. 5, the copy of the TOC information is recorded in at least one track whose lead sector is, for example, sector number 1024. Since the size of the TOC region is fixed at 32 sectors, as will be described, the laser sector of the copied TOC region is sector 1055; and the lead sector of the next-following user data track is identified as sector 1056. One reason for providing a copy of the TOC information in the program area is that some computer applications do not easily recognize data recorded in sectors having negative addresses (such as sectors −32 to −1 of the TOC information recorded in the lead-in area).
Still another embodiment of the data configuration recorded on the optical disk is illustrated in FIG. 6, wherein the TOC region is provided in the program area at sectors 0 to 31. Here, the recording of TOC information in the program area differs from the recording of TOC information in the program area of FIG. 5 in that the FIG. 6 arrangement does not include a copy of the TOC information. Nevertheless, since the TOC information is recorded in positive sector addresses in FIG. 6, the possibility of mis-interpretation due to the difficulty of recognizing negative sector addresses by a computer is obviated.
In the embodiments of FIGS. 5 and 6 wherein TOC information is recorded in the program area, it is appreciated that the TOC region is segregated from data files which are particularly relevant to the computer with which the optical disk is to be used. FIG. 7 illustrates a still further example of the data configuration recorded on the optical disk and illustrates the TOC region to be located from sector address 32 to sector address 63. In this arrangement, information recorded in sectors 0 to 31 is reserved for computer files that are particularly applicable to the computer system with which the optical disk is to be used. Thus, in the embodiments of FIGS. 5, 6 and 7 wherein TOC information is recorded in the program area, such TOC information is segregated from and, thus, does not interfere with file system data that may be recorded on the disk. Such file system data may occupy several sectors or several tens of sectors; and since the TOC information is recorded in a fixed number of sectors so as to occupy a fixed TOC region, there is no interference by the TOC information with such file system data.
As mentioned above, in the preferred embodiment TOC information is recorded in 32 sectors. Preferably, although not necessarily, each sector is comprised of 2048 bytes and an example of the TOC information recorded in a TOC region is set out in the following Table 1.
Table of Contents Information
Track Information (1-st Track)
Track Information (2-nd Track)
Track Information (3-rd Track)
Track Information (N-th Track)
From the foregoing table, it is appreciated that the TOC information includes one sector dedicated to disk information, described more particularly with respect to Table 2, and up to 31 sectors in which track information (see Table 3) is recorded. The TOC region also includes a reserved area for the recording of information that may be useful in the future. In a practical adaptation of the optical disk of the present invention, user information may be recorded in N tracks where, for example, N=256. The track information which is recorded in the TOC region relates to the data that is recorded only in a corresponding track, as will be described in conjunction with Table 3.
The data which constitutes the disk information recorded in the TOC region is shown in the following Table 2:
Reserved for Disk Size
Lead Out Sector Address
Reserved for Multi Session Parameters
Reserved for Writable Parameters
Total Volume Number
Reserved for Application ID Strings
Disk Title in English/ISO646
Local Language Country Code
Length of Disk Title in Local Lan (=N)
Disk Title in Local Lang
First Track Number
No. of Track Entry
The fields which identify the disk information are described more particularly as follows:
This field, comprised of 8 bytes, contains a character string that identifies the data structure recorded on the disk, including the data structure which is used to represent TOC information, the data structure used to represent track information and the data structure of a sector. For example, if the character string is “HD-CD001”, the data structure recorded on the disk is of the type illustrated in FIG. 4, the data structure used to represent TOC information is as shown in Table 1, the data structure used to represent track information is shown in Tables 2 and 3 and the data structure of the sectors of, for example, the user data tracks, is as shown in Table 4 (to be described). Different data structures may be identified by the character string “HD-CD002”, “HD-CD003”, etc. The particular character string which is recorded in this field is detected by the reproducing apparatus which permits proper interpretation of the played back data consistent with the sensed data structure.
This 1-byte data identifiers the type of disk as, for example, a read only disk, a write once read many (WORM) disk or an erasable disk (such as the writable optical disk known as the “Main” disc).
Reserved For Disk Size
This 1-byte field is used to identify the size of the optical disk. For example, a disk diameter of 120 millimeters may be identified by a byte whose value is “1”, a disk whose diameter is 80 millimeters may be identified by a byte whose value is “2”, and so on. In addition or, alternatively, this field may be used to identify the storage capacity of the disk.
Lead Out Sector Address
This 3-byte field identifies the address of the first sector in the lead-out area.
Reserved For Multisession and Writable Parameters
These two-fields, each formed of 20 bytes, store information which is particularly useful for erasable disks or for WORM disks and is not further described herein.
This 1-byte data field is used when several disks constitute a collection of data for a particular application. For example, if the collection includes 2, 3, 4, etc. disks, this field identifies which one of those disks is the present disk.
Total Volume Number
This 1-byte field identifies the total number of disks which constitute the collection in which the present disk is included.
This 16-byte field is used to identify the type of information or program that is recorded on the disk. Such identification constitutes the “catalog number” and is represented as UPC/EAN/JAN code presently used to identify various goods.
Reserved For Application ID Strings
This 8-byte field is intended to identify the particular user application for this disk medium. At present, this field is not used.
Disk Title in English/IS0646
This 16-byte field stores the title of the disk in the English language, as represented by the ISO646 standard. Although the actual title of the disk may be in another language, its English translation or a corresponding English identification of that title is recorded in this field. In other embodiments, the field may contain a lesser or greater number of bytes so as to accommodate English titles of lesser or greater length.
Local Language Country Code
This 3-byte field is intended to identify the actual language of the title of the disk. For example, if the actual title of the disk is in Japanese, this field records the “local language country” as Japan. If the title is in French, this field records the “local language country” as France. The code recorded in this field may exhibit a numerical value corresponding to a particular country or, alternatively, the field may be as prescribed by the ISO3166 standard. If it is desired not to utilize this field, the character string recorded therein may be 0×FFFFFF.
Length of Disk Title in Local Language
This 1-byte field identifies the number of bytes that are used in the “Disk Title In Local Language” field (to be described) to represent the title of the disk in the local language. If the actual disk title is not recorded in a language other than English, the “Disk Title In Local Language” field is left blank and the numerical value of this “Length Of Disk Title In Local Language” field is 0.
Disk Title In Local Language
This N-byte field represents the actual title of the disk in the local language. It is expected that different languages will adopt different standards to represent disk titles, and such local language standards are expected to be used as the data recorded in this field. It is appreciated that the number of bytes which constitute this field is variable.
First Track Number
This 1-byte field identifies the number of the track which constitutes the first track that contains user information. For example, if the TOC information is recorded in a single track, and if this single track is identified as track 0 in the program area, then the number of the track which constitutes the “First Track Number” is 1.
Number of Track Entries
This 1-byte field identifies the total number of user tracks that are recorded. It is appreciated that if this field contains a single byte, a maximum of 256 user data tracks, that is, tracks which contain user information, may be recorded.
The data recorded in the track information fields of the TOC data shown in Table 1 now will be described in conjunction with the following Table 3:
Tune Code at Start Point
Mastering Date & Time
Reserved for Application ID Strings
the information recorded in each of the fields which constitute the track information of Table 3 now will be described in greater detail.
This 1-byte field identifies the number of the track represented by this track information. Since one byte is used to identify the track number, it is appreciated that a maximum of 256 user data tracks may be recorded. Of course, a single track number is used to identify a respective track, and no two tracks on this disk are identified by the same track number. Although it is preferred that the successive tracks are numbered sequentially, it also is appreciated that, if desired, each track number may be assigned a random number and this random number is identified by the “Track Number” field.
This 1-byte data identifies the error correction code which is used to encode the user data recorded in this track. For example, the ECC type may be either long distance error correction code, known as the L format, or short distance error correction code, known as the S format. The difference between the L format and the S format is described below.
This 1-byte data identifies the data transfer rate by which data is recovered from this track. For example, if a reference data transfer rage is 1.4 Mbps, the “Speed Setting” field may exhibit a value representing 1×this reference rate or 2×the reference rate or 4×the reference rate or 6×the reference rate. FIG. 8 is a tabular representation of this “Speed Setting” field; and it is appreciated that the data transfer rate need not be an integral multiple of the reference data transfer rate, as represented by the value “FF”. The byte value 0 for this field, as shown in FIG. 8, represents that real time read-out of data is not required. It is appreciated that computer data, as opposed to, for example, video data, does not require real time read-out. Hence, if computer data is recorded in the track identified by the “Track Number” field in Table 3, the value of the “Speed Setting” field is set to 0.
Start and End Sector Addresses (SA)
These 3-byte fields identify the address of the start sector of the track identified in the “Track Number” field and the address of the end sector of that track. Since the number of sectors included in a track is variable, the start and end sector addresses of a given track are not fixed. Hence, these fields are useful when carrying out a high speed access operation of a desired track.
Time Code At Start Point
This 4-byte field identifies a time code for the start sector in the track identified by the “Track Number” field. It will be appreciated that if the user information represents video data, such video data may be recorded with conventional time codes and the start sector of the track which contains such video data is recorded in this “Time Code At Start Point” field. If time codes are not recorded with the user information, this field may be left blank or may be provided with no data, such as the character code 0.
This 4-byte data represents the overall playback time for the program information that is recorded in the track identified by the “Track Number” field. For example, if the user information in this track is an audio program, the playing time for this track may be on the order of about 10 minutes. If the user information constitutes compressed video data, the playing time may be 2 or 3 or even up to 15 minutes.
Mastering Date and Time
This 7-byte field identifies the date and time of creation of the master disk from which this optical disk was made. FIG. 9 is a tabular representation of this field. If desired, this field may be replaced by null data represented by character code 0.
Reserved For Application ID Strings
This 8-byte field is intended to store information representative of the particular application for which the data record in the track identified by the “Track Number” field is to be used. This differs slightly from the “Application ID” field in Table 2 because the Table 2 field is intended to identify the type of application or use intended for the entire disk, whereas the “Application ID” field of Table 3 simply the identifies the type or use of the data recorded in a particular track on that disk.
Referring now to FIG. 10, there is illustrated a preferred embodiment of the data structure of a sector of user information. TOC information also is recorded in sectors, and the structure of such TOC sector is similar. The following Table 4 identifies the fields of the sectors shown in FIG. 10.
It is seen that a sector is comprised of a sector header which contains 24-bytes arranged in one embodiment as shown in FIG. 10A, followed by 2,048 bytes of user data, 4-bytes of error detection code (EDC) and 12-bytes which are reserved. Preferably, a number of sectors constitute a “cluster”, and as one example, a cluster is comprised of 8 sectors or 16 sectors, as may be determined by the preferred format.
A more detailed explanation of the different fields which constitute the sector shown in FIG. 10A now will be provided.
This 4-byte field is formed of a predetermined bit pattern which is readily detected and which is unique and distinctive from the data pattern included in any other field of a sector. The accurate detection of the sync pattern may be confirmed sensing errors which are interpreted from the information reproduced from the sector. If a large number of errors are detected continually, it is safely assumed that the sync pattern has not been accurately sensed. Alternatively, and preferably, the demodulator which is used to convert 16-bit symbols to 8-bit bytes (or, more generally, to convert an m-bit symbol to an n-bit byte) may include suitable conversion tables which are not operable to convert the sync pattern to a byte. The sync pattern is assumed to be present when the demodulator is unable to find an n-bit byte which corresponds to a received m-bit symbol.
Cyclic Redundancy Code (CRC)
This 2-byte field is derived from the subcode data, the cluster position data and the sector address and mode data included in the sector header. Such CRC data is used to correct errors that may be present in these fields.
This 5-byte field is described below.
This 1-byte field identifies the particular order in the cluster in which this sector is located. For example, if the cluster is formed of a 8 sectors, this field identifies the particular sector as the first, second, third, etc. sector in the cluster.
This 3-byte field constitutes the unique address for this sector. Since the address is represented as 3-bytes, a maximum of 64K sectors theoretically may be recorded. FIGS. 4-7 represent the sector addresses of different user data tracks.
Mode and Sub-Header
These fields are conventionally used in CD-ROMs and the data represent here is the same as that conventionally used in such CD-ROMs.
2,048 bytes of information are recorded in the user data field. For example, computer data, compressed video data, audio data and the like may be recorded. If video data is recorded, the MPEG standard may be used to compress that data, as described in standard ISO1381-1.
Error Detection Code
This 4-byte data is cyclic code which is added by EDC adder 127 (FIG. 1) and is used to enable the detection of an uncorrectable error in the sector.
FIG. 10B schematically illustrates another embodiment of a sector header, this one containing 20-bytes. The fields of the 20-byte sector header of FIG. 10B are similar to the fields of the sector header shown in FIG. 10A, and to avoid unnecessary duplicative explanation, are not further described.
A detailed discussion of the sub-code field now is provided in conjunction with FIGS. 11A-11E. It is appreciated that the sub-code field is comprised of two portions: a 1-byte address portion and a 4-byte data portion. The value of the address portion serves to identify the type of data that is recorded in the data portion. For example, and as shown in FIG. 11A, if the value of the address portion is 0, null or zero data is recorded in the data portion.
If the value of the address portion is 1, as shown in FIG. 11B, the data portion is provided with the following 1-byte information:
This data identifies the number of the track in which the sector containing this sub-code is recorded.
This byte exhibits the structure shown in FIG. 12 wherein a “1” bit represents the copying of the associated user data is prohibited and a “0” bit indicates that copying of the associated data is permitted. The bit positions of the copyright byte identify the type of user data for which copying is selectively prohibited or permitted. As shown in FIG. 12, the identified user data is analog video data, analog audio data, digital video data, digital audio data, and the like. For example, if the user data in this sector is digital video data and if copying of that digital video data is prohibited, the copyright byte may appear as “00100000”.
This indicates the particular application intended for the user data that is recorded in this sector. Examples of typical applications are shown in FIG. 13 as computer text, video, vide/audio, etc. If no data is recorded in this sector, the application ID byte may be represented as the character 0.
This data indicates whether the user data is ECC encoded in, for example, the L format or the S format, as shown in FIG. 16. Other types of ECC codes may be represented by other values of this ECC type byte.
If the value of the sub-code address is 2, as represented in FIG. 11C, the data portion represents time code. That is, if the user data recorded in this sector is variable over time, as would be the case if such data is video data, the time code data recorded in the sub-code field represents time information at which the user data is recorded. An example of such time code data is represented in FIG. 14. It is appreciated that 2-digit BCD bits are used to represent the hour, minute, second and frame at which the user data in this sector is recorded.
If the value of the address portion is 3, as depicted in FIG. 11D, the data portion of the sub-code field represents the distance from the sector in which this sub-code field is recorded to the first sector in which an immediately preceding I compressed video picture is recorded; and also the distance from this sector to the first sector in which the next-following I compressed video picture is recorded. Those of ordinary skill in the art will recognize that video data, when compressed in accordance with the MPEG standard, may constitute an intraframe encoded video picture, typically known as an I picture, a predictive coded video picture, typically known as a P picture, and a bi-directionally predictive coded video picture, typically known as a B picture. The data portion of the sub-code field whose address portion has the value of 3 thus indicates the distances between this sector and the beginning of the next-preceding and next-following I pictures.
If the value of the address portion is 4, as shown in FIG. 11E, the data portion includes 1-byte picture type, indicating whether the video picture that is recorded in this sector is an I, P, or B picture (see FIG. 15), and 2-byte temporal reference data which indicates the location in the original picture display sequence of the particularly picture that is recorded in this sector. This temporal reference data is helpful during a playback operation because, as those of ordinary skill in the art recognize, the location of compressed B-picture data in the MPEG code sequence may be quite different from the actual location of that picture when the B-picture ultimately is displayed.
The ECC format which preferably is used with the present invention is the L format. A schematic representation of an encoded “data frame” is depicted in FIG. 17. The ECC “frame” is referred to herein as a C1 code word and this word, when recorded, consists of a sync pattern followed by 136 data symbols. The term “symbol” is used rather than “byte” because, as will be described, the recorded “symbol” consists of 16 bits (known as channel bits), whereas a byte typically is understood to consist of only 8 bits. It is appreciated, however, that the C1 code word, prior to conversion from 8-bit bytes to 16-bit symbols, that is, prior to modulation of the C1 code word, nevertheless consists of the construction shown in FIG. 17, wherein it will be understood that the illustrated symbols are, in fact, bytes.
The manner in which the C1 code word structure is generated now will be briefly described. 116 data bytes, or symbols, known as a C2 word, are supplied to, for example, the ECC encoder formed of memory 131 and ECC circuit 132 of FIG. 1. A C2 hold section is added to the C2 word, preferably by being inserted between two groups of 58 symbols, and a C1 hold section is added to the end of the resultant 128 symbols. A hold section merely reserves a location in the data stream in which parity data subsequently is inserted. Thus, a preliminary C1 word may be thought of as being formed of a group of 58 data symbols followed by a C2 hold section followed by a group of 58 data symbols followed by a C1 hold section. Then, C2 parity symbols are generated by, for example, modulo 2 addition. Preferably, one data symbol is one preliminary C1 word is modulo-2 combined with a data symbol included in the next (or second) preliminary C1 word. If desired, further combinations may be effected with a data symbol included in the third-following preliminary C1 word, and so on, to produce one C2 parity symbol. The next C2 parity symbol is produced by a similar combination of the next data symbol in this first preliminary C1 word with respective data symbols in the next-following preliminary C1 words. In this manner, C2 parity symbols are generated by combining a predetermined number of data symbols of the same predetermined number of successive preliminary C1 words. That is, if the C2 parity symbol is produced by modulo-2 combining a two data words, the one data word of the first preliminary C1 word is modulo-2 combined with one day symbol in the next symbol position of the next-following preliminary C1 word. If the C2 parity symbol is produced by combining three data symbols, then one data symbol in successive symbol positions from each of three successive preliminary C1 words are combined to produce the C2 parity symbol. And if the C2 parity symbol is generated by combining four data symbols, than one data symbol in successive symbol positions from each of four successive preliminary C1 words are combined.
As a preferred aspect of this ECC encoding, the data symbols which are combined occupy successive positions in the respective preliminary C1 words. That is, if the data symbol in the first preliminary C1 word is the nth data symbol, the data symbol in the second preliminary C1 word is the (nth+1) data symbol, the data symbol in the third preliminary C1 word is the (n+2)th data symbol, and so on.
When 12 C2 parity symbols are generated in the manner just described, those 12 C2 parity symbols are inserted into the C2 hold section of this first preliminary C1 word, thus forming a precursory C1 word. Then, 8 C1 parity symbols are generated by conventional parity symbol generation in response to the data and parity symbols included in this precursory C1 word. The generated C1 parity symbols are inserted into the C1 hold section thus forming the C1 code word.
In the C1 code word shown in FIG. 17, the C2 parity symbols are inserted between two groups of data symbols. Alternatively, the C2 parity symbols may be located at the end of the 116 data symbols, that is, at the end of the C2 word. A preestablished number of C1 code words having the structure shown in FIG. 17 constitute the long distance error correction encoded data. That is, a preestablished number of the C1 code words are used as the L format ECC encoded data having the structure shown in FIG. 18. As illustrated, 128 C1 code words are used, such that i=0, 1 . . . 127. Each C1 code word is comprised of a sync code, or pattern, followed by 136 symbols S0, S1, . . . Sj . . . S135, wherein j=0, 1 . . . 135. The circles shown in FIG. 18 represent the manner in which the C2 parity symbols are generated. As has been described above, the C2 parity symbols are generated for the C1 0 code word in response to the data symbols included in code words C1 0, C1 1, . . . C1 r, where r represents the number of data symbols and that are combined to generate the parity symbol. From FIGS. 17 and 18, it is seen that symbols S0-S127 constitute data and C2 parity symbols, and symbols S128-S135 constitute C1 parity symbols. It will be appreciated that, since twelve C2 parity symbols are recorded in a C1 code word, up to twelve data symbols can be corrected. Since these twelve data symbols are included in twelve successive C1 code words, a burst error of twelve C1 code words can be corrected, which amounts to a correctable error of 12×136=1,632 symbols.
An example of the S format ECC encoding is schematically illustrated in FIG. 19. In the S format, the twelve C2 parity symbols are divided into two groups of six C2 parity symbols each, with one group of six C2 parity symbols being added to 58 data symbols and the other group of six C2 parity symbols being added to the next 58 data symbols. Thus, rather than generating the C2 parity symbols from data symbols included in 128 C1 code words, the C2 parity symbols in the S format are generated from successive data symbols included in 64 C1 code words having the schematic representation shown in FIG. 19. Whereas the L format permits the use of C2 parity symbols to correct errors in twelve C1 code words, the S format supports C2 parity correction of up to six C1 code words. Hence, the S format permits the correction of a burst error of 6×136=816 symbols.
When compared to the ECC format used in, for example, CD-ROMs of type that have been proposed heretofore, the use of the L format or S format in accordance with the present invention permits a reduction in redundancy from about 25% of prior art CD-ROMs to about 15% in the present invention.
A sector formed of ECC encoded data in the L format or the S format is shown in FIG. 21 wherein the sector includes the sector header formed of 24 symbols and also is comprised of eighteen C1 code words, each C1 code word having the construction shown in FIG. 17. The last C1 code word included in the sector includes four error detection code symbols and twelve symbols that are reserved for future use. The sector header exhibits the structure shown in FIG. 10. Nevertheless, errors that may be present in the sector header can be corrected generally by using only the C1 parity symbols which are generated for that C1 code word.
As an aspect of this invention, the sequence of the symbols included in a C1 code word as recorded in a track differs from the sequence of the symbols that are supplied for recording. That is, and with reference to FIG. 1, the sequence of the symbols supplied to modulator 140 differs from the sequence of symbols supplied to switch 124. By recording the data symbols in what is referred to herein as a disarranged order, the possibility is reduced that a burst error will destroy the data to the extent that, when reproduced, the data will not be interpretable. In particular, if the data represents video information, the recording of the data symbols in disarranged order enhances the possibility that accurate video pictures nevertheless can be recovered even in the presence of the burst error. FIG. 20 is a schematic representation of the manner in which the data symbols are disarranged for recording.
Let it be assumed that data symbols are recorded on the disk in the order Dk and let it be further assumed that each C1 code word is formed of m symbols, with n of those symbols constituting a C2 code word (i.e. 116 data symbols and 12 C2 parity symbols) and m-n of those symbols constituting the C1 parity symbols. The relationship among i, j, k, m and n for recording thus is:
If the data symbols appear on the disk in the recorded sequence D0, D1, D2 . . . such data symbols are grouped into an odd group followed by an even group. For example, and assuming 136 symbols, data symbols D0-D67 constitute an odd group of odd numbered data symbols and data symbols D68-D135 constitute an even group of even data symbols. It will be understood that “odd” and “even” refer to the original sequence in which those data symbols had been presented for recording. In the foregoing equations, i is the sequential order in which the C1 code words are presented for recording, j is the sequential order of the m symbols in each C1 code word presented for recording and k is the order in which the m symbols are recorded on the disk. That is, Dj≠Dk.
When the C1 code words having data symbols in the sequence D0, D1, . . . D135 are played back from the disk, the data symbols stored in ring buffer 217 of FIG. 2 are rearranged to the sequence illustrated in FIG. 20. This sequence of FIG. 20 is referred to as the arranged sequence and is formed of sequential alternating odd and even data symbols which is the same sequence as the data symbols originally presented to switch 124 of FIG. 1 for recording. It will be appreciated that the data symbols which are included in the recorded C1 1 code word in fact belong in part to C1 0 code word and the C1 1 code word. That is, if the C1 1 recorded code word is formed of symbols D0, D1, . . . D135, the reproduced C1 0 code word includes symbols D1, D3, . . . D133, D135 and the reproduced C1 1 code word includes symbols D0, D2, . . . D132, D134. The sequential storage positions in ring buffer 217 of FIG. 2 of the symbols Dk that are reproduced from the disk may be expressed as follows:
where i is the sequential order of the C1 code words that are read out of the ring buffer, j is the sequential order of the sequence of the m symbols in each C1 code word that is read out of the ring buffer and k is the disarranged order in which the m symbols are recorded on the disk.
Although the present invention preferably records data in the L format of ECC encoding, the teachings herein may be employed with S format ECC encoding. Discrimination between the L format and S format may be made by sensing the ECC byte in the track information field of the TOC data, such as the ECC byte shown in Table 3, or by sensing the ECC byte included in the subcode field shown in FIG. 11B, wherein the ECC byte of the subcode field may have the structure shown in FIG. 16. Another technique that can be used for ECC format discrimination contemplates using one type of sector sync pattern when L format ECC encoding is used and another type of sector sync pattern when S format ECC encoding is used. Thus, not only is sector synchronization detected but, at the same time, the type of ECC format is sensed.
Yet another technique for discriminating between L format and S format ECC encoding employs the addition of a discrimination bit immediately following the sector sync pattern.
Still another technique for discriminating between the L and S ECC formats is based upon the ability of the ECC correcting circuit 216 of FIG. 2 to operate satisfactorily. For example, if error correction assumes that the ECC encoded data is in the L format and error correction is not possible, it is highly likely that the data actually is in the S format. Conversely, if error correction assumes that the ECC encoded data is in the S format but error correction is not possible, it is highly likely that the data had been encoded in the L format. Thus, discrimination between the formats is dependent upon the success or failure of error correction.
The ECC encoded data, whether in the L format or the S format, constitute convolution codes. A group of C1 code words may be thought of as a block and such C1 code words may be block coded in the manner shown schematically in FIG. 22. Here, in addition to L format ECC encoding, the C1 code words are block coded as will now be briefly described. Let it be assumed that the data symbols in a preliminary C1 word constitute a C2 word (as described above). Let it be assumed that the C2 words are presented in the sequence C2 1, C2 2, C2 3, etc. In FIG. 22, the symbols represented by an open circle are data symbols included in the C2 0 word, the symbols represented by a filled-in circle are data symbols included in the C2 16 word, the symbols represented by a triangle are data symbols included in the C2 17 word, the symbols represented by a square are data symbols included in the C2 18 word, and the symbols represented by an X are data symbols included in the C2 19 word. Since a block code consists of 144 C1 code words, but each C1 code word includes only 128 data symbols (including C2 parity symbols) it follows that one data symbol in the C1 17 code word cannot be included in the illustrated block and is expected to be included in the next-following block. However, block coding requires all of the data symbols in a block of code words C1 0-C1 143 to remain in that block and, therefore, the last data symbol of the C1 17 code word is “folded back” into this block as the last data symbol of the C1 0 code word. Similarly, the last two data symbols of the C1 18 word are expected to fall within the next-following block, but because of block coding, these two symbols, identified as data symbols 126 and 127, are folded back into the C1 0 and C1 1 code words, respectively. Stated generally, those data symbols of a C2 word which otherwise would be included in the next-following block are folded back to the beginning of the illustrated block such that each C1 code word included in a block of 144 C1 code words includes interleaved data symbols from 128 of the 144 C1 code words, as shown.
Each block consists of 8 sectors, whereby a block includes more than 16K bytes. Error correction can be carried out on a block-by-block basis.
FIG. 23 is a schematic representation of the block coding of S format ECC encoded data. The same principle that is used for the block coding of L format ECC encoded data, as discussed in conjunction with FIG. 22, is applicable to the block coding of S format ECC encoded data. Here, however, each block consists of 4 sectors; and as a result, each block is comprised of more than 8K bytes.
The modulation technique used to modulate the C1 code words for recording on disc 100 (e.g., the modulation technique used by modulator 140 of FIG. 1) now will be described.
One type of modulation is 8-to-14 modulation (EFM) which is used as the standard in compact discs, and one example of such EFM processing is described in Japanese patent application 6-2655. In conventional EFM, an 8-bit byte is converted into a 14-bit symbol (the bits of the symbols are known as “channel” bits because they are supplied to the recording channel) and successive symbols are separated by margin bits. Heretofore three margin bits were used, and these three bits were selected to assure that the Digital Sum Value (DSV) accumulated from successive symbols is reduced. EFM is a run length limited (RLL) code and, preferably, the shortest run length permitted in EFM consists of two consecutive zeros which are spaced between 1s, and the longest run length is limited to 10, wherein 10 consecutive zeros may be present between 1s.
If two margin bits are used rather than 3, the possible combinations of such margin bits are: 00, 01, 10 and 11. In EFM, a margin bit state 11 is prohibited. Hence, only three different combinations of margin bits can be used to link (or separate) successive symbols: 00, 01 and 10. But, depending upon the bit stream of one or the other symbols which are linked by the margin bits, one or more of these possible states may be precluded because, to use the precluded state may result in an undesirable DSV.
FIG. 24 is a schematic representation of a “string” of data symbols separated by margin bits. Each data symbol is comprised of 14 channel bits and the margin bits are comprised of 2 channel bits. Thus, margin bits M1 separate data symbols D1 and D2; margin bits M2 separate data symbols D2 and D3; margin bits M3 separate data symbols D3 and D4, and so on, with margin bits Mm separating data symbols Dm and Dm+1. Nevertheless, assuming that the 14 channel bits included in a data symbol are provided in 14 successive bit cells and further assuming that the margin bits are included in 2 successive bit cells, successive data transitions in the string of channel bits depicted in FIG. 24 are separated by no less than 2 data bit cells and by no more than 10 data bit cells.
A string of data symbols may include parity symbols, and FIG. 27 illustrates a frame of such symbols beginning with a sync pattern of 24 bit cells, followed by 12 data symbols (shown as 14-bit symbols separated by 2 channel bits), followed by 4 parity symbols, followed by 12 data symbols and ending with 4 parity symbols. The sync pattern is illustrated as a high signal level extending for 11 bit cells followed by a low signal level extending for 11 bit cells, followed by a high signal level extending for 2 bit cells. The inverse of this pattern can be used. FIG. 27 also depicts the two-bit margin bits which separate successive data symbols; and as mentioned above, in some instances, certain ones of the three permitted combinations of margin bits cannot be used. FIG. 28 schematically represents the conditions under which the margin bit combination 00 or the margin bit combination 01 or the margin bit combination 10 cannot be used. As will described, a signal known as the inhibit margin bit signal M identifies the margin bit combination which cannot be used. For example, when Minh=00, the margin bit combination 00 cannot be used. Similarly, when Minh=01, the margin bit combination 01 cannot be used. And when Minh=10, the margin bit combination 10 cannot be used.
Let it be assumed that margin bits separate data symbols D1 and D2. Let it be further assumed that the number of consecutive zeros at the leading end of data symbol D2 is represented as A and the number of zeros at the terminating end of data symbol D1 is B. If A+B is equal to or exceeds 8 successive zeros (A+B≧8) then the margin bit combination 00 is inhibited (Minh=00).
If the most significant bit C1 of data symbol D2 is “1” (A=0) or if the next most significant bit C2 is “1” (A=1) or if the least significant bit C14 of data symbol D1 is “1” the margin bit combination 01 is inhibited (Minh=01).
If the least significant bit C14 of data symbol D1 is “1” (B=0) or if the next least significant bit C13 is “1” (B=1), or if the most significant bit C1 of data symbol D1 is “1”, the margin bit combination 10 is inhibited (Minh=10).
The foregoing 3 conditions are not mutually exclusive; and from FIG. 28 it is seen that conditions may exist which preclude the margin bit combinations 01 and 10 (both margin bit conditions are precluded if the most significant bit C1 of data symbol D2 is “1” or if the least significant bit C14 of data symbol D1 is “1”). The number of inhibit margin bit combinations is represented as NI. If NI=0, all three margin bit combinations may be used. If NI=1, one of the three margin bit patterns is precluded and the other two may be used. If NI=2, two of the margin bit patterns are precluded but the third is permitted. It will be appreciated that NI never is three.
Turning now to FIG. 25, there is illustrated a flow chart which represents the manner in which a margin bit combination is selected for insertion by a margin bit generator between two data symbols. At step S1, the inhibited margin bit combinations are determined for each set of margin bits M1, M2 . . . Mm and the number of inhibited margin bit combinations NI1, NI2, . . . NIm likewise is determined. It will be appreciated that Minh and NI for each set of margin bits to be inserted between data symbols may be determined from the conditions depicted in FIG. 28.
The flow chart then advances to inquiry S2 which determines if the number of inhibited combinations for the margin bit pattern M1 is equal to 2. If so, the flow chart advances to step S3 and only a single margin bit combination can be selected. For example, if the most significant bit of data symbol D2 is “1”, NII=2 and Minh=01, 10. Step S3 thus permits only margin bit combinations 00 to be selected as the margin bit pattern M1.
However, if inquiry S2 is answered in the negative, then two or three different margin bit combinations can be selected. The flow chart advances to step S4 where the inhibited margin bit combination Minh for the n-th margin bit pattern (n72) is determined. But, if the number of inhibited combinations for the second margin bit pattern is 2, that is, if NI2=2, then the n-th margin bit pattern is construed as the (m+1)th margin bit pattern. That is, if NI2=2, only one margin bit combination can be selected for the remaining margin bit patterns Mn. The flow chart then advances to step S5 wherein data symbol D2 is linked to data symbol D3 which is linked to data symbol D4 . . . to data symbol Dn by the respective margin bit combinations which are not inhibited.
Thereafter, in step S6, since the margin bit patterns up to Mn have been selected, and since the data symbols up to Dn are known, the accumulated DSV up to Dn is calculated. The DSV determined for this data symbol simply is added to the DSV which has been accumulated from previous data symbols. Then, in step S7, the margin bit pattern M1 is selected as the particular margin bit combination which minimizes the DSV that is projected to be accumulated up to data symbol Dn.
It will be appreciated that steps S4-S7 rely upon a projected DSV; and although the margin bit pattern under consideration is margin pattern M1, the technique for selecting the appropriate margin bit combination for pattern M1 as based upon look ahead data symbols D2, D3, . . . Dn. FIG. 29 is a graphical representation of the manner in which the projected DSV is accumulated based upon “look ahead” data symbols. For simplification, it is assumed that m=3, that data symbols D1, D2 and D3 are known, that the accumulated DSV up to data symbol D1 is known and that margin bit pattern M1 is to be selected. FIG. 29A represents the 14-bit data symbol, wherein a “1” is represented by a transition and a “0” is represented by no transition in the digital signal. The data symbols shown in FIG. 29A are the same data signals used in FIGS. 29B and 29C. FIG. 29A represents the margin bit pattern M1 as the combination 10; FIG. 29B represents the margin bit pattern M1 as the combination 01 and FIG. 29C represents the margin bit pattern M1 as the combination 00. It is assumed that NI1=0, meaning that there are no inhibited margin bit combinations for margin bit pattern M. It is further assumed that the least significant bit of a data symbol is represented as “CWLL” and CWLL=0 in each of data symbols D1, D2 and D3. Furthermore, based upon the most significant bit of data symbol D3, margin bit combinations 01 and 10 are inhibited (see FIG. 28) and NI2=2. Finally, based upon the bit stream of the trailing end of data symbol D3 and the bit stream at the leading end of data symbol D4, margin bit combination 00 is inhibited for M3 (see FIG. 28) and NI3=1.
FIG. 29D illustrates the accumulated DSV that is obtained up to the end of data symbol D3 if M1=0, if M1=01 and if M1=00. In particular, curve a of FIG. 29D illustrates the accumulated DSV when M1=10; curve b represents the accumulated DSV when M1=01; and curve c represents the accumulated DSV when M1=00. It is seen that at the end of data symbol D2, DSV=3 if M1=10; DSV=1 if M1=01; and DSV=−5 if M1=00. Thus, to minimize the accumulated DSV, the margin bit combination 01 should be selected for margin bit pattern M1. But, if the margin bit combination 01 is selected, the accumulated DSV at the end of data symbol D3 is seen to be DSV=−5. On the other hand, if the margin bit combination 00 had been selected for the margin bit pattern M1, the accumulated DSV at the end of data symbol D3 is DSV=1. It is appreciated then, that if the projected DSV is examined, the particular margin bit combination that is selected for margin bit pattern M1 differs from the margin bit combination that would be selected if the projected DSV is not examined.
FIG. 26 is a block diagram of margin bit selection apparatus in which the margin bit combination for margin bit pattern M1 is determined by looking ahead by up to m data symbols, where m=4. Thus, the accumulated DSV up to the end of data symbol D5 is calculated. Input terminal 10 in FIG. 26 is supplied with 32 successive bytes that have been ECC encoded, and these bytes are used to read out 14-bit symbols from a conversion table 11 stored as a ROM. Successive 14-bit symbols are coupled to an adder 13 which adds a pseudo frame sync signal to the successive data symbols, the pseudo frame sync signal S1 f (“1XXXXXXXXXXX10”) being added to the leading portion of each sync frame. The pseudo frame sync signal serves to “reserve” a location in which the actual frame sync pattern is inserted, as will be described.
Successive data symbols are coupled to registers 14-17 wherein each data symbol is stored. Thus, register 17 stores data symbol D1, register 16 stores data symbol D2, register 15 stores data symbol D3, register 14 stores data symbol D4 and adder 13 now supplies data symbol D5 to the input of register 14. Data symbols D4 and D5 are coupled to discriminator 30 which examines these data symbols to determine if any of the bit patterns therein correspond to those shown in FIG. 28. Depending upon the sensed bit patterns, discriminator 30 generates the inhibit margin bit signal Minh which precludes certain margin bit combinations from margin bit pattern M4. The inhibit margin bit signal produced by the discriminator is comprised of 3 bits and is identified as the margin bit inhibit signal Sinh4. A “1” in the first bit position of Sinh4 inhibits the margin bit combination 10, a “1” in the second bit position of Sinh4 inhibits the margin bit combination 01 and a “1” in the third bit position of Sinh4 inhibits the margin bit combination 00. As an example, if only the margin bit combination 00 is a permitted margin bit pattern, margin bit inhibit signal Sinh4 is represented as “110”.
The output of register 17 is coupled to a frame sync converter 18 which converts the 14-bit pseudo frame sync signal S1 f to a 24-bit frame sync signal Sf. This 24-bit frame sync signal Sf is coupled to parallel-to-serial register 19. Those data symbols D1, D2, . . . which are supplied successively to frame sync converter 18 are not modified thereby and are supplied as is, that is, in their 14-bit configuration, to the parallel-to-serial register. Register 19 converts those bits which are supplied thereto in parallel to serial output form. In addition, after a 14-bit data symbol is serially read out of the register, a 2-bit margin pattern produced by a margin bit generator 50 is serially read out of the register. Parallel-to-serial register 19 is clocked with a channel bit clock having a frequency of 24.4314 MHz such that the serial bit output rate of register 19 is 24.4314 Mbps. These serial bits are modulated by an NRZI modulator 20 and coupled to an output 21 for recording.
The modulated NRZI serial bits also are fed back to a DSV integrator 40 which integrates the DC component of such serial bits. The DSV integrator thus accumulates the DSV of the data symbols and margin bit patterns.
Margin bit generator 50 functions in accordance with the flow chart shown in FIG. 25 to effect the operation illustrated by the waveforms of FIGS. 29A-29D. It is appreciated, then, that the margin bit generator 50 may be a digital signal processor, an arithmetic logic unit or a microprocessor programmed in accordance with the flow chart of FIG. 25. Thus, the appropriate margin bit combination is selected in order to minimize the accumulated DSV will obtain as a result of m subsequent data symbols.
The foregoing has described an EFM technique in which a margin bit pattern is inserted between successive 14-bit data symbols. As a result, each 8-bit byte is converted into a 14-bit data symbol plus a 2-bit margin pattern. A preferred embodiment of an 8-to-16 modulator which eliminates the generation of margin bit patterns, which minimizes the accumulated DSV and which is constrained to run length limited (2, 10) code now will be described. Referring to FIG. 30, a plurality of “fundamental conversion tables are provided, for example, four conversion tables T1, T2, T3 and T4. Each fundamental table is comprised of two separate tables, identified by the subscripts a and b, one of which converts an 8-bit byte into a 16-bit symbol having positive DSV and the other converting the same 8-bit byte into a 16-bit symbol having negative DSV.
The tables are categorized as follows: if the last bit of the immediately preceding 16-bit symbol ends as a “1” or if the last two bits of that 16-bit symbol end as “10”, the next 16-bit symbol is selected from table T1a or table T1b, depending upon whether it is desirable that this next selected 16-bit symbol exhibit a positive DSV (thus calling for table T1a) or a negative DSV (thus calling for table T1b).
If the immediately preceding 16-bit symbol ends with two, three or four successive 0s, the next-following 16-bit symbol is selected from either table T2 (that is, from either table T2a or table T2b) or from table T3 (that is, from table T3a or table T3b).
If the immediately preceding 16-bit symbol ends with six, seven or eight successive 0s, the next-following 16-bit symbol is selected from table T4.
The first 16-bit symbol that is generated immediately following a frame sync pattern is selected from table T1.
The 16-bit symbols produced from tables T2 and T3 differ from each other in the following important respects: all 16-bit symbols read from table T2 include a “0” as the first bit and a “0” as the thirteenth bit.
All 16-bit symbols read from table T3 include a “1” as the first or thirteenth bit or a “1” as both the first and thirteenth bit.
In the 8-to-16 conversion scheme used with the present invention, it is possible that the very same 16-bit symbol may be generated in response to two different 8-bit bytes. However, when the 16-bit symbol representative of one of these bytes is produced, the next-following 16-bit symbol is produced from table T2; whereas when the 16-bit symbol representative of the other byte is produced, the next-following 16-bit symbol is produced from table T3. It is appreciated that, by recognizing the table from which the next-following 16-bit symbol is produced, discrimination between the two bytes which, nevertheless, are converted into the same 16-bit symbol may be readily achieved.
For example, let it be assumed that an 8-bit byte having the value 10 and an 8-bit byte having the value 20 both are converted to the same 16-bit symbol 0010000100100100 from table T2. But, when this 16-bit symbol represents the byte having the value 10, the next-following 16-bit symbol is produced from table T2, whereas when the aforenoted 16-bit symbol represents the byte having the value 20, the next-following 16-bit symbol is produced from table T3. When the symbol 0010000100100100 is demodulated, it cannot be determined immediately if this symbol represents the byte having the value 10 or the byte having the value 20. But, when the next-following 16-bit symbol is examined, it is concluded that the preceding symbol 0010000100100100 represents the byte 10 if the next-following symbol is from table T2, and represents the byte having the value 20 if the next-following symbol is from table T3. To determine whether the next-following 16-bit symbol is from table T2 or table T3, the demodulator merely needs to examine the first and thirteenth bits of the next-following symbol, as discussed above.
Table Ta (for example, table T1a) includes 16-bit symbols having a DSV which increases in the positive direction. Conversely, the 16-bit symbols which are stored in table Tb have a DSV which increases in the negative direction. As an example, if the value of an 8-bit byte is less than 64, this byte is converted into a 16-bit symbol having a relatively large DSV. Conversely, if the value of the 8-bit byte is 64 or more, this byte is converted into a 16-bit symbol having a small DSV. Those 16-bit symbols which are stored in table Ta have positive DSV and those 16-bit symbols which are stored in table Tb have negative DSV. Thus, an input byte is converted into a 16-bit symbol having positive or negative DSV, depending upon which table is selected for conversion, and the value of the DSV is large or small, depending upon the value of the input byte that is converted.
The tables T1a, T1b, . . . T4a, T4b in FIG. 30 may be constructed as ROMs 62-69. An input to be converted is supplied from an input terminal 61 in common to each of these ROMs. The pair of tables Ta, Tb of a fundamental table are coupled to a selector switch which selects one or the other table to have read out therefrom the 16-bit symbol which corresponds to the input byte read out therefrom. As shown, selector switch 71 selectively couples the output from table T1a or table T1b to an input x1 of an output switch 75. Similarly, switch 72 selectively couples table T2a or table T2b to an input x2 of switch 75. Switch 73 selectively couples table T3a or table T3b to input x3 of switch 75. Switch 74 selectively couples table T4a or table T4b to input x4 of switch 75. Output switch 75 selectively couples one of its inputs x1-x4 to an output terminal 78 under the control of a table selector 76. Selector switches 71-74 select either table Ta or table Tb under the control of a DSV calculator 77. The 16-bit symbol which ultimately is supplied to output 78 also is coupled to the table selector and to the DSV calculator, as illustrated.
Table selector 76 senses the ending bits of the 16-bit symbol supplied from switch 75 to output terminal 78 to determine whether fundamental table T1, T2, T3 or T4 should be selected, in accordance with the table selecting conditions discussed above. It is appreciated that the table selector thus controls switch 75 to select the 16-bit symbol read from the proper fundamental table. For example, if it is assumed that the 16-bit symbol supplied to output terminal 78 ends with six, seven or eight successive 0s, switch 75 is controlled by the table selector to couple its input x4 to the output terminal such that the next-following 16-bit symbol is read from fundamental table T4. DSV calculator 77 calculates the accumulated DSV, which is updated in response to each 16-bit symbol supplied to output terminal 78. If the DSV increases in the positive direction, DSV calculator 77 controls selector switches 7-74 to couple the outputs from their respective tables Tb. Conversely, if the accumulated DSV is calculated to increase in the negative direction, selector switches 7-74 are controlled by the DSV calculator to couple the outputs from their respectively tables Ta. It is expected, therefore, that if the preceding 16-bit symbol exhibits a larger negative DSV, switches 7-74 are controlled to select the next 16-bit symbol having a positive DSV; and the particular table from which this next 16-bit symbol is read is determined by table selector 76. Thus, the accumulated DSV is seen to approach and oscillate about 0.
An example of a 16-to-8 bit converter, that is, a demodulator compatible with the 8-to-16 bit modulator of FIG. 30, is illustrated in FIG. 31. Here, tables are used to carry out an inverse conversion from 16-bit symbols to 8-bit bytes and such tables are identified as tables IT1, IT2, IT3 and IT4. These tables may be stored in ROMs 84, 85, 86 and 87. It is expected that each 8-bit byte read from a table corresponds to two 16-bit symbols, one having positive DSV and the other exhibiting negative DSV. Alternatively, if the 16-bit symbol is used as a read address, each 8-bit byte stored in a table may have two read addresses. Stated otherwise, each 8-bit byte may be stored in two separate read address locations.
An input terminal 81 is supplied with a 16-bit symbol, and this symbol is stored temporarily in a register 82 and then coupled in common to inverse conversion tables IT1-IT4. In addition, a table selector 83 is coupled to input terminal 81 and to the output of register 82 so that it is supplied concurrently with the presently received 16-bit symbol and the immediately preceding 16-bit symbol. Alternatively, table selector 83 may be thought of as being supplied with the presently received 16-bit symbol (from the output of register 82) and the next-following 16-bit symbol. The table selector is coupled to an output selector switch 88 which couples to output terminal 89 either conversion table IT1 or conversion table IT2 or conversion table IT3 or conversion table IT4.
The manner in which table selector 83 operates now will be described. As mentioned above, the first symbol that is produced immediately following the frame sync pattern is read from conversion table T1 in FIG. 30. Table selector 83 thus operates to detect the frame sync pattern so as to control output switch 88 to coupled table IT1 to output terminal 89.
If, as mentioned above, a 16-bit symbol may represent one or the other of two different 8-bit bytes, table selector 83 senses whether the next-following 16-bit symbol, as supplied thereto from input terminal 81, is from conversion table T2 or conversion table T3. This determination is made by examining the first and thirteenth bits of such next-following 16-bit symbol. If the table selector senses that the next-following 16-bit symbol is from table T2, output switch 88 is suitably controlled to select the inverse conversion table which converts the 16-bit symbol presently provided at the output of register 82 to its proper 8-bit byte. A similar operation is carried out when table selector 83 senses that the next-following 16-bit symbol had been read from conversion table T3 in FIG. 30.
The present invention converts an 8-bit byte into a 16-bit symbol, whereas the prior art converts an 8-bit byte into a 14-bit symbol and inserts three margin bits between successive symbols. Consequently, since the present invention uses only 16 bits in its bit stream as compared to the prior art use of 17 bits, the modulation technique of the present invention results in an effective reduction in data of 16/17, or about 6%.
While the present invention is particularly applicable to a CD-ROM on which computer data, video data, a combination of video and audio data or computer files may be recorded, this invention is particularly useful in recording and reproducing digital video discs (DVD) on which video data and its associated audio data are recorded. Such data is compressed in accordance with the MPEG standard; and when compressed video data is recorded on the disc, the subcode information included in each sector header (FIG. 10) includes a subcode address having the value 3 or the value 4 with the resultant subcode field appearing as shown in FIGS. 11D or 11E. If the subcode address value is 3, the user data recorded in the sector conforms to the standard ISO 11172-2 (MPEG 1) or ISO 13818-2 (MPEG 2). Data that is recorded in the subcode field, as shown in FIG. 11D, represents the difference between the address of the sector which contains this subcode and the lead sector in which the previous I picture or next-following I picture is recorded. It is expected that an I picture (that is, an intraframe encoded picture, as mentioned previously) is recorded in two or more sectors. Of course, each sector includes a header. However, the distance data which is recorded in the subcode field shown in FIG. 11D represents the distance to the lead, or first sector in which the previous I picture or next-following I picture is recorded. If an I picture is recorded partially in one sector and partially in another, the sector header of the “other” sector includes 0 data to represent the previous I distance and the next I distance in FIG. 11D. That is, the previous I distance and the next I distance are 0.
If the subcode address value is 4, the subcode field appears as shown in FIG. 11E and, as mentioned above, the picture type data indicates whether the video data that is recorded in compressed form in this sector is I, P or B picture data and the temporal reference data indicates the location in the sequence of pictures in which this particular video picture is disposed. The sector in which an I, P or B picture first is recorded is referred to as an I, P or B sector, respectively, even if such I, P or B picture data is recorded in a trailing portion of that sector, while other picture data is recorded in a leading portion thereof.
FIG. 32 is a block diagram of compression apparatus which is used to supply to input terminal 121 of FIG. 1 MPEG compressed video data. Video information, supplied as, for example, analog luminance (Y) and color difference (R—Y and B—Y) signals are digitized by an analog-to-digital converter 101 and compressed in accordance with the MPEG compression system by video compression circuitry 102. The compression system may be consistent with the MPEG-1 standard (ISO 11172-2) or the MPEG-2 standard (ISO 13818-2). The compressed video data is stored in a buffer memory 103 from which it is supplied to a multiplexor 107 for multiplexing with other data (soon to be described) which then is input to input terminal 121 (FIG. 1). Information related to the compressed video data stored in buffer memory 103 is supplied to system controller 110, this information being indicative of, for example, whether the compressed video data corresponds to an I, P or B picture, the temporal sequence of display pictures in which this compressed video picture is located, time code representing the time of receipt or time of recording of the video data, etc. The information derived from the stored, compressed video data and supplied to the system controller is used to generate subcode information that is recorded in the sector header. It is recalled from FIG. 1 that this information is supplied from system controller 110 to sector header encoder 129 for insertion into the sector header of the user data.
Audio signals, such as analog left-channel and right-channel signals L and R are digitized by an analog-to-digital converter 104 and compressed in an analog data compression circuit 105. This compression circuit may operate in accordance with the Adaptive Transform Acoustic Coding technique (known as ATRAC) consistent with MPEG-1 audio compression or MPEG-2 audio compression standards. It is appreciated that this ATRAC technique presently is used to compress audio information in recording the medium known as the “Mini Disc” developed by Sony Corporation. The compressed audio data is supplied from compression circuit 105 to an audio buffer memory 106 from which it subsequently is coupled to a multiplexor 107 for multiplexing with the compressed video data. Alternatively, compression circuit 105 can be omitted and the digitized audio data can be supplied directly to a buffer memory 106 as, for example, a 16-bit PCM encoded signal. Selective information stored in the audio buffer memory is coupled to the system controller for use in generating the subcode information that is recorded in the sector header.
Additional information, identified in FIG. 32 as sub-information, including character, computer, graphic and musical instrument for digital interface data (MIDI) also is coupled to multiplexor 107.
Title data is generated by a character generator 111 which, for example, may be of conventional construction. The title data is identified as fill data and key data and is compressed by a compression circuit 112 which encodes the title data in variable run length coding. The compressed title data is coupled multiplexor 107 for subsequent application to the input terminal 121 shown in FIG. 1.
Preferably, multiplexor 107 multiplexes the compressed video, audio and title data, together with the sub-information, in accordance with the MPEG-1 or MPEG-2 standard, as may be desired. The output of the multiplexor is coupled to input terminal 121 of FIG. 1 whereat the multiplexed data is ECC encoded, modulated and recorded on disc 100.
FIG. 33 is a block diagram of circuitry for recovering the video, audio, title and sub-information data that had been recorded on disc 100 and that had been reproduced from the disc by the playback apparatus shown in FIG. 2. The input to the data recovery circuit shown in FIG. 33 is output terminal 224 of FIG. 2. This terminal is coupled to a demultiplexor 248 which demultiplexes the aforedescribed multiplexed video, audio and title data as well as the sub-information. The demultiplexor operates in accordance with the MPEG-1 or MPEG-2 standard, as may be desired, to separate the compressed video data, the compressed audio data, the compressed title data and the sub-information. The compressed video data is stored in a buffer memory 249 from which it is expanded in expansion circuit 250, processed in a post processor 256, for example, as may be needed to conceal errors, and reconverted back to analog form by digital-to-analog converter 251. Expansion circuit 250 operates in accordance with the MPEG-1 or MPEG-2 standard such that the original video information is recovered.
Post processor 256 also is adapted to superimposed graphical title information on the recovered video data, as will be described below, such that the recovered title data may be suitably displayed, as by superposition on a video picture.
The separated audio data is supplied from demultiplexor 248 to an audio buffer memory 252 from which it is expanded in an expansion circuit 253 and reconverted to analog form by digital-to-analog convertor 254. Expansion circuit 253 operates in accordance with the MPEG-1 or MPEG-2 or mini disc standard, as may be desired. If the audio data that is recorded on disc 100 has not been compressed, expansion circuit 253 may be omitted or bypassed.
As depicted in FIG. 33, the sub-information separated by demultiplexor 248 is supplied as a direct output signal, consistent with the representation shown in FIG. 32 wherein such subinformation is not processed prior to being supplied to multiplexor 107 and no processing subsequent to demultiplexor 248 is illustrated.
The separated title data is applied to title buffer memory 233 from demultiplexor 248 from which the title data is decoded by a title decoder 260 that operates in a manner inverse to the operation of compression circuit 112 (FIG. 32). That is, decoder 260 may carry out an inverse variable length decoding operation. The decoded title data is supplied to post processor 256 for superposition onto the video information that has been played back from the optical disc.
Demultiplexor 248 monitors the remaining capacities of buffer memories 249, 252 and 233 to sense when these memories are relatively empty or filled. The purpose of monitoring the remaining capacities of the buffer memories is to assure that data overflow therein does not occur.
System controller 230 and user interface 231 of FIG. 33 are the same as system controller 230 and user interface 231 in FIG. 2.
The present invention finds particular application with a digital video disk (DVD) wherein the user information recorded in the program area shown in, for example, FIGS. 1-7, includes video and audio as well as file data, the latter being useful for computer applications. FIG. 34 is a schematic representation of a general form of an optical disk that can be used both as a DVD and as a CD-ROM, with the video data being recorded as “chapters” and, in the preferred embodiment, each chapter being recorded in a respective track. In addition to the usual TOC information, the optical disk schematically represented in FIGS. 34 is provided with an application TOC region disposed in the program area and containing application table of contents (ATOC) information that relates to the recorded chapters of video data.
As mentioned above, the video data is recorded as, for example, MPEG-compressed video data; and at the present time, two different MPEG formats are used to compress video data, namely MPEG-1 and MPEG-2 techniques. It is not unreasonable to expect that still further video compression techniques will be adopted; and such additional techniques may be identified as MPEG-3, MPEG-4, etc. Likewise, the audio data which accompanies video programming may be compressed in accordance with the MPEG-1 or MPEG-2 formats; and here too, it is reasonable to expect that still further audio compression techniques will be developed. As will be described below, the ATOC information identifies predetermined parameters of the MPEG-compressed video data and the compressed audio data recorded in the respective chapters; and such ATOC information accommodates the possibility that the audio data need not be compressed but simply may be PCM-encoded. As used herein, the expression “compressed audio data” is intended to refer to audio data that has been either compressed in accordance with an MPEG (or other developed) format or audio data that simply is PCM-encoded.
From FIG. 32, it is seen that the user information recorded on the disk and, thus, the user information recorded in respective chapters, is multiplexed from a stream of video data, a stream of audio data and a stream of title information. A chapter may contain compressed video data only or a combination of multiplexed compressed video and compressed audio data, or a combination of multiplexed compressed video data, compressed audio data and title data. The ATOC information serves to identify, for each chapter, the number of “streams” of data that have been multiplexed to form the chapter, each stream type and the particular format used to encode each stream.
The ATOC information also includes data which identifies each chapter by, for example, the name of that chapter (which may be assigned by the manufacturer of the disk to identify different video programs), the locations of the respective chapters (that is, the tracks in which the chapters are recorded) and the category of the programming included in that chapter (for example, the video program may be a movie, a music video, so-called “karaoke”, a sport video, a drama, etc.).
Still further, since the video data recorded in a chapter is assumed to be compressed in accordance with an MPEG format, further information relating to MPEG-compressed pictures are included in the ATOC information. For example, the MPEG format may compress video pictures so as to produce intraframe encoded picture data or predictively encoded picture data, as mentioned above. Because of the particular characteristics of such intraframe encoded picture data, a video picture of reasonably good quality can be readily recovered therefrom; and the locations of such “I-pictures” recorded in each chapter are identified in the ATOC information. Such I-picture locations are know as “entry points”; and the entry point data included in the ATOC information may be used to rapidly access and display representative chapter pictures so as to permit a user to play back a desired chapter or portion thereof.
In FIG. 34, the application TOC region is illustrated as being recorded in the first track of the program area; but it will be appreciated that any predetermined track in the program area can be assigned to this region. FIG. 34 also illustrates the recording of each chapter in a single track; but it is contemplated that a chapter may be recorded in a plurality of tracks. Preferably, however, not more than one chapter is recorded in a given track. Also, for convenience, the chapters are shown to be recorded in sequence (that is, if only one chapter is recorded in one track, each track contains the next-higher chapter number), but such sequential recording of chapters is not necessary. Of course, it is important that each chapter be uniquely identified, and it is helpful if there is a direct correspondence (e.g., one-to-one) between a particular chapter and the track in which that chapter is recorded. Thus, a desired chapter can be rapidly accessed for playback simply by scanning the disk for the particular track in which that chapter is recorded and then scanning that track either for the beginning of the chapter or for any desired entry point therein.
It should be noted here that when the user information is recorded as chapters of MPEG-compressed video data and compressed audio data on a DVD, each sector in a chapter may be of the type shown in FIG. 10A or 10B, and the subcode field included in each sector header may include the information discussed above in conjunction with FIGS. 11C-11E.
FIG. 35 represents the application TOC region and provides a preferred embodiment of the structure of the ATOC information recorded therein. Such data structure is comprised of the following illustrative areas:
a disk information area, which contains data that is useful for the entire disk and not simply for a particular chapter;
several p chapter information areas, with each such area containing information relating only to its corresponding chapter, as will be described in greater detail below, the chapter information associated with each chapter identifying predetermined parameters of the MPEG-compressed video data and the compressed audio data recorded in that chapter;
an area in which all of the possible names of the different chapters are recorded;
an area which identifies all of the aforementioned “streams” of data that constitute the user information in the chapter; and
an area which contains entry point information that identifies all of the entry points in each chapter.
It is expected that the information which is included in all of the aforementioned areas is less than the recording capacity of a data track; and the excess capacity of that track is reserved for future use. The number of bytes which constitute each of the aforementioned areas is depicted in FIG. 35.
The data which constitutes the disk information area of the ATOC information shown in FIG. 35 is depicted in greater detail in FIG. 36. The fields which identify the disk information are described more particularly as follows:
This field, comprised of 8 bytes, contains a character string that identifies the data structure used to represent the ATOC information. This TOC identifier, when detected by the controller in the DVD player permits the playback operation to be compatible with the format in which the ATOC information and the chapter information are recorded. For example, if the character string of the TOC identifier is “AVTOC001”, the data structure of the ATOC information and the data structure of the user information recorded in each chapter are as shown in FIGS. 35-44.
This 3-byte data is intended to identify the actual language of the names that are recorded in the name information area of the application TOC region. It will be appreciated that this 3-byte TOC language is similar to the Local Language Country Code recorded as the disk information in Table 2.
Total Number of Entry Points
This two-byte field identifies the number of I-pictures that are recorded on the disk. Each entry point designates a sector in which an I-picture first is recorded. It is appreciated that over 64 k I-pictures can be recorded on the disk.
The remaining fields shown in FIG. 36 are not further described herein as they are not needed for an adequate understanding of the present invention.
Each 32-byte chapter information area included in the application TOC region exhibits the data structure shown in FIG. 37 as will now be described. The information recorded in each of the chapter information fields is as follows:
This 1-byte field identifies the number of the chapter, and up to a maximum of 256 chapters can be recorded. As mentioned above, it is preferred to record one chapter in one data track; and it is contemplated that one chapter may be recorded in two or more data tracks. However, it is preferred that no more than one chapter be recorded in any given track. No two chapters on this disk are identified by the same chapter number.
Corresponding Track Number
This 1-byte field identifies the number of the track in which this chapter is recorded. In the simplest embodiment, if the application TOC region is recorded in track 1, then chapter 1 is recorded in track 2, chapter 2 is recorded in track 3, and so on.
This 1-byte field represents the program information (or data content) of this chapter. The value of the chapter category data identifies the chapter category as shown in FIG. 44. For example, if the chapter contains a movie, the value of the chapter category byte is 0. If the chapter is a music video, the value of the chapter category byte is 1. Other examples of chapter category representations are shown in FIG. 44; and it is to be understood that the present invention is not limited solely to the categories which are shown.
Pointer to Chapter Name
This 2-byte field identifies a particular 8-byte field in the name field area of the application TOC region shown in FIG. 35. In the preferred embodiment, 2,048 different name fields may be provided in the name field area and the 2-byte pointer to chapter name in FIG. 37 identifies a respective one of the 2,048 name fields. The name of the chapter thus need not to be included in the 32-byte chapter information area itself; and instead a separate name field area is provided from which the name of this corresponding chapter is found. Thus, the chapter name pointer simply “points” to the appropriate name field which contains the chapter name.
If the name of the chapter requires more than a single 8-byte name field, for example, if two or more name fields are needed, sequential name fields form a suitable “string” in which the entire name of the chapter is recorded. In that event, the chapter name pointer simply identifies the first name field in this string.
Pointer to Stream Parameters
This 2-byte field preferably includes several “pointers” which identify respective 4-byte stream parameter fields in the pool of stream parameter fields shown in FIG. 39. As mentioned above, each chapter is formed of MPEG-compressed video data together with compressed audio data and/or title data. Video compression may be in accordance with the MPEG-1 or MPEG-2 format. Audio compression may be in accordance with the MPEG-1 or MPEG-2 format or with the PCM format. The compressed video data constitutes one stream, the compressed audio data constitutes another stream and the title data constitutes yet a further stream. If, for example, a chapter consists of only one stream of data such as MPEG-compressed video data, only one stream parameter pointer is needed. If the chapter is formed of two multiplexed streams of data (e.g., video data and audio data or video data and title data) two stream parameter pointers may be used. And if the chapter is formed of three multiplexed streams (for example, video data plus audio data plus title data) then three stream parameter pointers are preferred. Each stream parameter pointer identifies a respective 4-byte stream parameter field included in the pool of stream parameters (FIG. 39) which represents the characteristics of the corresponding stream that is included in this chapter. As discussed above in conjunction with FIG. 35, the pool of stream parameters is recorded in a separate area in the application TOC region; and each 4-byte stream parameter field exhibits the data structure shown in FIG. 41.
As shown in FIG. 41, each 4-byte stream parameter field includes 1-byte data representing the stream type, and a representation of such 1-byte data is shown in FIG. 43. Depending upon the value of the stream type byte, the stream to which the stream parameter pointer points identifies the data included in this chapter as MPEG-1 compressed video data, MPEG-2 compressed video data, MPEG-1 compressed audio data, MPEG-2 compressed audio data, a further type of MPEG-compressed data, title data or PCM audio data. Thus, this 1-byte stream type data included in the stream parameter field to which the stream parameter pointer points satisfactorily identifies the necessary parameters of this stream of data included in the chapter.
As also shown in FIG. 41, the 4-byte stream parameter field includes 1-byte stream ID data which identifies the number of streams of data that are multiplexed in this chapter. Consistent with the foregoing discussion, the stream ID byte may indicate that the chapter is formed of only one stream of data (e.g., compressed video data) or two streams of data (e.g., compressed video and audio data or compressed video and title data) or three streams of data (e.g., compressed video, audio and title data).
FIG. 41 further illustrates that the 4-byte stream of parameter field includes 2-byte language data which identifies the language of the audio information or title information that may be included in this chapter.
In the foregoing discussion, it has been assumed that the 2-byte stream parameter pointer included in the chapter information area includes several pointers. Alternatively, only one pointer need be included; and if the chapter consists of two or three multiplexed streams of data, as represented by the 1-byte stream ID data included in the stream parameter field (FIG. 41), successive stream parameter fields are linked to provide the necessary representations of the types of streams that are multiplexed in this chapter. For example, let it be assumed that a single stream parameter pointer is included in the chapter information area and that this stream parameter pointer points to stream parameter no. 25. Let it be further assumed that this chapter consists of multiplexed video, audio and title data. The 4-byte stream parameter information recorded at stream parameter no. 25 thus includes a stream ID value of 3. As a result, stream parameter fields nos. 25, 26 and 27 and linked by this stream ID byte so that even though a single stream parameter pointer is used, the three stream parameters are indicated to identify the three types of streams that are multiplexed in this chapter. Thus, with a single stream parameter pointer, three 4-byte stream parameter fields nevertheless are identified in the pool of stream parameters to thereby represent the formats of the compressed video, compressed audio and title data included in this chapter.
Number of Streams
This 1-byte data simply identifies the number of streams that are used in this chapter. In the examples discussed above, if only compressed video data is recorded in this chapter, than the value of the 1-byte number of streams field is 1. If the chapter is formed of two multiplexed streams of data (e.g., compressed video and compressed audio or compressed video and title), the value of the number of streams field is 2. And if three multiplexed streams of data are used in this chapter (e.g., compressed video, compressed audio and title), than the value of the number of streams field is 3. It is appreciated that the number of streams field can be used to indicate the number of 4-byte stream parameter fields that are linked to identify the formats of the data used to record this chapter.
Pointer to Entry Point
This 2-byte field is similar to the stream parameter pointer and includes a pointer which identifies a 4-byte entry point field included in the pool of entry point information shown in FIG. 40. As mentioned above, it is expected that each chapter has recorded therein several I-pictures. Each I-picture may be recorded in one or more sectors. The address of the first sector in which an I-picture is recorded is designated an entry point. The entry point pointer included in the chapter information area of FIG. 37 thus points to one of these entry points included in the entry point pool (FIG. 40); and, preferably, the entry point pointer identifies the entry point field in which the first entry point of this chapter is designated.
Each 4-byte entry point field shown in FIG. 40 exhibits the data structure shown in FIG. 42. As illustrated, entry point data includes a 1-byte chapter number which identifies the chapter which contains this entry point and a 3-byte address which identifies the sector of this entry point. It will be recognized that the 3-byte sector address identifies the address of the first sector in which this I-picture is recorded. It is expected that a chapter contains hundreds if not thousands of I-pictures. Each I-picture constitutes an entry point. Preferably, all of the entry points in a chapter are linked such that information representing the first entry point in the entry point pool is identified by the entry point pointer in this chapter information area, data representing the next entry point in this chapter is recorded in the next entry point field in the pool, and so on. For example, if there are 500 entry points in this chapter, 500 successive entry point fields are linked; and the first of these entry point fields is identified by the entry point pointer. The number of such linked entry point fields and, thus, the number of such entry points included in this chapter are represented by the number of entry point fields shown in FIG. 37.
Number of Entry Points
This 2-byte field identifies the total number of entry points that are present in this chapter and, as mentioned above, thus determines the number of entry point fields included in the pool shown in FIG. 40 that are linked. It is appreciated that, by detecting the entry point pointer and the number of entry points, both included in the chapter information area, the location of each entry point in this chapter is identified. This number of entry point data permits quick access to an arbitrary entry point included in this chapter. Since the location of the first entry point is known by the entry point pointer and the entry point field identified by this pointer, and since the locations of subsequent entry points likewise are known by reason of the linked entry point fields, it is a relatively simple matter to rapidly access the third or twenty-fifth or one-hundred seventy fourth entry point, as may be desired.
This 12-byte data represents the International Standard Recording Code which identify a musical program recorded in this chapter. If this chapter does not contain a musical program, the ISRC data is recorded as 12 bytes of 0×FF.
It is appreciated that the application TOC region and the aforementioned ATOC information may be readily generated by TOC encoder 125 (FIG. 1) or by a separate ATOC encoder coupled to yet another input of switch 124 for recording in, for example, the first track of the program area of the optical disk.
While the present invention has been particularly shown and described with reference to preferred embodiments, it will be readily apparent to those of ordinary skill in the art that various changes and variations may be made without departing from the spirit and scope of the invention. To the extent that such variations and changes have been mentioned herein, the appended claims are to be interpreted as including such variations and changes as well as all equivalents to those features which have been particularly disclosed.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4413340 *||Nov 12, 1981||Nov 1, 1983||Sony Corporation||Error correctable data transmission method|
|US4476562 *||Sep 28, 1983||Oct 9, 1984||Sony Corporation||Method of error correction|
|US4825403 *||Apr 29, 1986||Apr 25, 1989||Data General Corporation||Apparatus guaranteeing that a controller in a disk drive system receives at least some data from an invalid track sector|
|US5060221 *||May 12, 1989||Oct 22, 1991||Sony Corporation||Digital data recording/reproduction apparatus|
|US5276674||Mar 15, 1991||Jan 4, 1994||Matsushita Electric Industrial Co., Ltd.||Optical recording medium having thin protective layer and two-dimensionally aligned code words and recording/reproducing apparatus employing the same|
|US5406538 *||May 15, 1990||Apr 11, 1995||Sony Corporation||Optical disk system with table of contents|
|US5455684 *||Sep 22, 1993||Oct 3, 1995||Sony Corporation||Apparatus and method for processing a variable-rate coded signal for recording to provide a high-speed search capability, apparatus and method for reproducing such processed signal, and recording including such processed signal|
|US5479303 *||Oct 20, 1993||Dec 26, 1995||Nippon Telegraph And Telephone Corporation||Method and apparatus for visual search control of digital video files|
|US5481530 *||Oct 18, 1993||Jan 2, 1996||Mitsubishi Chemical Corporation||High density optical recording method and recording medium|
|US5519680 *||Oct 1, 1993||May 21, 1996||Yamaha Corporation||Disc recording and reproducing device for improved recording of table of contents information|
|US5535008 *||Mar 16, 1994||Jul 9, 1996||Victor Company Of Japan, Ltd.||Method for jump-reproducing video data of moving picture coded with high efficiency|
|US5592450 *||Jun 7, 1995||Jan 7, 1997||Sony Corporation||Method for reproducing compressed information data from a disk using a spatial frequency less than the track pitch|
|US5596565 *||Jun 7, 1995||Jan 21, 1997||Sony Corporation||Method and apparatus for recording MPEG-compressed video data and compressed audio data on a disk|
|US5617384 *||Jun 1, 1995||Apr 1, 1997||Sony Corporation||Method and apparatus for recovering TOC and user information from an optical disk and using the TOC information to access user tracks|
|US5715355 *||Mar 17, 1995||Feb 3, 1998||Sony Corporation||Optical disk having a particular format to store user-selected data, such as video data or computer files, including a dedicated TOC region|
|US5793779 *||Jun 1, 1995||Aug 11, 1998||Sony Corporation||Optical disk and method and apparatus for recording and then playing information back from that disk|
|USRE31666 *||May 6, 1983||Sep 11, 1984||Sony Corporation||Burst-error correcting system|
|EP0399853A2 *||May 25, 1990||Nov 28, 1990||Sharp Kabushiki Kaisha||Recording and reproducing device|
|EP0406021A2 *||Jun 29, 1990||Jan 2, 1991||Sharp Kabushiki Kaisha||Disk recording and reproducing device|
|EP0482645A2 *||Oct 24, 1991||Apr 29, 1992||Pioneer Electronic Corporation||Optical recording system|
|EP0536764A1||Oct 8, 1992||Apr 14, 1993||Sony Corporation||Disc-shaped recording medium|
|EP0570922A2 *||May 18, 1993||Nov 24, 1993||Sony Corporation||Reproducing apparatus|
|U.S. Classification||386/262, 720/729, 386/331, 386/297|
|International Classification||G11B7/004, G11B7/0037, H04N9/82, G11B27/034, H04N7/24, H04N9/804, H04N9/877, H04N5/926, H04N5/945, G11B20/12, H04N7/52, G11B7/013, G11B27/32, G11B27/10, G11B27/30, H04N5/85, G11B27/11, G11B7/007, G11B20/14, G11B20/18, H04N9/806, G11B27/36, G11B7/24085, H04N21/236, H04N21/4402, H04N21/433, H04N21/438, H04N21/426, H04N21/434, H04N21/432, H04N21/2381, H04N21/4363, H04N5/76, G11B5/09|
|Cooperative Classification||G11B20/1251, G11B27/36, H04N21/4381, H04N21/4334, G11B27/329, G11B20/1426, G11B2020/1232, G11B27/105, G11B2220/2545, H04N9/8063, H04N21/23614, H04N5/9268, G11B27/11, G11B2220/2529, H04N21/4363, G11B20/12, H04N9/8233, H04N5/945, G11B7/007, G11B2220/65, G11B20/00086, G11B7/013, G11B20/1833, G11B27/034, G11B7/00745, G11B20/1809, H04N21/2381, G11B2220/218, H04N21/42646, G11B2220/2562, G11B27/3027, H04N9/8042, H04N21/4348, G11B2220/213, G11B2020/1271, H04N21/440209, G11B7/004, H04N5/9261, G11B20/1813, H04N21/4325, G11B27/3063, H04N9/877, G11B7/0037, H04N5/85, G11B7/24085|
|European Classification||G11B20/18D, H04N21/4363, H04N21/2381, G11B27/10A1, G11B20/12D4, H04N21/434W, G11B20/18B1, H04N21/438D, H04N9/877, G11B20/14A2B, G11B27/034, H04N5/926B, G11B27/30C2, H04N21/4402D, H04N5/945, G11B20/18B2, G11B27/32D2, G11B27/30C, H04N9/804B, H04N21/236W, H04N21/426D, H04N21/432P, H04N21/433R, G11B20/00P|
|Sep 30, 2005||FPAY||Fee payment|
Year of fee payment: 8
|Sep 30, 2009||FPAY||Fee payment|
Year of fee payment: 12