JP2004095165A - Reproducing device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a reproducing device which corresponds to a recording medium (disc) for recording data, is used for both audio data and general data to be able to record/reproduce data, is suitable for miniaturization and power saving and further prevents the use of an illegal copy. <P>SOLUTION: A data management structure provided with first management information on the recording medium and second management information that is physically arranged at the first position in a general data file recording area and is for managing a general data file is formed as management information for managing a reproducing operation of an audio data or general data file. As a reproducing device that corresponds to a recording medium, wherein specific keyword information is recorded in an area managed as a defective area in the first management information and/or the second management information, a defective area shown in the first management information and the second management information is retrieved, keyword information is read, and processing to be carried out is selected in accordance with the existence/absence of keyword information to be read out and contents of read keyword information. <P>COPYRIGHT: (C)2004,JPO

Description

<< The present invention relates to a reproducing apparatus corresponding to a recording medium (disk) for recording data.

2. Description of the Related Art A magneto-optical disk as a recording device, a reproducing device, and a recording medium capable of recording / reproducing music or the like has been put into practical use. What can be done (so-called mini-discs) are also known.

In the case of using this mini-disc system, so-called music is recorded / reproduced. In this mini-disc system, data other than music information can be recorded / reproduced.

In the present specification, a so-called digitized audio signal such as music or voice recorded on a magneto-optical disk is particularly called "audio data", and one unit thereof is called "song" or "audio track". It shall be. Data other than audio data, such as characters and graphics, which is used by information equipment such as a computer and recorded on a magneto-optical disk is called "general data" and is distinguished from audio data. One recording / reproduction unit of the general data is referred to as a “data file”.

By the way, it is not very suitable to use a mini disk system originally configured for music for general data so that information can be searched and updated. Especially, in the case of music management information for music use, unlike data file management information for data use, name data and attribute data for search are not important (at least, Address may be managed), data for transmitting search data to an external device may not be required, and there may be many audio data with a small data volume (for example, very short music) It is not necessary to deal with the case where a large number of small data files such as general data exist because it is unlikely that data files will be recorded. For example, the management information for audio data described below can handle only up to 255 songs. And not.

In these various points, the management information of the music for the music purpose is generated so as to be suitable for the music purpose, and cannot be said to be suitable for the general data. That is, for example, there is a problem that it is not appropriate to extend the mini-disc system for recording and reproducing general data by using the management method as it is.
Although the mini disk system is taken as an example, the same can be said for other types of recording / reproducing systems for music.

Further, in consideration of the management form when general data is recorded, in order to effectively use the recorded general data, the management information is edited and sorted by the evaluation coefficient of the file name, replaced, and linked to the file name table. Processing, such as changing the file allocation table, maintaining the file allocation table, etc., requires a large-capacity memory, consumes large power, and increases the required processing. The editing processing speed is also reduced. For example, if these processes are to be sufficiently executed by a small device such as a portable device driven by a battery, there is a problem that a burden is large in terms of power consumption, and it is difficult to achieve a sufficient speed in terms of a processing speed. is there.

Also, simply allowing a data file to be recorded / reproduced is not sufficient in terms of copy guard and the like. That is, it is easy to create an illegal disk by copying the disk software provided by the data software creator without the consent of the creator, and measures against this are desired.

SUMMARY OF THE INVENTION The present invention has been made in view of such problems, and extends a recording / reproducing system for music to data recording / reproducing, and performs recording / reproducing for both audio data and general data. For the purpose of making it possible to make devices suitable for miniaturization and power saving, and to prevent illegal copying, a recording medium suitable for these was used. A playback device is provided.

In addition, a data management structure including the first management information and the second management information is formed, and an area managed as a defect area in the first management information and / or the second management information. A keyword reading unit and an execution control unit are provided as a reproducing apparatus corresponding to a recording medium on which specific keyword information is recorded.
The keyword reading means searches for a defective area indicated in the first management information or the second management information so that the keyword information can be read.
The execution control unit selects a process to be executed according to the presence or absence of keyword information to be read by the keyword reading unit or the content of the read keyword information.

In addition, a data management structure including the first management information and the second management information is formed, and the address of the first management information is set in a predetermined management area in which the first management information is arranged. A keyword reading unit and an execution control unit are provided as a playback device corresponding to a recording medium containing at least specific keyword information as information recorded from an address calculated by a predetermined calculation using.
The keyword reading means accesses the address calculated by a predetermined operation using the address of the first management information so that the keyword information can be read.
The execution control unit selects a process to be executed according to the presence or absence of keyword information to be read by the keyword reading unit or the content of the read keyword information.

In these playback devices, if there is no keyword information to be read by the keyword reading means, or if the read keyword information is not correct, the execution control means performs a playback operation on the recording medium. Is controlled not to execute.

For example, in addition to the first management information provided for audio data, by providing second management information suitable for data file management for general data, a recording medium for music can be expanded for data use and audio data can be expanded. A recording medium corresponding to both data and general data can be realized. The second management information can be accessed by arranging it at the physically leading position in the area where the general data file is recorded, and can be used for reproduction management of the general data file. It becomes.

At this time, in the first management information, the area in which the general data file is recorded is managed as general data parts, so that the audio data area and the general data area can be identified in the first management information. Erroneous recording / erroneous erasure / reproduction errors based on the mixture are prevented.

Further, in addition to the first management information and the second management information, by providing third management information capable of managing a general data file that is not managed as a reproduction target by the first and second management information, This can be used for a simple recording / reproducing operation. That is, it is possible to hold a file that does not require complicated editing, separately from the data file managed by the second management information.

The third management information is specified to be arranged in any one of a plurality of general data parts that are not reproduced and managed by the first and / or second management information, or In a predetermined management area where the first management information is arranged, it can be accessed and read by arranging it at a position corresponding to an address calculated by a predetermined calculation using the address of the first management information. It becomes.

For one or more general data parts in which general data files managed by the third management information are recorded, one or both of the first management information and the second management information are used as recording / reproduction targets. By managing the defect area as a non-existent defect area, it is possible to use the area as an area independent of the first management information and the second management information. That is, they are not recorded / reproduced by the first management information or the second management information, and are not erased or erroneously reproduced.

{Circle around (2)} By making such a general data file managed by the third management information also managed by the second management information, it can be incorporated as an original data file.

Here, when the general data file managed by the third management information is included in the management target by the second management information, it is inconvenient to erase / rewrite by the operation using the third management information. However, in the third management information, the inconvenience is eliminated by managing the general data file as non-rewritable data.

Further, when the third management information is arranged in any one of the one or a plurality of general data parts which are not reproduced and managed by the first and / or second management information, the third management information is stored in the third data. Area is recorded as a defective area that is not a recording / reproducing target in one or both of the first management information and the second management information, so that the first management information The recording / reproducing operation is not performed by the second management information, and is not erased or erroneously reproduced.

Further, when specific keyword information is recorded in an area managed as a defective area in the first management information and / or the second management information, the normal first management information and the second The recording / reproduction operation is not performed by the management information, and the keyword information is not copied. Therefore, this keyword information can be used as copy guard data.
The specific keyword information may be included in information recorded from an address calculated by a predetermined operation using the address of the first management information in a predetermined management area where the first management information is arranged. The same is true.

According to the reproducing apparatus of the present invention as described above, the following various excellent effects can be obtained.

First, in addition to the first management information (U-TOC) provided for track management of audio data and the like, second management information (data U-TOC) suitable for data file management for general data is provided. By providing such a recording medium, a recording medium for music can be extended for data, and a recording medium for both audio data and general data can be realized. The second management information can be accessed by arranging it at the physically leading position in the area where the general data file is recorded, and can be used for reproduction management of the general data file. It becomes.

In the first management information, an area in which a general data file is recorded is managed as a general data part, that is, a part of a data track, so that the audio data area and the general data area are identified in the first management information. This makes it possible to prevent erroneous recording / erroneous erasure / reproduction errors or the like based on data mixture.

Furthermore, in addition to the first management information (U-TOC) and the second management information (data U-TOC), it is possible to manage a general data file that is not managed as a reproduction target by the first and second management information. By providing the third management information (simple U-TOC) that can be used, this can be used for a simple recording / reproducing operation. That is, it is possible to hold a file that does not require complicated editing, separately from the data file managed by the second management information.
When recording / reproducing is performed according to the third management information, there is no need to read / edit the second management information. Therefore, a large memory capacity is not required at the time of recording / reproducing / editing the data file. Also, power consumption can be reduced. Therefore, it is very suitable for small devices and the like.

Further, the third management information may be specified to be arranged in any one of the one or a plurality of general data parts which are not reproduced and managed by the first and / or second management information, or In a predetermined management area in which the management information of the first management information is arranged, by arranging at a position corresponding to an address calculated by a predetermined operation using the address of the first management information, quick access and reading can be performed. It becomes possible.

For one or more general data parts in which general data files managed by the third management information are recorded, one or both of the first management information and the second management information are used as recording / reproduction targets. By managing the defect area as a non-existent defect area, it is possible to use the area as an area independent of the first management information and the second management information. That is, it is not possible to perform the recording / reproducing operation based on the first management information or the second management information, and it is possible to prevent the data from being erased or erroneously reproduced.

Further, by making such a general data file managed by the third management information also managed by the second management information, it can be incorporated as an original data file.
As a result, a data file corresponding to the third management information can be played back by normal data file playback using the second management information, and therefore, does not have a playback function based on the third management information. It can be made reproducible also in the device.
Furthermore, by incorporating a data file corresponding to the third management information under the management of the second management information, the data file becomes a target of an advanced editing operation in the second management information and can be effectively used in various ways. become.

In addition, when a general data file managed by the third management information is included in a management target by the second management information, erasure / rewriting of the data file by an operation using the third management information is prohibited. This prevents the data file managed by the second management information from being erased without using the second management information.

In the case where the third management information is arranged in any one of the one or a plurality of general data parts which are determined to be defective areas by the first and / or second management information, The area where the third management information is recorded is managed as a defective area that is not a recording / reproduction target in one or both of the first management information and the second management information, so that the first management information and / or the second management information are managed as a defective area. It is not a recording / reproducing operation target by the management information and the second management information, and is not erased or erroneously reproduced.

Further, by setting specific keyword information to be recorded in an area managed as a defect area in the first management information and / or the second management information, the keyword is stored in a copy destination recording medium. Since information is not copied or correct keyword information cannot be obtained, an advanced copy guard system can be realized by not performing a reproducing operation or the like on such a recording medium.

Hereinafter, embodiments of the present invention will be described in the following order.

I. Configuration of recording / reproducing apparatus I-1 External appearance example I-2 Internal block

II. Disk structure II-1 Cluster structure II-2 Track structure II-3 P-TOC sector II-4 U-TOC sector (first management information)
II-5 Data U-TOC sector (second management information)
II-5-a Overall structure II-5-b Boot area II-5-c Volume descriptor II-5-d Volume space bitmap II-5-e Management table II-5-f Directory record block II-5-g Extent record block II-6 Data sector

III. Data file playback processing

IV. Recording / reproducing method using simple U-TOC (Type A)
IV-1 Simple U-TOC sector (third management information)
IV-2 Management state when simple U-TOC is recorded IV-3 Data file recording process using simple U-TOC IV-4 Data file playback process using simple U-TOC and transfer process to data U-TOC IV-5 Copy guard data recording using simple U-TOC IV-6 Reproduction processing corresponding to copy guard

V. Recording / reproducing method using simple U-TOC (Type B)
V-1 Management state when simple U-TOC is recorded V-2 Data file recording processing using simple U-TOC V-3 Data file reproduction processing by simple U-TOC and transfer processing to data U-TOC V-4 Copy guard data recording using simple U-TOC V-5 Reproduction processing corresponding to copy guard

VI. Recording position of data file managed by simple U-TOC

I. Configuration of recording / playback device

I-1 Appearance example

FIG. 1 shows the appearance of a recording / reproducing apparatus and a disk according to an embodiment.
As the disk 1, a magneto-optical disk is used, and the outside thereof is housed in a cartridge K as shown in FIG. 1, and the disk recording surface is exposed by sliding a shutter S.
The recording / reproducing apparatus 10 is provided with a disk insertion portion 11 into which a cartridge K containing the disk 1 is loaded. When the cartridge K is inserted into the disk insertion portion 11, the shutter S slides by an internal mechanism (not shown). Then, the surface of the disk 1 is exposed to be in a recordable or reproducible state.

A key input unit 12 for user operation and a display unit 13 for displaying and outputting menu information for data search and the searched data are provided on the upper surface of the housing of the recording and reproducing apparatus 10. The key input unit 12 includes a cursor movement key, an enter key, a data input key, and the like.
Reference numeral 14 denotes an image scanner unit, which detects image information written on a sheet of paper, converts the image information into dot data, and can input the dot data as image data.
Further, reference numeral 15 denotes an input / output connector unit, which can transmit and receive data to and from other information devices (computers, word processors, etc.) by connecting a communication cable C.

Reference numeral 16 denotes a terminal used for inputting / outputting an analog audio signal, and a line input / output of a reproduced audio signal from the disk 1 or an audio signal to be recorded on the disk 1 is made to another audio device via an audio code 17. You.

I-2 Internal block

FIG. 2 shows a configuration of a main part of the recording / reproducing apparatus 10.
FIG. 2 shows a state where the disk 1 (the cartridge K containing the disk 1) is loaded. Reference numeral 21 denotes a system controller that controls various operations of the recording / reproducing apparatus, and is formed by, for example, a microcomputer.
Reference numeral 22 denotes a spindle motor, and the loaded disk 1 is driven to rotate by the spindle motor 22. Reference numeral 23 denotes an optical head for irradiating a laser beam to the disk 1 during recording / reproducing, which produces a high-level laser output for heating a recording track to the Curie temperature during recording, and a reflected light due to the magnetic Kerr effect during reproduction. Provides a relatively low level laser output for detecting data from

Therefore, the optical head 23 is equipped with a laser diode as a laser output unit, an optical system including a deflection beam splitter and an objective lens, and a detector for detecting reflected light. The objective lens 23a is held by a two-axis mechanism 24 so as to be displaceable in the disk radial direction and in a direction of coming into contact with and separating from the disk, and the entire optical head 23 is movable in the disk radial direction by a thread mechanism 25.

Reference numeral 26 denotes a magnetic head for applying a magnetic field modulated by the supplied information to the magneto-optical disk, and is disposed at a position facing the optical head 23 with the disk 1 interposed therebetween.

(4) The information detected from the disk 21 by the optical head 23 by the reproducing operation is supplied to the RF amplifier 27. The RF amplifier 27 calculates the reproduced RF signal, tracking error signal, focus error signal, absolute position information (absolute position information recorded as a pre-groove (wobbling groove) on the disc 1), and address information by calculating the supplied information. , Subcode information, a focus monitor signal, and the like. Then, the extracted reproduced RF signal is supplied to the decoder unit 28. Further, the tracking error signal and the focus error signal are supplied to the servo circuit 29. Further, the focus monitor signal is supplied to the system controller 21.

Further, the absolute position information obtained by decoding the pre-groove information or the address information recorded as data, which is output from the address decoder 29, is supplied to the system controller 21 via the decoder unit 28, and various control operations are performed. Used for

The servo circuit 29 generates various servo drive signals based on the supplied tracking error signal, focus error signal, track jump command, seek command, rotation speed detection information, and the like from the system controller 21, and generates the two-axis mechanism 24 and the thread mechanism 25. To control focus and tracking, and control the spindle motor 22 to a constant angular velocity (CAV) or a constant linear velocity (CLV).

The reproduced RF signal is subjected to decoding processing such as EFM demodulation, CIRC decoding, and ACIRC decoding by the decoder unit 28, and then is subjected to predetermined processing via the system controller 21.

The information supplied to the system controller 21 as information to be recorded on the disk 1 at the time of the recording operation is subjected to encoding processing such as ACIRC encoding, CIRC encoding, and EFM modulation in the encoder unit 30, and then to the magnetic head driving circuit 31. Supplied.

The magnetic head drive circuit 31 supplies a magnetic head drive signal to the magnetic head 26 according to the encoded recording data. That is, the magnetic head 26 applies the N or S magnetic field to the disk 1. At this time, the system controller 21 supplies a control signal to the optical head 23 so as to output a laser beam at a recording level.

# 32 is a conversion memory for converting code data into font data, and performs font conversion processing for displaying character data and the like read from the disk 1.

Reference numeral 33 denotes a buffer RAM, which temporarily stores dot data captured by the image scanner 14, display data displayed on the display unit 13, transmission and reception data by the connector unit 15, and audio data read from the disk 1. And a temporary storage unit when outputting a data file.

When performing a recording / reproducing operation on the disk 1, management information recorded on the disk 1, that is, a pre-mastered TOC (hereinafter, referred to as P-TOC), a TOC for managing audio data recording / reproduction, and the like. (Hereinafter, referred to as U-TOC), a TOC for managing general data recording / reproduction (hereinafter, referred to as data U-TOC), and a TOC (hereinafter, referred to as simple U-TOC) used for simple general data recording / reproduction described later. -TOC), and the system controller 21 determines an address to be recorded and an address to search and reproduce data according to the management information. The management information is stored in the buffer RAM 33. You.
For example, when the disk 1 is loaded, the system controller 21 reads out the P-TOC and the U-TOC by executing a reproduction operation of a management information area (for example, the innermost side of the disk) and stores the read-out information in the buffer RAM 33. The information can be referred to at the time of recording / reproducing operation on the disc 1 thereafter.

The U-TOC, the data U-TOC, and the simple U-TOC are rewritten in accordance with data recording or erasing. The system controller 21 stores this rewriting in the buffer RAM 33 every time a recording / erasing operation is performed. The management information area of the disc 1 is rewritten at a predetermined timing in accordance with the rewriting operation.

A communication circuit 34 transmits and receives data to and from an external device via the connector unit 15.
Reference numeral 35 denotes a display controller, which is a control circuit for causing the display unit 13 to execute display data from the system controller 21, that is, display of a search menu, display of data read from the disk 1, and the like.
With the above configuration, the recording / reproducing apparatus 10 can perform a recording operation and a reproducing operation of various general data on the disk 1.

When the audio data is reproduced from the disk 1 and output as an audio signal, the reproduced RF signal as the audio data read from the disk 1 is subjected to EFM demodulation, decoding processing such as CIRC, etc. The data is temporarily written into the buffer RAM 33 by the system controller 21. The reading of audio data from the magneto-optical disk 1 by the optical head 23 and the transfer of reproduced audio data from the optical head 23 to the buffer RAM 33 are performed at 1.41 Mbit / sec (intermittently).

The data written in the buffer RAM 33 is read out at a timing when the transfer of the reproduction audio data becomes 0.3 Mbit / sec, and is supplied to the audio compression decoder unit 38. In this recording / reproducing system, an audio signal is recorded after being subjected to data compression processing at a digital data stage. For example, a process of compressing data of a sampling frequency of 44.1 Kbit (≒ 1.4 Mbit / sec) at 16 Mbit / s to 0.3 Mbit / sec of about 1/5 is performed. Therefore, at the time of reproduction, a decoding process which is a reverse process to the compression process is performed.
When a reproduction signal process such as a decoding process for the audio compression process is performed in the decoder unit 38, the signal is converted into an analog signal by the D / A converter 39, and is output from the terminal 16 b via a predetermined amplifier circuit or the code 17 to a line output. And output. For example, they are output as L and R audio signals.

When an audio signal recording operation is performed on the disk 1, a recording signal (analog audio signal) supplied to the terminal 16a from a line input system by the code 17 or a microphone system (not shown) is converted to an A / D converter. After being converted into digital data having a sampling frequency of 44.1 Kbits and quantization of 16 bits by 36, the digital data is supplied to an encoder section 37 and subjected to the above-described audio compression encoding processing. The recording data compressed by the encoder unit 34 is once written in the buffer RAM 33 by the system controller 21, read out at a predetermined timing, and sent to the encoder unit 30. Then, after being subjected to encoding processing such as CIRC encoding and EFM modulation by the encoder unit 30, it is supplied to the magnetic head drive circuit 31.

(4) The magnetic head drive circuit 31 supplies a magnetic head drive signal to the magnetic head 26 in accordance with the encoded recording audio data as in the case of general data recording. That is, the magnetic head 26 causes the magnetic head 26 to apply an N or S magnetic field. At this time, the system controller 21 supplies a control signal to the optical head 23 so as to output a laser beam at a recording level.

Although the reproducing operation has been described assuming that the disk 1 is a magneto-optical disk, an optical disk (and pit data such as P-TOC in a magneto-optical disk) on which data is recorded in a pit form like a CD is described. In this case, the reproduction is possible as a so-called mini-disc reproducing apparatus. In this case, the optical head 23 does not use the magnetic Kerr effect but the reproduction RF according to the change in the reflected light level due to the presence or absence of the pit similarly to the case of the CD player. This is to extract the signal. Of course, the magnetic field recording operation is not performed on the pit data area of the optical disk and the magneto-optical disk.

As described above, the TOC information on the disk 1 is read into the buffer RAM 33. The disk 1 corresponding to the recording / reproducing apparatus of this embodiment is a pre-mastered type (optical disk) in which music and the like are recorded in advance. A rewritable type (magneto-optical disk) that allows the user to record audio data and general data as described later, and a ROM area in which data files, music, and the like are recorded in advance, and a recordable light. There is a hybrid type provided with a magnetic area. In these discs, data for managing an area in which music and the like are already recorded and an unrecorded area are recorded as TOC information according to the type.

When recording audio data (songs) as described above, an unrecorded area on the disc is searched from the U-TOC, and audio data is recorded there. When reproducing audio data, the area in which the music to be reproduced is recorded is determined from the P-TOC when the music is a pre-mastered music, or the U-M is determined when the music is magneto-optically recorded. Judgment is made from the TOC, and the reproduction operation is performed by accessing the area.
On the other hand, for the operation of recording / reproducing general data, information of data U-TOC is used as management information.
The P-TOC is also recorded in the form of a ROM as pit data on the magneto-optical disk.

II. Disc structure

II-1 Cluster structure

In the mini-disk system, recording is performed on the magneto-optical disk 1 in units called clusters. This one cluster corresponds to two or three tracks. These clusters are temporally continued to form one track, that is, a song or data track.

As shown in FIG. 3, one cluster includes a sub data area of 4 sectors and a main data area of 32 sectors. One sector is 2352 bytes. The address is recorded for each sector.
In each sector, data is actually recorded in a 2048-byte area, and the other bytes are used for a header such as a synchronization pattern and an address, an error correction code, and the like.
The 4-sector sub-data area is used as sub-data and linking area, and TOC data, audio data, general data, etc. are recorded in the 32-sector main data area.

II-2 Truck structure

Here, the track structure in the disk 1 will be described, and the positional relationship and management mode of the P-TOC and U-TOC, and the data U-TOC will be described.

In the case of a magneto-optical disk, an area (pit area) in which data is recorded by embossed pits and a groove are provided as a so-called magneto-optical area, as roughly shown as a pit area in FIG. It is divided into MO areas.
Here, the pit area is a read-only management area in which a P-TOC is recorded, and a P-TOC sector described later is repeatedly recorded.

(5) Following the innermost pit area, the MO area is the area up to the lead-out area on the outermost circumference of the disc, but the recordable area from the position following the pit area to immediately before the lead-out area is the recordable area.

Further, the head area of the recordable area is a recording / reproduction management area, and is used as a U-TOC recording area or a laser power calibration area.
The U-TOC is recorded continuously at a required position in the recording / reproduction management area for three clusters, and the P-TOC indicates at which cluster address in the recording / reproduction management area the U-TOC is recorded. .

The recordable user area in which audio data and general data are actually recorded is an area following the recording / playback management area.
In this recordable user area, for example audio tracks, as shown as _{M 1, M 2, M 3} , i.e. or music is recorded, also the data file as shown as FL _1, FL _2, FL ₃ or is recorded .
The data U-TOC for managing the data file is recorded in the innermost part of the data file. In this example, so that the position immediately before the data file FL ₁ data U-TOC is recorded.

部分 In the recordable user area, the area where no music or data file is recorded is a free area. In other words, it is an unrecorded area and is managed as an area in which music and data files can be recorded in the future.

For example, the U-TOC manages a disk recorded as shown in FIG. 4A as shown in FIG. 4B.
That For each audio track as a _{M 1, M 2, M 3} , and manages the start address and end address. The same applies to the free area.
However, the site where the data file FL _1, FL _2, FL _3, and the data U-TOC is recorded are collectively managed as a single data track. Note that EB indicates an area in the data track managed by the U-TOC where no data file is actually recorded.

On the other hand, in the data U-TOC, as shown in FIG. 4C, the data files FL ₁ , FL ₂ , FL ₃ and the unrecorded blocks EB in the data track are managed.

Therefore, when the recording / reproducing apparatus reproduces an audio track, the reproduction is performed by discriminating the start address and the end address from the U-TOC, and when reproducing the data file, the data U-TOC is searched for from the U-TOC. Then, a required data file is accessed using the data U-TOC.

II-3 P-TOC sector

Next, the format of the P-TOC in the disc 1 will be described.
As the P-TOC information, designation of an area such as a recordable area (recordable user area) of a disc, management of a ROM area, and the like are performed. In the case of a premastered disc or a hybrid disc, it is also possible to manage audio tracks and data tracks recorded in ROM.

FIG. 5 shows the format of the P-TOC.
FIG. 5 shows the first sector (sector 0) of the P-TOC information repeatedly recorded in the read-only management area shown in FIG.
Note that sectors 0 to 7 are prepared as P-TOC sectors, but sectors 1 and subsequent sectors are optional.

The data area of the P-TOC sector is configured as a data area of, for example, 4 bytes × 588, 2352 bytes, and a synchronization pattern composed of all 0s or all 1s of 1 byte data is recorded at the head position.
Further, a high-order and low-order 2-byte cluster address and a 1-byte sector address are recorded as the address of this sector, and a 1-byte "02h" is added to form a header.
In the present specification, numerical values with "h" are in so-called hexadecimal notation.

(4) Following the header, an identification code in ASCII code corresponding to the character "MINX" is added at a predetermined address position. This “MINX” is an identification code indicating that the area is a P-TOC area on a disk for data file use.

Subsequently, the disc type (Disc type), recording level (Rec power), the number of the first track recorded (First TNO), and the number of the last track (Last TNO) are shown.
As the disc type, a code identifying whether the disc is a read-only pre-mastered disc, a recordable magneto-optical disc, or a hybrid disc is recorded.

The start address of the lead-out area of FIG. 4 is shown as a read-out start address LO _A followed.
Also, as the sector use status (Used sectors), each bit of this 1 byte corresponds to P-TOC sectors 0 to 7, and indicates whether or not each sector is used.

The power cal area start address PC _A is a start address of a power calibration area provided in the recording / reproduction management area.
The address of the start position of the U-TOC which is recorded in the recording reproduction management area as U-TOC start address UST _A is written.
In addition, the start address RST _A of the recordable user area is recorded.

Next, a correspondence table instruction data section having table pointers (P-TNO1 to P-TNO255) for associating each recorded track and the like with a parts table in a management table section described later is prepared.

In the area following the correspondence table instruction data section, a management table section in which 255 parts tables from (01h) to (FFh) are provided is prepared. In each of the parts tables, a start address as a starting point, an end address as an end, and mode information (track mode) of the part are recorded.
Note that a part refers to a track portion on which a series of data is physically continuously recorded on a disk.

The track mode information in each part table records, for example, information as to whether the part is set to prohibit overwriting or data copying, audio information, monaural / stereo type, and the like. .

In each of the parts tables from (01h) to (FFh) in the management table section, the contents of the parts are indicated by the table pointers (P-TNO1 to P-TNO255) of the corresponding table instruction data section. That is, for the first track, the parts table (01h) is recorded as the table pointer P-TNO1. Actually, a numerical value capable of indicating a certain parts table at a byte position in the TOC sector 0 by a predetermined calculation process is described in the table pointer.
In this case, the start address of the parts table (01h) is the start address of the recording position of the first track, and similarly, the end address is the address of the end position of the first track. Further, the track mode information is information on the first track.

Similarly, for the second track, its start address, end address, and track mode information are recorded in the parts table (02h) indicated by the table pointer P-TNO2.
Similarly, table pointers are prepared up to P-TNO255, so that up to 255th track can be managed on the TOC.
By forming the TOC sector 0 in this way, for example, at the time of reproduction, a predetermined music piece can be accessed and reproduced.

However, the track managed by the P-TOC is only a so-called premastered track. Therefore, in the case of a magneto-optical disk on which a ROM type audio track or data track is not recorded, the above-described correspondence table instruction data section and management table Since no part is used, all bytes are set to "00h".

II-4 U-TOC sector (first management information)

FIG. 6 shows the format of the first sector (sector 0) of the U-TOC. The U-TOC sector is a data area in which management information is mainly recorded on music recorded by the user and on a free area where new music can be recorded.
Note that sectors 0 to 7 are prepared for the U-TOC sector, but sectors 1 and thereafter are optional.

For example, when recording a certain music or data file on the disc 1, the recording / reproducing apparatus 10 searches for a free area on the disc from the U-TOC and records it. In addition, at the time of reproduction, an area or a data track where a music (audio track) to be reproduced is recorded is determined from the U-TOC information, and the reproduction operation is performed by accessing the area.

The U-TOC sector shown in FIG. 6 is provided with a header indicating a synchronization pattern and an address, similarly to the P-TOC sector.
Subsequently, at a predetermined address position, a maker code, a model code, a track number of the first track (First TNO), a track number of the last track (Last TNO), a sector use state (Used sectors), a disk serial number, and a disk ID are provided. Be recorded.
In one byte of the sector use status, each bit corresponds to U-TOC sectors 0 to 7, and indicates whether or not each sector is used.

Furthermore, in order to manage the audio track on which the user has recorded, the data track on which the data file is recorded, and the free area in association with a management table section to be described later, various table pointers (corresponding table instruction data sections) are used. An area for recording P-DFA, P-EMPTY, P-FRA, and P-TNO1 to P-TNO255) is prepared.

(4) 255 parts tables from (01h) to (FFh) are provided as management tables corresponding to the table pointers (P-DFA to P-TNO255). As in the P-TOC sector 0 in FIG. 5, each part table records a start address serving as a starting point, an end address serving as an end, and mode information (track mode) of the part. Further, in the case of the U-TOC sector 0, since the parts indicated in each part table may be successively connected to other parts, the parts table in which the start address and the end address of the connected parts are recorded Can be recorded.

In the case of the mini-disc system, for example, even if data of one music is physically discontinuous, that is, even if recorded over a plurality of parts, the reproduction operation is not hindered by reproducing while accessing between parts, so that there is no hindrance to the reproduction operation. The music or the like recorded by the user may be recorded in a plurality of parts for the purpose of efficient use of the recordable area. For this reason, link information is provided, for example, the numbers (01h) to (FFh) given to the respective parts tables (actually indicated by a numerical value which is a byte position in the U-TOC sector 0 by a predetermined arithmetic processing) Thus, the part tables can be connected by specifying the part tables to be connected.
It should be noted that since the pre-recorded music and data files are not usually divided into parts, the link information in the P-TOC sector 0 is all "(00h)" as shown in FIG.

In other words, in the management table section in the U-TOC sector 0, one parts table represents one part. For example, for a music composed of three parts connected, three parts connected by link information The table manages the position of each part.

Each part table from (01h) to (FFh) in the management table section of the U-TOC sector 0 is a table pointer (P-DFA, P-EMPTY, P-FRA, P-TNO1 to P-TNO1 to P-TNO1) in the corresponding table instruction data section. -TNO255) indicates the contents of the part as follows.

The table pointer P-DFA is attached to a defective area on the magneto-optical disk 1, and the start of one or more parts tables indicating a track portion (= part) serving as a defective area due to a scratch or the like is shown. Parts table is specified. That is, when a defective part exists, any one of (01h) to (FFh) is recorded in the table pointer P-DFA, and the corresponding part table indicates the defective part by the start and end addresses. . If another defective part exists, another part table is designated as link information in the part table, and the defective part is also shown in the part table. If there is no other defective part, the link information is set to, for example, "(00h)", and there is no link thereafter.

The table pointer P-EMPTY indicates the head part table of one or more unused part tables in the management table section. If an unused part table exists, the table pointer P-EMPTY is set as (01h) as the table pointer P-EMPTY. ) ~ (FFh) is recorded. If there are multiple unused part tables, the part table specified by the table pointer P-EMPTY is sequentially specified by the link information, and all the unused part tables are connected on the management table section. Is done.

The table pointer P-FRA indicates a writable free area (including an erasure area) of data on the magneto-optical disk 1, and one or a plurality of parts indicating a track part (= part) serving as the free area The first parts table in the table is specified. In other words, if there is a free area, any one of (01h) to (FFh) is recorded in the table pointer P-FRA, and the corresponding part table is indicated by the start and end addresses in the corresponding parts table. Have been. Further, when there are a plurality of such parts, that is, when there are a plurality of part tables, the link information sequentially designates the parts table whose link information is “(00h)”.

FIG. 7 schematically shows the management state of parts that are free areas by using a parts table. This is because when the part (03h) (18h) (1Fh) (2Bh) (E3h) is set as a free area, this state follows the table pointer P-FRA and the parts table (03h) (18h) (1Fh) (2Bh) ) (E3h) indicates the state represented by the link.
It should be noted that the above-described management of the defective area and the unused parts table is the same.

By the way, if the disk is a virgin disk on which no music or data files are recorded and there is no defect on the magneto-optical disk, the part table (01h) is designated by the table pointer P-FRA, and the disk recorder It is indicated that the entire bull user area is a free area. In this case, since the remaining part tables (02h) to (FFh) are not used, the part table (02h) is designated by the table pointer P-EMPTY described above, and the part table (02h) is not used. The parts table (03h) is specified as link information, and so on up to the parts table (FFh). In this case, the link information of the parts table (FFh) is set to "(00h)" indicating that there is no connection thereafter.
At this time, in the parts table (01h), the value of the start address (RST _A ) of the recordable user area is recorded as the start address, and the address (LO _A −1) immediately before the lead-out start address is recorded as the end address. ) Will be recorded.

The table pointers P-TNO1 to P-TNO255 indicate tracks on which recording has been performed on the magneto-optical disk 1 by the user. For example, the table pointer P-TNO1 indicates one or a plurality of parts on which data of the first track is recorded. The part table indicating the part that is the first in time is specified.

For example, when the music set as the first track is recorded as one part on the disc, the recording area of the first track is recorded as the start and end addresses in the parts table indicated by the table pointer P-TNO1. I have.

{Circle around (2)} For example, in the case where the music set as the second track is discretely recorded on a plurality of parts on the disc, each part is designated in order of time to indicate the recording position of the music. In other words, from the part table designated by the table pointer P-TNO2, another part table is sequentially designated by the link information in a temporal order, and linked to the part table in which the link information is "(00h)". (Same form as above, FIG. 7). In this way, for example, all the parts on which the data constituting the second music are recorded are sequentially specified and recorded, so that the data of the U-TOC sector 0 can be used to reproduce the second track, When performing overwriting on the area of two tracks, the optical head 23 and the magnetic head 26 are accessed so that continuous music information can be extracted from discrete parts, and recording using the recording area efficiently can be performed.

Further, in the present embodiment, the disc 1 may be used for data recording purpose (or may be used for data only) as described later, but in this U-TOC, the disc 1 is used for data purpose. Data tracks are also managed in the same way as music.

It should be noted that the data track is generally constituted by a plurality of data files, and for example, all parts on which general data is recorded on a disc are included in one data track.
A unit including all parts where general data is recorded on one disk is called a volume.

When all parts on which general data is recorded on the magneto-optical disk are linked to form one data track, the entire data track becomes one volume.
In the case of a hybrid disc, data tracks can also be formed in the pit area, and there may be two data tracks in the pit area and the recordable user area.

For example, when a data track exists as the fourth track as shown in FIG. 4, the area is managed by the table pointer P-TNO4.
That is, for example, the start address and the end address of the data track are indicated in the parts table guided by the table pointer P-TNO4. When the data track is divided into a plurality of parts, a part table indicating the start address and the end address of each part is linked.

In this case, the track mode information identifies that the part indicated in the parts table is a part constituting a data track instead of an audio track.
Track mode, (01h) ~ but are provided one byte (8 bits of d ₁ to d ₈₎ in each part table of up to (FFh), the each bit respectively show various modes state as follows ing.

For example, bit d ₁ indicates whether the part is recordable / non-recordable, bit d ₂ indicates whether the part is copyright protected, bit d ₃ indicates whether the part is copy-recorded after the original / 2 generation, d ₄ is the part Do audio data or general data, bits d _5, d ₆ whether the parts or normal audio, bit d ₇ its parts or monaural audio data or stereo audio data, the bit d ₈ thereof A mode is indicated for each of the emphasis processing of the data of the part.

Therefore, when a part is managed as a general data area, the bit d ₄ of this track mode is set to, for example, “1” (bit d ₄ = “0” in the case of audio data) in the corresponding part table, It will be identified as a track.
When general data is recorded as ROM on a disc as premastered pits, the data is managed in the P-TOC in the same manner as in the case of premastered music. of bit d ₄ is set to "1", as distinguished from the pre-mastered music.

II-5 Data U-TOC sector (second management information)

II-5-a Overall structure

As described above, only parts as data tracks are managed in the U-TOC, and management of each data file in the data track is performed by the data U-TOC.

FIG. 8 shows an example of the structure of a data track. As shown in FIG. 8A, the data U-TOC is recorded at the physical head position on the data track. That is, the data U-TOC is recorded at the position closest to the inner circumference of the disk in the data track. When the data track is divided into a plurality of parts, the data U-TOC is provided at the head of the part located on the innermost side of the disk.
This data U-TOC is composed of a boot area of one cluster and a volume management area of 16 clusters as shown in FIG.

As can be seen from FIG. 8B, the area following the data U-TOC is a file extent area. The file Aix Ceiling area, such as the actual data file FL ₁ to FL ₃ as shown in FIG. 8 (a) is recorded. Further, a data file can be further recorded in the unrecorded block EB.

The volume management area is composed of 512 management blocks as shown in FIG. The data area in one management block is 2048 bytes.
Then, the data in this management block becomes management information for recording / reproducing the actual data file.

Each management block is assigned a block number from 1 to 512. Then, the management block of the block number 1 is used as a volume descriptor VD. The management block with the block number 2 is used as a volume space bitmap VSB, and the management block with the block number 3 is used as a management table.
The usage of the management blocks of the block numbers 1 to 3 is defined as described above. The management blocks after block number 4 are used according to the usage form of the file extents area.
That is, it can be used as the management table MT, the directory record block DRB, and the extend record block ERB.

II-5-b Boot area

The boot area is used as an area indicating a program position when a computer program or the like exists.

The sector structure of the boot area is as shown in FIG. 9 or FIG.
In the boot area sector in FIG. 9, four block data of 512 bytes each can be recorded in 2048 bytes serving as a data area following a header in which a synchronization pattern and an address are described. That is, block 0 to block 3. For example, block 0 is composed of block data 0-0 to block data 0-511.

(4) Following the data area where the block data is recorded, 4-byte EDC data of EDC0 to EDC3 is recorded. Subsequently, as an ECC area, a 172-byte P parity of P-parity0 to P-parity171 and a 104-byte Q parity of Q-parity0 to Q-parity103 are recorded.

On the other hand, in the case of the type shown in FIG. 10, two block data of 1024 bytes can be recorded in 2048 bytes serving as a data area. That is, they are block 0 and block 1. For example, block 0 is composed of block data 0-0 to block data 0-123.
Others are the same as FIG.

II-5-c Volume descriptor

The first management block in the volume management area is used as a volume descriptor VD.
The volume descriptor VD performs basic management of data tracks (volumes) on the disk.

FIG. 11 shows the sector structure of the volume descriptor VD. In this sector, various management information is recorded in 2048 bytes serving as a data area, following a header in which a synchronization pattern and an address are described.

First, in the second to sixth bytes of the data area, a code "MD001" is recorded as an ID indicating a sector of the volume descriptor, for example, as an ASCII code.
Subsequently, the version ID of this system is recorded.

Next, a logical block size, a logical cluster size, and an allocation block size are recorded.
The logical block corresponds to an actual data area in a sector on the data track, and the sector on the data track has a data area of 2,048 bytes out of 2352 bytes. Therefore, “2048”, which is a byte length, is recorded as the logical block size. A logical block is the minimum data byte unit in recording / reproducing.

The logical cluster size indicates the number of logical blocks in the logical cluster. The logical cluster is a cluster in which management information and data are actually recorded. One cluster is composed of 36 sectors, of which 32 sectors (32 logical blocks) are used for data recording, and thus “32” is indicated as the logical cluster size.

と し て The number of logical blocks in the allocation block is indicated as the allocation block size. An allocation block indicates the same data unit as a logical cluster, and is a part of a data track where management information and a data file are actually recorded. For example, an area of 32 sectors as a logical cluster in the volume management area or the file extents area shown in FIG. 8B is one allocation block.

Subsequently, the total number of allocation blocks is recorded. This is the total number of allocation blocks in the volume. In the case of a hybrid disc, the number of allocation blocks in the pit area is also included.
The number of allocation blocks in the recordable area is recorded as the total number of recordable allocation blocks. For pre-mastered discs, this is zero.

In addition, the number of unrecorded allocation blocks among the recordable allocation blocks in the volume is described as the number of unrecorded allocation blocks.
Further, as the number of recorded allocation blocks, among the recordable allocation blocks in the volume, the number of allocation blocks that have already been recorded is described.
The number of allocation blocks having defects such as scratches is described as the number of defect allocation blocks.

Next, the number of directories in the volume and the number of data files in the volume are described.
Next, the maximum ID value is recorded. ID numbers are assigned to directories or data files in the order in which they are created, and this is the maximum value.

Subsequently, the volume attribute is recorded. Here, whether or not the volume management area is recorded in the mirror mode, whether or not it is an invisible file, whether or not it is write-protected, whether or not backup is necessary, and whether short location / long location is used. Is recorded.

Next, the byte length is described as the length of the volume management area.
The number of the first allocation block in the volume management area is recorded as the position of the volume management area.

Subsequently, similarly to the volume descriptor, other management blocks formed by using the management blocks in the volume management area, that is, the volume space bitmap VSB, the management table MT, the extent record block ERB, and the directory record block DRB. , The position of the first block and the number of blocks are recorded.
Subsequently, the byte length of the root directory and the number of directories in the root directory are recorded.

Further, although shown as various IDs in FIG. 11, various IDs and character set codes are recorded in the data area.
That is, a boot system ID, a volume ID and its character set code, a publisher ID and its character set code, a data prepare ID and its character set code, an application ID and its character set code are recorded.
In addition, the date and time of volume creation, the date and time of volume update, the date and time of expiration, and the date and time of validity are recorded. The 1024 to 2047 bytes in the data area are used as a system extension area.

Following the data area, a 4-byte EDC area and a 276-byte ECC area are provided. In the ECC area, a P parity of 172 bytes and a Q parity of 104 bytes are recorded.

II-5-d Volume space bitmap

The management block of the block number 2 in the volume management area is used as a volume space bitmap VSB.
This volume space bitmap VSB indicates the type of all allocation blocks in the data track.

FIG. 12 shows a sector structure of the volume space bitmap VSB. In this sector, two bits are allocated to one allocation block in 2048 bytes serving as a data area following a header in which a synchronization pattern and an address are described, and the type is indicated.
The sector of the volume space bitmap VSB is also provided with an EDC area and an ECC area following the data area.

FIG. 13A shows the contents of the data area.
The allocation block in the data track is the allocation block number from the number 0 in ascending order are assigned, bits 7 and 6 in the first byte of the data area of the volume space bitmap VSB, the allocation block AL ₀ of number 0 ... Allocation blocks AL ₁ , AL _2, ...
Thus, in the data area of the volume space bitmap VSB, it is possible to mark the information up to allocation block AL ₀ ~AL _8191, sufficient to cover all of the allocation blocks.

The 2-bit information is as shown in FIG. That is, "00" is assigned to an unrecorded allocation block, "01" is assigned to a recorded allocation block, "10" is assigned to a defective (defect) allocation block, and "11" is assigned to an undefined allocation block.
The remainder in the data area, that is, bits for which no corresponding allocation block exists, is set to “11”.

II-5-e Management table

The management block of the block number 3 in the volume management area is used as a management table MT, and the management blocks of the block number 4 and thereafter can be used as a management table.
This management table MT indicates a usage form of each management block in the volume management area.

FIG. 14 shows a sector structure of the management table MT. In this sector, 4 bytes are assigned to each management block in 2048 bytes serving as a data area following a header in which a synchronization pattern and an address are described, and each management block is managed.
In other words, the management block 0 entry to the management block 511 entry indicate the contents of use of each of the 512 management blocks in the volume management area.
Note that an EDC area and an ECC area are provided following the data area.

FIG. 15 shows 4-byte data contents in each of the management block 0 entry to the management block 511 entry.
The first management block (management block 0) is used for the volume descriptor as described above.
In this case, in the management block 0 entry, “80h” is described as the entry type in the fourth byte as shown in FIG. 15A to indicate that the management block 0 is a volume descriptor.

The second management block (management block 1) is used for the volume space bitmap as described above.
In this case, in the entry of the management block 1, “90h” is written as the entry type in the fourth byte as shown in FIG. 15B to indicate that the management block 1 is a volume descriptor. In the first and second bytes, the number of unrecorded allocation blocks is recorded.

In the entry corresponding to the management block used as the management table, as shown in FIG. 15C, the position of the next management table is recorded in the first and second bytes, and the unused management block is recorded in the third byte. The number is recorded. In order to indicate that the management block is a management table, “A0h” is described as an entry type in the fourth byte.

In the entry corresponding to the management block that is an extent record block, as shown in FIG. 15D, the position of the next extent record block is recorded in the first and second bytes, and the unused byte is recorded in the third byte. The number of extent record blocks is recorded. In order to indicate that the management block is an extent record block, "B0h" is described as an entry type in the fourth byte.

The directory record block includes a directory record written using one management block, the directory is completed, and the directory record included in one directory includes a plurality of management blocks, that is, a plurality of directory record blocks. May be recorded separately.

When a certain management block is a single directory record block, in the entry corresponding to the management block, a directory ID is recorded from 0 to 29 bits as shown in FIG. The type is “00h”.

When a certain management block is the first directory record block of a plurality of directory record blocks, the entry corresponding to the management block includes the next directory in the first and second bytes as shown in FIG. The position of the record block is recorded, and the upper byte of the directory ID is recorded in the third byte. Then, in order to indicate that the management block is the first directory record block, "D0h" is described as an entry type in the fourth byte.

When a certain management block is an intermediate directory record block of a plurality of directory record blocks (that is, not the first or last directory record block), the entry corresponding to the management block has the first, second, and third directory record blocks as shown in FIG. The position of the next directory record block is recorded in the second byte. Then, “E0h” is recorded as the entry type in the fourth byte to indicate that the management block is an intermediate directory record block.

If a certain management block is the last directory record block of a plurality of directory record blocks, the entry corresponding to the management block has the directory ID in the first, second, and third bytes as shown in FIG. Is recorded. Then, “F0h” is recorded as the entry type in the fourth byte to indicate that the management block is the last directory record block.

II-5-f Directory record block

The management blocks after block number 4 in the volume management area can be used as directory record blocks DRB.
One or a plurality of directory records are recorded in the directory record block DRB.

The directory records include a directory record for configuring a directory and a directory record for designating a position and the like corresponding to a certain data file.

FIG. 16 shows a sector structure of a directory record block DRB in which directory records for constituting a directory are recorded. In this sector, one or a plurality of directory records can be recorded in a data area of 2048 bytes following a header in which a synchronization pattern and an address are described.

First, as one unit of the directory record, the directory record length is indicated. Since the length of one unit of the directory record is variable, the directory record length indicates the byte length of the directory record.
Subsequently, the attribute of the directory is recorded. This indicates various attributes such as whether the directory record is a directory record for a directory, whether the directory including the directory record is an invisible directory, or a system directory.

Subsequently, the character set code and the short name ID are recorded. The character set code indicates the character type of the short name ID.
The short name ID is an ID recorded with 11 bytes.

Subsequently, a directory creation date and time and a directory update date and time are described, and an update date and time of this directory record is described as a status update date and time.
Further, a directory ID number and a directory length are shown.

Subsequently, as the directory position, the position of the directory record block in which the first directory record in the directory including the directory record is recorded is described.
Further, as the number of directory records, the number of directory records in the directory including the directory record is recorded.

Subsequently, the length of the long name ID is described, and the long name ID according to the length is recorded. That is, the long name ID has a variable length. In some cases, the long name ID is not recorded. In this case, the length of the long name ID is set to “00h”.
Also, only when the length of the long name ID is an even number of bytes, "00h" is recorded as padding to fill in too many bytes.
The byte following the long name ID is used as a system extension area.

One unit of the directory record corresponding to the directory is configured as described above, and a plurality of such directory records can be provided in the data area of 2048 bytes.
Note that an EDC area and an ECC area are provided following the data area.

Next, FIG. 17 shows a sector structure of a directory record block DRB in which a directory record corresponding to a certain data file is recorded.
Only when the data file is composed of one file unit, the position and the like are directly indicated by the directory record of this sector.
When the data file is composed of a plurality of files, the position of the data file is not directly indicated by the directory record, but is indicated by an later-described extent record block.

In this sector, one or a plurality of directory records respectively corresponding to the data file can be recorded in the data area of 2048 bytes following the header in which the synchronization pattern and the address are described.

As one unit of the directory record, similarly to the directory record in FIG. 16, the directory record length is indicated first, and then the attribute is recorded. This attribute indicates whether this directory record does not correspond to a directory, whether the corresponding data file is an invisible file, a system file, and whether the data file location is specified by an extent record. , Etc. are shown.

Next, similarly to the directory record of FIG. 16, a character set code, a short name ID, a directory creation date and time, a directory update date and time, and a status update date and time are described.

Next, the ID number of the data file and the data file length are shown.
Further, the position of the data file is indicated, followed by the number of allocation blocks used in the data file.
Further, an associate data length, an associate data position, and the number of allocation blocks of the associate data are described.

After that, the length of the variable long name ID is described, and the long name ID according to the length is recorded. If the long name ID is not recorded, the length of the long name ID is set to “00h”.
Also, only when the length of the long name ID is an even number of bytes, "00h" is recorded as padding to fill in too many bytes.
The byte following the long name ID is used as a system extension area.

One unit of the directory record corresponding to the data file is configured as described above, and a plurality of such directory records can be provided in the data area of 2048 bytes.
Note that an EDC area and an ECC area are provided following the data area.

II-5-g Extent record block

The management blocks of block number 4 and later in the volume management area can be used as extent record blocks ERB.
One or more extent records can be recorded in the extent record block ERB.

As an extent record, two types of data, an extent record index and an extent descriptor, can be recorded.
The extent descriptor is information for indicating the position of a file unit that actually constitutes a data file. As described above, the directory record indicates the position of the data file only when the data file is constituted by one file unit. When the data file is composed of a plurality of file units, the position of each file unit is specified by an extent descriptor.

The extent record index is information indicating the position of another extent record, and can form a tree structure of the extent record.

で は In the extent record, as a method of indicating a position in a file unit, there are a short location by a 16-bit address and a long location by a 32-bit address. Which one is adopted is shown in the volume descriptor described above.

FIG. 18 shows a sector structure of the extent record block DRB based on the short location.
In this sector, one or a plurality of extent records can be recorded in a data area of 2048 bytes following a header in which a synchronization pattern and an address are described. One extent record is composed of 32 bytes.

In this figure, an example is shown in which an extent record including an extent record index is recorded as the first 32-byte extent record of the data area.

In an extent record in which an extent record index is recorded, an index ID is recorded first. The index ID is set to “FFFFh”, indicating that the extent record includes an extent record index.

Subsequently, the maximum depth is recorded. The extent record tree structure is constructed by the extent record index, and the maximum depth indicates the subtree hierarchy specified from the extent record.
If the extent record index specifies an extent record including an extent descriptor, that is, if it is the lowest layer, the maximum depth is “0000h”.

Thereafter, up to seven extent record indexes can be recorded. That is, extent record index 0 to extent record index 7 and logical offset 0 to logical offset 7. As each of the extent record indexes 0 to 7, the index of another extent record is indicated, and correspondingly, the logical position of the extent record is indicated as a logical offset. The extent record index is data indicating which allocation table in the management block area.
The index of the extent record is indicated by the entry number and the management block number of the extent record.

In addition, an extent record index that specifies an extent record including an extent record index and an extent record index that specifies an extent record including an extent descriptor do not coexist in one extent record.

In the example of FIG. 18, an extent record including an extent descriptor is recorded as a second extent record in the data area. Up to eight extent descriptors can be recorded in one extent record. That is, extent 0 start position to extent 7 start position, and extent 0 block number to extent 7 block number.

ス タ ー ト As the extent x start position, the start position of the file unit is recorded. That is, the number of the first allocation block in the file unit is described. The number of allocation blocks constituting the file unit is recorded as the number of extents x blocks.

As described above, the extent record can record a maximum of seven extent record indexes or a maximum of eight extent descriptors.
Up to 64 such extent records can be provided in a data area of 2048 bytes.
Note that an EDC area and an ECC area are provided following the data area.

Next, FIG. 19 shows a sector structure of the extent record block DRB by the long location.
Since the actual data content is the same as that of the short location, duplicate description is avoided. However, in the short location, each data is recorded in 2 bytes, but in the long location, each data is 4 bytes. Be recorded.

Also in this case, the extent record can record a maximum of seven extent record indexes or a maximum of eight extent descriptors.
In the case of a long location, since one extent record is composed of 64 bytes, a maximum of 32 records can be provided in a data area of 2048 bytes.
Similarly, an EDC area and an ECC area are provided following the data area.

II-6 Data Sector

Next, the structure of the sector in the file extent area in which the data file is recorded will be described.

FIG. 20 shows the format of the data sector.
The leading 12 bytes of a 4 × 588 2352-byte sector are used as a synchronization pattern, and subsequently, a cluster address (Cluster H, Cluster L), a sector address (sector), and mode information are recorded and used as a header.

The next 4 bytes are provided with an address area (Logical Sector 0 to Logical Sector 3) for the application. Subsequently, information (Mode) indicating an error correction mode, category information (Category) indicating an attribute of the data file, and index information (Index) indicating a parameter of the data file are provided. Although a specific example of the index information is determined by the category information and the application (described later), when the index information is “00h”, it indicates that the data recording content (that is, the volume) is zero. . The information (Mode) indicating the error correction mode and the category information (Category) indicating the attribute of the data file will be described later.
A system ID is added as four bytes of ID0 to ID3.

Actual file data is recorded in a data area of 2048 bytes indicated as Data Byte0 to Data Byte2047.
The 276 bytes after the data area are set as additional areas (Aux 0 to Aux 275). This additional area can be used as an EDC area or an ECC area like the sector of the management block described above.
The usage of the additional area is indicated by information (Mode) indicating the error correction mode of the 21st byte of this sector.

For example, when Mode = “00h”, no area for adding data for error detection and correction is provided. That is, the additional areas (Aux 0 to Aux 275) after the 4 × 519 byte remain undefined.
In this case, with respect to the reproduction information from the disc, only error detection and correction processing by the CIRC code is performed by the decoder 28 shown in FIG. 2 in the recording / reproducing apparatus, but the CIRC code is used as is well known. It has sufficient error correction capability and does not cause any problem in error processing.

When Mode = “01h”, four bytes of parity for error detection are added as data for error detection and correction. That is, parity (ECD0 to ECD3) is added to the 4 bytes following the data area of 2048 bytes. Thus, the undefined additional area has 272 bytes indicated as (Aux4 to Aux275).
The generator polynomial for this parity P _(X) (that is, ECD0 to ECD3) is: P _(X) = (x ¹⁶ + x ¹⁵ + x ² +1) (x ¹⁶ + x ² + x + 1)
It is.
In this case, with respect to the reproduction information from the disc, the recording / reproducing apparatus can perform the error detection only with the digital signal output from the decoder 28 without using the error detection result from the decoder 28 shown in FIG.

When Mode = “02h”, data for error detection and correction is used for all the additional areas. That is, P parity (P-parity0 to P-parity171) is added to the 172 bytes following the data area of 2048 bytes, and Q parity (Q-parity0 to Q-parity103) is added to the subsequent 104 bytes. As a result, an error correction capability of up to about 80 bytes is realized.
The P parity and Q parity has the same configuration as the Reed-Solomon code Galois field employed by the so-called CD-ROM (Garoa Field) distance between the (2 ⁸⁾ (26, 24).

Next, the definition of category information (Category) provided in the 22nd byte of this sector will be described.
... When category information (Category) = "00h".
This indicates that this sector is an open sector in which no data is recorded, regardless of the state of the data area. Therefore, when it is desired to erase the contents of the sector, the category information (Category) may be rewritten to "00h".

... When category information (Category) = "01h".
Indicates that binary data is recorded in this sector. There are no restrictions on the type of data. Such a sector is used in such a manner that bytes recorded in the data area are directly passed as digital data to the application (software) side. When the category information is “01h”, the following index information indicates that a data area is secured by the value of the numerical value recorded in the byte as (Index) × 128 bytes. Become. Since the data area is 2048 bytes, the index information (Index) takes any value from "00h" to "10h".

... Category information (Category) = "10h"-"1Fh".
This indicates that document data is recorded in this sector.
In this case, similarly, the subsequent index information indicates that the data area is secured by the size of (numerical value x 128 bytes) recorded in the byte as (Index).

... Category information (Category) = "20h"-"2Fh".
This indicates that a single dot image, that is, one image file is recorded as black and white dot data in this sector. In this case, similarly, the subsequent index information indicates that the data area is secured by the size of (numerical value x 128 bytes) recorded in the byte as (Index).

... Category information (Category) = "30h" to "3Fh".
This indicates that multiple dot images, that is, a plurality of image files, are recorded as black and white dot data in this sector. In this case, similarly, the subsequent index information indicates that the data area is secured by the size of (numerical value x 128 bytes) recorded in the byte as (Index).

III. Data file playback processing

The process of reproducing a data file on the disk having the above-described disk structure by the recording / reproducing apparatus shown in FIG. 2 will be described with reference to FIGS. 2, 4 and 21.

FIG. 21 shows processing of the system controller 21 for reproducing a data file.
In order to reproduce the data file, the system controller 21 first accesses the optical disk 23 to the lead-in area of the disk 1 and reads the P-TOC (F101). Here, if the P-TOC cannot be read, it is determined that the disk is not a correct disk or that the disk has not been loaded when the reproducing operation is performed, and the process proceeds from step F102 to F103, where a disk error is detected. I do.

If the P-TOC can be read, access is made based on the U-TOC start address (UST _A ) in the P-TOC, and the U-TOC in the recording / reproduction management area is read (F104).
Here, if the U-TOC cannot be read, that is, if the U-TOC has not been recorded, it is determined that the disc is a virgin disc (F105 → F106).

When the U-TOC is read, the system controller 21 checks whether or not a data track exists as a track managed by the U-TOC. That is, it is confirmed whether or not there is a part with the bit d ₄ = “1” as the track mode information of the parts table (F107).
If not, that is, the data file is not recorded on the disc, and the data file reproduction process ends (F107 → NO).

When reproducing an audio track, the optical head 23 is made to access a required audio track from the U-TOC data at this point, and the data is read. Then, the audio signal is output as an audio signal from the output terminal 16b via the RF amplifier 27, the decoder 28, the buffer RAM 33, the audio compression decoder 38, and the D / A converter 39.

If a data track exists, the process proceeds to step F108, where a part including the smallest address among the parts constituting the data track is searched from the U-TOC and accessed. That is, the optical head 23 is made to access the part of the data track which is the innermost side on the disk.
As described above, the data U-TOC for managing the data track is located at the innermost portion of the data track on the disk.
Then, the data U-TOC is read by accessing the part (F109). That is, the management block used in the volume management area starting from the volume descriptor whose system ID is “MD001” is read.

(4) The data file can be reproduced by reading the data U-TOC. Then, in accordance with various operations for reproducing the data file, that is, in accordance with the operation of designating the data file to be reproduced (F110), the user accesses the position indicated by the directory record or the extent record, reads the data file, and loads the data into the buffer RAM 33. (F111).

Then, output is performed in a predetermined output mode according to an operation or the like (F112). For example, the data is output to the display unit 13 via the display controller 35, or output from the connector unit 15 to another device via the communication circuit 34.
If another data file has been reproduced, the process returns from step F113 to F110 again, and the process is repeated.

As described above, in the case of reproducing a data file, the U-TOC is traced from the P-TOC, and the data U-TOC is traced from the U-TOC, according to the directory structure in the data U-TOC (volume management area) described above. Reproduction processing will be performed.

IV. Recording / reproducing method using simple U-TOC (Type A)

By the way, the management of the recording / reproducing process of the data file using the data U-TOC as described above is executed according to the complicated directory structure in the data U-TOC. The above-mentioned data U-TOC makes it possible to form a hierarchical structure of a data file and perform complicated operations, thereby realizing a high-performance data recording / reproducing device. In this case, the data U-TOC is used. For example, in order to edit a file, for example, to sort a file or change a file link structure, a memory capacity and power consumption of a recording / reproducing apparatus are increased.
Therefore, when it is desired to realize a small-sized portable recording / reproducing apparatus, it is disadvantageous to use the data U-TOC as it is.

Therefore, in this embodiment, in addition to the above-described file recording / reproducing method using the data U-TOC, a recording method suitable for a small device using a simple U-TOC that performs simple data file management separately from the data U-TOC. / Reproduction method is realized.
This recording / reproducing method can of course be realized by the recording / reproducing apparatus shown in FIG. 2, and can also be adopted as a small portable recording / reproducing apparatus having substantially the same configuration. Then, in the small-sized portable recording / reproducing device, only the recording / reproducing by the simple U-TOC can be executed, so that the memory capacity and the power consumption can be reduced.
For example, in a portable still camera or the like, it is suitable for a case where photographed image data can be recorded on a disk.

As a recording / reproducing method using the simple U-TOC, two methods can be considered with respect to the recording position of the simple U-TOC, but these will be described separately as type A and type B. Type A is a type in which a simple U-TOC is recorded in a recordable user area, and type B is a type in which a simple U-TOC is recorded in a recording / reproduction management area.
First, type A will be described.

IV-1 Simple U-TOC sector (third management information)

First, the sector structure of the simple U-TOC will be described. This is common to type A and type B.
This simple U-TOC has a simple directory for data files.

The sector structure of the simplified U-TOC is shown in FIG.
In the case of this sector, a system ID is recorded from a predetermined byte position following a synchronization pattern, a cluster address (cluster H, cluster L), a sector address (sector), and a header according to a mode (mode).
As this system ID, a code “MIEX” is recorded by an ASCII code. This “MIEX” indicates that the sector is used as a simple U-TOC.

In 2048 bytes which is a data area, 64 directory units each consisting of 32 bytes can be recorded.
A 32-byte directory unit (that is, one directory) is provided corresponding to a certain data file.

The first eight bytes (Name0 to Name7) of the directory unit record the name of the data file. The following three bytes (Suffix0 to Suffix2) are allocated so that an extension is recorded.
For example, when searching for a data file recorded in the recordable user area while being managed by the simple U-TOC, the name and extension of the directory unit are used.

１In one byte following the extension, category information (Category) is allocated. The category information (Category) indicates the attribute of the data file corresponding to this directory unit, and is similar to the category information described in the data sector format described above with reference to FIG.

(4) The following two-byte volume information (Volume1-0, Volume1-1) indicates the number of allocation blocks (clusters) used by the data file indicated by this directory. That is, it indicates how many allocation blocks need to be accessed to reproduce the data file.

The following 2-byte index information (Index0, Index1) is used when a heading sector as reference information of the data file exists in the same cluster as the simple U-TOC sector, and is used as the index information (Index0). , The sector number of the heading sector is recorded, and the part number in the sector of the heading sector is recorded as index information (Index1).
If the heading sector does not exist, the index information (Index 0) is set to “00h”.

In the next byte, an erasure prevention flag (Flag) is recorded.
When the erasure prevention flag (Flag) = “00h”, the data file corresponding to the directory unit can be erased. When the erasure prevention flag (Flag) = “01h”, the directory unit corresponds. The data file cannot be deleted.

(5) In the next 5 bytes, date and time information when the data file corresponding to the directory unit was last updated is recorded. That is, information of year, month, day, hour, and minute is recorded in each byte as (Year), (Month), (Day), (Hour), and (Minutes).

Subsequently, the address of the corresponding data file is recorded. That is, two bytes of (Cluster-H) and (Cluster-L) indicate a cluster address, and one byte of (Sector) indicates a sector address.
With the above configuration, a directory unit is formed and functions as search information for each data file.

IV-2 Management when simple U-TOC is recorded

FIGS. 23, 25, and 27 show examples of the management form in the case where the simple U-TOC is recorded in the type A in which the simple U-TOC is recorded in the recordable user area.
FIG. 23, FIG. 25, and FIG. 27 show a track state and a management form when a data file to be managed by the simple U-TOC is recorded. That is, the data file is recorded on the disk by the recording device having the data file recording function by the simple U-TOC. This recording method will be described later.

Each example described here shows three types of management modes that can be executed, and records the simple U-TOC and the data files KFL ₁ and KFL ₂ managed by the simple U-TOC. Regarding the position, it is sufficient to use somewhere in the free area, and the recording position does not affect the identification of the type of management mode. The setting of the recording position for the type A and the type B described later will be collectively described later.

First, the example of FIG. 23 is an example in which an area in which a simple U-TOC and a data file managed by the simple U-TOC are recorded is managed as a defect area by both the U-TOC and the data U-TOC.

As shown in FIG. 23A, audio tracks M ₁ , M ₂ , M ₃ , data tracks, ie, data U-TOC, data files FL ₁ , FL ₂ , FL ₃ , and unrecorded block EB are A simple U-TOC and data files KFL ₁ and KFL ₂ managed by the simple U-TOC are recorded at physically separated positions.

In this case, depending on the U-TOC, audio tracks M ₁ , M ₂ , and M ₃ are managed as shown in FIG. 23B, and data U-TOC, data files FL ₁ , FL ₂ , FL ₃ , and unrecorded data are recorded. The blocks EB are collectively managed as data tracks. The free area is also managed by the U-TOC.
The area in which the simple U-TOC and the data files KFL ₁ and KFL ₂ are recorded is managed on the U-TOC as a defect area indicated by the table pointer P-DFA. That is, on the U-TOC, the areas of the simple U-TOC and the data files KFL ₁ and KFL ₂ are regarded as invalid areas for the recording / reproducing operation.

Further, depending on the data U-TOC, management of data files FL ₁ , FL ₂ , FL ₃ and unrecorded blocks EB is performed as shown in FIG.
The area where the simple U-TOC and the data files KFL ₁ and KFL ₂ are recorded is also managed as a defect area on the data U-TOC. In other words, this area is not an area as a data track managed by the data U-TOC, but the allocation blocks included in this area on the volume space bitmap are shown as defect allocation blocks.
Therefore, even on the data U-TOC, the areas of the simple U-TOC and the data files KFL ₁ and KFL ₂ are regarded as invalid areas for the recording / reproducing operation.

Then, for the simple U-TOC, the data files KFL ₁ and KFL ₂ are managed as valid data files as shown in FIG.
Therefore, the data files KFL ₁ and KFL ₂ can be reproduced only by a reproducing apparatus having a function of accessing a simple U-TOC described later.

Further, the data files KFL ₁ and KFL ₂ managed by such a simple U-TOC can be reproduced by incorporating them under the management of the data U-TOC and performing a reproduction operation using the data U-TOC. can do.

A state incorporating the data file KFL ₂ under the control of the data U-TOC from the state of FIG. 23 is shown in FIG. 24.
In this case, on the U-TOC as shown in FIG. 24 (b), the area of the data file KFL ₂ is updated to be a part of a part of the data track.
Then, in the data U-TOC, as shown in FIG. 24 (c), the one site that has been a defect area until it the portion corresponding to the data file KFL _2, will be managed as a new data file FL _4.

Although not change essentially administrative state as the simple U-TOC in FIG. 24 (d), the data file KFL ₂ shall be deleted prohibit this. That is, in the configuration of the directory unit shown in FIG. 22, erasure prevention flag of the directory unit corresponding to the data file KFL ₂ a (Flag) and "01h".

This is because to prevent the data file KFL ₂ is due to be incorporated in the management of the data U-TOC as a data file FL _4, it is erased by the recording or editing operation using a simple U-TOC .
That is, by recording / editing using a simple U-TOC, the data files KFL ₂ from being overwritten or erased, as the data file FL ₄ in the data U-TOC is no has been managed situation It is it is for results, as a means to avoid this, the data file KFL ₂ is an erasure prohibition file.
Therefore, when this is to be erased, it is erased in the operation by the data U-TOC.

In the example of FIG. 23, the area in which the simple U-TOC and the data file managed by the simple U-TOC are recorded is managed as a defect area by both the U-TOC and the data U-TOC. Alternatively, only the U-TOC may manage the defect area as a defect area, and the data U-TOC may not manage the defect area as being outside the data track.

Next, in the example of FIG. 25, the area in which the simple U-TOC and the data file managed by the simple U-TOC are recorded is defined as a defect area by the data U-TOC, and is defined as a defect area in the U-TOC. This is an example in which management is performed in a state where nothing exists.

As shown in FIG. 25 (a), the data track, i.e. a data U-TOC, data files _{FL 1, FL 2, FL 3} , unrecorded block EB respect, a simple U-TOC in successive positions, a simple Data files KFL ₁ and KFL ₂ managed by the U-TOC are recorded.

Of course, even when recorded at such a position, the management form may be the same as that in FIG. 23, but in this example, depending on the U-TOC, a simple U-TOC as shown in FIG. And data files KFL ₁ and KFL ₂ are managed as being regarded as a part of the data track. Therefore, the management of the area where the simple U-TOC and the data files KFL ₁ and KFL ₂ are recorded as the defect area as shown in FIG. 23 is not performed.

On the other hand, depending on the data U-TOC, the data files FL ₁ , FL ₂ , FL ₃ and unrecorded blocks EB are managed as shown in FIG. The area where the simple U-TOC and the data files KFL ₁ and KFL ₂ are recorded is managed as a defect area in the data track. That is, the allocation blocks included in this area are shown as defect allocation blocks on the volume space bitmap.
Therefore, on the data U-TOC, the area of the simple U-TOC and the data files KFL ₁ and KFL ₂ is regarded as an area where the recording / reproducing operation is invalid in the data track.

For the simple U-TOC, the data files KFL ₁ and KFL ₂ are managed as valid data files as shown in FIG.
Therefore, also in this case, the data files KFL ₁ and KFL ₂ can be reproduced only by a reproducing device having a function of accessing a simple U-TOC described later.

Further, the data files KFL ₁ and KFL ₂ managed by such a simple U-TOC can be reproduced by incorporating them under the management of the data U-TOC and performing a reproduction operation using the data U-TOC. can do.

A state incorporated in the state of FIG. 25 the data file KFL ₂ under the control of the data U-TOC shown in FIG. 26.
In this case, the management form on the U-TOC does not change as shown in FIG.
In the data U-TOC, as shown in FIG. 26 (c), of the sites have a defect area until it the portion corresponding to the data file KFL _2, manages as a new data file FL _4.
And it does not change basically managed state as shown in FIG. 26 in the simple U-TOC (d), as in the case of FIG. 24, the data file KFL ₂ is an erasure inhibited this.

Next, the example of FIG. 27 is an example in which an area in which a simple U-TOC and a data file managed by the simple U-TOC are recorded is managed as a defect area by the U-TOC.
FIG. 27A shows that, when no data track is recorded, a simple U-TOC is stored in a free area managed by the U-TOC and data files KFL ₁ and KFL ₂ managed by the simple U-TOC. Is recorded.

In this case, as shown in FIG. 27B, the U-TOC manages an area in which the simple U-TOC and the data files KFL ₁ and KFL ₂ are recorded as a defect area.
Since there is no data track, the data U-TOC does not exist, and therefore, the management by the data U-TOC is not performed (FIG. 27C).

In the simple U-TOC, data files KFL ₁ and KFL ₂ are managed as valid data files as shown in FIG.
Therefore, also in this case, the data files KFL ₁ and KFL ₂ can be reproduced only by a reproducing device having a function of accessing a simple U-TOC described later.

Further, the data files KFL ₁ and KFL ₂ managed by the simple U-TOC may be incorporated under the management of the data U-TOC so that the data files can be reproduced by a reproducing operation using the data U-TOC. it can.

A state incorporating the data file KFL ₂ under the control of the data U-TOC from the state of FIG. 27 is shown in FIG. 28.
In this case, since no data track exists, a data track is generated first. In other words, the simple U-TOC, and records the data U-TOC to the beginning of the area of the data file KFL _1, KFL _2, U-TOC as shown in FIG. 28 (b) of this region, as in FIG. 28 (c) It is managed as a data track above.

Furthermore, the newly recorded data U-TOC, to manage the data file KFL ₂ as a new data file FL _1, whereas, the region of the simple U-TOC and data files KFL ₁ and defect area. That is, it is managed as a defect allocation block.
On the simple U-TOC, as shown in FIG. 28 (d), the data file KFL _2, on the directory unit, the erasure prohibition this.
Thus only the data file KFL ₂ is controlled conditions as a data file FL ₁ on the data U-TOC is achieved.

In this case, only the area of the data U-TOC for data tracks KFL ₂ newly recorded as data track on the U-TOC, the region of the simple U-TOC and data files KFL _1, on U-TOC It may be a defect area.

As described above, various management forms for the area in which the simple U-TOC and the data file managed by the simple U-TOC are recorded are conceivable.

IV-3 Data File Recording Processing Using Simple U-TOC

Next, a data file recording process using a simple U-TOC that can be realized in a recording / reproducing apparatus as shown in FIG. 2 or a recording apparatus having a similar block configuration as recording means will be described. This recording process has a recording block configuration substantially the same as that of FIG. 2, but can be easily realized even in a small portable device, for example, in which various specifications such as a memory capacity are reduced.

This recording operation will be described as an operation of the recording / reproducing apparatus of FIG.
FIG. 29 shows the processing of the system controller 21 at the time of recording.
When data to be recorded is input and a recording operation is performed, an actual recording process is started (F201 → F202 → F203).
In the block of FIG. 2, data input is performed via the connector unit 15 and the communication circuit 34, or is performed by the image scanner 14. For example, in the case of a portable still camera or the like, data input is performed from photographing means. In a device such as an electronic organizer, character data is input by key operation.

First, a free area in which the input data can be recorded is searched from the U-TOC (F203). Then, the input data is recorded in the free area (F204).
Here, since a directory unit corresponding to the recorded data file must be recorded as a simple U-TOC, data for this is generated (F205). That is, if a simple U-TOC already exists on the disc on which recording has been performed, this is read and a directory unit corresponding to the data file recorded this time is generated. If the simple U-TOC does not exist, the simple U-TOC data in which the directory unit corresponding to the data file recorded this time is recorded is generated.
The discrimination of the presence / absence of the simple U-TOC on the disc and the reading process in the case where it is present are the same as the reading process in the process at the time of reproduction, which will be described later. .

When the editing / generation of the simple U-TOC data according to the data file recording is performed, the simple U-TOC data is recorded in the free area (F206).
Then, the area of the recorded simple U-TOC and data file is rewritten on the U-TOC and data U-TOC, or on the other hand, so that the U-TOC / data U-TOC is rewritten so as to be incorporated into the defect area. Perform (F207). That is, one or both of the U-TOC and the data U-TOC are rewritten so that any of the management modes of FIGS. 23, 25, and 27 described above is realized.
Thus, the recording operation of the data file corresponding to the simple U-TOC is completed.

IV-4 Reproduction of data file by simple U-TOC and transfer to data U-TOC

Next, for example, a reproduction process of a data file managed and recorded in the simple U-TOC as shown in FIGS. 23, 25 and 27, and only a simple U-TOC as shown in FIGS. 24, 26 and 28. A process of incorporating a data file managed by the data U-TOC under the management of the data U-TOC will be described.

FIG. 30 shows processing of the system controller 21 for data reproduction / transfer compatible with simple U-TOC. It should be noted that only the reproduction process among them is a process that can be easily realized even in a portable small device in which various specifications are downsized.

In order to reproduce a data file compatible with the simple U-TOC, the simple U-TOC must be read.
First, the system controller 21 reads the P-TOC by making the optical head 23 access the lead-in area of the disk 1 (F301). Here, if the P-TOC cannot be read, the process proceeds from step F302 to F303, and a disk error is determined.

If the P-TOC can be read, access is made based on the U-TOC start address (UST _A ) in the P-TOC, and the U-TOC in the recording / reproduction management area is read (F304).
If the U-TOC cannot be read, it is determined that the disk is a virgin disk (F305 → F306).

When the U-TOC is read, the system controller 21 determines whether a defect area exists in the management of the U-TOC (F307). When the area in which the simple U-TOC and the data file managed by the simple U-TOC are recorded is managed in the state of FIG. 23 or FIG. 27, the area is defined as a defect area on the U-TOC. That is, a defect area exists in the management of the U-TOC.

Then, as the subsequent processing, the parts indicated in the parts table derived from the table pointer P-DFA are sequentially accessed by the U-TOC (F308).
First, the first part is accessed and information is read from the first part to determine whether or not a disk error occurs (F309). If the part is a real defective part, a disk error should occur.
If a disk error has occurred, then the part indicated in the linked parts table is accessed from the parts table indicating the part (F309 → F312 → F308).

{Circle around (4)} When a part which is regarded as a defect area is accessed and reproduced, and no disc error occurs, it is determined whether or not a simple U-TOC exists there (F310). That is, it is determined whether or not the code data “MIEX” which is the system ID indicating the simple U-TOC has been read.

If it is determined in step F310 that "MIEX" could not be read, the part is not a defective part and a part for which no simple U-TOC is recorded. For example, there may be a case where the data file managed in the simple U-TOC is a part in which the data file is recorded, or a defective part but a disk error does not occur for some reason.
In this case, next, the part indicated in the linked parts table is accessed from the parts table indicating the part (F310 → F312 → F308).

By following the defective parts in this way, at some point, a part from which code data “MIEX” indicating a simple U-TOC can be read can be found. For example, assume that defect parts are managed on the U-TOC as shown in FIG. That is, as the parts indicated in the parts table derived from the table pointer P-DFA, the first two parts are defective parts, the parts having the simple U-TOC, and then the data files KFL managed by the simple U-TOC _If a part having ₁ is linked and managed, a simple U-TOC will be found at the time of access to the third part.
In such a case, the process proceeds from step F310 to F311 and the found simple U-TOC is read.

If a simple U-TOC is not found even after accessing and playing back a part which is regarded as a defect area and reading of the last part is completed, it is determined that the simple U-TOC does not exist on the disc. The reproduction operation of the data file managed by the simple U-TOC is not performed (F312 → F317). For example, this is a case where a defect area due to a defect exists in the disk in a state as shown in FIG.

If it is determined in step F307 that there is no defect area on the U-TOC, it is next checked whether a data track exists as a track managed by the U-TOC. That is, it is confirmed whether or not there is a part with the bit d4 = “1” as the track mode information of the parts table (F313).

For example, when the management state is as shown in FIG. 25, the area in which the simple U-TOC and the data file managed by the simple U-TOC are recorded is not regarded as a defect area on the U-TOC, but is recorded on the data U-TOC. It is a defect area.

Step F313: If it is determined that the data track does not exist, it means that the data U-TOC has not been recorded, and therefore, the simple U-TOC which is regarded as a defect area on the data U-TOC and the data file managed therefor Therefore, the data file reproduction processing by the simple U-TOC is terminated without the simple U-TOC (F313 → F317).

If there is a data track, the process proceeds to step F314, where a part including the smallest address among the parts constituting the data track is searched from the U-TOC and accessed. That is, the optical head 23 is made to access the portion of the data track which is the innermost side of the disk, and the data U-TOC is read (F315). That is, the management block used in the volume management area starting from the volume descriptor whose system ID is “MD001” is read.

When the data U-TOC is read, it is determined whether or not a defect area exists on the data U-TOC. That is, it is checked whether a defect allocation block exists on the volume space bitmap.
Here, if there is no defect allocation block, that is, there is no simple U-TOC, the data file reproduction processing by the simple U-TOC ends (F316 → F317).

If there is a defect allocation block, the process proceeds to step F308 to sequentially access the defect parts (defect allocation block) and search for a simple U-TOC in the same manner as described above (F308, F309, F310, F312). Then, when an allocation block from which code data "MIEX" can be read is found, the simple U-TOC is read in step F311.
If “MIEX” is not found even after all defect allocation blocks have been reproduced, it is determined that there is no simple U-TOC (F312 → F317).

(4) If the simple U-TOC can be read by the above processing, the data file managed by the simple U-TOC can be reproduced. Then, in accordance with various operations for reproducing the data file, that is, in response to an operation of designating a data file to be reproduced (F318), a position indicated by the directory unit is accessed, the data file is read, and the data is loaded into the buffer RAM 33 (F319). ).

Then, output is performed in a predetermined output mode according to an operation or the like (F320). For example, the data is output to the display unit 13 via the display controller 35, or output from the connector unit 15 to another device via the communication circuit 34.
When the reproduction operation of another data file managed by the simple U-TOC is performed, the process returns from step F324 to F318 again, and the process is repeated.

By the way, for example, at the stage of reproducing and outputting a certain data file, the user performs an operation of incorporating the data file under the management of the data U-TOC, or the like, thereby performing the incorporating process. That is, when the transfer operation is performed (F321), the data U-TOC is rewritten, and the corresponding data file is stored in the data U-TOC as shown in FIGS. 24 (c), 26 (c), and 28 (c). -A data file managed by TOC. Further, if the management state is as shown in FIG. 23 or FIG. 27, the U-TOC is updated so that the management as shown in FIG. 24 (b) and FIG. 28 (b) is performed in the U-TOC. Is performed (F322).
Then, the simple U-TOC is rewritten. That is, in the directory unit corresponding to the data file, the erasure prevention flag (Flag) is set to “01h” (F323).

As described above, in the case of reproducing a data file corresponding to the simple U-TOC, the U-TOC is traced from the P-TOC, the defect area of the U-TOC is searched, and the simple U-TOC is read. Alternatively, the simple U-TOC is read by following the data U-TOC from the U-TOC, searching for a defect area on the data U-TOC. Then, the reproduction process is performed according to the directory unit in the simple U-TOC.

When the recording / reproducing is performed by the simple U-TOC as described above, there is no need to read / edit the data U-TOC, so that a large memory capacity is not required for the recording / reproducing / editing operation of the data file. Power consumption can be reduced. Therefore, it is a very suitable recording / reproducing method for a small device or the like.

In addition, a data file managed by the simple U-TOC can be incorporated under the management of the data U-TOC, so that normal data file playback using the data U-TOC can be performed to support the simple U-TOC. The data file can be played. Therefore, it is possible to reproduce even a device that does not have a reproducing function by the simple U-TOC.

Also, by incorporating a data file corresponding to the simple U-TOC under the management of the data U-TOC, the data file becomes a target of an advanced editing operation in the data U-TOC and can be effectively used in various ways.
For example, what was shot with a portable still camera having a recording function by the simple U-TOC and recorded as a data file on a disc was reproduced on a full-spec recording / reproducing device, and a necessary data file was selected. A use form in which the data is incorporated under the management of the data U-TOC and various advanced edits are performed is also possible.

IV-5 Copy Guard Data Recording Using Simple U-TOC

By the way, as described above, since the simple U-TOC is managed as a defect area by the U-TOC and / or the data U-TOC, it is used as a hidden protection area for preventing illegal copying, Copy guard can be performed.

In the mini-disc data system of this embodiment, a copy protection flag can be set as the track mode information of the parts table in the U-TOC, and the copy protection flag is also set as the attribute data of the file or directory in the data U-TOC. Can stand.
However, it is relatively easy to modify the recording / reproducing apparatus so that these flags can be ignored. Therefore, this is not an absolute copy guard means.

Therefore, here, a method for realizing more reliable copy guard using the simple U-TOC will be described.
In this embodiment, the simple U-TOC is used. However, instead of the simple U-TOC, a sector dedicated to copy guard is provided, and this is managed as a defect area similarly to the simple U-TOC. Is also possible.

In the copy guard method, first, a keyword for copy guard is recorded in the simple U-TOC.
This recording process is shown in FIG.

First, a keyword is set (F401). This means that the recording apparatus generates the keyword data set in the recording program for copy guard, for example.

Then, this keyword is recorded using one directory unit of the simple U-TOC shown in FIG.
For example, a keyword is recorded using 8 bytes (Name0 to Name7) of the name of the data file in the directory unit and 3 bytes of the extension (Suffix0 to Suffix2).
Then, using the category information (Category) and the volume information (Volume1-0, Volume1-1), the directory unit is a directory corresponding to a data file of length "0", that is, a directory unit in which a keyword is recorded. As shown.

When such directory unit data is generated (F402), a free area is searched from the U-TOC (F403), and the free area is written as a simple U-TOC (F404).
Then, similarly to the case of recording the data file corresponding to the simple U-TOC, one or both of the U-TOC and the data U-TOC are updated so that the recorded simple U-TOC is set as a defect area. (F405).

As described above, a keyword is recorded in the simple U-TOC, and the reproducing apparatus performs processing according to the keyword, thereby performing copy guard.
When data is copied from a normal disk, a defect area on the U-TOC and the data U-TOC is ignored during reproduction of the original disk.
Therefore, no keyword is recorded on the copied disc.

In addition, it is not impossible to copy the defect area. However, if the keyword is set to the one that performs the operation with the information unique to the original disc, the keyword can be copied. Also in this case, copy guard can be performed.

For example, a copy guard system is set so that an accurate keyword value can be obtained by calculating a cluster address at a position where a keyword is recorded and a keyword value.
Then, even if even the keyword is copied, it is almost impossible to record the keyword at the cluster address having exactly the same value on the copy destination disk, so that an accurate keyword cannot be obtained from the disk. become.

IV-6 Playback processing corresponding to copy guard

In the case where the keyword is recorded in the simple U-TOC on the regular disc as described above, a reproduction process for realizing the copy guard will be described.
FIG. 33 shows the processing performed during reproduction. This is shown as processing after a disc is loaded and P-TOC and U-TOC are read.

(4) When an operation such as a reproduction operation is performed on the loaded disk 1, the system controller 21 determines whether a defect area exists in the management of the U-TOC (F501). Assuming that the disc is an appropriate disc and the keyword is to be recorded in the simple U-TOC, the simple U-TOC exists in an area which is regarded as a defect area in either the U-TOC or the data U-TOC.

If a defect area exists in the management of the U-TOC, the parts indicated in the parts table derived from the table pointer P-DFA are sequentially accessed by the U-TOC, and the simple U-TOC is searched ( F503, F504, F505, F507). That is, the same processing as steps F308, F309, F310, and F312 in FIG. 30 described above is performed. Then, when the code data “MIEX” is read, the simple U-TOC is found, and the simple U-TOC is read (F506).

If it is determined that no defect area exists on the U-TOC, the process advances from step F502 to F508 to check whether a data track exists as a track managed by the U-TOC.
If the data track exists, the data U-TOC at the physical head position is accessed and fetched (F509, F510), and the existence of a defect area on the data U-TOC is confirmed (F511). If there is a defect area, the simple U-TOC is searched by following the defect area, that is, the defect allocation block (F503, F504, F505, F507).
Then, when the code data “MIEX” is read, the simple U-TOC is found, and the simple U-TOC is read (F506).

When the simple U-TOC is read, a directory unit in which the keyword is recorded is searched in the simple U-TOC, and it is confirmed whether a correct keyword exists (F512). That is, the directory unit in which the keyword is recorded is confirmed from the category information (Category) and the volume information (Volume1-0, Volume1-1), and is assigned to the data file (Name0 to Name7) and the extension (Suffix0 to Suffix2) bytes. Check which keywords are used.
If the keyword is correct, it is determined that the disc is a regular disc (F513), and a program corresponding to the reproducing operation is executed (F514).

On the other hand, in other cases, the disc is determined to be an illegally copied disc.
That is, when no defect area exists in either the U-TOC or the data U-TOC, a defect area exists in either the U-TOC or the data U-TOC, but the simple U-TOC is included in the defect area. If it is not included, since there is no simple U-TOC to be recorded, it is determined that the disc is an illegal copy disc (F508 → F515), (F507 → F515), (F511 → F515).

Also, a case where a simple U-TOC is present but no keyword is recorded, a case where the keyword is incorrect, or a system which obtains a specific value by, for example, calculating a cluster address and a keyword as described above. If the calculation result is not a correct value, the disc is determined to be an illegal copy disc (F512 → F515).

When it is determined that the disc is an illegal copy disc, the system controller 21 ignores the reproduction operation and the like, and does not perform any operation (F516). As a result, the illegally copied disk becomes an invalid disk that is not a playback target for the recording / reproducing device, and a reliable copy guard is realized.

V. Recording / reproducing method using simple U-TOC (Type B)

Next, as a recording / reproducing method using the simple U-TOC, type B in which the simple U-TOC is recorded in the recording / reproducing management area will be described.
Note that the sector structure of the simple U-TOC is the same as that of FIG.

V-1 Management form when simple U-TOC is recorded

FIGS. 34, 36, and 38 show management examples of the type B in which the simple U-TOC is recorded in the recording / reproduction management area when the simple U-TOC is recorded.
FIG. 34, FIG. 36, and FIG. 38 show a track state and a management form when a data file to be managed by the simple U-TOC is recorded. That is, the data file is recorded on the disk by the recording device having the data file recording function by the simple U-TOC. This recording method will be described later.

Note that each example described here shows three types of management modes that can be executed in the same manner as described in the type A, and the data files KFL ₁ and KFL managed by the simple U-TOC. Regarding the recording position of ₂ , it is only necessary to use somewhere in the free area, and the recording position does not affect the identification of the type of the management form. The setting of the recording position will be described later.

First, the example of FIG. 34 is an example in which an area in which a data file managed by the simple U-TOC is recorded is managed as a defect area by both the U-TOC and the data U-TOC.

As shown in FIG. 34A, audio tracks M ₁ , M ₂ , M ₃ , data tracks, that is, data U-TOC, data files FL ₁ , FL ₂ , FL ₃ , and unrecorded blocks EB are Data files KFL ₁ and KFL ₂ managed by the simple U-TOC are recorded at physically separated positions.
The simple U-TOC is recorded at a position having a predetermined offset from the U-TOC position in the recording / reproduction management area.

In this case, depending on the U-TOC, audio tracks M ₁ , M ₂ , and M ₃ are managed as shown in FIG. 34B, and data U-TOC, data files FL ₁ , FL ₂ , FL ₃ , and unrecorded data are recorded. The blocks EB are collectively managed as data tracks. The free area is also managed by the U-TOC.
The area in which the data files KFL ₁ and KFL ₂ are recorded is managed as a defect area indicated by the table pointer P-DFA on the U-TOC. That is, on the U-TOC, the areas of the simple U-TOC and the data files KFL ₁ and KFL ₂ are regarded as invalid areas for the recording / reproducing operation.

Further, depending on the data U-TOC, management of data files FL ₁ , FL ₂ , FL ₃ and unrecorded blocks EB is performed as shown in FIG.
The area where the data files KFL ₁ and KFL ₂ are recorded is also managed as a defect area on the data U-TOC. In other words, this area is not an area as a data track managed by the data U-TOC, but the allocation blocks included in this area on the volume space bitmap are shown as defect allocation blocks.
Therefore, even on the data U-TOC, the areas of the data files KFL ₁ and KFL ₂ are regarded as invalid areas for the recording / reproducing operation.

For the simple U-TOC, the data files KFL ₁ and KFL ₂ are managed as valid data files as shown in FIG.
Therefore, the data files KFL ₁ and KFL ₂ can be reproduced only by a reproducing device having a function of accessing the simple U-TOC as described later.

Similarly to the case of the type A, the data files KFL ₁ and KFL ₂ managed by the simple U-TOC are incorporated under the management of the data U-TOC, and are reproduced by the reproduction operation using the data U-TOC. May also be reproducible.

A state incorporating the data file KFL ₂ under the control of the data U-TOC from the state of FIG. 34 is shown in FIG. 35.
In this case, as the management on U-TOC as shown in FIG. 35 (b), to incorporate the area of the data file KFL ₂ as one part of the data track, and updates the U-TOC.
Also the data U-TOC, as shown in FIG. 35 (c), of the sites have a defect area until it the portion corresponding to the data file KFL _2, will be managed as a new data file FL _4.

Although not change essentially administrative state as the simple U-TOC in FIG. 35 (d), the data file KFL ₂ is erasure preventing flag of the directory unit corresponding to the data file KFL ₂ a (Flag) "01h" Is prohibited. This data file FL ₄ in the data U-TOC is prevented from is erased by such editing operations on data file KFL ₂ on the simple U-TOC.
When the data file KFL ₂ (= FL ₄ ) is to be erased, it is erased in the operation by the data U-TOC.

In the example of FIG. 34, the area in which the data file managed by the simple U-TOC is recorded is managed as a defect area by both the U-TOC and the data U-TOC. Only the TOC may be managed as a defect area, and the data U-TOC may not be managed as being outside the data track.

Next, in the example of FIG. 36, the area in which the data file managed by the simple U-TOC is recorded is set as a defect area by the data U-TOC, and is managed in a state where the area is not set as the defect area by the U-TOC. This is an example.

As shown in FIG. 36 (a) management, data track, i.e. a data U-TOC, data files _{FL 1, FL 2, FL 3} , unrecorded block EB respect, the successive positions, by the simple U-TOC Recorded data files KFL ₁ and KFL ₂ are recorded.
The simple U-TOC is recorded at a position having a predetermined offset from the U-TOC position in the recording / reproduction management area.

Needless to say, even when the data is recorded at such a position, the management form may be the same as that shown in FIG. 34. However, in this example, depending on the U-TOC, the data file KFL ₁ as shown in FIG. And KFL ₂ are managed as a part of the data track. Therefore, as shown in FIG. 34, the area where the data files KFL ₁ and KFL ₂ are recorded is not managed as a defect area.

On the other hand, depending on the data U-TOC, management of data files FL ₁ , FL ₂ , FL ₃ and unrecorded blocks EB is performed as shown in FIG. The area where the data files KFL ₁ and KFL ₂ are recorded is managed as a defect area in the data track. That is, the allocation blocks included in this area are shown as defect allocation blocks on the volume space bitmap.
Therefore, on the data U-TOC, the area of the simple U-TOC and the data files KFL ₁ and KFL ₂ is regarded as an area where the recording / reproducing operation is invalid in the data track.

Then, for the simple U-TOC, the data files KFL ₁ and KFL ₂ are managed as valid data files as shown in FIG.
Therefore, also in this case, the data files KFL ₁ and KFL ₂ can be reproduced only by a reproducing device having a function of accessing a simple U-TOC described later.

The data file KFL ₂ that is managed only in the simple U-TOC in FIG. 36 shows a state incorporated under the control of the data U-TOC in FIG. 37.
In this case, the management form on the U-TOC does not change as shown in FIG.
In the data U-TOC, as shown in FIG. 37 (c), of the sites have a defect area until it the portion corresponding to the data file KFL _2, manages as a new data file FL _4.
And it does not change basically managed state as shown in FIG. 37 in the simple U-TOC (d), as in the case of FIG. 35, the data file KFL ₂ is an erasure inhibited this.

Next, the example of FIG. 38 is an example in which an area in which a data file managed by the simple U-TOC is recorded is managed as a defect area by the U-TOC.

FIG. 38A shows a case where data files KFL ₁ and KFL ₂ managed by the simple U-TOC are recorded in a free area managed by the U-TOC when no data track is recorded. Is shown.
The simple U-TOC is recorded at a position having a predetermined offset from the U-TOC position in the recording / reproduction management area.

In this case, the U-TOC manages the area where the data files KFL ₁ and KFL ₂ are recorded as a defect area as shown in FIG.
Since there is no data track, there is naturally no data U-TOC, and therefore management by the data U-TOC is not performed (FIG. 38 (c)).

In the simple U-TOC, data files KFL ₁ and KFL ₂ are managed as valid data files as shown in FIG.
Therefore, also in this case, the data files KFL ₁ and KFL ₂ can be reproduced only by a reproducing device having a function of accessing a simple U-TOC described later.

Also, it is shown in FIG. 39 the state state incorporating the data file KFL ₂ under the control of the data U-TOC from Figure 38.
In this case, since no data track exists, a data track is generated first.
That is, the data U-TOC is recorded at the head position of the area of the data files KFL ₁ and KFL ₂ as shown in FIG. 39C, and this area is used as a data track on the U-TOC as shown in FIG. to manage.

Furthermore, the newly recorded data U-TOC, to manage the data file KFL ₂ as a new data file FL _1, whereas, the area of the data file KFL ₁ and defect area. That is, it is managed as a defect allocation block.
On the simple U-TOC, as shown in FIG. 39 (d), the data file KFL _2, on the directory unit, the erasure prohibition this.
Thus only the data file KFL ₂ is controlled conditions as a data file FL ₁ on the data U-TOC is achieved.

In this case, only the area of the data U-TOC for data tracks KFL ₂ newly recorded as data track on the U-TOC, the area of the data file KFL _1, so as to defect area on U-TOC It may be.

As described above, various management forms for the area in which the simple U-TOC and the data file managed by the simple U-TOC are recorded are conceivable.

V-2 Data File Recording Processing Using Simple U-TOC

Next, a data file recording process using a simple U-TOC that can be realized in a recording / reproducing apparatus as shown in FIG. 2 or a recording apparatus having a similar block configuration as recording means will be described. As in the case of type A, this recording process has a recording block configuration substantially similar to that of FIG. 2, but can be easily realized even in a small portable device in which various specifications such as a memory capacity are reduced. .

This recording operation will be described as an operation of the recording / reproducing apparatus of FIG.
FIG. 40 shows the processing of the system controller 21 during recording.
When data to be recorded is input through the connector unit 15 and the communication circuit 34 or by the image scanner 14 and a recording operation is performed, an actual recording process is started (F601 → F602 → F603).

First, a free area in which the input data can be recorded is searched from the U-TOC (F603). Then, the input data is recorded in the free area (F604).
Here, since a directory unit corresponding to the recorded data file must be recorded as a simple U-TOC, data for this is generated (F605). That is, if a simple U-TOC already exists on the disc on which recording has been performed, this is read and a directory unit corresponding to the data file recorded this time is generated. If the simple U-TOC does not exist, the simple U-TOC data in which the directory unit corresponding to the data file recorded this time is recorded is generated.
The discrimination of the presence / absence of the simple U-TOC on the disc and the reading process in the case where it is present are the same as the reading process in the process at the time of reproduction, which will be described later. .

When the editing / generation of the simple U-TOC data according to the data file recording is performed, the simple U-TOC data is recorded in the recording / reproduction management area (F606). The recording position in the recording / reproduction management area is a position having a predetermined offset from the U-TOC. For example to obtain a cluster address as a value obtained by adding a specific offset value for U-TOC start address UST _A, which is the start address of the simple U-TOC.

Then, the U-TOC / data U-TOC is rewritten so that the recorded data file area is incorporated into the defect area on the U-TOC and / or the data U-TOC (F607). ). That is, one or both of the U-TOC and the data U-TOC are rewritten so that any of the management modes of FIGS. 34, 36, and 38 described above is realized.
Thus, the recording operation of the data file corresponding to the simple U-TOC is completed.

V-3 Reproduction processing of data file by simple U-TOC and transfer processing to data U-TOC

Next, for example, as shown in FIGS. 34, 36, and 38, a reproduction process of a data file managed and recorded in the simple U-TOC, and only a simple U-TOC as shown in FIGS. A process of incorporating a data file managed by the data U-TOC under the management of the data U-TOC will be described.

FIG. 41 shows processing of the system controller 21 for data reproduction / transfer compatible with simple U-TOC. It should be noted that only the reproduction process among them is a process that can be easily realized even in a portable small device in which various specifications are downsized.

In order to reproduce a data file compatible with the simple U-TOC, the simple U-TOC must be read.
First, the system controller 21 reads the P-TOC by making the optical head 23 access the lead-in area of the disk 1 (F701). Here, if the P-TOC cannot be read, the process proceeds from step F702 to F703, and a disk error is determined.

If the P-TOC can be read, access is made based on the U-TOC start address (UST _A ) in the P-TOC, and the U-TOC in the recording / reproduction management area is read (F704).
If the U-TOC cannot be read, it is determined that the disk is a virgin disk (F705 → F706).

When the U-TOC is read, the system controller 21 causes the optical head 23 to access a position having a predetermined offset from the U-TOC position (F707), and reads data from that position. This is a simple U-TOC access operation.
Here, if the data cannot be read, it means that the simple U-TOC does not exist. Therefore, the data file reproduction processing by the simple U-TOC is completed without the simple U-TOC (F708 → F710).

When data is read from a position having a predetermined offset from the U-TOC, it is determined whether or not the data is a simple U-TOC (F709). That is, it is determined whether or not the code data “MIEX” which is the system ID indicating the simple U-TOC has been read.

If it is determined in step F709 that "MIEX" could not be read, it is determined that the disc does not have a simple U-TOC, and the data file reproduction processing by the simple U-TOC ends (F709 → F710). .
If code data "MIEX" exists as data read from a position having a predetermined offset from the U-TOC, the process proceeds from step F709 to F711, and the simple U-TOC is read.

(4) If the simple U-TOC can be read, the data file managed by the simple U-TOC can be reproduced. Then, in accordance with various operations for reproducing the data file, that is, in response to an operation of designating a data file to be reproduced (F712), a position indicated by the directory unit is accessed, the data file is read, and the data is loaded into the buffer RAM 33 (F713). ).

Then, output is performed in a predetermined output mode according to an operation or the like (F714). For example, the data is output to the display unit 13 via the display controller 35, or output from the connector unit 15 to another device via the communication circuit 34.
When a reproduction operation of another data file managed by the simple U-TOC is performed, the process returns from step F718 to F712 again, and the process is repeated.

By the way, for example, at the stage of reproducing and outputting a certain data file, the user performs an operation of incorporating the data file under the management of the data U-TOC, or the like, thereby performing the incorporating process. That is, when the transfer operation is performed (F715), the data U-TOC is rewritten, and the corresponding data file is written to the data U-TOC as shown in FIGS. 35 (c), 37 (c) and 39 (c). -A data file managed by TOC. If the management state is as shown in FIGS. 34 and 38, the U-TOC is also changed so that the management of the U-TOC is as shown in FIGS. 35 (b) and 37 (b). Update (F716).
Then, the simple U-TOC is rewritten. That is, in the directory unit corresponding to the data file, the erasure prevention flag (Flag) is set to “01h” (F717).

As described above, in the case of data file reproduction corresponding to the simple U-TOC is recorded simple U-TOC by adding a predetermined offset value to the U-TOC start address UST _A shown in P-TOC An address that should be present is obtained, and a simple U-TOC is read from that position. Then, the reproduction process is performed according to the directory unit in the simple U-TOC.

When recording / reproducing is performed by the simple U-TOC as described above, there is no need to read / edit the data U-TOC, as in the case of type A described above. Sometimes a large memory capacity is not required and power consumption can be reduced. Therefore, it is a very suitable recording / reproducing method for a small device or the like.

In addition, a data file managed by the simple U-TOC can be incorporated under the management of the data U-TOC, so that normal data file playback using the data U-TOC can be performed to support the simple U-TOC. The data file can be played. Therefore, it is possible to reproduce even a device that does not have a reproducing function by the simple U-TOC.

Also, by incorporating a data file corresponding to the simple U-TOC under the management of the data U-TOC, the data file becomes a target of an advanced editing operation in the data U-TOC and can be effectively used in various ways.
For example, what was shot with a portable still camera having a recording function by the simple U-TOC and recorded as a data file on a disc was reproduced on a full-spec recording / reproducing device, and a necessary data file was selected. A use form in which the data is incorporated under the management of the data U-TOC and various advanced edits are performed is also possible.

V-4 Copy Guard Data Recording Using Simple U-TOC

By the way, even in this type B, since the simple U-TOC is not managed by the U-TOC and / or the data U-TOC, it can be used as a hidden protection area for preventing illegal copying and performing copy guard. it can.
In this embodiment, the simple U-TOC is used. However, instead of the simple U-TOC, an area dedicated to copy guard is provided in the recording / reproduction management area, and the keyword is recorded there. Good.

Also in this case, first, a keyword for copy guard is recorded in the simple U-TOC.
FIG. 42 shows this recording process.
First, the recording apparatus generates keyword data set in a recording program for copy guard (F801).

Then, this keyword is recorded using one directory unit of the simple U-TOC shown in FIG. That is, similar to the case described in the type A, the keyword is recorded using 8 bytes (Name0 to Name7) of the name of the data file in the directory unit and 3 bytes of the extension (Suffix0 to Suffix2).
Further, using the category information (Category) and the volume information (Volume1-0, Volume1-1), the directory unit is a directory corresponding to a data file of length "0", that is, a directory unit in which a keyword is recorded. To show that

Such After generating a directory unit data (F 802), by adding the start address UST _A predetermined to offset the U-TOC, obtaining a cluster address to be recorded simple U-TOC in the recording reproduction management area. Then, the data is written to the cluster address as a simple U-TOC (F803).

As described above, a keyword is recorded in the simple U-TOC, and the reproducing apparatus performs processing according to the keyword, thereby performing copy guard.
Normally, when data is reproduced from a certain disc and copied to another disc, the simple U-TOC is ignored on the disc on the reproducing side.
Also, by performing reproduction using the simple U-TOC as described above, it is possible to reproduce and copy a data file corresponding to the simple U-TOC, but the simple U-TOC itself is not reproduced and output. Therefore, it is not copied.
Therefore, no keyword is recorded on the disk on which the data is copied.

V-5 Playback processing corresponding to copy guard

As described above, a description will be given of a reproduction process for realizing copy guard when a keyword is recorded in the simple U-TOC on a regular disc.
FIG. 43 shows a process performed during reproduction. This is shown as processing after a disc is loaded and P-TOC and U-TOC are read.

When an operation such as a reproducing operation is performed on the loaded disk 1, the system controller 21 accesses an address position obtained by adding a predetermined offset to the U-TOC start address UST _A recorded in the P-TOC (F902). ), It is determined whether data exists at that position and whether the data is a simple U-TOC (F903, F904).
Then, when the code data “MIEX” is read and it is determined that the simple U-TOC exists, the simple U-TOC is read (F905).

After the simple U-TOC is read, a directory unit in which the keyword is recorded is searched for, and it is confirmed whether or not the keyword exists (F906). That is, the directory unit in which the keyword is recorded is confirmed from the category information (Category) and the volume information (Volume1-0, Volume1-1), and is assigned to the data file (Name0 to Name7) and the extension (Suffix0 to Suffix2) bytes. Check which keywords are used.
If it is a correct keyword, it is determined that the disc is a regular disc (F907), and a program corresponding to a reproduction operation or the like is executed (F908).

On the other hand, when the simple U-TOC does not exist, or when the simple U-TOC exists but the keyword is not written or the keyword is incorrect, the disc is determined to be an illegally copied disc. (F903 → F909), (F904 → F909), (F906 → F909).

When it is determined that the disc is an illegal copy disc, the system controller 21 ignores the reproduction operation or the like altogether and does not perform any operation (F910). As a result, the illegally copied disk becomes an invalid disk that is not a playback target for the recording / reproducing device, and a reliable copy guard is realized.

VI. Recording position of data file managed by simple U-TOC

As described above, the recording / reproducing method using the simple U-TOC is realized as type A or type B. In the case of type A, the data files corresponding to the simple U-TOC and the simple U-TOC are free. In the case of type B, data files corresponding to the simple U-TOC are recorded in the free area.

In either case, the data file (the data file and the simple U-TOC in the case of type A) may be recorded at any position in the free area. Recording is performed at a position on the outer peripheral side of the disk.
Hereinafter, the recording position will be described. In the description, the recording position of the data file corresponding to the simple U-TOC will be described by taking the type B as an example, but the same applies to the type A. That is, the same applies to the recording position of the simple U-TOC in type A.

Figure 44 (a), the data file KFL ₁ corresponding to the simple U-TOC, shows a case of recording a relatively disc inner edge side of the free area.
At this time, the data track is located from the data file KFL ₁ on the outer peripheral side, thus the data U-TOC has been a backward address from the data file KFL _1.

Here, as described above, operation of incorporated data file KFL ₁ corresponding to the simple U-TOC under the control of the data U-TOC is to have been made.
In this case, the incorporation operation, an area in which data file KFL ₁ is recorded, may be updated data U-TOC to manage as new data file FL ₃ in the data U-TOC. Further, on the U-TOC remove the area of the data file KFL ₁ from the defect area, so that the incorporated as part of the data track.

However, is located on the inner circumferential side than the data U-TOC position is far of this new data file FL _3.
Among the data U-TOC's parts constituting the data tracks, since it is recorded at the head position of the most inner circumference side part is defined, constitute a data track data file KFL ₁ as a data file FL ₃ Once incorporated into the part that, data U-TOC immediately prior to the parts that made this data file FL ₃ is that it must be recorded.

Therefore, as the processing at the time of incorporation, not only updates for incorporation in the data U-TOC, just before the parts to be data file FL ₃ as shown in FIG. 44 (b) the updated data U-TOC Then, as shown in FIG. 44 (c), it is necessary to incorporate the data U-TOC area into the free area.
That is, a number of processes such as updating the contents of the data U-TOC, recording the data U-TOC at a new position, and updating the data track, defect area, and free area in the U-TOC are required.

On the other hand, FIG. 45 (a), the data file KFL ₁ corresponding to the simple U-TOC is shows a case of recording the position where the disc outer peripheral side of the free area. At this time, the data track is located on the inner circumferential side than the data file KFL _1, so that the data U-TOC is that it the front of the address from the data file KFL _1.

Here, the operation of incorporated data file KFL ₁ corresponding to the simple U-TOC under the control of the data U-TOC is performed.
In this case, as the transfer operation, as shown in FIG. 45B, the data U-TOC is updated so that the area where the data file KFL is recorded is managed as a new data file FL in the data U-TOC. Just fine. Further, on the U-TOC remove the area of the data file KFL ₁ from the defect area, so that the incorporated as part of the data track.

That is, in this case, there is no need to change the position of the data U-TOC, and only the content that needs to be updated at the position of the data U-TOC needs to be rewritten.
Also, there is no need to update the free area on the U-TOC. Therefore, the transfer is completed by a relatively simple process.

As can be seen from the examples of FIGS. 44 and 45, it is assumed that the data file corresponding to the simple U-TOC can be recorded at a position on the outer peripheral side of the disk as much as possible in consideration of the transfer process to the data U-TOC. convenient.
In addition to this, after the transfer to the data U-TOC, it is preferable that the position of the transferred data file and the position of the data U-TOC are physically close. This will increase the access speed during reproduction. In particular, in the case of the CLV system, the rotation speed of the spindle motor differs depending on the position on the disk. However, when accessing a long distance, it takes time to establish and control the rotation speed of the spindle motor. However, the closer the positions of the data file and the data U-TOC are, the better.

Therefore, in this embodiment, the recording position of the data file corresponding to the simple U-TOC is set under the following conditions 1, 2, and 3.

1 When there is no data track (data U-TOC) A necessary area length is searched for and recorded in a portion of the existing free area closest to the outer peripheral side of the disk. In this way, when a data track is subsequently formed, the data U-TOC, which is the head position, is located on the disk inner circumference side of the data file corresponding to the simple U-TOC. Further, by recording the data track at the outermost peripheral position, the degree of freedom in recording the data track thereafter can be maximized.

2 When a data track (data U-TOC) exists: A necessary area length is searched for and recorded at a position on the outer peripheral side of the data track and close to the data track in the existing free area. This allows the data file corresponding to the simple U-TOC to be located on the outer peripheral side of the disk with respect to the data U-TOC and, if possible, to be recorded at a continuous position after the data track. To be advantageous.

3 When there is no free area that satisfies the above conditions In this case, the recording should be performed at a position as close to the outer peripheral side as possible among the existing free areas. In this case, the data file corresponding to the simple U-TOC may be on the inner side of the data U-TOC as shown in FIG. 44, but this is unavoidable.

When recording a data file using the simple U-TOC, by selecting the recording position as described above, the most convenient state for recording / reproducing a normal data file using the data U-TOC can be obtained. it can.

Although the embodiments of the present invention have been described above, it is needless to say that the present invention can be variously modified in addition to those shown in the embodiments.

FIG. 1 is an explanatory diagram of the appearance of a recording / reproducing device and a disk according to an embodiment of the present invention. FIG. 2 is a block diagram of the recording / reproducing device of the embodiment. FIG. 3 is an explanatory diagram of a cluster structure of a disk according to the embodiment. FIG. 4 is an explanatory diagram of a management state of a disk on which U-TOC and data U-TOC of the embodiment are recorded. FIG. 4 is an explanatory diagram of a P-TOC sector of the disk of the embodiment. FIG. 4 is an explanatory diagram of a U-TOC sector of the disk of the embodiment. FIG. 4 is an explanatory diagram of a link form of a U-TOC sector of the disk of the embodiment. FIG. 3 is an explanatory diagram of a data track of the disk of the embodiment. FIG. 4 is an explanatory diagram of a boot area in data U-TOC of the disk of the embodiment. FIG. 4 is an explanatory diagram of a boot area in data U-TOC of the disk of the embodiment. FIG. 4 is an explanatory diagram of a volume descriptor in data U-TOC of the disk of the embodiment. FIG. 4 is an explanatory diagram of a volume space bitmap in data U-TOC of the disk of the embodiment. FIG. 8 is an explanatory diagram of data recorded in a volume space bitmap in data U-TOC of the disk of the embodiment. FIG. 4 is an explanatory diagram of a management table in data U-TOC of the disk of the embodiment. FIG. 7 is an explanatory diagram of data recorded in a management table in data U-TOC of the disk of the embodiment. FIG. 8 is an explanatory diagram of a directory record block in the data U-TOC of the disk of the embodiment. FIG. 8 is an explanatory diagram of a directory record block in the data U-TOC of the disk of the embodiment. FIG. 4 is an explanatory diagram of an extent record block in the data U-TOC of the disk of the embodiment. FIG. 4 is an explanatory diagram of an extent record block in the data U-TOC of the disk of the embodiment. FIG. 3 is an explanatory diagram of a data sector of the disk of the embodiment. 9 is a flowchart of data reproduction processing corresponding to data U-TOC of the embodiment. FIG. 3 is an explanatory diagram of a simple U-TOC sector of the disk of the embodiment. FIG. 4 is an explanatory diagram of a track management state of a disc on which a simple U-TOC of the embodiment is recorded. FIG. 9 is an explanatory diagram of a track management state after a data file corresponding to the simple U-TOC of the embodiment is incorporated into the data U-TOC. FIG. 4 is an explanatory diagram of a track management state of a disc on which a simple U-TOC of the embodiment is recorded. FIG. 9 is an explanatory diagram of a track management state after a data file corresponding to the simple U-TOC of the embodiment is incorporated into the data U-TOC. FIG. 4 is an explanatory diagram of a track management state of a disc on which a simple U-TOC of the embodiment is recorded. FIG. 9 is an explanatory diagram of a track management state after a data file corresponding to the simple U-TOC of the embodiment is incorporated into the data U-TOC. 6 is a flowchart of a recording process for simple U-TOC according to the embodiment. It is a flowchart of reproduction | regeneration / transfer processing corresponding to simple U-TOC of an Example. It is explanatory drawing of the simple U-TOC search operation of an Example. 9 is a flowchart of copy guard data recording processing according to the embodiment. 9 is a flowchart of a reproduction process for copy guard according to the embodiment. FIG. 4 is an explanatory diagram of a track management state of a disc on which a simple U-TOC of the embodiment is recorded. FIG. 9 is an explanatory diagram of a track management state after a data file corresponding to the simple U-TOC of the embodiment is incorporated into the data U-TOC. FIG. 4 is an explanatory diagram of a track management state of a disc on which a simple U-TOC of the embodiment is recorded. FIG. 9 is an explanatory diagram of a track management state after a data file corresponding to the simple U-TOC of the embodiment is incorporated into the data U-TOC. FIG. 4 is an explanatory diagram of a track management state of a disc on which a simple U-TOC of the embodiment is recorded. FIG. 9 is an explanatory diagram of a track management state after a data file corresponding to the simple U-TOC of the embodiment is incorporated into the data U-TOC. 6 is a flowchart of a recording process for simple U-TOC according to the embodiment. It is a flowchart of reproduction | regeneration / transfer processing corresponding to simple U-TOC of an Example. 9 is a flowchart of copy guard data recording processing according to the embodiment. 9 is a flowchart of a reproduction process for copy guard according to the embodiment. FIG. 4 is an explanatory diagram of a recording position of a data file corresponding to a simple U-TOC of the embodiment. FIG. 4 is an explanatory diagram of a recording position of a data file corresponding to a simple U-TOC of the embodiment.

Explanation of reference numerals

Reference Signs List 1 disc 10 recording / reproducing device 11 disc insertion unit 12 key input unit 13 display unit 14 image scanner unit 15 input / output connector unit 16 input / output terminal 21 system controller 23 optical head 28 decoder 30 encoder 32 conversion memory 33 buffer RAM
34 Communication Circuit 35 Display Controller 36 A / D Converter 37 Encoder 38 Decoder 39 D / A Converter

Claims (3)

First management information recorded or updated according to the recording of the audio data or the general data file, and arranged in a predetermined management area on the recording medium as management information for managing the reproduction operation of the audio data or the general data file And a second management information which is arranged at a physically leading position in the area where the general data file is recorded and manages the general data file, is formed. A reproduction device corresponding to a recording medium on which specific keyword information is recorded in an area managed as a defect area in the second management information and / or the second management information;
Keyword reading means capable of searching for a defective area indicated in the first management information or the second management information and reading the keyword information;
An execution control unit that selects a process to be executed according to the presence or absence of keyword information to be read by the keyword reading unit or the content of the read keyword information;
A playback device comprising: First management information recorded or updated according to the recording of the audio data or the general data file, and arranged in a predetermined management area on the recording medium as management information for managing the reproduction operation of the audio data or the general data file And a second management information which is arranged at a physically leading position in the area where the general data file is recorded and manages the general data file, is formed. In the predetermined management area in which the management information is arranged, at least specific keyword information is included as information recorded from an address calculated by a predetermined calculation using the address of the first management information. As a playback device corresponding to the recording medium,
Keyword reading means capable of accessing an address calculated by a predetermined operation using an address of the first management information and reading the keyword information;
An execution control unit that selects a process to be executed according to the presence or absence of keyword information to be read by the keyword reading unit or the content of the read keyword information;
A playback device comprising: If the keyword information to be read by the keyword reading means does not exist, or if the read keyword information does not have the correct content, the execution control means does not execute the reproducing operation on the recording medium. The playback device according to claim 1, wherein the playback device is controlled to:

Images