JP2008305546A - Information recording and reproducing device and method, program storing medium, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To read out a grouped file at high speed. <P>SOLUTION: An information recording and reproducing device sets Gathered information, records it on a recording medium and reads out the Gathered information, the Gathered information including information on head and end positions of a group-managed File Structure, a group-managed file (Files grouped in Fig. 14) and a backup of the grouped file (Files Back Up (grouped) in Fig. 14) among information recorded on the recording medium in a UDF format. In such a case, the information recording and reproducing device reads out the Gathered information first, thereby reads out all files of a group containing desired files at once. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an information recording / reproducing apparatus and method, a program storage medium, and a program, and more particularly, to a file system that does not have a function of grouping and recording or reproducing a specific file for each attribute. The present invention relates to an information recording / reproducing apparatus and method, a program storage medium, and a program, which can be processed at high speeds.

  A technique for recording a file on a large-capacity recording medium is spreading.

  Various formats for recording files on these large-capacity recording media have been proposed.

For example, there is a UDF (Universal Disc Format) used in a DVD (Digital Versatile Disc) (for example, see Non-Patent Document 1).

Universal Disk Format Specification Revision 2.01 March 15, 2000 Optical Storage Technology Association

  However, in the above UDF, for example, it has a structure capable of recording in a state where a large number of files are scattered, and information indicating the position of the file is stored in a nested state between files. Therefore, in order to finally obtain the file to be read, a large number of addresses must be accessed. When a moving image recorded on a recording medium in such a state is reproduced, the timing of reproduction is As a result, there is a problem that smooth video cannot be reproduced.

  The present invention has been made in view of such a situation, and in particular, in the case of a format that can be recorded in a state where a large number of files are scattered like a UDF, it is necessary to read at high speed. Files are managed by grouping them to improve the reading speed, and as a result, it is possible to guarantee the time required for playing back moving images.

  An information rule reproducing device according to one aspect of the present invention includes: a recording unit that records a file managed by a UDF that does not have a group management mechanism on a recording medium; and the file based on an attribute thereof. The first files that need to be grouped are grouped, the second file that does not need to be grouped among the files, and the arrangement of each group of the first files on the recording medium And setting means for setting the first file and the second file on a recording medium based on the arrangement set by the setting means, and the arrangement of the first file and the second file Control means for controlling the recording means so as to record the arrangement information based on the recording medium at a predetermined position of the recording medium. With placing the body of the management file to the beginning of the partition, placing the backup files of the body of the file to the end portion of the partition.

  The recording means can further arrange the metadata file at the beginning of the partition and arrange the backup file of the metadata file at the end of the partition.

  The control unit causes the first file and the second file to be recorded on a recording medium based on the arrangement set by the setting unit, and includes the first file and the second file. The recording means can be controlled to record arrangement information based on the arrangement in a user data area of the recording medium.

  The control unit causes the first file and the second file to be recorded on a recording medium based on the arrangement set by the setting unit, and includes the first file and the second file. The recording means can be controlled to record arrangement information based on the arrangement at a fixed address in the user data area of the recording medium.

  The control unit causes the first file and the second file to be recorded on a recording medium based on the arrangement set by the setting unit, and includes the first file and the second file. The recording means can be controlled to record the arrangement information based on the arrangement in an area where general recording data of the recording medium is not recorded.

  An information recording / reproducing method according to an aspect of the present invention includes a recording step of recording a file managed by a UDF that does not have a group management mechanism on a recording medium, and the file based on the attribute thereof. The first files that need to be grouped are grouped, the second file that does not need to be grouped among the files, and the arrangement of each group of the first files on the recording medium And setting the first file and the second file on a recording medium on the basis of the arrangement set in the processing of the setting step, and the first file and the second file A control step for controlling the processing of the recording step so as to record the arrangement information based on the arrangement at a predetermined position of the recording medium. Seen, wherein the recording step is configured to place the body of the group management file at the beginning of the partition, placing the backup files of the body of the file to the end portion of the partition.

  In the recording step, the metadata file can be arranged at the beginning of the partition, and the backup file of the metadata file can be arranged at the end of the partition.

  According to one aspect of the present invention, there is provided a program storage medium program including: a file managed by a UDF that does not have a group management mechanism; and a first file that needs to be grouped among the files based on an attribute thereof. A setting step for setting the arrangement on the recording medium for the second file that is not required to be grouped among the files and each group of the first file, and processing of the setting step The first file and the second file are recorded on the recording medium based on the arrangement set in step 1, and arrangement information based on the arrangement of the first file and the second file is recorded on the recording medium. A control step for controlling to record at a predetermined position of the file, wherein the recording step includes a group-managed file body Together arranged at the beginning of the partition, placing the backup files of the body of the file to the end portion of the partition.

  In the recording step, the metadata file can be arranged at the beginning of the partition, and the backup file of the metadata file can be arranged at the end of the partition.

  The program according to one aspect of the present invention groups a file managed by a UDF that does not have a group management mechanism into a first file that needs to be grouped among the files based on the attributes thereof. The setting step for setting the arrangement on the recording medium for the second file that does not need to be grouped among the files and the group of the first file, and the setting step are set. Based on the arrangement, the first file and the second file are recorded on the recording medium, and arrangement information based on the arrangement of the first file and the second file is stored at a predetermined position on the recording medium. This is a control step that controls the recording of data in a group, and when the body of a group-managed file is placed at the beginning of a partition , To execute processing comprising the steps of placing the end portion of the backup file partition body of the file to the computer.

  In the control step, the metadata file may be arranged at the head portion of the partition, and the backup file of the metadata file may be arranged at the tail portion of the partition.

  The information recording / reproducing apparatus of the present invention may be an independent apparatus or a block that performs information processing.

  According to the present invention, a group-managed file recorded on a recording medium can be read at high speed.

  FIG. 1 is a diagram showing a configuration of an embodiment of a recording / reproducing apparatus 1 to which the present invention is applied.

  A CPU (Central Processing Unit) 11 executes various processes according to a program stored in a ROM (Read Only Memory) 12 or a storage unit 18. A RAM (Random Access Memory) 13 appropriately stores programs executed by the CPU 11 and data. The CPU 11, ROM 12, and RAM 13 are connected to each other by a bus 14.

  An input / output interface 15 is connected to the CPU 11 via the bus 14. The input / output interface 15 is connected to an input unit 16 including a keyboard, a mouse, and a microphone, and an output unit 17 including a display and a speaker. The CPU 11 executes various processes in response to commands input from the input unit 16. Then, the CPU 11 outputs an image, sound, or the like obtained as a result of the processing to the output unit 17.

  The storage unit 18 connected to the input / output interface 15 is composed of, for example, a hard disk and stores programs executed by the CPU 11 and various data. The communication unit 19 communicates with an information processing apparatus such as an external server via a network represented by the Internet or an intranet.

  The storage unit 18 stores various programs, and the CPU 11 reads out these programs and executes corresponding processes. The storage unit 18 stores, for example, an OS that is a basic program and a driver. The program stored in the storage unit 18 may be acquired and stored via the communication unit 19 in addition to the above.

  The image / audio codec 20 is read from the magnetic disk 41, the optical disk 42, the magneto-optical disk 43, the semiconductor memory 44, or the recording medium 81 (FIG. 2) of the recording / reproducing mechanism unit 22 connected to the drive 30. The image or audio file compressed by a predetermined compression method is expanded in a predetermined manner and supplied to the external connection I / F (Interface) 21 or the output unit 17. The image / audio codec 20 compresses an image signal and an audio signal supplied from the input unit 16 and the external connection I / F 21 by a predetermined method, and connects the magnetic disk 41, the optical disk 42, and the magneto-optical device connected to the drive 30. Recording is performed on the disk 43, the semiconductor memory 44, or the recording medium 81 (FIG. 2) of the recording / reproducing mechanism unit 22.

  The recording / reproducing mechanism 22 records predetermined information on a recording medium 81 (FIG. 2) such as a Blu-Ray Disc (trademark), which is a magneto-optical recording medium, or is recorded on the recording medium 81. Read information. The detailed configuration of the recording / reproducing mechanism 22 will be described later with reference to FIG.

  The drive 30 connected to the input / output interface 15 drives a magnetic disk 41, an optical disk 42, a magneto-optical disk 43, or a semiconductor memory 44 when they are mounted, and programs and data recorded there. Get etc. The acquired program and data are transferred to and stored in the storage unit 18 as necessary.

  Next, the operation of the recording / reproducing apparatus 1 in FIG. 1 will be described.

  When the CPU 11 is instructed by the input unit 16 to record the input data supplied via the external connection I / F 21, the CPU 11 performs image / audio based on a program stored in the ROM 12, the RAM 13, or the storage unit 18. The codec 20 is controlled, the input data is compressed by a predetermined compression method, supplied to the recording / reproducing mechanism 22, and the input data is recorded on a recording medium 81 (FIG. 2) described later.

  Further, when the input unit 16 instructs the reproduction of the data recorded on the recording medium 81 attached to the recording / reproducing mechanism unit 22, it is based on a program stored in the ROM 12, the RAM 13, or the storage unit 18. Then, the recording / playback mechanism unit 22 is controlled to play back the data recorded on the recording medium 81 and supplied to the video / audio codec 20, and the video / audio codec 20 is controlled to expand the input data by a predetermined expansion method. Thus, the data is output to the outside via the external connection I / F 21, or is output to the output unit 17 to be displayed or sound is output.

  Next, a detailed configuration of the recording / reproducing mechanism unit 22 will be described with reference to FIG.

  The control unit 51 controls the entire operation of the recording / reproducing mechanism unit 22, and controls the recording unit 52 based on the control signal supplied from the CPU 11, so that the recording / reproducing block 53 is connected to the recording medium 81. The information is recorded, or the reproducing unit 54 is controlled to cause the recording / reproducing block 53 to read the information recorded on the recording medium 81.

  The file system information generating unit 62 of the control unit 51 needs file system information necessary for grouping (also referred to as group management) a file having a predetermined attribute in the input data based on the file attribute of the input data. A Gathered file is generated and supplied to the recording unit 52. This gathered file (or gathered.inf file) has a management structure for grouping and managing files that need to be read first among the files recorded on the recording medium 81 according to attributes. It is recorded. Details of the gathered file will be described later.

  The file system information recognition unit 61 of the control unit 51 reads the file system information supplied from the reproduction unit 54, and reads a predetermined file based on the file system information. Further, the file system information recognition unit 61 reads the gathered file and analyzes the information recorded in the gathered file, thereby recognizing the management structure of the files managed as a group. And the control part 51 (file system information recognition part 61) controls the reading part 91 so that a file may be read based on this management structure. In the following, the information recorded in the gathered file is also referred to as gathered information.

  The recording / reproducing block 53 is controlled by the writing unit 73 or the reading unit 91 and physically records or reproduces information on the recording medium 81. The recording medium 81 can be recorded mechanically, optically, magnetically, or magneto-optically, and can be repeatedly written (for example, a DVD-RW (Digital Versatile Disc-Rewritable), DVD-RAM ( Digital Versatile Disc-Random Access Memory), which can be written only once (for example, DVD-R (Digital Versatile Disc-Recordable), DVD-ROM (Digital Versatile Disc-Read Only Memory) Any disc format recording medium capable of recording or reproducing data can be used. Accordingly, the recording / reproducing block 53 may be any as long as it can record / reproduce corresponding to these recording media 81.

  The ECC encoder 71 adds an error correction code to the input, encodes it, and outputs it to the modulator 72. The modulation unit 72 modulates the data input from the ECC encoding unit 71 and outputs the data to the writing unit 73. The writing unit 73 supplies the data input from the modulation unit 72 to the recording / reproducing block 53 and causes the recording medium 81 to execute processing.

  Information recorded in the recording medium 81 is read out by the reading unit 91 of the reproducing unit 54. The demodulating unit 92 demodulates the data read from the recording medium 81 by the reading unit 91 and supplies the demodulated data to the ECC decoding unit 93. The ECC decoding unit 93 separates the data supplied from the demodulation unit 92 into a normal file (for example, AV (Audio Visual) stream data) and file system information, and outputs the normal file as output data. The file system information is output to the control unit 51.

  Next, with reference to FIG. 3, a file management structure of input data managed by the file system information generation unit 62 as a group will be described. The recording medium 81 basically records files in UDF format. Accordingly, each file is recorded on the recording medium 81 in the UDF format in accordance with the management structure shown below.

  FIG. 3 shows an example of managing various data files when AV stream data is recorded on a rewritable recording medium. The management structure is the Blu-Ray Disc Rewritable (trademark) standard. (The management structure conforms to the Blu-Ray Disc Rewritable (trademark) standard, but the recording format is the UDF format). In FIG. 3, three layers of a content management layer, a playlist layer, and a clip layer are shown from the top in the figure.

  Here, the playlist management table 111 and the thumbnail management table 112 belong to the content management layer. Also, playlists 113-1 to 113-3 belong to the playlist layer. Furthermore, clip information 121-1 to 121-3 belongs to the clip layer. In the following description, when it is not necessary to distinguish the playlists 113-1 to 113-3 and the clip information 121-1 to 121-3, the playlist 113 and the clip information 121 are simply referred to. The same applies to other configurations.

  A combination of the AV stream 131 file and the clip information 121 file (having AV stream attribute information) is particularly called a clip. The AV stream 131 is, for example, MPEG-TS (Moving Picture Experts Group-Transport Stream) data, and is a file having a structure in which information such as Video, Audio, or subtitles is multiplexed. In addition, the AV stream 131 may be multiplexed with command information for performing control during reproduction. In the figure, an example in which command information is multiplexed is shown.

  A playlist has a structure that has multiple play items that refer to a specific range of a clip by using the playback start point and playback end point, and provides a function to continuously play multiple playback sequences with one playlist. is doing. Furthermore, a playlist management table 111 for presenting a list of playlists to the user, a thumbnail management table 112 used for the thumbnail display function, and thumbnail files 141-1 and 141-2 and thumbnail files 151- 1,151-2 exists.

  A pair of one AV stream 131 and its attached information is considered as one object, which is called a clip. The AV stream file is called an AV stream file, and the attached information is called clip information 121.

  In general, a file used in a computer or the like is handled as a byte string, but the content of the AV stream 131 is expanded on the time axis, and the playlist 113 designates an access point in the clip information 121 mainly by a time stamp. To do. When the playlist 113 gives the time stamp of the access point in the clip, the clip information 121 is used to find address information (data byte position) in the AV stream 131 at which to start decoding the stream. It is done.

  The playlist 113 is introduced for the purpose of allowing a user to select a playback section that the user wants to see from clips and easily edit it. One playlist 113 is a collection of playback sections in a clip. One playback section in a clip is called a play item, which is represented by a pair of IN point and OUT point on the time axis. Therefore, a playlist is a collection of play items.

  In FIG. 3, the files are grouped as follows according to the usage / update frequency and the maximum total size of the files belonging to the group. The playlist management table 111, thumbnail management table 112, and playlist 113 are in group 1, clip information 121 is in group 2, menu thumbnail files 141 and 142 are in group 3, and mark thumbnail files 151 and 152 are in group 4. are categorized.

  These files to be grouped are management data required when the AV stream 131 is reproduced. By extracting these management data and managing them in one place, the management data can be read quickly. As a result, AV stream data can be played back at high speed.

  In the above, the example of grouping the management data files of the AV stream 131 has been described. However, it is also possible to group files that are not defined in the Blu-ray Disc Rewritable standard. That is, in the figure, a group X is defined as a file group different from the management data file of the AV stream 131, and the files 161-1 and 161-2 belong to the group. Note that files 171-1 and 171-2 in the figure are files that are not grouped. Further, since the AV stream 131 is not management data, it is not managed as a group.

  FIG. 4 shows an example of a directory structure of Blu-Ray Disc Audio Visual (BDAV) information defined in Blu-Ray Disc Rewritable Format (BD-RE) recorded on the recording medium 81. Other directories may be created under the root directory, but they are ignored for UDF format records.

  As shown in the figure, the root directory includes one directory.

  In the “BDAV” directory, all files and directories defined by the BDAV application format are recorded. Further, the “BDAV” directory includes directories described below.

  A database file of the playlist 113 is recorded in the “PLAYLIST” directory. This directory is set even when there is no playlist 113.

  A database of clips is recorded in the “CLIPINF” directory. This directory is set even when there is no clip.

  An AV stream file is recorded in the “STREAM” directory. This directory is set even when there is no AV stream file.

  The “PLAYLIST” directory records two types of PlayList files, Real PlayList and Virtual PlayList. In the case of FIG. 4, 11111.rpls and 22222.vpls are recorded. Of these, the file indicated by “xxxxx.rpls” holds information related to one Real PlayList, and one file is created for each playlist. Here, “xxxxx” is five numbers from 0 to 9.

  The file indicated by “yyyyy.vpls” holds information related to one Virtual PlayList, and one file is created for each playlist. The file name is “yyyyy.vpls”. Here, “yyyyy” is five numbers from 0 to 9.

  A Real PlayList is considered to share the stream portion of the clip it references. That is, the Real PlayList occupies the data capacity corresponding to the AV stream portion of the clip referenced by the Real PlayList in the disc. When the AV stream is recorded as a new clip, a Real PlayList that refers to the reproducible range of the entire clip is generated. When a part of the playback range of the Real PlayList is erased, the data of the clip stream part to which it refers is also erased.

  The Virtual PlayList is regarded as not sharing the clip data. Even if the VirtualPlayList is changed or deleted, the clip does not change anything. In the description of the present specification, the Real PlayList and the Virtual PlayList are collectively referred to simply as a play list.

  The “CLIPINF” directory holds one file corresponding to each AV stream file. In the case of FIG. 4, 01000.clpi and 02000.clpi are held.

  A file indicated by “zzzzz.clpi” is clip information 121 corresponding to one AV stream 131. The file name is “zzzzz.clpi”, where “zzzzz” is five numbers from 0 to 9.

  The “STREAM” directory holds AV stream files. In the case of FIG. 4, 01000.m2ts and 02000.m2ts are held.

  The file indicated by “zzzzz.m2ts” is the AV stream 131 file. The file name is “zzzzz.m2ts”, where “zzzzz” is five numbers from 0 to 9. Note that the same five numbers “zzzzz” are set as file names in one AV stream 131 file and the corresponding clip information 121.

  The “BDAV” directory holds menu1.tdt and menu2.tdt corresponding to the thumbnail files 141-1 and 141-2 immediately below, and also corresponds to the thumbnail files 151-1 and 151-2. mark1.tdt and mark2.tdt are held. Furthermore, info.bdav corresponding to the playlist management table 111 and menu.tidx and mark.tidx corresponding to the thumbnail management table 112 are held.

  In addition, a “DATA1” directory and a “DATA2” directory are set immediately under the “root” directory, and File1.dat, corresponding to the files 161-1 and 161-2 are respectively managed as groups. File2.dat... And FileA.dat, FileB.dat... Corresponding to the files 171-1 and 171-2 are held.

  In the files and directories managed under the directory shown in FIG. 4, as shown in FIG. 3, menu1.tdt and menu2.tdt corresponding to the thumbnail files 141-1 and 141-2 are group 3 and are thumbnail files. Mark1.tdt and mark2.tdt corresponding to 151-1 and 151-2 are group 4. info.bdav corresponding to the playlist management table 111, menu.tidx, mark.tidx corresponding to the thumbnail management table 112, In addition, 11111.rpls and 22222.vpls held in the "PLAYLIST" directory are grouped as group 1, and 01000.clpi and 02000.clpi held in the "CLIPINF" directory are grouped as group 2, respectively. Being held.

  In addition to the files managed by the BDFS group, File1.dat and File2.dat corresponding to the files 161-1 and 161-2 held in the “DATA1” directory are grouped as a group X. Yes.

  3 and 4 show the management structure in grouping in the case of recording on the recording medium 81 in the UDF format based on the Blu-Ray Disc Rewritable (rewritable recording medium) standard. 5 and 6, an example of a grouping management structure (logical format) in Blu-Ray Disc ROM (read-only recording medium) is shown. FIG. 5 shows an example in which HD (High Density) movie content is recorded.

  In FIG. 5, playlists 221-1 through 221-3, clip information 231-1 through 231-3, AV streams 232-1 through 232-3, files 251-1 and 251-2, and file 261- 1, 261-2 are playlists 113-1 to 113-3, clip information 121-1 to 121-3, AV streams 131-1 to 131-3, files 161-1 and 161-2 in FIG. The file 171-1 and 171-2 are the same as the file 171-1 and 171-2, and the description thereof is omitted as appropriate.

  Two layers of playback programs 211-1 and 211-2 (movie objects) and titles 201 and 202 exist above the clip information 231 and the playlist 221 described in FIG. 3. The playback program 211 (movie object) programmatically provides functions necessary for presenting HD movie content, such as specifying the playlist to be played, responding to user operations, jumping between titles 201 or 202, and branching of the playback sequence. is doing.

  The titles 201 and 202 can be recognized by the user and used as an index for starting the reproduction of the content. The titles 201 and 202 have a structure for designating one movie object to be executed. In addition to normal titles, there are titles that are automatically played back first and titles for displaying menus.

  The applications (application programs) 203 and 204 are for executing games and Web contents that are extended applications. At this time, the reproduction programs (execution objects) 212-1 and 212-2 are activated and executed. The playback program 212 may use a playlist or may not use a playlist. Further, the reproduction program 212 can refer to any image file 241, audio file 242, and file 243 in these application programs 203 and 204.

  The numbers of the titles 201 and 202 indicating the HD movie content and the applications 202 and 203 can be further increased, and are shown as Other 205 in FIG. Also, it is possible to record on the recording medium 81 in a mixed manner, and FIG. 5 shows a mixed state.

  Also in FIG. 5, as in the case shown in FIG. 3, files are grouped as follows according to the usage / update frequency and the maximum total size of files belonging to the group. That is, titles 201 and 202, applications 203 and 204, Other 205, playback programs 211-1, 211-2, 212-1, 212-1, and playlists 221-1 to 221-3 are clipped to group A. Information 231 is classified as group B, and image file 241, audio file 242, and file 243 are classified as group C.

  Note that the groups A, B, and C in FIG. 5 are simply named for convenience as in the case of the groups 1, 2, 3, and 4 in FIG. 3, and are the same in terms of a group of files to be processed. belongs to.

  FIG. 6 shows an example of a directory structure of Blu-Ray Disc Movie (BDMV) information defined in Blu-Ray Disc ROM Format (BD-ROM) recorded on the recording medium 81. Other directories may be created under the root directory, but they are ignored for UDF format records.

  As shown in the figure, the root directory includes one directory.

  In “BDMV”, all files and directories defined by the BDMV application format are recorded. Further, the “BDMV” directory includes directories described below.

  A database file of the playlist 221 is recorded in the “PLAYLIST” directory. This directory is set even when there is no playlist 221.

  A database of clips is recorded in the “CLIPINF” directory. This directory is set even when there is no clip.

  An AV stream file is recorded in the “STREAM” directory. This directory is set even when there is no AV stream file.

  In the “PLAYLIST” directory shown in FIG. 4, 11111.mpls and 22222.mpls are recorded. Of these, the file indicated by “xxxxx.mpls” holds information related to one Movie PlayList, and one file is created for each playlist. Here, “xxxxx” is five numbers from 0 to 9.

  The “CLIPINF” directory holds one file corresponding to each AV stream file. In the case of FIG. 5, 01000.clpi and 02000.clpi are held.

  A file indicated by “zzzzz.clpi” is clip information 231 corresponding to one AV stream 232. The file name is “zzzzz.clpi”, where “zzzzz” is five numbers from 0 to 9.

  The “STREAM” directory holds AV stream files. In the case of FIG. 5, 01000.m2ts and 02000.m2ts are held.

  The file indicated by “zzzzz.m2ts” is an AV stream 232 file. The file name is “zzzzz.m2ts”, where “zzzzz” is five numbers from 0 to 9. Note that the same five numbers “zzzzz” are set as the file name in one AV stream 232 file and the corresponding clip information 231.

  In the "BDMV" directory, Unit_Key_Gen_Value.inf and CPS_CCI.inf are held as copy control related files, and index.bdmv is held as a title management table file. . Furthermore, MoviObject.bdmv is held as a playback program management table.

  In addition, immediately under the “root” directory, a “Resource” directory, a “DATA1” directory, and a “DATA2” directory are set. These directories are not essential directories in the Blu-Ray Disc ROM Format, but are added as examples of directories for storing extended data required by the contents. In the “Resource” directory, Image.jpg, Audio.pcm, and Jimaku.txt corresponding to the image file 241, the audio file 242, and the file 243, which are files managed in groups, are held. The “DATA1” directory holds File1.dat and File2.dat corresponding to the files 251-1 and 251-2, and the “DATA2” directory holds files 261-1 and 261-2. FileA.dat, FileB.dat, etc. are stored.

  In the files and directories managed under the directory shown in FIG. 6, Unit_Key_Gen_Value.inf, CPS_CCI.inf, index.bdmv, MoviObject.bdmv, and 11111.mpls, 22222 held in the “PLAYLIST” directory .mpls is group A, 01000.clpi held in the "CLIPINF" directory, 02000.clpi is group B, and Image.jpg, Audio.pcm, held in the "Resource" directory, and , Jimaku.txt is stored as a group C.

  In addition to the files managed in the above group, File1.dat and File2.dat corresponding to the files 251-1 and 251-2 held in the “DATA1” directory are grouped as a group X.

  Next, referring to FIG. 7, a Blu-ray Disc standard file system (BDFS) is taken as an example of a file system characterized in that files to be recorded are grouped and arranged according to a specific rule for each group. I will explain.

  At the beginning and the end of the figure, there are provided areas for data margin, which are indicated as “reserved”.

  Fixed areas are allocated to portions indicated by AIA (Allocation Information Areas) 1 to 4 in the drawing, and information that is read first when information recorded on the recording medium is read is recorded. Addresses in which file system information (MIA (Management Information Area)) is stored are recorded inside AIA1 to AIA4, and access to MIA becomes possible by analyzing AIA. In the AIA, two pieces of information, MainMIA and ReservedMIA (for backup), are recorded.

  MIA stores file system information (information on directories and files on recording media) and is variable. This file system information includes information on file grouping and a method for arranging the grouped files. In the Blu-ray Disc Rewritable standard, as shown in FIG. 7, the MIA has gathered file areas (MainG1, ResG1, MainG2, ResG2, G3 in the figure) together with the following file groups 1 to 3 (MainG1, ResG1, MainG2, ResG2, G3). Gathered block in the area indicated by LB Region for gathered files in the figure). These are managed by grouping IDs called allocation classes set for each group. For example, MainG1 is allocated class 1 (AC1), MainG2 is AC2, G3 is AC3, and G4 is AC4 Has been.

  In the MIA, position information of each file is recorded. For example, as shown in FIG. 8, MainG1 records SMG1 as a start address, EMG1 as an end address, and ResG1 starts. SRG1 is recorded as an address, ERG1 is recorded as an end address, SMG2 is recorded as a start address in MainG2, EMG2 is recorded as an end address, SRG2 is recorded as a start address and ResG2 is recorded as an end address ERG2 is recorded, G3 is recorded with SG3 as the start address, EG3 is recorded as the end address, G4 is recorded with SG4 as the start address, EG4 is recorded as the end address, and MainG1 is the start address It is recorded in the range from SMG1 to the end address EMG1, ResG1 is recorded in the range from the start address SRG1 to the end address ERG1, and MainG2 is recorded from the start address SMG2. Is recorded in the range from address EMG2, ResG2 is recorded in the range from start address SRG2 to end address ERG2, G3 is recorded in the range from start address SG3 to end address EG3, and G4 is recorded from start address SG4 It is recorded in the range up to the end address EG4.

  As a result, on the recording medium on which information is recorded according to the Blu-ray Disc Rewritable standard, the file system information and the file groups of groups 1 to 3 can be acquired by one continuous area reading. Note that groups 1 to 4 in the figure correspond to the grouping method described in FIGS.

  Groups 1 to 3 are application management data in the Blu-ray Disc Rewritable standard. These files need to be read collectively from the recording medium at a high speed, and are recorded together in the gathered file area together with the MIA described above. Further, the files belonging to group 1 and group 2 are files essential for content reproduction, and even when a defective sector occurs on the recording medium, a mechanism for losing the file data as much as possible is necessary. For the files belonging to group 2, the same file is recorded in two places, the main area and the reserved area.

  Group 4 (G4 in the figure) is thumbnail information for marks. The files need to be recorded together, but are less frequently used than the groups 1 to 3, and are less likely to be read at the start of access to the recording medium. Therefore, although it is recorded in a continuous recording area as a single group, it is not recorded in the gathered file area together with other groups.

  The AV stream file has an attribute of “guaranteeing the rate at the time of reproduction”, and when the file is arranged on the recording medium, it is necessary to follow an arrangement rule for guaranteeing the rate at the time of reproduction. In the case of AV stream files, it is not necessary to group and record in a specific area as in groups 1 to 4 above. Therefore, although the attributes of the file are defined, they are not arranged together. Also, when recording general files that are not defined in the Blu-Ray Disc standard, neither the guarantee of the playback rate nor the arrangement method of recording in a specific area is required, so general files (Data in the figure) File) is recorded in another location.

  Note that the area indicated as “Free Area” in FIG. 7 is an area in which no file is recorded.

  Further, the form of the file system shown in FIG. 7 is merely an example based on the Blu-ray Disc standard file system, and may be based on other standards or rules, and is flexible. The rule may be changed.

  Next, referring to FIG. 9, the file system information and the operations in the various groups described in FIG. 7 for each of the general operation in the Blu-ray Disc Rewritable standard and the operation unrelated to the Blu-ray Disc Rewritable standard. Explain whether the file has changed.

  In FIG. 9, as examples of specific application operations, “create playlist”, “split playlist”, “join playlist”, “delete entire playlist”, “delete partial playlist”, "Editing a virtual playlist without using a bridge", "Editing a virtual playlist using a bridge", "Deleting a virtual playlist", "Dubbing sound settings", "Change playlist display order", "Menu" "Add thumbnails" and "Add mark thumbnails" are listed. Examples of operations other than specific application operations include "Adding non-standard files (for JPEG images, etc.)" and " "Deleting non-standard files".

  Further, in FIG. 9, changes occur in each of the MIA, the files of groups 1 to 4 (G1 to G4 in the figure), the AV stream (AV Stream), and the non-application file in accordance with various operations. Items are marked with a circle, and those without change are marked with “-”.

  As shown in FIG. 9, in the “playlist creation” process and the “virtual playlist edit without bridge” process, the MIA, group 1 and 2 files, and AV stream are changed, "Playlist split" process, "Playlist merge" process, "Delete entire playlist" process, "Delete partial playlist" process, "Edit virtual playlist using bridge" process, "Virtual play" In the “delete list” process, “after-recording audio setting” process, and “playlist display order change” process, the MIA and group 1 files are changed, and in the “add menu thumbnail” process, The files of MIA and groups 1 and 3 are changed, and in the “add mark thumbnail” process, MIA, groups 1 and 4 The file is changed, MIA and non-specific application files are changed in the “Add non-standard file (for JPEG images)” (for applications) process, and only MIA in “Delete non-standard file” process Has been shown to change.

  As described above, the file system information (MIA) changes in every operation, while the files in each group vary depending on whether or not the change has occurred.

  Note that the case of “changed” in group units corresponds to a case where a new file is recorded, the content of the recorded file changes, and data needs to be re-recorded. If you simply delete a file, the previously used area will not be used anymore. Except for files that have been deleted from the group of files recorded in a specific area for each group, the entire group will again be deleted. Must be recorded.

  Next, prior to the description of the recording process according to the present invention, a procedure for accessing a file in a conventional UDF will be described with reference to FIGS.

  FIG. 10 shows an example of the UDF Volume Structure structure, and FIG. 11 shows the contents of File Structure and Files. Here, a case of accessing “root / BDMV / Unit_Key_Gen_Value.inf” shown in FIG. 11 will be described as an example.

  In FIG. 10, Volume Structure records information related to the logical volume and information related to the analysis start point of the file structure recorded in the partition. In FIG. 10, the leftmost column is LSN (Logical Sector Number), the second column from the left is Structure, the second column from the right is Descriptors, and the rightmost column is LBN (Logical Sector Number). 11, the leftmost column is LBN (Logical Block Number), the middle column is Structure, and the rightmost column is Descriptors. Each is shown.

  Address information in the volume is represented by LSN (logical sector number), and addresses in the partition are represented by LBN (logical block number). Further, when there are a plurality of partitions in the volume, a plurality of pieces of partition information can be recorded in the Logical Volume Descriptor.

  10 and 11, only items necessary for processing will be described, and description of items unnecessary for processing will be omitted as appropriate.

  First, Anchor-1 anchor information (Anchor Volume Descriptor Pointer) where the LSN indicated by the number 1 in FIG. 10 is 256 is analyzed, and the position of the Volume Descriptor Sequence indicated by the number 2 is acquired. Subsequently, the Volume Descriptor Sequence in which the LSN indicated by the number 2 is located at positions 32 to 47 is analyzed. Volume Descriptor Sequence includes “Primary Volume Descriptor”, “Implementation Use Volume Descriptor”, “Partition Descriptor”, “Logical Volume Descriptor”, “Unallocated Spece Descriptor”, “Terminating Descriptor”, and “Trailing Logical Sectors” “Primary Volume Descriptor” is information identifying a volume, “Implementation Use Volume Descriptor” is information indicating compatibility, “Partition Descriptor” is information identifying a partition, and “Logical Volume Descriptor”. Is the information indicating the location of the logical partition, “Unallocated Spece Descriptor” is the information indicating the unused area, “Terminating Descriptor” is the information indicating the last position of the area, and “Trailing Logical Sectors” is the remaining area. Stores information.

  Among these, the position of the “Logical Volume Integrity Sequence” described in the “Logical Volume Descriptor” with the LSN of 35 indicated by the number 3 in FIG. 10, the position of the target partition, and the position of the File Set Descriptor in the partition To get.

  Further, the “Logical Volume Integrity Sequence” with 48 LSN indicated by the number 4 is analyzed, and the consistency check of the Volume information is performed. If there is no problem in consistency, the LSN 272 to 272Nall-272 indicated by the number 5 are checked. Analyzes the structure and files inside the partition. Access to the target partition can be started by the above procedure.

  Subsequently, since the root information is stored in the File Set Descriptor having the LBN of (A + 1) indicated by the number 11 in FIG. 11, this is analyzed, and the LBN indicated by the number 12 is (A +). 3) Get the location of the File Entry (indicated as FE (Root Directory) in the figure) of the root directory.

  Further, the File Entry (indicated as FE (Root Directory) in the figure) of the root directory whose LBN indicated by the number 12 is (A + 3) is analyzed, and the location where the root directory information is described ( Get LBN = A + 4). Next, the FID (File Identifier Descriptor) of the BDMV directory indicated by the number 13 in the information of the root directory is analyzed, and the FE (File Entry) of the BDMV directory indicated by the number 14 (FE ( Position (LBN = A + 5).

  Further, the File Entry of the BDMV directory indicated by the number 14 is analyzed, and the position (LBN = A + 9) where the information of the BDMV directory is recorded is obtained.

  Subsequently, information on the BDMV directory is acquired, and the File Identifier Descriptor of Unit_Key_Gen_Value.inf in the BDMV directory indicated by the number 15 is analyzed to acquire the position of the File Entry of Unit_Key_Gen_Value.inf. Then, the file entry of Unit_Key_Gen_Value.inf of number 16 is analyzed, the position where the data of Unit_Key_Gen_Value.inf is recorded is obtained, the address where the data of Unit_Key_Gen_Value.inf is recorded is accessed, and the target data is obtained. . With the above procedure, the data of the “root / BDMV / Unit_Key_Gen_Value.inf” file indicated by the number 17 can be acquired.

  As shown in FIG. 10 and FIG. 11, a mechanism for acquiring data of a specific file group earlier than a general file, which was shown as a Gahtered block in BDFS in conventional UDFs, is provided. Not. Even if you want to read multiple files at once, there is a possibility that both the File Entry and the file body are recorded at arbitrary addresses on the recording medium for each file. When these data are spread, it may take a very long time to acquire the data body. In addition, files saved under multiple levels of directories need to acquire and analyze three items: File Identifier Descriptor (FID), File Entry (FE), and directory information each time one level down the directory. Need to access many places.

  Therefore, in the present invention, in a file system that does not have a mechanism for acquiring data of a specific file group such as a UDF faster than a general file, the files are grouped, and the grouped files are Gathered information is managed collectively so that it can be accessed at high speed.

  Here, the recording process by the recording / reproducing mechanism unit 22 in FIG. 2 will be described with reference to the flowchart in FIG.

  In step S1, the file system information generating unit 62 sets a file grouping rule. This grouping rule is a grouping rule as described with reference to FIG. 3 or FIG. Here, the description will be made assuming that the grouping rule described with reference to FIG. 5 is set, but the grouping rule is not limited to this. In general, grouping rules that are determined to some extent are used. Therefore, when a fixed grouping rule is used, information on the grouping rule is stored in a memory (not shown) and read out. Anyway.

  In step S <b> 2, the file system information generation unit 62 controls the writing unit 73 to set an empty gathered.inf file on the recording medium 81 by using the recording / playback block 53 while securing a sufficient area. That is, the file system information generation unit 62 sets a dummy Gathered.inf file at any position on the recording medium 81 in order to write gathered information after the file arrangement is confirmed. At this time, in a recording medium that can be overwritten a plurality of times, a dummy file can be recorded on the recording medium and the final data can be overwritten later, but a recording medium that cannot be overwritten, such as a WriteOnce medium Then the same method cannot be used. In the case of WriteOnce media, instead of actually recording a dummy file on the recording medium, it is possible to reserve the area that can be recorded and perform processing so that other files are not recorded in the reserved area. Processing can be performed.

  In step S3, the file system information generating unit 62 creates a file and a directory (corresponding to the File Structure of UDF) immediately under the root directory as shown in FIG. 13, for example. For example, as shown in FIG. 13, the file system information generation unit 62 creates a file in each directory together with a gathered.inf file, a BDMV directory, a Resource directory, a DATA1 directory, and the like immediately under root. In FIG. 13, the configuration other than Gathered.inf is the same as the configuration described with reference to FIG.

  In step S4, the file system information generation unit 62 arranges all the files according to the arrangement rule for each group of input data input to the writing unit 73 via the ECC encoding unit 71 and the modulation unit 72. Then, the data is written on the recording medium 81 by the recording / reproducing block 53. At this time, the file system information generation unit 62 stores the arrangement information of the written data in a memory (not shown).

  For example, all files are arranged according to an arrangement rule as shown in FIG. Here, FIG. 14 shows an example of the arrangement of recording areas when the structure adopted in UDF version 2.01 or earlier is used and Gathered information is defined.

  In FIG. 14, the file structure related to the file that performs group management, the file structure related to the file that does not perform group management, the body of the file that performs group management (Files in the figure), the AV stream (AV Stream in the figure), and the group management. The backup data of files to be performed (Files Back Up in the figure) and general data that does not perform group management (Files in the figure) are shown separately, but other configuration examples such as dividing the group management area into multiple groups It may be. In FIG. 13, in one partition, a file structure related to a file that performs group management from the 0 direction in units of LBN, a file structure related to a file that does not perform group management, a file main body that performs group management, an AV stream, and a group Files are managed in the final LBN direction in the order of backup data for files to be managed and general data for which group management is not performed.

  In step S5, the file system information generation unit 62 reads the gathered information based on the information stored in a memory (not shown), controls the writing unit 73 via the ECC encoding unit 71 and the modulation unit 72, and The recording / playback block 53 overwrites Gathered.inf on the recording medium 81. That is, when arranged as shown in FIG. 14, Gathered information includes the file structure related to the file that performs group management, the body of the file that performs group management, the AV stream, and the backup data of the file that performs group management. The position is read, and for example, gathered information as shown in FIG. 15 is generated.

  In FIG. 15, SSt is recorded as the start address, ESt is recorded as the end address in G-Structure, SMGA is recorded as the start address, and EMGA is recorded as the end address in MainG-A. -A records SRGA as the start address, ERGA as the end address, MainG-B records SMGB as the start address, EMGB as the end address, ResG-B starts SRGB is recorded as the address, ERGB is recorded as the end address, SGC is recorded as the start address, EGC is recorded as the end address, SGX is recorded as the start address, and GX is recorded as the end address. EGX is recorded, G-Structure is recorded in the range from start address SSt to end address ESt, MainG-A is recorded in the range from start address SMGA to end address EMGA, ResG- A is recorded in the range from the start address SRGA to the end address ERGA, MainG-B is recorded in the range from the start address SMGB to the end address EMGB, and ResG-B is in the range from the start address SRGB to the end address ERGB GC is recorded in the range from the start address SGC to the end address EGC, and GX is recorded in the range from the start address SGX to the end address EGX.

  G-Structure indicates File Structure information related to the group management file represented as File Structure (group management) in FIG. 14, and groups A, B, C, and X are stored in Files (group management). A grouped file to be placed.

  As described above, Gathered.inf is recorded on the recording medium 81. When reading, the file management structure (File Structure) and files managed as a group are read from Gathered.inf and recognized. Therefore, high-speed reading is possible.

  Although the case where the grouping rule in FIG. 5 is applied has been described above, the grouping rule is not limited to this. For example, in UDF, there is a field called File Type in File Entry. Although this area is not used for file grouping, for example, this File Type may be newly defined and used as an ID for grouping like an allocation class in BDFS.

  Further, data arranged under a specific directory may be handled as one group. In this case, it is necessary to separately record a table that defines the relationship between directories and groups.

  Further, when the present invention is applied only to a specific application, it is expected that the relationship between the file and the group is defined by the application standard. In this case, there is no need to describe the relationship between files and groups using a file system or a specific table. If the recording / playback device is compatible with the application to be used, know what the files correspond to each group. Therefore, it is possible to read the grouped files together without any problem. In this case, for example, the same effect as described above can be obtained simply by allowing the groups 1 to N to be defined as a mechanism.

  Further, the arrangement rule of FIG. 14 may be one using a metadata partition adopted in UDF version 2.50 or later as shown in FIG. 16, for example. Here, the metadata partition means that File Structure is handled as a single file (metadata file (MD Files in the figure)), so that File Structure was acquired separately for each directory / file in earlier versions. It solves the problem of long access time. As described above, in applications where there are files that need to be managed and groups that do not need to be managed, even for File Structure that is handled as a whole metadata file as a metadata file, It is desirable to be able to separate the parts related to files that are managed by the group from the parts that are not. Therefore, it is assumed that the gathered information defined as shown in FIG. 16 can be defined so as to divide the metadata file.

  That is, in FIG. 16, MD (metha data) File FE (File Entry) stores MD File entry information, and the position of the MD File can be recognized based on this information. File Structure is composed of MD, and information on various management structures is recorded. Some File Structures are group-managed and some are not group-managed. In addition, as shown in MD Mirror, File Structure records similar files as backups. Files are group-managed files and some are not group-managed. In addition, the same files are recorded as backups for files managed in groups.

  In FIG. 16, Gathered information includes information on the group management of the file structure composed of MD Files, the file body managed in the group (Files in the figure), and the backup of the file managed in the group (in the figure Files Back Up) and MD Mirror are group-managed. Therefore, the arrangement information for each group managed in these is managed as Gathered information in Gathered.inf.

  As shown in FIG. 14, the gathered information is not limited to the group-managed file structure, the group-managed files, and the group-managed files back up, but as shown in FIG. (As shown by the dotted line in FIG. 17), a file structure that is not group-managed, a file that is not group-managed, and a file back-up that is not group-managed may be used.

  Similarly, the gathered information is managed in groups among the File Structures composed of MD Files as shown in FIG. 16, files managed in groups (Files in the figure), and groups managed. Files (Files Back Up in the figure) and MD Mirror are not limited to those managed in groups, but are composed of MD Files as shown in FIG. 18 (as indicated by the dotted line in FIG. 18). Use file structures that are not group-managed, files that are not group-managed (Files (outside group) in the figure), AV streams, and MD Mirror that are not group-managed. Also good.

  Next, a process for reproducing information recorded on the recording medium 81 by the recording / reproducing mechanism 22 shown in FIG. 2 will be described with reference to the flowchart shown in FIG.

  In step S11, the file system information recognizing unit 61 controls the reading unit 91 to read the information recorded on the recording medium 81 via the recording / reproducing block 53, and sets the demodulating unit 92 and the ECC decoding unit to 93. The file system information is analyzed, and the Gathered.inf file is acquired based on the address information on the recording medium 81 where Gathered.inf exists.

  In step S12, the file system information recognition unit 61 analyzes the acquired Gathered.inf and acquires Gathered information. That is, by this processing, the file system information recognition unit 61 obtains information as shown in FIG. 15 described above, thereby grasping where the group management information is recorded on the recording medium 81. It will be in a state that can be.

  In step S <b> 13, the file system information recognition unit 61 determines whether the file to be acquired (file to be reproduced) is gathered-managed, that is, a group-managed file.

  For example, if it is determined in step S13 that the file to be acquired is a file that is gathered and managed, the file system information recognition unit 61 records the file recorded in the acquired gathered information in step S14. Based on the position information of the group to which the group belongs, the reading unit 91 is controlled to operate the recording / reproducing block 53 so that all the files belonging to the group are collectively read from the recording medium 81 and acquired.

  That is, if the file to be acquired is a group-managed file, it belongs to one of the groups. For example, if the file to be acquired is a file belonging to the group A of the grouping rule in FIG. 5, the position where the group of the file to be acquired is recorded on the recording medium 81 by the gathered information shown in FIG. Since it is understood that the range is from the address SMGA to the address EMGA, files belonging to the group A are collectively read based on this information.

  On the other hand, if it is determined in step S13 that the file to be acquired is not Gahtered-managed, that is, a file that is not group-managed, in step S15, the file system information recognition unit 61 obtains file system information. Analyze and get only the files you want to get individually.

  According to the above, if the file to be acquired is a group-managed file, generally, other files managed as the same group are often required at the same time, and by collecting and reading together with gathered information, It is possible to read the files more efficiently than to search and read the files individually, and as a result, high-speed reading (high-speed reproduction) can be realized.

  In the above, the address location of the gathered.inf file is confirmed based on the file system information, and the gathered.inf file is acquired. For example, the gathered.inf file is recorded at a fixed address on the recording medium 81. Thus, the Gathered.inf file may be directly acquired without acquiring the file system information.

  FIG. 20 shows a recording / playback mechanism unit 22 in which a gathered.inf file is recorded at a fixed address on the recording medium 81 so that the gathered.inf file can be directly acquired without acquiring file system information. The configuration is shown. 2 that are the same as those of the recording / reproducing mechanism 22 in FIG. 2 are denoted by the same reference numerals, and description thereof will be omitted as appropriate.

  20 differs from the recording / reproducing mechanism 22 in FIG. 2 in that a file system information recognizing unit 301 and file system information are replaced by a file system information recognizing unit 61 and a file system information generating unit 62. The generation unit 302 is provided.

  The file system information recognizing unit 301 basically has the same function as the file system information recognizing unit 61. Further, the file system information recognizing unit 301 is further recorded in a fixed address on the recording medium 81 by the file system information generating unit 302. Inf can be read without analyzing the file system information and obtaining the recording address.

  The file system information generation unit 302 is basically the same as the file system information generation unit 62, but records gahtered.inf at a fixed address on the recording medium 81.

  Next, recording processing by the recording / reproducing mechanism 22 in FIG. 20 will be described with reference to the flowchart in FIG. Note that the processing of steps S21, S23 to S25 in the flowchart of FIG. 21 is the same as the processing of steps S1, S3 to S5 in the flowchart of FIG.

  In step S <b> 22, the file system information generation unit 302 controls the writing unit 73 to determine a sufficient area for an empty gathered.inf file on the recording medium 81 by the recording / playback block 53 in advance on the recording medium 81. Set it on a fixed address. That is, the file system information generation unit 302 sets a dummy Gathered.inf file to a fixed address on the recording medium 81 in order to write gathered information after the file arrangement is confirmed.

  With the above processing, the Gathered.inf file is recorded at a fixed address on the recording medium 81. Therefore, without reproducing the location of the Gathered.inf file by the file system information during playback, The Gathered.inf file can be acquired, and as a result, the reading speed can be improved.

  Next, the reproduction process by the recording / reproducing mechanism unit 22 in FIG. 20 will be described with reference to the flowchart in FIG. Note that the processing of steps S32 to S34 in the flowchart of FIG. 22 is the same as the processing of steps S13 to S15 in the flowchart of FIG.

  In step S31, the file system information recognition unit 301 controls the reading unit 91 to read and acquire the Gathered.inf file recorded at a fixed address on the recording medium 81 via the recording / playback block 53, Analyzes the acquired Gathered.inf and acquires Gathered information.

  With the above processing, it is possible to omit the processing of step S11 in the flowchart of FIG. 19, so that the file to be acquired can be acquired at a higher speed, and as a result, combined with the high-speed reading by the grouping processing. In addition, high-speed read processing is possible.

  In the above description, a case where a group-managed file and a file or directory that is not group-managed are managed by one partition on the recording medium 81 has been described. A partition for recording unmanaged files may be provided so that grouped files can be managed by one partition.

  It is also possible to assign a unique partition for each group or groups. Allocating a partition to each group (or multiple groups) that you want to read at a high speed collectively means that the gathered information that has been recorded in the user data area in the form of a gathered.inf file is recorded in the UDF Volume Structure. The area allocation information for each partition can be used instead. That is, in the method described below, it is not essential to record the gathered information as a specific file in the user data area.

  FIG. 23 shows recording in which a grouped file is recorded on a recording medium 81 and a partition for recording a file that is not managed by a group is provided, so that the grouped file can be managed by one partition. The structure of the reproduction | regeneration mechanism part 22 is shown. In FIG. 23, the same components as those of the recording / reproducing mechanism 22 in FIG. 2 are denoted by the same reference numerals, and description thereof will be omitted as appropriate.

  23 differs from the recording / reproducing mechanism 22 in FIG. 2 in that a file system information recognizing unit 311 and file system information are replaced with a file system information recognizing unit 61 and a file system information generating unit 62. The generation unit 312 is provided.

  The file system information recognizing unit 311 basically has the same function as the file system information recognizing unit 61, but is further managed in a group set on the recording medium 81 by the file system information generating unit 312. A file that is group-managed is read (reproduced) from a partition that records a file that is recorded, and a file that is not group-managed is read (reproduced) from a partition that records a file that is not group-managed.

  The file system information generation unit 312 is basically the same as the file system information generation unit 62, but further includes a partition for recording files managed in a group on the recording medium 81, and group management. Set up the partition to record the unrecorded file, and record the corresponding file in each partition.

  Next, recording processing by the recording / reproducing mechanism 22 in FIG. 23 will be described with reference to the flowchart in FIG. Note that the processing of steps S41, S42, and S46 in the flowchart of FIG. 24 is the same as the processing of steps S1, S2, and S5 in the flowchart of FIG.

  In step S43, the file system information generation unit 312 controls the writing unit 73 to set two or more partitions on the recording medium 81 by the recording / reproducing block 53. For example, here, two partitions 1 and 2 are set.

  In step S44, the file system information generation unit 312 performs file and directory (corresponding to the File Structure of UDF), group-managed file and directory, and file and directory not group-managed for each partition. To create. For example, as shown in FIG. 25, the file system information generation unit 312 creates a file and directory that are group-managed in the partition 1, and creates a file and directory that is not group-managed in the partition 2.

  That is, in FIG. 25, a PLAYLIST directory, a CLIPINF directory, a Resource directory, and a DATA1 directory, which are directories of groups A, B, C, and X that are group-managed based on the grouping rule of FIG. Are created in the partition 1, and the STREAM directory and the DATA2 directory, which are directories not group-managed, and the files belonging to the respective directories are created in the partition 2.

  In step S45, the file system information generation unit 312 receives the input data input to the writing unit 73 via the ECC encoding unit 71 and the modulation unit 72 for each group and for each partition according to the arrangement rule. All the files are arranged and written on the recording medium 81 by the recording / reproducing block 53. At this time, the file system information generation unit 312 stores the arrangement information of the written data in a memory (not shown).

  For example, all files are arranged according to an arrangement rule as shown in FIG. In FIG. 26, the file structure related to the file for group management, the main body of the file for group management (Files in the figure), and the backup data of the file for group management (Files Back Up in the figure) are partition 1. The file structure, the AV stream (AV Stream in the figure) related to the file not subjected to group management, and the general data not subjected to group management (Files in the figure) are recorded.

  In this way, when group-managed files and non-group-managed files are managed by different partitions, when group-managed information is read continuously, all groups can be accessed with a single access. Since managed files can be read continuously, a high-speed reading process can be realized.

  Next, with reference to the flowchart of FIG. 27, the reproducing process by the recording / reproducing mechanism unit 22 of FIG. 23 will be described. In step S51, the file system information recognition unit 311 acquires the gathered information set by the file system information generation unit 312 at the time of recording, that is, the information that the group management file is recorded in the partition 1. The process of step S52 in the flowchart of FIG. 27 is the same as the process of step S13 in the flowchart of FIG.

  In step S53, the file system information recognition unit 311 controls the reading unit 91 based on the position information of the group to which the file belongs, recorded in the acquired gathered information, and operates the recording / reproducing block 53, All the files belonging to the group are collectively read out and acquired from a predetermined partition in which the group-managed directory and files of the recording medium 81 are recorded.

  That is, for example, in the case of FIG. 25 and FIG. 26, if the file to be acquired is a file that is managed by grouping, it is recorded in the partition 1, so that it is desired to acquire it by gathered information. From the partition 1 in which the group of files is recorded, the files of the group to which the file to be acquired belongs are collectively read out.

  In step S54, the file system information recognizing unit 311 analyzes the file system information, and acquires only the files to be acquired individually from the directory where the group management is not performed and the directory in which the files are recorded. In this case, the file system information recognition unit 311 controls the reading unit 91 based on the position information of the group to which the file belongs, recorded in the file system information, and operates the recording / reproducing block 53 to record the recording medium. The files are individually read out from the predetermined partition 2 in which the directories and files not managed by the group 81 are recorded.

  Through the above processing, when the group-managed file and the non-group-managed file are managed by different partitions, when the group-managed information is continuously read, the recording / reproducing block 53 is recorded on the recording medium. With respect to 81, since all group-managed files can be read continuously with one access, high-speed reading processing can be realized.

  In the above, an example in which gathered information (gathered.inf file) is written on a general recording data recording area (so-called user data area) in the recording medium 81, and a grouped file are dedicated. Although an example in the case of allocating a partition is described, a gathered.inf file may be written in a physical area (for example, a lead-in area).

  FIG. 28 shows the configuration of the recording / playback mechanism unit 22 in which gathered information is written in the physical area of the recording medium 81 and the gathered information file recorded in the physical area of the recording medium 81 is read. In FIG. 28, the same components as those of the recording / reproducing mechanism 22 in FIG. 2 are denoted by the same reference numerals, and description thereof will be omitted as appropriate.

  28 differs from the recording / reproducing mechanism 22 in FIG. 2 in that a file system information recognizing unit 331 and file system information are replaced with a file system information recognizing unit 61 and a file system information generating unit 62. The generation unit 332 is provided.

  The file system information recognizing unit 331 basically has the same function as the file system information recognizing unit 61. Further, the file system information recognizing unit 331 is gathered by the file system information generating unit 332 set on the physical area of the recording medium 81. The reading unit 91 is controlled to read information.

  The file system information generation unit 312 is basically the same as the file system information generation unit 62, but the writing unit 73 further records gathered information on the physical area of the recording medium 81. To control.

  Next, recording processing by the recording / reproducing mechanism 22 in FIG. 28 will be described with reference to the flowchart in FIG. Note that the processing of steps S61 to S63 in the flowchart of FIG. 29 is the same as the processing of steps S1, S3, and S4 in the flowchart of FIG.

  In step S64, the file system information generation unit 332 controls the writing unit 73 to write gathered information on the physical area of the recording medium 81 by the recording / playback block 53 as shown in FIG.

  That is, as shown in FIG. 30, gathered information that has been recorded as a gathered.inf file together with other data in the user data area is recorded in the physical area.

  With the above processing, when information on the recording medium 81 is read, the gathered information is recorded in the information of the physical area that is read first. Therefore, at the time of reproduction, the gathered.inf file Gathered information can be acquired without confirming the position, and as a result, the reading speed can be improved.

  Next, the reproduction processing by the recording / reproducing mechanism unit 22 of FIG. 28 will be described with reference to the flowchart of FIG. Note that the processing of steps S72 to S74 in the flowchart of FIG. 31 is the same as the processing of steps S13 to S15 in the flowchart of FIG.

  In step S71, the file system information recognition unit 331 controls the reading unit 91 to acquire gathered information recorded on the physical area of the recording medium 81 as shown in FIG. .

  With the above processing, when reading information on the recording medium 81, it is possible to acquire the gathered information without checking the position of the gathered.inf file from the file system information, and as a result, the reading speed is improved. It becomes possible to make it.

  In the above, based on rules that are not supposed to be used for group management such as UDF, in particular, Gathered information is provided on the recording medium, and group management is performed based on this, and group management of files by partitioning However, for example, Gahtered information may be written using a rule in UDF without using the Gathered.inf file described above.

  FIG. 32 shows a configuration of the recording / reproducing mechanism unit 22 that records the gathered information described above using a rule in the UDF. In FIG. 32, the same components as those of the recording / reproducing mechanism 22 in FIG. 2 are denoted by the same reference numerals, and description thereof will be omitted as appropriate.

  32 differs from the recording / reproducing mechanism 22 in FIG. 2 in that a file system information recognizing unit 341 and file system information are replaced with a file system information recognizing unit 61 and a file system information generating unit 62. The generation unit 342 is provided.

  The file system information recognition unit 341 is similar to the file system information recognition unit 61 in basic functions, but further controls the reading unit 91 and records it in the File Structure portion of the UDF by the file system information generation unit 342. The read unit 91 is controlled to read the group-managed file based on the information described in the file structure.

  The file system information generation unit 342 is similar to the file system information generation unit 61 in basic functions, but further sets information corresponding to the File Structure portion of the UDF and records it in the recording medium 81. Thus, the writing unit 73 is controlled.

  Next, recording processing by the recording / reproducing mechanism 22 in FIG. 32 will be described with reference to the flowchart in FIG.

  In step S81, the file system information generating unit 342 creates a file and a directory (corresponding to the File Structure and File of the UDF) directly under the root directory as shown in FIG. That is, the file system information generation unit 342 creates a file in each directory together with the BDMV directory, the Resource directory, the DATA1 directory, and the like directly under the root as shown in FIG. 34, for example. The structure in FIG. 34 is the same as that obtained by deleting Gathered.inf in FIG. 13 and is the same as the configuration described with reference to FIG.

  In step S82, the file system information generation unit 342 determines the arrangement of FID information and FE information, which are directory information, in a memory (not shown). Further, in step S83, the file system information generation unit 342 controls the writing unit 73 to determine the actual file arrangement for each directory arrangement determined on the recording medium 81 and record the file data. At this time, the file system information generating unit 342 sequentially stores the written file, the FID of the directory, and the FE in a memory (not shown).

  In the case of UDF, it takes time to read out. When accessing one file, first, it recognizes File Identifier Descriptor (FID), and secondly, reads File Entry (FE) based on the FID. Thirdly, since the file body is accessed based on the FE, there is a problem that the recording positions of the FE and the file body are not limited even though there are three steps. Therefore, the file system information generation unit 342 determines the arrangement by applying a certain rule to the arrangement method of the FE and the file body.

  That is, for FEs, FEs for files / directories under the same directory are successively arranged in the order of FIDs described in the directory information. In addition, the file body is also arranged continuously in the order of FID arrangement in the directory information as in the case of FE. Furthermore, the above rules are defined not only within a directory but also between a plurality of directories in the same directory for a specific application.

  In step S84, the file system information generation unit 342 controls the writing unit 73 to determine the FE information from the written file position information and the directory information arrangement information determined in step S82. Write to the recording medium 81 as Structure information.

  In step S85, the file system information generation unit 342 controls the writing unit 73 to determine FID information from the FE arrangement information determined in step S82, and writes the FID information as file structure information in the recording medium 81.

  As a result, for example, the structure of the BDMV directory in FIG. 34 is described in File Structure in the arrangement format shown in FIG. In FIG. 35, the left column indicates LBN, the center indicates Structure, and the right column indicates Descriptors. That is, in the area where LBN is A, the structure of the BDMV directory is described as Structure, and as Descriptors, FID (parent derectory), FID (Unit_Key_Gen_Value.inf), FID (CPS_CCI.inf),. (PLAYLIST), FID (CLIPINF), and FID (STREAM) are described. These are described as files recorded directly under the BDMV directory in FIG. 34 or as the FID of the directory.

  Furthermore, in the region where LBN is A + 1 to A + 7, the structure of ICB (Information Control Blocks) for files under CLIPINF Directory is described as Structure, and as Descriptor, at the position corresponding to the above-mentioned FID, FE (Unit_Key_Gen_Value.inf), FE (CPS_CCI.inf)... FE (PLAYLIST), FE (CLIPINF), and FE (STREAM) are arranged from the top. That is, as shown in FIG. 35, the FID and FE items are arranged in the same order.

  By arranging in this way, the start point and end point of the area where the FE for the file / directory under the same directory is written can be obtained by examining the first FID and the last FID in the directory information.

  Other directories are structured in the same structure. For example, the CLIPINF directory is configured as shown in FIG. In the region where LBN is from B to B + X, the structure of the CLIPINF directory is described as Structure, and as Descriptors, FID (parent derectory), FID (01000.clpi), FID (02000.clpi)・ It is described as FID (XXXXX.clpi). These are described as each file recorded directly under the CLIFINF directory in FIG. 34 or as the FID of the directory.

  Furthermore, the structure of ICB (Infomation Control Blocks) for files under CLIPINF is described as Structure in the region where LBN is B + X + 1 to B + X + N, and it corresponds to the above-mentioned FID as Descriptor From the top, FE (01000.clpi), FE (02000.clpi),... FE (XXXXX.clpi) are arranged at the positions. That is, also in FIG. 36, the items of FID and FE are arranged in the same order.

  Thereby, first read the first FID, read the first FE based on this, further confirm the start position of the first file body, read the FID at the final position, read the FE at the final position based on this, In addition, by confirming the end position of the last file body, the start address and end address of the area where files under the directory are stored can be obtained, and data can be obtained collectively by one reading. Is possible.

  Next, with reference to the flowchart of FIG. 37, the reproducing process by the recording / reproducing mechanism unit 22 of FIG. 28 will be described.

  In step S91, the file system information recognition unit 341 controls the reading unit 91 to analyze the file system information recorded on the recording medium 81 via the recording / playback block 53, and the directory where the target file exists. Get information about.

  In step S92, the file system information recognition unit 341 acquires the position of the FE indicated by the first / last one of the file FIDs in the directory information acquired in the process of step S91.

  In step S93, the file system information recognizing unit 341 controls the recording / reproducing block 53 to obtain information on the range from the start point of the file pointed to by the acquired first FE to the end point of the file pointed to by the last FE (or the first FE). Information in a range from the start point of the directory pointed to to the end point of the directory pointed to by the last FE).

  In step S94, the file system information recognition unit 341 acquires a target individual file from the data read together in the process of step S93. That is, the file system information recognition unit 341 acquires a target individual file based on the file system information from the files read together.

  That is, for example, when the files stored in the BDMV directory, the PLAYLIST directory, and the CLIPINF directory shown in FIG. 35 are consecutively arranged by the above processing, the first file FE (under the BDMV directory) Assuming that the last file (XXXXX.clpi) under the CLIPINF directory is the end point as shown in FIG. 36 with Unit_Key_Gen_Value.inf) as the start point, by reading these pieces of information together, Stored files can be read at once, enabling high-speed reading.

  As a result, the first FID is read first, the first FE is read based on this, the start position of the first file body is confirmed, the last FID is read, the last FE is read based on this, and By confirming the end position of the last file body, the start address and end address of the area where the files under the directory are stored can be obtained from the information of the start position and end position of the file body. Data can be acquired collectively. Also, by defining the above rules not only within a directory but also between a plurality of directories within the same directory for a specific application, the start address and end address of the entire management data can be assigned to a single file structure. It can be acquired by analyzing the part. As a result, the reading speed can be improved.

  In the above description, for example, in the description of the placement rule with reference to FIG. 14 and the like, the case of a single-layer disc has been described. However, the same placement rule can be set even in a multi-layer disc. .

  For example, FIG. 38 shows a case where a metadata partition is used, but the present invention can also be applied to a multi-layered medium even when a metadata partition is not used.

  In FIG. 38, the arrangement rules from the top to the first to fourth layers are described. The first and third layers are arranged so that the LBN increases in the outermost peripheral direction in the figure, and the second and fourth layers are arranged. Are arranged so that the LBN increases in the innermost circumferential direction in the figure, and regions are set continuously in the first layer, the second layer, the third layer, and the fourth layer.

  In the first layer, the LBN increases in the order of “Volume Structure”, “MD File FE”, “File Structure”, “MD Bitmap FE”, “MD Bitmap”, “MD Mirror (Case 1)”, and “File Data”. In the second layer, the LBN increases in the order of “File Data”, “MD Mirror (Case2)”, “Free Area”, and in the third layer, “Free Area” The fourth layer is recorded with the LBN increasing in the order of “Free Area”, “MD Mirror (Case 3)”, and “Volume Structure”.

  Here, “MD Mirror” is for recording a metafile (File Structure) twice, and there are three possible recording positions of “MD Mirror” (namely, Case 1 to 3). Only one is recorded). Further, the metadata bitmap file is used to define an area in use and an area not in use in the metafile, but there is no need to apply when the recording medium 81 is a ROM. Therefore, when using with ROM media, “MD Bitmap FE” and “MD Bitmap” in the figure are not required.

  In multi-layer ROM media, since the amount of data is determined at the time of disc manufacture, in the case of a dual-layer disc as shown in FIG. 42, half of the amount of data is recorded in the first and second layers, respectively. The logical block is allocated only to the area where the data is recorded.

  In FIG. 39, in the first layer, “Volume Structure”, “MD File FE”, “File Structure”, “MD Bitmap FE”, MD Bitmap ”,“ MD Mirror (Case 1) ”, and“ File ” Data is arranged in the direction of increasing LBN, and in the second layer, “File Data”, “MD Mirror (Case 2)”, “Free Area”, and “Volume Structure” are arranged in the direction of decreasing LBN. As in the case of Fig. 38, there are two possible recording positions for "MD Mirror": Case 1 and Case 2 (that is, only one of them is recorded).

  According to the above, in any case, the group-managed file recorded on the recording medium can be read at high speed (reproduced at high speed).

  The series of processes described above can be executed by hardware, but can also be executed by software. When a series of processes is executed by software, a program constituting the software may execute various functions by installing a computer incorporated in dedicated hardware or various programs. For example, it is installed from a program storage medium in a general-purpose personal computer or the like.

  As shown in FIG. 1, the program storage medium in which the program is stored is distributed to provide a program to the user separately from the recording / playback apparatus 1, and is a magnetic disk 41 (flexible disk) on which the program is recorded. ), Optical disk 42 (including compact disc-read only memory (CD-ROM), DVD (digital versatile disk)), magneto-optical disk 43 (including MD (mini-disc)), or semiconductor memory 44 In addition to a package medium, the program is provided with a ROM 12 on which a program is recorded and a hard disk included in the storage unit 18 provided to the user in a state of being incorporated in the recording / reproducing apparatus 1 in advance.

  In this specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in time series in the order described, but of course, it is not necessarily performed in time series. Or the process performed separately is included.

  Further, in this specification, the system represents the entire apparatus constituted by a plurality of apparatuses.

It is a figure which shows the structure of one Embodiment of the recording / reproducing apparatus to which this invention is applied. It is a figure which shows the structure of the recording / reproducing mechanism part of FIG. It is a figure which shows the example of group management. It is a figure which shows the structure of the directory and file produced | generated by the group management of FIG. It is a figure which shows the other example of group management. It is a figure which shows the structure of the directory and file produced | generated by the group management of FIG. It is a figure explaining the example of arrangement | positioning of the data recorded on a recording medium. It is a figure which shows file system information. It is a figure which shows the presence or absence of the change according to various operation of the file by which group management was carried out. It is a figure explaining the access procedure to the file by UDF. It is a figure explaining the access procedure to the file by UDF. 3 is a flowchart for explaining a recording process by a recording / reproducing mechanism unit in FIG. 2. It is a figure which shows the structure of the directory and file produced | generated by the group management by the recording / reproducing mechanism part of FIG. It is a figure explaining the example of arrangement | positioning of the data recorded on a recording medium by the recording / reproducing mechanism part of FIG. It is a figure explaining gathered information. FIG. 10 is a diagram for explaining another example of an arrangement of data recorded on a recording medium by the recording / reproducing mechanism unit of FIG. 2. FIG. 10 is a diagram for explaining still another example of the arrangement of data recorded on a recording medium by the recording / reproducing mechanism unit of FIG. 2. FIG. 10 is a diagram for explaining still another example of the arrangement of data recorded on a recording medium by the recording / reproducing mechanism unit of FIG. 2. 3 is a flowchart for explaining a reproduction process by a recording / reproduction mechanism unit in FIG. 2. It is a figure which shows the other structure of the recording / reproducing mechanism part of FIG. FIG. 21 is a flowchart for describing recording processing by the recording / reproducing mechanism unit of FIG. 20. FIG. FIG. 21 is a flowchart for describing playback processing by the recording / playback mechanism unit of FIG. 20. FIG. FIG. 10 is a diagram showing still another configuration of the recording / reproducing mechanism unit of FIG. 1. It is a flowchart explaining the recording process by the recording / reproducing mechanism part of FIG. It is a figure explaining the structure of the directory for every partition in the recording process by the recording / reproducing mechanism part of FIG. It is a figure explaining the example of arrangement | positioning of the data recorded on a recording medium by the recording / reproducing mechanism part of FIG. It is a flowchart explaining the reproduction | regeneration processing by the recording / reproducing mechanism part of FIG. FIG. 10 is a diagram showing still another configuration of the recording / reproducing mechanism unit of FIG. 1. It is a flowchart explaining the recording process by the recording / reproducing mechanism part of FIG. It is a figure explaining the process recorded on the physical layer on a recording medium by the recording / reproducing mechanism part of FIG. It is a flowchart explaining the reproduction | regeneration processing by the recording / reproducing mechanism part of FIG. FIG. 10 is a diagram showing still another configuration of the recording / reproducing mechanism unit of FIG. 1. FIG. 33 is a flowchart for describing a recording process by a recording / reproducing mechanism unit in FIG. 32. FIG. FIG. 33 is a diagram for describing a directory structure in a recording process by the recording / reproducing mechanism unit of FIG. 32. It is a figure explaining File Structure recorded by the recording process by the recording / reproducing mechanism part of FIG. It is a figure explaining File Structure recorded by the recording process by the recording / reproducing mechanism part of FIG. FIG. 33 is a flowchart for describing playback processing by the recording / playback mechanism unit of FIG. 32. FIG. It is a figure explaining the example of arrangement | positioning of the data in the other structure of the recording medium of FIG. It is a figure explaining the example of arrangement | positioning of the data in the other structure of the recording medium of FIG.

Explanation of symbols

  22 recording / reproducing mechanism unit, 51 control unit, 52 recording unit, 53 recording / reproducing block, 54 reproducing unit, 61 file system information recognizing unit, 62 file system information generating unit, 71 ECC encoding unit, 72 modulating unit, 73 writing Unit, 81 recording medium, 91 reading unit, 92 demodulating unit, 93 ECC decoding unit, 301 file system information recognizing unit, 302 file system information generating unit, 311 file system information recognizing unit, 312 file system information generating unit, 331 file system Information recognition unit, 332 File system information generation unit, 341 File system information recognition unit, 342 File system information generation unit

Claims (11)

A recording means for recording a file managed by UDF without a group management mechanism on a recording medium;
Based on the attribute of the file, the file is grouped with a first file that needs to be grouped, a second file that does not need to be grouped with the file, and the file Setting means for setting an arrangement on the recording medium for each group of the first file;
Based on the arrangement set by the setting means, the first file and the second file are recorded on a recording medium, and arrangement information based on the arrangement of the first file and the second file is stored in the recording medium. Control means for controlling the recording means to record at a predetermined position of the recording medium,
The information recording / reproducing apparatus, wherein the recording means arranges a group-managed file main body at a head portion of a partition and arranges a backup file of the file main body at a partition end portion. The information recording / reproducing apparatus according to claim 1, wherein the recording unit further arranges the metadata file at a head portion of the partition and arranges a backup file of the metadata file at a tail portion of the partition. The control means records the first file and the second file on a recording medium based on the arrangement set by the setting means, and arranges the first file and the second file. The information recording / reproducing apparatus according to claim 1, wherein the recording unit is controlled to record arrangement information based on the information in a user data area of the recording medium. The control means records the first file and the second file on a recording medium based on the arrangement set by the setting means, and arranges the first file and the second file. The information recording / reproducing apparatus according to claim 1, wherein the recording unit is controlled to record the arrangement information based on the information at a fixed address in a user data area of the recording medium. The control means records the first file and the second file on a recording medium based on the arrangement set by the setting means, and arranges the first file and the second file. The information recording / reproducing apparatus according to claim 1, wherein the recording unit is controlled so as to record arrangement information based on the recording information in an area in which general recording data of the recording medium is not recorded. A recording step of recording a file managed by UDF without a group management mechanism on a recording medium;
Based on the attribute of the file, the file is grouped with a first file that needs to be grouped, a second file that does not need to be grouped with the file, and the file A setting step for setting an arrangement on the recording medium for each group of the first file;
Based on the arrangement set in the processing of the setting step, the first file and the second file are recorded on a recording medium, and arrangement information based on the arrangement of the first file and the second file is recorded. And a control step for controlling processing of the recording step so as to record at a predetermined position of the recording medium,
The information recording / reproducing method, wherein the recording step arranges a main body of a group-managed file at a head portion of a partition, and places a backup file of the main body of the file at a tail portion of the partition. The information recording / reproducing method according to claim 6, wherein the recording step further arranges the metadata file at a head portion of the partition and arranges a backup file of the metadata file at a tail portion of the partition. Based on the attributes of files managed by UDF that do not have a group management mechanism, the first file that needs to be grouped is grouped, and the grouping of the files A setting step for setting an arrangement on the recording medium for the second file that is not necessary and each group of the first file;
Based on the arrangement set in the setting step, the first file and the second file are recorded on the recording medium, and the arrangement is based on the arrangement of the first file and the second file. A control step for controlling information to be recorded at a predetermined position of the recording medium,
The recording step arranges a group-managed file main body at the beginning of the partition and arranges a backup file of the file main body at the end of the partition. Program storage storing a computer-readable program Medium. The program storage medium according to claim 8, wherein the recording step further arranges a metadata file at a head portion of the partition and a backup file of the metadata file at a tail portion of the partition. Based on the attributes of files managed by UDF that do not have a group management mechanism, the first file that needs to be grouped is grouped, and the grouping of the files A setting step for setting an arrangement on the recording medium for the second file that is not necessary and each group of the first file;
Based on the arrangement set in the setting step, the first file and the second file are recorded on the recording medium, and the arrangement is based on the arrangement of the first file and the second file. A control step for controlling information to be recorded at a predetermined position on the recording medium, wherein the body of the group-managed file is placed at the beginning of the partition, and the backup file of the body of the file is placed at the end of the partition A program that causes a computer to execute a process including: The program according to claim 10, wherein the control step further arranges a metadata file at a head portion of a partition and places a backup file of the metadata file at a tail portion of the partition.

Images