Write-once information recording medium, information recording device, information recording method, information reproduction device and information reproduction method. RU patent 2504028.

FIELD: information technology.

SUBSTANCE: recording medium has a user data area and a control information area. Control information includes a space bitmap and a disc definition structure, which includes space bitmap location information. The size of the space bitmap is defined such that the combined size of the space bitmap itself and the disc definition structure is always equal to the size of one unit. If the size of the user data area in a predetermined recording layer exceeds a predetermined size, multiple space bitmaps are formed for the user data area of the predetermined recording layer.

EFFECT: arranging TDDS in a predetermined location for a disc with high density of recording on a layer.

40 cl, 30 dwg

The technical field

The present invention relates to media recording information, which includes information bitmap indicating recorded whether each zone or has not yet been recorded, and who can perform the operation random write, and also relates to a method and device for reading and/or writing from/to such recording media. The present invention is effectively applicable, in particular, to the optical disk, such as a BD-R (single disc Blu-ray high-density, in which the write operation can be performed only once, and to read and/or write from/to a disk.

Prior art

Recently various removable media data storage with huge storage capacities and drives to handle these media are becoming very popular. Examples of known removable media data storage with large storage capacities include optical discs, such as DVD and Blu-ray (which is also referred to in this document as "the BD"). Optical drive performs its read/write by creating tiny recesses (or tags) to the optical drive using a laser beam and, therefore, can be effectively used for the processing of such removable media data storage with huge storage capacities. In particular, the red laser used for DVD, while the blue laser beam with a shorter wavelength than a red laser beam is used for BD, thereby making the storage density and capacity storage for BD higher and greater than the density of storage and storage capacity of a DVD. With regard to BD-R, for example, implemented a maximum storage capacity of only 27 Gigabytes per layer recording.

For example, provides optical disc that uses the recording material with phase change for the layer recording. Optical drive with the phase change is irradiated by a laser beam, and the status of atomic bond of thin film substance, which is laid on a layer for the record, locally varies depending on the input energy, thereby recording the information on it. In addition, when irradiated by the laser beam with much lower power than the power used for recording, optical disk has a coefficient of reflection, variable due to such differences in physical state. Also, if detected value of such variation coefficient of reflection, the information stored in it, can be read.

Optical discs phase-change include rewritable optical discs, on which information can be overwritten by a certain number of times using the recording material with phase change for its layer recording, and unwritable optical discs, on which information can be recorded only once. If a write operation on the limits of the labels is done on such a write once optical disk, the disk is irradiated by the laser beam, which in sequence many impulses to vary the physical condition of the recording material, thereby leaving the record label on it. Also, the information is read from such optical disk by reading the reflection coefficient of variation between these formed marks and spaces.

However, since the optical disk drive is a removable storage medium of information likely to be certain defects on its layer recording due to the presence of dust or scratches. Among other things, the higher the density of the recording media, the more easily on the recording media influence defects. That is why more and more popular measure becomes implementation of the defect management not only on rewritable optical disks (for example, BD-RE), but also on optical disks (for example, BD-R)to ensure the reliability read or written data (see, for example, Lined publication of the patent application (Japan) no 2005-56542, patent document number 1). In addition, BD-R differs not only sequential recording mode, in which the write operation is performed with the specific starting point of the record, which is typical for media data storage, but also the regime of random write, in which the write operation is in an arbitrary point of entry (see, for example, the Publication of the Japan patent № 3861856, US7188271, Publication of an application for a patent US2007/0122124, room 2, room 3 and 4).

Fig. 1 illustrates the usual location of the different zones on an optical disc. Disc-shaped optical disk 1 has a spiral track 2, along which offers numerous divided into 3 blocks. Units 3 units are not only the correction of mistakes, but also the smallest units of operations read/write. Each unit 3 is sometimes called a "cluster" for BD and sometimes "ECC" for DVD. One cluster, which is one unit for BD, equal to 32 sectors (i.e. one sector has a size of 2 KB, and one cluster has a size of 64 KB). On the other hand, one ECC, which is one block for the DVD is 16 sectors (i.e. 32 kilobytes). In addition, the storage area on an optical disc 1 about is divided into primary zone 4 zone 5 data and end zone 6. User data presumably read from and written in zone 5 data. Initial zone 4 and the final area 6 act as allowable reserves, which give an opportunity to the optical head (not shown) back on track, even if the optical head went beyond the established boundaries for access to the final part of the zone of 5 data. In other words, these zones 4 and 6 of the act, so to speak, as the "edges". Such location of the zones is usually used as a rewriteable CD-ROM and on a write once optical disk. Fig. 2 shows the structure of the data from one layer to record traditional optical disk function defect management.

Zone 5 data zones consists of 14 user data from which the user data are read or written, and reserve zones, each of which is specified in advance to provide an alternative block (which will be referred to herein as a "proxy block") for the defective unit, if any, in the area of 14 user data. In the example illustrated in Fig. 2, internal backup zone 15 is placed closer to the inside edge of the optical drive 1, and the external reserve zone 16 is placed closer to its external border. In other words, although one reserve area is situated in zone 5 data and another reserve area is situated outside zones 5 the data in Fig. 2, reserve zone can be granted only on one of these two parties (for example, only in zone 5 data). Therefore, the arrangement shown in Fig. 2 doesn't always have to be adopted.

Each of the initial zone 4 and the end zone 6 zones for the storage of the management structure of the disk (which is abbreviated as called this document "DMS"), which provides fragments of control information about the layout (or amount) of reserve zones on the optical disc 1 record mode, defective units, etc. In particular, the initial zone 4 includes the first and second zone 10 and 11 disk management (DMA) (referred to in this document as "DMA #1" and "DMA #2", respectively). On the other hand, end zone 6 includes the third and fourth DMA 12 and 13 (referred to in this document as "DMA #3" and "DMA #4", respectively). It should be noted that DMA sometimes means the area of the defect management.

DMA #1-#4 are placed in their own areas and retain virtually identical fragments of management information, except for some pre-defined types of information, for example, location information that helps you prepare for the occasion when any of the DMA #1-#4 itself becomes defective. In other words, even if the information cannot be retrieved from one of these four DMA properly, information management defects can still be obtained until there is at least one DMA, from which information can be retrieved properly.

Initial zone 4 has an additional first TDMA (time zone disk management) 17. TDMA is a zone of the unique optical drive worm, which is (i.e. a non-updatable) disk, and is used to add a temporary control information and update it at a time when the optical drive 1 is used. It should be noted that TDMA sometimes implies time zone defect management.

Further in this document is described with reference to Fig. 14 exactly how to use TDMA 17. First of all processing format initialization (also called simply "initialization") is write-once optical disk 1 is prepared to use by defining the layout (or size) of reserve zones and record mode, thereby, recording the initial TDMS (temporal structure of the disk management) 20, as shown in part (a) of Fig. 14.

Then, as shown in part (b) of Fig. 14, processing entry runs in zone 14 user data and TDMS #0 21, the information about them (for example, information defects and endpoint information recording) is updated as a result of the processing of the record, written at the beginning of the unwritten zone TDMA 17 (i.e. to use area to the right of the border between the recorded area and unwritten area).

Layout DMA is not distinguished between optical disc and writable optical disk. However, as the rewritable optical disk drive is writable (i.e., updated), each piece of management information, including temporary control information, while the optical drive 1 is used, can be updated in these areas DMA. On the other hand, optical drive worm is (i.e. a non-updatable). That is why write-once optical disk 1 has an area called "TDMA", to update the time information that cannot be found on any disk, in addition to . Also, when the process of finalization (also called "closing the disc") is performed in order to prevent the user from further adding any additional pieces of information on disc 1 and make the drive , the contents of the last TDMS is copied to the DMA.

In the example illustrated in Fig. 2, only one TDMA 17 allegedly placed in the primary zone 4. However, two or more TDMA 17 may reside (see, for example, the patent publication Japan # 3865261, patent document number 5). Optional, several TDMA also can be provided for each layer to record and also placed in reserve areas. For example, as shown in Fig. 15, for more TDMA #1 and TDMA#2 may, accordingly, be provided for internal and external reserve zones 15 and 16 zone 5 data, in addition to TDMA #0 in the primary zone 4. In addition, if a write-once optical disk 1 has several layers to record, these zones TDMA can be provided for each of these multiple layers to write.

DMS recorded in the DMA, and TDMS 21, recorded in TDMA 17, consist of identical elements. The following description TDMS 21 describes as an example.

Fig. 16 illustrates the elements that form the TDMS 21 on BD-R, which is optical disk and the mode random write. In Fig. 16 structure of optical disc 1 with just one layer for entries is shown as an example. Therefore, the data contained within each of these pieces of information allegedly provided only for a single layer recording in the example illustrated in Fig. 16.

TDMS 21 composed of SBM (bitmap space) 30, TDFL (temporary list of defects), 31 and TDDS (temporal structure of the disk definition) 32.

SBM has 30 SBM-title 40, which includes the ID of the disclosing identification information as SBM 30, information on the number of updates and information on the range of the SBM to control (for example, the starting address and size of the considered area information 41 bitmap indicating the status of a record (for example, written and unwritten state in this range of the SBM for management. Information 41 bitmap is further described below. In the optical disc 1 with multiple layers for the record, zone 5 data, in which SBM 30 can be controlled (more specifically, area 14 user data)are not physically contiguous to each other between its multiple layers for the record, and, therefore, SBM 30 is available for each of these layers for recording.

TDFL 31 has DFL-title 42, including ID, revealing its identity as TDFL, information on the number of updates and information on the number of DFL-records 43 (for example, n+1 Fig. 16), which are defective, and replacement information TDFL; this number DFL-records 43; and a pointer 44 the end of DFL, which includes the ID, revealing its identity as the final position TDFL 31, the size of which is variable according to the number of DFL-records 43 and information on the number of updates. TDFL 31 and TDDS 32 with a size in one sector (which should be described below) can be combined size of at most four block (i.e. four cluster for BD), if there is only one layer to write, and can be combined size of at most eight blocks (i.e. in eight clusters for BD), if there are two layer recording. In other words, the size of the TDFL 31 estimated at most four block (i.e. four cluster relatively BD) minus one sector", if there is only one layer for recording, but at most eight blocks (i.e. eight clusters for BD) minus one sector", if there are two layer recording.

TDDS 32 has DDS-title 50, which includes the ID of the disclosing identification information as TDDS 32, and information on the number of updates; size 51 internal backup zone and size 52 external backup zones, which are fragments of information about the appropriate amounts of internal and external reserve zones 15 and 16, which determine the location of the zones in zone 5 data; information 53 recording mode, indicating whether the mode recording mode recording mode or random write; size 54 TDMA internal backup zone, size 55 TDMA external backup zones, which provide information about the size in case of TDMA in the internal and external reserve areas 15 and 16, as shown in Fig. 15; information 56 location SBM #0 which is information about the location of the storage device last SBM 30; and information 57 location DFL #0, information 58 location DFL #1, information 59 location DFL #2 and information 60 locations DFL #3, which are fragments of information of the location of the corresponding units in which is stored the last TDFL 31 (most of four blocks).

TDDS 32 has a fixed size, for example, the size in one sector, as described above.

Further information herein 41 bitmap is described in detail with reference to Fig. 19. Information 41 bitmap is a fragment of information to use, for example, to check the written and unwritten part of the zone data in chunks. The information 41 bitmap one unit of a given range of areas, SBM which has to be controlled (for example, area 14 user data)associated with one bit, and the condition of this block is specified as zero, if he is still unwritten unit, and its status is single, when the unit becomes recorded. In other words, provided that eight blocks A-H in this range of areas, SBM which must be controlled, associated with bits 0-7, respectively, in single-byte (i.e. ) data in a predefined byte position in the information 41 bit map, as shown in Fig. 19 if all are interested in the area is unwritten, as shown in Fig. 19(A), where each bit (i.e. from bit 0 to bit 7) information 41 bitmap is a null-value. On the other hand, after a write operation was performed for units B, C and F, of its associates bits 1, 2 and 5 of information 41 bitmap must be the unit, and single-byte (i.e. eight-bit) data in a predefined position byte of information 41 bitmap must be 26h that is a hexadecimal number, as shown in Fig. 19(B). As one block is associated with one bit, 4000h (that also is a hexadecimal number) blocks can be managed using a single sector (2 kilobytes) information 41 of the bitmap, and 78000h (that also is a hexadecimal number and is 491520 according decimal) blocks can be managed using a 30 sectors of information 41 bitmap.

With regard to BD-R, if the maximum capacity per layer for entries is 27 Gigabytes, the maximum number of units (or clusters)included in zone 14 user data, is less than 68000h (which again is a hexadecimal number). That is why shall be sufficient if the information 41 bitmap has a size of 30 sectors. As a result, provided that SBM-header 40 has a size in one sector, you can ensure that the combined size of SBM 30 with a size of 31 sector and TDDS 32 with a size in one sector is always equal to or less than one unit (i.e., 32 sectors or one cluster). On the other hand, since the size of the TDFL 31 is variable according to the number of DFL-records 43, impossible to ensure that the combined size TDFL 31 and TDDS 32 is always equal to or less than one block.

Each of SBM 30 and TDFL 31 is always written in TDMA 17 using combination with TDDS 32 as one unit entries (called "unit update the structure of the disk management").

Further describes the initial TDMS 20 (see Fig. 14).

Initial TDMS 20 located in the beginning TDMA 17 (i.e. in a position which should be used (written) first on an optical disc 1).

Initial TDMS 20 has items that are identical, but with a bit of great content from conventional TDMS 21. As shown in Fig. 17, the initial TDMS 20 includes one unit (i.e. one cluster) data as a combination of elementary SBM 30 and TDDS 32, which together form one unit updates the management structure of the disk, and another block (i.e. another cluster) data as a combination of primary TDFL 31 and TDDS 32, which form the other unit structure update disk management.

When used in this document "initial SBM 30" is mentioned as SBM, for which specifies only information about the identity of his SBM-header 40 and range of the SBM, which must be controlled, and information on the number of updates and information 41 bitmap is zero (i.e., area 14 user data is completely unwritten).

In addition, the starting TDFL 31 referred to as TDFL minimum size, in General, not including the DFL-records 43, i.e. TDFL includes only the DFL-title 42 (which provides only identifier information, but for which the number of DFL-records 43 and information on the number of updates are zero), and a pointer 44 the end of the DFL (which was set to ID information, but that information number of updates is zero). Since the starting TDFL 31 has a size, which is equal to or less than the size of one sector, combined size must be equal to or less than the size of one block (or cluster) even when recording in combination with TDDS 32. In addition, TDDS 32, which must be recorded in this case can have data, almost identical to the data recorded as the initial SBM 30 and TDDS 32, described above. May differ only information 57 location DFL #0. In other words, if the data cannot be written in this unit due to the presence of a defect, for example, recorded in the following block instead, for example, only this value might differ from the value TDDS 32, which is written with an initial SBM 30.

As described above, at the beginning of TDMA 17 preserves the initial part of the data TDMS 20. In addition, in this initial location is always written TDDS 32, which provides information, which clearly specifies the layout of zones and recording mode zone 5 data on an optical disc 1. Thus, even if you cannot accurately determine immediately, where is this TDDS 32, provides information that indicates the layout of zones and recording mode zone 5 data on an optical disc 1 (for example, if there were a certain number TDMA or if TDMA already updated a certain number of times), the layout of zones and recording mode zone 5 data can still be determined specifically by reading data from a single block at the beginning of TDMA 17 (or the first of the following blocks, for which the operation of reading/writing can be carried out properly, if it is defective unit).

In particular, if in (read-only) device for optical disc 1 loaded optical disc 1 without reserve zones, until, at least, the location, i.e. zone layouts) optical disc 1 is known, this device can also perform the processing of read into the read query, issued by the host, even without the latest management information. The reason why the latter control information is not always required, and TDDS 32 identifying the location of the optical disc 1, preferably obtained as quickly and as safely as possible. Therefore, from this point of view, is also the preferred is that captures the data that always have TDDS 32 in a predefined location (for example, one block at the beginning of TDMA 17).

In addition, if there are several TDMA, if the information size TDMA, located in the reserve area is inaccessible, even the location of this TDMA cannot be determined. For this reason, it is very important and effective for optical drive to perform a read/write on this optical disc 1 so that the data TDDS 32 are always placed in a predefined location (for example, at the beginning of TDMA 17 in this example).

In the above example shows that the mode random write. In the mode of recording, on the other hand, only SRRI (information SRR), which provides information about the start location tracks (also called SRR (range recording)) and information about the final location of the recorded section is written instead of SBM 30. In this case, the initial TDMS consists of an initial TDFL 31, initial SRRI and TDDS 32, has a size, which is equal to or less than one unit (or a cluster), and, consequently, are recorded as data in one block (one cluster).

It should be noted that DMS, which shall be recorded in the DMA, and TDMS, which should be recorded in TDMA, has mutually various orders recorded and posted data. In particular, in TDMS, TDDS placed at the end of TDMS. The DMS, on the other hand, DDS is placed in the start location DMS (see patent document number 1).

Besides, lately, people stronger and stronger try to additionally increase the storage capacity of optical discs. Examples of these methods for the implementation of the optical drive with huge capacity (i.e. ways to increase their storage tanks) include the increase storage density per layer to save by reducing the length of labels and periods of records that must be retained or reduction step tracks and increase in overall storage capacity through the provision of several layers to record information.

Of these methods, according to the method to increase storage density per layer to save by reducing the lengths of the marks and of the gaps that need to be retained, it is expected that must be implemented in a storage density is 32 Gigabytes, or 33.4 Gigabytes per layer for the record, that approximately 25% exceeds the maximum size, in 27 GB of traditional BD. In addition, can also be implemented in the future even higher storage density.

Short description of the invention

However, if the storage capacity per layer to record increased, the size of the zone 5 data and zone 14 user data that must be managed by SBM, also, of course, should increase. As described above, 4000h (which is a hexadecimal number that corresponds to 16384 according to the decimal numeral system) units can be controlled from one sector of information 41 bitmap. If the maximum size information 41 bitmap is 30 sectors, the number of managed units is 78000h (which is a hexadecimal number that corresponds to the 491520 according decimal). Provided that the storage capacity per layer to record increased to 33.4 Gigabytes, for example approximately 7D000h (which is a hexadecimal number, which corresponds to approximately 512000 according decimal) blocks are required per layer recording. To manage these units, however, requires 32 sectors, that is more than 30 sectors as the maximum size of the information 41 bitmap. In this case, however, the combined size of SBM 30 and TDDS 32 exceed one block (32 sectors). Therefore, the size of one unit updates the management structure of the disk, which is a combination of SBM 30 and TDDS 32, also should exceed one block (i.e. two units or more).

In this case, if the initial TDMS 20 recorded according to the traditional procedure, so as to have content that is identical to the content of traditional TDMS, the initial TDMS 20 must have a location shown in Fig. 18. In this case, the data TDDS 32 may not always be placed in a predefined location (i.e. in the beginning of TDMA 17). In the example illustrated in Fig. 18, TDDS 32 is located in the second block from the beginning. However, if the block TDMA 17, in which shall be recorded the initial TDMS 20, is defective unit, for example, the write operation must be repeated a certain number of times for the next block until the write operation is performed properly. That is why the search should be carried out with simultaneous checking of each block to find a block with proper TDDS 32.

In addition, in this case the information 41 bitmap included in SBM 30, which shall be recorded in the initial block of the initial TDMS 20 shall have any value, which is the important bit. For this reason, information about the identity of disclosing identification information as TDDS 32, which should be included in the DDS-title 50, and information 41 bitmap, as a rule, reconciled with each other. Therefore, it is very difficult to search TDDS 32 to properly recorded block 3.

Brief summary of the invention

The objective of this invention is to provide the media information, the location of zones of which is determined so that the data include TDDS 32, always can be placed in a predefined location (for example, in the initial block TDMA 17)even if the control information, such as SBM 30, increases as the storage capacity per layer to record increases, as well as provide a way to perform operations read/write on the DVD recording of information.

Write-once media records information according to the present invention has at least one layer for the record, and the data is written in chunks. Write-once media information record includes the area of user data, that data must be written to custom; and a zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds a predefined size, more bitmaps space formed for the zone of user data predefined layer recording. Unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about a range of areas which must be managed by reference to its associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as increases the size of the zone of user data. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects, which does not provide information on the defective zone.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

Recording device information according to the present invention, records information on write-once media record information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data that must be written to custom data; and a zone of control information, in order to maintain control information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds a predefined size, the recording of information generates more bitmaps space for the zone of user data predefined layer for recording and records unit updates the management structure of the disk, which includes one of several bitmaps space and structure definitions disk and having the size in one unit, in the area of management information.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space contains one of these pieces of information bitmap.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as increases the size of the zone of user data. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects, which does not provide information on the defective zone.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

A method of recording information according to the present invention is made with the possibility of recording information on write-once media record information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. A method of recording information includes the stages at which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, form more bitmaps space for the zone of user data predefined layer to write and record unit updates the management structure of the disk, which includes one of several bitmaps space and structure definitions disk and having the size in one unit, in the area of management information.

In one preferred embodiment, the method further includes the stages at which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, share information bitmap into several fragments of information bitmap and associate one of these pieces of information bitmap with each of several bitmaps space.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about a range of areas which must be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increase as the size increases zone of user data. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information write unit or update the structure of management disk or a second unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects, which does not provide information on the defective zone.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

The device of reading of the information according to the present invention, reads recording media information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds pre-defined, more bitmaps space formed for the zone of user data predefined layer recording. Unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information. Also, the reader reads the unit updates the management structure of the disk, which includes the structure definitions disk and having the size of one block from the zone of control information and receives a bitmap space.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space contains one of these pieces of information bitmap. Also, the reader reads the associated piece of information bitmap of each bitmap space.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases, and a predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects. The initial list of defects does not provide information on the defective zone. Reader reads the unit or update the structure of management disk or a second unit updates the management structure of the disc from the unit in a predefined location.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

The method of reading information according to the present invention is made with the possibility to read information from recording media information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds a predefined size, more bitmaps space formed for the zone of user data predefined layer recording. Unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information. The method of reading information includes the stages at which reads unit updates the management structure of the disk, which includes the structure definitions disk and having the size of one block from the zone of control information and receive a bitmap space.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space is provided with one of these pieces of information bitmap. The method of reading information additionally includes a stage at which reads associate piece of information bitmap of each bitmap space.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects. The initial list of defects does not provide information on the defective zone. The method of reading information includes the stage at which reads either the unit of update management structure disk or a second unit updates the management structure of the disc from the unit in a predefined location in the zone of the control information.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

Fig. 7 depicts a block diagram of the sequence of operations ways, showing the execution of processing format initialization (i.e. initialization) according to the first preferred option for the implementation of the present invention.

Fig. 8(a)-(b) shows the structure of the data of the initial TDMS 20 according to the second preferred option for a specific implementation of the present invention.

Fig. 9 depicts a block diagram of the sequence of operations ways, showing the execution of processing format initialization (i.e. initialization) according to the second preferred option for the implementation of the present invention.

Fig. 10 shows the structure of the data of the initial TDMS according to the third specific preferred option for the implementation of the present invention.

Fig. 11(a)-(b) is schematically represents the way is written TDMS, and what information location is provided by TDDS in the third preferred embodiment of the present invention.

Fig. 12 depicts the structure of initial data SBM 30 according to the third preferred option for the implementation of the present invention.

Fig. 13 depicts a block diagram of the sequence of operations ways, showing the execution of processing format initialization (i.e. initialization) the third preferred option for the implementation of the present invention.

Fig. 14 depicts how the update TDMA.

Fig. 15 depicts how a certain number of TDMA can be placed on a layer recording.

Fig. 16 depicts what kinds of information are in the TDDS.

Fig. 17 depicts the structure of initial data TDMS 20.

Fig. 18 shows the structure of the data of different initial TDMS 20.

Fig. 19(A) and 19(B) represent information bitmap.

Fig. 20 depicts a cross-section of the optical drive as a preferred option for the implementation of the present invention.

Fig. 21 depicts the structure of multi-layer disc.

Fig. 22 shows the structure of a single-layer disc as the preferred option of the implementation of the present invention.

Fig. 23 shows the structure of a double-layer drive as the preferred option of the implementation of the present invention.

Fig. 24 shows a three-layered structure of the disk as the preferred option of the implementation of the present invention.

Fig. 25 depicts the structure of four-layer disk as the preferred option of the implementation of the present invention.

Fig. 26 depicts the physical structure of the optical drive as the preferred option of the implementation of the present invention.

Fig. 27(A) represents the approximate BD 25 GB, and Fig. 27(B) depicts an optical disk with a higher storage density than 25 GB BD.

Fig. 28 depicts how the sequence of labels recordings on the track with the help of the light ray.

Fig. 29 depicts a diagram showing how OTF varies with the shortest record label the disk with the storage capacity of 25 GB.

Fig. 30 shows an example in which the spatial frequency of the short tags (2T) exceeds the frequency OTF-cut and in which the signal reading 2T has an amplitude equal to zero.

Description of the preferred options for the implementation of

The following are the preferred embodiments of the present invention with reference to the accompanying drawings. The following description of the preferred options for the implementation of the present invention recording media information is supposed to be a recording medium of information which information can be added only once. It should be noted that the storage capacity of the recording media per layer recording (i.e. the size of the zone 14 user data) is given so that SBM 30 has a size of at least one block (more specific information 41 bitmap has a size of 31 sector or more), and that the combined size of SBM 30 and TDDS 32 is more than one block.

The first version of the implementation

(1) zone layouts

Optical disk 1 as write-once recording media information according to the first specific preferred option for the implementation of the present invention has a layout (or the location of zones), identical to the above described with reference to Fig. 2.

(2) the Layout of the data of the initial TDMS 20

Fig. 3 illustrates the layout of the initial data of the temporal structure of 20 disk management (TDMS), which is written at the beginning of the time zone 17 disk management (TDMA) (or the first of several TDMA) optical disc 1 according to the first preferred option for the implementation of the present invention.

As shown in Fig. 3, the initial TDMS 20 consists of an initial bitmap 30 space (SBM), two temporary structures, 32 disk definition (TDDS) and initial provisional list of 31 defects (TDFL). In each of SBM 30 and TDFL 31 write operation is performed in combination with an associate of TDDS 32 (i.e. unit-based update the structure of the disk management). Initial TDMS 20, shown in Fig. 3, consists of identical elements (but of a different order of entries) with the initial TDMS illustrated in Fig. 17. In particular, before the data, including the initial SBM 30, recorded a one-block (or one cluster) data combinations of the initial TDFL 31 and TDDS 32 (i.e. units update the structure of the disk management) is written (or hosted) first. After that recorded (or disposed of) two blocks (or two cluster) data combinations initial SBM 30 and TDDS 32 (i.e. units update the structure of the disk management). It should be noted that when these three block units of data are formed in combination, insignificant part of the data of these three blocks of data can be either fictitious data (all of which are zero), or complementary data indicating his insignificancy, thereby forming the data with the size of one block.

Under such an arrangement, even if the size of SBM 30 increases storage capacity per layer for recording so that the size of the unit structure update disk management, i.e. the combined size of SBM 30 and TDDS 32 exceeds one block (i.e., is two units or more), data, including TDDS 32, can always be located in the first block TDMA 17. Also, if the first unit is defective, these data can be placed in the first of the following blocks in which the operation of reading/writing can be carried out properly.

It should be noted that the identical effect should be achieved, even if this method applies to the case of SBM 30 has a size of 31 sector and less (i.e. to the case when the combined size of SBM 30 and TDDS 32 equal to or less than one block).

Specific recording procedure described below in section (5).

(3) Various kinds of information contained in TDDS 32

Fig. 4 illustrates the structure of the data TDDS 32 according to the first preferred option for the implementation of the present invention.

TDDS 32, shown in Fig. 4, contains basically the same information already described with reference to Fig. 16, but with additional features information 61 location SBM #1, as well as information 56 location SBM #0.

In particular, TDDS 32, shown in Fig. 4 includes DDS-title 50, which includes the ID of the disclosing identification information as TDDS 32 and information on the number of updates; size 51 internal backup zone and size 52 external backup zones, which are fragments of information about the appropriate amounts of internal and external reserve zones 15 and 16, that determine the location of the zones in zone 5 data; information 53 recording mode, indicating whether the mode recording mode recording mode or random write; size 54 TDMA internal backup zone, size 55 TDMA external backup zone, provide information to the size if a TDMA in the internal and external reserve areas 15 and 16, as shown in Fig. 15; information 57 location DFL #0, information 58 location DFL #1, information 59 location DFL #2 and information 60 locations DFL #3, which are fragments information location of the corresponding blocks in which the last TDFL 31 (most of the four units); and information 56 location SBM #0 and information 61 location SBM #1, which are fragments of information about the location of the storage device last SBM 30. In other words, when SBM has a size of 30 in two blocks, its location information is also increasing, respectively.

Further in this document using specific examples described in detail why these pieces of information location (i.e., information location TDFL 31 and location information SBM 30) should be provided for the relevant blocks.

Fig. 5 schematically illustrates how TDMS 21 (see Fig. 14) can be written in TDMA 17, and what information location is provided TDDS 32. In Fig. 5 four blocks A-D TDMA 17 are considered as an example.

Part (a) of Fig. 5 illustrates the case when the size of the combined data TDFL 31 and TDDS 32 equal to or less than one block, and the case when SBM 30 and TDFL 31 are recorded simultaneously (for example, when you write the initial TDMS 20).

In the first block of A written TDFL 31 and TDDS 32. At this point in time location information DFL #0 TDDS 32 specifies the starting location of the block A, hosts TDFL 31. On the other hand, information 56 location SBM #0 and information 61 location SBM #1 is written to point to the corresponding initial location of the blocks B and C as their expected locations, as these SBM #0 and #1 has not yet been written.

Part (b) of Fig. 5 illustrates the case when TDFL 31 has a size of more than two block, and when the block B, which must be written, is defective. Because TDFL 31 and TDDS 32 have a combined size in three blocks, the data of the first unit (TDFL #0) are written in block A. however, because the next block B is defective unit, the data of the second block (TDFL #1) is written in block C, which comes after the defective unit. Also, then the rest of the data (i.e. data TDFL #2 and TDDS 32, which have a combined size in one block) is written in block D. In this case the information 57 location DFL #0 specifies the starting location of the unit b, information 58 location DFL #1 specifies the starting location of the block C, and information 59 location DFL #2 specifies the starting location of the block D, as indicated by the solid arrows in Fig. 5.

Similarly, part (a) of Fig. 5 part (c) of Fig. 5 also illustrates the case when the size of the combined data TDFL 31 and TDDS 32 equal to or less than one block, when SBM 30 and TDFL 31 are recorded simultaneously and when block C, which must be written, is defective. In the first block of A written TDFL 31 and TDDS 32. At this point in time location information DFL #0 TDDS 32 specifies the starting location of the block A, hosts TDFL 31. On the other hand, information 56 location SBM #0 and information 61 location SBM #1 is written to point to the corresponding initial location of the blocks B and C as expected location, because these SBM #0 and #1 is not recorded, as indicated by the dotted arrows in Fig. 5.

The data is then SBM 30 and TDDS 32 recorded more than two blocks. In this case, SBM #0 can be written properly in block B, but the write operation in block C is unsuccessful, since this block C is defective. Therefore, the data SBM #1 and TDDS 32, which have a combined size in one block, written in block D, which comes after the defective unit.

At this time of the relevant pieces of information location TDDS 32 point to the next location. In particular, information 57 location DFL #0 specifies the starting location of the block A, in which TDFL 31 placed identical TDDS 32, described above. On the other hand, information 56 location SBM #0 and information 61 location SBM #1 point to the appropriate locations that these SBM #0 and #1 is actually recorded, as indicated by the solid arrows in Fig. 5. In other words, although the information 56 location SBM #0 indicates a block B, information 61 location SBM #1 specifies the starting location of the block D, excellent location, expected from TDDS 32, which is written in block A.

In other words, in this example, two TDDS 32, which must be written, have partially different content, but the correct information is always written in the new TDDS 32 (i.e. in TDDS 32, written in block D in the example illustrated in part (c) of Fig. 5).

In the example above, we already know that TDFL 31 and SBM 30 should be recorded simultaneously. In the event, such as shown in part (c) of Fig. 5, however, the information 56 location SBM #0 and information 61 location SBM #1 may remain unchanged from the previous information on the location of the previous SBM 30, recorded properly. In other words, by specifying the previous location in which the write operation was successful, instead of saving the information about their expected locations, the wrong piece of information location should never be extracted regardless of what TDDS 32 has been read.

In the example illustrated in paragraphs (a) and (c) of Fig. 5, the order of entry TDMS 21 is given so that TDFL 31 written before SBM 30. However, this order must be observed, at least for the initial TDMS section 20 (2)described above. Thus, relatively TDMS 21, SBM 30 can be recorded before TDFL 31.

(4) reader/writer

Fig. 6 shows a configuration for a device 100 read/write optical disk to perform read and write operations on an optical disk 1 of this preferred option of the implementation of the present invention. This device 100 can be either a recording device or device.

The device is 100 read/write optical drive connects to the controller on the high level (not shown) via bus 180 o. Controller high level may be, for example, the host computer (host PC).

Module 170 control system includes a module 171 entries and module 172 read to read and write data, including user data and control information; the module 173 management of the location of access for positioning on an optical disc 1, from which the data must be read or written next time, by reference to control information about the optical drive 1; 174 module upgrade the management information required to update management information is stored in the device mass memory 160 management information; and module 175 formation of management information for the formation of TDMS 21 and DMS, which must be written in TDMA or DMA, through a combination of data that must be refreshed from SBM 30, TDFL 31 and TDDS 32, which are stored in the device mass memory 160 control information.

(5) the Way to write (or initialization) initial TDMS 20

Fig. 7 is a block diagram of the sequence of operations ways, showing a procedure in which the device is 100 read/write optical disk handles the formatting initialization (i.e. initialization) write once optical disk 1.

First, at the stage of 701 form the control information in the initial state. In particular, the module 175 formation of management information forms the SBM 30, TDFL 31 and TDDS 32 in the initial state in a storage device 160 control information. In this case, SBM 30, TDFL 31 and TDDS 32 in the initial state is referred to as fragments of control information, which is configured to only information identifier, but for which the number of updates is a null-value. With regard to SBM 30 and TDFL 31, the "SBM 30 and TDFL 31 in the initial state" is synonymous with "initial SBM 30" and "initial TDFL 31, respectively.

Then at the stage of 702 form the initial TDMS 20. In particular, the module 175 formation of management information and translates the initial TDMS 20 in the form of record by combining SBM 30, TDFL 31 and TDDS 32 with each other so that the control information in the initial state, which was formed on the previous stage of processing 701, has the form of an initial TDMS 20 illustrated in Fig. 3. More specifically module 175 formation of control information provides data area of the three blocks to write in a storage device 160 management information, resets the area completely null data and then places the initial TDFL 31 at the beginning of the first block, TDDS 32 - at the end of the first block, the initial SBM 30 - from the beginning of the second block, and TDDS 32 - at the end of the third unit, thereby forming the data corresponding to the initial TDMS 20. With regard to the TDDS 32, its value must change, where at the stage of processing 703 or 705 update the location information that will be described below. That is why preferably TDDS 32 placed not at this moment in time, but just before a write occurs.

Then at the stage 703 update the information of the location of TDFL 31. In particular, directly before the write operation, the module 174 update management information updates the information of the location of the DFL the data corresponding to TDDS 32, which is shaped in a storage device 160 control information. More specifically, 170 module system management module uses 173 management of the location of access and thus calculates the location of the recording (for example, the original location of the TDMA 17), which can be written starting TDMS 20. Meanwhile module 174 update management information updates the information 57 location DFL #0 so that the information 57 indicates the location of the recording (for example, the original location of the TDMA 17), which is computed via the module 173 management of the location of access, and also clears 58 location DFL #1, information 59 location DFL #2 and information 60 locations DFL #3 to zero. The data is then placed in a predefined location (for example, at the end of the first block, in this case) in the area of data, which is provided for recording in the memory device 160 control information.

As for the location of SBM 30, still it is not known exactly what is the location of this information should be recorded. That is why the information of the location of SBM 30 can be zero or her location information can be forecasted assuming that piece of information also recorded properly.

Afterwards, the 705 update the information of the location of SBM 30. In particular, before the recording module 174 update management information updates the information of the location of SBM in data corresponding TDDS 32, which is shaped in a storage device 160 control information. More specifically, a module 170 control system calculates the location of the recording (for example, the second block when counting from the beginning of TDMA 17, if the write operation was successful at the first attempt in the previous step 704 processing) near the location where a portion of the initial TDMS 20 recorded in the previous step 704 processing, using module 173 management of the location of access. Meanwhile module 174 update management information updates the information 56 location SBM #0 so that the information 56 specifies the location of the recording (for example, at the beginning of the second block when counting from the beginning of TDMA 17), which is computed via the module 173 management of the location of access and update the information 61 location SBM #1 so that the information 61 points to the following location of the unit (i.e. at the beginning of the third block at counting from the beginning of TDMA 17).

It should be noted that the write operation is performed using information location 57 DFL #0, indicating the location of the recording identical to a location record in the previous step 704 processing, and using information 58, 59 and 60 of the location of the DFL #1, #2 and #3, which is expected to equal to zero (i.e., analogous TDDS 32, which was recorded in the previous step 704 processing).

Then at the stage of 706 write another part of the initial TDMS 20. In particular, the module 170 control system instructs the module 130 laser control task for the state recording, including laser power and strategy for the record, moves the optical head 120 via the module 140 control mechanisms in the location of the recording, which is defined by a module 173 management of the location of access at the previous stage 705 processing, and then receives the combined initial SBM 30 and TDDS 32, which are the data of the remaining two (i.e. the second and third units of the initial TDMS 20, recorded via the module 171 entries. If the write operation in any of these blocks is unsuccessful, identical sequence of processing steps are performed in the given block from the stage of 705 processing, and the write operation is repeatedly executed until all will not be recorded correctly in each block.

Although not described for this sequence of operations, TDDS 32 may contain information on the number of updates in DDS-header 50. During processing format when the initialization of null or any other appropriate value, indicating that it is information that is recorded during processing format when the initialization is recorded as the number of updates. In this case, each of SBM 30 and TDFL 31 record only once during handling formatting initialization, and, therefore, it can be written with information on the number of updates that are supposedly equal to zero. On the other hand, with regard to the TDDS 32, she is logged two times during processing, formatting during initialization. In this case, the write operation is also information on the number of updates that are supposedly equal to zero to indicate that each TDDS 32 included in the initial TDMS 20. However, the write operation can also be performed with information on the number of updates that are supposedly equal to zero for the first TDDS 32, which should be written, and one for the second TDDS 32, which should be written, respectively. In other words, the write operation can be performed with the task exact number of updates every time.

Through the implementation of these stages of processing initial processing TDMS 20 perform during formatting during initialization. According to the method described above, the data, including TDDS 32, always can be placed at the start location TDMA 17. That is why, even if the size of the data management information increased due to increased number of layers for the record, superimposed on the same disk, or increase storage density zone layouts optical disc 1 can still be understood by reading data from a predefined location, even without searching TDMA 17 for the last fragment of the control information.

The second variant of the implementation of the

(1) zone layouts

Optical disk 1 as the second specific preferred option of the implementation of the present invention has a layout (or the location of zones), identical to the above described for optical disc 1 first preferred option of the implementation of the present invention.

(2) the Layout of the data of the initial TDMS 20

Fig. 8 illustrates the layout of the initial data of the temporal structure of 20 disk management (TDMS), which is written at the beginning of the time zone 17 disk management (TDMA) (or the first of several TDMA) optical disc 1 according to the second preferred option for the implementation of the present invention.

Since the information 41 bitmap SBM 30 should be in one block (i.e., 32 sectors), the combined data SBM 30, and of temporal structure 32 definitions disk (TDDS) (i.e. units update the structure of the disk management) should be of a size corresponding to the two blocks. As shown in Fig. 8, the initial SBM 30, is included in the initial TDMS 20 of the second preferred option of the implementation of the present invention is that consists only of SBM-header 40 and has no information 41 bitmap.

This aspect will also be described. When you write the initial TDMS 20 (i.e. when the formatting occurs during initialization), all storage area (including the area of 5 data) on an optical disc 1 is still unwritten. In other words, information 41 bitmap SBM 30, contained in the initial TDMS 20, is recorded as data consisting of only zeros. In other words, even if the data has yet been recorded, the information 41 bitmap included in the initial TDMS 20, may still . That is why the initial SBM 30 the preferred option implementation consists only of SBM-title 40, no information 41 bitmap to reduce the size of the initial TDMS 20, that is one indication of this preferred option for implementation.

Part (a) of Fig. 8 illustrates the approximate location of the initial TDMS 20. Each initial temporary list of 31 defects (TDFL) and TDDS 32, which should be included in the combination of the initial TDMS 20, must be of a size only in one sector, as well as the initial SBM 30. That is why the data of one unit, which includes the initial SBM 30, initial TDFL 31 and TDDS 32, are treated as a unit update the structure of the disk management only for initial TDMS 20, and these pieces of information are recorded together as one unit.

Part (b) of Fig. 8 illustrates another approximate location of the initial TDMS 20. Similar to the first preferred option for the implementation of the present invention, as described above, the first unit of the initial TDMS 20 is the data one block (i.e. a unit update the structure of the disk management), which is a combination of primary TDFL 31 and TDDS 32, which should be written (or posted) at the start location, and her next block of data is another block (i.e. a unit update the structure of the disk management), which is a combination of initial SBM 30 and TDDS 32, which should be written (or posted) next.

As shown in these drawings through the introduction of the initial SBM 30 as data consisting only of SBM-title 40, primary TDMS 20, data, including TDDS 32, can always be located in the first block at the start location TDMA 17 (or in the first of the following blocks in which the operation of reading/writing can be carried out properly if the first unit is defective unit).

(3) Various kinds of information contained in TDDS 32

In the optical disc 1 second preferred option of the implementation of the present invention each TDDS 32 contains data that is identical to an analog optical disc 1 first preferred option of the implementation of the present invention that has already been described with reference to Fig. 4.

(4) reader/writer

The device is 100 read/write optical disk to perform the operation of reading/writing to optical disc 1 this second preferred option of the implementation of the present invention is identical configuration similar to the prototype of the first preferred option of the implementation of the present invention that has already been described with reference to Fig. 6.

(5) the Way you write (or initialized) initial TDMS 20

Fig. 9 depicts a block diagram of the sequence operations ways, showing a procedure in which the device is 100 read/write optical disk handles the formatting initialization (i.e. initialization) on a write once optical disk 1 according to the second preferred option for the implementation of the present invention. In the example described below, the initial TDMS 20 presumably written as one unit together, as shown in part (a) of Fig. 8. It should be noted that the procedure entry, as shown in part (b) of Fig. 8, basically the same as already described in section (5) with reference to Fig. 7 for the first preferred option of the implementation of the present invention, and its description is omitted in this document.

First, at the stage 901 form the control information in the initial state. In particular, the module 175 formation of management information forms the SBM 30, TDFL 31 and TDDS 32 in the initial state in a storage device 160 control information. In this case, SBM 30, TDFL 31 and TDDS 32 in the initial state is referred to as fragments of control information, which is configured to only information identifier, but for which the number of updates is a null-value. With regard to SBM 30 and TDFL 31, the "SBM 30 and TDFL 31 in the initial state" is synonymous with "initial SBM 30" and "initial TDFL 31, respectively.

Then at the stage of 902 form the initial TDMS 20. In particular, the module 175 formation of management information and translates the initial TDMS 20 in the form of record by combining SBM 30, TDFL 31 and TDDS 32 with each other so that the control information in the initial state, which was formed on the previous stage 901 processing, has the form of an initial TDMS 20, shown in part (a) of Fig. 8. More specifically, a module 175 formation of control information provides data area one block for recording in the memory device 160 management information, resets the area completely null data and then places the initial TDFL 31 in the first sector of this block, the initial SBM 30 second upstream sector of the block and TDDS 32 in the last sector of the block, thereby forming the data corresponding to the initial TDMS 20. With regard to the TDDS 32, its value must change, when location information is updated at the stage of processing 903, which will be described below. That is why, preferably TDDS 32 placed not at this point in time, and is placed directly before starting to write operation.

Then at the stage of 903 update the information of the location of TDFL 31 and SBM 30. In particular, directly before the write operation, the module 174 update management information updates the information of the location of the DFL and location information SBM in data corresponding TDDS 32, which is shaped in a storage device 160 control information. More specifically, 170 module system management module uses 173 management of the location of access and thus calculates the location of the recording (for example, the original location of the TDMA 17), which can be written starting TDMS 20. Meanwhile module 174 update management information updates the information 57 location DFL #0 so that the information 57 indicates the location of the recording (for example, the original location of the TDMA 17), which is computed via the module 173 management of the location of access, and also resets all the information 58, 59 and 60 of the location of the DFL #1, #2 and #3 to zero. In addition, the module 174 update management information also updates information 56 location SBM #0 so that the information 56 specifies the location of the recording in an identical block (for example, at the beginning of the 31st sector when counting from the beginning of the first unit of TDMA 17). On the other hand, information 61 location SBM #1 set so that it was either zero or a value indicating that there is an effective information 41 bitmap, but that information has not yet been recorded (for example, FFFFFFFFh, which is a hexadecimal number). The data is then placed in a predefined location (for example, at the end of the first block, in this case) in the area of data, which is provided for recording in the memory device 160 control information.

Then at the stage of 904 record a portion of the initial TDMS 20. In particular, the module 170 control system instructs the module 130 laser control task for the state recording, including laser power and strategy for the record, moves the optical head 120 via the module 140 control mechanisms in the location of the recording, which is defined by a module 173 management of the location of access at the previous stage 903 processing, and then receives the combined initial SBM 30, primary TDFL 31 and TDDS 32, which are the initial data TDMS 20, recorded via the module 171 entries. If the write operation in this block 3 is unsuccessful, identical sequence of processing steps are performed again with stage 903 processing, and the write operation is repeatedly executed until all will not be recorded correctly.

Through the implementation of these stages of processing initial processing TDMS 20 perform during formatting during initialization.

According to the method described above, the data, including TDDS 32, always can be placed at the start location TDMA 17. That is why, even if the size of the data management information increased due to increased number of layers for the record, superimposed on the same disk, or increase storage density disk layout areas optical disc 1 can still be understood by reading data from a predefined location, even without searching TDMA 17 for the last fragment of the control information.

The third option is the implementation of the

(1) zone layouts

Optical disk 1 as the third specific preferred option of the implementation of the present invention has layout (or location) zones identical to the already described for optical disc 1 first preferred option of the implementation of the present invention.

(2) the Layout of the data of the initial TDMS 20

Fig. 10 illustrates the layout of the initial data of the temporal structure of 20 disk management (TDMS), which is written at the beginning of the time zone 17 disk management (TDMA) (or the first of several TDMA) optical disc 1 according to the third preferred option for the implementation of the present invention.

In particular, SBM 30, which is a combination of SBM-header 40 with a size in one sector and information 41 bitmap size 31 sector or more, has a size of at least 32 sectors (i.e. one unit). In a preferred embodiment such SBM 30 is divided into two bitmaps space, each of which has a size of at most 31 sector (i.e. primary SBM #0 30 and initial SBM #1 30). Each of these two pieces of data combined with TDDS 32 to generate data size in the same block as one unit structure update disk management. Also, the write operation is presumably for this unit. Thus, each of these bitmaps space is defined to be the size in one unit, in combination with TDDS 32 regardless of the size of the zone 14 user data.

More specifically, if the combined size of SBM-header 40 and information 41 bitmap is one block and one sector (i.e., 33 sector only, if SBM-title 40 has a size in one sector, but information 41 bitmap has a size of 32 sectors), formed the initial SBM #0 30 with effective data in 17 sectors, consisting of SBM-header 40 and the first half (i.e. 16 sectors) information 41 bitmap (referred to in this document as "partial information 41 bitmap #0"), and the other initial SBM #1 30 with effective data in 16 sectors, which are the second half of the information 41 bitmap (referred to in this document as "partial information 41 bitmap #1"). Then each of these SBM is combined with TDDS 32, thereby forming a unit update the structure of the drive control, and performing a write operation on the basis of this unit. As a result, the write operation can be performed so that TDDS 32 placed in each block, as shown in Fig. 10.

In a preferred embodiment zone size 14 user data in case the combined size information 41 bitmap, TDDS 32 and SBM-header 40 is one block is supposed to be "a pre-defined size". If the size of the zone 14 user data in a predefined layer recording exceeds the pre-set size, information 41 bitmap is divided into several fragments of information bitmap (for example, two pieces of information bitmap, which is referred to in this document as "partial information 41 bitmap #0" and "partial information 41 bitmap #1", respectively, if the size of the zone 14 user data in two or fewer times exceeds a pre-defined size). In this case, each of several bitmaps space (i.e. SBM #0 and #1 30) includes its associated fragment of several pieces of information bitmap. Each of several bitmaps space (SBM #0 and #1 30) has a size of one unit when combined with TDDS 32.

It should be noted that in respect of the data in one block, which is a combination of either initial SBM #0 30 and TDDS 32 or initial SBM #1 30 and TDDS 32, the data, in addition to the 17 sectors initial SBM #0 30 and one sector TDDS 32, and data, in addition to the two sectors initial SBM #1 30 and one sector TDDS 32 should not be used. That is why such unused data can be either fictitious data, consisting only of zeros, or complementary data indicating his insignificancy, and these unused data are combined, thereby forming and writing data to the size of one block.

Under such an arrangement, even if the size of SBM 30 (more specific information 41 bitmap) increases storage capacity per layer recording (i.e. the size of the zone 14 user data) so that the size of the unit structure update disk management, i.e. the combined size of SBM 30 and TDDS 32 exceeds one block (i.e., is two units or more), data, including TDDS 32, can always be located in the first block TDMA 17. Also, if the first unit is defective, these data can be placed in the first of the following blocks in which the operation of reading/writing can be carried out properly. More specifically, such a layout, TDDS 32 can be recorded in each block 3 TDMA 17, which recorded the initial TDMS 20.

It should be noted that this method of recording is applicable not only to the initial TDMS 20 during handling formatting initialization, but also to conventional TDMS 21 at that time, when the usual write operation is performed for TDMA.

In the example above, information 41 bitmap size 32 sectors allegedly divided into partial information bitmap, which includes the data of the first 16 sectors, and partial information bitmap, including data last 16 sectors, and these two pieces of partial information bitmap allegedly placed separately in SBM #0 30, which is the first block in the SBM 30 initial TDMS 20, and in SBM #1 30, which is the second unit SBM 30, respectively. Advantage that should be achieved through such a link will be described later.

In particular, information 41 bitmap changes when the write operation is performed for a range of zones, which must be managed by reference to information 41 bitmap SBM 30. In this case, if a write operation is performed only for a block, the relevant area, managed by a reference to the first 16 sectors information 41 bitmap, only the first 16 sectors information 41 bitmap change and some 16 sectors remain unchanged.

In this case only the SBM #0 30, which includes the data of the first 16 sectors information 41 bitmap (i.e. partial information 41 bitmap #0), should be updated in the SBM 30. For example, if a write operation is performed only for a zone, which should be managed by reference to the first 16 sectors (i.e. partial information 41 bitmap #0) information 41 bitmap (i.e. only a part of the zone, which should be managed by reference to information 41 bitmap SBM 30), and information 41 bitmap changed, as shown in part (a) of Fig. 11, after treatment of the format when the initialization is performed, only the changed SBM #0 should be updated, as shown in part (b) of Fig. 11.

In this case the information 56 location SBM #0 indicated by TDDS 32, changes to the information, which specifies the starting location of the block D, which just re-recorded, but the information of the location of the SBM #1 can remain as is, to still point to the original location of the block B, for which you have a previous write operation.

If only part of the management information (for example, SBM 30), that is to be updated, written in TDMA 17, as described above, TDMA 17, which is the area of control information can be used more effectively in comparison with the case when the data of the whole SBM 30 (with the size of a two-block in this example) must be recorded each time.

However, if the only part that should be updated, written in TDMA 17, information on the number of updates contained in SBM-header 40, should be problematic. In other words, every time SBM 30, which should be written, updated, the write operation must be run with information on the number of updates Lin in SBM-header 40. That is why, according to the layout, in which SBM-header 40 is included only in SBM #0 30 as shown in Fig. 10 even if a write operation was performed for a zone, which should be managed by reference to partial information 41 bitmap #1 included in the SBM #1 30, and if only this partial information 41 bitmap #1 SBM #1 30 altered, not only SBM #1 30, but also SBM #0 30, which includes SBM-header 40 the information on the number of updates should be recorded simultaneously.

To overcome this problem SBM-header 40 can be provided for each unit update the structure of controlling the drive size in one block, which includes information 41 bit map, as shown in Fig. 12. In other words, SBM-header 40 can be given not only to SBM #0 30 but also for SBM #1 30. In this case, SBM #1 30 consists of SBM-header 40-and second-16 sectors information 41 bitmap (i.e. partial information 41 bitmap #1) and has effective data size in 17 sectors. Then there are several (for example, two in this example) independent SBM 30 in the pre-defined layer recording.

More specifically, SBM-header 40 contains information about a range of areas which must be managed by reference to SBM. In other words, area 14 user data that must be managed by reference to information 41 bitmap range is divided into zones, which must be managed by SBM #0 30 and the range of the zone that must be managed by SBM #1 30, and SBM-header 40 is available for each of these two ranges to manage them. Areas ranges that should be managed by reference to SBM #0 30 and SBM #1 30, differ from each other. That is why SBM-title 40, containing information on the ranges of areas which need to be managed by SBM, preferably available for both of SBM #0 and #1 30. In addition, to update information on the number of updates, as described above, SBM-header 40 preferably be provided for both of SBM #0 and #1 30 when SBM 30 partially renewed.

As described above, each of several bitmaps space (SBM #0 and #1 30) to use to manage the area 14 user data in a predefined layer for the record, have a header (i.e. SBM-header 40)containing information on the range, which should be managed by reference to partial information bitmap (i.e. partial information bitmap #0 or #1 41), contained in it. In addition, the header (i.e. SBM-header 40) each of several bitmaps space (SBM #0 and #1 30) may contain information on the number of updates SBM 30 bitmap space.

As a result, if a write operation is performed only for a zone, which should be managed by reference to partial information 41 bitmap #1 included in the SBM #1 30, and if only partial information 41 bitmap #1 SBM #1 30 modified, can be updated only this SBM #1 30. On the other hand, if partial information bitmap both of SBM #0 and #1 30 changed, TDMS 21, which includes both of these SBM #0 and #1 30, written in TDMA 17. However, if only partial information 41 bitmap #1 SBM #1 30 revised; TDMS 21, which includes SBM #1 30, but not including SBM #0 30 is written in TDMA 17.

As described above, if a write operation was performed for the zone management, which must be managed by reference to specific fragment partial information bitmap, that only bitmap space included in this particular fragment of partial information of the bitmap must be updated and recorded into a temporary area of 17 disk management (TDMA). If a write operation was performed for the zone management bitmap space, which includes a specific piece of information bitmap, no need to update every bit map of space and record it in a temporary area of 17 disk management (TDMA). In other words, because only part of the control information that must be updated, can be written in TDMA 17, thus, the time zone 17 disk management (TDMA) can be used more effectively.

In the example above, information 41 bitmap size 32 sectors presumably evenly split on the first 16 sectors and the second 16 sectors which should be assigned to the relevant bits of partial information bitmap for SBM #0 and #1 30. However, the appointment should always be carried out evenly.

For example, is also effective to assign the first 30 sectors (i.e., the maximum size that any fragment of partial information bitmap probably could have) to SBM #0 30, the last two sector - for SBM #1 30, respectively. This should be effective, particularly when only SBM #0 30 has SBM-header 40 with information on the number of updates. In this case, the size of the zone, which is managed by information 41 bitmap contained in SBM #0 30 which includes SBM-title 40, which should be written every time SBM 30 is written in TDMA 17, preferably exceed the size of the zone, which is managed by information 41 bitmap contained in SBM #1 30 without SBM-header 40. In this case, the more area, which should be managed by reference to information 41 bitmap, the greater the likelihood of changes to the information 41 bitmap and the less often should be updated SBM #1 30.

For this reason, if only partial information bitmap SBM #0 and #1 30 changed, TDMS 21, including as SBM #0 30 and SBM #1 30, written in TDMA 17. However, if only partial information 41 bitmap #1 SBM #1 30 changed, TDMS 21, which includes SBM #1 30, but not including SBM #0 30 may be recorded in TDMA 17. Hence, may be achieved by the effect of selective write only part of the control information that must be updated, TDMA 17, as described above.

Optional header (i.e. SBM-header 40) multiple bitmaps space (i.e. SBM #0 and #1 30 may include the identifier specifying that this information is bitmap space (i.e. SBM #0 or #1 30) and information about the range, which should be managed by reference to partial information bitmap (i.e. partial information bitmap #0 or #1 41), which has each of these bitmaps space (SBM #0 and #1 30). Examples of these pieces of information about the range, which should be managed by reference to partial information bitmap, include the start address and size of the zone under consideration.

As a result, by extracting information (for example, the starting address and size of the zone under consideration) with a range of areas which must be managed using the header of a particular bitmap space, can this area, managed by reference to this particular bit map space. In addition, if you activate this range information zone, which should be managed by reference to the title (for example, the starting address and size of the zone under consideration), the zone management bitmap space can be assigned to any random size, and destination templates can easily change, thereby providing you with a wider range of selectivity (or flexibility).

(3) Various kinds of information contained in TDDS 32

In the optical disc 1 third of the preferred option of the implementation of the present invention each TDDS 32 contains data that is identical to an analog optical disc 1 first preferred option of the implementation of the present invention that has already been described with reference to Fig. 4.

(4) reader/writer

In the future, this document describes some of the processing is done by a device and method for recording information on optical disc 1 third of the preferred option of the implementation of the present invention, if the size of the zone 14 of user-specific data layer for a record exceeds a predefined size (for example, the size of the zone of the user data in case the information 41 bitmap, TDDS 32 and SBM-header 40 have a combined size in one block). In this case, more bitmaps space (for example, SBM #0 and #1 30) are formed concerning a zone of user-specific data layer for the record. Then unit updates the management structure of the disk, which includes one of several bitmaps space (SBM #0 and #1 30) and the structure of the disk definition (TDD) 32, is written into a temporary area of 17 disk management (TDMA).

Such a treatment of the recording and processing of entries, which will be described below are performed by instructing 170 module management system (see Fig. 6) to control the relevant components of the device read/write 100 and by instructing the optical head 120 irradiation on the optical disk 1 using a laser beam.

In addition, if the size of the zone 14 of user-specific data layer for a record exceeds a predefined size (for example, the size of the zone 14 user data in case the information 41 bitmap, TDDS 32 and SBM-header 40 have a combined size in one block), the information 41 bitmap is divided into several fragments partial information bitmap (i.e. partial information #0 and #1 41 bitmap). Then one of these fragments partial information bitmap can be provided for each multiple bitmaps space (i.e. SBM #0 and #1 30).

In addition, the unit updates the management structure of the disk is written in block in a predefined location in the time zone 17 disk management (TDMA). Alternatively, instead of unit update the structure of management of such a disk, the second unit updates the management structure of the disk, which includes the structure 32 definitions disk (TDDS) and the initial list of 31 defects (TDFL) and has a size in one block can also be written. In this case, the temporary structure 32 definitions disk (TDDS) may include information location of the initial list of defects.

The initial list of 31 defects (TDFL) is TDFL smallest size, generally doesn't include the DFL-records 43, which are fragments of information about the defective zone. In other words, the initial list of 31 defects (TDFL) is TDFL, including the DFL-title 42, which is given only to the ID information, and in which the number of DFL-records 43 and information on the number of updates is zero, and the index 44 the end of DFL, for which to set the ID information, and that information on the number of updates is zero. Since the starting TDFL 31 has a size, which is equal to or less than one sector, combined size should be equal to or less than one unit (i.e. the same cluster) even when recording together with TDDS 32.

In addition, the "block in a predefined location in the time zone 17 disk management (TDMA)is mentioned as the first of several to be read and written blocks in the time zone 17 disk management (TDMA).

In the future, this document describes the device and method to read information from an optical disc 1 third of the preferred option of the implementation of the present invention. Processing reading is performed by instructing the optical head 120 irradiation on the optical disk 1 using a laser beam, reception of Ohr Hozer for signal reading and then instruct the module 170 management system (see Fig. 6) to control the relevant components of the device read/write 100.

A certain number of bitmaps space (i.e. SBM #0 and #1 30) is formed relatively zone 14 user data of a particular layer recording. In the time zone 17 disk management (TDMA) optical disc 1 remains unit updates the management structure of the disk, which includes one of these bitmaps space (SBM #0 and #1 30) and the temporal structure of 32 definitions disk (TDDS) and having the size of one block. From this time zone 17 disk management (TDMA) of this optical disc 1 retrieved unit updates the management structure of the disk, which includes temporal structure to 32 disk definition (TDDS) and having the size in one unit, and bitmap space (i.e. SBM #0 or #1 30).

Additionally, in a block in a predefined location in the time zone 17 disk management (TDMA) optical disc 1 of the implementation of the preferred option is saved to either the unit of structure update disk management, or other unit updates the management structure of the disk, which includes temporal structure to 32 disk definition (TDDS) and the initial list of 31 defects (TDFL) and having the size of one block. In this case, the unit or update the structure of the disk management or other unit updates the management structure of the disk can be read from a block in a predefined location in the time zone 17 disk management (TDMA). Optional, temporal structure, 32 disk definition (TDDS) may have information about the location of the initial list of defects. In this case, the "block in a predefined location in the time zone 17 disk management (TDMA)" may be the first of several to be read and written blocks in the time zone 17 disk management (TDMA).

(5) the Way to write (or initialization) initial TDMS 20

Fig. 13 is a block diagram of the sequence of operations ways, showing a procedure in which the device is 100 read/write optical disk handles the formatting initialization (i.e. initialization) on a write once optical disk 1 according to the third preferred option for the implementation of the present invention.

First, at the stage 1301 form the control information in the initial state. In particular, the module 175 formation of management information forms the SBM 30, TDFL 31 and TDDS 32 in the initial state in a storage device 160 control information. In this case, SBM 30, TDFL 31 and TDDS 32 in the initial state is referred to as fragments of control information, which is configured to only information identifier, but for which the number of updates is a null-value. With regard to SBM 30 and TDFL 31, the "SBM 30 and TDFL 31 in the initial state" is synonymous with "initial SBM 30" and "initial TDFL 31, respectively.

Then at the stage 1302 form the initial TDMS 20. In particular, the module 175 formation of management information and translates the initial TDMS 20 in the form of record by combining SBM 30, TDFL 31 and TDDS 32 with each other so that the control information in the initial state, which was formed on the previous stage 1301 processing, has the form of an initial TDMS 20 illustrated in Fig. 10.

More specifically, if SBM has a size of 30, for example, in one unit and one sector (i.e., 33 sector), 175 module of formation of control information provides data area of the three blocks to write in a storage device 160 management information, resets the area completely null data and then puts the data corresponding to the first 17 sectors (i.e. initial SBM #0 30 consisting of one sector SBM-header 40 and the first 16 sectors information 41 bitmap (partial information 41 bitmap #0)) for initial SBM 30 since the beginning of the first the block. Module 175 formation of management information places the TDDS 32 in the last sector of the first block of the data corresponding to the second 16 sectors (i.e. initial SBM #1 30, which includes partial information 41 bitmap #1) for initial SBM 30 - from the beginning of the second block, TDDS 32 - in the last sector of the second block, the initial TDFL 31 - in the beginning of the third block and TDDS 32 - in the last sector of the third unit, thereby forming the data corresponding to the initial TDMS 20.

As shown in Fig. 12, each several bitmaps space (SBM #0 and #1 30) to use to manage the area 14 user data in a predefined layer for the record, have a header (i.e. SBM-header 40)containing information about the range of areas that must be managed by reference to partial information bitmap (i.e. partial information bitmap #0 or #1 41), contained in it. In this case, the data that must be placed at the beginning of the second unit in the zone data, which is supplied with the storage device 160 managing information, data are 17 sectors, consisting of one sector SBM-header 40 and data of the second 16 sectors initial SBM 30 (i.e. initial SBM #1 30, which includes partial information 41 bitmap #1).

In addition, SBM-header 40 may include an identifier that indicates that this information is bitmap space and information on the range, which should be managed by reference to each of several bitmaps space (for example, the starting address and size of the zone under consideration). In addition, SBM-header 40 optionally may contain information on the number of updates SBM bitmap 30 space.

With regard to the TDDS 32, its value must change, when location information is updated on the stages of 1303, 1305 or 1307 processing, which will be described below. That is why preferably TDDS 32 placed not at this point in time, and placed immediately before a write occurs.

Then at the stage of 1303 update the information of the location of SBM 30. In particular, directly before the write operation, the module 174 update management information updates the information of the location of SBM in data corresponding TDDS 32, which is shaped in a storage device 160 control information. More specifically, 170 module system management module uses 173 management of the location of access and thus calculates the location of the recording (for example, the original location of the TDMA 17), which can be written starting TDMS 20. Meanwhile module 174 update management information updates the information 56 location SBM #0 so that the information 56 specifies the location of the recording (for example, the original location of the TDMA 17), which is computed via the module 173 management of the location of access, and also resets all the information 58, 59 and 60 of the location of the DFL #1, #2 and #3 to zero. The data is then placed in a predefined location (for example, in the last sector of the first block in this case) in the area of data, which is provided for recording in the memory device 160 control information.

With regard to the information 61 location SBM #1, which is information about the location of SBM 30 and TDFL #0, location information 57, which is information about the location of TDFL 31, at this point in time is still unknown in which the locations of these pieces of information should eventually be recorded. That is why these pieces of information locations can be zero, or their location information can be anticipated under the assumption that these pieces of information are also recorded properly. For example, information 61 location SBM #1 can point to the original location of the second unit when counting from the beginning of TDMA 17, and information 57 location DFL #0 may indicate the starting location of the third block at counting from the beginning of TDMA 17.

Then at the stage 1304 record a portion of the initial TDMS 20. In particular, the module 170 control system instructs the module 130 laser control on the task of recording conditions, including laser power and strategy for the record, moves the optical head 120 via the module 140 control mechanisms in the location of the recording, which is defined by a module 173 management of the location of access at the previous stage 1303 processing, and then receives the combined initial SBM #0 30 and TDDS 32, which are the data of the first unit of the initial TDMS 20, recorded via the module 171 entries. If the write operation in this block 3 is unsuccessful, identical sequence of processing steps are performed again with stage 1303 processing, and the write operation is repeatedly executed until all will not be recorded correctly.

Afterwards, the 1305 update the information of the location of SBM 30. In particular, before starting the writing process, 174 module update management information updates the information of the location of SBM in data corresponding TDDS 32, which is shaped in a storage device 160 control information. More specifically, a module 170 control system retrieves the location of the recording, which can be written starting TDMS 20 (for example, the original location of the second unit when counting from the beginning of TDMA 17, if the write operation was successful at the first attempt in the previous step 1304 processing), calculated via the module 173 management of the location of access. Meanwhile module 174 update management information updates the information 61 location SBM #1 so that the information 61 specifies the location of the recording (for example, the original location of the second unit when counting from the beginning of TDMA 17), which is computed via the module 173 management of the location of access. In this case the information 56 location SBM #0 allegedly points to the location where the recording is made at the previous stage 1304 processing, and information 58, 59 and 60 of the location of the DFL #1, #2 and #3 is supposed to be zero. The data is then placed in pre-defined locations (for example, in the last sector of the second block when counting from the beginning in this case) in the area of data, which is provided for recording in the memory device 160 control information.

As for the location TDFL #0 57, which is information about the location of TDFL 31, at this point in time is still unknown exactly what the location of this information should be recorded. That is why the information location 57 TDFL #0 can be zero or location information can be forecasted assuming that piece of information also has been properly recorded. For example, information 57 location DFL #0 may indicate the starting location of the third block at counting from the beginning of TDMA 17, which is the next location where the write operation can be performed.

Afterwards, the 1307 update the information of the location of TDFL 31. In particular, before the recording module 174 update management information updates in the location information TDFL. More specifically, a module 170 control system retrieves the location of the recording, which can be written starting TDMS 20 (for example, the third block when counting from the beginning of TDMA 17, if the write operation was successful at the first attempt on the previous stages 1304 and 1306 processing), next to the location for which a portion of the initial TDMS 20 recorded in the previous step 1306 processing, calculated via the module 173 management of the location of access. Meanwhile module 174 update management information updates the information 57 location DFL #0 so that the information 57 indicates the location of the recording (for example, the original location of the third block at counting from the beginning of TDMA 17), which is computed via the module 173 management of the location of access. In this case, update the information 56 location SBM #0, to indicate the location where a write operation was performed at the previous stage 1304 processing, update the information 61 location SBM #1 to point to the location in which a write operation was performed at the previous stage 1306 processing and write information 58, 59 and 60 of the location of the DFL #1, #2 and #3 as zero (i.e., analogous TDDS 32, which was recorded at the stage of processing 1304).

Then at the stage 1308 write another part of the initial TDMS 20. In particular, the module 170 control system instructs the module 130 laser control task for the state recording, including laser power and strategy for the record, moves the optical head 120 via the module 140 control mechanisms in the location of the recording, which is defined by a module 173 management of the location of access at the previous stage 1307 processing, and then receives the combined data of the initial TDFL 31 and TDDS 32, which are the data of the third block (i.e. the last block) initial TDMS 20, recorded via the module 171 entries. If a write operation this unit is unsuccessful, identical sequence of processing steps perform again step 1307 processing, and the write operation is repeatedly executed until all will not be recorded correctly.

TDDS 32 contains information on the number of updates in DDS-header 50. During processing format when the initialization is null or any other appropriate value, indicating that this information, which is recorded in processing time format when the initialization is recorded as the number of updates. In this case, each SBM 30 and TDFL 31 is recorded only once during handling formatting initialization and can therefore be written with the information on the number of updates that are supposedly equal to zero. With regard to the TDDS 32, on the other hand, TDDS 32 is written three times during processing, formatting during initialization. In this case, the write operation with its information on the number of updates that are supposedly equal to zero, to indicate that each TDDS 32 included in the initial TDMS 20. However, the write operation can also be performed with information on the number of updates that are supposedly equal to zero for the first TDDS 32 for records, a unit for the second TDDS 32 for records, and two for the third TDDS 32 for recording. In other words, the write operation can be performed with the task exact number of updates every time.

Through the implementation of these stages of processing processing entry initial TDMS 20 runs during formatting during initialization.

According to the method described above, TDDS 32 can be placed in each block 3, which should be recorded in TDMA 17 (i.e. TDDS 322 can also be hosted in a predefined location, such as the starting location TDMA 17). That is why, even if the size of the data management information increased due to increased number of layers for the record, superimposed on the same disk, or increase storage density disk layout areas optical disc 1 can still be understood only by reading data from a predefined location, even without searching TDMA 17 for the last fragment of the control information.

With reference to Fig. 13 describes how to perform a write operation while processing format initialization. However, when conventional TDMS 21, which includes SBM 30, shall be recorded, for example, both of SBM #0 30 and SBM #1 30 which form SBM 30, not always must record, as mentioned in section (2) describe the third preferred option of the implementation of the present invention. In other words, as in section (2) describe the third preferred option of the implementation of the present invention can be written to only some block SBM 30, in which information 41 bitmap updated and includes information that should be recorded in TDMA 17.

Optical disc 1 any one to three preferred options for the implementation of the present invention, described above, is optical disc, with at least one layer recording. Fig. 20 illustrates the cross-section of an optical disc 1. In Fig. 20 as an example illustrates the multi-layer optical disc 1 with three layers to record. Optical disc 1 includes layer 1002 for information recording, consisting of layers of L0, L1 and L2 for the records that are placed on top of each other in this order so that the layer L0 to write is at the furthest distance from the optical drive 1, irradiated by the light beam (i.e., the nearest to the substrate 1001). Area 14 user data is available for each of these layers for recording.

Briefly describes how to produce it in the optical drive 1. First, layers L0, L1 and L2 for the record, which includes the tracks which are recorded signals addressing and information signals representing control data, are formed in this manner on a substrate 1001 disk. As a result, you may get the layers to record, in each of which the user data area, the zones of faults and reserve zones are placed as shown in Fig. 1 and 2. Optional, dividing the layers may be provided between the layers for the record. Besides, layers to record can be covered, for example, the protective layer.

Although not described in the first, second and third preferred options for the implementation of the present invention, if there are multiple TDMA, as shown in Fig. 15, flat area, which provides information about the current TDMA, for example, can sometimes placed at the beginning of TDMA 17. Even in this case, "the original location of the TDMA 17", which is described as an example of a "pre-determined location in which shall be recorded the initial TDMS 20", references in this document to the initial location of the zone to use to record TDMS (which may be either a primary TDMS 20 or conventional TDMS 21), in addition to this indicator zone, i.e. the unit in the area of management information optical disc 1, in which the write operation earlier than in other places (one of the few to be read/written blocks, which is located at the beginning of the zone of control information).

In addition, according to some alternative method, a copy of the first TDDS 32, which should be recorded in TDMA, can be stored in this zone indicator. In this case, the layout of the areas optical disc 1 can be understood by scanning this indicator. However, in some cases, this indicator is not saved (for example, when you use one of several TDMA, which should be used first (for example, TDMA 17 in the primary zone 4)). Even in this case the identical effect should be achieved through the placement of data, including TDDS 32, always in a predefined location (for example, at the start location TDMA, which should be used first).

In the first, second and third preferred options for the implementation of the present invention described above, SBM 30 presumably has a size in two blocks. Nevertheless, the effects identical to the effects already described for the first, second and third preferred options for the implementation of the present invention can also be achieved, even if SBM 30 has a size of three units or more.

As SBM 30 has a size of more than one unit (i.e. in two units or more) in the first, second and third preferred options for the implementation of the present invention described above, SBM 30 may have information, such as a limitation of the SBM, indicating that this is the final location of the SBM 30 identical limiter 44 DFL TDFL 31.

Furthermore, in the first, second and third preferred options for the implementation of the present invention described above, SBM 30 presumably used as a typical fragment of the control information. However, the present invention must not only be applied SBM 30. On the contrary, an identical effect should be achieved, even if the present invention is applied to a different type of control information that has a size of one bloc or more when recording in TDMA 17, but should form together with TDDS 32 unit updates the management structure of the disk with the size of more than one unit (i.e. in two units or more), in particular, during processing, formatting during initialization.

Further in this document recording media information according to the present invention is described in detail.

<Basic parameters>

In particular, regarding BD, uses a laser beam with a wavelength of approximately 405 nm (which may be within range 400-410 nm provided that mistakes than 5 nm relative to a standard value of 405 nm) and lens element with the NA (numerical aperture) approximately 0,85 (which may be within range 0,84-0,86 provided that mistakes than 0,01 relative to a standard value of 0.85). BD has a track pitch of approximately 0,32 microns (which may be within range 0,310-0,330 microns provided that mistakes than 0,010 microns with respect to standard values 0,320 microns), and has one or two layers to write. BD has one-sided single-layer or as a one-sided double layer structure on the side of the fall of the laser beam and the plane of the storage layer, or to write at a depth 75-100 microns when measured from the surface of the protective coating BD.

Signal recording supposedly is modulated through modulation technology 17PP. Record label presumably have the length of the shortest label in 0,149 microns or 0,138 microns (which is the length of the label 2T, where T is one cycle of the reference clock pulse and the reference period of modulation in the case, if the mark is recorded in accordance with a pre-defined rule modulation), i.e. length T channel bits in 74,50 nm or 69,00 nm. BD has a storage capacity of 25 GB or 27 GB (more precisely, 25,025 GB or 27,020 GB), if it is a single-sided single layer disc, but has a storage capacity of 50 GB or 54 GB (more precisely, 50,050 GB or 54,040 GB), if he is unilateral, two-layer disc.

Clock frequency of the channel is estimated at approximately 66 MHz (according to the speed of transmission on the channel bits 66,000 Mbit/s) at standard speed (BD BD 1x), 264 MHz (according to the speed of transmission on the channel bits 264,000 Mbit/s) in transmission speed 4x BD, 396 MHz (according to the speed of transmission on the channel bits 396,000 Mbit/s) in transmission speed 6x BD and 528 MHz (according to the speed of transmission on the channel bits 528,000 Mbit/s) in transmission speed 8x BD.

Also, the standard linear velocity (which is also referred to in this document as "reference linear velocity" or "1X") estimated 4917 m/s or 4554 m/S. Linear speed of 2x, 4x, 6x and 8x equal 9834 m/s, 19668 m/s, 29502 m/s and 39336 m/s, respectively. Linear speed in excess of the standard linear speed, usually larger than the standard linear speed in a positive whole number of times. But the factor will not necessarily be an integer and can also be a positive real number. Not necessarily linear velocity, which is below the standard linear velocity (for example, the linear velocity of 0.5x), can also be set.

It should be noted that these settings are the settings of already produced commercial single-layer or double-layer BD, which have a storage capacity of approximately 25 GB or about 27 GB per layer. To increase storage capacity BD already investigated and developed BD high density storage capacity of approximately 32 GB or approximately 33,4 GB per layer, three - or four-layer BD. In the future, this document, describes the indicative options for the application of the present invention for such BD.

<Structure of multi-layer recording information>

For example, provided that the optical drive is a single-sided disc, on which information is read and/or written by the fall of the laser beam on the side of protective coating, and if need be provided with two or more layers for the record, these multiple layers to record should be placed between the substrate and a protective coating. Sample structure for such a multi-layer disc is shown in Fig. 21. The optical drive is shown in Fig. 21, is (n+1) layers 502 to record information (where n is an integer number that is equal to or greater than zero). In particular, in the optical drive, the protective layer 501, (n+1) layers 502 for recording information (layers Ln-L0) and the substrate 500 are placed on top of each other in this order relative to the surface inside a laser beam 505. In addition, between each pair of adjacent (n+1) layers 502 for information recording inserted as element of the optical buffer separating layer 503. In other words, support layer L0 can be placed on the deepest level, which is located on the predefined depth from the surface of the incidence of light (i.e. at the greatest distance from the light source). Several layers of L1, L2,..., Ln writes can be arranged one above the other the reference layer L0 to the surface of the falling light.

In this case the depth of supporting layer L0, measured from the surface of incidence of the light multi-layer disc, can be equal to the depth (for example, approximately 0.1 mm) one layer for a single layer disk, measured from the surface of the falling light. If the depth of the deepest layer (i.e. the remote layer) is constant regardless of the number of layers for the record, placed on top of each other (i.e. if the innermost layer of the multi-layer disc is almost identical to a single layer for a single layer disc distance)can be compatible in the implementation of access to a reference layer, regardless of whether the drive is single-layered or multi-layered. In addition, even if the number of placed one upon the other layers to record increases, the impact tilt almost does not increase. This is due to the fact that although the innermost layer of the most affects the slope, the depth of the deepest layer multi-layer disc is approximately identical to the depth of a single layer for a single layer disc and is not increased in this case, even if the number of layers for the record, placed on top of each other, increase.

With regard to the direction of movement of the beam spot (which is also referred to herein as the "direction of the tracking" or "spiral direction"), the optical drive can be either a parallel path, or type the opposite way.

In the disk type parallel path spot is in the same direction in each layer, i.e. from some internal radial location of the outer boundary of the disk or from some external radial location of the inner boundary of the disk in each layer recording.

On the other hand, the disk type the opposite way, the direction of movement of the spot is reversed whenever layers that you want to scan, change from one layer to record on a connecting room. For example, if the stain on the bearing layer L0 passes from some internal radial location of the external border (and this is the direction mentioned in this document simply as "outside"), then a spot on the layer L1 for the record goes from some external radial location to the inner border (and this is the direction mentioned in this document simply as "inside"), and a spot on the layer L2 to record goes out etc. In other words, a stain on a layer of Lm records (where m is either null or an even number) runs out, and the spot on a layer Lm+1 for write takes place inside. On the contrary, the stain on the layer Lm records (where m is either null or an even number) goes inside, but the stain on the layer Lm+1 for record runs out.

With regard to the thickness of the protective coverings (protective layer)to minimize the impact of distortions spots in consequence of, or reduction of the focal length with the increase in the numerical aperture (NA), or tilt, protective coating can be reduced thickness. Numerical aperture (NA) is defined to be 0.45 for CD, 0,65 for DVD, but approximately 0.85 for BD. For example, if the recording medium has a total thickness of about 1.2 mm, protective coating can have a thickness of 10-200 microns. More specifically, the single-layer disc may include a transparent protective coating with the thickness of about 0.1 mm and a substrate with a thickness of approximately 1,1 mm On the other hand, double-layer disc may include protective coating with a thickness of approximately 0.075 mm, separating layer with a thickness of approximately 0.025 mm and a substrate with a thickness of approximately 1,1 mm Also, if the drive has three or more layers for the record, thickness(s) of the protective coating and/or separation layer can be further reduced.

<Configuration for one to four drives>

Fig. 22, 23, 24 and 25 illustrates a sample configuration for a single-layer, two-layer, three-layer and four disk drives, respectively. As described above, if the distance from the surface of incidence of the light to supporting layer L0 is supposed to be constant, each of these discs can have total thickness of the disk is about 1.2 mm (but more preferably, 1.40 mm or less, if you have a printed label), and the substrate 500 can have a thickness of approximately 1.1 mm, therefore the distance from the surface of incidence of the light to supporting layer L0 is approximately 0.1 mm in any of the examples shown in Fig. 23-25. In a single layer disc, shown in Fig. 22 (i.e. if n=0 in Fig. 21), the protective layer 5011 has a thickness of about 0.1 mm per layer disc, shown in Fig. 23 (i.e. if n=1 in Fig. 21), the protective layer 5012 has a thickness of approximately 0.075 mm, and the separation layer 5302 has a thickness of approximately 0,025 mm, three disk shown in Fig. 24 (i.e. if n=2 in Fig. 21), and in disk shown in Fig. 25 (i.e. if n=3 in Fig. 21), the protective layer 5013, 5014 and/or separating layer 5303, 5304 can be even more subtle.

<A process of manufacturing of optical disc>

This single-layer or multilayer disc (i.e. disk with k layers for recording, where k is an integer number that is equal to or greater than unity) can be manufactured by performing the following steps of the manufacturing process.

At the stage of forming of layers for the record, when forming the i-th layer recording (where i is an odd number, that is within the range 1-k) in the calculation of the substrate, the circular or spiral paths are created so that the laser beam scans the layer to record from certain inner radial location on the disk to the outer limits. On the other hand, is formed when the j-th layer recording (where j is an even number, that is within the range 1-k) in the calculation of the substrate, the circular or spiral paths are created so that the laser beam scans the layer recording from some external radial location on the disk to its inner border. With regard to the single-layer disc, k=1, and, therefore, an odd number of i, which is within the range 1-k, should be unit, when k=1, and only one layer recording is available as the i-th layer recording. In addition, if k=1, there is an even number j, that is within the range 1-k, and, consequently, the j-th layer recording is not available.

Also, various zones can be assigned to the lanes in each of these layers for recording.

Fig. 26 shows the physical structure of an optical disc 1 according to the preferred option for the implementation of the present invention. On optical disc 1 many tracks 2 is located either concentrically or spiral. Also, each of these tracks 2 is divided into many sectors. As described below, the data allegedly written on each of these tracks 2 on the basis of the unit 3 pre-defined size.

Optical disk 1 of this preferred option implementation has a large storage capacity per layer recording information than traditional optical drive (for example, BD 25 GB). Storage capacity is increased by increasing the linear density storage, for example, by reducing the lengths of the record labels that, for example, should be retained on an optical disc. When used in this document to "increase linear density storage" means the reduction of the length of the channel bits, which is the length, corresponding to the time T of one cycle of reference of the synchronization signal (i.e. the time T of the reference cycle modulation if the label is written by a pre-defined rule modulation). Optical disk 1 can have multiple layers to record information. For the following instructions, however, only one layer to record the information described for convenience. In case if there are multiple layers to record the information in a single optical drive, even if the tracks are the same width for the relevant sectors to record information, linear density storage may also differ between the layers through uniform variation of lengths labels in layers.

Each track 2 is divided into multiple blocks of every 64 kilobytes, that is a unit of data storage. Also, sequential block addresses are assigned to the blocks. Each of these blocks is divided into three into subunits tubes, each of which has a predefined length (i.e. three into subunits tubes to form one unit). Rooms subunits 0, 1, and 2 are assigned to three in this order.

<Storage density>

Further in this document density storage is described with reference to Fig. 27, 28 and 29.

Fig. 27(A) illustrates an example of BD 25 GB for which the laser beam 123 presumably has a wavelength of 405 nm, and the lens 220 lens presumably has a numerical aperture (NA) of 0.85.

Similarly, DVD, information is also written on track 2 BD as a sequence of labels 120, 121, which are formed as a result of physical changes. The shortest of this sequence marks mentioned in this document as "the shortest label. Fig 27(A) the label 121 is the shortest label.

The BD storage capacity of 25 GB the shortest label 121 has the physical length of the 0,149 microns, which is about 1/2,7 the shortest DVD label. Also, even if the resolution of the laser beam increases by changing the parameters of the optical system, such as wavelength (405 nm) and NA (0,85), this value is still quite close to the limit of the optical resolution, below which the record label is not perceptible to the light beam.

Fig. 28 illustrates the state, when the beam spot is formed in a sequence of tokens record on the track. In BD beam spot 30 has a diameter of approximately 0,39 microns, which may vary depending on the parameters of the optical system. If the linear density of storage increases without changing the structure of the optical system, the record label is compressed with identical amount of the beam spot 30, and read permission must decline.

The shorter the record label, the lower the signal amplitude reading, which should be built, when the record label is scanned with the help of the light beam. Also, the amplitude becomes zero when the label length is equal to the limit of the optical resolution. The inverse number of the same period of these record labels called "spatial frequency, and the relationship between spatial frequency and amplitude of the signal is called "the optical transfer function (OTF)". As the spatial frequency is increased signal amplitude decreases almost linearly. Also received the maximum frequency at which the amplitude of the signal becomes zero, called OTF-cutoff.

Fig. 29 is a schedule showing how OTF BD storage capacity of 25 GB varies with the length of the shortest of the record label. Spatial frequency, the shorter the label on the BD is approximately 80% and is sufficiently close to the frequency of the OTF-cut. You can also see that an alarm reading, representing the shortest tag has an amplitude, which is small and accounts for approximately 10% of the maximum apparently detected amplitude. Storage capacity in which the spatial frequency the shorter the label on the BD is located very close to the frequency of the OTF-cut-off (i.e. storage capacity at which the signal reading has virtually no amplitude), corresponding to approximately 31 GB in BD. When the signal frequency reading, representing the shortest label fits close to or exceeds the frequency OTF-cutoff limit optical resolution for laser beam may have been reached or even exceeded. As a result, the signal reader has a lower amplitude and SNR drops sharply.

That is why in the optical drive, high-density storage, shown in Fig. 27(B), shall have a linear density storage, specified by the signal frequency reading, representing the shortest label that can be in the vicinity of the frequency OTF-cut-off (i.e. below, but not significantly lower frequency OTF-cut-off) or exceed the frequency OTF-cut.

Fig. 30 is a schedule showing how the amplitude of the signal varies with the spatial frequency in the case, if the spatial frequency of the short tags (2T) exceeds the frequency OTF-cut and if the signal is read 2T has zero amplitude. In Fig. 30, spatial frequency, the shorter the label 2T 1.12 times higher than the OTF-cut.

<Relationship between wavelength, NA and length label>

Optical drive B with a high density of storage should meet the following relation between the length of the waves, numerical aperture and lengths of labels/passes.

Provided that the length of the shorter label is TM nm, and length of the shortest crossing is TS nm, the sum of P the length of the shortest label and the length of the shortest crossing is (TM+TS) nm. In the case of modulation 17, it is P=2T+2T=4T. With three parameters of the wavelength λ laser beam (which is 405 nm±5 nm, i.e. in the range 400-410 nm), the numerical aperture (NA) (which is 0.85±0,01, i.e. in the range 0,84-0,86) the sum of P and the length of the shortest tag and length of the short (P=2T+2T=4T in the case of modulation 17, in which the shortest length is 2T), if a single length T is reduced to such a point that the inequality

P< l /2NA

satisfied, the spatial frequency, the shorter the label exceed the frequency OTF-cut.

If NA=0.85 and l=405, finite length T, corresponding to the frequency of the OTF-cut, is calculated by using the following expression:

T=405/(2×0,85)/4=59,558 nm

(Conversely, if P>l/2NA, spatial frequency, the shorter the label becomes lower frequency OTF-cut).

As can be easily seen SNR should decrease only by increasing the linear density storage, due to the limit of the optical resolution. Therefore, if the number of layers to record information per drive increased excessively, reducing the SNR can have an unacceptable degree of taking into account the allowable reserve system. In particular, around the point in which the frequency the shorter the record label exceed the frequency OTF-cut, SNR should begin to decline sharply.

In the above definition density storage is described by comparing the signal frequency reading, representing the shortest label, with a frequency OTF-cut. However, if the density of information in the mass memory of your device BD additionally increases, the density of information in memory (and linear density of storage and storage capacity) may be defined on the basis of the principle of the identical only that described by reference to the relationship between the frequency of the signal reading, representing the second most short tag (or third most short label, or even less a record label), and the frequency OTF-cut.

<Storage density and the number of layers>

On the other hand, if the spatial frequency of the shortest labels equals or exceeds the frequency OTF-cut, storage capacity per layer can be approximately equal or exceed 32 GB (for example, 32,0 GB approximately 0.5 GB or 32 GB±1 GB), approximately equal to or greater than 33 GB (for example, 33,0 GB approximately 0.5 GB or 33 GB±1 GB), approximately equal to or greater than 33,3 GB (for example, 33,3 GB approximately 0.5 GB or 33.3 GB±1 GB), approximately equal or exceed 33,4 GB (for example, 33,4 GB approximately 0.5 GB or 33.4 GB±1 GB) approximately equal or exceed 34 GB (for example, 34,0 GB approximately 0.5 GB or 34 GB±1 GB) or approximately equal or exceed 35 GB (for example, by 35.0 GB approximately 0.5 GB or 35 GB±1 GB).

In this case, if the storage density per layer is 33.3 GB, full storage capacity of approximately 100 GB (more precisely 99,9 GB) is implemented through three combined layers for recording. On the other hand, if the storage density per layer is 33,4 GB, full storage capacity, which is more than 100 GB (more precisely 100,2 GB), is implemented through three combined layers for recording. This storage capacity is almost equal to the capacity if the four layer for the record, each of which has a density storage in 25 GB, provided for one BD. For example, if the storage density per layer is 33 GB, full storage capacity is 33 x 3=99 GB, only 1 GB (or less) to less than 100 GB. On the other hand, if the storage density per layer is 34 GB, full storage capacity is 34 x 3=102 GB, 2 GB (or less) exceeds 100 GB. In addition, if a storage density per layer is 33.3 GB, full capacity of the storage is 33.3 x 3=99,9 GB that only 0.1 GB (or less) to less than 100 GB. Also, if the storage density per layer is 33,4 GB, full storage capacity is 33,4 x 3=100,2 GB that only 0.2 GB (or less) exceeds 100 GB.

It should be noted that if a storage density increased significantly, it is difficult to perform a read accurately, because short tags should be read in quite difficult conditions. That is why the practical storage density, which must implement the full storage capacity of 100 GB or more without too substantial increase storage density should be around 33.4 GB per layer.

In this case, the optical drive can have either a four-layer structure with a storage density 25 GB per layer or three-layer structure with storage density in 33-34 GB per layer. If the number of layers for the record, superimposed in the disk increases, there is nevertheless signal the reading obtained from each of these layers has reduced amplitude (or reduced SNR), and the scattered light is also formed of these layers (i.e. the signal reading obtained from each layer for the record must be under the influence of signal received from the adjacent layer). For this reason, if the three-layer disc storage density in 33-34 GB per layer is used instead of the four-layer disk storage density 25 GB per layer, the full storage capacity of approximately 100 GB is realized by a smaller number of layers (i.e. three instead of four) with minimized the influence of this scattered light. That is why the manufacturer of the drive to which you want to realize the full capacity of the storage of approximately 100 GB while minimizing the number of layers for the record, superimposed, should prefer the three-layer disc with density information storage device in 33-34 GB per layer. On the other hand, the manufacturer of the drive to which you want to realize the full capacity of the storage of approximately 100 GB using traditional format as is (i.e. density information storage device in 25 GB per layer)may choose a four-layer disc with density information storage device in 25 GB per layer. Thus manufacturers with different needs can reach their goals using mutually various structures and, consequently, they have a high degree of flexibility in designing drives.

Alternatively, if the storage density per layer is in the range of 30 to 32 GB, the full storage capacity of three-layer disc almost reaching 100 GB (i.e. approximately 90-96 GB), but the full capacity of the storage layer drive is 120 GB or more. Among other things, if the storage density per layer is approximately 32 GB, the four-layer disk must have a full storage capacity of approximately 128 GB, which is two in the degree of seven, which should easily and conveniently be processed via computer. Furthermore, compared with the total capacity of the storage of approximately 100 GB implemented through a three-layer disk, even the most short tags can also be read at less severe conditions.

That is why, when the density of storage is necessary to increase the number of various densities of storage per layer (for example, about 32 GB and approximately 33,4 GB) preferably offered as several options so that the manufacturer disks can design the disk more flexible through the use of one of these multiple storage densities and any number of layers to write in a random combination. For example, a manufacturer who needs to increase the total capacity of the storage and simultaneous minimization of the influence of several layers on top of each other, offers the option of creating a three-layer disc with a total capacity of storage of approximately 100 GB by means of the arrangement on each other three layers to write with a storage density in 33-34 GB per layer. On the other hand, manufacturer, which needs to increase the full storage capacity while minimizing the impact on the read performance is offered the option of creating a four-layer disk with the full storage capacity of approximately 120 GB or more by placing one on top of another four layers to write with a storage density in 30-32 GB per layer.

In addition, if the grooves are cut on the recording medium of the optical information recording medium is part of the grooves and part between the parts of the grooves. That is why methods of recording data should vary depending on whether the data should be written on the part of the grooves, or on the part of . Specifically, data can be written differently, for example, only part of the grooves, only part of the or as part of the grooves, and on the part of . In this case, the method of recording data on part (i.e. the part of the grooves, or part ), which act when viewing from below the surface of incidence of the light, is called a "on the tracks". On the other hand, the method of recording data on the parts that are pressed when viewing from below the surface of incidence of the light, is called a "in the groove". According to the present invention, at least one of these two ways of recording can be applied arbitrarily. In other words, should be applied only entry on the tracks, or only a record in the grooves, or one of these two ways can be used selectively.

If one of these two entries should be allowed to selectively, information specify how records, indicating which of the two recording modes (i.e., a record on the tracks or record in the groove) must be applied for the media can be recorded on the media. With regard to the multilayer media, information job recording method for the relevant sectors should be maintained. In this case the information specify how records for relevant sectors may be stored together in the reference layer (which may be the deepest (L0) or the most superficial layer when viewing from below the surface of incidence of the light or layer, access to which is to be before all of the other layers during the boot disk). Alternatively, the only piece of information associated specify how records can be saved in each layer. Even alternatively, information specify how records for all layers can be stored in each layer.

In addition, information specify how records can be stored in a BCA (service procurement area) or in a zone of the information about the disk or imposed by a swinging groove. Area information about the disc is inside and/or outside the area of storage and is used to store mainly control information. Area information about the disk area is read-only and can have a wider track pitch than the store the zone data. Information specify how records can be stored in one, any two or all of these areas and parts.

Film to record can have the following two different properties, which are determined by the reflection coefficients of its recorded and unrecorded parts. In particular, if has a more high reflectivity than the recorded part of the film for entries has the property "from high to low (H to L). On the other hand, if part has a lower coefficient of reflection than the recorded part of the film for entries has the property "from low to high" (L to H). According to the present invention, at least one of these two properties in the film to record can be applied arbitrarily. In other words, a film for the recording media may only be the property of H to L or only property of L to H. Alternatively, a film for the entries can selectively allow one of these two properties.

If one of these two properties should be allowed to selectively, information job properties in the film for the record, indicating which of these two properties should have a film to record (i.e. H to L or L to H), can be recorded on the media. With regard to the multilayer media, information job properties in the film for entries for the relevant sectors should be maintained. In this case, the information you specify the properties of film entries for the relevant sectors may be stored together in the reference layer (which may be the deepest (L0) or the most superficial layer when viewing from below the surface of incidence of the light or layer, access to which is to be before all of the other layers during the boot disk). Alternatively, the only piece of information associated job properties in the film for recording can be saved in each layer. Even alternatively, the information you specify the properties of film entries for all the layers can be stored in each layer.

In addition, the information you specify the properties of films for recording may be preserved in the SCA (service procurement area) or in a zone of the information about the disk or imposed by a swinging groove. Area information about the disc is inside and/or outside the area of storage and is used to store mainly control information. Area information about the disk area is read-only and can have a wider track pitch than the store the zone data. Information job properties in the film to record can be stored in one, any two or all of these areas and parts.

With regard to the different formats and the aforementioned techniques, as storage density increases, the media, optical disk should have several different densities storage. In this case only some of these different formats and ways can be applied according to the density of storage, or others can be changed in different formats or methods.

As described above, write-once recording media information according to the present invention has at least one layer for records and information is written on it in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds pre-defined, more bitmaps space formed for the zone of user data predefined layer recording. Unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space contains one of these pieces of information bitmap.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects, which does not provide information on the defective zone.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

Recording device information according to the present invention, records information on write-once media record information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer recording exceeds the previously defined, the recording of information generates more bitmaps space for the zone of user data predefined layer for recording and records unit updates the management structure of the disk, which includes one of several bitmaps space and structure definitions disk and having the size in one unit, in the area of management information.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space contains one of these pieces of information bitmap.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of areas, managed by reference to this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

A method of recording information according to the present invention is configured to record information on write-once media record information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. A method of recording information includes the stages at which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, form more bitmaps space for the zone of user data predefined layer to write, and write unit updates the management structure of the disk, which includes one of several bitmaps space and structure definitions disk and having the size in one unit, in the area of management information.

In one preferred embodiment, the method further includes the stages at which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, share information bitmap into several fragments of information bitmap; and associate one of these pieces of information bitmap with each of several bitmaps space.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects, which does not provide information on the defective zone.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

The device of reading of the information according to the present invention, reads recording media information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds a predefined size, more bitmaps space formed for the zone of user data predefined layer recording. Unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information. Also, the reader reads the unit updates the management structure of the disk, which includes the structure definitions disk and having the size of one block from the zone of control information and receives a bitmap space.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space contains one of these pieces of information bitmap. Also, the reader reads the associated piece of information bitmap of each bitmap space.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases, and a predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects. The initial list of defects does not provide information on the defective zone. Reader reads the unit or update the structure of management disk or a second unit updates the management structure of the disc from the unit in a predefined location.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

The method of reading information according to the present invention is made with the possibility to read information from recording media information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes the area of user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information. Area of user data is available for each layer recording. Management information includes bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of the disk definition, that includes information location of the bitmap space. The size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data. If the size of the zone of user data in a predefined layer for the record exceeds pre-defined, more bitmaps space formed for the zone of user data predefined layer recording. Unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information. The method of reading information includes the stage at which reads unit updates the management structure of the disk, which includes the structure definitions disk and having the size of one block from the zone of control information and receipt of the bitmap space.

In one preferred embodiment, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap. Each of several bitmaps space contains one of these pieces of information bitmap. The method of reading information additionally includes a stage at which reads associate piece of information bitmap of each bitmap space.

In this particular preferred embodiment, each of several bitmaps space includes a header that provides information about a range of areas which must be managed by reference to associated piece of information bitmap for the bitmap space.

In particular a preferred embodiment, the size of the bitmap increases as the size of the zone of user data increases. Predefined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

In another preferred embodiment, the header provides information about the start address and size range of managed areas through the links on this piece of information bitmap.

Still one another preferred embodiment, the header provides information on the number of updates bitmap space.

Still one another preferred embodiment, the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and which has a size of one block. The structure of the disk definition includes location information about the initial list of defects. The initial list of defects does not provide information on the defective zone. The method of reading information includes the stage at which reads either the unit of update management structure disk or a second unit updates the management structure of the disc from the unit in a predefined location in the zone of the control information.

In this particular preferred embodiment, the unit in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

Still one another preferred embodiment, the bitmap space in each layer recording is divided into a number of parts of the bitmap space that can form a unit update the structure of determining disk size in one unit when combined with the structure of the disk definition. Unit structure update determine the disk size in one block, which is formed by combining parts of the bitmap space and structure definition disc is recorded in a zone of control information.

Still one another preferred embodiment, the bitmap space in each layer to record consists of data bitmap indicating whether each unit in the area of data written or unwritten; and header that provides information about the bitmap data. Unit structure update disk definition, formed by combining the header and definition structure disk without data bitmap bitmap space, is written in block in a predefined location.

Another way to record information according to the present invention is made with the possibility to write on write-once media record information that has at least one layer to record and on which information is recorded on a block basis. Write-once media records information includes data area in which the user data must be recorded; and the zone of control information for storage management structure of the disk, which provides control information about the recording medium information. Area data is available for each layer recording. The structure of the disk management includes bitmap space to use to analyze the written and unwritten condition in the zone-based data layer for the record; the list of defects for defect management in the area of data; and the structure of the disk definition, that includes information about the location of the zones recording media information and location information bitmap space and the list of defects. Bitmap space and the list of defects are recorded in the area of management information based on the unit of structure update disk management, which is defined through a combination of structures disk definition with each other. The combined size of the bitmap space and the structure of the disk definition in each layer recording is more than one block. A method of recording information includes the stage at which record the unit update the structure of controlling the drive size in one block, which includes the structure of the disk definition, at least in the unit in a predefined location in the zone of the control information.

In one preferred embodiment, the unit in a predefined location is a block in the zone of control information, in which the write operation earlier than in the other blocks.

In another preferred embodiment, the unit in a predefined location is at the beginning of the zones of the control information.

Still one another preferred embodiment, the unit of structure update determine the disk size in one unit, formed by combining the list of defects and structure of the disk definition of the initial state is recorded in a block in a predefined location.

Still one another preferred embodiment, the bitmap space in each layer recording is divided into a number of parts of the bitmap space that can form a unit update the structure of determining disk size in one unit when combined with the structure of the disk definition. Unit structure update determine the disk size in one block, which is formed by combining parts of the bitmap space and structure definition disc is recorded in a zone of control information.

Still one another preferred embodiment, the bitmap space in each layer to record consists of: data bitmap indicating whether each unit in a zone data written or unwritten; and header that provides information about the bitmap data. Unit structure update disk definition, formed by combining the header and definition structure disk without data bitmap bitmap space, is written in block in a predefined location.

Another recording device information according to the present invention is performed with the possibility to write on write-once media record information that has at least one layer to record, and to which the information is written in chunks. Write-once media information record includes: the data area in which the user data must be recorded; and the zone of control information, in order to save disk management structure, which provides control information about the recording medium information. Area data is available for each layer recording. The structure of the disk management includes: bitmap space to use to analyze the written and unwritten condition in the zone-based data layer for the record; the list of defects for defect management in the area of data; and the structure of the disk definition, that includes information about the location of the zones recording media information and location information bitmap space and the list of defects. Bitmap space and the list of defects are recorded in the area of management information based on the unit of structure update disk management, which is defined through a combination of structures disk definition with each other. The combined size of the bitmap space and the structure of the disk definition in each layer recording is more than one block. Device information record includes management module for recording unit update the structure of controlling the drive size in one block, which includes the structure of the disk definition, at least in the unit in a predefined location in the zone of the control information.

In one preferred embodiment, the unit in a predefined location is a block in the zone of control information, in which the write operation earlier than in the other blocks.

In another preferred embodiment, the unit in a predefined location is at the beginning of the zones of the control information.

Still one another preferred embodiment, records management module unit update the structure of determining disk size in one unit, formed by combining the list of defects and structure of the disk definition of the initial state, the unit in a predefined location.

Still one another preferred embodiment, the bitmap space in each layer recording is divided into a number of parts of the bitmap space that can form a unit update the structure of determining disk size in one unit when combined with the structure of the disk definition. Module records management unit structure update determine the disk size in one block, which is formed by combining parts of the bitmap space and the structure of the disk definition, in the area of management information.

Still one another preferred embodiment, the bitmap space in each layer to record consists of data bitmap indicating whether each unit in the area of data written or unwritten; and header that provides information about the bitmap data. Module records management unit update the structure of the disk definition, formed by combining the header and definition structure disk without data bitmap space in a block in a predefined location.

Another device of reading of the information according to the present invention is arranged to read information from recording media information that has at least one layer to record and in which the write operation is performed on a block basis. Write-once media records information includes data area in which the user data must be recorded; and the zone of control information for storage management structure of the disk, which provides control information about the recording medium information. Area data is available for each layer recording. The structure of the disk management includes bitmap space to use to analyze the written and unwritten condition in the zone-based data layer for the record; the list of defects for defect management in the area of data; and the structure of the disk definition, that includes information about the location of the zones recording media information and location information bitmap space and the list of defects. Bitmap space and the list of defects are recorded in the area of management information based on the unit of structure update disk management, which is defined through a combination of structures disk definition with each other. The combined size of the bitmap space and the structure of the disk definition in each layer recording is more than one block. Also, reader includes management module for reading unit update the structure of controlling the drive size in one block, which includes the structure of the disk definition, at least from the block in a predefined location in the zone of the control information.

Industrial applicability

Recording media information according to the present invention can be used as a write-once optical disk, in which the write operation may be arbitrarily in any location. In addition, the method of reading/record of information according to the present invention is applicable to a drive, optical drive that can read and write from/to the write-once optical disk, in which the write operation may be arbitrarily in any location.

List of reference numbers

1 - optical disk

2 - track

4 - the initial area

5 - area data

6 - a final area

10, 11, 12, 13 - DMA

14 - zone user data

a 15 - 16 backup area

17 - TDMA

20 - initial TDMS

21 - TDMS

31 - TDFL

32 - TDDS

40 - SBM-header

41 - information bitmap

42 - the DFL-header

43 - the DFL-record

44 - end index DFL

50 - DDS-header

51 - the size of the internal backup zone

52 - size external backup zone

53 - information record mode

54 - size TDMA internal backup zone

55 - size TDMA external backup zone

56 - information location SBM #0

57 - information location DFL #0

58 - information location DFL #1

59 - information location DFL #2

60 - information location DFL #3

61 - information location SBM #1

100 - reader/write optical disk

110 module processing instructions

120 - optical head

130 module laser control

140 module control mechanisms

150 - storage device

160 - storage device management information

170 - module system management

171 - writer

172 module reading

173 - control module location access

174 module update management information

175 module of formation of operating information

180 - I / o bus

1. Write-once media record information that has at least one layer to record, and to which the information is written in chunks, with write-once recording media information contains: the user data user data must be recorded; and the zone of control information for storage management information on a write once media recording information, and the area of user data provided for each referred layer for recording and control information contains: bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and the structure of determine the disk, which includes the information of the location of the bitmap space, and with the size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data, and moreover, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, more bitmaps space formed for the zone of user data predefined layer for the record, and with a unit update the management structure of the disk, which includes one of several bitmaps space and structure definitions disk and having the size in one block is written in the zone of the control information.

3. Write-once media recording of information on p.2, in which each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to its associated piece of information bitmap for the bitmap space.

4. Write-once media recording of information on item 3, in which the size of the bitmap increases as the size of the zone of user data increases, and where pre-determined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

5. Write-once media recording of information on item 3, in which the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

6. Write-once media recording of information on item 3, in which the header provides information on the number of updates bitmap space.

7. Write-once media recording information of claim 1, wherein the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and that has a size in one unit, in which the structure of the disk definition includes location information about the initial list of defects and that the initial list of defects does not provide information on the defective zone.

8. Write-once media, record the information in paragraph 7, where the bloc in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

9. Device information is recorded for recording information on write-once media record information that has at least one layer to record, and to which the information is written in chunks, with write-once media information record contains: - zone user data user data must be recorded; and zone control information storage management information on a write once media recording information, and the area of user data is available for each referred layer for recording and control information contains: - bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and - the structure of the disk definition, that includes information location of the bitmap space, and with the size of the bitmap space is defined that combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data, and moreover, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, the recording of information generates more bitmaps space for the zone of user data predefined layer for recording and records unit updates the management structure of the disk, which includes one of several bitmaps space and structure definitions disk and having the size in one block in the area of management information.

10. Recording device information item 9, in which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap, and in which each of several bitmaps space is provided with one of these pieces of information bitmap.

11. The device records the information in paragraph 10, in which each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to its associated piece of information bitmap for the bitmap space.

12. Recording device information item 11, in which the size of the bitmap increases as the size of the zone of user data increases, and where pre-determined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

13. Recording device information item 11, in which the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

14. Recording device information item 11, in which the header provides information on the number of updates bitmap space.

15. Recording device information item 9, in which the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and that has a size in one unit, in which the structure of the disk definition includes location information about the initial list of defects, and in which the initial list of defects does not provide information on the defective zone.

16. Recording device information item 15, where the bloc in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

17. A method of recording information for recording information on write-once media record information that has at least one layer to record, and to which the information is written in chunks, with write-once media information record contains: - zone user data user data must be recorded; and zone control information storage management information on a write once media recording information, and the area of user data is available for each referred layer for recording and control information contains: - bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and - the structure of the disk definition, that includes information location of the bitmap space, and with the size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone of user data, and a way of recording information contains the stages at which, if the size of the zone of user data in a predefined layer for the record exceeds pre-defined, form a more bitmaps space for the zone of user data predefined layer to write and record unit updates the management structure of the disk, which includes one of the few bit maps of space and structure definitions disk and having the size in one block in the area of management information.

18. A method of recording information on item 17, additionally contains the stages at which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, - share information bitmap into several fragments of information bitmap and - associate one of these pieces of information bitmap with each of several bitmaps space.

19. A method of recording information see item 18, in which each of several bitmaps space includes a header that provides information about a range of areas which must be managed by reference to its associated piece of information bitmap for the bitmap space.

20. A method of recording information on .19, in which the size of the bitmap increases as the size of the zone of user data increases, and where pre-determined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

21. A method of recording information on .19, in which the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

22. A method of recording information on .19, in which the header provides information on the number of updates bitmap space.

23. A method of recording information on item 17, in which the unit in a predefined location in the area of management information write unit or update the structure of management disk or a second unit updates the management structure of the disk, which includes the structure of the disk definition and initial list of defects and that has a size in one unit, in which the structure of the disk definition includes location information about the initial list of defects and that the initial list of defects does not provide information on the defective zone.

24. A method of recording information 23, where the bloc in a predefined location is above a few to be read and written blocks in the area of management information.

25. Reader for reading information from recording media information that has at least one layer to record, and to which the information is written in chunks, with write-once media information record contains: - zone user data user data must be recorded; and zone control information storage management information on a write once media recording information, and the area of user data is available for each referred layer recording, and with control information contains: - bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and - the structure of the disk definition, that includes information location of the bitmap space, and with the size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone user data, and moreover, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, more bitmaps space formed for the zone of user data predefined layer recording, and unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size of one block is written in the area of management information, and the reader reads the unit structure update disk management, which includes the structure definitions disk and having the size of one block from the zone of control information and receives a bitmap space.

26. Reader for section 25, in which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap, and in which each of several bitmaps space is provided with one of these pieces of information bitmap, and the reader reads the associated piece of information bitmap of each bitmap space.

27. Reader on .26, in which each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to its associated piece of information bitmap for the bitmap space.

28. Reader on item 27, in which the size of the bitmap increases as the size of the zone of user data increases, and where pre-determined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

29. Reader on item 27, in which the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

30. Reader on item 27, in which the header provides information on the number of updates bitmap space.

31. Reader for section 25, in which the unit in a predefined location in the area of management information is written to the unit or update the structure of the disk management or other unit update the structure of management disk, which includes the structure of the disk definition and initial list of defects and that has a size in one unit, in which the structure of the disk definition includes location information about the initial list of defects and that the initial list of defects does not provide information on the defective zone, and the reader reads the unit or update the structure of management disk or a second unit updates the management structure of the disc from the unit in a predefined location.

32. Reader on .31, where the bloc in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.

33. The method of reading information for reading information from recording media information that has at least one layer to record, and to which the information is written in chunks, with write-once media information record contains: - zone user data user data must be recorded; and zone control information storage management information on a write once media recording information, and the area of user data is available for each referred layer recording, and and control information contains: - bitmap space, that includes information bitmap to use to control the States of records in the zone of user data in a predefined one of the layers of the record; and - the structure of the disk definition, that includes information location of the bitmap space, and with the size of the bitmap space is determined so that the combined size of the bitmap space and structure definitions disk is always equal to the size of one block, regardless of the size of the zone user data, and moreover, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, more bitmaps space formed for the zone of user data predefined layer recording, and unit structure update disk management, which includes one of several bitmaps space and structure definitions disk and having the size in one unit, is recorded in the area of management information, and the method of reading information includes the stage at which reads unit updates the management structure of the disk, which includes the structure definitions disk and having the size of one block from the zone of control information and receive a bitmap space.

34. The method of reading information on .33, in which, if the size of the zone of user data in a predefined layer for the record exceeds a predefined size, information bitmap is divided into several fragments of information bitmap, and in which each of several bitmaps space contains one of these pieces of information bitmap, and with the method of reading information additionally includes a stage at which reads associate piece of information bitmap of each of the mentioned bitmap space.

35. The method of reading information 34, in which each of several bitmaps space includes a header that provides information about the range, which should be managed by reference to its associated piece of information bitmap for the bitmap space.

36. The method of reading information on .35, in which the size of the bitmap increases as the size of the zone of user data increases, and where pre-determined size is the size of the zone of user data, when combined size of the bitmap structure definition disc and title becomes equal to the size of one block.

37. The method of reading information on .35, in which the header provides information about the start address and size range of managed area via the links on this piece of information bitmap.

38. The method of reading information on .35, in which the header provides information on the number of updates bitmap space.

39. The method of reading information on .33 in which the unit in a predefined location in the area of management information write unit or update the structure of management disk or a second unit structure update disk management, that includes the structure of the disk definition and initial list of defects and that has a size in one unit, in which the structure of the disk definition includes location information about the initial list of defects and that the initial list of defects does not provide information on the defective zone, and the method of reading information includes the stage at which reads either the unit of update management structure disk or a second unit updates the management structure of the disc from the unit in a predefined location in the zone of the control information.

40. The method of reading information on § 39, where the bloc in a predefined location is at the beginning of the few to be read and written blocks in the area of management information.