JP3620241B2 - File management apparatus, file management method, recording medium, and file management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a file management apparatus, a file management method, a recording medium, and a file management system that manage each file according to a hierarchical structure of directories and files.
[0002]
[Prior art]
Conventionally, files composed of data such as images and sounds are managed by a directory and a hierarchical structure of files. In such a hierarchical structure, each directory or each file has its own directory name or file name, and it is necessary to hold information on the names of higher or lower directories and files. Therefore, when a file stored in an external storage device is not named, a normal computer manages each file after naming the file.
[0003]
[Problems to be solved by the invention]
However, some files, such as images and music, can be handled easily without assigning a file name, and the computer requires that all files and directories have their own names. Managing all files using names is not an efficient process and may increase the processing load. In addition, in the file management method as described above, the information for managing each file is concentrated in the directory, so the area for managing the directory information becomes large and the directory is destroyed. It was impossible to revive the above hierarchical structure.
[0004]
Also, when the number of files in a directory increases, it may be desirable to group these files according to their usage and type. At this time, in the conventional hierarchical structure, it is necessary to provide a directory or change the file name of the file to be grouped. However, providing a directory for simple grouping is a heavy processing burden. Further, even if a unique file name is assigned to each file for grouping the files, the files cannot be grouped if the file names are changed again.
[0005]
Also, since conventional directories and files do not have usage / type information that indicates images taken with a camera, for example, they are managed after it is determined how they are used in the application format. The processing burden was heavy.
[0006]
The present invention has been proposed in view of such circumstances, and facilitates the management of directories and files, and can greatly reduce the processing burden when managing these files and file management. It is an object to provide a method, a recording medium, and a file management system.
[0007]
[Means for Solving the Problems]
In order to solve the above-described problem, a file management apparatus according to the present invention has a directory entry including a file having a file number and continuous recording information indicating whether the file is continuously recorded as a group of files for each file. Storage means for storing the directory, and management means for managing the file or directory indicated by the file number of the directory entry of the stored one directory so as to be in a hierarchy below the one directory. The storage means stores, as the directory, a directory having a directory entry including a file number and continuous recording information indicating whether or not it is the first of continuous, for each file, and the management means reads from the storage means Based on the continuous recording information of the one directory, each file indicated by each successive directory entry of the one directory is managed as a group of continuous files, and the management means reads the one read from the storage means. Based on the continuous recording information of the directory, the file number from the file number of the directory entry having continuous recording information indicating the beginning of the next to the directory entry immediately preceding the directory entry having continuous recording information indicating the beginning of the next continuous The file indicated by is managed as a continuous file And, even in a predetermined file already recorded in the storage means,By changing the order of the file numbers recorded in the directory entryThe file can be inserted and edited in a set of continuously recorded files.
[0008]
A file management method according to the present invention includes a directory entry comprising a file having a file number, and continuous recording information indicating whether the file number and the file are continuously recorded as a group of files, and whether the file is the first in a series. Store the directory for each file, read the continuous recording information of the one directory, and based on the read continuous recording information of the one directory, from the file number of the directory entry having the continuous recording information indicating the beginning of the continuous The file indicated by the file number up to the directory entry immediately preceding the directory entry having the continuous recording information indicating the beginning of the next continuous is managed as a group of continuous files, and even if it is a predetermined file already recorded ,By changing the order of the file numbers recorded in the directory entryThe file can be inserted and edited in a set of continuously recorded files.
[0009]
A recording medium according to the present invention includes a directory entry including a file having a file number and continuous recording information indicating whether the file number and the file are continuously recorded as a group of files and indicating whether the file is the first in a series for each file. A directory having continuous recording information indicating the beginning of the next sequence from the file number of the directory entry having continuous recording information indicating the beginning of the sequence based on the continuous recording information of the one directory. The file indicated by the file number up to the directory entry immediately before the entry is managed as a group of continuous files, even if it is a predetermined file already recorded,By changing the order of the file numbers recorded in the directory entryThe file can be inserted and edited in a set of continuously recorded files.
[0010]
A file management system according to the present invention includes a file having a directory number including a file having a file number and continuous recording information indicating whether the file number and the file are continuously recorded as a group of files and whether the file is the first in a series. A recording medium for recording a directory included in each, a storage means for storing a file and a directory read from the recording medium, and a file or directory indicated by a file number of a directory entry of one stored directory And a file management apparatus having management means for managing so as to be in a hierarchy below one directory, wherein the management means is based on the continuous recording information of the one directory read from the storage means. For each successive directory entry in the current directory Each of the files is managed as a group of continuous files, and the management means, based on the continuous recording information of the one directory read from the storage means, the directory entry having continuous recording information indicating the beginning of the continuous The file indicated by the file number from the file number to the directory entry immediately preceding the directory entry having the continuous recording information indicating the first of the next continuous is managed as a continuous file, and a predetermined record already recorded in the storage means Even a fileBy changing the order of the file numbers recorded in the directory entryThe file can be inserted and edited in a set of continuously recorded files.
[0011]
A file management method according to the present invention includes a file having a directory number including a file having a file number and continuous recording information indicating whether the file number and the file are continuously recorded as a group of files and whether the file is the first in a series. A directory having each is recorded on a recording medium, a file and a directory are read from the recording medium, the read file and directory are stored, and the first of the continuous is based on continuous recording information of one directory. The file indicated by the file number from the file number of the directory entry having continuous record information indicating the directory entry immediately before the directory entry having continuous record information indicating the first of the next continuous is managed as a group of continuous files. , Predetermined files already recorded Even,By changing the order of the file numbers recorded in the directory entryThe file can be inserted and edited in a set of continuously recorded files.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0013]
The present invention is applied to the memory card system 1 having the configuration shown in FIG. The memory card system 1 includes a host computer 10 and a memory card 20.
[0014]
Specifically, as shown in FIG. 1, the host computer 10 includes a hard disk 11 for storing various files such as still images and audio, a directory for managing each file collectively, files from the hard disk 11, etc. Is stored in a RAM (Random Access Memory) 12 and a first serial interface (hereinafter referred to as “first serial I / F”) that transmits and receives data to and from the memory card 20 via three lines. 13 and a CPU (Central Processing Unit) 14 for controlling each circuit. For example, files such as images and sounds stored in the hard disk 11 can be managed by a hierarchical structure using directories.
[0015]
The RAM 12 temporarily stores, for example, a file stored in the hard disk 11, and supplies this file to the first serial I / F 13 via the bus as necessary.
[0016]
The first serial I / F 13 transmits data to the memory card 20 or receives data stored in the memory card 20 via three lines. Specifically, the first serial I / F 13 transmits a serial clock SCK for transmitting the control data and file via the first line. The first serial I / F 13 outputs a chip select signal CS indicating the current state in response to switching of serial data such as a file or control data on the first line via the second line. . Further, the first serial I / F 13 transmits a file and control data to be written to the memory card 20 and receives a file read from the memory card 20 via the third line.
[0017]
The CPU 14 controls reading of files from the RAM 12 and the hard disk 11, writing of files to the RAM 12, etc., and control of transmission / reception of files with the memory card 20. For example, the CPU 14 issues a register instruction for determining whether or not the write protection of an erroneous erasure prevention switch (not shown) of the memory card 20 is turned on, or designates an address to the memory card 20 to specify a predetermined file. Issue a write command.
[0018]
As shown in FIG. 1, the memory card 20 includes a second serial I / F 21 that serially transmits and receives files and control data from the host computer 10, a flash memory 22 that stores files and directories, And a controller 23 that controls reading or writing of a file or the like stored in the flash memory 22.
[0019]
The flash memory 22 is, for example, of the NAND type, and stores the file transmitted from the host computer 10 by dividing it into blocks (for example, 8 kbytes or 16 kbytes) as erase units, as shown in FIG. To do. Each block 0, 1, 2,..., N is composed of one page (= 512 bytes + 16 bytes) composed of a data area for storing 512 bytes of files and the like and a 16-byte redundant area. In the redundant area, distributed management information for managing data in the data area of the block is stored. When these pieces of distributed management information are collected, set management information (set management file) is configured. The collective management file is composed of several blocks, and collectively manages the data recording state of all the blocks. For example, a part of the distributed management information of each block in the flash memory 22 is collectively managed. A bitmap table is provided.
[0020]
Here, the file includes a user file format used for images and sounds, and a system file format for system management. A predetermined logical address is assigned to each file, and the flash memory 22 has a predetermined logical address. Stored in the data area of one or more blocks.
[0021]
As shown in FIG. 3, the user file format file is composed of a 512-byte header portion which is attribute information of the file and a data portion which is main information. The header portion is a 128-byte OS header that is information for managing the file in the memory card 20 and a general-purpose one that can be handled by a normal personal computer or the like, and 240 bytes that are indispensable management information. File header and a 144-byte entry area. The data portion has a table data area and four entry data. In the data section shown in FIG. 3 described above, up to four entry data are stored. That is, a user file format file is composed of a maximum of four entry data. In FIG. 3, the entry data includes an index, image data, and two auxiliary data. However, the entry data is not particularly limited, and may be other audio data.
[0022]
Specifically, as shown in FIG. 4, the OS header includes “file ID” (2 bytes), “file version” (2 bytes), “file size” (4 bytes), “number of used blocks” (2 Byte), “Number of links” (1 byte), “Date” (8 bytes), “Manufacturer / model code” (4 bytes), “Initial registration directory number” (2 bytes), “Application category” (1 byte) , “File name” (11 bytes), “keyword registration number” (1 byte), “keyword character code” (1 byte), “keyword character string” (32 bytes), “0 reset reserve” (4 bytes), It has “individual data” (32 bytes) and an unused area “reserve”.
[0023]
“File ID” represents the type (use) of the file, and the same applies to the file header. “File version” indicates a so-called version number, and is used to determine whether the host computer 10 or the memory card 20 can process this file. “File size” indicates the total size of the file including the header portion and the data portion in bytes. The “number of used blocks” indicates the number of blocks using the file in the flash memory 22. “Number of links” indicates the number of directories or files referring to the file. Note that the “number of links” includes the directory to which the file belongs. For example, since a file that is not referenced from another directory is linked only to the directory to which the file belongs, the “number of links” is 1. “Date” indicates the date when the file was created or updated. The “manufacturer / type code” indicates the manufacturer name and model of the device that has written the file to the memory card 20. The “initial registration directory number” indicates the directory number registered first, and is not updated even when the file moves to another directory. “Application category” indicates a category of an application in which this file is used. The “file name” is a file name used when the host computer 10 manages the file, and is not particularly used in the memory card 20. “Number of registered keywords” indicates the number of registered keywords. The “keyword character code” indicates the character code of the keyword. A “keyword character string” can be specified by determining a keyword and a separator. “0 reset reserve” is always set to 0 when rewriting. “Individual data” is for management for each file ID, and is data used for a purpose determined by the file ID, for example, and can be used freely by the user.
[0024]
Specifically, the file header includes “standard identification data” (8 bytes), “file standard identification data” (8 bytes), “file ID” (2 bytes), “file version” as shown in FIG. (2 bytes), “application creation date” (8 bytes), “application update date” (8 bytes), “creation manufacturer / model code” (4 bytes), “update manufacturer / model code” (4 bytes), “ 0 reset reserve (16 bytes), “number of data entries” (1 byte), “number of tables” (1 byte), “character code” (1 byte), “title character string” (128 bytes), and unused It has the area “Reserve”.
[0025]
“Standard identification data” indicates that the flash memory 22 stores a file in accordance with a predetermined standard. “File standard identification data” indicates that the file is created in accordance with the predetermined standard. “File ID” represents the type of file, and the OS header has the same thing. “File version” indicates a version number. The “application creation date” indicates the date when the application is created, and the “application update date” indicates the date when the application is updated. “Created manufacturer / type code” indicates the manufacturer that created the file and the model name thereof, and “Updated manufacturer / type code” indicates the manufacturer that updated the file and the model name thereof. The “number of data entries” indicates the number of entry data described later. “Number of tables” indicates the number of data in the table data area. “Character code” indicates an input character by a predetermined code number. The “title character string” indicates a title character.
[0026]
In the entry area, data (hereinafter referred to as “entries”) for managing the four entry data of the data part is stored.
[0027]
Each entry in the entry area is provided corresponding to four entry data. As shown in FIG. 5, for each of the four entry data, “start address” (4 bytes), “data size” (4 bytes) ), “Data type ID” (1 byte), “reserve” (1 byte), and “individual data” (26 bytes). For example, “start address” of entry 1 indicates the top logical address of “entry data 1 index” shown in FIG. 3, and “start address” of entry 2 indicates the top logical address of “entry data 2 image data”.
[0028]
On the other hand, as a file in the system file format, for example, a directory file is applicable, and the configuration of the header portion is different from that in the user file format.
[0029]
Here, one directory is composed of one file, that is, one directory file, and has a maximum size of 8 kbytes. A directory file is composed of a header part and a data part, and each file is managed mainly by directory information in the header part and a directory entry list in the data part.
[0030]
As shown in FIG. 6, the header portion of the directory file includes “OS header” (128 bytes), “file header” (240 bytes), “system entry area” (48 bytes), “directory information” (96 bytes). ). The “OS header” and “file header” are the same as those in the user file format described above.
[0031]
The “system entry area” is almost the same as that in the user file format, but individual data is not provided for each entry. Specifically, as shown in FIG. 7, for each entry, “start address” (4 bytes), “data size” (4 bytes), “data type ID” (1 byte), “reserve” (3 bytes) ) For example, the “start address” of one entry indicates the start logical address of group information described later, and the “start address” of the other entry indicates the start logical address of a directory entry described later.
[0032]
“Directory information” manages directory information. As shown in FIG. 8, “directory ID” (2 bytes), “target file ID” (1 byte), “number of groups” (1 byte). , “Parent directory” (2 bytes), “Number of directories” (2 bytes), “Number of files (all files)” (2 bytes), “Number of target files” (2 bytes), “Access point” (2 bytes) , “Number of directory entries” (2 bytes), “Number of directory entries for system” (2 bytes), “Number of used system directory entries” (2 bytes), “Number of reserved blocks” (2 bytes), “Number of used blocks” (2 bytes) and an unused area “reserve” (72 bytes).
[0033]
“Directory ID” represents the type of directory, and “Target file ID” represents a target file ID. That is, they do not indicate the name of the directory itself or the file itself, but indicate the use of, for example, images and audio. The “target file ID” describes the upper 1 byte of the “file ID” of the target file in the directory. Thereby, the file ID for identifying by the “target flag” can be designated. If only the “target file ID” is changed, the file type of the directory can be easily changed. “Number of groups” is the number of registered groups when a plurality of files in the directory are grouped. “Parent directory” indicates the parent directory, that is, the directory number of the hierarchy one level higher. “Number of directories” indicates the total number of directories included, and “Number of files (all files)” indicates the number of all files included in the directory. The “number of target files” indicates the number of files that can be handled in the directory, that is, the number of target files included. The “access point” indicates a directory entry to be accessed first when access to the directory is started. “Number of directory entries” indicates the number of directory entries in the user area described later. “Number of system directory entries” indicates the number of directory entries in the system directory area. Specifically, as shown in FIG. 9, each directory file is provided with a system directory area and a user area. These areas can be set for each directory. The system directory area is an area for handling special files necessary for the system such as management files, and the area is fixed by a directory entry. That is, the first to predetermined directory entries correspond to the system directory area, and the other directory entries correspond to the user area. Therefore, the “number of system directory entries” indicates the number of directory entries for the system. The root directory has 256 system directories. On the other hand, in the user area, the directory entries are arranged without a gap from the start position of the area. The “number of used system directory entries” indicates the number of directory entries actually used in the system directory area. “Number of secured blocks” indicates the number of blocks of the flash memory 22 that the application wants to secure, and “Number of used blocks” indicates the number of blocks used by the application.
[0034]
The data portion of the directory file has “group information” (variable length) as entry data 1 and “directory entry list” (variable length) as entry data 2, as shown in FIG.
[0035]
As shown in FIG. 10, “group information” includes “group number” (1 byte), “group information size” (1 byte), “directory ID” (2 bytes), “0 reset reserve” (1 byte). , “Reserve” (3 bytes), “Date” (8 bytes), “Individual data” (8 bytes), “Title” (variable length).
[0036]
“Group information” is information for grouping desired files in a directory. As will be described in detail later, a pseudo directory is substantially provided in a hierarchy below the directory. “Group information size” indicates the size of group information, and is a fixed length of 24 bytes + an arbitrary number of bytes of “title”. “Directory ID” is an ID assigned to each directory type, and “0 reset reserve” is always set to 0 when correction is made. “Reserve” is set to 0 when the file is created. “Date” indicates the creation date of the file, which can be changed by the user. “Individual data” is not particularly defined, and “title” indicates the title of the directory file.
[0037]
The “directory entry list” indicates elements belonging to the directory, and as shown in FIG. 11, a plurality of directory entries are collected. One directory entry is 4 bytes. The directory entry is composed of “file number” (2 bytes), “attribute information” (1 byte), and “group number” (1 byte).
[0038]
As shown in FIG. 12, “file number” has “0” in the first bit in 2 bytes, and the remaining 15 bits indicate the head logical address of the file or directory. When “0xffff” is indicated, it means that it is not used.
[0039]
As shown in FIG. 13, the “attribute information” includes “directory / file” (1 bit), “target flag” (1 bit), “mark 1” (1 bit), “mark 2” (1 bit), It has “continuous recording” (2 bits) and “reserve” (2 bits) information. “Directory / file” indicates that there is a directory under the directory when the directory is 1, and indicates that there is a file when the directory is 0. The “target flag” indicates that the file has the target file ID specified by the above-described directory information when it is 1, and indicates that the file is other than that when it is 0. For example, it is used when determining whether the file is an image or a file other than an image. “Mark 1” indicates that the mark 1 is specified when the mark is 1, and indicates that there is no such specification when the mark is 0. “Mark 2” is the same as “Mark 1”. “Mark 1” and “Mark 2” are marking flags that can be specified by the user. “Continuous recording” is used to indicate a continuous set of something such as continuous shooting or simple video. This continuous recording requires that directory entries are adjacent to each other, that is, files are continuous. Specifically, “00” indicates a normal file, “11” indicates the head of a continuous file, and “10” indicates a continuously designated file. For example, in FIG. 14, each 2-bit number indicates the “continuous recording” value of the file indicated by each directory entry. For example, files 2 to 5 and files 6 to 9 are continuously recorded. Each file collected as a continuous record needs to have the same “group number” with the directory entries of the parent directory being continuous. Then, by having 2-bit information for each file, a group of files in the directory can be identified as being continuously recorded. A description when one of the continuously recorded files is deleted or a new file is inserted will be described later.
[0040]
As shown in FIG. 15, the “group number” is a group number indicated by 8 bits and indicating a one-layer pseudo directory. Thereby, files having the same group number in the same directory are handled as one group. Note that the file with the group number 0 is not grouped at all, and is handled as a file directly under the directory.
[0041]
Here, it is assumed that nine files 1 to 9 exist in the same directory. Further, files 1, 5 and 7 belong to group 1, files 2 and 4 belong to group 2, files 3 and 6 belong to group 3, and files 8 and 9 belong to group 0.
[0042]
At this time, as shown in FIG. 16, group 1 to group 3 are located in a hierarchy below the directory and play a pseudo role as directories. The files 8 and 9 belonging to the group 0 are handled as those directly under the directory.
[0043]
That is, by providing a “group number” of only 1 byte per entry, it is possible to exhibit a group function in which a directory is further provided under the parent directory. Further, since group information may be provided in the directory file, each group can be given a name, and the group function has a function comparable to a normal directory.
[0044]
For example, as shown in FIG. 17, each group may not be handled like a pseudo directory, but may be handled simply as indicating a file having a group relationship.
[0045]
Further, the grouping function as shown in FIGS. 16 and 17 is compatible between a host computer that can handle groups and a host computer that cannot handle groups. That is, a file or directory stored in a host computer having a grouping function (hereinafter referred to as “host computer 10A”) is transmitted to a host computer having no grouping function (hereinafter referred to as “host computer 10B”). However, no problem occurs. Such compatibility will be described below by taking the case of a “camera directory” whose usage is a camera. The host computer 10A has a function of rearranging the directory entries in the directory entry list shown in FIG. 11 and a host computer 10A that does not have the function, and each will be described.
[0046]
For example, as shown in FIG. 18A, it is assumed that there are nine files 1 to 9 in the camera directory, and each file is classified into group 0 to group 3. Files 1, 5 and 7 are classified as group 1 as family photos, files 2 and 4 are classified as group 2 as hobby photos, files 3 and 6 are classified as group 3 as company relationships, and files 8 and 9 Are classified into group 0 as unclassified. Group 0 is handled as being directly under the camera directory. At this time, in the directory entry list shown in FIG. 11, the directory entries are arranged in the order of file 1, file 2, file 3,. That is, in the directory entry list, the directory entries of each file are arranged in the order shown in FIG.
[0047]
Here, in the host computer 10A, the CPU 14 can rearrange the directory entries as shown in FIG. 18B with respect to the directory file for the camera directory stored in the RAM 12. That is, the CPU 14 rearranges the directory entries so that the same group is continuously arranged in the directory entry. As a result, as shown in FIG. 19, the files 1 to 9 are grouped and arranged for each group such as a family photo or a hobby photo.
[0048]
Then, when the host computer 10A transmits the directory file of the camera directory and the files 1 to 9 to the host computer 10B, the host computer 10B moves to the hierarchy below the camera directory as shown in FIG. Arrange the files. Specifically, since the host computer 10B arranges the files in accordance with the arrangement of the directory entries in the directory file for the camera directory, each file can be arranged in the same order as the arrangement order of the files in the host computer 10A. Therefore, each file is also arranged in a group in the host computer 10B.
[0049]
As described above, when the host computer 10A has a grouping function and has a function of rearranging the directory entry list for each group, the host computer 10B that does not have the grouping function also performs grouping to store each file. Can be lined up.
[0050]
On the other hand, even in the host computer 10A that does not have the function of rearranging the directory entries for each group, the files in the camera directory can be grouped as shown in FIG.
[0051]
However, when the host computer 10A transmits the directory file for the camera directory and the files 1 to 9 to the host computer 10B, the host computer 10B arranges the files as they are as shown in FIG. That is, the host computer 10B arranges the files in accordance with the arrangement of directory entries in the directory file for the camera directory, and arranges the files in the order of files 1, 2, 3,.
[0052]
In the memory card system 1 configured as described above, the CPU 14 of the host computer 10 causes the directory file of the root directory of the logical address 0 (hereinafter referred to as “root directory file”) from the flash memory 22 of the memory card 20 and others. Each file can be managed by reading out the directory file and the header portion of the necessary file. Specifically, when the start-up is started, the CPU 14 starts the process of step S1 shown in FIG.
[0053]
In step S <b> 1, the CPU 14 transmits a command for instructing reading of the file having the logical address 0 to the memory card 20 via the first serial I / F 13. In the memory card 20, the controller 23 reads the file at the logical address 0 from the flash memory 22 in accordance with the above command, and transmits it to the host computer 10 via the second serial I / F 21. The CPU 14 stores the file received by the first serial I / F 13 in the RAM 12, checks whether this is the root directory file, and proceeds to step S2.
[0054]
In step S2, it is determined whether the root directory file exists in the flash memory 22. If it exists, the process proceeds to step S3, and if it does not exist, the process proceeds to step S7.
[0055]
In step S3, its own application directory is checked, and the process proceeds to step S4. For example, if the host computer 10 is a camera device having an imaging unit (not shown), it is checked whether a “camera” directory exists at a predetermined position in the root directory. If it exists, it is found that the memory card 20 is used in a camera device, and the process of step S4 and step S5 described later is performed. That is, in the root directory, a directory determined for each application category is provided. For example, in the case of a camera, a directory called “camera” is provided at a predetermined position.
[0056]
In step S4, it is determined whether or not its own application directory, for example, the “camera” directory exists. If it exists, the process proceeds to step S5, and if it does not exist, the process proceeds to step S9.
[0057]
In step S5, the contents of the application directory are read out, and the process proceeds to step S6.
[0058]
In step S6, the directory entry of the directory file in the application directory is checked, the files necessary for the application such as the album image list and the music list are accessed, and the application process is started.
[0059]
On the other hand, in step S7 when it is determined in step S2 that the root directory file does not exist, it is determined whether or not a root directory file is to be created. If it is to be created, the process proceeds to step S8. Here, the case where the root directory is not created corresponds to the case where the memory card 20 is write-protected, for example.
[0060]
In step S8, a root directory file of logical address 0 is created, and the process proceeds to step S9.
[0061]
In step S9, it is determined whether or not to create its own application directory. If it is to be created, the process proceeds to step S10. If it is not to be created, this process is stopped. That is, when there is no “camera” directory, it is necessary to create a “camera” directory as in the process of step S10 described later, or to suspend the process and replace the memory card 20 by the user. .
[0062]
In step S10, an application directory is created in the root directory file, and the process proceeds to step S5. Then, the processing of the application is started through the processing of step S5 and step S6.
[0063]
As described above, for example, when starting up the host computer 10 having an imaging unit (not shown), after first confirming the existence of the root directory, a predetermined application directory, in this case, the “camera” directory is checked. , Processing the contents of that directory.
[0064]
Next, the operation of the CPU 14 when performing directory creation processing will be described. When the creation of the directory file is instructed, the CPU 14 of the host computer 10 starts the process of step S11 shown in FIG.
[0065]
In step S11, the CPU 14 checks a free logical address and proceeds to step S12.
[0066]
In step S12, it is determined whether there is a free logical address. If there is no space, an error occurs because a directory cannot be created. If there is a space, the process proceeds to step S13.
[0067]
In step S13, the directory information of the directory file to be created is set to an initial value. Further, when all directory entries are initialized and group information is prepared, all the areas are cleared, and the process proceeds to step S14.
[0068]
In step S14, it is checked whether each block in the flash memory 22 included in the memory card 20 has a capacity that can store a directory file, and the process proceeds to step S15.
[0069]
In step S15, it is determined whether there is a vacancy in the block. If there is no vacancy, an error occurs. If there is a vacancy, the process proceeds to step S16.
[0070]
In step S16, the CPU 14 transmits to the memory card 20 a command for writing the contents together with the directory file, and the process proceeds to step S17. At this time, in the memory card 20, the controller 23 writes the directory file into the flash memory 22 in accordance with the above command.
[0071]
In step S17, the bitmap table of the set management file stored in the RAM 12 is updated, and the process proceeds to step S18.
[0072]
In step S18, the created directory is registered in the parent directory that is one level above the created directory, and the process proceeds to step S19. For example, in the directory file of the parent directory, the “directory number” of the directory information is updated, or a directory entry related to the created directory is created.
[0073]
In step S19, the CPU 14 transmits a command for instructing the update of the collective management file to the memory card 20 at a good timing such as when a predetermined calculation process is completed, and ends the process. At this time, in the memory card 20, the controller 23 writes the updated portion of the set management file to the flash memory 22 in accordance with the command.
[0074]
As described above, when creating a directory, a logical address having a free space is attached instead of creating a directory name.
[0075]
Next, the operation of the CPU 14 when creating a file and registering it in its parent directory will be described. When the CPU 14 of the host computer 10 is instructed to create a file, it starts the processing of step S21 shown in FIG.
[0076]
In step S21, the CPU 14 checks whether there is a space in the directory entry of the parent directory of the newly created file, and proceeds to step S22.
[0077]
In step S22, it is determined whether or not there is a directory entry space in the parent directory. If there is space, the process proceeds to step S23. If there is no space, an error occurs and the file registration process in the directory is stopped.
[0078]
In step S23, a header portion of the file to be created is created and stored in the RAM 12, and the process proceeds to step S24.
[0079]
In step S24, a command instructing to write the file in each block is transmitted to the memory card 20, and the process proceeds to step S25. Therefore, in the memory card 20, the controller 23 writes a new file in the flash memory 22 according to this command. When writing the file to two or more blocks, a concatenated address indicating a concatenated state between the blocks is written as distribution management information for each block.
[0080]
In step S25, it is determined whether or not the writing of the file to the flash memory 22 is completed. If the writing is completed, the process proceeds to step S26. If the writing cannot be performed, an error occurs and registration of the file in the directory is stopped. To do.
[0081]
In step S26, the CPU 14 writes the first logical address of the file in a free directory entry for the directory file of the parent directory of the file. Further, “group number” and “attribute information” are written in this directory entry as necessary, and the process proceeds to step S27.
[0082]
In step S27, the directory information of the directory file is updated, and the process proceeds to step S28.
[0083]
In step S28, the CPU 14 transmits a command for instructing the writing of the directory file to the memory card 20, and ends the process. At this time, in the memory card 20, the controller 23 writes the directory file into the flash memory 22 in accordance with the above command.
[0084]
As described above, when registering a file in a directory, instead of registering the file name in the directory, register a 4-byte directory entry consisting of the file number (first logical address), attribute information, and group number. ing. As a result, it is possible to prevent a large amount of information from being concentrated in the directory, and even when a large number of files are registered, the amount of information in the directory is prevented from being excessively increased, and the data in the flash memory 22 is prevented. The recording area can be used effectively.
[0085]
Next, the operation of the CPU 14 when examining whether a file is suitable for the usage of its parent directory, that is, when examining the usage of the file by the “target flag” shown in FIG. The CPU 14 of the host computer 10 starts the process of step S31 shown in FIG. 25 when an instruction to investigate the usage of a file belonging to a certain directory is issued.
[0086]
In step S31, the CPU 14 checks the “target flag” of the usage information of the directory entry to be checked against the directory file of the parent directory, and proceeds to step S32.
[0087]
In step S32, it is determined whether or not the “target flag” is “1”. When it is “1”, the process proceeds to step S33, and when it is not “1”, the process proceeds to step S34.
[0088]
In step S33, since the file indicated by the “target flag” matches the usage of the directory, the CPU 14 performs predetermined processing on the file.
[0089]
In step S34, since the file indicated by the “target flag” does not match the usage of the directory, the CPU 14 regards this file as not being processed and ends the processing.
[0090]
In this way, the CPU 14 can easily determine whether the usage of the file and its parent directory matches by simply looking at the 1-bit “target flag”, and can access a predetermined file at high speed. Can do.
[0091]
If there is no “target flag”, the CPU 14 starts the process of step S41 shown in FIG.
[0092]
In step S41, the CPU 14 checks the “file number” of the directory entry to be checked with respect to the directory file of the parent directory, and proceeds to step S42.
[0093]
In step S 42, an instruction to read only the header portion of the file indicated by “file number”, that is, the head logical address is transmitted to the memory card 20, and the header portion data transmitted from the memory card 20 is stored in the RAM 12. Then, the process proceeds to step S43.
[0094]
In step S43, the read “file ID” of the header part is compared with the “target file ID” shown in FIG. 8 of the directory information of the parent directory, and the process proceeds to step S44.
[0095]
In step S44, it is determined whether or not the upper 1 byte of the read “file ID” matches the “target file ID”. If they match, the process proceeds to step S45, and if they do not match, the process proceeds to step S46.
[0096]
In step S45, since this file matches the usage of the directory, the CPU 14 performs a predetermined process on this file.
[0097]
In step S46, since this file does not match the purpose of the directory, the CPU 14 regards this file as not subject to processing and ends the processing.
[0098]
In this way, the CPU 14 can determine whether the usage of the file and its parent directory match even when there is no “target flag”.
[0099]
Next, the processing of the CPU when reading the nth image file in the directory will be described. When the CPU 14 of the host computer 10 is instructed to read the nth image file, it starts the process of step S51 shown in FIG.
[0100]
In step S <b> 51, the CPU 14 transmits a command for reading a target directory file to the controller 23 of the memory card 20. Specifically, a command for reading data from the block corresponding to the specified logical address is transmitted, and the process proceeds to step S52.
[0101]
In step S <b> 52, the controller 23 reads data from the block in which the target directory file is stored from the flash memory 22 and transmits the data to the host computer 10. In the host computer 10, the CPU 14 stores the transmitted data in the RAM 12, stores the directory information, group information, directory entry list, and the like shown in FIG. 6, and proceeds to step S53.
[0102]
In step S53, the process goes to the first directory entry of the user area in the directory entry list shown in FIG. 9 of the directory file, and the process proceeds to step S54.
[0103]
In step S54, the “target flag” shown in FIG. 13 of the directory entry is checked, and the process proceeds to step S55.
[0104]
In step S55, the CPU 14 determines whether the file indicated by the first directory entry is an image or an image based on the “target flag”. If the file is an image, the process proceeds to step S56; Proceed to S61.
[0105]
In step S56, it is determined whether the file number indicated by the directory entry is the designated file number n. If it is the designated file number, the process proceeds to step S57. If not, the process proceeds to step S60.
[0106]
In step S57, the CPU 14 performs a process for acquiring the file number and proceeds to step S58.
[0107]
In step S <b> 58, the CPU 14 transmits a command for reading the 512-byte header portion of the file to the memory card 20 based on the acquired file number (first logical address). Then, the CPU 14 checks the “start address” and “data size” of each entry data such as an index and an image based on the entry list of the header part transmitted from the memory card 20, and proceeds to step S59.
[0108]
In step S <b> 59, the CPU 14 transmits a command for reading each entry data such as an index and an image to the memory card 20 based on the “start address” and “data size”. In the memory card 20, the controller 23 reads each entry data according to the command and transmits it to the host computer 10. When entry data is stored in a plurality of blocks, the entry data is read from each block based on the “concatenated address”.
[0109]
On the other hand, in step S60 when it is determined in step S56 that the file number indicated by the directory entry is not the target file number n, the CPU 14 increments the number of directory entries by one and proceeds to step S61.
[0110]
In step S61, the CPU 14 proceeds to the processing of the next directory entry and proceeds to step S62.
[0111]
In step S62, the CPU 14 determines whether or not the processing of the last directory entry has been completed. When it is determined that the processing has ended, the CPU 14 ends the series of processing assuming that there is no corresponding file, and returns to step S54 if not. The next directory entry in step S61 is processed.
[0112]
As described above, in the memory card system 1, the host computer 10 can read a desired file from the flash memory 22 without providing a file name for each file. Specifically, the CPU 14 of the host computer 10 checks the directory entry list provided in each directory in order. When a directory entry indicating a desired file is found, a command for reading the desired file is transmitted to the memory card 20 in accordance with the logical address indicated by the directory entry, and a file reading process is performed. This eliminates the need for character string processing using file names and directory names, so that it is not necessary to provide an area for storing character strings in each directory. The directory management area is reduced, and more data is stored in the flash memory 22. It can be memorized.
[0113]
Next, the processing of the CPU when deleting the nth image file in the directory will be described. When an instruction to delete the nth image file is issued, the CPU 14 of the host computer 10 starts the process of step S71 shown in FIG.
[0114]
In step S <b> 71, the CPU 14 transmits a command for reading a target directory file to the controller 23 of the memory card 20. Specifically, a command for reading the block corresponding to the logical address of the designated number is transmitted, and the process proceeds to step S72.
[0115]
In step S <b> 72, the controller 23 reads data from the block in which the target directory file is stored from the flash memory 22 and transmits the data to the host computer 10. In the host computer 10, the CPU 14 stores the transmitted data in the RAM 12, and proceeds to step S73. Therefore, the RAM 12 stores the directory information, group information, directory entry list, and the like shown in FIG.
[0116]
In step S73, the process goes to the first directory entry of the user area in the directory entry list shown in FIG. 9 of the directory file, and the process proceeds to step S74.
[0117]
In step S74, the “target flag” shown in FIG. 13 of the directory entry is checked, and the process proceeds to step S75.
[0118]
In step S75, based on the “target flag”, the CPU 14 determines whether the file indicated by the first directory entry is an image or an image. If the file is an image, the process proceeds to step S76. Proceed to S83.
[0119]
In step S76, it is determined whether the file number indicated by the directory entry is the designated file number n. If it is the designated file number, the process proceeds to step S77, and if not, the process proceeds to step S82.
[0120]
In step S77, the CPU 14 performs a process for acquiring the file number and proceeds to step S78.
[0121]
In step S78, the CPU 14 transmits a command indicating the file deletion process of the designated file number to the memory card 20, and proceeds to step S79. On the other hand, in the memory card 20, the controller 23 clears the block in which the file specified in accordance with the command is stored.
[0122]
In step S79, the CPU 14 deletes the directory entry related to the deleted file from the directory entry list of the target directory. At this time, the CPU 14 updates the directory entry list by closing the deleted directory entry, and proceeds to step S80.
[0123]
In step S80, the CPU 14 performs a directory information update process as the directory entry is deleted. For example, “number of files (all files)”, “number of target files”, “number of directory entries”, and the like are updated, and the process proceeds to step S81.
[0124]
In step S81, since the directory entry list and directory information constituting the header portion of the directory file have been changed as described above, the CPU 14 sends a command to the memory card 20 indicating that a new header portion of the directory file is to be written. Send. In the memory card 20, the controller 23 updates the directory file header part to the flash memory 22 according to the command.
[0125]
On the other hand, in step S82 when it is determined in step S76 that the file number indicated by the directory entry is not the target file number n, the CPU 14 increments the number of directory entries by one and proceeds to step S83.
[0126]
In step S83, the CPU 14 proceeds to the next order of directory entry processing and proceeds to step S84.
[0127]
In step S84, the CPU 14 determines whether or not the process of the last directory entry has been completed. When it is determined that the process has ended, the CPU 14 ends the series of processes assuming that there is no corresponding file. Returning to step S74, the next directory entry in step S83 is processed.
[0128]
As described above, in the memory card system 1, the host computer 10 can delete a desired file stored in the flash memory 22 even if the file name is not provided for each file. That is, the CPU 14 of the host computer 10 searches a directory entry list provided in each directory in order to find a directory entry indicating a desired file, and issues a command to delete the desired file according to the logical address of the memory card 20. Send to. As a result, the file stored in the flash memory 22 is deleted. This eliminates the need for character string processing using file names and directory names, so that it is not necessary to provide an area for storing character strings in each directory, and the directory management area is reduced to store more data in the flash memory 22. Can be made.
[0129]
Next, the processing of the CPU when deleting a directory will be described. When the directory to be deleted is designated, the CPU 14 of the host computer 10 starts the process of step S91 shown in FIG.
[0130]
In step S91, the CPU 14 transmits to the memory card 20 a command for reading the directory file of the directory designated for deletion from the flash memory 22, and the process proceeds to step S92. In the memory card 20, the controller 23 reads a directory file from the flash memory 22 based on the command, and transmits it to the host computer 10 via the second serial I / F 21.
[0131]
In step S92, the CPU 14 stores the directory file from the memory card 20 in the RAM 12, examines each directory entry in the directory entry list, and proceeds to step S93.
[0132]
In step S93, the CPU 14 determines whether there is a directory entry that designates a file or directory, that is, whether a file or other directory exists in the lower layer. If there is a directory entry that designates a file or the like, it is determined that an error has occurred, and the deletion process of this directory is terminated. If not, the process proceeds to step S94. In step S94, the CPU 14 determines the directory to be deleted. Is transmitted to the memory card 20, and the process proceeds to step S95.
[0133]
In step S95, the controller 23 of the memory card 20 erases the data in the block of the flash memory 22 storing the directory file to be deleted, and proceeds to step S96. Note that the “erased” flag may be set in the distribution management information of the block, and the data in the block may be erased after a predetermined process is completed.
[0134]
In step S96, it is determined whether or not the erasure has been completed normally. If the erasure has been completed normally, the process proceeds to step S97. If the erasure has not been completed normally, it is determined that an error has occurred and the directory deletion process is stopped.
[0135]
In step S97, the CPU 14 updates the portion of the set management file stored in the RAM 12 that has changed due to directory deletion, and proceeds to step S98.
[0136]
In step S98, the CPU 14 transmits the collective management file to the memory card 20 and a command for instructing to write the file when it is cut off, for example, after completion of the predetermined arithmetic processing. Therefore, in the memory card 20, the controller 23 performs a process of writing the set management file to the flash memory in accordance with the above command.
[0137]
As described above, in the memory card system 1, the host computer 10 can delete a desired directory file stored in the flash memory 22 even if a file name is not provided for each file. That is, even if the directory to be deleted does not have information such as the file name of the file under it, the CPU 14 of the host computer 10 uses the directory entry list provided in the directory to delete the directory under the directory to be deleted. You can check if there are any files. This eliminates the need for character string processing using file names and directory names, so that it is not necessary to provide an area for storing character strings in each directory. The directory management area is reduced, and more data is stored in the flash memory 22. It can be memorized.
[0138]
Next, the operation of the CPU 14 when performing change processing when continuous recording / editing is performed will be described. When the CPU 14 of the host computer 10 is instructed to change the “continuous recording” of the attribute information of the directory entry, it starts the process of step S101 shown in FIG.
[0139]
In step S101, the CPU 14 determines whether or not a deletion process for continuously recorded files has been instructed. If the process is a file deletion process, the process proceeds to step S102, and if the process is not a file deletion process, the process proceeds to step S106.
[0140]
In step S102, the specified file deletion process command is transmitted to the memory card 20 to execute the file deletion process, and the process proceeds to step S103.
[0141]
In step S103, it is determined from the directory entry list of the parent directory whether the “continuous recording” of the directory entry of the deleted file is “11”. When “continuous recording” is “11”, the process proceeds to step S104, and when it is not “11”, the process is terminated.
[0142]
In step S104, it is determined whether the “continuous recording” of the directory entry next to the directory entry of the deleted file is “10”. If it is “10”, the process proceeds to step S105, and if it is not “10”. The process ends.
[0143]
In step S105, the "continuous recording" of the next directory entry is changed to "11", the file indicated by the next directory entry is set to the head of the continuous recording, and the process is terminated.
[0144]
Therefore, as shown in FIG. 14 described above, when files 2 to 5 are continuously recorded, if file 2 is deleted, file 3 is shown as shown in FIG. 31 by the processing of steps S102 to S105. The continuous recording of the directory entry is changed to “11”. That is, only when the first file of continuous recording is deleted and the next file to be deleted is in the middle of continuous recording, the “continuous recording” of the next file is set to “11”. change. As a result, even when continuously recording files are deleted, the continuous recording state of each file that has not been deleted can be maintained.
[0145]
On the other hand, in step S106 when it is determined that the deletion process is not performed in step S101, it is determined whether a new file insertion process is instructed between continuously recorded files. If the file insertion process is performed, the process proceeds to step S110. If it is not a file insertion process, the process proceeds to step S107.
[0146]
In step S107, it is determined whether the group changing process shown in FIG. 19 or the like has been instructed. If the group changing process, the process proceeds to step S108, and if not the group changing process, the process ends.
[0147]
In step S108, the “group number” of the directory entry list indicating the file whose group is to be changed is changed from the directory entry list of the parent directory, and the process proceeds to step S109.
[0148]
In step S109, it is determined whether or not “continuous recording” of the directory entry is “00”. If it is “00”, the process ends. If it is not “00”, the process proceeds to step S104. Then, the processes of steps S104 and S105 described above are performed.
[0149]
Therefore, since the file whose group has been changed is out of the continuous recording state except for the normal file whose “continuous recording” is “00”, if the “continuous recording” of the immediately following file is “10”, The “continuous recording” of the directory entry of the file immediately after that is set to “11”. As a result, the file immediately after the file whose group has been changed can be set to the top of the continuous recording, and the continuous recording state of each file having no group change can be maintained.
[0150]
On the other hand, in step S110 when it is determined in step S106 that the insertion process is to be performed, the file to be inserted is actually inserted, and the process proceeds to step S111.
[0151]
In step S111, it is determined whether the “continuous recording” of the directory entry corresponding to the file next to the inserted file is “10”. If it is “10”, the process proceeds to step S112, and if it is not “10”. Advances to step S113.
[0152]
In step S112, the “continuous recording” of the inserted file is set to “10”, and the process ends.
[0153]
In step S113, the “continuous recording” of the inserted file is set to “00”, and the process ends.
[0154]
For example, in FIG. 14 described above, when the file 5.5 is inserted between the file 5 and the file 6, as shown in FIG. 32, the “continuous recording” of the next file 6 is “11”. By the process of S113, the “continuous recording” of the inserted file becomes “00”. Further, when the file 7.5 is inserted between the file 7 and the file 8, the “continuous recording” of the next file 8 is “10”, and therefore the “continuous recording” of the inserted file is performed by the processing of steps S111 and S112. "Becomes" 10 ".As the continuous recording is changed, the file number is also changed so that the files are continuous.
[0155]
Therefore, when a file is inserted immediately before continuous recording of each file, the file is in a normal state, and when a file is inserted during continuous recording, the file is in a continuous recording state. .
[0156]
As described above in detail, the present invention can read, write and erase files without using file names and directory names, and can manage directories and files with a smaller amount of data. Therefore, it is suitable for recording a file or the like on a recording medium having a relatively small storage capacity such as the flash memory 22.
[0157]
In the present embodiment, a memory card including a flash memory has been described as an example of a recording medium. However, the present invention is not limited to this, and the present invention is not limited to this example, and may be a medium such as a magnetic disk or an optical disk. Of course, it is applicable.
[0158]
【The invention's effect】
According to the file management apparatus and the file management method of the present invention, by providing continuous recording information indicating whether or not each file is the first continuous, a group of continuously recorded files without newly providing a directory. Can recognize if there is. Therefore, it is possible to easily recognize whether the file is a group of files while avoiding the processing burden on the management unit and the increase in the amount of data in the recording medium due to the provision of a new directory.
[0159]
According to the recording medium of the present invention, by recording only continuous recording information indicating whether each file is the first continuous or not, it is recognized whether or not it is a group of files continuously recorded with a smaller amount of data. be able to.
[0160]
According to the file management system and the file management method of the present invention, it is possible to determine whether a group of continuously recorded files by providing continuous recording information indicating whether each file is the first continuous without providing a new directory. You can recognize whether or not. Therefore, it is possible to easily recognize whether or not the file is a group of files with a smaller amount of data while avoiding the processing load of the management unit and the increase in the amount of data in the recording medium due to the provision of a new directory.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a memory card system to which the present invention is applied.
FIG. 2 is a diagram for explaining a configuration of data stored in a flash memory in a memory card of the memory card system.
FIG. 3 is a diagram for explaining a configuration of a user format file stored in the flash memory;
FIG. 4 is a diagram for explaining a configuration of an OS header of the file.
FIG. 5 is a diagram for explaining a configuration of a file header and an entry area of the file.
FIG. 6 is a diagram for explaining the configuration of a directory file.
FIG. 7 is a diagram for explaining a configuration of a system entry area of the directory file.
FIG. 8 is a diagram for explaining a configuration of directory information of the directory file.
FIG. 9 is an explanatory diagram of a system directory area and a user area determined by the directory information.
FIG. 10 is a diagram for explaining a configuration of group information of the directory file.
FIG. 11 is a diagram for explaining the configuration of a directory entry list of the directory file.
FIG. 12 is a diagram for explaining the file number of each directory entry.
FIG. 13 is a diagram for explaining attribute information of each directory entry.
FIG. 14 is an explanatory diagram of a state of continuous recording of each file.
FIG. 15 is a diagram for explaining a group number of each directory entry;
FIG. 16 is a diagram for explaining handling of groups in a directory;
FIG. 17 is a diagram for explaining handling of groups in a directory;
FIG. 18 is a diagram illustrating a relationship between each file and a group.
FIG. 19 is an explanatory diagram of a hierarchical structure when a group is supported.
FIG. 20 is an explanatory diagram of a hierarchical structure when a group is not supported.
FIG. 21 is an explanatory diagram of a hierarchical structure when a group is not supported.
FIG. 22 is a flowchart showing processing when starting up an application;
FIG. 23 is a flowchart showing processing when a directory is created.
FIG. 24 is a flowchart showing a process for registering a file.
FIG. 25 is a flowchart showing processing when there is a target flag;
FIG. 26 is a flowchart showing processing when there is no target flag;
FIG. 27 is a flowchart illustrating processing when an image file is read.
FIG. 28 is a flowchart illustrating processing when deleting an image file.
FIG. 29 is a flowchart showing processing when a directory is deleted.
FIG. 30 is a flowchart showing processing when changing the state of continuous recording.
FIG. 31 is a diagram illustrating a state of continuous recording when one file is deleted.
FIG. 32 is a diagram illustrating a state of continuous recording when a file is inserted.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 Memory card system, 10 Host computer, 11 Hard disk, 12 RAM, 13 1st serial I / F, 14 CPU, 20 Memory card, 21 2nd serial I / F, 22 Flash memory, 23 Controller

Claims (20)

Storage means for storing a file having a file number and a directory having a directory entry consisting of continuous recording information indicating whether the file is continuously recorded as a group of files;
Management means for managing the file or directory indicated by the file number of the directory entry of one stored directory so as to be in a hierarchy below the one directory;
The storage means stores, as the directory, a directory having a file entry and a directory entry composed of continuous recording information indicating whether or not it is the first of continuous, for each file,
The management means manages each file indicated by each successive directory entry of the one directory as a group of continuous files based on the continuous recording information of the one directory read from the storage means,
The management means, based on the continuous recording information of the one directory read from the storage means, from the file number of the directory entry having the continuous recording information indicating the beginning of the continuous, continuous recording information indicating the beginning of the next continuous Manage the file indicated by the file number up to the directory entry immediately before the directory entry having
Even for a predetermined file already recorded in the storage means, the file can be inserted and edited in a set of continuously recorded files by changing the order of the file numbers recorded in the directory entry. A file management apparatus characterized by the above. When a predetermined file already recorded in the storage means is inserted into a set of continuously recorded files, when inserting as the beginning of the continuous recording, the continuous information of the file is set to the beginning of the continuous. The file management apparatus according to claim 1, wherein the file management apparatus records information together with the continuous recording information indicated. When a predetermined file that has already been recorded in the storage means is inserted into a set of continuously recorded files, the continuous information of the file must be stored in the middle of the continuous recording. The file management apparatus according to claim 1, wherein the file management apparatus is recorded together with continuous recording information indicating that When a predetermined file already recorded in the storage means is inserted into a set of continuously recorded files, the continuous information of the file is irrelevant to the continuity when it is inserted as a file that delimits the continuous recording. The file management apparatus according to claim 1, wherein the file management apparatus is recorded together with continuous recording information indicating that Storing a directory having a file having a file number and a directory entry for each file including a file number and whether the file is continuously recorded as a group of files and continuous recording information indicating whether the file is the first in a series;
Read the continuous recording information of the above one directory,
Based on the read continuous recording information of the one directory, the directory entry immediately before the directory entry having the continuous recording information indicating the first of the next continuous from the file number of the directory entry having the continuous recording information indicating the first of the continuous Manage the files indicated by the file numbers up to a group of continuous files,
File management that enables the file to be inserted and edited in a set of continuously recorded files by changing the order of the file numbers recorded in the directory entry even if the file is already recorded Method. When a predetermined file already recorded in the storage means is inserted into a set of continuously recorded files, when inserting as the beginning of the continuous recording, the continuous information of the file is set to the beginning of the continuous. 6. The file management method according to claim 5, wherein recording is performed together with the continuous recording information indicated. When inserting a predetermined file that has already been recorded into a set of continuously recorded files, the continuous information of the file must be in the middle of the continuous recording when it is inserted as a file in the middle of the continuous recording. 6. The file management method according to claim 5, wherein recording is performed together with continuous recording information indicating. When a predetermined file already recorded is inserted into a set of continuously recorded files, the continuous information of the file is irrelevant to the continuity when it is inserted as a file that delimits the continuous recording. 6. The file management method according to claim 5, wherein recording is performed together with continuous recording information indicating. A file having a file number, and a directory having a directory entry for each file indicating whether the file number and the file are continuously recorded as a group of files and continuously recording information indicating whether the file is the first in the sequence,
Based on the continuous recording information of the one directory, from the file number of the directory entry having the continuous recording information indicating the first of the continuous to the directory entry immediately before the directory entry having the continuous recording information indicating the first of the next continuous Manage the file indicated by the file number as a group of continuous files,
A recording medium that can insert and edit a file in a set of continuously recorded files by changing the order of the file numbers recorded in the directory entry, even if the file is already recorded . When a predetermined file already recorded is inserted into a set of continuously recorded files, the continuous recording of the file indicates that the continuous information of the file indicates the beginning of the continuous. The recording medium according to claim 9, wherein the recording medium is recorded together with information. When a predetermined file already recorded is inserted into a set of continuously recorded files, the continuous information of the file must be in the middle of the continuous recording when the file is inserted as a continuous recording file. The recording medium according to claim 9, wherein the recording medium is recorded together with continuous recording information indicating. When a predetermined file that has already been recorded is inserted into a set of continuously recorded files, the continuous information of the file is not related to continuity when the file is inserted as a file that delimits the continuous recording. The recording medium according to claim 9, wherein the recording medium is recorded together with continuous recording information indicating. A record for recording a file having a file number and a directory having a directory entry for each file indicating whether the file number and the file are continuously recorded as a group of files and whether or not it is the first of the continuous Medium,
Storage means for storing the file and directory read from the recording medium, and the file or directory indicated by the file number of the directory entry of the stored one directory is managed so as to be a hierarchy below the one directory. And a file management device having management means for
The management means manages each file indicated by each successive directory entry of the one directory as a group of continuous files based on the continuous recording information of the one directory read from the storage means,
The management means, based on the continuous recording information of the one directory read from the storage means, from the file number of the directory entry having the continuous recording information indicating the beginning of the continuous, continuous recording information indicating the beginning of the next continuous Manage the file indicated by the file number up to the directory entry immediately before the directory entry having
Even for a predetermined file already recorded in the storage means, the file can be inserted and edited in a set of continuously recorded files by changing the order of the file numbers recorded in the directory entry. A file management system characterized by: When a predetermined file already recorded in the storage means is inserted into a set of continuously recorded files, when inserting as the beginning of the continuous recording, the continuous information of the file is set to the beginning of the continuous. 14. The file management system according to claim 13, wherein recording is performed together with the continuous recording information indicated. When a predetermined file that has already been recorded in the storage means is inserted into a set of continuously recorded files, the continuous information of the file must be stored in the middle of the continuous recording. 14. The file management system according to claim 13, wherein recording is performed together with continuous recording information indicating that When a predetermined file already recorded in the storage means is inserted into a set of continuously recorded files, the continuous information of the file is irrelevant to the continuity when it is inserted as a file that delimits the continuous recording. 14. The file management system according to claim 13, wherein recording is performed together with continuous recording information indicating that A recording medium includes a file having a file number and a directory having a file entry and a directory entry including continuous recording information indicating whether the file is continuously recorded as a group of files and indicating whether the file is the first in the series or not. Record,
Read a file and directory from the recording medium, store the read file and directory,
A file from a file number of a directory entry having continuous recording information indicating the first of the continuous to a directory entry immediately before the directory entry having continuous recording information indicating the first of the next continuous, based on the continuous recording information of one directory Manage the file indicated by the number as a group of continuous files,
File management that enables the file to be inserted and edited in a set of continuously recorded files by changing the order of the file numbers recorded in the directory entry even if the file is already recorded Method. When a predetermined file already recorded in the storage means is inserted into a set of continuously recorded files, when inserting as the beginning of the continuous recording, the continuous information of the file is set to the beginning of the continuous. 18. The file management method according to claim 17, wherein recording is performed together with the continuous recording information indicated. When inserting a predetermined file that has already been recorded into a set of continuously recorded files, the continuous information of the file must be in the middle of the continuous recording when it is inserted as a file in the middle of the continuous recording. 18. The file management method according to claim 17, wherein the file management method is recorded together with the continuous recording information indicating. When a predetermined file already recorded is inserted into a set of continuously recorded files, the continuous information of the file is irrelevant to the continuity when it is inserted as a file that delimits the continuous recording. 18. The file management method according to claim 17, wherein the file management method is recorded together with the continuous recording information indicating.

Images