KR100657346B1 - Optical Recording medium, recording/reproducing method and recording/reproducing apparatus - Google Patents

Abstract

Disclosed is an optical recording information storage medium, a recording / reproducing method, and a recording / reproducing apparatus according to the present invention.

An optical recording information storage medium according to the present invention is provided with a lead-in area, a data area and a lead-out area, wherein the data area replaces a user data area for recording user data and a defective block generated in the user data area. A spare area for a spare block for managing the defect block and a defect list entry containing state information of the replacement block, and managing the spare block in the user data area before newly reassigning the spare area for re-initialization of a medium. If an existing defective block exists in the user data area even after the reinitialization, the status information of the defective block is changed to status information indicating that the defective block is a reinitialized block and may be a defect. According to the present invention as described above, the disk reinitialization can be quickly performed, and the drive system can be improved by eliminating unnecessary operation of the drive system in the future by managing defect state information of the blocks.

Description

Optical recording medium, recording / reproducing method, recording / reproducing apparatus

1 is a schematic block diagram of a configuration of a recording / reproducing apparatus according to the present invention;

2 is a structural diagram of a single recording layer disc according to the present invention;

3 is a structural diagram of a double recording layer disc according to the present invention;

4 is a data structure diagram of a defect list according to the present invention;

5 is a data structure diagram of a defect list entry shown in FIG. 4;

6 is a reference diagram for describing state information of a defect list entry illustrated in FIG. 5;

7 is a reference diagram for explaining a method for processing a defect list entry of a block in a newly allocated spare area due to disk reinitialization according to the present invention;

(A) of FIG. 8 shows state information of a defect list immediately before a new spare area allocation in accordance with the present invention in the situation shown in FIG. 7 (a), and (b) is new in the situation shown in FIG. A diagram showing status information of a defect list immediately after allocation of the spare area;

9 is a reference diagram for explaining a method of processing a defect list entry of a block in a newly allocated spare area due to disk reinitialization according to the present invention;

(A) of FIG. 10 shows status information of a defect list immediately before a new spare area allocation in accordance with the present invention in the situation shown in FIG. 9 (a), and (b) is new in the situation shown in FIG. 9 (b). A diagram showing status information of a defect list immediately after allocation of the spare area;

FIG. 11 is a diagram showing a DFL entry in three states when state information 1 is " 3 " representing a state that may be a defect in accordance with the present invention; FIG.

12 is a reference diagram for explaining a state in which a continuous defect block of known length is partially present in the spare area and part of the user data area according to the present invention;

FIG. 13 is a reference diagram for explaining a change of a DFL entry in the situation shown in FIG. 12; FIG.

14 is a reference diagram for explaining a state in which a start address of a continuous defect block exists in a user data area or exists in a spare area due to allocation of a new spare area of a continuous defect block of unknown length according to the present invention;

15 is a reference diagram for explaining a change of a DFL entry in the situation shown in FIG. 14;

16A and 16B are flowcharts illustrating the process of a reinitialization method according to the present invention.

The present invention relates to the field of discs, and more particularly, to an optical record information storage medium, a recording / reproducing method, and a recording / reproducing apparatus for disc reinitialization.

While using the rewritable information storage medium, scratches, fingerprints, dust, etc., increase the defects on the medium. Defective blocks that occur during the use of the medium are registered and managed as defect information, and the host or drive system will write the data in good blocks without allocating data to these defective blocks as much as possible. As the disk continues to be used, these defective blocks will increase. Thus, the user will want to reinitialize the disk.

In such a case, when the user removes fingerprints or dust generated on the disk surface, the defective blocks registered on the defect information may be judged as good blocks through black after recording. As described above, when re-initialization of the rewritable information storage medium is required, the drive system determines whether there is a defect through the test after writing the blocks of the recordable area of the entire disk or the defective blocks registered on the defect information.

As described above, when reinitializing the rewritable information storage medium, if the defective blocks registered on the entire disk or the defect information are recorded and judged as defective through the verification, the reinitialization takes too long, which may cause inconvenience to the user. .

SUMMARY OF THE INVENTION An object of the present invention is to provide an optical recording information storage medium, a recording / reproducing method, and a recording / reproducing apparatus, which can solve the above problems and quickly perform disk reinitialization.

One feature of the present invention for solving the above problems is an optical recording information storage medium, wherein the medium is provided with a lead-in area, a data area and a lead-out area, and the data area is for recording user data. And a spare area for a replacement block for replacing a defective block generated in the user data area, and a defect list entry containing state information of the defective block and the replacement block is managed, If the defective block in the user data area before the spare area is newly allocated for reinitialization is in the user data area even after the reinitialization, the status information of the defective block is reinitialized and the defect may be defective. Changes to status information indicating that this is a possible block .

It is preferable that the defective block in the user data area before allocation of the spare area includes a defective block having a replacement block, a defective block having no replacement block, and a block that may be a defect.

According to another aspect of the present invention, in an optical recording information storage medium, the medium includes a lead-in area, a data area, and a lead-out area, and the data area includes a user data area for recording user data and the user data area. A spare area for a replacement block for replacing a defective block generated in the second block; a defect list entry containing state information of the defective block and the replacement block is managed, and the spare area is newly created for reinitialization of a medium. If a defective block in the user data area before being allocated is included as a replacement block of the newly allocated spare area after the reinitialization, the state information of the replacement block is reinitialized and the replacement block may be used for replacement. It is changed to status information indicating that the block is missing.

It is preferable that the defective block in the user data area before allocation of the spare area includes a defective block having a replacement block, a defective block having no replacement block, and a block that may be a defect.

According to still another aspect of the present invention, in an optical recording information storage medium, the medium includes a lead-in area, a data area, and a lead-out area, and the data area includes a user data area for recording user data and the user data. A spare area for a replacement block for replacing a defective block generated in the area, a defect list entry containing state information of the defect block and the replacement block is managed, and the spare area is managed for reinitialization of a medium. If a replacement block that is not available for replacement that was in the spare area before being newly allocated is included as a defective block in the user data area after the reinitialization, the status information of the defective block is reinitialized and the defect may be defective. Is changed to state information indicating a possible block .

According to still another aspect of the present invention, in an optical recording information storage medium, the medium includes a lead-in area, a data area, and a lead-out area, and the data area includes a user data area for recording user data and the user data. A spare area for a replacement block for replacing a defective block generated in the area, a defect list entry containing state information of the defect block and the replacement block is managed, and the spare area is managed for reinitialization of a medium. If newly allocated, the state information of the defective block in the user data area and the replacement block in the spare area is changed.

The defect list entry may include physical address information of a defective block, physical address information of a replacement block for replacing the defective block, first state information indicating a defect state of the defective block or the availability state of the replacement block, and It is preferred to include second state information indicating whether the medium is reinitialized.

If the defective block in the user data area before the spare area is newly allocated is in the user data area even after the reinitialization, the defect list entry of the defective block indicates that the defective block is a block that may be defective. Preferably, the first state information and the defect block are changed to a defect list entry that includes second state information indicating reinitialization.

If a defective block in the user data area before the spare area is newly allocated is included as a replacement block of the newly allocated spare area after the reinitialization, the defect list entry of the replacement block is replaced by the replacement block. Preferably, the replacement block is changed to a defect list entry including first state information indicating that the block cannot be used and second replacement information indicating that the replacement block has been reinitialized.

If a replacement block that cannot be used for replacement in the spare area before the spare area is newly allocated becomes a defective block of the user data area after the reinitialization, the defect list entry of the defective block is defective. Preferably, the defect list entry is changed to include first state information indicating that the block may be a second state information indicating that the defective block is reinitialized.

Before allocating the new spare area, if there is a contiguous defect list entry in which the probable blocks are arranged consecutively and do not know the length of the contiguous block, a predetermined number of blocks from the start block of the contiguous block. Based on the result of the test by " test after write ", for a contiguous block belonging to the user data area after the allocation of a new spare area, first state information according to the test result and second state information indicating that it has been reinitialized First status information and reinitialization indicating that the containing defect list entry is registered and belongs to a newly allocated spare area and that the block can be used for replacement or a block that cannot be used for replacement according to the test result. A lease containing second state information indicating that the It is an entry registration is preferred.

Prior to the allocation of the new spare area, if there is a contiguous defect list entry in which the blocks likely to be defects are arranged consecutively and do not know the length of the contiguous block, the start block of the contiguous block is the new spare area. If it belongs to the user data area after the assignment of, the consecutive defect list entry is maintained. If the start block of the consecutive block belongs to the newly allocated spare area, a predetermined number of blocks are written from the start block. Based on the results of the test by " test ", a defect list entry is registered that includes first state information indicating that the block can be used for replacement or a block that cannot be used for the replacement and second state information indicating that it has been reinitialized. It is preferable.

According to still another aspect of the present invention, in a recording / reproducing method, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, wherein the spare area is newly allocated for reinitialization of an optical recording medium in which a defect list entry containing state information of the defective block and the replacement block is managed; And if the defective block in the user data area is in the user data area even after the reinitialization by assigning the spare area, the status information of the defective block is reinitialized and is likely to be defective. Change the status information indicating that the block It is to include.

According to still another aspect of the present invention, in a recording / reproducing method, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, wherein the spare area is newly allocated for reinitialization of an optical recording medium in which a defect list entry containing state information of the defective block and the replacement block is managed; And if the defective block in the user data area is included as a replacement block of the newly allocated spare area after the re-initialization by new allocation of the spare area, the replacement block may include the state information of the replacement block. Phase indicating that the block has been reinitialized and cannot be used for replacement It comprises the step of changing the information is preferred.

According to still another aspect of the present invention, in a recording / reproducing method, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, wherein the spare area is newly allocated for reinitialization of an optical recording medium in which a defect list entry containing state information of the defective block and the replacement block is managed; And if the replacement block that cannot be used for replacement in the spare area before the spare area is newly allocated is included as a defective block of the user data area after the reinitialization, the defect information of the defective block is stored. Block is reinitialized and indicates that the block is likely defective Changing to status information.

According to still another aspect of the present invention, in a recording / reproducing method, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, wherein the spare area is newly allocated for reinitialization of an optical recording medium in which a defect list entry containing state information of the defective block and the replacement block is managed; And changing status information of a defective block in the user data area and a replacement block in the spare area.

According to still another aspect of the present invention, in a recording / reproducing apparatus, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, wherein the defect list and a defect list entry containing state information of the replacement block are read out from or recorded on the optical recording medium on which the recording medium is managed; A recording / reading section and a new allocation of the spare area for reinitialization of the medium, and if a defective block in the user data area exists in the user data area even after the reinitialization by allocating the spare area; Status information of a faulty block, said faulty block being reinitialized and And a control unit for controlling the recording / reading unit to change and record the state information indicating that the block may be a box.

In still another aspect of the present invention, in a recording / reproducing apparatus, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, the data being read from and recording data to and from the optical recording medium in which a defect list entry containing state information of the defect block and the replacement block is managed; And a newly allocated spare area for re-initialization of the medium, and a defective block in the user data area is allocated to the newly allocated spare area by the new allocation of the spare area. When included as a replacement block, the status information of the replacement block, the replacement The lock is to a controller for controlling the write / read unit to record the change in the state information indicating that the block has been re-initialized, which can not be used for replacement.

According to still another aspect of the present invention, in a recording / reproducing apparatus, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, wherein the defect list and the defect list entry containing state information of the replacement block read data from and record data to the medium; A recording / reading unit and a replacement block for allocating the spare area for reinitialization of the medium, and a replacement block that cannot be used for replacement in the spare area before the spare area is newly allocated, after the reinitialization. When included as a defective block of the state information of the defective block, Group is intended to cover the defect block has been re-initialized unit control section for controlling the write / read to write, or change to a status information indicating that the block with a possible defect.

According to still another aspect of the present invention, in a recording / reproducing apparatus, a lead-in area, a data area, and a lead-out area are provided, and the data area is generated in the user data area and the user data area for recording user data. A spare area for a replacement block for replacing a defective block, the data being read from an optical recording medium in which a defect list entry containing state information of the defect block and the replacement block is managed, and writing data to the medium; The recording / reading unit to allocate the spare area for re-initialization of the medium, and to change and record the state information of the defective block in the user data area and the replacement block in the spare area. It includes a control unit for controlling the wealth.

The present invention will now be described in detail with reference to the accompanying drawings.

1 is a schematic block diagram of a configuration of a recording / reproducing apparatus according to the present invention.

Referring to FIG. 1, the recording / reproducing apparatus includes a recording / reading unit 2 and a control unit 1.

The recording / reading section 2 is provided with a pickup or the like to record data on the disk 4, which is an optical recording information storage medium according to the present invention, and reads the recorded data.

The control unit 1 controls to record and read data on the disc 4 according to a predetermined file system. In particular, according to the present invention, the control unit 1 newly allocates a spare area for re-initialization of the disk, and according to the new allocation result of the spare area, state information of defective blocks in the user data area and replacement blocks in the spare area. Manage it.

The control unit 1 includes a system controller 10, an I / F 20, a DSP 30, an RF AMP 40, and a servo 50.

In writing, the host I / F 20 receives a predetermined write command from the host 3 and sends it to the system controller 10. The system controller 10 controls the DSP 30 and the servo 50 to carry out the write command received from the host I / F 20. The DSP 30 adds additional data such as parity for error correction to the data to be recorded received from the host I / F 20 and performs ECC encoding to generate an ECC block, which is an error correction block, and then, in a predetermined manner. Modulate. The RF AMP 40 converts the data output from the DSP 30 into an RF signal. The recording / reading section 2 provided with the pickup records the RF signal transmitted from the RF AMP 40 on the disc 4. The servo 50 receives a command necessary for servo control from the system controller 10 to servo control the pickup of the recording / reading unit 2.

In particular, according to the present invention, the system controller 10 manages a defect state of blocks when newly allocating a spare area for reinitialization of a disk.

If the system controller 10 determines that the physical address of the defective block in the user data area before disk reinitialization is still included in the user data area even after the allocation of a new spare area due to disk reinitialization, the defect of this defective block The list entry is controlled to be replaced by a defect list entry having status information indicating that the defect block has been reinitialized and may be a defect.

In addition, the system controller 10 determines that the physical address of the defective block in the user data area before the disk reinitialization is included in the physical address of the replacement block of the new spare area after the allocation of the new spare area due to the disk reinitialization. In this case, it is controlled to change the defect list entry of this replacement block into a defect list entry having status information indicating that the replacement block has been reinitialized and cannot be used for replacement.

In addition, the system controller 10 determines that the physical address of the replacement block that cannot be used for the replacement in the spare area before the disk reinitialization is included in the physical address of the user data area after the allocation of the new spare area due to the reinitialization. If so, the defect list entry of this defect block is controlled to be changed to a defect list entry having status information indicating that the defect block has been reinitialized and that the block is not yet verified, which may be a defect. The defect list entry and status information will be described later in detail.

At the time of reproduction, the host I / F 20 receives a reproduction command from the host 3. The system controller 10 performs initialization necessary for regeneration. The recording / reading section 2 outputs an optical signal obtained by irradiating a laser beam on the disk 4 and receiving a laser beam reflected from the disk 4. The RF AMP 40 converts an optical signal output from the recording / reading section 2 into an RF signal and provides modulated data obtained from the RF signal to the DSP 30, while providing a servo signal for control obtained from the RF signal. Provided to the servo 50. The DSP 30 demodulates the modulated data and outputs data obtained through ECC error correction. Meanwhile, the servo 50 receives the servo signal received from the RF AMP 40 and the command required for the servo control received from the system controller 10 to perform servo control for the pickup. The host I / F 20 sends data received from the DSP 30 to the host.

The structure of the optical record information storage medium according to the present invention will now be described.

2 shows an example of the structure of a single recording layer disc according to the present invention.

Referring to FIG. 2, the disc has a lead-in area at its inner circumference, a lead-out area at its outer circumference, and a data area at its center.

The lead-in area includes the DMA # 2, the recording condition test area, and the DMA # 1, and the data area includes the spare area # 1, the user data area, and the spare area # 2, and the lead-out area includes the DMA # 3 and the DMA #. Includes 4

A defect management area (DMA) is an area for recording the defect management information in a rewritable information storage medium, which is provided in the inner or outer area of the disc.

The spare areas for recording a replacement block for replacing a defective block in which a defect occurs when a defect occurs in a predetermined portion of the user data area of the disc are sized and allocated according to a drive manufacturer or a user's choice at initialization. This spare area is newly allocated when the presence or absence is determined and the disk needs to be reinitialized while the disk is in use.

The defect management information recorded in the defect management area includes a defect list (DFL) for defect information and a disc definition structure (DDS) including information about the structure of the data area of the disc. It is.

The defect list is composed of a defect list header and a defect list entry, and the format thereof will be described later in detail with reference to FIG. 4.

The recording condition test area is an area provided for a test for testing with various recording powers according to a write strategy to find an optimal recording power and variables according to the recording method.

3 shows an example of the structure of a dual recording layer disc according to the present invention.

3, lead-in area # 0, data area, and lead-out area # 0 are provided in one recording layer L0, and lead-in area # 1, data area, and lead-out area # 1 are provided in another recording layer L1. Prepared.

The lead-in area # 0 of the L0 layer includes the DMA # 2, the write condition test area, and the DMA # 1. The data area includes the spare area # 1, the user data area, and the spare area # 2, and the lead-out area is the DMA. # 3, DMA # 4.

The lead-in area # 1 of the L1 layer includes the DMA # 2, the recording condition test area, and the DMA # 1, and the data area includes the spare area # 4, the user data area, and the spare area # 3, and the lead-out area # 1 Includes DMA # 3 and DMA # 4.

4 shows the data format of a defect list according to the present invention.

Referring to FIG. 4, a defect list 400 according to the present invention includes a defect list header (DFL header) 410 and a list of defect list entries (DFL entry list) 420.

The DFL header 410 records the number information for defect management of blocks. The DFL header 410 includes a defect list identifier 411, a number of defect blocks 412 having replacement blocks, and a number of defect blocks 413 without replacement blocks. ), The number of spare blocks available 414, the number of spare blocks unavailable 415, and the number of defective blocks 416.

The number 412 of defective blocks with replacement blocks means the number of defect list entries with defect status information indicating that the defective block has been replaced with a replacement block in the spare area.

The number 413 of defective blocks without replacement blocks refers to the number of defect list entries that are defective blocks but have defect status information indicating the defect block itself without a replacement block in the spare area.

The number of spare blocks available 414 means the number of defect list entries that have defect status information indicating which blocks are available for replacement among the non-replaced blocks in the spare area.

The number of spare blocks not available 415 refers to the number of defect list entries that have defect status information that indicates which of the non-replaced blocks in the spare area cannot be used for replacement.

The number of blocks 416 that may be defective refers to the number of defect list entries that have defect status information that represents a block suspected of defective but not yet verified among the blocks in the user data area.

DFL entry list 420 is a set of defect list entries having defect status information for blocks, including DFL entry # 1 421, DFL entry # 2 422, ... DFL entry #N 423. ).

FIG. 5 shows the data format of the DFL entry shown in FIG. 4.

Referring to FIG. 5, the DFL entry #i 500 includes a state information 1 510, a physical address 520 of a defective block, a state information 2 530, and a physical address 540 of a replacement block. do.

The state information 1 510 refers to information about a defect state of the defective blocks in the user data area and information about the availability state of the replacement blocks in the spare area. The state information 1 will be described in detail with reference to FIG. 6.

The state information 2 530 refers to information about a state indicating whether the replacement blocks in the spare area are available. As described above, a fast reinitialization can be achieved by displaying only the information indicating that the reinitialization is performed in the state information 2 of the defect list entry without performing the post-record verification operation during reinitialization. Also, when writing data after reinitialization, if the status information 2 of the defect list entry for the block to be written is set to status information indicating that it is reinitialized, the drive system knows this and instructs the host to write data to a part of the block. Even if the read-Modify-Write without a separate read-Modify-Write can be recorded by padding the predetermined data to the rest of the block. In addition, when the play command is issued from the host, the drive system recognizes that the data written in the block is meaningless data if the state information 2 is displayed as status information indicating that the state 2 is reinitialized. You can send it to or send a check message.

The physical address 520 of the defective block refers to the physical address where the defective block in the user data area is located, and the physical address 540 of the replacement block refers to the physical address where the replacement block in the spare area is located.

FIG. 6 is a reference diagram for describing state information 1 of the DFL entry illustrated in FIG. 5.

Referring to FIG. 6, the state information 510 has five states of “1”, “2”, “3”, “4”, and “5”.

Status information "1" represents the status of a defective block with a replacement block. In this case, the physical address of the defective block indicates the physical address of the defective block in the user data area, and the physical address of the replacement block refers to the physical address where the replacement block replacing the defective block is recorded in the spare area.

Status information "2" represents the status of a defective block without a replacement block. In this case, the physical address of the defective block represents the physical address of the defective block in the user data area.

Status information "3" indicates a state of a defective block that may be a defect. Blocks that are likely to be defective are not yet verified by post-recording error correction when excessive RF or servo signals are detected in the process of scanning or scanning disks, but may not be verified by future post-recording error correction that may be defective. Indicates the required block. In this case, the physical address of the defective block represents the physical address of the defective block, which has not been verified but is likely to be defective.

The state information "4" represents a state indicating that the replacement block is usable as a state of the replacement block in the spare area. In this case, the physical address of the replacement block represents the physical address of the usable block among the non-replaced blocks of the spare area.

The state information "5" represents a state indicating that the replacement block cannot be used as a state of the replacement block in the spare area. In this case, the physical address of the replacement block represents the physical address of the block that cannot be used among the non-replaced blocks of the spare area.

Status information "1 ", " 2 ", " 3 " represents states of blocks in the user data area, and status information " 4 ", " 5 " represents states of blocks in the spare area.

Although state information 2 530 is not shown in the figure, for example, if state information 2 530 is set to "1", it indicates that it is reinitialized, and state information 2 530 is set to "0". If set, this may indicate that the block has not been reinitialized or has been reused since reinitialization. State information 2 set to "0" indicates that this block contains valid data, and state information 2 set to "1" indicates that this block has been reinitialized and no valid data exists in this block. .

7 is a reference diagram for explaining a method of processing a defect list entry of a block in a newly allocated spare area due to disk reinitialization according to the present invention.

FIG. 7A shows a state of a data block in a single recording layer disk in which spare area # 1 is allocated and used before disk reinitialization, and (b) shows in a disk to which spare area # 1 is newly allocated after disk reinitialization. Indicates the state of the data block.

Referring to FIG. 7A, only the spare area # 1 is allocated, and the data area includes the spare area # 1 and the user data area. Blocks ①, ② and ③ are recorded at the end of the user data area. Block ① is a defect block, which indicates a block having a replacement block for replacing this defect block. Block ② indicates a defective block that does not have a replacement block for replacing this defective block. Block ③ indicates a block that may be defective.

In such a state, if a new spare area # 1 is allocated by reinitializing the disk while the disk is in use, the defective blocks still present in the user data area after reinitialization are also included in the user data area after reinitialization (b Is the state as shown in

Referring to FIG. 7B, the DFL entries for the defective block ① having the replacement block, the defective block ② having the replacement block, and the block ③ likely to be defective, together with the status information indicating that these blocks have been reinitialized Switch to a DFL entry with state information that may be.

(A) of FIG. 8 shows state information of a defect list immediately before a new spare area allocation in accordance with the present invention in the situation shown in FIG. 7 (a), and (b) is new in the situation shown in FIG. Status information of the defect list immediately after allocation of the spare area is shown.

Referring to FIG. 8A, the DFL entry for block ① is the first entry shown in FIG. 8A. Since the block ① is a defective block having a replacement block, the state information 1 is set to "1", and the physical address of this defective block is recorded as "0010000h", and the state information 2 is not yet reinitialized. Is set to ". Since block ② is a defective block that does not have a replacement block, the state information 1 is set to "2", and the physical address of this defective block is recorded as "0010100h", and the state information 2 is not yet reinitialized. 0 "is set. Since block ③ is a block that may be defective, the state information 1 is set to "3", and the physical address of this defective block is recorded as "0010110h", and the state information 2 is not yet reinitialized. Is set to ".

The DFL entry list shown in FIG. 8A becomes a DFL entry list state as shown in FIG. 8B by reinitialization of newly allocating a spare area.

Referring to FIG. 8B, the DFL entry for block ① is the first entry shown in FIG. 8B, the DFL entry for block ② is the second entry, and the DFL entry for block ③ is Is the third entry. The DFL entries for blocks ①, ②, and ③ are all set to "3" indicating that state information 1 is a block that may be defective by reinitialization, and "1" indicating that state information 2 indicating whether to reinitialize was reinitialized. Is set to ".

Since the defective block in the user data area after the disk reinitialization is a block that may be defective, it is desirable to verify the defectiveness of the block by performing a verification process after recording. .

Set to "1" to indicate that the DFL entry has been reinitialized by reinitialization 2, and if this block is used again, state information 2 should be changed to "0". The reason for indicating the state information 2 by reinitialization as "1" is to indicate that the data recorded in this block is no longer meaningful data due to reinitialization.

9 is a reference diagram for explaining a method of processing a defect list entry of a block in a newly allocated spare area due to disk reinitialization according to the present invention.

(A) of FIG. 9 shows a state of data blocks in a single recording layer disk in which spare area # 1 is allocated and used before disk reinitialization, and (b) shows in a disk to which spare area # 2 is newly allocated after disk reinitialization. Indicates the state of the data block.

Referring to FIG. 9A, only the spare area # 1 is allocated to the data area, and the data area includes the spare area # 1 and the user data area. Blocks ④, ⑤, and ⑥ are recorded at the end of the user data area, and block ⑦ is recorded in the spare area # 1. Block ④ is a defect block, which indicates a block having a replacement block for replacing this defect block. Block ⑤ indicates a defective block that does not have a replacement block for replacing this defective block. Block ⑥ indicates a block that may be defective. Block ⑦ is a replacement block in the spare area, indicating that the replacement block cannot be used for replacement.

In this state, spare area # 1 is further reduced and allocated by disk re-initialization while the disk is in use, and block ⑦ in spare area # 1 before re-initialization is included in the user data area after re-initialization. 2 is newly allocated and blocks ④, ⑤, and ⑥ that were in the user data area before reinitialization are all included in spare area # 2 as shown in (b).

Referring to FIG. 9B, when the defective blocks ④, ⑤, and ⑥ that existed in the user data area before reinitialization are included in the spare area by reinitialization, all of the DFL entries for these blocks are rewritten. Switch to a DFL entry with status information indicating that it is a block that cannot be used for replacement with status information that has been initialized. If the replacement block ⑦ in the spare area before the reinitialization is included in the user data area by reinitialization, the DFL entry for the block is status information indicating that the block is likely to be defective along with the status information that it has been reinitialized. Switch to the DFL entry with.

(A) of FIG. 10 shows status information of a defect list immediately before a new spare area allocation in accordance with the present invention in the situation shown in FIG. 9 (a), and (b) is new in the situation shown in FIG. 9 (b). Status information of the defect list immediately after allocation of the spare area is shown.

Referring to Fig. 10A, the DFL entry for block ④ is the first entry shown in Fig. 9A. Since the block ④ is a defective block having a replacement block, state information 1 is set to "1", and the physical address of this defective block is recorded as "0010000h", and the state information 2 is "0" because it is not yet reinitialized. Is set to ". Since the block ⑤ is a defective block having no replacement block, the state information 1 is set to "2", and the physical address of this defective block is recorded as "0010100h", and the state information 2 is not yet reinitialized. 0 "is set. Since block ⑥ is a block that may be defective, status information 1 is set to "3", and the physical address of this defective block is recorded as "0010110h", and status information 2 is not yet reinitialized. Is set to ". Since block ⑦ is a replacement block for which replacement is not available, the state information 1 is set to "5", and the physical address of this replacement block is recorded as "0100000h", and the state information 2 is not yet reinitialized. It is set to "0".

The DFL entry list shown in FIG. 10 (a) is brought into the DFL entry list state as shown in FIG. 10 (b) by reinitialization of newly allocating a spare area.

Referring to FIG. 10B, the DFL entry for block ④ is the second entry shown in FIG. 10B, the DFL entry for block ⑤ is the third entry in FIG. 10B, and The DFL entry for block ⑥ is the fourth entry of (b), and the DFL entry for block ⑦ is the first entry of (b). The DFL entries for blocks ④, ⑤, and ⑥ are all set by reinitialization to " 5 ", which indicates that the state information 1 is a block that cannot be used for replacement, and state information 2 indicating whether to reinitialize is reinitialized. Is set to " 1 ", indicating that the defective block's physical address is changed to the replacement block's physical address position. The DFL entry for the block is set to "3" to indicate that state information 1 is likely to be defective by reinitialization, and to "1" to indicate that state information 2 to indicate whether to reinitialize has been reinitialized, The physical address of the replacement block is changed to the physical address location of the defective block.

Although the above has been described with respect to a single recording layer disk, the same method applies to a dual recording layer disk.

Now, with reference to FIGS. 11-15, the process of the continuous defect block in which a defect block appears continuously is demonstrated.

11 shows three states of a DFL entry in the case where state information 1 is " 3 " representing a state that may be a defect in accordance with the present invention.

11A shows a single block DFL entry that may be a defect.

Referring to Fig. 11A, "3" is set to indicate that the state information 1 of the DFL entry is a defective block, and the physical address of the defective block represents the physical address of the defective block. In state information 2, " 0 " is set which indicates the state before reinitialization, and the physical address of the replacement block is recorded as " 1 " indicating that this block is a single block.

Fig. 11B shows a continuous block DFL entry which knows the length of the defect.

Referring to Fig. 11B, " 3 " is set to indicate that the state information 1 of the DFL entry is a defective block, and the physical address of the defective block indicates the start physical address of this continuous defective block. The information 2 is set to "0" indicating the state before reinitialization, and "5" indicating the length of this continuous defective block is recorded in the physical address of the replacement block.

FIG. 11C shows a continuous block DFL entry whose length may be a defect.

Referring to Fig. 11C, "3" is set to indicate that the state information 1 of the DFL entry is a defective block, and the physical address of the defective block represents the physical address of the defective block. State information 2 is set to "0" indicating the state before reinitialization is yet, and the physical address of the replacement block does not know the length of this consecutive defective block, so a predetermined promise value "FFh" is written to indicate this. It is.

12 is a reference diagram for explaining a state in which a continuous defect block of known length is partially present in the spare area and part of the user data area according to the present invention.

Referring to Fig. 12A, blocks # 1 to # 5, which may be defects, are continuously arranged in the user data area. These defectability blocks # 1 to # 5 form a continuous defect block. The start address of this consecutive defective block is indicated by "0001000h".

In such a state, a spare area is newly allocated by re-initialization, so that a part of the consecutive defect blocks is included in the newly allocated spare area, and a part is included in the user data area, as shown in FIG. 12B. have.

Referring to FIG. 12B, two blocks, consecutive blocks # 1 and # 2, of consecutive consecutive blocks are included in the spare area by allocating a new spare area, and three blocks, blocks # 3 to # 5. Is included in the user data area. As will be described later, the continuous defect block belonging to the user data area is still a continuous defect block that is likely to be a defect, and the block belonging to the spare area becomes a substitute block which cannot be used.

FIG. 13 is a reference diagram for explaining a change of a DFL entry in the situation shown in FIG. 12.

FIG. 13A shows the state shown in FIG. 12A, that is, the state of the DFL entry of the consecutive defective blocks in the user data area immediately before reinitialization.

Referring to Fig. 13A, "3" is set to indicate that the state information 1 of the DFL entry is a defective block, and the physical address of the defective block is "0001000h" which is the starting physical address of this continuous defective block. Is recorded, and status information 2 is set to " 0 " representing the state before reinitialization, and " 5 " representing the length of this continuous defective block is recorded in the physical address of the replacement block. ,

FIG. 13B shows the state shown in FIG. 12B, that is, the state of the DFL entry after reinitialization.

Referring to FIG. 13B, the defect possibility blocks # 3 to # 5 belonging to the user data area even after the allocation of the new spare area are shown as the first DFL entry in FIG. 13B. That is, "3" is set to indicate that the state information 1 of the first DFL entry is a block that may be defective, and the physical address of the defective block is recorded with "0001010h", which is the starting physical address of this consecutive defective block. Information 1 is set to " 1 " indicating that it has been reinitialized, and " 3 " representing the length of this consecutive defective block is recorded in the physical address of the replacement block.

After allocation of the new spare area, blocks # 1 and # 2 belonging to the spare area are represented by second and third DFL entries in FIG. That is, "5" is set to indicate that the state information 1 of the second DFL entry is an unusable block, "1" is set to indicate that the state information 2 is reinitialized, and "0001000h" is set to the physical address of the replacement block. Is recorded. Status information 1 of the third DFL entry is set to "5" indicating that the block is not available, status information 2 is set to "1" indicating that it is reinitialized, and "0001001h" is written to the physical address of the replacement block. It is. Consecutive defect blocks in the user data area can be represented by one DFL entry, but replacement blocks in the spare area generate a DFL entry for each replacement block even if it is consecutive.

14 is a reference diagram for explaining a state in which a start address of a continuous defect block exists in a user data area or exists in a spare area by assigning a new spare area to a continuous defect block of unknown length according to the present invention.

There are two ways to deal with consecutive defect blocks of unknown length by reinitialization.

One is to test certain blocks by the "post-write test" from the start block of the continuous defective block, and then check each of the tested blocks after the new allocation of the spare area, whether the block exists, that is, the user data area or the spare area. To create a DFL entry. That is, first, the test is performed by "Test after recording". If it is determined that the test result is defective among the consecutive blocks in the user data area even after a new spare area is allocated, the DFL entry is registered accordingly. If it is determined that there is no, there is no need to register a DFL entry for this block. And, if it is determined that the defect is defective among the consecutive blocks in the newly allocated spare area, a DFL entry having status information indicating that the replacement block is unavailable is registered. Register a DFL entry with status information indicating that it is a block.

The other is to generate a DFL entry after the allocation of a new spare area depending on where the start address of the contiguous defect block belongs. That is, after the allocation of a new spare area, when the start address of the consecutive defective block belongs to the spare area, certain blocks are written from the start block, tested by test, and then a DFL entry is generated according to the test result. After the allocation of the new spare area, when the start address of the contiguous defect block belongs to the user data area, the original DFL entry is maintained as it is. At this time, the status information indicating the reinitialization is not displayed in the status information 2. The status information of reinitialization is to eliminate unnecessary Read-Modify-Write process when data is written to such blocks by the host in the future. The probable contiguous block, whose length is unknown, cannot know its length. This is because it is unclear how far the reinitialized information has been reinitialized from the physical address of the defective block. This second method will be described with reference to FIGS. 14 and 15.

Referring to Fig. 14A, a continuous defect block, which is a continuous defect block but whose length is not known, is arranged in the user data area. Although the length of this continuous defective block is unknown, it is indicated that the starting address is "0000100h".

Referring to FIG. 14B, it shows a state after a new spare area is allocated in the situation as shown in FIG. 14A. After a new allocation of the spare area, the spare area becomes smaller so that the start address of the contiguous defect block whose length was in the user data area before the new allocation is still included in the user data area. In this state, since the start address of the continuous defect block whose length is unknown is still in the user data area, it is assumed that the continuous defect block is in the user data area and the DFL entry is processed accordingly.

Referring to FIG. 14C, it shows a state after a new spare area is allocated in the situation as shown in FIG. 14A. After the new allocation of the spare area, the spare area has grown so that the spare area includes the start address of a contiguous defect block whose length was in the user data area before the new allocation. In this state, since the start address of the continuous defective block whose length is unknown is in the spare area, it is assumed that the continuous defective block is in the spare area, and a predetermined block from the starting address is tested by the "test after write" operation. To process the DFL entry accordingly.

FIG. 15 is a reference diagram for explaining a change of a DFL entry in the situation shown in FIG. 14.

FIG. 15A shows the situation shown in FIG. 14A, that is, the state of the DFL entry immediately before reinitialization.

Referring to Fig. 15A, "3" is set to indicate that the state information 1 of the DFL entry is a defective block, and the physical address of the defective block represents the physical address of the defective block. State information 2 is set to "0" indicating the state before reinitialization is yet, and the physical address of the replacement block does not know the length of this consecutive defective block, so a predetermined promise value "FFh" is written to indicate this. It is.

FIG. 15B shows the DFL entry in the situation shown in FIG. 14B, that is, when a start address of a continuous defective block whose length is unknown after reinitialization exists in the user data area.

Referring to FIG. 15B, state D2 remains the same as the state of the DFL entry shown in FIG. 15A, and state information 2 indicating the reinitialization state also maintains "0" as described above.

FIG. 15C illustrates a DFL entry in the situation shown in FIG. 14C, that is, when a start address of a continuous defective block whose length is unknown after reinitialization exists in the spare area.

Referring to (c) of FIG. 15, when a start address of a continuous defective block whose length is unknown after reinitialization exists in the spare area, a predetermined block is written from this start address and tested after a predetermined block, and the DFL entry is determined according to the test result. Create For example, if the test results show that this consecutive defective block contains two defective blocks, the first block is a block usable by the test, and the second block is a block unusable by the test. As shown in (c), two DFL entries are created.

16A and 16B are flowcharts illustrating a process of a reinitialization method according to the present invention.

Referring to FIG. 16A, after a disk used in a drive system is loaded, the system controller of the drive system receives a disk reinitialization command (step 1601).

Upon receiving such a disk reinitialization command, the system controller first allocates a new spare area to the user data area (step 1602).

Next, the system controller changes the defect list entry according to the allocation of the spare area. First, it is determined whether the block to be changed is a single defective block or a continuous defective block (step 1603), and if it is about a single defective block, the process proceeds to step 1604. If it relates to a continuous defect block, the process proceeds to 'A'.

In step 1604, the system controller determines whether the defective block included in the user data area is included in the user data area even after assignment of the new spare area.

If it is still included in the user data area, the DFL entry of this block is replaced with a DFL entry indicating that the block has not yet been verified, which may be defective, with status information that the block has been reinitialized (step 1605). .

Next, it is determined whether the defective block included in the user data area is included in the spare area after the allocation of the new spare area (step 1606).

If it is determined that the defective block in the user data area is to be included in the spare area after the allocation of the new spare area, the block indicates that the DFL entry of the block cannot be used for replacement with status information indicating that it has been reinitialized. Change to a DFL entry (step 1607).

Next, if a replacement block that is not available for replacement of the spare area is to be included in the user data area after the allocation of the new spare area (step 1608), the system controller sends a status information indicating that the DFL entry of this block has been reinitialized. Together it is replaced with a DFL entry indicating that it is a block that has not yet been tested that may be defective (step 1609).

Next, in the case of the continuous defect block, the process proceeds to 'A' to determine whether the length of the continuous defect block that may be a defect is known (step 1610).

In case of a contiguous block whose length is a known defect, for the contiguous block in the user data area even after the allocation of the spare area, the state information 2 indicating that the contiguous block has been reinitialized is set to "1" and replaced with the contiguous block DFL entry. (Step 1611). Subsequently, the process replaces the DFL entry indicating that the contiguous block included in the newly allocated spare area is not available to the contiguous block (step 1612). If a contiguous block that is likely to be defective is part of the user data area due to the new allocation of the spare area and part of the spare area, the process proceeds to step 1611 for some blocks belonging to the user data area. Some blocks belonging to the area may be processed by step 1612.

If the length of the contiguous block that is likely to be defective is unknown, one of two methods may be used depending on the intention of the drive manufacturer (step 1613).

In the case of Method 1, a predetermined block is tested by "post-write test" from the start block belonging to the continuous block unconditionally, and is changed into a DFL entry according to the test result (step 1614). That is, for consecutive blocks belonging to the user data area after the allocation of the new spare area, the first block includes information indicating that the block is defective or may be defective according to the test result, and second state information indicating that it is reinitialized. Registers a defect list entry and includes, for successive blocks belonging to the newly allocated spare area, first state information indicating that the replacement block is available or unavailable according to the test result and second state information reinitialized. Register the defect list entry.

In the case of method 2, if the start block of the contiguous block belongs to the user data area after allocating the spare area, the remaining block is assumed to belong to the user data area and is replaced with the contiguous block DFL entry, and the start block of the contiguous block is newly allocated. If it belongs to the spare area, it is assumed that the remaining blocks will also belong to the spare area and is replaced with a DFL entry indicating that the replacement block is available or unavailable according to the result verified by the test after the recording (step 1615).

The recording / reproducing method as described above can also be embodied as computer readable codes on a computer readable recording medium. Computer-readable recording media include all kinds of recording media on which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, and may also be implemented in the form of a carrier wave (for example, transmission over the Internet). Include. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. In addition, functional programs, codes, and code segments for implementing the recording / reproducing method can be easily inferred by programmers in the art to which the present invention belongs.

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. Therefore, the disclosed embodiments should be considered in descriptive sense only and not for purposes of limitation. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope will be construed as being included in the present invention.

According to the present invention as described above, the reinitialization process can be performed quickly by reinitializing the disc by managing only defect information without a post-record verification process when reinitializing the disc. That is, reinitialization can be achieved by displaying information indicating that the reinitialization has been performed in the state information 2 of the defect list entry during reinitialization, and the state information 2 of the defect list entry for the block to be recorded if the data is to be recorded after the reinitialization. Is set to "1", the drive system knows this and even if the host tells it to write data to a portion of the block, it is still possible to write the data by padding the rest of the block immediately without a separate Read-Modify-Write. have. In addition, when the play command is issued, the data recorded in the block is meaningless data, so it is possible to immediately transmit null data to the host or send a check message. As described above, according to the present invention, it is possible to reduce the time due to reinitialization and to prevent unnecessary RMW process in the rewritable medium.

Claims (12)

In the recording / playback method, A lead-in area, a data area and a lead-out area are provided, the data area including a user data area for recording user data and a spare area for a replacement block for replacing a defective block generated in the user data area; Allocating the spare area for reinitialization of an optical recording medium in which a defect list entry containing state information of the defect block and the replacement block is managed; If the defective block in the user data area is in the user data area even after the reinitialization due to the allocation of the spare area, the status information of the defective block is reinitialized and the block is likely to be defective. And recording by changing to status information indicating. The method of claim 1, And a defective block in the user data area prior to the allocation of the spare area includes a defective block having a replacement block, a defective block having no replacement block, and a block that may be a defect. In the recording / playback method, A lead-in area, a data area and a lead-out area are provided, the data area including a user data area for recording user data and a spare area for a replacement block for replacing a defective block generated in the user data area; Allocating the spare area for reinitialization of an optical recording medium in which a defect list entry containing state information of the defect block and the replacement block is managed; When a defective block in the user data area is included as a replacement block of the newly allocated spare area after the reinitialization by the new allocation of the spare area, the replacement block is reinitialized. Changing to status information indicating that the block cannot be used for replacement. The method of claim 3, And a defective block in the user data area prior to the allocation of the spare area includes a defective block having a replacement block, a defective block having no replacement block, and a block that may be a defect. In the recording / playback method, A lead-in area, a data area, and a lead-out area are provided, and the data area includes a user data area for recording user data and a spare area for a replacement block for replacing a defective block generated in the user data area. Allocating the spare area for reinitialization of an optical recording medium in which a defect list entry containing state information of the defect block and the replacement block is managed; If a replacement block that cannot be used for replacement in the spare area before the spare area is newly allocated is included as a defective block of the user data area after the reinitialization, the defective block is reconstructed. Changing to status information indicating that the block has been initialized and is likely to be defective. In the recording / playback method, A lead-in area, a data area and a lead-out area are provided, the data area including a user data area for recording user data and a spare area for a replacement block for replacing a defective block generated in the user data area; Allocating the spare area for reinitialization of an optical recording medium in which a defect list entry containing state information of the defect block and the replacement block is managed; And changing the state information of the defective block in the user data area and the replacement block in the spare area. The method of claim 6, The defect list entry is Physical address information of a defective block, physical address information of a replacement block for replacing the defective block, first state information indicating a defective state of the defective block or whether the replacement block is available, whether the medium is reinitialized Recording / reproducing method comprising second status information indicating. The method of claim 7, wherein The changing step, If a defective block in the user data area before the spare area is newly allocated is in the user data area even after the reinitialization, a defect list entry of the defective block indicates that the defective block is a block that may be defective. And change the first state information and the defect block into a defect list entry including second state information indicating reinitialization. The method of claim 7, wherein The changing step, If a defective block in the user data area before the spare area is newly allocated is included as a replacement block of the newly allocated spare area after the reinitialization, the defect list entry of the replacement block is replaced by the replacement block. And a first list of status information indicating that the block cannot be used and a second list of status information indicating that the replacement block has been reinitialized. The method of claim 7, wherein The changing step, If a replacement block that cannot be used for replacement in the spare area before the spare area is newly allocated becomes a defective block of the user data area after the reinitialization, a defect list entry of the defective block is made. Changing to a defect list entry including first state information indicating that the block is possibly a block and second state information indicating that the defective block has been reinitialized. The method of claim 7, wherein The changing step, Before allocating a new spare area, if there is a contiguous defect list entry in which the probable blocks are arranged consecutively and do not know the length of the contiguous block, a predetermined number of blocks from the start block of the contiguous block. Based on the result of the test by " test after recording ", for a contiguous block belonging to the user data area after allocating a new spare area, includes first state information according to the test result and second state information indicating that it has been reinitialized. Registers a defect list entry, and, for a contiguous block belonging to a newly allocated spare area, first state information indicating a block that can be used for replacement or a block that cannot be used for replacement, and second state information indicating reinitialization. Registering a defect list entry containing a Recording / reproducing method as ranging. The method of claim 7, wherein The changing step, Before the allocation of a new spare area, if there is a contiguous defect list entry in which the blocks that are likely to be defective are arranged consecutively and do not know the length of the contiguous block, the start block of the contiguous block is allocated to the new spare area. If the user belongs to the user data area, the continuous defect list entry is retained. If the start block of the continuous block belongs to the newly allocated spare area, a predetermined number of blocks from the start block are " tested " Based on the results verified by the processor, registering a defect list entry including first state information indicating a block that can be used for replacement or a block that cannot be used for replacement, and second state information indicating reinitialization. Recording / playback method.

Images