JP2649675B2 - Optical disk storage management method - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to a storage management method for an optical disk.

[Prior Art] In recent years, an optical disk apparatus using an optical disk in which an optical storage medium is formed in a disk shape as a storage medium has been put into practical use, and an image data filing apparatus which handles a large amount of data, or a large capacity It is applied to auxiliary storage devices and the like.

The track pitch is 1-2 on the surface of this optical disc.
A recording track of μm is formed, and data is recorded by changing the state of the surface of the recording track (for example, the reflectance) in accordance with the data to be recorded. In many cases, when data is recorded, the surface of the recording track is destroyed, so that the recorded data cannot be directly updated on the recording track.

On the optical disk, data is recorded / reproduced in sector units of a predetermined length (for example, 2048 bytes), thereby increasing the degree of freedom of file access and improving the efficiency of error correction processing for correcting data errors. Can do well.

By the way, for example, when an optical disk device is used as an image filing device, conventionally, image information is managed independently in page units.

Therefore, search information is added to each page so that each piece of image information can be identified / searched.

However, since the number of pages of image information stored on the optical disk is very large, the storage area of the optical disk required for storing the search information is large, and the recording efficiency of data on the optical disk deteriorates. I was

Therefore, in order to solve such inconvenience, it is conceivable to collectively manage a plurality of pieces of image information in one file.

However, in this method, for example, when the same image information is used in common for a plurality of files, it is necessary to input the image information when forming each file, which is troublesome and also increases the efficiency of use of the optical disc. Is disadvantageously reduced.

[Purpose] The present invention has been made in order to solve the disadvantages of the related art, and has as its object to provide a storage management method of an optical disc that can improve the use efficiency of the optical disc.

[Structure] In order to achieve this object, the present invention provides a data file composed of a plurality of variable length records, and stores and manages the storage state in the data area of each variable length record constituting the data file in a record order. In addition to registering information in a file header, variable-length records belonging to different data files can be registered in the file header.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 shows an optical disk system according to one embodiment of the present invention. This system includes a host device HST and an optical disk device ODE.

In the host device HST, the central processing unit 1 is for performing various data processing such as processing for the file system according to the present invention. This processing program is stored in the program memory 2 and the work area is the work memory 3. Formed.

The CRT display device 4 and the keyboard 5 form a man-machine interface with the host device HST, and the magnetic disk control device 6 and the magnetic disk drive device 7 are auxiliary storages mainly used in the host device HST. Make up the device.

The optical disk interface 8 is for exchanging data between the host device HST and the optical disk device ODE.
This is for exchanging data with an external device such as an image reading device or an image recording device.

Then, these central processing unit 1, program memory 2, work memory 3, CRT display device 4, keyboard 5,
Data is exchanged between the magnetic disk controller 6, the optical disk interface 8, and the external interface 9 via the system bus 10.

In the optical disk device ODE, the optical disk control device 11
Is for exchanging data with the host device HST and recording / reproducing data on / from the optical disk driven by the optical disk drive device 12.

As is well known, an optical disc has a physical format for recording / reproducing data in units of a predetermined length of sector, and a sector address is set for each sector. In this embodiment, one sector is
It consists of 2048 bytes (2K bytes).

2 (a) to 2 (e) exemplify a divided state of a storage area of an optical disk.

The storage area of the optical disk is divided into two areas: a data area AD for storing a data file and a management information area AM for storing management information for accessing the data file. It is divided into a header area HD, a system area SM, and a search data area KY. In this case, the sector address 0 matches the start of the management information area AM, and the end of the data area AD matches the last sector address that can be accessed from outside.

The system area SM includes system area link information for indicating a secondary system area (not shown) that is secured when the system area SM is full, and a file header (described later).
File identifiers for efficient access to
An FID directory area in which a directory (referred to as FID hereinafter) is stored, and a file header for registering the recording state of each data file or search data file in the data area AD or the search data area KY. It consists of a file header area.

The search data area KY includes search data area link information for indicating a secondary search data area (not shown) that is secured when the search data area KY is full, and search data. It consists of a search data file area in which files are stored.

The header area HD includes a volume mark for displaying characteristics and the like of the optical disc, a data area last sector number indicating a last sector number (sector address) of the data area AD,
A header area last sector number indicating the last sector number of the header area HD, a volume name for identifying the optical disc,
Start logical block address of the system area SM (hereafter, LB
A), the system area size indicating the size of the storage area allocated to the area in sector units, various control flags, the FID directory area start LBA indicating the FID directory area start LBA, and the like. Indicates the size of the storage area allocated to the area in sector units
FID directory area size, file header area LBA that indicates the head LBA of the file header area, file header area size that indicates the size of the storage area allocated to the area in sector units, and head LBA of the search data area KY It is composed of a search data area start LBA, a search data area size indicating the size of the storage area allocated to the area in sector units, and a data area start LBA indicating the start LBA of the data area AD.

Therefore, based on the contents of the header area HD, the identification of the optical disk and the allocation status of each area can be known.

Here, in general, the LBA and the sector address (sector number) are the same, but a physically defective sector is replaced by another good sector by the optical disk device ODE, so that not all the sectors are identical. Note that the replacement sector area is set further outside the data area AD.

The system area link information is at the beginning of the next system area.
Next system area start LBA indicating LBA, next system area size indicating the size of the storage area allocated to the area in sector units, control flag for displaying the presence or absence of the next system area, FID directory in the next system area Next FID directory area first LBA indicating the area's first LBA, next FID directory area size indicating the size of the storage area allocated to the area in units of sectors, next file area's first LBA indicating the file header area in the next system area The first LBA of the file header area, the size of the next file header area indicating the size of the storage area allocated to the area in sector units, and the file header number (hereinafter referred to as the FNO
And the next file header last FNO indicating the FNO assigned to the last file header in the next file header area.
Consists of

Therefore, based on the system area link information, the presence or absence of the next system area and the allocation status of each area in the next system area can be known.

The search data area link information includes a next search data area start LBA indicating the next search data area start LBA, a next search data area size indicating the size of the storage area allocated to the area in sector units, And a control flag for displaying the presence or absence of the next search data area.

Therefore, based on the search data area link information, the presence / absence of the next search data area and the allocation status of the next search data area can be known.

The next system area and the next search data area link information are secured in the empty area of the data area AD at the time when the system information SM and the search data area KY are full, and at the same time, the system area link Information and search data area link information are each formed and stored.

In the FID directory area, as shown in FIG. 3 (a), FID directory blocks are stored in sector units. Each FID directory block has a block header, a predetermined number, as shown in FIG. 3 (b). FID
It consists of a directory and a block header backup.

The contents of the block header and the block header backup are the same, and the first FNO of the next FID directory block indicating the first FNO of the next FID directory block is stored as shown in FIG.

One FID directory is made up of an FID, a version number (hereinafter, referred to as VNO), and an FNO, as shown in FIG.

Here, the FID is set by the host device HST to identify the file (data file or search data file; the same applies hereinafter), and the VNO and FNO are set to the optical disk device ODE when the file header is generated / updated. Is set automatically. Note that VNO is set to 1 when a file is generated, and thereafter, is incremented with updating.

For example, if the size of the block header and the block header backup is 24 bytes, and the size of the FID directory is 10 bytes, 200 FID directories are stored in one FID directory block. Therefore, in that case, every time 200 new file headers are formed, 200 FIDs corresponding to those file headers are created.
The directory is recorded in a new FID directory block. At the time of this recording, the 200 FID directories
Sorted in ascending order using FID and VNO as keys.

In the file header area, as shown in FIG. 4A, a file header block is stored in sector units.
For example, 16 file headers are stored in one file header block as shown in FIG. In this case, the size of one file header is 128 bytes.

There are two types of file headers, a basic file header FDN as shown in FIG. 4 (c) and an extended file header FDE as shown in FIG. 4 (d).

The basic file header FDN includes a basic file header management information section FDNa for identifying each basic file header FDN, and a mapping data section MPNa for registering a recording state of a file managed by the file header. The extended file header FDE includes an extended file header management information section FDEa for identifying each extended file FDE, and a mapping data section MPEa for registering a file recording state.

The basic file header management information section FDNa is a file header identifier of a value “1” indicating that the file header is the basic file header FDN, and a file header continuous number indicating the number of extended file headers FDE following the basic file header FDN. , FNO, FID, VNO, file type for identifying whether the file managed by this file header is a data file or a search data file, a creation date indicating the date when the file was created, and the file The update date, which indicates the date on which the file was updated, the file size, which indicates the total data size of the file, the maximum record side, which indicates the size of the largest record (described later) when the file is a data file, and after the file was created / updated Of the empty area of the data area at the time of closing It consists of a data area current pointer representing the head LBA, and a search data file area current pointer representing the head LBA of the current search data file when the file is closed after being generated / updated.

Here, the file header number FNO is set as follows.

That is, when generating one file header, using the LBA of the file header block in which the file header is stored and the offset (order number starting from 0) of the file header in the file header block, the following expression is used. Is calculated.

FNO = LBA × 16 + (offset) The extended file header management information section FDEa is registered in the mapping data section MPEa of the file header identifier, FNO and the extended file header FDE having the order in which the sequence is continuous with the basic file header FDN. It consists of an extended file type that indicates the type of record that is present. The FNO has the same value as the FNO of the corresponding basic file header FDN.

Here, the configurations of the data file and the search data file will be described.

As shown in FIG. 5 (a), one data file is made up of a plurality of records each having a variable length and composed of a set of data. For example, when the data file is image data, one record corresponds to one page of image data. However, a plurality of records constituting one data file are not always recorded in a continuous area.

Since data recording / reproduction on the optical disk is performed in units of sectors (SC), the data of each record is recorded on the optical disk in units of sectors. Also,
If there is an empty area in the last sector where the record is recorded,
The empty area is filled with “0”.

In addition to the types of records that are recorded in the continuous area, there are divided records that are divided into a plurality of segments and recorded as shown in FIG. 5B. In this case as well, each record segment is recorded in sector units, and if there is an empty area in the maximum number of sectors where the record segment is recorded, the empty area is filled with "0".

The area of one search data file is shown in FIG.
As shown in (1), a plurality of blocks having the same size as a sector are secured in a continuous area. This area is secured when the search data file is generated, and thereafter, the contents of the test data file are recorded in empty blocks of the secured area as required by the host system. Also in this case, recording / reproduction of data is performed in units of blocks (sectors), and each block is designated by an order number from the head of the area.

Therefore, the mapping data part MPNa of the basic file header FDN and the mapping data part MPEa of the extended file header FDE have records such as those shown in FIGS. 6 (a) to (d) according to the type of each file and record. Definition data NSR, division record definition data STR, division record map data SDM, and search data file definition data KYM are arranged.

The record definition data NSR includes a record type taking a value “0” representing a non-divided record, a record identifier for identifying each record in the file, a record size representing a record size, and a head LBA of the record. It consists of the LBA at the head of the record.

The divided record definition data SDR includes a record type, a record identifier, and a value that take a value “1” representing the divided record.
Record size, the number of segments that represent the number of record segments that make up the record, and the divided record map data that registers data about the first record segment of that divided record in the mapping data section MPEa of the next extended file header FDE It consists of a segment map offset indicating the order of SDM.

The divided record map data SDM includes a segment number indicating the order of the record segments in the divided record, a record identifier, a segment length indicating the size of the segment, and a record segment head LBA indicating the head LBA of the record segment.

The search data file definition data KYM is a search data block size that indicates the size of the area allocated to the search data file, and the head of the search data file that indicates the head LBA of the area allocated to the search data file. Consists of LBA.

Therefore, a data file consisting of the records 1 to 4 shown in FIGS. 5A and 5B, and FIG.
The file header indicating the search data file shown in FIG. 7 is as shown in FIGS. 7A and 7B, respectively.

That is, the file header of the data file includes the basic file header FDN1 and the extension file header FDE1, and the file header of the search data file includes the basic file header FDN2.

In the mapping data part of the basic file header FDN1,
The record definition data NSR1 to NSR3 of the records 1 to 3 and the divided record definition data SDR4 of the record 4 are arranged in the record order, and the mapping data part of the extended file header FDE1 includes the divided record map data SDM1 of the record segment of the record 4. , SDM2 are arranged in segment order. Note that the record identifiers of the divided record map data SDM1 and SDM2 have the same value as the record identifier of the divided record definition data SDR4.

In the mapping data part of the basic file header FDN2,
Search data file definition data KYM1 corresponding to the area allocated to the search data file is arranged.

FIG. 8 shows a general format of a file header of a data file. However, if the file header fits only in the basic file header, no extended file header is added, and if it does not include a divided record, no extended file header having a divided record definition part is added to the mapping data part.

With the above configuration, the central processing unit 1 records / reproduces data on / from the optical disk as follows. In this case, a control process for recording / reproducing data on the optical disc (hereinafter, referred to as an optical disc file system) and a control process for a higher-order file system (hereinafter, referred to as a file system), that is, setting of FID for a file , Data file configuration (for example, record configuration, etc.),
The configuration of the search data file and processing such as file search are performed by the central processing unit 1.

When the optical disk is set in the optical disk device ODE, first, the optical disk file system transfers the contents of the FID directory area of the system area SM to the magnetic disk device (consisting of the magnetic disk control device 6 and the magnetic disk drive device 7; the same applies hereinafter). read out.

At this time, if there is a file header that is not registered in the FID directory, the file header is read and an FID directory (hereinafter referred to as a current directory) relating to the unregistered file header is formed on the work memory 3. At this time, the FID directory data in the current directory is sorted in ascending order using the FID and VNO as keys.

In addition, the file header is generated /
When updated, the corresponding FID directory data is formed, and the FID directory data in the current directory is rearranged in the work memory 3 in the same manner as described above.

When 200 pieces of FID directory data are formed in the current directory (that is, FID directory blocks), the 200 pieces of FID directory data are recorded in a new FID directory block of the optical disc.

By the way, the file system specifies the FID of the search data file that registers the necessary search information,
Requests the optical disk file system to open a file.

As a result, the optical disk file system finds the FNO of the file header having the specified FID by referring to the FID directory, reads the target search file data by referring to the file header, and transfers the contents to the file system. I do.

Thereby, the file system searches for the target data file based on the contents of the search data file,
Get the FID for that data file. When the reading of the search data file is completed, the file system instructs the optical disc file system to close the inspection data file.

When reading the data file, the optical disk file system is requested to open the file with the FID of the data file specified.

Therefore, the optical disk file system finds the FNO of the file header having the designated FID by referring to the FID directory, reads out the target file data by referring to the file header, and transfers the contents to the file system.

When a desired data file is obtained in this way, the file system performs a process according to the type of the data file.

For example, the contents of the data file are displayed to the operator on the CRT display device 4 so that the operator can perform desired processing.

When the operator closes the data file without performing any operation on the data file, the file system requests the optical disk file system to close the file. Thereby, the optical disk file system closes the opened data file.

When the operator performs any operation on the data file, for example, deletes or adds a record, the file system transmits a command and data for updating the data file corresponding to the operation to the optical disk file system. Output to

As a result, the optical disk file system updates the data corresponding to the command and creates a new file header in the work memory 3 with the update,
Further, the current directory is updated based on the file header.

Then, when closing the accessed data file, the optical disk file system records a file header formed in accordance with the access in a temporary buffer formed in the magnetic disk device.

When updating the content of the search data file in conjunction with the creation / update of the data file, the file system records the FID attached to the search data file, the block number indicating the block for recording the update content, and the update data. The update data is transferred to the optical disk file system with the number of blocks to be specified specified.

Thereby, the optical disk file system obtains the FNO corresponding to the designated FID by referring to the FID directory, and reads the file header. Then, the target search data file is found, and the data transferred from the file system is sequentially recorded from the designated block. When the recording is completed, the file system instructs the optical disc file system to close the search data file.

When a series of operations is completed and the operator instructs to remove the optical disk, the optical disk file system stores the file header created in the temporary buffer of the magnetic disk device at that time in a new file header block. , Optical disk drive
The optical disk is ejected from 12.

If the number of file headers is formed for the file header block during access to the optical disk, the file header for one block is recorded in the file header area.

In this manner, the data file and the search data file can be recorded on the optical disc and read out.

Now, when a record registered in another data file is taken into another data file, the taking is performed as follows. In the following description, each record corresponds to, for example, one page of image information.

For example, as shown in FIG. 9, when the data file (FID = 1) composed of records 11 and 12 is to be imported into another data file (FID = 2) composed of records 21 and 22, the latter data file is used. The record definition data NSR of the fetched record 11 is added to the fetching position (in this case, the first record; RNO = 1) in the mapping data section of the file header of the file.

As a result, the record 11 is arranged at the first record of the data file (FID = 2). The RNO indicates the sequence number of a record in the data file, and the file system can access a target record by specifying the RNO.

Also, with the change of this record, the version of the data file is increased by one, and the VNO in the file header is changed.
Is updated. Of course, the FID will not change.

FIG. 10 shows an example of processing performed by the optical disk file system when a request from the file system is received to import a record specified in the target file into the edited file. Note that an edit file refers to a data file into which records are imported from another data file.
The target file is a data file in which records to be imported into the edit file are registered.

First, using the edit files FID and VNO, referring to the FID directory, the FNO of the file header of the edit file
And reads the file header (process 101).

Next, using the FID and VNO of the target file, referring to the FID directory, the FN of the file header of the edited file
O is obtained and its file header is read (process 102).

Then, the record definition data of the record of the RNO specified in the target file is copied from the file header of the target file, and the record definition data is inserted immediately before the record definition data of the RNO specified in the file header of the edit file. (Or add) to form a file header of the edited file that has been upgraded. Further, the current directory is updated according to the file header (process 103).

The file header of the edited file thus formed is output to the magnetic disk drive, and the edited file is closed (process 104). Then, the target file is closed (process 105), and this process ends.

As described above, according to the present embodiment, records registered in other data files can be captured. For example, when the same image information is commonly used in a plurality of files, the utilization efficiency of the optical disc is reduced. Can be improved.

[Effects] As described above, according to the present invention, a data file is composed of a plurality of variable length records, and the storage state of each variable length record constituting the data file in the data area is recorded in the file header in the record order. And the variable length records belonging to different data files can be taken into the file header, so that there is an advantage that the use efficiency of the optical disk can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an optical disk system according to one embodiment of the present invention, FIGS. 2 (a) to 2 (e) are schematic diagrams illustrating a divided state of a storage area of an optical disk, and FIG. 3 (a).
4A to 4D are schematic diagrams showing a configuration example of a file identifier directory area, FIGS. 4A to 4D are schematic diagrams showing a configuration example of a file header, and FIGS. 5A to 5C. Is a schematic diagram showing a configuration example of recording data, and FIGS. 6 (a) to (d).
FIG. 7 is a schematic diagram illustrating data arranged in the mapping data section, FIGS. 7A and 7B are schematic diagrams illustrating a file header, FIG. 8 is a schematic diagram illustrating a general example of a file header, FIG. 9 is a schematic diagram for explaining record fetching, and FIG. 10 is a flowchart showing an example of processing performed by the optical disk file system when fetching records. HST: Host device, ODE: Optical disk device.

Claims (1)

(57) [Claims] In an optical disk storage management method in which a storage area of an optical disk is divided into a data area and a storage management information area, a data file is composed of a plurality of variable length records, and each variable length record of the data file is composed of a plurality of variable length records. A storage management method for an optical disk, characterized in that a storage state in a data area is registered in a file header constituting storage management information in a record order, and that variable length records belonging to different data files can be registered in the file header.