JP3420155B2 - RECORDING DEVICE, RECORDING METHOD, COMPUTER-READABLE RECORDING MEDIUM RECORDING PROGRAM - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION The present invention is, records equipment, record how
Computer readable recording method , program
Recording medium

[0002]

2. Description of the Related Art In recent years, magneto-optical disks (hereinafter referred to as MO (Magneto)
A recording medium such as tic optical) is widely used for recording computer data. Further, as a next-generation recordable recording medium, development of a DVD-RAM disk (hereinafter abbreviated as DVD-RAM) is desired.

In the conventional MO, the HD (Hard Di
Like sc) and FD (Flexible Disc), an area of several kilobytes called a sector is the minimum access unit. Therefore, one file will be recorded over one or more sectors. The writing and reading of files are executed as a part of the functions of the computer OS (called a file system). For such a file system, for example, ISO / IEC13
346.

For example, when a 200 kbyte file is newly recorded on a recording medium having a sector size of 2 kbytes, the computer finds 100 free sectors and records the file. At that time, the 100 empty sectors may not be physically consecutive sectors. For example, when the empty sectors exist discretely such as 30, 30, 30, and 10, one file is distributed and recorded at four locations. Each distributed file portion, that is, a file portion recorded in consecutive sectors is called an extent.

As described above, according to the conventional technique, the file can be divided into a plurality of extents and recorded, so that no matter how many times the file is written and erased on the recording medium, all the sectors can be effectively used. There are advantages.

[0006]

However, according to the recordable recording medium and file system in the prior art, when audio / video data (hereinafter abbreviated as AV data) is recorded, a smooth continuous reproduction is performed at the time of reproduction. There is a problem that we cannot guarantee. In other words,
When recording / erasing of AV data on a recordable recording medium is repeated several times, the AV data file is not always recorded in physically consecutive sectors, and is recorded as a plurality of extents as described above. Will be recorded. As a result, in the reproducing apparatus, the seek operation of the optical pickup occurs between the extents, and continuous data reading cannot be performed.

For example, when a seek occurs from the innermost circumference of the disc to the outermost circumference of the disc, a seek time of several hundred milliseconds occurs. A video needs to reproduce a picture at about 30 frames per second, but if a seek time of several hundred milliseconds occurs, the reproduced video will be interrupted. In particular, with a large-capacity recording medium such as a DVD-RAM, it is possible to record, reproduce, and delete a plurality of AV data (TV programs, etc.) as if they were VTRs. In file management,
The inability to guarantee continuous playback is a serious problem.

Further, the data recorded on the recording medium is AV
There is not only data but also computer data, and it is necessary to consider efficient storage of both of these on disk. In view of the above problems, and ensure a smooth continuous reproduction of AV data, and records device capable of efficiently recorded together with data other than AV data, serial
Recording method , computer readable recording program
The purpose is to provide an effective recording medium .

[0009]

In order to solve the above-mentioned problems, the recording apparatus of the present invention is an AV file which should guarantee continuous reproduction.
And optical discs for non-AV files that do not require the guarantee.
A recording device for recording on the optical disc,
The area is an area where N_sec consecutive sectors of S_size bytes are consecutive.
The optical disc is divided into a plurality of blocks
The disk contains sector information indicating the data allocation status of each sector.
Information is recorded, the recording device stores the sector information in an optical disc.
And the file to be recorded
If it is an AV file, refer to the read sector information
By doing so, the AV file can be continuously played to the playback device.
Continuous empty space of a certain size or more that can guarantee
Search means for searching the region and two or more searched
Write the AV file by dividing it into continuous free space
Means for storing the Vo in the playback device.
The output transfer rate of the track buffer, Tj, to the playback device
The maximum jump time of the optical pickup, Vr
Given the input transfer rate of the rack buffer, it is the size corresponding to the number N of the blocks represented by the formula N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr)).
It is characterized in that that.

[0010]

[0011]

[0012]

Here, the recording device further includes the writing device.
Management showing the area where the AV file is written
Equipped with means to create information and write it to the optical disc
You may stay.

Also, a computer read according to the present invention.
Possible storage media are AV files, which should guarantee continuous playback,
Also, write non-AV files that do not require the guarantee on the optical disc.
Computer read recording program for recording
Recordable area of the optical disc
Is an area with N_sec consecutive S_size bytes sectors.
The optical disc is divided into a plurality of blocks to be locked.
Sector information indicates the data allocation status of each sector
Is recorded, and the program is recorded from the optical disc.
Read out the information and the data to be recorded.
If the file is an AV file, the read sector information
AV file for the playback device
Over a certain size that can guarantee continuous playback of
Search step and 2 searched for continuous free space
Write an AV file by dividing it into one or more continuous free areas
The writing step is executed by the computer,
The specified size of Vo is the track buffer in the playback device.
Output transfer rate, Tj
The maximum jump time of the track, Vr
The size is equivalent to the number N of the blocks represented by the formula N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr))
It is characterized by that.

[0015]

[0016]

[0017]

BEST MODE FOR CARRYING OUT THE INVENTION First, a list of items in the embodiment will be described. (1) First Embodiment (1-1) Optical Disc (1-1-1) Physical Structure of Recordable Optical Disc (1-1-2) File System Management Information (Part 1) (1-1-3) File system management information (Part 2) (1-1-4) Minimum size of AV block (1-2-2) Hardware configuration of DVD recorder 10 (1-2-3) Functional block diagram (1-2- 4) Commands executed by the file system unit 102 (1-3) Recording / deletion (1-3-1) Manual recording process (1-3-2) Scheduled recording of AV data (1-3-3) AV data (1-3-4) Non-AV data recording (1-3-5) Non-AV data deletion (2) Second embodiment (2-1) Optical disc (2-1-1) Pseudo continuous recording ( 2-1-2) Pseudo continuous recording allocation (2-1-3) Pseudo continuous recording allocation management information and space bit map (2-2) Recording / playback device (2-2-1) System and hardware configuration (2 -2-2) Functional block diagram (2- 3-1) Recording of AV file (3) Third embodiment (3-1) Minimum size of pseudo continuous recording area (3-2) Recording of AV file Recordable optical disk and optical disk recording in the embodiments of the present invention The apparatus will be described in the above item order. (1) First Embodiment (1-1) Optical Disc (1-1-1) Physical Structure of Recordable Optical Disc FIG. 1 shows the appearance of a DVD-RAM disc which is a recordable optical disc in the embodiment of the present invention and It is a figure showing the recording area. As shown in the figure, the DVD-RAM disc has a lead-in area at the innermost circumference, a lead-out area at the outermost circumference, and a data area therebetween. The lead-in area is
In the recording / reproducing apparatus, a reference signal necessary for stabilizing the servo and an identification signal with other media are recorded. In the lead-out area, the same reference signal as in the lead-in area is recorded.

The data area is divided into a sector (2 kbytes), which is the minimum access unit, and is further divided into a plurality of block areas (hereinafter referred to as AV blocks) including a plurality of consecutive sectors. ing. The AV block has a size ensured so that the playback is not interrupted even if a seek operation occurs in the playback device, and is about 7 Mbytes in this embodiment. The data area is managed as follows by providing an AV block in addition to a unit called a sector.

Non-AV data other than AV data is allocated in sector units, while AV data is allocated in AV block units. Non-AV data is managed in sector units, and AV data is managed in AV block units. The data written in the sector in the AV block may be AV data or non-AV data. In addition, AV blocks include AV data and non-AV
It is managed so that the data does not mix.

FIG. 2 is a view showing a cross section and a surface of a DVD-RAM which is enlarged and cut out to a sector level. As shown in the figure, one sector consists of a pit row portion formed on the surface of a reflective film such as a metal thin film, and an uneven portion. The pit string is 0.4 stamped to show the sector address.
It consists of pits of μm to 1.87 μm.

The concavo-convex portion is composed of a concave portion (called a groove) and a convex portion (called a land). Recording marks, which are metal thin films capable of phase change, are attached to the surfaces of the lands and the grooves. The phase change means that the state of the adhered metal thin film changes to a crystalline state and an amorphous state by irradiation with a light beam. Data can be written in the uneven portion by utilizing the phase change. In the MO disc, only the land portion is used for recording, whereas in the DVD-RAM, data can be recorded also in the land portion and the groove portion. Realization of data recording in the groove portion increases the recording density as compared with MO. The error correction process for the sector is performed for every 16 sectors. In this embodiment, EC
A sector group (16 sectors) to which C (Error Correcting Code) is added is called an ECC block.

In the DVD-RAM, the data area is divided into a plurality of zone areas in order to realize rotation control called Z-CLV (Zone-Constant Linear Velocity) in the recording / reproducing apparatus. Figure 3 (a) shows the DVD
FIG. 6 is a diagram showing a plurality of zone areas concentrically provided in a RAM. As shown in the figure, the DVD-RAM is divided into 24 zone areas from zone 0 to zone 23. Here, the zone area refers to a group of tracks that are accessed at the same angular velocity. In the present embodiment, one zone area includes 1888 tracks. The rotational angular velocity of the DVD-RAM is set for each zone area so that it becomes faster toward the inner circumferential side zone, and is kept constant while the optical pickup makes access within one zone. This allows the DVD-RA
The recording density of M is increased and the rotation control in the recording / reproducing device is facilitated.

FIG. 3B is an explanatory diagram in which the lead-in area, the lead-out area, and the zone areas 0 to 23, which are shown concentrically in FIG. 3A, are arranged in the lateral direction. The lead-in area and the lead-out area each have a defect management area (DMA). The defect management area is an area in which position information indicating the position of a sector in which a defect has occurred and alternative position information indicating in which of the alternative areas the sector that replaces the defective sector exists are recorded. .

Each zone area has a user area therein, and also has an alternative area and an unused area at the boundary. The user area is an area that the file system can use as a recording area. The replacement area is an area used as an alternative when a defective sector exists.
The unused area is an area that is not used for data recording.
The unused area is provided for about two tracks. The unused area is provided because the sector address is recorded at the same position on the adjacent tracks in the zone.
In the LV, since the recording positions of the sector addresses are different on the tracks adjacent to the zone boundary, it is possible to prevent erroneous determination of the sector addresses due to the recording positions.

Thus, there are sectors that are not used for data recording at the zone boundaries. Therefore, as shown continuously in only the sectors used for data recording, the DVD-R
AM is a logical sector number (LSN: Logical
Sector Number) is assigned to the physical sector of the user area. As shown in FIG. 3C, the area for recording user data, which is composed of sectors to which the LSN is added, is called a volume space.

Further, as shown in FIG. 3D, volume structure information for treating the disc as a logical volume is recorded on the inner and outer circumferences of the volume space. A portion of the volume space excluding the inner and outer volume structure information areas is an area in which a user file is recorded and is called a partition space. In the partition space, a logical block number (LBN: Logical Block Number) is assigned from the first sector in sector units.

In each zone area, the AV block has a fixed size, but AV_BLK # n, which is the last AV block in the zone area, has a larger size than other AV blocks. FIG. 4 is a diagram hierarchically showing the relationship between AV blocks and sectors in the zone area. As shown in the figure, one AV block consists of 224 ECC blocks, that is, 3584 sectors. However, since the number of sectors in the zone is not always an integral multiple of 224 ECC blocks,
The size of the last AV block in the zone is an integral multiple of the ECC block and larger than the 224 ECC block. Therefore, in the DVD-RAM, a table describing the size of the final block length for each zone is recorded as part of the management information.

FIG. 5 shows the final block length table. In the final block length table, the final block length and the final logical block number are associated with each other and recorded. Here, the final block length is in units of ECC blocks, that is, the number of ECC blocks. The final logical block number indicates the logical block number of the sector at the end of the final block (that is, the end of the zone) to indicate the position of the zone boundary.

By thus making the block length of the final AV block variable, it is possible to efficiently use the recording area of the disc while avoiding the AV block from straddling the zone boundary. (1-1-2) File System Management Information (1) Next, the file system structure of the DVD-RAM will be described. The file system of this embodiment is ISO / IEC1
In addition to managing according to the regulations of 3346, AV data is managed in AV block units.

FIG. 6 is a diagram showing a sector management table and an AV block management table of the file system management information recorded in the volume space. In the figure, the volume space, the sectors, and the recorded contents of the sectors are hierarchically illustrated. The first layer shows the volume space shown in FIG. The second hierarchy shows each sector area in which the sector management table and the AV block management table are recorded in the partition space. A sector management table (also referred to as a space bit map) indicating the data allocation status for each sector is recorded in the sector areas of the logical block numbers 0 to 79. In the sector areas of the logical sector numbers 84 and 85, an AV block management table showing the data allocation status in units of AV blocks is recorded.

The space bitmap shown in the third layer is
For all sectors in the partition space, each sector is assigned or unassigned.
In this example, the bit map is 1 bit per sector. For example, since the logical block numbers 0 to 79 are allocated as the space bitmap, they are “0 (allocated)”. Similarly, the logical block number 848
Since 5 is also assigned as the AV block management table, it is “0 (allocated)”. As described above, each bit in the space bitmap corresponds to a logical sector and is "0" (allocated) when a file or a part of the file is or will be recorded in the sector by the user or application. Otherwise, "1 (unallocated)" is recorded.

In the AV block management table shown in the third layer, with respect to all AV blocks in the partition space, each AV block is unused ("00") or allocated to AV data ("01"). It is represented by 2-bit data whether it is already assigned (“10”) to non-AV data. For example, in the AV block 0, a space bitmap and a non-A
Since V data is assigned, it is recorded as "10". In the AV block management table, an AV block already assigned to AV data is recorded in the space bitmap as all sectors included in the AV block being assigned. This avoids mixing AV data and non-AV data in one AV block.
A continuous recording area for V data is secured.

FIG. 7 is a diagram showing the relationship between the AV block management table and the space bitmap. The left side of the figure is an AV block management table, in which 2-bit data indicating the allocation status of AV blocks is arranged. In this example, the AV blocks (AV_BLK in the figure) # 0 to # 2 have "
10 (non-AV data) ", AV block (AV_BLK in the figure)
"01 (AV data)" is assigned to # 3 to # 75, and "00 (unallocated)" is assigned to the AV block # 76 and thereafter. The right side of FIG.
Only the portions showing the allocation status of the sectors included in the blocks # 0, # 3, and # 79 are shown arranged in a broken line frame. A
In the space bitmap portion corresponding to V block # 0, the AV block is allocated to 10 (non-AV data), so the sector in which non-AV data is recorded is "0 (allocated)". The unrecorded sector is set to “1 (unallocated).” Since the AV block is allocated to “01 (AV data)”, the space bitmap part corresponding to the AV block # 3 is all set. It is set to "0 (allocated)" for the sector.
Further, the space bit map portion corresponding to the AV block # 79 is set to “1 (unallocated)” for all sectors because the AV block is not “00” allocated.

The AV block management table may be stored as data for a file system like the space bitmap or the like, or may be stored as one file. In the latter case, the AV block management table will be managed as a file of non-AV data. Further, although the AV block management table has a table structure in this example, it may have a list structure. (1-1-3) File System Management Information (Part 2) FIG. 8 is a diagram for explaining information other than the sector management table and AV block management table in FIG. 6 among the file system management information. is there. In the figure, the volume space, the sectors, and the recorded contents of the sectors are hierarchically illustrated. Arrows ~ in the figure show the order in which the recording position of the file "Movie1.VOB" is specified according to the management information in the figure.

The first layer in the figure shows the volume space shown in FIG. 3 (d). The second layer shows a file set descriptor, a terminal descriptor, a file entry, a directory, etc. in the management information. This information is
It conforms to the file system specified in ISO / IEC13346. The file system defined in ISO / IEC13346 is
It realizes hierarchical directory management. 9 shows a hierarchical directory structure corresponding to the management information shown in FIG.
Shown in. In FIG. 9, an elliptical figure represents a directory and a rectangle represents a file. The root directory is
One directory called Video and File1.DAT, File2.DA
It has two files called T and the DVD directory is
It has three files, Movie1.VOB, Movie2.VOB, and Movie3.VOB. The management information of FIG. 8 is illustrated along this directory structure. However, the recording area of each file shows only Movie1.VOB.

The file set descriptor (LBN80) in the second layer indicates the LBN of the sector in which the file entry of the root directory is recorded. The end descriptor (LBN81) indicates the end of the file set descriptor. File entry (LBN82, 584, 3585
Is recorded for each file (including directory), and indicates the recording position of the file or directory. The file entry for a file and the file entry for a directory are defined in the same format so that a hierarchical directory structure can be freely constructed.

Directory (LBN83, 585, etc.)
Indicates the recording position of the file entry for each file and each directory included in the directory. The third hierarchy illustrates three file entries and two directories. The file entry and the directory are tracked by the file system, and have a data structure that can specify the recording position of a specific file, regardless of how the directory structure is hierarchized.

Each file entry includes an allocation descriptor indicating the recording position of the file or directory. When the file or directory is divided and recorded in a plurality of extents, the file entry includes a plurality of allocation descriptors for each extent. For example, each file entry of the LBNs 82 and 584 in the figure includes one allocation descriptor, which means that the file is not divided into a plurality of extents (consisting of one extent). On the other hand, LB
Since the file entry of N3585 includes two allocation descriptors, it means that the file consists of two extents.

Each directory includes, for each file and directory included in the directory, a file identification descriptor indicating the recording position of the file entry. According to such file entries and directories,
For example, as shown by the arrow in the figure, "root / video / Movie1.
The recording position of the "VOB" file is the file set descriptor →
→ file entry (root) → → directory (ro
ot) → → file entry (video) → → directory (video) → → file entry (Movie1.VOB)
→→ File (Movie1.VOB extents # 1, #
Followed in the order of 2).

FIG. 10 is a diagram in which the link relationship between the file entry and the directory on this path is rewritten according to the directory structure. In the figure, the root directory includes file identification descriptors for the parent directory (the root parent is the root itself), the VIDEO directory, the File1.DAT file, and the File2.DAT file. Also, the VIDEO directory is for the parent directory (root) directory, for the Movie1.VOB file,
Includes file identifier descriptors for Movie2.VOB files and Movie3.VOB files. Also in the figure, the recording position of the Movie1.VOB file is specified by following the above steps 1 to 3.

FIG. 11A shows a more detailed data structure of the file entry. As shown in the figure, the file entry has a descriptor tag, an ICB tag, an allocation descriptor length, an extended attribute, and an allocation descriptor. In the figure, BP represents a bit position and RBP represents a relative bit position. The descriptor tag is a tag indicating that it is a file entry. There are types of tags in the DVD-DAM, such as a file entry descriptor and a space bitmap descriptor. In the case of a file entry, 261 indicating the file entry is described as a descriptor tag.

The ICB tag indicates attribute information about the file entry itself. The extended attribute is information for indicating an attribute higher than the content defined by the attribute information field in the file entry. In the allocation descriptor field, as many allocation descriptors as the extents of the file are recorded. The allocation descriptor indicates a logical block number (LBN) indicating the recording position of the extent of the file or directory. The data structure of the allocation descriptor is shown in FIG. FIG. 11 (b)
In, the allocation descriptor includes data indicating the extent length and a logical block number indicating the recording position of the extent. However, the upper 2 bits of the data indicating the extent length indicate the recording status of the extent recording area as shown in FIG.

FIGS. 12A and 12B show detailed data structures of the file identification descriptors for the directory and the files included in the directories, respectively. These two types of file identification descriptors have the same format, and the management information, the identification information, the length of the directory name, and the address that indicates in which logical block number the file entry of the directory or file is recorded , Extension information, and a directory name. As a result, the address of the file entry corresponding to the directory name or file name is specified. (1-1-4) Minimum Size of AV Block The size (lower limit) of the AV block shown in FIG. 4 will be described.

The AV block is composed of 224 ECC blocks (about 7 MBytes) excluding the final AV block in each zone. In order to guarantee continuous playback of AV data, A
The minimum size of the V block is determined in relation to the buffer in the playback device. FIG. 13 shows D in the reproducing apparatus.
FIG. 7 is a modeled view of buffering AV data read from a VD-RAM.

In the upper part of FIG. 13, the AV data read from the DVD-RAM is subjected to ECC processing, temporarily stored in a FIFO (First In First Out) memory called a track buffer, and further output from the track buffer to a decoder. To be done. The transfer rate (minimum value) of the track buffer input is Vin, and the transfer rate (maximum value) of the track buffer output is Vout (provided that Vin> Vout).
Here, Vin = 8 Mbps and Vout = 11 Mbps.

The lower part of FIG. 13 is a graph showing changes in the data amount of the track buffer in this model. The vertical axis represents the amount of data in the track buffer, and the horizontal axis represents time. The period T1 on the time axis is the time during which all AV data from the beginning to the end of the AV block #j filled with AV data is read. In this period, (Vin-Vout)
The amount of data in the buffer increases at the rate of. Period T
3 is also the same.

The period T2 (hereinafter referred to as the jump period) is
AV block light peak from #j to AV block #k Kkua <br/> Tsu maximum time-flop takes to jump showing a (for example, from the innermost circumference to the outermost circumference). The jump time includes the seek time of the optical pickup and the time required for the rotation of the optical disc to stabilize. In this period, the amount of data in the buffer decreases at the rate of Vout. The same applies to the period T4.

When the size of the AV block is L bytes, the lower limit value is calculated as follows. Period T2
Then, only AV data is read from the track buffer. If the buffer capacity becomes 0 within this period, an underflow will occur in the decoder. In this case, continuous reproduction of AV data cannot be guaranteed.

In order to guarantee continuous reproduction (to prevent underflow), the following expression must be satisfied.

[0050]

[Equation 1] The buffer accumulation amount B is the amount of data accumulated in the buffer at the end of the period T1. The read amount R is the total amount of data read within the period T2. The accumulated amount B can be expressed by the following equation.

[0051]

[Equation 2] The read amount R can be expressed by the following equation. However, the maximum jump time Tj is considered to be about 1.5 seconds at worst.

[0052]

[Equation 3] When the above (Equation 1) is replaced with (Equation 2) and (Equation 3), the following equation is obtained.

[0053]

[Equation 4] From this equation, the AV block size L must satisfy the following equation.

[0054]

[Equation 5] As described above, if AV data is recorded in a continuous sector of 5.5 Mbytes in one AV block, AV
Even if a jump occurs between blocks, continuous playback is guaranteed. The minimum size of an AV block for guaranteeing continuous reproduction is 5.5 Mbytes. In this embodiment, AV
The reason why the block size is 7.2 Mbytes is
This is because the margin is expected in case a disk error occurs. Also, the capacity of the track buffer must be (Equation 3) in order to prevent underflow.
Therefore, at least 1.5 MB is required. (1-2) Recording / Reproducing Apparatus Next, an optical disk recording / reproducing apparatus of the present invention will be described with reference to the drawings. (1-2-1) Overall System FIG. 14 shows an example of the configuration of a system using the optical disc recording / reproducing apparatus of this embodiment.

This system includes an optical disk recording / reproducing apparatus 10 (hereinafter referred to as a DVD recorder 10), a remote controller 6 for operating the same, a display 12 connected to the DVD recorder 10, and a receiver 9. The DVD recorder 10 is equipped with the above-mentioned DVD-RAM as an optical disc, compresses audio / video data contained in an analog broadcast wave received through the receiver 9, and records the AV block on the DVD-RAM as a minimum unit. D
The compressed audio / video data recorded in the VD-RAM is expanded, and the video signal and audio signal are output to the display 12. (1-2-2) Hardware Configuration of DVD Recorder 10 FIG. 15 is a block diagram showing the hardware configuration of the DVD recorder 10.

This DVD recorder 10 includes a control unit 1, M
PEG encoder 2, disk access unit 3, MPEG
Decoder 4, video signal processor 5, remote controller 6, bus 7
It also has a remote control signal receiver 8 and a receiver 9.
The control unit 1 includes a CPU 1a, a processor bus 1b, a bus interface 1c, and a main memory 1d, and executes a program stored in the main memory 1d to record, reproduce, or edit AV data in the DVD recorder 10. Control the whole thing. Particularly, when recording AV data, the control unit 1 performs control according to the above file system with the AV block of the DVD-RAM as the minimum unit.

The MPEG encoder 2 compresses the audio / video signal contained in the analog broadcast wave received by the receiver 9 into an MPEG stream. The disk access unit 3 has a track buffer 3a inside, and the control unit 1
Under the control of M
PEG stream to DV via track buffer 3a
Recorded in D-RAM, and MPE from DVD-RAM
The G stream is read and output to the MPEG decoder 4 via the track buffer 3a.

The MPEG decoder 4 uses the MPE read from the DVD-RAM by the disk access unit 3.
The video signal processing unit 5 that decompresses the G stream and outputs the video data and the audio signal as the decompression result performs signal processing for converting the video data from the MPEG decoder 4 into a video signal for the display 12.

The remote control signal receiving unit 8 receives the remote control signal and determines what kind of user operation has been performed.
To notify. As shown in FIG. 14, the DVD recorder 10 has a configuration based on the assumption that it is used as a substitute for a conventional stationary VTR for home use. Not limited to this configuration,
When the DVD-RAM is also used as a recording medium of a computer, it may have the following configuration. That is, the disk access unit 3 is connected to the computer bus as a DVD-RAM drive device via an IF called SCSI or IDE. In addition, components other than the disk access unit 3 in FIG.
It is realized that S and an application program are executed.

This DVD recorder 10 includes a control unit 1, M
PEG encoder 2, disk access unit 3, MPEG
Decoder 4, video signal processor 5, remote controller 6, bus 7
It also has a remote control signal receiver 8 and a receiver 9.
FIG. 16 is a block diagram showing the structure of the MPEG encoder 2. As shown in the figure, the MPEG encoder 2 includes a video encoder 2a, a video buffer 2b for storing the output of the video encoder, and an audio encoder 2c.
An audio buffer 2d for storing the output of the audio encoder, a system encoder 2e for multiplexing the encoded video data in the video buffer 2b and the encoded audio data in the audio buffer 2d, and a synchronization clock for the encoder 2. It is composed of an STC (system time clock) unit 2f for generating and an encoder control unit 2g for controlling and managing them. The encoder control unit 2g outputs information such as GOP (Group Of Picture: MPEG stream of about 0.5 seconds including at least one I picture) information and picture information of the encoded data and the control unit 1 of FIG. Pass to.

FIG. 17 is a block diagram showing the structure of the MPEG decoder 4. As shown in the figure, MPEG decoder 4
Is a demultiplexer 4a for separating the MPEG stream into a video stream and an audio stream, a video buffer 4b for temporarily storing the separated video stream, and a video decoder 4c for decoding the video stream stored in the video buffer 4b. , An audio buffer 4d for temporarily storing the separated audio stream, an audio decoder 4e for decoding the audio stream stored in the audio buffer 4d, an STC (system time clock) unit 4f for generating a synchronization clock, and a synchronization An adder 4g that adds an offset to the clock, and a selector that selects one of the synchronous clock and the synchronous clock with the offset and supplies the demultiplexer 4a, the audio decoder 4e, and the video decoder 4c. Composed of a h~4j.

The MPEG decoder 4 shown in the figure is a general MPE having no selectors 4h to 4j and an adder 4g.
The configuration may be the same as that of the G decoder. (1-2-3) Functional Block Diagram FIG. 18 is a functional block diagram showing the configuration of the DVD recorder 10 by function. Each function in the figure is realized by the CPU 1a in the control unit 1 controlling the hardware shown in FIG. 14 by executing the program in the main memory 1d.

In FIG. 18, the DVD recorder 10 includes a disc recording unit 100, a disc reading unit 101, a file system unit 102, a recording / editing / playback control unit 105, a user IF unit 106, an AV data recording unit 110, an AV data editing unit 120, and The AV data reproducing unit 130 is included. The disk recording unit 100 includes a file system unit 10
When the logical sector number and the logical data (2048 bytes) in units of one or more sectors are input from 2, the data is recorded on the disk in units of ECC blocks (16 sectors). If the logical data is less than 16 sectors, the ECC block is once read, the ECC process is performed, and then the ECC block is recorded.

When the logical sector number and the number of sectors are input from the file system unit 102, the disk reading unit 101 reads in ECC block units, and E
Only the required sector data is transferred to the file system unit through the CC processing. Similar to the disc recording unit, overhead is reduced by reading in units of 16 sectors for each ECC block when reading AV data.

The file system unit 102 is mainly composed of A
The AV data recording unit 110 and the AV data editing unit 12 have an AV file system unit 103 for writing and editing V files and a common file system unit 104 for performing common processing for AV files and non-AV files.
0, receiving a command for writing or reading a file from the AV data reproducing unit 130, performs file management for an AV file with the AV block of the optical disc as a minimum unit, and for the non-AV data, the common file system unit 104. File management is performed by using the sector of the optical disc as the minimum unit.

Among various file management by the file system unit 102, here, (a) writing AV data, (b) deleting AV data, (c) writing non-AV data, and (d) deleting non-AV data. The allocation of AV blocks and sectors in each scene will be described. (A) When writing AV data: When the AV file system unit 103 receives a recording command of AV data from the AV data recording unit 110 or the like, the AV block “00 (unallocated)” in the AV block management table is set to the AV block.
A is assigned to the data and the A
The AV data is recorded in the V block, the AV block is changed to "01 (for AV)" in the AV block management table, and all the sectors included in the AV block are set to "0 (allocation) in the space bitmap. Already)"
Change to.

FIG. 19 shows how the AV block management table and space bitmap change when writing AV data.
Shown in. The left side of the figure is A in the AV block management table.
It shows before and after the change of 2-bit data indicating the allocation status of V block #n. The right side of the figure is A in the space bitmap.
It shows before and after the change of the portion corresponding to the sector included in the V block #n. As shown in the figure, when the AV block #n is newly assigned to "01 (for AV data)" from "00 (unallocated)" in the AV block management table, the AV block is assigned to the AV block in the space bitmap. "1 (unallocated)" to "0" for all included sectors
(Allocated) ”, whereby AV data and non-AV data are not mixed in one AV block, and a continuous recording area corresponding to the AV block length is secured for the AV data.

(B) When deleting AV data: When the AV file system unit 103 receives a command for deleting AV data from the AV data editing unit 120, the AV data in the AV block management table is recorded with the AV data.
Change the block to "00 (unallocated)" and
All sectors included in the V block are changed to "1 (unallocated)" in the space bitmap.

FIG. 20 shows how the AV block management table and space bitmap change when AV data is deleted. As shown in the figure, when the AV block #n is newly changed from "01 (for AV data)" to "00 (unallocated)" in the AV block management table, it is changed to the AV block in the space bitmap. "0 (allocated)" to "1 (unallocated)" for all included sectors
Is changed to.

(C) At the time of writing non-AV data: When the common file system section 104 receives a non-AV data write command from the recording / editing / playback control section 105,
Sectors included in the AV block “10 (for non-AV)” in the block management table and “1 (unallocated)” in the space bitmap are assigned to the non-AV data, and the non-AV data is assigned to the assigned sector. Recording is performed via the disc recording unit 100, and the sector is changed to "0 (allocated)" in the space bitmap. If "10" in the AV block management table
If there is no "1 (unallocated)" sector included in the "(non-AV)" AV block, the non-AV data is allocated to the sector in the "00 (unallocated)" AV block, The AV block is changed to "10 (for non-AV)" and the sector is changed to "0 (allocated)".

(D) When deleting non-AV data: When the common file system unit 104 receives a non-AV data deletion command from the recording / editing / playback control unit 105 or the like, the non-AV data is recorded in the space bitmap. Change all sectors to "1 (unallocated)". Further, when all the sectors in the AV block including the sector become “1 (unallocated)”, the AV block is set to “10” in the AV block management table.
(For non-AV data) to "00 (unallocated)".

The recording / editing / playback control section 105 is a section for controlling the entire DVD recorder 10. In particular, it controls a guidance display prompting a user operation, and accepts a user operation for the guidance display via the user IF section 106. Depending on the operation, recording of new AV data, reproduction and editing of recorded AV data, etc. can be performed by the AV data recording unit 110, A
A request is made to the V data editing unit 120 and the AV data reproducing unit 130.

The user IF section 106 receives a user operation from the remote controller 6 and notifies the recording / editing / playback control section 105 of it. AV data recording unit 110, AV data editing unit 1
20, the AV data reproducing unit 130 receives a recording request, an editing request, and a reproducing request from the recording / editing reproducing control unit 105, and issues commands required for the requested recording, editing, and reproducing to the AV file system unit 103. . (1-2-4) Command Executed by File System Unit 102 Next, various commands supported by the file system unit 102 will be described.

The file system unit 102 receives various commands from the AV data recording unit 110, the AV data editing unit 120, the AV data reproducing unit 130, the recording / editing reproduction control unit 105, etc., and manages files. FIG. 21 is a list showing commands related to file management by the file system unit 102. The processing contents of the file system unit 102 for each command will be briefly described.

"CREATE" creates a new file on the disk and returns a file identification descriptor. "DELETE" deletes the file that exists on the disk. More specifically, when the AV file is deleted, the allocation of the recording area is released in AV block units, and when the non-AV file is deleted, the allocation of the recording area is released in sector units.

"OPEN" acquires a file identification descriptor for a file recorded on the disc in order to access the file. "CLOSE" closes the open file. “WRITE” records a non-AV file on the disc. More specifically, non-A
A recording area is allocated to each sector in the V AV block and recording is performed in the allocated sector.

"READ" reads a file recorded on the disc. "SEEK" moves in the data stream recorded on the disc. "RENAME" changes the file name. "MKDIR" creates a new directory on disk. “RMDIR” deletes the directory that exists on the disk.

“STATFS” inquires about the current status of the file system. "SET_ATTR" changes the attributes of the file that is currently open. “AV-WRITE” records an AV file on the disc. More specifically, A
A recording area is allocated for each V block and recording is performed in the allocated AV block.

"SEARCH_DISCON" checks whether or not there is a discontinuous boundary (zone boundary) in the specified section, and if there is, it is TRUE.
, Or FALSE if there is none. "MERGE" merges the two AV files on the disc with the data in the memory.
"SPLIT" divides the AV file on the disc into two AV files.

“SHORTEN” deletes the end of the AV file on the disc and deletes unnecessary parts of the AV file. "REPLACE" replaces a part of the AV file with the data in the memory. What should be noted here is that “AV-WRITE” for recording AV data and “WRITE” for recording non-AV data are separately supported.

By combining these commands, the AV data recording section 110 and the AV data editing section 12
0, the AV data reproducing unit 130 realizes processing such as recording, editing, and reproducing. (1-3) Recording / Deletion Next, in the DVD recorder 10, (1-3-1) manual recording of AV data, (1-3-2) scheduled recording of AV data, (1-3-3) AV data (1-3-4) non-AV data recording and (1-3-5) non-AV data deletion will be described in detail. (1-3-1) Manual recording process Manual recording is a recording process that starts immediately after setting a few items when the user presses the "record" key on the remote controller without setting the reserved time. .

For example, when the user presses the record button on the remote controller 6 as shown in FIG. 22, a guidance image 200 as shown in FIG. 23 is displayed on the display 12 under the control of the recording / editing / playback control section 105. When the user presses “1” and “select” in this guidance image 200, a guidance image 201 for setting recording conditions (recording time and recording quality in this example) is displayed.

The "recording time" of the recording condition is set by moving the focus to "unlimited" or "designated time" with the cursor button of the remote controller 6 and pressing the "select" button again. When “designated time” is selected, the ten key button is used to switch to the guidance image for inputting the time. When the setting of the designated time is completed, the guidance image 201 is displayed again.

There are three types of "recording quality" of the recording condition regarding the bit rate and resolution of MPEG data: high image quality, standard, and time priority. The bit rate and resolution of each are shown in FIG. Now, as a case of manual recording, it is assumed that “unlimited” and “time priority” are selected in the guidance image 201, and the “record” button on the remote controller is pressed after moving to the guidance image 202. This starts the manual recording process.

FIG. 25A is a flowchart showing the contents of the manual recording process. In the figure, first,
The notification of pressing the “record” button is sent to the recording / editing / playback control unit 105 via the user IF unit 106. The recording / editing / playback control unit 105 issues a "CREATE" command to the common file system unit 104 (step 250).
In response to this, the common file system unit 104 returns a file identification descriptor if a file can be created. At this time, according to the recording condition that the recording time is unlimited,
The file size is the maximum size of the disc. Further, the recording / editing / playback control unit 105 notifies the AV data recording unit 110 of the file identifier and the parameter indicating the time priority set in the recording condition.

The AV data recording section 110 starts the MPEG encoder 2 to encode the video data and the audio data of the program of the specific channel which is being received via the receiver 9, and the MPEG data of the encoded result is stored in the track buffer 3a. Start the transfer process. At the same time, the AV data recording unit 110 sends an "OPEN" command to the A
Issued to the V file system unit 103 (step 25)
As a result, the information about the file identification descriptor and its file entry given from the recording / editing / playback control unit 105 is held in the work memory (not shown) (hereinafter, the above information in the work memory is Fd (file descriptor)). Abbreviated).

Further, the AV data recording section 110 receives an "AV-WRITE" command every time a fixed amount of MPEG data is accumulated in the track buffer 3a until a stop command is received from the recording / editing / playback control section 105. Is issued to the AV file system unit 103 (steps 252, 253),
When the stop command is received, the "AV-WRITE" command (step 254) is issued, and the "CLOSE" command is issued (step 255) to finish the process. The "AV-WRITE" command in step 254 is for processing the allocation descriptor of the final extent to be held in Fd. The “CLOSE” command in step 255 is for writing back Fd in the work memory by the file identification descriptor and file entry on the DVD-RAM.

Next, details of the data recording process by the above-mentioned "AV-WRITE" will be described. FIG. 26 shows "AV-WRITE".
7 is a flowchart showing the processing contents of the AV file system unit 103 that received a command. In the figure, "AV-WRI
The “TE” command is issued to the AV file system unit 103 together with the designation of three parameters. The three parameters are the Fd opened by the "OPEN" command, the size of the data to be recorded, and the buffer holding it (the track buffer 3a in this embodiment). Also, F specified as a parameter
Like the file entry, d includes information indicating the recording position of the extent and the extent length, and is sequentially updated when a plurality of “AV-WRITE” commands are issued from the time the file is opened until the time it is closed. . In the second and subsequent “AV-WRITE” commands, new data is added after the already recorded data.

In the figure, the AV file system unit 1
03 provides a counter for counting the size specified as a parameter in the work memory until recording of data of the specified size is completed (step 26
5: no), data is allocated and recorded for each sector as follows. The AV file system unit 103 determines whether there is already recorded data in the opened file (when issuing the first AV-WRITE at the time of recording) or when there is already recorded data (2 at the time of recording). AV after the first time
-When WRITE is issued) and the AV block is recorded up to the end (step 266: no), the AV file system unit 103 searches for an AV block of "00 (unallocated)" in the AV block management table ( In step 267, it is newly allocated to "01 (for AV)" (step 268), and all sectors in the AV block are changed from "1 (unallocated)" to "0 (allocated)" (step 268). Step 269).

Further, the AV file system unit 103 is
If there is already recorded data in the opened file and it is not recorded until the end of the AV block (step 266: yes), the process proceeds to step 270. The AV file system unit 103 extracts one sector's worth of data from the track buffer 3a in the head sector of the newly allocated AV block as described above, or in the sector following the already recorded data, and DV
The data is recorded in the D-RAM (step 270) and the counter is updated (step 271). Further, the AV file system unit 103 determines whether or not the currently recorded sector and the sector recorded immediately before that are continuous (step 272). Here, when both sectors are not physically continuous, and when both sectors cross the zone boundary of the AV block, it is determined that they are not continuous. Whether to cross the zone boundary is determined by the final block length table shown in FIG. If it is determined that they are not continuous, the AV data recorded up to the AV block immediately before that is held as one extent in the allocation descriptor of Fd (step 273). If it is determined that they are continuous, the process returns to step 265.

When the recording of the data of the size specified as the parameter is completed by repeating the recording in the sector as described above (step 265: yes), the AV file system unit 103 causes the last recorded sector to be recorded. The allocation descriptor of the last extent including is stored in Fd (step 274), and the process of "AV-WRITE" is completed.

In this way, the AV file system unit 10
When receiving the "AV-WRITE" command, 3 assigns an AV block, which is a continuous area of about 7 Mbytes, as a minimum unit. As a result, the extents forming the newly recorded AV file have a length of at least about 7 Mbytes except the last extent, so that continuous reproduction can be guaranteed.

In step 270, it has been described that the data for one sector is recorded on the DVD-RAM for the sake of convenience. ,
It is recorded on the DVD-RAM. (1-3-2) Scheduled recording of AV data Scheduled recording refers to a recording process when the user presses the "record" key on the remote controller together with setting the reserved time. That is, in FIG. 23 described above, the guidance image 2
This is the case where the designated time is set in 01.

Now, as a case of reserved recording, it is assumed that "designated time" and "time priority" are selected in the guidance image 201 and the "recording" button on the remote controller is pressed after moving to the guidance image 202. This starts reserved recording. FIG. 25B is a flowchart showing the processing contents of the reserved recording. In FIG. 9B, first, a notification of pressing the “record” button in the reserved recording is sent to the recording / editing / playback control unit 105 via the user IF unit 106.
The recording / editing / playback control unit 105 notifies the common file system unit 104 of the designated time and “CREAT
The "E" command is issued (step 256). In response to this, the common file system unit 104 returns a file identification descriptor if a file can be created. At this time,
The file size corresponding to the number of AV blocks corresponding to the designated time is taken. Further, the recording / editing / playback control unit 105 determines whether or not there is a free area corresponding to the designated time, depending on whether or not the common file system unit 104 notifies the file identification descriptor (step 257).

If the result of determination is that there is no free area, the recording / editing / reproduction control section 105 cannot record for the specified time, so error processing is performed and processing ends. When there is a free area, the recording / editing / playback control unit 105 notifies the AV data recording unit 110 of the file identifier, the designated time, and the parameter indicating the time priority set in the recording condition.
Upon receiving this, the AV data recording unit 110 issues an "OPEN" command at the time when the start time has come (step 258) (step 259). The subsequent processing of the AV data recording unit 110 is performed in steps 252 to 25 of FIG.
Almost in the same way as 5, the "OPEN" command is issued to the AV file system unit 103, the "AV-WRITE" command is repeatedly issued until the end time, and finally the "CL"
Issue the "OSE" command to end the process (step 2
58-262).

In this way, in the case of the reserved recording, it is checked in advance whether or not there are the number of empty AV blocks required for the recording of the designated time, and then the recording is performed. The steps 256 and 257 may be reversed. (1-3-3) Deletion of AV Data Deletion of a file is executed by the common file system unit 104 as processing of the “DELETE” command for both AV files and non-AV files. Common file system unit 10
When a “DELETE” command for a specific file is received from the recording / editing / playback control unit 105 or the like, reference numeral 4 indicates whether the file is an AV file or a non-AV file based on the file name extension, attribute information, or the like.
It is determined whether the file is a file, and different processing is performed on the AV block management table and the space bitmap according to the determination result.

FIG. 27 shows the common file system section 104.
7 is a flowchart showing a deletion process for an AV file by the. When the extent exists by referring to the file entry of the AV file (step 240: yes), the common file system unit 104 sets “01 (for AV data)” to the AV block included in the extent in the AV block management table. From "00
(Unallocated) ”(step 241), and for all sectors included in the AV block in the space bitmap, changed from“ 0 (allocated) ”to“ 1 (unallocated) ”(step 242). The extent is deleted from the entry (step 243) If the extent does not remain (step 240: no), the file identification descriptor is deleted and the process ends.

FIG. 28 (a) shows an explanatory diagram of the AV file to be deleted. The upper part of FIG.
In # 14, a state in which the AV file # 1 and the AV file # 2 are recorded is shown. The AV file # 1 consists of two extents (AV file # 1-1, AV file # 1-2), and the AV file # 2 consists of (AV file # 2-1, AV file # 2-2). The lower part of FIG. 9A shows a state in which the extent of the AV file # 1 in the AV blocks # 11 and # 14 is deleted.

An explanatory diagram showing changes in the AV block management table and the space bitmap in this case is shown in FIG.
Shown in. The left side of FIG. 10B is before deletion, and the right side is after deletion. According to the deletion process of FIG. 27, AV block # 11,
# 14 is “01 (A
V data) ”to“ 00 (unallocated) ”, A
All sectors in the V blocks # 11 and # 14 are changed from "0 (allocated)" to "1 (unallocated)" in the space bitmap. In addition, in the lower part of FIG.
The AV data of the V blocks # 11 and # 14 are not physically erased, but the AV file system unit 103
Are only treated as invalid data by. (1-3-4) Recording Non-AV Data FIG. 29 shows non-AV data recorded by the common file system unit 104.
It is a flowchart which shows the recording process of a file.

When the common file system unit 104 receives the "WRITE" command from the recording / editing / playback control unit 105 or the like and there is non-AV data to be recorded (step 261), the common file system unit 104 reads "10" in the AV block management table.
A sector included in the AV block (for non-AV) or "00 (unallocated)" and "1 (unallocated)" in the space bitmap is searched (step 262).
If the AV block including the found sector is "00 (unallocated)", it is changed to "10 (non-AV)" (step 263), and the sector found in the space bitmap is "1 (unallocated)". From "0 (allocated)" (step 264), and the non-AV data is recorded in the sector (step 265). Further, if the sector and the sector recorded immediately before that sector are continuous, step 2
Returning to step 61, if they are not consecutive, the allocation descriptors of extents up to the immediately preceding sector are recorded in the file entry (steps 266, 267). If there is no data to be recorded in step 261, the allocation descriptor of the extent up to the last recorded sector is recorded in the file entry (step 268), and the process ends. (1-3-5) Deletion of Non-AV Data When the common file system unit 104 receives a “DELETE” command for a specific file from the recording / editing / playback control unit 105, when the file is a non-AV file, The deletion process is performed as follows.

FIG. 30 shows the common file system section 104.
7 is a flowchart showing a deletion process for a non-AV file by the. When the extent exists by referring to the file entry of the non-AV file (step 271: yes), the common file system unit 104 starts from “0 (allocated)” for all sectors included in the extent in the space bitmap. It is changed to "1 (unallocated)" (step 242).

Next, in the AV block management table, it is determined whether or not all the sectors in the AV block included in the extent are "1 (unallocated)" (step 273). When all sectors are unallocated, the AV block is set to "1" in the AV block management table.
0 (for non-AV) ”to“ 00 (unallocated) ”(step 274) Further, the allocation descriptor of the extent is deleted (step 275) and the process returns to step 271. At step 271, the remaining extents are left. If there is not, the processing ends.

An explanatory view of the non-AV file to be deleted is shown in FIG. The upper part of FIG.
In the figure, it is shown that files # 3 and # 4, which are non-AV data, are recorded. Each of the files # 3 and # 4 has one extent. The lower part of FIG.
This shows that the extent of the file # 3 in the AV block # 11 has been deleted.

An explanatory view showing changes in the AV block management table and the space bitmap when the file # 3 is deleted is shown in FIG. The left side of FIG. 10B is before deletion, and the right side is after deletion. According to the deletion process of FIG.
Since the file # 4 remains in the AV block # 11, "10 (non-A
(For V data) ”remains. In the space bitmap corresponding to AV block # 11, the sector included in the extent of file # 3 is changed from“ 0 (allocated) ”to“ 1 (unallocated) ”. Note that the non-AV data of the file # 3 is not physically deleted in the lower part of FIG.
Are only treated as invalid data by.

As described above, the DVD-RAM in this embodiment has the space bit map and the AV block management table as a part of the management information for the file system. As a result, continuous areas are allocated in units of AV blocks, so that continuous reproduction of AV data can be guaranteed. Further, in the DVD-RAM of the present embodiment, when an AV block is allocated for AV data, all sectors included in the AV block are registered on the space bitmap as allocated. According to such management, even if the DVD-RAM of the present application is accessed by the conventional file system that only supports the space bitmap, the sector group included in the AV block for AV data is The data is prevented from being written and the continuous sector area reserved for AV data is lost.

AV assigned for non-AV data
In the block, only the sector in which the data is actually written among the sectors included in the AV block is recorded as allocated in the space bitmap. That is,
Unlike the AV block allocated for AV data, the AV block allocated for non-AV data is not registered as allocated on the space bitmap even for the sector in which data is not recorded.

Therefore, even if the AV block has already been allocated for non-AV data, other non-AV data can be written as long as there is a free space, so that in one AV block for non-AV data. It is possible to have a plurality of non-AV data files. Therefore, an AV block for AV data and an A block for non-AV data
It is possible to mix V blocks and improve the usage efficiency of the entire disk.

In the above-described embodiment, the DVD recorder 10 has a structure on the premise that it is used as a substitute for the conventional stationary household VTR as shown in FIG.
If the DVD-RAM is also used as a recording medium of a computer, not limited to this configuration, the following configuration may be adopted. That is, the disk access unit 3 is DV
IF called SCSI or IDE as a D-RAM drive device
Connected to the computer bus via. Further, the components other than the disk access unit 3 in the figure are realized by executing the OS and application programs on the computer hardware. In that case, the disk recording unit 100, the disk reading unit 101, and the file system unit 102 are realized mainly as a function of the OS or an application that expands the function of the OS, and the other components are realized mainly as a function of the application program. Also, the file system unit 10
Various commands supported by 2 correspond to service commands such as system calls provided to the application.

Further, in the above embodiment, the AV block management table represents the allocation status of each AV block by 2 bits, but the number of bits may be increased and other attribute information may be added. FIG. 32 shows a second configuration example of the AV block management table. In the AV block management table shown in the figure, each AV block has 2-byte data representing allocation information and attribute information. Of the 2-byte data, the upper 4 bits are for managing the allocation status of the AV block as in the above embodiment, and the lower 12 bits are the A.
This represents the number of valid ECC blocks that do not cause an address error among the ECC blocks included in the V block. For example, the first AV block has 224 valid ECC blocks.
The sixth AV block includes one ECC block in which an address error has occurred and 223
(DF in hexadecimal) contains valid ECC blocks.

As described above, in the AV block management table of FIG. 32, the number of valid ECC blocks excluding the ECC block including the address error is recorded. If the file system unit 102 does not know the number of valid ECC blocks of each AV block, it does not know how much data can be written in each AV block. Therefore, the file system unit 102 performs address error processing when recording the data. become. According to the AV block management table shown in the figure, the file system unit 102 is freed from complicated address error processing at the time of recording data.

It is also possible to have a record as to which ECC block or sector the address error occurred in as another information, which can be used by the AV file system. Further, when the probability of occurrence of an address error is extremely low and most of the AV block sectors can be regarded as a fixed-length block, the most significant 0 bit is set as a flag indicating whether it is a variable length and the flag is set. In this case, the area of the size is effective. In that case, if the size of the AV block is obtained from the area, the processing of the file system is reduced.

FIG. 33 shows a third configuration example of the AV block management table. In the AV block management table shown in the figure, each AV block is managed by 4-bit data. Similar to the above embodiment, the lower 3 bits of the 4-bit data indicate the allocation status of the AV block, and the upper 1 bit (called variable length bit) indicates whether the AV block has a fixed length or a variable length. Here, the fixed length means that the AV block has 224 effective ECC blocks in which no address error occurs. Variable length means that there are other than 224 valid ECC blocks in the AV block. The variable-length AV block has an ECC block in which an address error occurs or is an AV block at the end of a zone boundary.

The block length of the variable length AV block is recorded in the variable length AV block table shown on the right side of FIG. This table records a block number and the number of valid ECC blocks in association with each variable-length AV block, and is provided in place of the final block length table shown in FIG. In the AV block management table of FIG. 32, A in which the variable length bit corresponds to “1” (hatched portion)
The V block records the number of valid ECC blocks in the variable length AV block table. In this way, by providing the variable-length AV block management table with the size of the AV block and the AV block number, the file system manages the AV block in which the variable-length flag is set in the AV block management table. The variable length AV block table can be immediately obtained by the AV block number. Further, in the third configuration example, the size of the AV block management table itself can be made smaller than that in the second configuration example of FIG.

If the physical size of each AV block is variable, recording the sizes of all AV blocks in the variable-length AV block table facilitates the mapping of sectors to AV blocks. it can.
Furthermore, instead of having the physical size of each AV block in the variable-length AV block table, if the start sector number, track number, and zone number of each AV block are provided in the AV block management table, it becomes the same as the previous example. Similarly, mapping of sectors to AV blocks becomes easier.

FIG. 34 shows a fourth configuration example of the AV block management table. This AV block management table is
Two-byte data is used for each AV block, and the number of files recorded in the AV block is provided in addition to the allocation status of the AV block. Upper 4 in 2 byte data
The bit indicates the allocation status as in the above embodiment, and the lower 12
The bit indicates the number of files. In this case, the maximum number of files is 4095, so 1A
Up to 4095 files can be recorded in the V block.

Now, the lower 12 bits of the 2-byte data will be called a counter. The counter is a story closed in one AV block, and even if it is a large file such as an AV file, or even if it is a non-AV file and the size is small, it may be recorded over multiple AV blocks due to the free space. To be In this case, the counter is treated as one file if a part of the file is recorded. In other words, whether the file is recorded in the file or only a part of the file, both are considered as one file from the viewpoint of the counter. When one file is divided into a plurality of extents in the AV block, it is considered as one file.

The introduction of the counter brings two advantages in the management of the AV block. The first point is non-AV
That is, it becomes easy to determine whether to release the AV block for data. In the above embodiment, the file system unit 1
In No. 02, when all the sectors included in the AV block for non-AV data are unused in the sector bitmap at the time of file deletion, the AV block is released as an unused one. As described above, in the above embodiment, it is necessary to search the space bitmap to release the AV block. When the counter is recorded in the AV block management table as shown in FIG. 34, the AV block for non-AV data can be released when the counter reaches 0, and the search of the sector bitmap is unnecessary. can do. Of course, it is indispensable to change the sector bitmap for the sector from which data has been deleted.

The second point is A assigned for AV data.
It is to facilitate the coexistence of a plurality of files even in a V block. The coexistence here means that one AV file is divided into separate AV files by editing, not by adding another AV file to an AV block in which the AV file is already written. Also in this case, the counter can manage the existence of a plurality of AV files in the AV block, and the counter can be set to 0.
Then, the AV block can be released.

Furthermore, when considering the coexistence of AV files in an AV block, it is actually sufficient to consider the coexistence of two files. In this way, since at most two AV files coexist in an AV block, it is sufficient to have only a flag indicating whether they coexist, not a counter. In this case, the file system unit 102
As for the release of the AV block for non-AV data, the space bitmap may be checked and the coexistence flag may be used for the release of the AV block for AV data.

The variable length bit in the third configuration example can be provided also in the fourth configuration example. Furthermore, if the data for one AV block in the AV block management table is set to 3 bytes or more, it is possible to have the size of the AV block at the same time. FIG. 35 shows a fifth configuration example of the AV block management table.

In the above embodiment, the AV block at the end of the zone area has a variable length so that the AV block does not cross the zone boundary. Here, it is assumed that all AV blocks have a fixed length of about 7 MB and AV block areas are provided in order from the head of the disc. In this case,
Like the AV block in the shaded area of 5, there is an AV block having a zone boundary inside. Since continuous reproduction cannot be guaranteed even if an AV file is recorded in an AV block having a zone boundary inside, it is necessary to separately manage whether or not there is a zone boundary in the AV block. Therefore, in the fifth configuration example, the AV block management table is provided with a flag indicating whether or not there is a zone boundary in the AV block.
Manage blocks.

In the AV block management table of FIG. 35,
The allocation status and the presence / absence of a zone boundary of 1AV block are represented by 4-bit data. The upper 1 bit in the 4-bit data is a flag indicating whether or not a zone boundary is included in the AV block, and the lower 3 bits indicate the allocation status of the AV block. In this case, the file system unit 10
2 is for assigning AV data to AV blocks,
The AV block including the zone boundary is not allocated alone, and the AV file may be recorded continuously in three AV blocks including the AV block including the zone boundary and adjacent AV blocks before and after the AV block. .
In this way, continuous reproduction can be guaranteed even if an AV file is recorded in an AV block including zone boundaries.

If it is assumed that only a non-AV file can be recorded in an AV block including a zone boundary, 24 AV blocks as many as the zone boundaries are prepared for the non-AV file. The total capacity is 164 MB in total, and the area in which AV files can be recorded is reduced. Therefore, the file system unit 102
At the zone boundary, it is desirable to manage the above three AV blocks collectively.

In the AV block management table shown in FIG. 6, the boundary between AV blocks and the last AV block in the zone area are discontinuous in the sense that they are discontinuous. It may have a flag. By doing this, the file system section 1
When allocating two consecutive AV blocks in 02, it is easy to determine in the AV block management table whether consecutive AV blocks are continuous or divided at zone boundaries.

Further, it is possible to reserve AV blocks for non-AV data in a certain size in advance and reserve them first.
An AV block for V data and an AV block for non-AV data do not coexist, and it becomes easy to secure a continuous area for AV data. Also, it does not maintain compatibility with other file systems and AV file systems, that is, A
If a disc written in the V file system is accessed only by the AV file system, the sectors of all the sectors included in the AV block having the AV attribute are not allocated, and the sector in which the AV data is actually written is written. Only one can be assigned. This gives A
It becomes easy to manage the free area in the V block.

Further, in the above embodiment, with respect to the sectors included in the AV block for AV data, all the sectors are assigned, but only the sectors in which the AV data are actually written are assigned. May be. As a result, the compatibility with other file systems that do not support AV blocks is sacrificed to some extent, but the management of free areas within AV blocks is facilitated. (2) Second Embodiment Hereinafter, an optical disc and an optical disc recording / reproducing apparatus according to the second embodiment will be described. (2-1) Optical disc The optical disc according to the present embodiment is different from the first embodiment in that (1) a point where pseudo continuous recording is provided instead of the AV block according to the first embodiment, and (2) an AV block management table The difference is that pseudo continuous recording allocation information is provided instead of. Hereinafter, the same points as those of the first embodiment will be omitted, and different points will be described.

Regarding point (1), regardless of whether or not AV data is recorded on the optical disc of the first embodiment, AV blocks of substantially fixed length are fixed and preset over the entire data recording area. However, in the present embodiment, there is no fixed AV block on the medium,
When recording AV data, an area called pseudo continuous recording larger than the fixed length is dynamically allocated.

Regarding the point (2), in the optical disc of the first embodiment, the allocation status of all AV blocks is managed by one AV block management table, whereas in the present embodiment, pseudo allocation is performed for each AV file. A pseudo continuous recording allocation table for managing the area allocated as continuous recording is recorded. Therefore, the optical disc in the present embodiment is the same as that in the first embodiment in FIGS. 1 to 3 and FIGS. 8 to 12. Further, in FIG. 4, although there is no fixed AV block in each zone area in the present embodiment, it is divided into a plurality of zones and that an ECC block (16 sectors) is used as a read / write unit. Are the same. The AV block management table shown in FIG. 6 does not exist, but the sector management table (space map) is the same. (2-1-1) Pseudo continuous recording The AV file in this embodiment is composed of one or a plurality of pseudo continuous recordings to guarantee continuous reproduction.
Pseudo-continuous recording is an A of a size equal to or larger than the size for guaranteeing continuous reproduction in continuous sectors (ECC blocks) excluding the skip by the ECC block skip method.
An area in which V data (a portion of AV data) is recorded or recorded AV data.

The ECC block skip system skips the ECC block including the defective sector and skips to the next E when there is a defective sector that causes an address error or the like.
It refers to writing to the CC block. This method is suitable for continuous reproduction of AV data in that there is no jump to the alternative area, as compared with the linear replacement method of writing to the sector in the alternative area that is secured in advance in the same zone.

One pseudo continuous recording is an integer number of ECC
It is assumed that a block is included and the head sector does not straddle a plurality of zones such that the head sector is the head sector of the ECC block. The minimum size of the pseudo continuous recording is 224 ECC blocks (about 7 MB) as in the AV block of the first embodiment in order to guarantee continuous reproduction of AV data.

The result of this allocation is recorded as allocation information together with the AV file. The allocation information is A
Although it may be recorded at the beginning of the V file, in the present embodiment, it is recorded as one non-AV file corresponding to the AV file and has a list structure. (2-1-2) Allocation of Pseudo-Continuous Recording Pseudo-continuous recording allocation management information (hereinafter, simply referred to as allocation information) is assigned to which area on the optical disk one or more pseudo-continuous recordings constituting an AV file are allocated. This is information that indicates whether or not it has been.

In the optical disk recording apparatus, the pseudo continuous recording is allocated to the empty area on the optical disk before recording the AV file. 36A and 36B are diagrams showing a specific example of allocation information corresponding to one AV file and a space bitmap corresponding to the specific example. In the figure, the allocation information is recorded as a table composed of two entries e1 and e2. Each entry consists of a starting sector number (LSN), an ending sector number and an attribute from the left side of FIG. The attribute "0" indicates that the continuous recording is performed, and "1" indicates that the recording area is a free area. In this example, the attribute does not take a value other than "0".

The area of the optical disk from the start sector number to the end sector number in each entry represents a part of the pseudo continuous recording or a sector area to which one pseudo continuous recording is assigned. Here, the relationship between the pseudo continuous recording and the extent managed in the file system will be described. Pseudo continuous recording corresponds to the extent one-to-one when the extent does not cross the zone boundary, but many-to-one when the extent crosses the zone boundary.
Corresponding to. For example, when an extent straddles one zone boundary, two pseudo continuous recordings are made before and after the zone boundary, which corresponds to one extent. (2-1-3) Pseudo-continuous recording allocation management information and space bitmap FIG. 36 (b) is a diagram showing a state of the space bitmap when pseudo-continuous recording is allocated as shown in FIG. is there.

In the space bit map in the figure, the bits corresponding to the sectors (sector numbers 6848 to 34847) allocated to the pseudo AV block #i are set to allocated "0" (allocated). The allocation information and the space bit map, since the unit of management is used to manage the allocation situation of different but both data region, it is desirable to manage in conjunction.

In the optical disk recording apparatus, the area allocated to the pseudo AV block in the allocation information is set to "0" (allocated) in the space bit map. (2-2) Recording / reproducing apparatus Next, an optical disk recording / reproducing apparatus in the second embodiment will be described. (2-2-1) System and Hardware Configuration The system configuration shown in FIG. 14, the hardware configuration of the DVD recorder shown in FIG. 15, the configuration of the MPEG encoder 2 shown in FIG. 16, the MPEG decoder shown in FIG. Four
The configurations of 1 and 2 are the same in this embodiment.

However, compared to the first embodiment, the optical disc is provided with pseudo continuous recording instead of the AV block of the first embodiment, and the point that pseudo continuous recording allocation information is provided instead of the AV block management table. Is different from. Therefore, the programs in the main memory 1d in FIG. 15 are also different. (2-2-2) Functional Block Diagram FIG. 37 is a functional block diagram showing the configuration of the DVD recorder 10 in this embodiment by function. For each function in the figure, the CPU 1a in the control unit 1 has a main memory 1d.
It is realized by controlling the hardware shown in FIG. 14 by executing the program.

In the figure, the same components as those of FIG. 18 in the first embodiment are designated by the same reference numerals. The description of the same components will be omitted, and different points will be mainly described below. The difference is that the file system unit 1 in FIG.
02, recording / editing / playback control unit 105, AV data recording unit 1
Instead of 10, the file system unit 202, the recording / editing / playback control unit 205, and the AV data recording unit 210 are provided.

The file system unit 202 is different in that it has an AV file system unit 203 and a common file system unit 204 instead of the AV file system unit 103 and the common file system unit 104 in the first embodiment. Compared to the AV file system unit 103, the AV file system unit 203 includes the "AV file system unit 203" shown in FIG.
The only difference is that it does not support the "_WRITE" command.

The common file system unit 204 is different from the common file system unit 104 in that AV data is also written by the “WRITE” command.
That is, the file system unit 202 treats AV data and non-AV data as equal without distinguishing them. The AV data recording unit 210, the AV data editing unit 220, and the AV data reproducing unit 2 determine whether the data is AV data or non-AV data.
It will be distinguished at 30.

The AV data recording unit 210, the AV data editing unit 120, and the AV data reproducing unit 130 respectively receive a recording request, an editing request, and a reproducing request from the recording / editing / reproducing control unit 205, and perform the requested recording, editing, and reproducing. The command necessary for the above is issued to the AV file system unit 103. The AV data recording section 210 receives a recording request from the recording / editing / playback control section 105, and sends a command necessary for the requested recording to A
Issued to the V file system unit 103, and at the same time, as shown in FIG.
Create and update the allocation information shown in. More specifically, when the AV data recording unit 210 receives a recording request, the AV data recording unit 210 searches for an unused area by searching the space bitmap and the pseudo continuous recording allocation information, and determines whether the fixed length (about 7 Mbytes) or more. An area is secured and new pseudo continuous recording allocation information is generated. At this time, if the pseudo-continuous recording already exists, a new pseudo-continuous recording area is secured so that the pseudo-continuous recording is recorded in as continuous a region as possible, and the pseudo-continuous recording is performed on the secured area. Create allocation information. (2-3-1) Recording of AV File Next, recording of an AV file in the DVD recorder 10 will be described in detail.

FIG. 38 is a flowchart showing the recording process in the DVD recorder of this embodiment.
When the “record” button is pressed, or when the current time reaches the start time of “recording reservation”, the recording start notification is given via the user IF unit 106.
Done to 5.

The recording / editing / playback control unit 10 receiving this notification
Reference numeral 5 secures a pseudo continuous recording area of a certain size (about 7 Mbytes) or more. That is, referring to the space bitmap and the continuous recording area management file, an area that can be used as a pseudo continuous recording area is secured (step 38).
0). At this time, there is already recorded AV data,
When the AV data to be recorded is logically continuous, a new continuous recording area is secured so as to be continuous with the existing continuous recording area as much as possible.

Further, the recording / editing / playback control unit 105 is
The V data recording unit 210 is notified of the file identifier and the parameter indicating the time priority set in the recording condition. AV
The data recording unit 210 MPEs the video data and audio data of the program of the specific channel being received via the receiver 9.
Encoding is started by the G encoder 2, and further the process of transferring the MPEG data of the encoding result to the track buffer 3a is started (step 381).

Next, the recording / editing / playback control section 105 issues a "CREATE" command including designation of the newly allocated continuous recording area to the common file system section 104 (step 382). In response to this, the common file system unit 104 returns a new file identification descriptor when a file can be created in a new continuous recording area.

Further, the AV data recording section 210 displays "OP
By issuing the "EN" command to the AV file system unit 103 (step 383), information about the file identification descriptor and its file entry given from the recording / editing / playback control unit 105 is held in the work memory (not shown). (Hereinafter, the above information in the work memory is abbreviated as Fd (file descriptor)).

Until the AV data recording section 210 receives a stop command from the recording / editing / playback control section 105 (step 384: yes), a predetermined amount of M is stored in the track buffer 3a.
Each time PEG data is accumulated, a "WRITE" command is issued
Issued to the V file system unit 103 (step 38)
5, 386). Here, it is assumed that the “WRITE” command is issued to the AV file system unit 103 together with the designation of three parameters. The three parameters are "OPEN"
The Fd opened by the command, the size of the data to be recorded, and the buffer holding it (the track buffer 3a in this embodiment).

Here, Fd designated as a parameter
Like the file entry, contains information indicating the recording position of the extent and the extent length. This information specifies the pseudo continuous recording area secured in step 380. Further, when a plurality of "WRITE" commands are issued from the time Fd is opened to the time Fd is closed, it is sequentially updated. In the second and subsequent “WRITE” commands, new data is added after the already recorded data.

The AV data recording section 210 receives the "WRITE" command (steps 384, 38) at the time of receiving the stop command.
7), and further issues a “CLOSE” command (step 388) to notify the AV file management information generation unit 112 that the recording of the AV file (VOB) is completed (step 389). After this, the AV data recording unit 21
0 refers to the Fd (extent) of the recorded AV data to create or update the pseudo continuous recording allocation information. That is, when a new AV file is recorded, quasi-continuous recording allocation management information is created and additionally AV information is recorded.
When the file is recorded, the pseudo continuous recording allocation management information is updated, and at the same time, the space bitmap is updated (step 390). The updated or created pseudo continuous recording allocation management information is recorded as a non-AV file via the common file system unit 204.

The "WRITE" command in step 387 is for recording the data left in the track buffer. The "CLOSE" command of step 388 is for the Fd in the work memory to be written back by the file identification descriptor and file entry on the DVD-RAM.
As described above, the DVD recorder according to the present embodiment dynamically reserves and allocates the pseudo continuous recording area by referring to the space bitmap and the allocation information when recording the AV data. Therefore, the first
Compared with the DVD recorder in the embodiment, since there is no logical partition on the medium called an AV block, the data area on the optical disc can be used more effectively. (3) Third Embodiment An optical disc and a DVD recorder according to this embodiment are
Compared to the second embodiment, (1) the minimum size of the pseudo continuous recording can be dynamically changed, and (2) the pseudo continuous recording allocation management information is not included. The differences from the second embodiment will be mainly described below.

Regarding the point (1), in the second embodiment, the fixed size that guarantees continuous reproduction is fixedly treated as about 7 Mbytes, but in the present embodiment, the bit rate of the video object actually encoded is set. The DVD recorder 10 is configured so that the minimum size of the pseudo continuous recording can be determined according to the above. Regarding the point (2), the DVD recorder 10 does not record the allocation management information on the optical disk, but searches the empty area from the space bitmap every time recording and secures an area that can be allocated as pseudo continuous recording. Is configured. (3-1) Minimum Size of Pseudo Continuous Recording Area First, the theoretical basis for determining the minimum size for guaranteeing continuous reproduction in (1) above will be described.

FIG. 39 shows an AV read from a DVD-RAM in a reproducing device for reproducing a video object.
FIG. 6 is a modeled view of how data is buffered in a track buffer. This model is a model that defines the minimum specifications that should be provided as a playback device, and continuous playback can be guaranteed as long as this specification is satisfied.

In the upper part of FIG. 39, the AV data read from the DVD-RAM is subjected to ECC processing, temporarily stored in the track buffer (FIFO memory), and further output from the track buffer to the decoder. Let Vr be the transfer rate of the track buffer input (readout rate from the optical disk), and Vo be the transfer rate of the track buffer output (decoder input rate) (provided that Vr> Vo).
In this model, Vr = 11Mbps.

The lower part of FIG. 39 is a graph showing changes in the data amount of the track buffer in this model. The vertical axis represents the amount of data in the track buffer, and the horizontal axis represents time. In the figure, it is assumed that the pseudo continuous recording #j having no defective sector and the pseudo continuous recording #k having a defective sector are sequentially read. The period T1 on the time axis is the time required to read all the AV data from the beginning to the end of the pseudo continuous recording #j that does not include a defective sector. During this period, the amount of data in the buffer increases at the rate of (Vr-Vo).

The period T2 (hereinafter referred to as the jump period) is
This is the time required for the optical pickup to jump from the pseudo continuous recording #j to the pseudo continuous recording #k. Jump time includes a seek time of the optical pickup, the time required for <br/> rotation of the optical disc to stabilize. This time is the maximum jump time from the innermost circumference to the outermost circumference, and is about 1500 mS in this model. In this period,
The amount of data in the buffer decreases at the rate of Vo.

The periods T3 to T5 are the time required to read all the AV data from the beginning to the end of the pseudo continuous recording #k including the defective sector. In the period T4, the Ecc block including the defective sector is skipped and the next Ec block is skipped.
It is time to skip to block c. This skip means that if there is even one defective sector in the Ecc block, the Ecc block (16 sectors) is skipped and the next Ecc block is jumped to. That is, the Ecc block in which the defective sector exists in the pseudo continuous recording does not mean that the defective sector is logically replaced with the alternative sector (alternative Ecc block), and that the Ecc block (all 16 sectors) is simply not used. (ECC block skip method above). This time T4 is the rotation waiting time when the disk makes one rotation at maximum, and is about 105 mS in this model. In the periods T3 and T5, the amount of data in the buffer increases at the rate of (Vr-Vo), but the period T4
Then the rate of Vo will decrease.

The size of the pseudo continuous recording is N, where N_ecc is the number of all Ecc blocks included in the pseudo continuous recording.
It is expressed as _ecc * 16 * 8 * 2048 bits. The lower limit value of N_ecc for guaranteeing continuous reproduction can be derived as follows. In the period T2, only AV data is read from the track buffer. If the buffer capacity becomes 0 within this period, an underflow will occur in the decoder. In this case, continuous reproduction of AV data cannot be guaranteed. Therefore, in order to guarantee continuous reproduction (to prevent underflow), the following formula must be satisfied.

[0157]

[Equation 6] The buffer storage amount B is the amount of data stored in the track buffer at the end of the period T1. The consumption amount R is the total amount of data read during the period T2. > = Means greater than or equal to. The accumulated amount B can be expressed by the following equation.

[0158]

[Equation 7] The consumption amount R can be expressed by the following equation.

[0159]

[Equation 8] Replacing both sides of the above (Equation 6) with (Equation 7) and (Equation 8) gives the following equation.

[0160]

[Equation 9] From this formula, the number of Ecc blocks N_ecc for guaranteeing continuous reproduction must satisfy the following formula.

[0161]

[Equation 10] In this equation, Tj is the above jump time, which is a maximum of 1.5 seconds. Vr is a fixed value (about 11 Mbps in the reproducing device model shown in the upper part of FIG. 39). Also, Vo is
Considering that the video object has a variable bit rate, it is expressed by Expression 11. That is, Vo is not the maximum physical transfer rate of the output of the track buffer, but is obtained as the substantial input rate of the variable bit rate AV data of the decoder by Expression 11. However, regarding the pseudo continuous recording length, the number of packs during pseudo continuous recording composed of N_ecc Ecc blocks is N_pack.

[0162]

[Equation 11] Here, SCR_first_next is the SCR of the first pack of the next pseudo continuous recording, and SCR_first_current is the SCR of the first pack of the pseudo continuous recording. The SCR indicates the time when the pack should be output from the track buffer to the decoder, and has a unit of (1 / 27M) sec.

As shown in (Equation 10) and (Equation 11), the minimum size of the pseudo continuous recording can be theoretically calculated according to the bit rate of the AV data actually recorded. Further, the above expression 10 is valid when there is no defective sector on the optical disk, but the number of Ecc blocks N_ecc for guaranteeing continuous reproduction when there is a defective sector will be described.

Defective sectors are included in the pseudo continuous recording area.
It is assumed that there are dN_ecc ECC blocks. This dN_
AV data is not recorded in the ecc ECC blocks due to the ECC block skip. Loss time Ts due to skipping dN_ecc ECC blocks is T4 * d
It is expressed as N_ecc (T4 is the ECC block skip time in the model of FIG. 39).

When these are added to the equation 10, in order to guarantee continuous reproduction even when there is a defective sector, a continuous area of the ECC block number N_ecc that satisfies the following expression may be set as a pseudo continuous recording area. .

[0166]

[Equation 12] As described above, the size of the pseudo continuous recording area may be set to satisfy the formula 10 when the defective sector does not exist and to satisfy the formula 12 when the defective sector exists. However, when one continuous AV data is composed of a plurality of pseudo continuous recordings, not all pseudo continuous recordings need to satisfy the expression 10 or the expression 12, and the pseudo continuous recordings at the beginning and the end are expressed by the expression 10s. Alternatively, the number 12 may not be satisfied. Because
This is because the trailing pseudo-continuous recording has no succeeding AV data, and the leading pseudo-continuous recording delays the decoding start timing, that is, starts supplying data to the decoder when the data is accumulated in the track buffer. By doing so, continuous reproduction can be guaranteed between the beginning and the next pseudo continuous recording. (3-2) Recording of AV File Next, recording of an AV file in the DVD recorder 10 will be described in detail.

FIG. 40 is a flow chart showing the recording process in the DVD recorder of this embodiment. 38 is different from FIG. 38 in that step 400 is provided instead of step 380 and step 390 is deleted. The other points are the same as those in FIG. 38, and therefore the following description will be focused on the different points. When the “record” button is pressed, or when the current time reaches the start time of “record reservation”, the user IF unit 10 is notified of the start of recording.
6 to the recording / editing / playback control unit 105.

The recording / editing / playback control unit 10 which has received this notification
Step 5 secures a pseudo continuous recording area having a size equal to or larger than the minimum size (step 400). That is, the recording / editing / playback control unit 105 calculates the actual bit rate of the video object in accordance with (Equation 10) and (Equation 11). However,
For convenience, the size may be a predetermined size that satisfies the above minimum size. Furthermore, referring to the space bitmap and each allocation descriptor of the file management area, the free area on the optical disk is searched, the free space list is created, and the determined minimum size is exceeded in the created free space list. The area is secured as pseudo continuous recording. At this time, the area where the zone boundary exists is treated as two different empty areas before and after the zone boundary.

FIG. 41 shows an example of the free space list. In the figure, the head sector represents the head sector number of the free area, and the tail sector represents the tail sector number of the free area. The attribute indicates that it is a free area. In this example, when the determined minimum size is about 7 Mbytes (3500 sectors), the free area C1 is smaller than this and the free areas C2 and C3 are larger than this. In this case, the recording / editing / playback control unit 105 secures the empty areas C2 and C3 as pseudo continuous recording.

The subsequent recording process is the same as that shown in FIG. However, when recording, the AV data recording section 210 sequentially records from the empty area on the inner circumference side of the optical disc in the free space list. Also, the free space list is not recorded on the optical disc. FIG. 42 shows
41 is a flowchart showing a specific example of a process of ensuring a pseudo continuous recording area in step 400 in FIG. 40.

The recording / editing / playback control section 105 searches for an empty area on the optical disk by referring to the space bitmap and each allocation descriptor of the file management area (step 421). At this time, the recording / editing / playback control unit 105
Is a small free area for AV data (for example, the number 1
00 kbytes) may be ignored. According to the search result, the recording / editing / playback control unit 105 creates the free space list (step 422). At this time, the vacant area crossing the zone boundary is treated as two different vacant areas before and after the zone boundary. The recording / editing / playback control unit 105 determines whether or not a zone boundary exists in the empty area by inquiring of the AV file system unit 103 (“SEARCH_DISCON” in FIG. 21). The position of the zone boundary on the optical disc is fixed in advance and stored and managed by the AV file system unit 103.

Further, the recording / editing / playback control unit 105 determines the minimum size required for the pseudo continuous recording according to the above (Equation 10) and (Equation 11). However, if there is a defective sector, it is determined according to (Equation 12) and (Equation 11) (step 423). In order to simplify this determination, the AV data bit rate predetermined according to the image quality (for example, “high image quality”, “standard”, and “time priority” shown in FIG. 24) and the expected defective sector ratio are set. , The minimum size may be determined based on the margin.

Next, the recording / editing / playback control unit 105 secures an empty area having a size equal to or larger than the determined minimum size as the pseudo continuous recording, and further determines the recording order. This order is determined, for example, so that the empty area secured so as to reduce the seek operation is from the inner circumference side to the outer circumference side.
As described above, the DVD recorder according to the present embodiment refers to the space bitmap and the file allocation descriptor when recording AV data,
Dynamically secure the area for pseudo continuous recording. Therefore, the second
Compared with the DVD recorder in the embodiment, the pseudo continuous recording area can be dynamically allocated during recording without recording the pseudo continuous recording allocation information.

In the third embodiment, the free space list is constructed so that it is created every time a video is recorded. However, the DVD recorder creates and records the free space when the optical disk is loaded in the optical disk drive device. It may be configured to update each time. Further, the DVD recorder may be configured to record the above free space list on the optical disc after it is created, refer to the recorded free space list before recording, and update it after recording.

[0175]

According to the present invention record apparatus of the present invention is, to guarantee continuous playback
AV files and non-AV files that do not require the guarantee
A recording device for recording the optical disc onto an optical disc.
The recording area of the disk is N_sec consecutive S_size byte sectors.
It is divided into multiple blocks with the continuous area as a block.
Data allocation status of each sector on the optical disk
Sector information indicating the sector is recorded.
Read means for reading information from the optical disc and recording
If the desired file is an AV file, the read
The AV information for the playback device
The specified size that can guarantee continuous playback of files.
And a search means for searching a continuous free area of
Write the AV file by dividing it into two or more continuous free areas.
It has a writing means for writing, and the predetermined size is Vo
The output transfer rate of the track buffer in the playback device,
When Tj is the maximum jump of the optical pickup in the playback device
During this period, Vr was set as the input transfer rate of the track buffer.
Sometimes, N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr)) is the size corresponding to the number N of the blocks.
It is configured to that.

[0176] According to the configured record apparatus in this way,
Prior to recording an AV file on an optical disc, a continuous free space of a predetermined size or more is searched for, so the AV file is
The files are recorded in consecutive sectors of a predetermined size or larger. The so predetermined size even interrupted play in any reproduction apparatus is defined so as to prevent, recorded AV file by the Symbol recording apparatus (not drop frames) without interruption video and audio in any reproducing apparatus Ru can be assured of continuous playback.

[0177]

[0178]

[0179]

Here, the recording device is further provided with the writing device.
Management showing the area where the AV file is written
Equipped with means to create information and write it to the optical disc
You may stay.

According to this structure, since the management information is recorded on the optical disk, it is possible to easily search the empty area at a higher speed. In addition, the computer-readable storage medium according to the present invention should be an AV that guarantees continuous playback.
Files and non-AV files for which the guarantee is not required are
The computer that recorded the program for recording on the disk.
A readable recording medium, the optical disc
In the recording area of, N_sec consecutive S_size byte sectors
Divided into multiple blocks with the area
The optical disk shows the data allocation status of each sector.
Sector information is recorded, and the program stores the optical disc.
Read step to read sector information from disk
If the file to be recorded is an AV file, it will be read.
By referring to the sector information
Predetermined that can guarantee continuous playback of AV files
Search step and search
Divide the AV file into two or more continuous free areas found
Write and perform writing steps on your computer
The above-mentioned predetermined size allows Vo to be tracked in the playback device.
Output buffer transfer rate, Tj
Pickup maximum jump time, Vr
When the input transfer rate of the buffer is N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr)) , the size corresponding to the number N of the blocks is expressed.
It is characterized by that.

[0182] According to this record medium, in the computer, by operating the program, AV file
The file can be recorded in a continuous area having a size equal to or larger than the predetermined size. As a result, Ru can guarantee a continuous playback of the AV file.

[0183]

[0184]

[0185]

Further, the recording device or
If a computer-readable recording medium records, it guarantees continuous playback of video data when video data and other data coexist, and efficiently stores both video data and other data. be able to.

[0187]

[0188]

[0189]

[0190]

[0191]

[0192]

[0193]

[0194]

[0195]

[0196]

[0197]

[Brief description of drawings]

FIG. 1 is a diagram showing an appearance and a recording area of a DVD-RAM disc which is a recordable optical disc according to an embodiment of the present invention.

FIG. 2 DVD-R cut out by expanding to a sector level
It is a figure which shows the cross section and surface of AM.

FIG. 3 (a) Zone area 0 to 0 in DVD-RAM
23 is a diagram showing other components. (B) It is explanatory drawing which arrange | positioned zone area 0-23 etc. in the horizontal direction. (C) Logical sector number in the volume space (LS
It is a figure which shows N). (D) Logical block number in the volume space (LB
It is a figure which shows N).

FIG. 4 is a diagram showing a hierarchical relationship between AV blocks and sectors in a zone area.

FIG. 5 is a diagram showing a final block length table.

FIG. 6 is a diagram showing a sector management table and an AV block management table of file system management information recorded in a volume space.

FIG. 7 is a diagram showing a relationship between the AV block management table and a space bitmap.

FIG. 8 is a diagram for explaining information other than the sector management table and AV block management table in FIG. 6 among the file system management information.

9 is a diagram showing a hierarchical directory structure corresponding to the management information shown in FIG.

FIG. 10 is a diagram showing a link relationship shown by arrows in FIG. 6 along a directory structure.

FIG. 11A is a diagram showing a more detailed data structure of a file entry. (B) It is a figure which shows the data structure of an allocation descriptor. FIG. 6C is a diagram showing a recording state of upper 2 bits of data indicating an extent length.

FIG. 12A is a diagram showing a detailed data structure of a directory file identification descriptor. (B) It is a figure which shows the detailed data structure of the file identification descriptor for files.

FIG. 13 is a modeled view of buffering AV data read from a DVD-RAM in the playback device.

FIG. 14 is a diagram showing a configuration example of a system using the optical disc recording / reproducing apparatus in the present embodiment.

FIG. 15 is a block diagram showing a hardware configuration of the DVD recorder 10.

16 is a block diagram showing the structure of an MPEG encoder 2. FIG.

FIG. 17 is a block diagram showing a configuration of an MPEG decoder 4.

FIG. 18 is a functional block diagram showing the configuration of the DVD recorder 10 by function.

FIG. 19 is a diagram showing how an AV block management table and space bitmap change when writing AV data.

FIG. 20 is a diagram showing how an AV block management table and space bitmap change when AV data is deleted.

21 is a diagram showing a list showing commands relating to file management by the file system unit 102. FIG.

22 is a diagram showing an example of a button arrangement of the remote controller 6. FIG.

FIG. 23 is a diagram showing a guidance image.

[Fig. 24] Fig. 24 is a diagram illustrating bit rates and resolutions of high image quality, standard, and time priority.

FIG. 25 is a flowchart showing the processing contents of the AV file system unit 103 during manual recording in the DVD recorder 10.

FIG. 26 is a flowchart showing the processing contents of the AV file system unit 103 in reserved recording in the DVD recorder 10.

FIG. 27 is a flowchart showing a deletion process for an AV file by the common file system unit 104.

FIG. 28 (a) is an explanatory diagram of an AV file before and after deletion. (B) It is a figure which shows the change of an AV block management table and a space bit map.

FIG. 29 shows a non-AV by the common file system unit 104.
It is a flowchart which shows the recording process of a file.

FIG. 30 shows a non-AV by the common file system unit 104.
It is a flowchart which shows the deletion process about a file.

FIG. 31A is an explanatory diagram of a non-AV file before and after deletion. (B) It is a figure which shows the change of an AV block management table and a space bit map.

FIG. 32 is a diagram showing a second configuration example of an AV block management table.

FIG. 33 is a diagram showing a third configuration example of an AV block management table.

FIG. 34 is a diagram showing a fourth configuration example of an AV block management table.

FIG. 35 is a diagram showing a fifth configuration example of an AV block management table.

FIG. 36 (a) is a diagram showing a specific example of allocation information corresponding to one AV file and a space bitmap corresponding to it. (B) is a diagram showing a state of the space bit map when the pseudo continuous recording is assigned as shown in (a) of FIG.

FIG. 37 is a functional block diagram showing the structure of the DVD recorder according to the second embodiment for each function.

FIG. 38 is a flowchart showing a recording process in the AV data recording unit.

FIG. 39 is a diagram showing a playback device model.

FIG. 40 is a flowchart showing a recording process in the DVD recorder of the third embodiment.

FIG. 41 is a diagram showing a free space list.

42 is a flowchart showing a specific example of a process of ensuring a pseudo continuous recording area in step 400 in FIG.

[Explanation of symbols]

1 control unit 1a CPU 1b Processor bus 1c bus interface 1d main memory 2 MPEG encoder 2a video encoder 2b video buffer 2c audio encoder 2d audio buffer 2e system encoder 2f part 2g encoder control unit 3 Disk access section 3a track buffer 4 MPEG decoder 4a Demultiplexer 4b video buffer 4c video decoder 4d audio buffer 4e audio decoder 4f part 4g adder 4h-4j selector 5 Video signal processor 6 remote control 7 buses 8 Remote control signal receiver 9 receiver 10 DVD recorder 12 display 100 disc recording section 101 copies 102 File System Department 103 AV file system section 104 Common File System Department 105 Recording / editing / playback control unit 106 user IF section 110 AV data recorder 112 AV File Management Information Generation Unit 120 AV data editor 130 AV data playback unit 202 File System Department 203 AV file system section 204 Common File System Department 205 Recording / Editing / Playback Control Unit 210 AV data recorder 220 AV data editor 230 AV data playback unit

─────────────────────────────────────────────────── ─── Continued front page (72) Inventor Hiroshi Kato 1006 Kadoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. (72) Tomoyuki Okada 1006 Kadoma, Kadoma City, Osaka Matsushita Electric Industrial Co., Ltd. (72) Inventor Kaoru Murase 1006 Kadoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. (56) Reference JP 10-320923 (JP, A) JP 9-163300 (JP, A) JP-A-11-144383 (JP, A) JP-A-63-104284 (JP, A) International publication 99/13469 (WO, A1) International publication 97/13366 (WO, A1) (58) Fields investigated (Int .Cl. ⁷ , DB name) H04N 5 / 85,5 / 91-5/956 G11B 20 / 10,20 / 12

Claims (6)

(57) [Claims] 1. An AV file for which continuous playback is guaranteed, and
And a recording device for recording a non-AV file that does not require the guarantee onto an optical disc, wherein the recording area of the optical disc has a sector of S_size bytes.
Divided into a plurality of blocks having N_sec continuous areas as blocks, sector information indicating a data allocation state of each sector is recorded on the optical disc, and the recording device includes a reading unit that reads the sector information from the optical disc. When the file to be recorded is an AV file, by referring to the read sector information, a continuous free area of a predetermined size or more that can guarantee continuous playback of the AV file to the playback device is searched. And a writing means for writing the AV file by dividing the AV file into two or more continuous free areas searched for. With the predetermined size, the Vo is transferred to the output buffer of the track buffer in the reproducing apparatus, and Tj is reproduced. When the maximum jump time of the optical pickup in the device, Vr, is the input transfer rate of the track buffer, In represented by the number N
A recording device having a size corresponding to the above block. N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr)) 2. The recording apparatus according to claim 1, further comprising a unit that creates management information indicating an area in which the AV file is written by the writing unit and writes the management information on the optical disc. 3. An AV file for which continuous playback is guaranteed, and
And a recording method for recording a non-AV file that does not require the guarantee on an optical disc, wherein the recording area of the optical disc has a sector of S_size bytes.
The optical disc is divided into a plurality of blocks having N_sec consecutive areas as blocks, sector information indicating a data allocation state of each sector is recorded on the optical disc, and the recording method includes a reading step of reading sector information from the optical disc. , If the file to be recorded is an AV file, by referring to the read sector information, a continuous free space of a predetermined size or more that can guarantee continuous playback of the AV file to the playback device is created. It includes a searching step of searching and a writing step of writing an AV file by dividing it into two or more continuous free areas searched for, and the predetermined size is Vo, which is an output transfer rate of a track buffer in the playback device, Tj. The maximum jump time of the optical pickup in the playback device, Vr is the input transfer rate of the track buffer When the number is expressed by the following equation N
The recording method has a size corresponding to the block. N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr)) 4. The recording method according to claim 3, wherein the recording method further includes a step of creating management information indicating an area in which the AV file is written by the writing step and writing the management information on the optical disc. 5. An AV file for which continuous playback is guaranteed, and
And a computer-readable recording medium recording a program for recording a non-AV file that does not require the guarantee on an optical disc, wherein the recording area of the optical disc has a sector of S_size bytes.
Divided into a plurality of blocks having N_sec continuous areas as blocks, sector information indicating a data allocation state of each sector is recorded on the optical disc, and the program reads out sector information from the optical disc, When the file to be recorded is an AV file, by referring to the read sector information, a continuous free area of a predetermined size or more that can guarantee continuous playback of the AV file to the playback device is searched. And a write step of writing the AV file by dividing it into two or more continuous free areas that have been searched, the predetermined size is defined as Vo, the output transfer rate of the track buffer in the playback device, Tj is the maximum jump time of the optical pickup in the playback device, and Vr is the trackback When the § input transfer rate, the number is expressed by the following equation N
A recording medium having a size corresponding to the above block. N = Vo * Tj / ((N_sec * 8 * S_size) * (1-Vo / Vr)) 6. The recording according to claim 5, wherein the program further causes the computer to execute the step of creating management information indicating an area in which the AV file is written in the writing step and writing the management information in the optical disc. Medium.