Av data recording apparatus and method, and disk recorded by the same

The present invention relates to an AV data recording device and a method thereof suitable for recording / reproducing AV data such as digital images.

In recent years, due to the high density of optical discs, the use of optical discs as a recording medium for digital images including moving images has been advancing. Its application range is wide, and it is expected to be used not only as a peripheral device for computers but also as a video player for home use, and in the future as a recording medium for recording instead of a tape medium.

In such a wide range of application fields, in order to handle data in common, it is common practice to manage data in logical units called files. As one of such file management methods, there is a file system using a format based on the UDF (Universal Disk Format) standard.

The UDF standard is stipulated to ensure media compatibility between various computer operating systems (OS), and is also adopted in DVD-Video players, which are consumer devices. And support on a wider range of platforms is expected in the future.

The configuration of a file system (hereinafter referred to as "UDF file system") using the UDF standard will be described below with reference to the drawings. Figure 35 shows a configuration example of a data recording / playback device to which a conventional AV data recording method is applied.

In FIG. 35, 101 indicates a disk such as an optical magnetic disk, 102 indicates a recording medium driving unit, and for example, when the disk 101 is a magneto-optical disk, the recording medium driving unit 102 is composed of a spindle motor or the like.

Further, 103 indicates a recording / reproducing unit. For example, when the disk 101 is a magneto-optical disk, it is composed of an optical pickup, a magnetic head, a servo circuit, a modulation / demodulation circuit, and the like. Reference numeral 104 denotes a memory unit, which temporarily stores data during data recording and reproduction. Reference numeral 105 denotes a disk drive unit, which is composed of a disk 101, a recording medium drive unit 102, a recording / playback unit 103, and a memory unit 104.

Reference numeral 106 denotes an AV signal processing unit, which performs processing such as MPEG compression on the AV input signal input from a CCD camera or the like, or processing such as MPEG decoding on the AV data read from the disk 101. Output to a monitor, etc.

Further, 107 indicates a system control unit, and controls the AV signal processing unit 106 and the disk drive unit 105.

In the data recording / playback device configured in this way, at the time of data recording, the AV signal input to the AV signal processing unit 106 is subject to the control of the system control unit 107 after performing image compression processing such as the MPEG method. , Transferred to the memory unit 104.

Next, the system control unit 107 operates the recording medium drive unit 102 and the recording / playback unit 103 to record the data on the memory unit 104 on the disk 101.

At the time of data reproduction, the system control unit 107 operates the recording medium driving unit 102 and the recording / reproducing unit 103, and the data recorded on the disk 101 is transferred to the memory unit 104.

Next, under the control of the system control unit 107, data is read from the memory unit 104 and output as an AV signal from the AV signal processing unit 106.

Next, a configuration example of the UDF file system, which is a conventional file management method, will be described with reference to the drawings. FIG. 36 is a structural diagram of the UDF configured on the disk 101 in the volume space.

In FIG. 36, in order to treat the disk 101 as a logical volume, the disk 101 is divided into units called sectors, and the logical sector numbers from 0 (zero) to the last logical sector (Last LSN) for that sector. (LSN) is assigned. In addition, the volume structure is recorded at the beginning and end portions in the volume space. Further, a partition space for recording the file structure information and user data files is allocated between these volume structures.

In the partition space, the logical block number (LBN) is assigned in the range from 0 (zero) to the final logical block number (Last LBN) in sector units from the first sector. FIG. 37 is a structural diagram in the partition space when the directory structure shown in FIG. 38 is recorded on the disk 101.

In FIG. 38, the directory DIR1 exists under the ROOT directory, and FILE1_1 and FILE1_2 exist under the directory DIR1. At this time, in FIG. 37, the space bitmap descriptor is recorded at LBN = 0 to 79.

The space bitmap descriptor has a space bitmap indicating whether or not each logical block can be assigned. Each bit of the space bitmap corresponds to each logical block, and when this bit value is '1', the logical block is in the unallocated state, and when it is '0' (zero), it is in the allocated state. Means.

A File Set Descriptor is recorded at LBN = 80. The file set descriptor records the location information of the file entry in the root directory. File entries will be described in detail later.

The termination descriptor is recorded in LBN = 81. The termination descriptor represents the termination of the fileset descriptor column.

The file entry of the root directory is recorded in LBN = 82. A file entry is used to store various attribute information unique to each file, information on the recording position of the file, information on the size of the file, etc., and manage the file as a group of extents. Extents will be described in detail later.

Figure 39 shows an example of a file entry configuration. In the descriptor tag field, information for discriminating various descriptors such as a space bitmap descriptor, a file set descriptor, and a file entry is recorded in the partition space. In the case of a file entry, the value 261 is specified to be described. Attribute information about the file entry itself is recorded in the ICB (Information Control Block) tag field. The extended attribute field is used to describe attribute information other than the content specified in the attribute information field in the file entry. In the allocation descriptor field, the required number of allocation descriptors that manage the area of consecutive logical blocks as one extent are recorded.

Figure 40 shows the structure of the allocation descriptor. In the allocation descriptor, extents are indicated by extent length and extent position.

Figure 41 shows the interpretation of the upper two bits of the extent length contained in the allocation descriptor. The value of the upper 2 bits indicates the allocation state and recording state of the extent. If the value is '0' (zero), it is an allocated and recorded extent and the data in the file is recorded. If the value is '1', it is an allocated and unrecorded extent, and the area is allocated to a specific file / directory but no data is recorded. If the value is '2', it is an unassigned and unrecorded extent and no data has been recorded. If the value is '3', it is a continuation extent of the allocation descriptor. Multiple allocation descriptors can be recorded in the allocation descriptor field in the file entry, and one file is composed of a collection of extents managed by those allocation descriptors. The extents that make up this file are called the main data stream and store user data.

In the directory, the file name of the file contained in the directory and the location information of the file entry are recorded. In UDF, directories are also a type of file, which is recorded at LBN = 83 and LBN = 85 in Figure 37.

Figure 42 shows an example of the configuration of the directory file recorded at LBN = 85. A directory file is composed of a plurality of file identification descriptors, and each file identification descriptor has information about each file contained in the directory. The main information that each file identification descriptor has is the file name of the file it corresponds to and the location information of its file entry. Figure 43 shows an example of the logical structure of directories / files in file management information according to the UDF standard.

In FIG. 43, the fileset descriptor is recorded at a predetermined location in the partition space as part of the file management information. The file set descriptor stores the recording position of the file entry for the ROOT directory file. The file identification descriptor in the ROOT directory file stores the recording location of the file entry in directory DIR1. There are multiple file identification descriptors in the file in the directory DIR1, which stores the file names of FILE1_1 and FILE1_2 and the recording position of the file entry, respectively.

Further, in UDF, it is possible to use an extended file entry instead of the file entry. Figure 44 shows a configuration example of an extended file entry. The UDF standard stipulates that the value '266' is described in the descriptor tag field of the extended file entry.

The extended file entry differs from the file entry in that it has a Stream Directory ICB field. The stream directory ICB stores the location information of file entries for describing a special directory called a stream directory.

Figure 45 shows an example of a stream directory configuration. A stream directory is also a type of directory file, and like a general directory file, it is composed of a plurality of file identification descriptors.

However, the file identification descriptor in the stream directory differs from a general directory file in that it is associated with a special file called a named data stream.

Also, in the stream directory, the main data stream is pointed to as the parent entry instead of the parent directory.

The named data stream also constitutes one data stream by the collection of extents managed by the allocation descriptor in the extended file entry.

Therefore, the file managed by the extended file entry will consist of one main data stream and zero or more named data streams.

Figure 46 shows an example of the directory / file logic structure when extended file entries are used according to the UDF standard. In FIG. 46, the relationship between the file set descriptor, the ROOT directory, the directory DIR1, and the files FILE1_1 and FILE1_2 is the same as in FIG. 43. However, in FIG. 46, the extended file entry is used instead of the file entry.

In FIG. 46, the stream directory ICB field of the extended file entry stores the recording position of the file entry in the stream directory.

There are multiple file identification descriptors in the file in the stream directory, which store the names of named_stream_1 and named_stream_2 and the recording location of the extended file entry, respectively.

In FIG. 46, the directory DIR1 constitutes one file by a directory file which is a main data stream and three data streams of named_stream_1 and named_stream_2 which are named data streams.

The operation of the data recording / playback device reading a desired file from the disk having the structure of the UDF file system described above will be described below.

In the case of having a hierarchical structure as shown in FIG. 43, the operation when trying to acquire the recording position of the target file will be described. Here, it is assumed that the file FILE1_1 is the target file.

First, read the contents of the ROOT directory file. That is, it looks at the fileset descriptor and gets the location of the file entry in the ROOT directory from it. Then, the allocation descriptor is read from the file entry, the position and length of the extent of the ROOT directory file are obtained, and the data of the ROOT directory file is read. By scanning the information in the obtained ROOT directory file, a file identification descriptor that matches the target directory name DIR1 can be detected.

Next, read the contents of the target directory file. That is, when a file identification descriptor that matches the target directory is detected, the location information of the file entry is obtained from the contents of the file identification descriptor, and the file entry is read out. The allocation descriptor is read from the file entry related to such a directory, the position and length of the extent recorded therein are obtained, and the data in the directory file is read.

Finally, in order to read the target file, the data of the file in the read directory DIR1 is scanned, and the file identification descriptor that matches the target file name FILE1_1 is detected. When a file identification descriptor that matches the target directory is found, the location information of the file entry is obtained from the file identification descriptor and the file entry is read out. Then, the allocation descriptor is read from the file entry, the position and length of the extent recorded therein are obtained, and the data of the target file FILE1_1 is read.

Next, the operation of the data recording device recording data on a disk having a UDF file system structure will be described. Here, the case where FILE1_3 is further recorded under the directory DIR1 will be described for the disk having the partition space shown in FIG. 37.

First, the space bitmap is scanned to obtain an unallocated logical block whose bits are '1'. Record the data of FILE1_3 as an extent for the unallocated logical block. When the extent recording is complete, record a file entry pointing to FILE1_3 for the unallocated logical block.

At this time, the required number of extent position information and extent length representing FILE1_3 are recorded in the file entry as the allocation descriptor. Record the file identification descriptor pointing to FILE1_3 in the file in directory DIR1, which is the parent directory of FILE1_3.

The file name of FILE1_3 and the location information of the file entry are recorded in this file identification descriptor. The bit in the space bitmap corresponding to the sector allocated by the above process is set to '0' (zero), and the allocated state is set.

As a result of the above processing, the logical volume space is as shown in FIG. 47. The order of processing the file management information is not particularly limited to the above example, and may be performed in another order.

The operation of reading a desired named data stream from a disk having a UDF file system structure will be described below. Here, in the case of having the hierarchical structure as shown in FIG. 46, the operation when trying to acquire the recording position of the target named data stream will be described. In FIG. 46, it is assumed that named_stream_1 is the target data stream.

The operation of reading the file entry of the directory DIR1 which is the parent entry of the named data stream named_stream_1 is as described above.

Read the stream directory ICB from the extension file entry in directory DIR1 and get the extension file entry for the stream directory recorded there.

Then, the allocation descriptor is read from this extended file entry to obtain the position and length of the extent of the stream directory, and the data of the stream directory file is read.

By scanning the information in the obtained stream directory, it is possible to find a file identification descriptor that matches the name named_stream_1 of the target named data stream.

The position information of the extended file entry is obtained from the contents of this file identification descriptor, and the extended file entry is read out.

The allocation descriptor is read from the extended file entry related to the named data stream, the position and length of the extent recorded therein are obtained, and the data of the target named data stream named_stream_1 is read.

Recording a named data stream is done in the same way as recording a file. The difference is that the file identification descriptor, which stores the recording location of the extended file entry for the named data stream, is recorded in the directory file of the stream directory.

The order of processing for the named data stream is not particularly limited to the above example, and may be performed in another order.

<p> However, the file management method using the UDF described above has the following problems. That is, in UDF, a directory is recorded as a file in the partition space, and a file entry is also recorded in the partition space. Therefore, these directory files and file entries may be distributed and distributed on the disk. Therefore, when trying to read all the files under a certain directory, if the directory files and file entries are distributed, the seek operation for the disk frequently occurs.</p><p> For example, also in FIG. 47, the file entries of FILE1_1, FILE1_2, and FILE1_3 are distributed and arranged, and a seek operation is indispensable for reading them. If the file to be played is a file that requires real-time playback, such as an AV file, it may be difficult to realize it due to the occurrence of seek operation.</p><p> Similarly, when real-time recording such as an AV file is required, when trying to record a file entry after recording the AV data itself, a seek operation for the disk will occur, and AV data recording during that time will occur. It will stop. Such a problem is also the same when a large amount of JPEG-compressed still image files and the like are recorded and viewed.</p><p> In addition, when the device is started up, it is conceivable to reduce the number of seeks to the disk by reading all the file management information into the memory and performing on-memory processing, but many seek operations occur at that time as well. It takes time to start up. Further, since the required memory capacity cannot be predicted in advance, it becomes difficult to construct a system in which computer resources are efficiently arranged.</p><p> An object of the present invention is to provide an AV data recording device and a method capable of minimizing seek operation even when a UDF file system is used in order to solve the above-mentioned problems. ..</p>

<p> The AV data recording device according to the present invention in order to achieve the above object includes a compression unit that compresses an AV signal into AV data and generates it, a recording / playback unit that records the AV data on a disk, and a recording / playback method. The compression unit further generates attribute information including random access information regarding the AV data, and the system control unit is in a recording area physically different from the recording area of the AV data. , A plurality of the attribute information related to the plurality of the AV data are collectively recorded, and the AV data and the file management information for managing the attribute information as a file are referred to as the AV data and the recording area of the attribute information. It is characterized by recording collectively in physically different areas.</p><p> Further, in the AV data recording apparatus according to the present invention, it is preferable that the AV data is an MPEG transport stream.</p><p> In order to achieve the above object, the AV data recording device according to the present invention includes a recording / playback unit that records AV data on a disk or reproduces the recorded AV data, and a system control unit that controls the recording / playback method. It has extension management information that manages consecutive blocks on the disk as extents, file management information that groups extents and manages them as files, and directory information that groups files and manages them as directories. It is characterized by securing a reserved extent which is an area for recording at least one of file management information, a part of a file, and the entire file.</p><p> With such a configuration, even when UDF is used, the file management information of the recorded file is not distributed and recorded in the disk, and the seek operation for the disk can be minimized. Therefore, it is possible to perform high-speed and highly reliable recording. Further, by assigning the reservation extent, it is possible to prevent other information from being recorded.</p><p> In addition, in this specification, "extent management information" is an allocation descriptor. Further, "directory information" means a directory file composed of a plurality of file identification descriptors. Each file description identifier has the file name, the location information of the file entry, and the like for each file included in the directory.</p><p> Further, the "file management information" is a file entry or an extended file entry. Further, "part of a file" means at least one extent in a file consisting of one or more extents managed by a file entry or an extended file entry. On the other hand, "whole file" means all extents in a file consisting of one or more extents managed by a file entry or an extended file entry.</p><p> Further, the "reserved extent" is an AV reserved area which is a directory in which an AV file is recorded, an extent allocated to the AV reserved area management file, and a continuous area secured by the AV reserved area management file. ..</p><p> Further, in the AV data recording device according to the present invention, it is preferable that at least information for managing the position and capacity on the disk is recorded in advance on the disk with respect to the reserved extent. This is because the area on the disk reserved as a reserved extent can be easily known. In particular, in a commutative medium such as an optical disc, another data recording / playback device can easily know the position and capacity of the reserved extent secured by one data recording / playback device.</p><p> Further, in the AV data recording device according to the present invention, it is preferable to secure reserved extents as allocated extents. This is because it is possible to prevent other information from being recorded by assigning the reserved extent.</p><p> Further, in the AV data recording device according to the present invention, it is preferable to secure the reserved extent by recording the file management information of the file in advance. This is because it is not necessary to scan the unrecorded area at the time of file recording, so that the seek operation can be reduced.</p><p> Further, in the AV data recording device according to the present invention, when recording an AV file on a disk, it is preferable to record attribute information related to the AV file in a reserved extent. This is to make it possible to easily perform special playback such as fast-forward playback and fast-rewind playback, and playback at a specified time.</p><p> Further, in the AV data recording device according to the present invention, it is preferable that the attribute information related to the AV file is an extent that forms a part of the AV file. This is to make it possible to easily perform special playback, playback at a specified time, etc. when attribute information is stored inside the AV file.</p><p> Further, in the AV data recording device according to the present invention, it is preferable that the attribute information related to the AV file is a part or all of a file different from the AV file. This is to make it possible to easily perform special playback, playback at a specified time, etc. when attribute information is stored inside a file other than the AV file.</p><p> Further, in the AV data recording device according to the present invention, it is preferable that the AV file is an MPEG transport stream and the attribute information about the AV file recorded in the reserved extent includes the time map information of the transport stream. This is to make it possible to easily perform special playback such as fast-forward playback and fast-rewind playback, and playback at a specified time.</p><p> The "time map information" is information in which the playback time of the AV stream and the recording position are associated with each other. For example, it has a hierarchical data structure composed of two tables called a time map table and a VOBU table. ..</p><p> Further, in the AV data recording device according to the present invention, it is preferable that the AV file is an Exif image file and the attribute information about the AV file recorded in the reserved extent includes Exif attached information which is a part of the Exif image file. Since the additional information includes reduced image information related to the AV file represented by thumbnail information, the reduced image file and other Exif attached information can be played back at high speed by reading only the attribute information recorded in the reservation extension. Because it can be done.</p><p> Further, in the AV data recording device according to the present invention, when a subdirectory is newly created under the directory, the file management information of the file created under the subdirectory hierarchy, a part of the file, and the entire file Of these, it is preferable to secure a new reservation extension for recording at least one of them. This is because the same effect can be expected when recording under a subdirectory.</p><p> Further, in the AV data recording device according to the present invention, when a subdirectory is newly created under the directory, the directory information of the subdirectory, the file management information, a part of the file, and the entire file are stored in the reserved extent. , It is preferable to record at least one of them. This is because the same effect can be expected when recording under a subdirectory.</p><p> Further, the AV data recording device according to the present invention detects a defective block in the reserved extent when securing the reserved extent, and skips the defective block when recording the data in the reserved extent. It is preferable to record. This is because the continuity of the data to be recorded in the reserved area is not impaired, so that highly reliable recording can be performed.</p><p> Further, in the AV data recording device according to the present invention, when recording data on a disk, if the remaining capacity of the reserved extent area reserved in advance is insufficient, a new reserved extent different from the reserved extent is placed on the disk. It is preferable to secure and record the data. This is to prevent the recording / playback of AV data from stopping by minimizing the seek operation.</p><p> Further, in the AV data recording apparatus according to the present invention, when recording a reduced image file including reduced image information about the AV file on a disk, it is preferable to record the reduced image file in the reserved extent. This is because even when displaying a large-capacity reduced image file containing a plurality of image data, the seek operation does not occur, so that the display can be performed at high speed.</p><p> Next, the AV data recording method according to the present invention in order to achieve the above object includes a step of recording AV data on a disk or reproducing the recorded AV data, and a step of controlling the recording / reproduction method. , An AV data recording method that has extent management information that manages consecutive blocks on a disk as extents, file management information that groups extents and manages them as files, and directory information that groups files and manages them as directories. It is characterized in that a reserved extent, which is an area for recording at least one of directory information, file management information, a part of a file, and the entire file, is secured.</p><p> With such a configuration, even when UDF is used, the file management information of the recorded file is not distributed and recorded in the disk, and the seek operation for the disk can be minimized. Therefore, it is possible to perform high-speed and highly reliable recording. Further, by assigning the reservation extent, it is possible to prevent other information from being recorded.</p><p> Further, in the AV data recording method according to the present invention, it is preferable that at least information for managing the position and capacity on the disk is recorded in advance on the disk with respect to the reserved extent. This is because the area on the disk reserved as a reserved extent can be easily known. In particular, in a commutative medium such as an optical disc, another data recording / playback device can easily know the position and capacity of the reserved extent secured by one data recording / playback device.</p><p> Further, in the AV data recording method according to the present invention, it is preferable to secure reserved extents as allocated extents. This is because it is possible to prevent other information from being recorded by assigning the reserved extent.</p><p> Further, in the AV data recording method according to the present invention, it is preferable to secure the reserved extent by recording the file management information of the file in advance. This is because it is not necessary to scan the unrecorded area at the time of file recording, so that the seek operation can be reduced.</p><p> Further, in the AV data recording method according to the present invention, when recording an AV file on a disk, it is preferable to record attribute information related to the AV file in a reserved extent. This is to make it possible to easily perform special playback such as fast-forward playback and fast-rewind playback, and playback at a specified time.</p><p> Further, in the AV data recording method according to the present invention, it is preferable that the attribute information related to the AV file is an extent that forms a part of the AV file. This is to make it possible to easily perform special playback, playback at a specified time, etc. when attribute information is stored inside the AV file.</p><p> Further, in the AV data recording method according to the present invention, it is preferable that the attribute information related to the AV file is a part or all of a file different from the AV file. This is to make it possible to easily perform special playback, playback at a specified time, etc. when attribute information is stored inside a file other than the AV file.</p><p> Further, in the AV data recording method according to the present invention, it is preferable that the AV file is an MPEG transport stream and the attribute information about the AV file recorded in the reserved extent includes the time map information of the transport stream. This is to make it possible to easily perform special playback such as fast-forward playback and fast-rewind playback, and playback at a specified time.</p><p> Further, in the AV data recording method according to the present invention, it is preferable that the AV file is an Exif image file and the attribute information about the AV file recorded in the reserved extent includes Exif attached information which is a part of the Exif image file. Since the additional information includes reduced image information related to the AV file represented by thumbnail information, the reduced image file and other Exif attached information can be played back at high speed by reading only the attribute information recorded in the reservation extension. Because it can be done.</p><p> Further, in the AV data recording method according to the present invention, when a subdirectory is newly created under a directory, the file management information of the file created under the subdirectory hierarchy, a part of the file, and the entire file Of these, it is preferable to secure a new reservation extension for recording at least one of them. This is because the same effect can be expected when recording under a subdirectory.</p><p> Further, in the AV data recording method according to the present invention, when a subdirectory is newly created under the directory, the directory information of the subdirectory, the file management information, a part of the file, and the entire file are included in the reserved extent. , It is preferable to record at least one of them. This is because the same effect can be expected when recording under a subdirectory.</p><p> Further, the AV data recording method according to the present invention detects a defective block in the reserved extent when securing the reserved extent, and skips the defective block when recording the data in the reserved extent. It is preferable to record. This is because the continuity of the data to be recorded in the reserved area is not impaired, so that highly reliable recording can be performed.</p><p> Further, in the AV data recording method according to the present invention, when recording data on a disk, if the remaining capacity of the reserved extent area reserved in advance is insufficient, a new reserved extent different from the reserved extent is placed on the disk. It is preferable to secure and record the data. This is to prevent the recording / playback of AV data from stopping by minimizing the seek operation.</p><p> Further, in the AV data recording method according to the present invention, when recording a reduced image file including reduced image information about the AV file on a disk, it is preferable to record the reduced image file in the reserved extent. This is because even when displaying a large-capacity reduced image file containing a plurality of image data, the seek operation does not occur, so that the display can be performed at high speed.</p><p> Further, the same effect can be expected for the disc recorded by the AV data recording device and the method according to the present invention as described above.</p>

<p> As described above, according to the AV data recording device according to the present invention, by recording the file management information and the attribute information of the AV file in the continuous area secured in advance, the real-time recording / reproduction of the AV file is hindered. It is possible to reduce the seek operation to the disk.</p><p> Further, even when a large amount of still images are recorded by JPEG compression or the like, since the file management area is recorded in the continuous area, it is possible to read out at high speed.</p>

Hereinafter, the AV data recording device according to the embodiment of the present invention will be described with reference to the drawings. Hereinafter, a file containing audio data or video data encoded by the MPEG method, JPEG method, or the like is referred to as an AV file. Further, in the present specification, the disc means all recording media having a disc shape such as an optical disc such as DVD-RAM, MO, DVD-R, DVD-RW, DVD + RW, and a hard disk.

(Embodiment 1) FIG. 1 shows a configuration diagram of an AV data recording device according to the first embodiment of the present invention. In FIG. 1, 1 indicates a disk such as a magneto-optical disk, and 2 indicates a recording medium driving unit. For example, when the disk 1 is a magneto-optical disk, the recording medium driving unit 2 is composed of a spindle motor or the like.

Reference numeral 3 denotes a recording / playback unit, and when the disk 1 is a magneto-optical disk, it is composed of an optical pickup, a magnetic head, a servo circuit, a modulation / demodulation circuit, and the like. Reference numeral 4 denotes a memory unit, which temporarily stores data during data recording and reproduction. Reference numeral 5 denotes a disk drive unit, which is composed of a disk 1, a recording medium drive unit 2, a recording / playback unit 3, and a memory unit 4.

In addition, 6 indicates an AV signal processing unit, for example, processing such as MPEG compression on an AV input signal input from a CCD camera or the like, or processing such as MPEG decoding on AV data read from a disk medium. And output to a monitor etc. Reference numeral 7 indicates a system control unit, which controls the AV signal processing unit 6 and the disk drive unit 5.

In the AV data recording device configured in this way, when recording data, the AV signal input to the AV signal processing unit 6 is subject to the control of the system control unit 7 after performing image compression processing such as the MPEG method. , Transferred to memory section 4. Next, under the control of the system control unit 7, the recording medium drive unit 2 and the recording / playback unit 3 operate to record the data on the memory unit 4 on the disk 1.

At the time of data reproduction, the recording medium driving unit 2 and the recording / reproducing unit 3 operate under the control of the system control unit 7, and the data recorded on the disk 1 is transferred to the memory unit 4. Next, under the control of the system control unit 7, data is read from the memory unit 4 and output as an AV signal from the AV signal processing unit 6.

FIG. 2 is an example diagram of the file / directory structure in the state immediately after the directory for recording the AV file is created in the first embodiment. In FIG. 2, ROOT surrounded by an ellipse indicates the root directory, and AV_DIR1 indicates the directory in which the AV file is recorded.

FIG. 3 is an example diagram of the data structure of the partition space in the state where the file / directory structure shown in FIG. 2 is recorded in the disk used for the AV data recording device according to the first embodiment of the present invention. In FIG. 3, the space bitmap descriptor is recorded at LBN = 0 to 79. In addition, since LBN = 251 or later, the "unallocated state" is set, so each bit corresponding to these sectors is set to '1'.

In addition, a fileset descriptor is recorded at LBN = 80. If the file entry is a file entry in the root directory, the location information is recorded in the file set descriptor. In addition, the termination descriptor is recorded in LBN = 81.

Furthermore, the file entry of the ROOT directory is recorded in LBN = 82, the directory file of the ROOT directory is recorded in LBN = 83, and the file entry of the directory AV_DIR1 is recorded in LBN = 84.

Next, LBN = 85 is an extent (1) in which the directory file in directory AV_DIR1 is recorded. Similarly, LBN = 86 to 250 are extents (2) of the directory AV_DIR1, and the values of the upper two bits of the allocation descriptor are set so that the extents are "allocated" and "unrecorded". Therefore, in the operation of the conventional file system, data cannot be written to LBN = 86 to 250. Hereinafter, this estent (2) is referred to as an AV reserved area. As mentioned above, LBN = 0 to 250 are already "allocated", so the corresponding bits in the space bitmap are set to '0' (zero).

In the first embodiment, the extents of the "allocated" and "unrecorded" extents in the directory AV_DIR1 in the initial state of the recording medium are defined in advance. As a result, in the recording / playback processing for the disk 1 as shown in FIG. 4 (step S401 in FIG. 4), a system configuration is possible in which the contents of LBN = 0 to 250 on the disk 1 are read into the memory unit 4. Therefore, it is possible to reduce the number of seek operations that occur during recording / playback.

Here, FIG. 4 shows a flow chart of a process of recording an AV file on a disk having such a data structure. When the recording of the AV file is started by the user's instruction or the like, in FIG. 4, the contents of LBN = 0 to 250 on the disk 1 are first read into the memory unit 4 (step S401). Next, the information in the AV reserved area on the memory unit 4 is scanned, and it is determined whether or not there is an unrecorded area that can newly record the file identification descriptor and the file entry (step S402). When it is determined that there is not enough unrecorded area for new recording (step S402: No), error processing is performed and AV file recording is terminated. When it is determined that there is a sufficient unrecorded area, the file identification descriptor and the file entry are recorded in the unrecorded area in the AV reserved area on the memory unit 4 (step S403).

At this time, the size of the extent of the directory AV_DIR1 changes depending on the file identification descriptor and the recording of the file entry, so the allocation descriptor of the file entry of the directory AV_DIR1 is rewritten accordingly. Specifically, it is a rewrite operation in which the extent length of the extent (1) is changed by adding a file identification descriptor and the part in which the file entry is recorded is excluded from the extent (2).

Next, the space bitmap on the memory unit 4 is scanned to determine the presence or absence of the number of unrecorded logical blocks required to record the AV file (step S404). When it is determined that there are no required number of unrecorded logical blocks (step S404: No), error processing is performed and AV file recording is terminated. If it is determined to exist, data is recorded in the logical block of the recording medium corresponding to the unrecorded area obtained in step S404 (step S405).

When the recording of the AV file data is completed, in order to update the file management information of the AV file, the location and length information of the extent of the AV file is added to the allocation descriptor in the file entry on the memory section 4 created in step S403. Record (step S406). In addition to the allocation descriptor, necessary information such as the file name and file creation time is also updated for the file identification descriptor and the file entry.

Next, the space bitmap on the memory unit 4 is changed to '1' indicating "allocated" for the bit corresponding to the logical block in which the data was recorded in step S405 (step S407). Then, the contents of the memory unit 4 are written back to the positions of LBN = 0 to 250 on the disk 1 (step S408). When the file is recorded in this way, the AV file is recorded under the directory AV_DIR1.

When attempting to record a plurality of AV files continuously, in the processing flow chart shown in FIG. 4, after the processing of step S401, steps S402 to S407 are repeated until the recording of all AV files is completed, and all AVs are recorded. After recording the file, proceed to step S408.

As a result, it is not necessary to write the file identification descriptor and the file entry to the recording medium each time a file is created, and the number of seek operations can be significantly reduced.

According to the processing flow diagram shown in Fig. 4, the data structure of the partition space after the AV files FILE1.DAT and FILE2.DAT are recorded under the directory AV_DIR1 is as shown in Fig. 5. Here, it is used to record a new file entry from a logical block with a large LBN in the AV reserved area, while the file identification descriptor is added to the end of the recorded extent (1) in the directory AV_DIR1. It is recorded by the method. Since both the file identification descriptor and the file entry have a variable length data structure, it is possible to record the file identification descriptor from the smaller LBN of the AV reserved area and the file entry from the larger LBN in this way. desirable.

If, as a result of adding a file, there is not enough space to describe the file identification descriptor in extent (1), the block adjacent to extent (1) in the AV reserved area is included in extent (1). Modify the allocation descriptor in the directory AV_DIR1 and record the file identification descriptor in that part. However, the addition of the file entry and the file identification descriptor to the AV reserved area is not limited to the above procedure. For example, the AV reserved area is divided into two areas, and the area with the smaller LBN is used. May be used to record the file identification descriptor and the file entry may be recorded from the beginning of the rest. In this case, for example, the length of the file name of the file to be recorded is determined in advance, the upper limit of the data length recorded in the file identification descriptor is set in advance, and the capacity allocation when dividing the AV reserved area is determined. It will be decided.

To play a recorded AV file using the recording state disc shown in Fig. 5, follow the procedure below. First, the contents of LBN = 0 to 250 on the disk 1 are read into the memory unit 4 in the same manner as in step 401 shown in FIG. It then scans the recorded extents in directory AV_DIR1 to get the names of the files that exist under directory AV_DIR1.

Next, the data of the file is accessed and the file is played according to the procedure described in the conventional technique. If you want to play the next file continuously, the file identification descriptors and file entries of all the files existing under the directory AV_DIR1 are read in the memory section 4. Therefore, when playing an AV file under the directory AV_DIR1, it is possible to directly access the extent of the file to be played, and the seek operation for the file entry that occurred in the conventional method does not occur, and it is fast. Continuous file playback is possible.

Such continuous reproduction is easily realized by recording according to the processing procedure shown in FIG. 4, and if the recording procedure of the present invention is not used, it is recorded under the directory AV_DIR1. It is uncertain in which logical block of the partition space the entry is recorded even if the AV file is created. Similarly, the read operation to the memory unit 4 can be easily and quickly realized by recording according to the processing procedure shown in FIG. Even if the recording procedure according to the present invention is not used, reading into the memory unit 4 is possible, but for that purpose, many seek operations cannot be avoided at the start of the recording / reproducing operation.

The recording procedure is not limited to the processing procedure shown in FIG. 4, and as described in, for example, International Publication W098 / 14938, a continuous free space is provided prior to recording the actual data. It is also possible to secure a plurality of them, register them as "allocated state" in the space bitmap, and then start recording the actual data.

In addition, the allocation descriptor and space bitmap information of the directory AV_DIR1 may be updated collectively after the recording of the file data is completed.

In addition, the process for initializing the data structure of the partition space in the disk as shown in Fig. 3 shall be performed when necessary prior to recording the AV file.

Further, the directory / file name in which the AV file is recorded is not limited to the one described in the first embodiment, and may be another directory / file name.

In addition, although it was assumed that LBN = 0 to 250 were read into the memory unit 4 during recording / playback, it is not necessary to retain all the information in the memory unit 4, and only the information necessary for the recording / playback operation is retained. Also, only the information that needs to be updated may be written back to disk 1.

In addition, LBN = 86 ~ 250 is secured as an extent that is "allocated" and "unrecorded" in the directory AV_DIR1 to make it an AV reserved area, but the recording position and capacity of the AV reserved area are LBN = 0 ~ It is not limited to 250, and other recording positions and capacities may be used as long as it is secured as a continuous area on the disk.

Although the case where the file entry is used has been described in the first embodiment, the extended file entry may be used. When the extended file entry is used, the AV reserved area may be reserved as a part of the extent of the named data stream in the directory AV_DIR1. Further, in this case, the extents constituting the AV reserved area may be "allocated" and "recorded" extents.

(Embodiment 2) Hereinafter, the AV data recording device according to the second embodiment of the present invention will be described with reference to the drawings. In the second embodiment, in the first embodiment, the file identification descriptor and the file entry of the newly recorded AV file are recorded in the "allocated" and "unrecorded" extents of the directory AV_DIR1. On the other hand, a management file that stores the management information of the AV file is created under the directory AV_DIR1, and the management file has extents that are "allocated" and "unrecorded". There is a feature.

FIG. 6 is an example diagram of a file / directory structure in a state immediately after a directory for recording an AV file is created in the AV data recording device according to the second embodiment of the present invention. It differs from the directory structure shown in Fig. 2 in that a management file called AVFILES.IFO exists under the directory AV_DIR1.

Further, FIG. 7 is an example diagram of the data structure of the partition space in the state where the directory for recording the AV file is recorded. In FIG. 7, the space bitmap descriptor is recorded at LBN = 0 to 79. Here, since LBN = 251 and later are in the "unallocated state", each bit corresponding to these sectors is set to '1'.

In addition, the file set descriptor is recorded in LBN = 80. If the file entry is a file entry in the root directory, its location information is recorded in the fileset descriptor.

In addition, LBN = 81 has a termination descriptor, LBN = 82 has a file entry in the ROOT directory, LBN = 83 has a directory file in the ROOT directory, LBN = 84 has a file entry in directory AV_DIR1, and LBN = The file entries of the AVFILES.IFO file are recorded in 85 respectively.

LBN = 86 is an extent in which the directory file of directory AV_DIR1 is recorded. LBN = 87 ~ 250 is an extent of the AVFILES.IFO file, and the value of the upper 2 bits of the allocation descriptor is set so that this extent is "allocated" and "unrecorded". In the second embodiment, this area is the AV reserved area.

When recording an AV file on a disk having such a data structure, the same processing procedure as shown in FIG. 4 can be performed. However, the difference is that the AV reserved area for recording the new file identification descriptor and file entry is the "allocated" and "unrecorded" extent of the management file AVFILES.IFO.

When playing back an AV file from a disc on which the AV file is recorded, the same procedure as described in the first embodiment can be performed. In the second embodiment, no data is recorded in the AVFILES.IFO file in the initial state, but for example, the attribute information related to the directory AV_DIR1 is recorded in the initial state, and it is "allocated". Not only "unrecorded" extents but also "allocated" and "recorded" extents may be configured. Further, this "allocated" and "recorded" extent may be used as the AV reservation area.

In the second embodiment, the case where the file entry is used has been described, but the extended file entry may be used. Further, when the extended file entry is used, the AV reserved area may be reserved as a part of the extent of the named data stream of the file AVFILES.IFO. Further, in this case, the extents constituting the AV reserved area may be "allocated" and "recorded" extents.

In the second embodiment, the AV reserved area management file is recorded under the same directory as the directory where the AV file is recorded, but the AV reserved area management file is recorded in another directory. There may be. By recording the AV reserved area management file in another directory, it is possible to prevent the management file from being accidentally deleted by the user's operation or the like.

(Embodiment 3) Hereinafter, the AV data recording device according to the third embodiment of the present invention will be described with reference to the drawings. In the third embodiment, a case where 100 AV files are recorded under the directory AV_DIR1 will be described. FIG. 8 is an example diagram of the file / directory structure according to the third embodiment.

In the first and second embodiments, extents that are "allocated" and "unrecorded" are assigned to directories and files, and file entries and the like of AV files are recorded in the area. The difference in the third embodiment is that when the directory for recording the AV file is created, the file identification descriptor and the file entry for the AV file are created in advance in the continuous area.

Further, FIG. 9 is an example diagram of the data structure of the partition space according to the third embodiment. In FIG. 9, a file name is automatically assigned to each file and recorded in the file identification descriptor. In the third embodiment, since 100 files are under the directory AV_DIR1, 100 file identification descriptors are recorded in the extent of the directory AV_DIR1. The allocation descriptor in each file entry of the AV file recorded in LBN = 101 to 200 does not indicate an extent, and the data capacity as a file is 0 (zero).

In the third embodiment, the file identification descriptor and the file entry are already recorded. Therefore, when recording the AV file, the data is read into the memory unit 4 in the same manner as the processing procedure shown in FIG. 4, but in step S402, the unrecorded area is not scanned, and LBN = 101 instead. The information of the file entry recorded in ~ 200 is scanned, the file entry whose file size is 0 (zero) is detected, and the detected file is recorded as a new AV file. Then, when the data recording is completed, the information on the position and length of the extent recorded in the allocation descriptor of the file entry on the memory unit 4 and other file management information are updated. Finally, as in step S408, the contents of the memory unit 4 are written back to the disk 1. Similarly, when playing back the AV file, the procedure described in the first embodiment can be performed.

In the third embodiment, a file entry having a file size of 0 (zero) is detected and used as a new AV file, but the method of detecting a new file entry is limited to this method. It may be another method instead of the one. For example, change the file name between the initial state and after recording the actual AV data, or record the AV data using the file attribute field in the file identification descriptor, the extended attribute field in the file entry, etc. You may decide whether it is good or not.

In addition, although the data capacity of the file is assumed to be 0 (zero) in the initial state, for example, common attribute information between AV files is recorded so that the data is recorded even in the initial state. You may.

(Embodiment 4) Hereinafter, the AV data recording device according to the fourth embodiment of the present invention will be described with reference to the drawings. As described above, in the first to third embodiments, the file management information such as the file entry is recorded in the area reserved in advance. The fourth embodiment differs in that not only the file entry but also the attribute information of the AV file is recorded in the area reserved in advance. As a result, it has a feature that specific information of an AV file can be accessed continuously at high speed.

FIG. 10 is an example diagram of the data structure of the AV file recorded in the fourth embodiment. In FIG. 10, the AV file of the fourth embodiment is an MPEG transport stream, and is composed of an AV stream section which is a video stream and an attribute information section which is a private stream. The AV stream unit is composed of a plurality of video object units (Video Object Unit: hereinafter referred to as "VOBU").

One VOBU is AV data corresponding to 0.4 to 1 second of video data, and includes a video data section called GOP (Group Of Pictures) in the MPEG2 standard. Since the GOP contains at least one I-picture, it can be played independently. Further, in the case of special playback such as fast forward playback and fast rewind playback, or playback at a specified time, the I picture in the GOP is extracted as an image to be played back.

Attribute information related to the AV stream is recorded in the attribute information unit, and for example, the recording date and time of the file, comments on the recorded information, parameters at the time of recording, thumbnail images, and the like are recorded. Further, in addition to the above-mentioned attribute information, time map information is recorded for the AV stream as information that facilitates special playback such as fast-forward playback and playback at a specified time.

The time map information is information that associates the playback time of the AV stream with the recording position, as described in Japanese Patent No. 3028517, and as shown in FIG. 11, the time map table and the VOBU table. It has a hierarchical data structure consisting of two tables called.

Here, the time map table shows the recording position of the VOBU corresponding to the playback time when the playback is performed every TMU (for example, 60 seconds) at a fixed time interval on the time axis whose start time is the beginning of the AV stream section. It is a table in which time maps # 1, # 2, ... are arranged.

The VOBU table is a table in which VOBU maps including the playback time and data size of each VOBU are arranged in the order of playback time from the beginning of the AV stream section.

FIG. 12 shows a more detailed data structure of the time map information. In addition, Fig. 13 shows the logical connection relationship between the time map table and the VOBU table.

Here, the general time map information includes the number of time maps and VOBU maps included in the time map information, a time unit indicating a fixed time interval in which the time map is provided (hereinafter referred to as "TMU"), and an AV stream section. It includes a time offset (hereinafter referred to as "TM_OFS") that indicates the time difference between the start time and the time on the first time map. However, the value of TM_OFS is '0' unless editing work such as deleting the beginning of the AV stream part is performed.

Further, in the time map table, a plurality of time maps # 1, # 2, ... Are provided at regular time intervals indicated by the TMU, and are arranged in chronological order.

Each time map is composed of a VOBU map number, a time difference (hereinafter referred to as "TM_DIFF"), and a VOBU address (hereinafter referred to as "VOBU_ADR"). Note that VOBU_ADR is the position information in the AV stream section at the beginning of the corresponding VOBU.

The playback time for the time map #i (hereinafter referred to as "time map time") is represented by (Equation 1).

(Equation 1) (Time map time) = (TMU * (i-1) + TM_OFS)

The VOBU map number indicates the VOBU map number existing at the playback time represented by (Equation 1). For example, as shown in Fig. 13, the time map # 1 is the time when the start time of the AV stream section and TM_OFS are added, the time map # 2 is after TMU from the time map # 1, and after that, 2TMU, 3TMU, ... Refers to the VOBU map that exists at the playback time of.

TM_DIFF indicates the time difference between the start time of the corresponding VOBU and the time map time. Therefore, the start time of VOBU # j is represented by (Equation 2).

(Number 2) (Start time of VOBU) = TMU * (j-1) + TM_OFS -TM_DIFF

In the VOBU table, VOBU maps # 1, # 2, ..., Which have a one-to-one correspondence with the VOBU included in the AV stream section, are arranged. Each VOBU map consists of a reference image size, VOBU playback time, and VOBU size.

The reference image size is the size of the first I picture in VOBU, and is used to find the target image during special playback or playback at a specified time. For example, by adding the VOBU playback time to the VOBU start time in order until the playback time of the target image is reached, the VOBU to be played back is specified, and the image in the VOBU is further specified.

The VOBU size is the data size of the VOBU, and is used to specify the position of the target image data during special playback or playback at a specified time.

As described above, according to the fourth embodiment, it is possible to search for a specific image such as an I-picture at high speed even during special reproduction or the like.

The file / directory structure in the initial state in the fourth embodiment is the same as that in FIG. On the other hand, the data structure of the partition space for it is shown in FIG. The difference from Fig. 3 is that in addition to the file management information, the area for recording a part of the AV file is also reserved as the "allocated" and "unrecorded" extent of the directory AV_DIR1. Therefore, the logical block in which the extent (2) of the directory AV_DIR1 is recorded is LBN = 86 to 500, and if the same number of AV files are assumed, more will be secured than in the case of Fig. 3. At this time, the capacity to be secured is the sum of the capacity of the file management information and the capacity of the attribute information unit for the expected number of AV files.

In the AV file, the attribute information section contains an item called time map information that changes according to the data capacity of the AV stream section, but conditions such as the disk capacity, the number of AV files to be recorded, and the bit rate of the AV stream are set. Thereby, the maximum capacity of the time map information unit recorded in the disk 1 can be determined in advance. Therefore, for the AV file recorded in the directory AV_DIR1, it is sufficient to secure the capacity of the AV reserved area in anticipation of the capacity of the entire attribute information unit when the capacity of the time map information unit is maximized. Become.

When an AV file is recorded on a disk having such a data structure, it is performed according to the processing flow chart of FIG.

In FIG. 15, first, the contents of LBN = 0 to 500 on the disk 1 are read into the memory unit 4 (step S1301). Next, the extent information of the directory AV_DIR1 on the memory unit 4 is scanned to determine whether or not there is an unrecorded area sufficient to record the file identification descriptor, the file entry, and the attribute information unit of the file (step S1302). If it is determined that there is not enough unrecorded area to record the attribute information section (step S1302: No), error processing is performed and AV file recording is terminated. If it is determined that there is enough unrecorded area to record the attribute information part, the file identification descriptor and file entry in the unrecorded area in the extent in the directory AV_DIR1 on the memory part 4 and the attribute information part of the AV file. Is recorded (step S1303).

Then, the allocation descriptor of the file entry in the directory AV_DIR1 is rewritten according to the recording of the file identification descriptor and the file entry. Specifically, it is a rewriting operation such as changing the extent length of a recorded extent by adding a file identification descriptor and excluding the portion where the file entry is recorded from the unrecorded extent. Also, in the attribute information section of the AV file, the information for which the information to be recorded has already been determined is recorded in the AV reserved area on the memory section 4.

Next, the space bitmap on the memory unit 4 is scanned to determine the presence or absence of the number of unallocated logical blocks required to record the AV file (step S1304). When it is determined that there are no required number of unallocated logical blocks (step S1304: No), error processing is performed and AV file recording is terminated. When it is determined that there are a required number of unallocated logical blocks, data is recorded in the logical blocks of the recording medium corresponding to the unrecorded area obtained in step S1303 (step S1305).

Further, since the time map information is obtained at this time from the attribute information of the AV file, it is appropriately recorded in the AV reserved area on the memory unit 4. When the recording of the AV file data is completed, the location and length information of the extent of the AV file is recorded in the allocation descriptor in the file entry created in step S1303 (step S1306). In addition to the allocation descriptor, necessary information such as the file name and file creation time is updated for the file identification descriptor and the file entry.

Next, with respect to the space bitmap on the memory unit 4, the bit corresponding to the logical block in which the data was recorded in step S1305 is changed to '1' representing "allocated" (step S1307). Then, the contents of the memory 3 are written back to the positions of LBN = 0 to 500 on the disk 1 (step S1308). When the file is recorded in this way, the AV file is recorded under the directory AV_DIR1.

When attempting to record a plurality of AV files continuously, in the process flow diagram shown in FIG. 15, after step S1301, steps S1302 to S1307 are repeated until the recording of all AV files is completed, and all the AV files are recorded. After the recording of is completed, the process proceeds to step S1308. As a result, it is not necessary to write the file identification descriptor and the file entry to the disk every time a file is created, and the number of seek operations can be significantly reduced.

According to the processing flow shown in FIG. 15, the data structure of the partition space after the AV files FILE1.DAT and FILE2.DAT are recorded under the directory AV_DIR1 is shown in FIG. Here, the file identification descriptor, the file entry, and the attribute information part of the AV file are recorded in the place that was the AV reserved area.

When playing back an AV file from a disc having a data structure as shown in FIG. 16, the procedure can be the same as the procedure described in the first embodiment. However, in step S408, it is assumed that the contents of LBN = 0 to 500 on the disk 1 are read into the memory unit 4.

In addition, when you want to play a specific display time of a certain AV file, the attribute information part including the file identification descriptor, file entry and time map information of all AV files existing under the directory AV_DIR1 directory is on the memory part 4. It has been loaded. Therefore, the offset position in the file with respect to a certain playback time can be obtained by processing only the information in the memory unit 4, and the seek operation with respect to the disk 1 is not required. As a result, it is possible to easily execute special reproduction in which only a specific frame is selectively reproduced. In addition, it is possible to perform operations such as extracting various attribute information and displaying it as a list to the user at high speed.

Such continuous reproduction is realized by recording according to the processing procedure shown in FIG. 15, and if the recording procedure according to the fourth embodiment of the present invention is not used, the AV file The attribute information of is recorded in the same extent as the AV stream part, and will be distributed and arranged on the disk. As a result, it is inevitable that a seek operation for extracting attribute information will occur.

The positional relationship between the file entry, the attribute information, and the time map information in the AV reserved area may be in a different order. Also, when playing an AV file, the part in the AV reserved area where the attribute information of the AV file is recorded is also read into the memory section 4, but it should be read as needed instead of reading everything from the beginning. You can do it. Even in this case, the number of seek operations can be reduced as compared with the conventional technology, and the attribute information of the AV file and the table for high-speed access can be read at high speed.

Further, in the fourth embodiment, the AV reserved area is provided as an extent of the directory AV_DIR1, but as in the second embodiment, a management file may be created and the AV reserved area may be provided as the extent. In this case, the AV file is recorded / reproduced in the same manner as in the second embodiment.

The AV reserved area may be secured as a plurality of extents. For example, an AV reserved area for the file management area may be provided as an extent of the directory AV_DIR1, and an AV reserved area for the attribute information of the AV file may be provided separately as an extent of the management file.

Alternatively, two types of management files may be provided, the first management file may be provided with an AV reserved area for the file management area, and the second management file may be provided with an AV reserved area for the attribute information of the AV file. good. In addition, any other method may be used as long as the AV reserved area is secured as a continuous area.

The time map information may be any information as long as the playback time of the AV stream is associated with the recording position, and may be other than the configuration shown in FIG.

In the fourth embodiment, the AV file is an MPEG transport stream, but it may be in another format, and the specific information of the AV file may be recorded in a predetermined area. ..

(Embodiment 5) Hereinafter, the AV data recording device according to the fifth embodiment of the present invention will be described with reference to the drawings. As described above, in the fourth embodiment, an AV file composed of an AV stream unit in which MPEG2 video data is recorded and an attribute information unit is recorded. In the fifth embodiment, the AV file is an Exif image file, and is composed of an Exif main image which is the main image data and ancillary information related thereto.

That is, the AV file in the fifth embodiment is composed of a header part consisting of attached information related to the still image and a video data part consisting of the still image data main body, and the attached information is recorded in the AV reserved area. It has the characteristics of. This has the advantage that specific information such as thumbnail images of AV files can be accessed at high speed and continuously by seeking only within the AV reserved area.

FIG. 17 is an example diagram of a data structure of an AV file in the AV data recording device according to the fifth embodiment of the present invention. In FIG. 17, the AV file of the fifth embodiment is composed of a header part and a video data part.

Ancillary information about the video data section is recorded in the header section. For example, the recording date and time of the file, comments on the recorded information, parameters at the time of recording / compression, thumbnail images, and the like are recorded. Further, in the video data section, a JPEG-compressed still image data body is recorded.

The file / directory structure in the AV data recording device according to the fifth embodiment is the same as that in FIG. On the other hand, the data structure of the partition space for it is the same as in FIG.

However, in the AV reserved area, the file management information of the AV file and the data of a predetermined capacity from the beginning of the AV file are recorded. It is assumed that at least the thumbnail image portion of the header portion of the AV file is included in the data for the predetermined capacity.

As a result, when displaying a thumbnail list of recorded AV files, a list of recording dates and times, etc. to the user, the information is recorded in the AV reserved area, which is a continuous area, so that the information can be displayed at high speed. Is possible.

As shown in FIG. 18, even if padding data is inserted in the data structure of the AV file to adjust the capacity of the header part so that the capacity of the entire header part is an integral multiple of the logical block capacity of the UDF. good. At this time, since the capacity of the header portion is an integral multiple of the logical block capacity of the UDF due to the padding data, the video data portion is always arranged from the beginning of the logical block. In addition, only the file management information and the header part are recorded in the AV reserved area. Therefore, when recording / reproducing an AV file, the header part and the video data part can be completely separated, and the processing can be performed in units of logical blocks, so that recording / playback can be performed at higher speed.

In the fifth embodiment, the AV file is an Exif file including the main image compressed by the JPEG method, but the present invention is not particularly limited to this, and a still image in a format having attached information in the header portion. Any file will do.

There may be a plurality of AV directories on the disk. In that case, a still image file is recorded in one directory as in the fifth embodiment, and the other directory is as in the fourth embodiment. You may record an MPEG2 video file. Furthermore, the number of AV directories is not limited to two as described above, and the number of directories can be increased as needed.

At this time, the AV reserved area may be managed for each directory, or a dedicated management directory may be provided to manage the AV reserved area used in each directory. For example, as shown in FIG. 19, the AV reserved area management file AVFILES.IFO is placed under the management directory AV_INFO, and the AV reserved area managed by the AV reserved area management file is used to create a still image under the AV directory AV_DIR1. It is conceivable to record the file and record the video file under the directory AV_DIR2.

Note that the recording is not limited to the moving image file and the still image file for each directory, and the moving image file and the still image file may be mixed and recorded in one directory.

As described above, according to the fifth embodiment, the data recorded by the user and the information for management thereof can be separated, and the destruction of the management information due to an erroneous operation or the like can be avoided. Although a single AV reserved area management file is used here, for example, an AV reserved area management file may be provided for each AV directory.

(Embodiment 6) Hereinafter, the AV data recording device according to the sixth embodiment of the present invention will be described with reference to the drawings. In the sixth embodiment, a case where the AV directory has a hierarchical structure will be described. It is convenient to support hierarchical directories in order to classify recorded data. However, in the case of UDF, since the directory is also treated as a kind of file, it is unavoidable that the seek operation occurs especially in the deep directory structure.

Therefore, in the sixth embodiment, a reserved area is provided for creating a hierarchical directory. FIG. 20 is an example diagram of the file / directory structure immediately after the directory for recording the AV file is created.

FIG. 21 shows the data structure of the partition space in the state where the file / directory structure shown in FIG. 20 is recorded in the disk used for the AV data recording device according to the sixth embodiment of the present invention.

LBN = 86 ~ 250 is the extent (2) of the AV_DIR1 directory, and the value of the upper 2 bits of the allocation descriptor is set so that the extent (2) is "allocated" and "unrecorded". .. In the following, this extent (2) is referred to as an AV directory reserved area.

When creating a subdirectory under the AV directory on a disk having such a data structure, the process flow diagram shown in FIG. 22 is followed.

First, the contents of LBN = 0 to 250 on the disk 1 are read into the memory unit 4 (step S171). Next, the information in the AV directory reserved area on the memory unit 4 is scanned, and it is determined whether or not there is an unrecorded area sufficient to newly record the file identification descriptor and the file entry for the AV subdirectory. (Step S172). If it is determined that there is not enough unrecorded area (step S172: No), error processing is performed and the AV subdirectory creation process is terminated.

When it is determined that there is a sufficient unrecorded area, the file identification descriptor and the file entry are recorded in the unrecorded area in the AV reserved area on the memory unit 4 (step S173). At this time, the extent size of the AV_DIR1 directory changes depending on the file identification descriptor and the recording of the file entry, so the allocation descriptor of the file entry in the AV_DIR1 directory is rewritten accordingly.

Specifically, it is a rewriting operation such as changing the extent length of the extent (1) by adding a file identification descriptor and excluding the part where the file entry is recorded from the extent (2).

Next, the space bitmap on the memory unit 4 is scanned to determine the presence or absence of the number of consecutive unallocated logical blocks required to record the AV subdirectory file and the AV reserved area allocated to it (step). S174). When it is determined that there are no required number of consecutive unallocated logical blocks (step S174: No), the process ends.

When it is determined that there are a required number of consecutive unallocated logical blocks, data is recorded for the logical blocks of the disk corresponding to the unallocated area obtained in step S173 (step S175). Here, the recording of data includes the creation of a directory file of the AV subdirectory and the operation of securing the AV reserved area allocated to the AV subdirectory.

After the data recording is completed, in order to update the file management information of the AV subdirectory file, the extent position and length information of the AV subdirectory file is added to the file entry on the memory section 4 created in step S173. Record in the allocation descriptor (step S176).

In addition to the allocation descriptor, necessary information such as the file name and file creation time is also updated for the file identification descriptor and the file entry.

Next, with respect to the space bitmap on the memory unit 4, the bit corresponding to the logical block in which the data was recorded in step S173 is changed to '1' indicating "allocated" (step S177).

Then, the contents of the memory unit 4 are written back to the positions of LBN = 0 to 250 on the disk 1 (step S178). By this series of processing, the AV subdirectory AV_SUB_DIR1 is created under the directory AV_DIR1. The directory structure at this time is shown in Fig. 23. The data structure of the partition space at this time is shown in FIG.

Here, as in the first embodiment, it is used for recording a new file entry from a logical block having a large LBN in the AV directory reserved area, while the file identification descriptor is a recorded extent of the directory AV_DIR1. It is recorded by adding it to the end of extent (1). However, what is recorded here is not an AV file, but a directory file.

In addition, the created AV subdirectory is the extent (2), and the value of the upper 2 bits of the allocation descriptor is set so that this extent (2) is "allocated" and "unrecorded". ing. After that, when recording an AV file under the directory AV_SUB_DIR1, this AV reserved area is used to record in the same procedure as in the first embodiment.

Further, when recording an AV file on a disk having such a data structure, the process flow diagram of FIG. 25 is followed.

First, the contents of LBN = 0 to 79 and LBN = 250 to 400 on the disk 1 are read into the memory unit 4 (step S201). Next, the information of the AV reserved area in the subdirectory AV_SUB_DIR1 on the memory unit 4 is scanned, and it is determined whether or not there is an unrecorded area sufficient for newly recording the file identification descriptor and the file entry (step S202). If it is determined that there is not enough unrecorded area (step S202: No), error processing is performed and AV file recording is terminated.

When it is determined that there is a sufficient unrecorded area, the file identification descriptor and the file entry are recorded in the unrecorded area in the AV reserved area in the subdirectory AV_SUB_DIR1 on the memory unit 4 (step S203).

Next, the space bitmap on the memory unit 4 is scanned to determine the presence or absence of the number of unallocated logical blocks required to record the AV file (step S204). When it is determined that there are no required number of unallocated logical blocks (step S204: No), error processing is performed and recording processing is terminated.

When it is determined that there are a required number of unallocated logical blocks, data is recorded in the logical blocks of the recording medium corresponding to the unrecorded area obtained in step S203 (step S205).

After recording the AV file data, in order to update the file management information of the AV file, the location and length information of the extent of the AV file is the allocation descriptor in the file entry on the memory part 4 created in step S205. Record in (step S206).

Next, with respect to the space bitmap on the memory unit 4, the bit corresponding to the logical block in which the data was recorded in step S205 is changed to '1' indicating that it is allocated (step S207).

Then, the contents of the memory unit 4 are written back to the positions of LBN = 0 to 79 and LBN = 250 to 400 on the disk 1 (step S208). In this way, AV files can be recorded under the directory AV_SUB_DIR1.

FIG. 26 shows the data structure of the partition space after the AV files FILE1.DAT and FILE2.DAT are recorded under the directory AV_SUB_DIR1 by the process shown in FIG. 25.

In FIG. 26, of the AV reserved area allocated to the directory AV_SUB_DIR1, it is used to record a new file entry from a logical block having a large LBN, while the file identification descriptor is an extent that is a recorded extent of the directory AV_SUB_DIR1. It is recorded in the form of being added at the end of (1). If a predetermined number of AV files are recorded under the directory AV_SUB_DIR1, another subdirectory is created under the directory AV_DIR1 and the AV files are recorded under that directory.

To play an AV file from a disc having the data structure shown in FIG. 26, follow the procedure below. First, the ROOT directory is read, and the directories AV_DIR1 and the directory AV_SUB_DIR1 are read. At this time, the part corresponding to the AV reserved area allocated to the directory AV_SUB_DIR1, that is, LBN = 251 to 400 is read into the memory unit 4.

It then scans the recorded extents in directory AV_SUB_DIR1 to get the names of the files under directory AV_SUB_DIR1.

Next, the data of the file is accessed and the file is played according to the procedure described in the conventional technique.

When reading a file under another AV subdirectory, access the file after reading the AV reserved area allocated to that AV subdirectory in the same way.

As described above, according to the sixth embodiment, even when the directory has a hierarchical structure, it is possible to significantly reduce the number of seek operations when creating a file or reading a file. ..

The new AV subdirectory may be created, for example, when instructed by the user or when a predetermined number of files are recorded under the AV subdirectory.

(Embodiment 7) Hereinafter, the AV data recording device according to the seventh embodiment of the present invention will be described with reference to the drawings. In the seventh embodiment, when the AV directory has a hierarchical structure, the case where the AV reserved area is also allocated to the AV subdirectory will be described.

First, in the seventh embodiment, the structure of the file / directory immediately after the directory for recording the AV directory is created is the same as that in FIG. The data structure in the partition space is the same as in FIG. FIG. 27 shows a processing flow diagram when a subdirectory is further created under the AV directory on a disk having such a data structure.

In FIG. 27, first, the contents of LBN = 0 to 250 on the disk 1 are read into the memory unit 4 (step S241). Next, the information in the AV directory reserved area on the memory unit 4 is scanned, and it is determined whether or not there is a sufficient unrecorded area for newly recording the file identification descriptor and the file entry for the AV subdirectory. (Step S242).

If it is determined that there is not enough unrecorded area (step S242: No), error processing is performed and the AV subdirectory creation process ends. If it is determined that there is sufficient unrecorded area (step S242: Yes), the file identification descriptor, file entry, and AV subdirectory file are recorded in the unrecorded area in the AV reserved area on the memory unit 4 (step). S243).

At this time, when the file identification descriptor, the file entry, and the AV subdirectory file are recorded, the extent size of the AV_DIR1 directory changes, so the allocation descriptor of the file entry of the AV_DIR1 directory is rewritten accordingly. Specifically, it is a rewriting operation that changes the extent length of extent (1) by adding a file identification descriptor and excludes the part where the file entry or directory file is recorded from extent (2).

Next, the space bitmap information on the memory unit 4 is updated if necessary (step S244). Then, the contents on the memory unit 4 are written back to the positions of LBN = 0 to 250 on the disk 1 (step S245).

By this series of processing, the AV subdirectory AV_SUB_DIR1 is created under the directory AV_DIR1. The directory structure after creating the AV subdirectory is the same as the structure shown in FIG. 23.

Figure 28 shows the partition structure after the AV subdirectory is created. In FIG. 28, as in the first embodiment, the file identification descriptor is recorded in the form of being added to the end of the extent (1) which is the recorded extent of the subdirectory AV_SUB_DIR1. On the other hand, the recording of new file entries and directory files is used for recording from the logical block having a large LBN in the AV directory reserved area.

Next, FIG. 29 shows a flow chart of processing when recording an AV file on a disk having such a data structure. In FIG. 29, first, the contents of LBN = 0 to 250 on the disk 1 are read onto the memory unit 4 (step S261), the information in the AV directory reserved area on the memory unit 4 is scanned, and the file identification descriptor and the file are displayed. Determine if there is enough unrecorded space to record a new entry (step S262).

If it is determined that there is not enough unrecorded area (step S262: No), error processing is performed and the recording processing of the AV file is terminated. When it is determined that there is sufficient unrecorded area (step S262: Yes), the file identification descriptor and the file entry are recorded in the unrecorded area in the AV reserved area on the memory unit 4 (step S263).

Next, the space bitmap on the memory unit 4 is scanned to determine the presence or absence of the number of unallocated logical blocks required to record the AV file (step S264). When it is determined that there are no required number of unallocated logical blocks (step S264: No), error processing is performed and the recording processing of the AV file is terminated. When it is determined that there are a required number of unallocated logical blocks (step S264: Yes), data is recorded for the logical blocks corresponding to such regions (step S265).

After recording the AV file data, record the location and length of the extent of the AV file in the allocation descriptor in the file entry on the memory section 4 created in step S263 in order to update the file management information of the AV file. (Step S266).

Next, with respect to the space bitmap on the memory unit 4, the bit corresponding to the logical block in which the data was recorded in step S265 is changed to '1' indicating that it is allocated (step S267). Then, the contents on the memory unit 4 are written back to the positions of LBN = 0 to 250 on the disk 1 (step S268). In this way, it is possible to record AV files under the subdirectory AV_SUB_DIR1.

Figure 30 shows the structure of the partition space after the AV file FAILE1.DAT is recorded in the AV subdirectory AV_SUB_DIR1 and a new subdirectory AV_SUB_DIR2 is created. In FIG. 30, the file management information of the AV subdirectory and the AV file recorded under the AV subdirectory and the AV subdirectory file itself are recorded in the AV reserved area of the directory AV_DIR1. With such a structure, it is possible to reduce the seek operation for the disk even when the files under different AV subdirectories are continuously accessed. The directory structure in this case is as shown in FIG. 31.

When playing an AV file from a disk having such a data structure, first read the ROOT directory and then read the directory AV_DIR1. At this time, the area including the part corresponding to the AV reserved area allocated to the directory AV_DIR1, that is, LBN = 0 to 250 is read into the memory unit 4.

Next, the extent of the subdirectory AV_SUB_DIR1 in the memory unit 4 is scanned to obtain the file name recorded under the subdirectory AV_SUB_DIR1.

Even when reading a file under another AV subdirectory, the extent of the directory file has already been read in the memory section 4, so the target file can be accessed by scanning such information.

As described above, according to the seventh embodiment, it is possible to significantly reduce the number of seek operations when creating a file or reading a file even when the directory has a hierarchical structure. It becomes.

(Embodiment 8) In the recording of an AV file, for the purpose of real-time recording, it is common practice to skip-record defective blocks as described in International Publication W098 / 14938 without performing replacement processing. ..

On the other hand, the file management information recorded in the AV reserved area needs to be recorded with high reliability because if the information cannot be read due to a defect in the disk or the like, the file cannot be played back.

Therefore, in the AV data recording method according to the eighth embodiment, when a directory for recording an AV file is created and an AV reserved area is secured, a defective block is inspected at the same time, and if a defective block is found, the block is detected. Control to secure the AV reserved area by using the next block without using it.

This enables highly reliable recording without impairing the continuity of the data to be recorded in the AV reserved area.

(Embodiment 9) When the AV file has a thumbnail image as a separate file, a continuous area for recording the thumbnail file is secured as a reserved area.

As a result, when trying to display a thumbnail list of recorded files to the user, the thumbnails are recorded in the continuous area, so that the thumbnails can be displayed at high speed.

(Embodiment 10) In the above-described embodiment, when a new AV file is recorded, it is sufficient to determine the presence or absence of an unrecorded area in the AV reserved area and record a new AV file. If it is determined that there is no unrecorded area, error processing is performed and the recording of the AV file is terminated.

However, in such a process, even if the free space of the disk remains, a new problem arises that the AV file cannot be recorded any more when the unrecorded area disappears in the AV reserved area.

Therefore, the tenth embodiment is characterized in that when the capacity of the AV reserved area is insufficient, a new AV reserved area is secured and then the AV file is recorded.

FIG. 32 shows the partition space in which there is no unrecorded area in the AV reserved area by recording the AV file. In this case, a plurality of AV files are recorded in LBN = 251 to 685, and file management information such as file entries for those AV files are recorded in the AV reserved area LBN = 86 to 250, all of which are recorded. It has been recorded. Therefore, even if a new AV file is to be recorded, the AV file cannot be recorded because there is no unrecorded area in the AV reserved area.

Therefore, a new AV reserved area is secured as an allocated and unrecorded extent of the directory AV_DIR1. The process of securing a new AV reserved area is performed by the procedure shown in FIG. 33.

In FIG. 33, first, the space bitmap information is scanned to determine the presence or absence of the number of consecutive unallocated logical blocks required to secure a new AV reserved area (step S331). When it is determined that the required number of logical blocks does not exist (step S331: No), error processing is performed and the operation of securing the AV reserved area ends (step S332).

If it is determined that there are the required number of logical blocks (step S331: Yes), the unallocated area is secured as an allocated and unrecorded extent (3) in the directory AV_DIR1. That is, the information about the extent position and extent length of this extent (3) is recorded in the allocation descriptor in the file entry of the directory AV_DIR1 (step S333).

Then, for the space bitmap, the bit corresponding to the logical block of extent (3) is changed to '1' indicating "allocated" (step S334).

Figure 34 shows the state of the partition space after securing a new AV reserved area. In FIG. 34, as an example, LBN = 686 to 850 is secured as a new AV reserved area.

The processing procedure for securing a new AV reserved area is not limited to the above-mentioned order. For example, after determining the presence or absence of a necessary logical block, the space bitmap information is changed, and then the directory AV_DIR1 Information about extents (3) may be recorded in the allocation descriptor in the file entry.

Further, as shown in the second embodiment, when the AV reserved area is reserved as the extent of the management file AVFILES.IFO, the new AV reserved area is also used as the extent of the management file AVFILES.IFO. You just have to secure it.

Further, when the AV reserved area is secured as a named stream, the AV reserved area may be secured as a new AV reserved area as a new named stream.

<figref num="1">Configuration diagram of the AV data recording device according to the first embodiment of the present invention.</figref><figref num="2">Illustrated diagram of the initial directory structure in the AV data recording apparatus according to the first embodiment of the present invention.</figref><figref num="3">Illustrated diagram of the initial partition space in the AV data recording apparatus according to the first embodiment of the present invention.</figref><figref num="4">Flow chart of AV file recording process in the AV data recording device according to the first embodiment of the present invention.</figref><figref num="5">Illustrated diagram of the partition space after recording an AV file in the AV data recording apparatus according to the first embodiment of the present invention.</figref><figref num="6">Illustrated diagram of the initial directory structure in the AV data recording apparatus according to the second embodiment of the present invention.</figref><figref num="7">Illustrated diagram of the initial partition space in the AV data recording apparatus according to the second embodiment of the present invention.</figref><figref num="8">Illustrated diagram of the initial directory structure in the AV data recording apparatus according to the third embodiment of the present invention.</figref><figref num="9">Illustrated diagram of the initial partition space in the AV data recording apparatus according to the third embodiment of the present invention.</figref><figref num="10">Illustrated diagram of AV file configuration in the AV data recording device according to the fourth embodiment of the present invention.</figref><figref num="11">Explanatory drawing of time map in AV data recording apparatus which concerns on Embodiment 4 of this invention</figref><figref num="12">Explanatory drawing of time map in AV data recording apparatus which concerns on Embodiment 4 of this invention</figref><figref num="13">Explanatory drawing of time map in AV data recording apparatus which concerns on Embodiment 4 of this invention</figref><figref num="14">Illustrated diagram of the initial partition space in the AV data recording apparatus according to the fourth embodiment of the present invention.</figref><figref num="15">Flow chart of AV file recording process in the AV data recording device according to the fourth embodiment of the present invention.</figref><figref num="16">Illustrated diagram of the partition space after recording an AV file in the AV data recording apparatus according to the fourth embodiment of the present invention.</figref><figref num="17">Illustrative diagram of the data structure of a still image file in the AV data recording device according to the fifth embodiment of the present invention.</figref><figref num="18">Illustrative diagram of the data structure of a still image file in the AV data recording device according to the fifth embodiment of the present invention.</figref><figref num="19">Illustrated diagram of the multi-directory structure in the AV data recording apparatus according to the fifth embodiment of the present invention.</figref><figref num="20">Illustrated diagram of the initial directory structure in the AV data recording apparatus according to the sixth embodiment of the present invention.</figref><figref num="21">Illustrated diagram of the initial partition space in the AV data recording apparatus according to the sixth embodiment of the present invention.</figref><figref num="22">Flow chart of AV file recording process in the AV data recording device according to the sixth embodiment of the present invention.</figref><figref num="23">Illustrated diagram of the directory structure after creating a subdirectory in the AV data recording apparatus according to the sixth embodiment of the present invention.</figref><figref num="24">Illustrated diagram of the partition space after creating the subdirectory in the AV data recording apparatus according to the sixth embodiment of the present invention.</figref><figref num="25">Flow chart of AV file recording process in the AV data recording device according to the sixth embodiment of the present invention.</figref><figref num="26">Illustrated diagram of the partition space after recording an AV file in the AV data recording apparatus according to the sixth embodiment of the present invention.</figref><figref num="27">Flow chart of subdirectory creation process in the AV data recording device according to the seventh embodiment of the present invention.</figref><figref num="28">Illustrated diagram of the partition space after creating the subdirectory in the AV data recording apparatus according to the seventh embodiment of the present invention.</figref><figref num="29">Flow chart of AV recording processing to a subdirectory in the AV data recording device according to the seventh embodiment of the present invention.</figref><figref num="30">Or to the seventh embodiment of the present invention illustration of partition space after an AV file recorded in the subdirectory in the AV data recording apparatus mow</figref><figref num="31">Illustrated diagram of the directory structure after creating a subdirectory in the AV data recording apparatus according to the seventh embodiment of the present invention.</figref><figref num="32">Illustrated diagram of the partition space before securing a new AV reserved area in the AV data recording apparatus according to the tenth embodiment of the present invention.</figref><figref num="33">Flow chart of AV file recording process in the AV data recording device according to the tenth embodiment of the present invention.</figref><figref num="34">Illustrated diagram of the partition space after securing a new AV reserved area in the AV data recording apparatus according to the tenth embodiment of the present invention.</figref><figref num="35">Configuration diagram of a conventional AV data recording device</figref><figref num="36">Illustrative diagram of the volume space structure in a conventional AV data recording device</figref><figref num="37">Illustrated diagram of partition space in a conventional AV data recording device</figref><figref num="38">Illustrative diagram of the directory structure in a conventional AV data recording device</figref><figref num="39">Illustrative diagram of file entries in a conventional AV data recording device</figref><figref num="40">Illustrative diagram of allocation descriptor in a conventional AV data recording device</figref><figref num="41">Interpretation explanatory diagram of extent length in a conventional AV data recording device</figref><figref num="42">Diagram of directory file configuration in a conventional AV data recording device</figref><figref num="43">Illustrative diagram of the hierarchical structure of files in a conventional AV data recording device</figref><figref num="44">Illustrated diagram of extended file entry in a conventional AV data recording device</figref><figref num="45">Schematic diagram of the structure of a stream directory file in a conventional AV data recording device</figref><figref num="46">Illustrative diagram of the hierarchical structure of a named data stream in a conventional AV data recording device</figref><figref num="47">Illustrative diagram of the partition space after recording in a conventional AV data recording device</figref>

Code description

1,101 Disk 2,102 Recording medium drive unit 3,103 Recording / playback unit 4,104 Memory unit 5,105 Disk drive unit 6,106 AV signal processing unit 7,107 System control unit