MXPA01005144A - Method of immediate writing or reading files on a disc like recording medium - Google Patents

Abstract

A method of recording digital information signals on a removable rewritable disc like recording medium, the method comprising a short initialization step whereafter a blanc, unformatted medium is ready to receive user data. The initialization step comprises defining a general purpose area on the recording medium which is not intended for recording user data but for defect management and special application programs.

Description

METHOD OF WRITING OR IMMEDIATE READING OF FILES IN A DISCO TYPE RECORDING MEDIA The invention relates to a method for recording digital information signals in a rewritable and removable disk type recording medium, with a program area of the disc and, before the removal of the disc out of a recording device, by finalizing the disc with an input and output area that comprises control information. The invention also relates to an apparatus for recording digital information signals in, or from, a rewritable and removable disk type recording medium, the apparatus comprises input means for receiving the digital information signals, recording medium, receiving to receive the recording medium, recording means for reading the digital information signals in the recording medium, reading means for digital information signals stored in the recording medium, output means for outputting the digital information signals read , control means adapted for recording control digital information signals that represent the user data in a program area in the recording medium.

The world of PCs needs a replacement for the floppy disk drive. A rewritable storage medium of the disc type optical type, such as CD-RW, seems to be a logical choice because the magnetic floppy reading function has already been replaced by the CD-ROM. All the PCs of today are equipped with a CD-ROM and applications and the software is distributed on CD-ROM. Therefore a recording medium such as CD-RW or rewritable DVD, seems to be the perfect means to fill the need for writing possibility. Recording media of the optical-magnetic type have already tried to fill this gap, but all of them omit compatibility with the installed base. This is exactly what the CD-RW for example can deliver to the installed base of over approximately 200 million CDROM drives. The CD-RW media is cheap and the capacity is sufficient for the use of the floppy. In addition, the manufacturers of the operating systems want to get rid of the legacy material like the floppy drive. For OEM companies the idea is attractive, as they can replace the floppy drive, the CD-ROM drive and the DVD-ROM with a spindle unit as a Combi and with a double writer in the future. A new feature would also be added to the unit in addition to the speed that is always increasing. There are products on the market that allow the use of a CD-RW as a floppy drive, but do not behave the way you would expect a floppy CD to do. The access time is too low, the formatting time takes too much and the most important thing is that the unit does not fit in the current OS strategy. The disk must be immediately available to drag and send files. It requires a quick expulsion, the deletion must be instantaneous. For the purpose of allowing multiple shipping and shipping, a defect management is required. However, the management of defects must be done by the unit. This opens the way for the use of UDF 1.02 instead of UDFI.5, which is not supported on the write side by the operating system manufacturers. The unit should do the most background formatting and not the application or OS to minimize bus traffic and the interaction between the unit and the OS. Finally, the unit must do the Reading / Modification / Writing for packages.

Accordingly, among other things, it is an object of the invention to obviate the aforementioned disadvantages. According to one of its aspects, a method according to the invention is characterized by performing an initiation step as defined in the characterized part of claim 1. Due to the very limited amount of data to be recorded, this step will be completed in only a few seconds. The disk is then ready for data storage. further, the general purpose area can be used to add additional functionality by, for example, storage device driver programs that are found here or that allow such programs to use disk space. As the general purpose area can still be read by the legacy units as these units report the start of the Output area as the end of the user area, these units can employ additional functionality. So that compatibility is achieved. A favorable characterization is obtained by adding defect management according to the characterized part of the claim 2. This is required in case the functionality of dragging and sending files equivalent to the functionality of the removable disk is added. Another favorable characterization is obtained by reserving space for device drivers to handle defect management according to the characterized part of claim 3. This allows the legacy units to handle the defect areas. Another improvement is obtained by adding a sentinel area next to a defect table as defined in the characterized part of claim 5. This area can be used favorably for storage of property information as copyright information. This area can also be used to store a new defect table when the previous table has been worn. Another characterization is obtained by performing the formatting when the unit is inactive, according to the characterized part of claim 6. This has the advantage that the medium is formatted before an expulsion request occurs. The following characterization performs a completion step according to the characterized part of claim 7. The recording medium will be in a compatible CD-ROM state while the secondary defect table (SDT) can be read by a CD player. -ROM or a legacy reader. However, a favorable characterization is obtained by allowing an early ejection step according to the characterized part of claim 8. The ejection time is made as short as possible while the recording medium leaves the unit in a compatible state. of a CD-ROM or legacy unit. All data is recorded contiguously while the temporary defect table (DTT) can be used for defect management. Other favorable characterizations are described in the description.

These additional aspects and advantages of the invention will be discussed in more detail hereinafter with reference to the description of the preferential characterizations and in particular with reference to the accompanying Figures which show: Fig. 1 a basic disk deployment of a CD- ROM; Fig. 2 a display of a disc according to the invention; Fig. 3 link details of the Program Area; Fig. 4 the deployment of the General Purposes Area; Fig. 5 the location of the first Main Defect Table (MDT) in the Entry Area; Fig. 6 the replacement of a defective MDT; Fig. 7 the replacement of a defective Secondary Defect Table (SDT); Fig. 8 the composition of a Defect Table Package; Fig. 9 the display of the Table of Defects; Fig. 10 the deployment of the Sentinel Pack; Fig. 1 1 the status of the disk after initialization; Fig. 12 the status of the disc after some de-icing and recording; Fig. 13 the status of the disk after several completion steps; Fig. 15 the early ejection status of the disc, Fig. 16 the disc re-opening status and Fig. 17 a computer data system comprising a computer and a recording apparatus. Fig. 1 schematically illustrates the basic format of a CD-ROM, as it is known from the relevant standard, which is often denoted as the "Yellow Book", in analogy with the "Red Book" standard for the CD Audio. Descriptions of the physical standard of the CD-ROM can be found in the public documents available ISO / IEC 10149, from the audio CD in IEC 908. The physical standard for the recordable CD, denoted as the "Orange book"; is described in ISO / IEC 11172/1/2/3 /. The standard for the logical format of the CD-ROM is described in ISO-9660 (the Sierra Alta standard) and for the CD recordable in ECMA 168 / ISO13940 (the Frankfurter proposal). The area that transports data from the CD-ROM starts with an INPUT area, a DATA AREA is available for user data and ends with an OUTPUT area.

The methods for Formatting and Managing Defects described in this description can be used to optimize the performance of high-speed CD-RW in a computer environment. To exploit the total capabilities of the CD-RW High speed in a computer data storage environment, several conditions must be completed: 1) the system needs random access, 2) the recorded discs must be compatible with compatible Multi-read CD-ROM drives, 3) the system needs a Defect Management method that the unit or a dedicated device driver can manage, 4) formatting must be done by the unit in another plane [in back-ground] (without interaction with the application or Operating System that operates in the computer), 5) the disk must be available for immediate use after the insertion and the expulsion time must be minimum, 6) the recording is based on fixed packages of 32 blocks of User Data, in a single Track, on a single session disc.

To ensure read compatibility with multi-read CD-ROM drives (or legacy CD-R / RW recorders), the following requirements must be met: - the drive has an Entry Area, a Program Area and an Area of Exit, - all Program Areas between the Entrance Area and the Exit Area must be completely formatted. - all data, including the information on Defect Management and Replacement Areas, must be available within the Program Area (the space logically to which it will be directed) of the disk. Then the Defect Management can be managed by a dedicated device driver that operates under the computer's Operating System. When a disc meets all these conditions, we call this disc: "ROM-compatible". Because current CD-ROM drives do not support Defect Management, optional device drivers, which can add this functionality to the system, can be provided throughout the General Purpose Area, for example, during formatting.

The Defect Management System is based on a Main Defects Table (MDT) in the Disc Entry Area, and a Defective Defects Tables (SDT) and Replacement Packages in the General Purposes Area. The Defect Tables must be preceded by the so-called Sentinel Pack (STL) that contains all the OOh bits. The general deployment of the disk obtained with a method according to the invention is illustrated with respect to Fig. 2. The General Purpose Area is preferably located on the outside of the disk against the Entry area. A CD-writer with defect management according to the invention will report the start address of the General Purpose Area as the starting address of the Exit area. Then a UDF file system gets a smaller partition to use. The unused part is reserved for the replacement areas and contains the defect tables. In contrast to a legacy unit that will still report the end of the original Output address. This trick is needed to make defect management compatible with legacy units such as the CD-ROM. A CD-ROM reader is able to read the defect management area because it will be in your data area. A device driver will perform defect management instead of a legacy unit. Future CD-ROM readers will gain the ability to handle defect management on their own. This is just a firmware change in the ROM firmware. A writer Exit pointer must be added to the firmware. Compatibility with CD / DVD-ROM is obtained through a device or application driver that reads the defect table and handles defect management. The operating system then interacts with a CD-ROM, a legacy CD-RW, DVD-ROM or DVD-RAM only by means of a device driver or application that handles defect management. The CD-RW with the improved format according to the invention interacts directly with the Operating System. Usually the end user of a system likes to have the disk ready to be used seconds after it has been inserted into the drive. However, a blank disk has to be formatted before all of its capabilities can be fully exploited. Because the normal formatting process takes too much time, a formatting procedure in another plane [in the back-ground] will be defined, which starts the disk with a minimum amount of information, after which it will be available for recording and then will proceed with formatting during the time intervals when the unit is inactive. The formatting in another plane [in back-ground] only defines the physical formatting of the disk, which is independent of the system. A fully formatted disk is always in a ROM-compatible state. An ejection command can be executed without any delay. When an ejection is requested before the disk is fully formatted, a quick termination process will be executed to make the ROM-compatible disk before it leaves the recorder.

According to the existing CD-RW recording format, the data can be recorded in several different writing actions. This is referred to as increasing writing. In the case of increasing writing, the recorded data link rules must be taken into account. A link position is the physical location on the disk where the recording of the EFM signals is allowed to start and stop. In the case of data recording, an EFM recording sequence will start and end with Link blocks, Run in and Run out. Spaces are not allowed between recordings, a set of User Data, Run in, Link and Run out blocks is called a Package. The number of blocks of User Data in a package is called the size of the Package. The Link block contains the link position.

Fig. 3 shows details of the Link in the Program Area according to the existing CD-RW format. The Program Area consists of a Track with Fixed Packs with a size of 32 Usurary Data Blocks. Here is: LNK = Link Block, RI1.RI4 = Blocks Run-in, RO1, RO2 = Blocks Run-out, UDI..UD32 = Blocks of User Data and TDB = Block of Description of Track.

The Fig. 4 shows the deployment of the General Purpose Area (GPA) according to the invention. The General Purposes Area (GPA) consists of three parts: - the General Application Area (GAA), - the Defect Management Area (DMA), - a Reserved Package.

The GPA is located within the space logically to which the disk will be directed (see Fig. 2) at the end of the Program Area, immediately preceding the Departure Area. The Defect Management system will not be active in the GPA, so that there are no replacements of defective Packages in the GPA. The General Application Area (GAA) can be used for data storage that does not allow the Defects Administration to make replacements. Such as application programs or device drivers that can handle defect management. Or the support of multiple operating systems that use UDF or ISO 9660 files. Or support for multiple sources such as music / video playback. The size of the GAA is defined during disk formatting. It is allowed to specify a length = 0 for the GAA.

The Defect Management Area (DMA) consists of N Packs made for the replacement of defective Packages in the Data Area, a Sentinel Pack (STL), and the Secondary Defects Table (STD). The number of Replacement Packages N is defined during disk formatting. The SDT is made for use by CD-ROM drives and CD legacy recorders for Defect Management during reading. It is also a reinforcement in cases of failures in the MDT. The SDT is contained in a Package. The SDT will be preceded by a Sentinel Package. The contents of all 2K Blocks of the Sentinel Pack will be all zeros. The last GPA Package will be a Reserved Package. This Package will not be used for any purpose other than the use of File System.

The High Speed CD-RW Defect Management System is based on a Main Defect Table (a Package) located in the Entry Area, a Secondary Table of Defects, containing a copy of the DTM, in the Area of General Purposes and Replacement Packages in the General Purpose Area. Fig. 5 shows the location of the first MDT in the Entry area.

The Defect Management of a recorder only replaces the complete Packages, which are discovered to be defective during writing or reading. The detection of possible errors can be based on, for example, excessive servo signals, feedback of an "OPC in operation" during writing, or error flags of the error correction system during reading.

It can be updated to the MDT by a recorder each time a defect is detected. If the MDT is wearing out due to too many overwrites (or becomes defective for other reasons of failure), a new STL packet is created preceding the existing STL packet and then the old STL packet is overwritten by a new MDT packet. Fig. 6 shows the replacement of a defective MDT. The defective MDT package will be overwritten with a DT with the update count field configured for FFFFh, indicating that this table is no longer valid.

The SDT only needs to be updated when the disc is ejected from a recorder. If the SDT is wearing out due to too many overwrites (or becomes defective due to other failure reasons), a new STL packet is created preceding the existing STL packet and then the old STL packet is overwritten by a new SDT, which is illustrated with reference to Fig. 7. The defective SDT packet will be overwritten with a DT with the update count field configured for FFFFh, indicating that this table is no longer valid. The number of Replacement Packages will decrease by one and the Defect Tables will be adapted respectively.

Therefore, according to a characterization of the method of the invention, three Defects Tables are defined: - the Main Defects Table (MDT), located in the Entry Area, - the Secondary Defect Table (SDT), located in the General Purpose Area (GPA) and which is an exact copy of the MDT. In addition, according to a characterization of the method of the invention, a third Table of Defects is defined: - a Table of Temporal Defects (TDT). This DTT is created in place of the SDT, when an expulsion is requested before the Back-ground Formatting process has finished, which will be discussed later. All Defect Tables have the same display and after ejecting the disc from the recorder, they contain the same information. Each Table of Defects (DT) is contained in consecutive Blocks, said 4 Blocks are repeated 8 times to fill a complete Package. Fig. 8 shows the composition of a Defect Table Package. This repetition provides good protection against local disc defects (dust, scratches, etc.). The package must be filled consecutively, starting with DT 0, part 0 and ending with DT7, part 3.

The Defects Table contains a list of Packages, which have been determined to be defective during verification or during the use of the medium, and a list of Packages has been reserved for replacements. The Defective Package will be replaced linearly by a reserved Package as assigned in the Defects Table. The identification of defective packets can occur either during the read or write operation of the recorder.

Each 2K Block in the Defect Table Package will have the contents as defined in Fig. 9, which shows the Defect Table Display. The address method to be used for the Defect Management is in accordance with the Logical Block Numbering. With reference to Fig. 9, the specific bytes have the following content: Byte 0-2: Signature: These 3 bytes will be set to: 4D4454h, which represent the characters "MDT", in each Block of an MDT, 534454h, which represent the characters "SDT", in each Block of an SDT, 544454h, that represent the characters "TDT", in each Block of a TDT, Byte 3: version number: this byte will be set to OOh.

Byte 4.5: DT update count These bytes will indicate the total number of update operations in this Defects Table. This field will be set to OOOOh during the creation of the DT, and will be increased by one each time the DT is overwritten. If the DT Package is defective, this Package will be overwritten with a DT with the update count field set to FFFFh, indicating that this table is no longer valid.

Byte 6: DT number / DT part number The 4 most significant bits of this byte specify the DT number in the packet as a binary value 0-7- the least significant 4 bits of this byte specify the part number in the DT as a binary value 0-3.

Byte 7: parts of DT in use This byte specifies the number of parts (0-4) of the DT that actually contains valid DT Entries.

Byte 8,9: Number of DT Entries: These 2 bytes indicate the number of replacement entries in the DT (the total of all 4 parts). The value will be equal to the number of Replacement Packages in the Defect Management Area.

Byte 10-15: Reserved: these 6 bytes are reserved and will be configured to OOh.

Byte 16-18: Start of the General Purposes Area These 3 bytes will specify the Logical Block Number (LBN) of the first User Data Block of the first Package in the General Purposes Area. Byte 16 bit 7-4 are reserved and will be set to zero.

Byte 16, bit 7-4: Reserved bit 3-0: The LBN of the first GPA User Data Block Byte 17, bit 7-0: The LBN of the first GPA User Data Block Byte 18, bit 7-0: The LBN of the first GPA User Data Block Byte 19,20: Size of the Replacement Area These 2 bytes will specify the number of separate Packages for replacement of defective Packages.

Byte 21-23: Size of the General Application Area These 3 bytes will specify the number of separate packets for the storage of data that are not under the control of the Defect Management.

Byte 24,25: Disk Status These 2 bytes contain flags to indicate the disk's status. They can be used, for example, to track the formatting process in another plane [Back-ground].

Byte 24 Bit 7-5: Format Status Bit 4-1: Reserved and set to zero Bit 0: Dirty Disk Byte 24 Bit 7-0: Reserved and set to zero Formatting Status: Bit 7,6 = 00: disk not formatted, 01: disk partially formatted, 10: disk completely formatted by the user, 11: disk completely formatted by the manufacturer , Bit 5 was made to be used as a flag of "De-icing not ready", the details will be discussed in the following Bit 5 = 1: indicates that the disk has been recorded non-consecutively, and that there are blank areas between some recordings Bit 5 = 0: indicates that all Packages between the start of the Program Area and the last User Data recorded in the Data Area (see Fig. 2) have been recorded or formatted. Before ejecting a disk with bit 5 set to 1, the blank area (s) will be formatted.

Dirty Disc: Bit 0 was made to be used as a general "Power Failure Flag". It must be set to 1 in each write action and reset to 0 when the disk is closed and ejected in a normal way.

Byte 26-28: Last Written Address These 3 bytes will specify the Logical Block Number (LBN) of the first User Data Block of the last Package that has been recorded or formatted. Byte 26 bit 7-4 are reserved and will be set to zero.

Byte 26 bit 7-4: Reserved bit 3-0: The LBN of the first User Data Block of the last formatted packet Byte 27 bit 7-0: The LBN of the first User Data Block of the last formatted package Byte 28 bit 7-0: The LBN of the first User Data Block of the last formatted packet Byte 29-31: these 3 bytes are reserved and will be configured to OOh.

Byte 32-2047: The DT replacement entries Each DT Entry consists of 6 bytes. The first three bytes indicate a defective Package and the last three bytes identify the Replacement Package that has been assigned. The most significant bits of byte n and byte n + 3 are used to indicate the status of the replacement. The unused bytes will be set to OOh.

Byte n bit 7.6: Status 1 bit 5.4: Reserved 1 bit 3-0: The LBN of Defective Pack Byte n + 1 bit 7-0: The LBN of Defective Package Byte n + 2 bit 7-0: The LBN of Defective Package Byte n + 3 bit 7,6: Status 2 bit 5,4: Reserved 2 bit 3-0: The LBN Replacement Pack Byte n + 4 bit 7-0: The LBN Replacement Package Byte n + 5 bit 7-0: The LBN Replacement Package The LBN of Defective Package will be equal to the LBN of the first User Data Block in the defective Package that is to be replaced. The Replacement Package LBN shall be equal to the LBN of the first User Data Block in the Replacement Package, which is assigned to retain the replaced Package.

The Status and Reserved value can be defined as follows: Status 1: bit 7,6: = 00: the entry identifies a valid replacement, = 01: the entry identifies a defective Package that has not been recorded at its replacement address, = 10: The entry identifies a Replacement Package usable in future replacements, the Defective Package LBN will be set to zero, = 11: the entry identifies a Replacement Package not usable for future replacements, the Defective Package LBN is not specified.

Reserved 1: bit 5.4 set to 00 Status 2: bit 7,6: = 00: the original location was recorded with the same data as the replacement location, = 01: the original location may contain different data such as those of the replacement location, = 10: reserved, = 11: reserved.

Reserved 2: bit 5.4 set to 00 The DT Entries in the tables will be separated in ascending order as if each DT Entry were a single unsigned binary integer bit 48. There will be no hierarchical replacements: no LBN Replacement Pack will be equal to any Defective Pack LBN.

The following display of the Sentinel Packs will be explained with respect to Fig. 10 Each block K in the STL Pack will have the contents as shown in Fig. 10. Here the successive bytes have the following content: Byte 0-2: Signature These 3 bytes will be set to: 53544Ch, representing the characters "STL", in each Block of an STL, Byte 3: version number: this byte will be set to OOh Byte 4.5: STL update count These bytes will indicate the total number of update operations in this STL package. That field will be set to OOOOh during the creation of the STL, and will be incremented by one each time the STL is rewritten. If the STL Package is defective, this Package will be overwritten with an STL with the update count field set to FFFFh, indicating that this table is no longer valid.

Byte 6,7: Reserved: these 2 bytes are reserved and will be configured to OOh.

Byte 8-2047: Reserved: These 2040 bytes are reserved and will be configured to OOh.

As it is apparent earlier, each MDT / SDT / TDT is preceded by a Sentinel Pack (also referred to as a zero packet). This package can be used in an advantageous manner for storage of property information as copyright information. Information of this type stored in the Entry area, can not be read by the CD-ROM reader. On the contrary, an SDT is readable.

Next, the Defect Management procedure will be discussed.

At the start (the details will be discussed later) an MTD is created, which contains a TD Entry for each Replacement Package, with Status 1 = 10, the LBN of Defective Package configured to OOOOOh and Status 2 = 00. The Packages that were found to be defective during the reading of the recorder, can be indicated in the Table of Defects with Status 1 set to 01, and the LBN of Defective Package configured as the LBN of the first Block of User Data of the defective Package. If a Replacement Package itself is found to be defective, this is indicated by Status 1 = 11. The Defective Package LBN is not defined.

If an error is detected in a Package during reading, the unit may replace the Package, mark the Package for replacement, or ignore the error. If the defective Package is to be replaced or marked for replacement, the unit will assign the Replacement Package with Status 1 = 10 and lowest LBN. If you replace Package, then: - the original Package data will be recorded in the Package identified by the Replacement Package LBN. - the Status 1 field of the DT Entry will be set to 00, - the separation order of the Defects Table will be maintained, if the Package is marked for a subsequent replacement, then: - the Status 1 field of the TD Entry will be set to 01, - the order of separation from the Table of Defects will be maintained, - future reading requests will be met from the Package identified by the LBN of Defective Package, - future writing requests will be handled when writing to the Package identified by the LBN of the Replacement Package, when changing the Status 1 field to 00, and when updating the order of separation of the Table of Defects. Optionally you can also overwrite the original location. The Status 2 field will be set respectively.

Next the formatting in another plane [back-ground] will be explained in more detail. It will be considered as a fully formatted disk if the Entrance Area has been recorded, as much as possible of the Program Area and the Departure Area. The user data bytes in the 2K Blocks can contain relevant data or can be configured for test data (all bytes AAh). It will be considered as a partially formatted disk if at least the TDM has been recorded in the Entrance Area. The status of the disc will be indicated by the Disk Status and Last Written Address fields contained in the MDT. If compatibility with CD-ROM drives is required, then the disk will contain an Entry Area, an Exit Area and a Program Area with no blank areas between the Entry and Exit areas. Formatting is the process for achieving CD-ROM compatibility status. Formatting can be done in two different ways: When pre-formatting, which is the conventional way of formatting used by various storage media. After the pre-formatting process, the disk is already fully formatted. The User Data will usually consist of the following steps: - write Input Area, - write Data Area, - write Output Area, - check the Data Zone (optional) including the DMA update (they are present).

Formatting can also be done as: Formatting in another plane [back-ground], which is the formatting process that operates in the other plane during the use of the disc in a recorder. After the process of Formatting in Another Plane [Back-ground], the disk is already fully formatted. The User Data can be recorded on the disk during the process of Formatting in Another Plane [Back-ground]. The process of Formatting in Another Plane [Back-ground] consists of the following steps: - Start - De-icing - Completion - Closing of early expulsion (if applicable) - Re-opening of an ejected disk early - Verification Because the Pre-formatting process may be somewhat long, the Formatting in Another Plane [Back-ground] can be a more efficient solution in time for the user of the disk. During the process of Formatting in Another Plane [Back-ground] only a minimum amount of data will be recorded on the disk, after which the disk can be used by the application. A disc in which a process of Formatting in Another Plane [Back-ground] is active, can be formatted later by the CD recorder in the other plane during the moments when the application is not accessing the disc.

Next, it will be explained and started. When a blank disc is inserted into a recorder, a startup procedure is initiated on the host computer. This start creates an STL and an MDT at the end of the Entry Area, according to a set of parameters given by the host computer, such as: Start of GPA, Size of the Replacement Area, Size of the GAA. In general, the host computer also writes some initial File System Structures (FSS) on the disk. These File System Structures as well as the User Data can be placed anywhere in the space to which the disk will logically be directed. In the following examples it is assumed that the disk is initially recorded sequentially. As a result of the start procedure the next disk, as shown schematically in Fig. 11, will exist. Due to the very limited amount of data that will be recorded, the startup procedure will be completed in just a few seconds. Now the disk is ready for data storage and can be released for the application.

Next, the de-icing will be explained, with reference to Fig. 12, which shows the status of a disk after some de-icing and recording. De-icing is the process of recording all the Packages in the Program Area of the disk. During the de-icing phase, non-recorded areas will be filled with Packages containing 2K Blocks with all AAh bytes or with User Data when requested. The de-icing must be done by the unit itself, without any support from the host computer. During the time intervals when the unit is inactive, the De-icing process can proceed in the other plane. When the application or OS requests disk access, the De-icing process is suspended and disk control returns to the OS. The requested application that writes to blank areas will be registered by the unit and will not be overwritten by the De-icing process. The unit will keep records of all areas that have been recorded or de-iced.

In the following the completion will be described in more detail, with reference to Fig. 13, which shows the status of a disk after several completion steps. After the entire Data Area and General Purpose Area has been recorded or de-iced, the Entry and Exit Area is recorded. To be able to interrupt the recording of the Entry and Exit Area in writing / reading requests of the host computer, the Input area as well as the Output Area are written in variable Pack sizes. The Entry and Exit must be recorded continuously until the time of the interruption request, after which the recording stops when writing a Packet Termination (2 Blocks Run-out and a Partial Link Block). After the action requested by the guest has been completed, the writing on the Entry and Exit is summarized with a start of the Package (Partial Link Block and 4 Run-in Blocks) followed by the User Data Blocks. To prevent too much fragmentation in the Entry and Exit areas, each Package must have a size of at least 128 User Blocks. At the end of the finalization process the host computer overwrites the General Application Area with the required files, updates the File System Structures and creates additional File System Structures if needed (eg secondary UDP AVDP).

Next, the process of ejecting a disc from a recorder will be explained, with reference to Fig. 14 that shows an example of the final status of a disc. When the disc is ejected from the recorder, the MDT Package will be copied to the SDT Package.

. However, an early expulsion may be possible as explained hereinafter, with reference to Fig. 15, which shows an early ejection status of the disk. When the user presses the eject button on the unit, he expects the disc to come out in the shortest possible time. However, it also expects the disk to be "ROM-compatible". This means that the disk must have at least one Entry and Exit Area and no blank areas in the Program Area. If the process of Formatting in Another Plane [Back-ground] has not yet finished, the unit may decide to end the de-icing and the completion processes in the normal way. If the remaining formatting is going to take a long time to complete, then the unit may decide to close the disk in a temporary ROM-compatible manner, for which the following steps are needed (see Fig. 15): - the write requests / reading of the computer will be completed and the active de-icing process will be stopped, - if recordings have been made in blank areas, all blank areas until the last recorded packet will be de-iced, 1) Only Replacement Packages that are currently in use (indicated in the MDT with Status 1 = 00) are copied to the location immediately following the area reserved for temporary GAA. 2) A copy adapted from the MDT is placed as TDT (Table of Temporary Defects) next to the replaced Replacement Packages, along with an STL and a Reserved Package: - the signature on the copy will be set to 544454h - the DT Entries on the DTT will point to the temporary Replacement Packs, while the DT Entries on the MDT will not be changed (still pointed to the Replacement Packages on the final GPA), - the LWA (Last Written Address) in the MDT and TDT will be configured in the LBN of the first User Data Temporary Reserved Packet Block, - all other fields in the TDM and DTT will not be changed and will reflect the values of the final disk after the formatting has been completed in full, - if the SLT and / or the TDT can not be written correctly in the desired location, then the next 2 Packages will be used. The DTT will always be only one Package before the start of the Temporary Exit. 3) An Output Area of at least 30 seconds is recorded. If this Exit will overlap the recorded Packages in the General Purpose Area, then the normal De-icing and Completion processes will be terminated instead of applying this early expulsion procedure. 4) The Input Area is recorded, with subcode data according to the actual situation of the disc.

) The OS writes to the GAA immediately after the last Package has been de-iced or recorded, the temporary GAA will be the same size as the final GAA. 6) The OS updates the file system structures and writes the additional structures required, 7) If all the data to be stored in the GAA does not occupy all the Packages, then the remaining Packages are de-iced. 8) The DTT is updated, including the reset to 0 of the dirty disc bit, 9) The MDT is updated including the reset to 0 of the dirty disk bit.

Next, the re-opening and the early ejection disc will be discussed, with reference to Fig. 16, which shows a re-opening status of the disc. When an early eject disc is re-inserted into a recorder, this device will detect the "partially formatted" status and the host computer can initiate the continuation of the Formatting in Another Plane [Back-gound]. The De-icing will be restarted from the position indicated by the LWA pointer (see Fig. 15), then start overwriting the Temporary Exit Area. Proceed until the entire disk has been de-iced / finalized. Replacement Packages already present in the final GPA will not be overwritten. The temporary GPA is considered formatted. The file system links for the temporary GAA are invalid. New write requests can overwrite the temporary GPA. Before the next expulsion, the OS will update the File System Structures.

Finally, it is pointed out that although the invention has been described with reference to preferential characterizations thereof, it should be understood that these are not limiting examples. Therefore, several modification of this may be apparent to those skilled in the art, without departing from the vision of the invention, as defined in the claims. For example, a CD-RW can be replaced by a DVD-RW or something similar.

Next, a characterization of a computer data system comprising a computer and recording apparatus according to the invention will be described, with reference to Fig. 17. The recording apparatus 1 comprises means for receiving recording medium 2. to receive a removable recording medium 3. The recording medium 3 may be a disc of the type that can be read optically as a CD-RW, DVD-RAM or DVD-RW. The recording medium 3 is driven rotatably by the rotation means 4. An optical collection unit 5, which can be moved in a radial direction of the recording medium 3, optically writes detectable marks along a track spiral 8 in the recording medium 3 employing a light beam 6. For this purpose the recording medium 3 is provided with a suitable phase change material having different otic properties in crystalline or amorphous states. The heating with the light beam 6 can induce these states. The light beam 6 is modulated by the recording means 9 according to the digital information signals to be recorded. These digital information signals have been appropriately encoded by means of coding 10, using the EFM modulation and the CIRC error coding, as prescribed in the CD standards. The input means 11, which can employ suitable interface means, receive the digital information signals from a connected computer 12.

Alternatively, the digital information signals in the recording medium 3 can be read via the same optical collection unit 5, by means of suitable reading means 13. These are connected to the decoding means 14 to perform the decoding processes EFM and CIRO error correction The decoded and corrected signal is output, via the output means 15, which comprises a suitable interface circuit, to the computer 12. All the units are controlled by a control unit 16 connected to the media. memory 17, such as a non-volatile ROM. The control unit 16 may comprise a processing unit that operates according to a specific program loaded in the memory means 17, for the purpose of performing the method according to the invention, either independently or under the control of the computer 12. The computer 12 comprises an interface circuit 18 adapted to receive digital information signals from the recording apparatus 1 or to send digital information signals to the recording apparatus 1. The digital information signals may comprise, in addition to read signals from the recording medium 3 or to be recorded there, control signals from the computer 12 for controlling the recording apparatus 1. The interface circuit 18 is connected to an internal data and address bus 19 for the purpose of exchanging data and controlling signals with a hard disk drive 20, a RAM memory unit 21, a central processor unit 22 and a ROM memory unit 22. The computer 12 can be loaded with a suitable operating system and a device driver for operating the recording apparatus 1. In the case of a recording apparatus according to the invention, the recording apparatus 1 will play the largest parts of the method according to the invention itself, as the formatting in another Plane [Back-gound or administration of defects, without requiring excessive interaction with the computer12. In that case the computer 12 will only interact with the recording apparatus 1 in the case of writing request, reading or expulsion and the like. However, another characterization of the invention is obtained when the recording apparatus 1 is not adapted to independently perform the method of the invention, as in the case of a legacy CD-RW reader or a CD-ROM reader. In that case the computer 12 will have to use a dedicated device driver, loaded in the corresponding memory units of the computer 12, to control the recording apparatus 1 in such a way that at least the defect manager performs according to the method of the invention, said dedicated device driver can be obtained from the recording medium 3 itself or from other external means such as the Internet.

The invention can be implemented by either hardware or software, and those various "means" can be represented by the same hardware article. In addition, the invention lies in each novel feature or combination of features. It is also noted that the word "comprises" does not exclude the presence of other elements or steps other than those that were enlisted in a claim. Any reference sign does not limit the vision of the claims.

Claims (20)

CHAPTER CLAIMING Having described the invention, it is considered as a novelty and, therefore, the content is claimed in the following:
1. CLAIMS 1. A method for recording digital information signals on a recordable and removable disk as a recording medium, the method comprises the recording of user data within a program area of the disk and, before the removal of the disk outside the device recording, finalizing the disc with an input area and output area comprising control information, the method is characterized by, performing a start step after inserting a blank disc into the recording apparatus, the start step comprises recording control data in an input area said control data defines a general purpose area (GPA) within the program area of the disk and where after the disk is ready to record user data in an area and data remaining from the program area.
2. 2. A method according to claim 1, wherein the start step comprises the definition of a main defect table (MDT) in the input area adapted to contain a list of addresses of defect areas and replacement areas, and the definition of a defect management area (DMA) within said general purpose area (GPA) adapted to contain replacement areas for defect management.
3. 3. A method according to claim 2, wherein the start step comprises the definition of a general application area (GAA) within the general purpose area (GPA) adapted to contain application controllers adapted to handle defect management and / or support specific operating systems.
4. 4. A method according to claim 3, characterized by, replacing defect areas with replacement areas in the defect management area (DMA) and recording the addresses of defect areas and corresponding replacement areas in the table of main defects (MDT) in the entrance area.
5. 5. A method according to claim 2, wherein the start step comprises the definition of a sentinel area (STL) within the input area comprising test data adapted to be overwritten by a new main defect table when the table of Major defects (MDT) become defective.
6. 6. A method according to claim 1, wherein the start step is followed by a formatting step in another back-ground plane designed to perform when there is user data written on the disk, the formatting step in another plane [back-ground] comprises a step of de-icing which comprises the recording of test data in blank areas within the data area, said de-icing step being performed until the entire data area has been recorded with data test when it is not yet recorded with user data.
7. 7. A method according to claim 6, wherein the start step is to take place when the de-icing step has been completed, the completion step comprises: completing the recording of the entry and exit areas, recording the area of General application (GAA) with the required data if needed and record a copy of the main defect table (MDT) as a secondary defect table (SDT) in the general purpose area (GPA).
8. 8. A method according to claim 7, comprising an early ejection step to perform when the disc is ejected from a recorder before completing the completion step, the early ejection step comprises: completing the recording or reading requests, stopping one step of active de-icing and play only one de-icing step to de-ice all blank areas until the last recorded area with user data, record a temporary general purpose area next to the area with the latest data from user recorded or next to the de-iced area, copy replacement areas that are in use within the defect management area (DMA) to the area immediately followed by the temporary general application area, copy an adapted copy of the defect table main as a temporary defect table next to the copied replacement areas and record a temporary output area next to the temporary defect table and record the entrance area.
9. 9. A method according to claim 7, comprising a reopening step performed when an early ejection step has been performed, the re-opening step comprising: performance of the de-icing step for areas following the last recorded area before the temporary entry area.
10. 10. A method of reproducing digital information signals recorded on a rewritable and removable disk as a recording medium such as that obtained with a method according to claim 7, characterized by, performance of defect management using the table of secondary defects (SDT).
11. 11. A method of reproducing digital information signals recorded on a rewritable and removable disk as a recording medium such as that obtained with a method according to claim 7, characterized by, the performance of defect management employing the temporary defects table (TDT).
12. 12. A method according to claim 1, wherein the recording medium is of the optical type.
13. 13. A method according to claim 12, wherein the recording medium is a CD of the rewritable type and which is in a compatible CD-ROM state after completing the early ejection step.
14. 14. A recording apparatus for recording digital information signals in a rewritable and removable disk-type recording medium, the recording apparatus comprises, means for receiving the digital information signals, means for receiving recording medium to receive the medium removable, recording means for recording digital information signals in the removable medium, reading means for reading digital information signals recorded in the removable medium, output means for issuing read digital information signals, control means adapted to control signals of digital information representing user data in a program area in the recording medium, characterized in that, the control means are adapted to perform the method according to one of claims 1-9. 15. A recording apparatus according to claim 14, characterized in that, the control means are adapted to record status information of recording medium from a recording medium, the status information of recording medium comprises the status of format corresponding to an early ejection step or an end step, and to summarize the formatting step in another plane [back-ground] in case the half-read status information of a recording medium corresponds to a step of early expulsion.
15. 15. A recording apparatus according to claim 14, characterized in that the control means is adapted to register the areas that have been recorded or de-iced.
16. 16. A recording apparatus according to claim 14, characterized in that, the control means are adapted to store the address of the last recorded or de-iced area of the recording medium and to summarize the recording or de-icing of this area .
17. 17. A recording apparatus according to claim 14, characterized in that the control means is adapted to read digital information signals recorded in the recording medium according to the method of the claim.
18. 18. A computer data system comprising a computer connected to an apparatus for recording digital information signals in a rewritable and removable disk-type recording medium, the recording device comprising: means of entry connected to the computer to receive signals from digital information thereof, means for receiving recording medium to receive the removable medium, recording means for recording digital information signals recorded on the removable medium, reading means for reading recorded digital information signals, recorded on the removable medium, output means for issuing the digital information signals read to the computer, control means adapted to control digital recording information signals representing the user data in a program area in the recording medium, characterized in that, the computer is adapted to control the control means of the grading apparatus tion to perform the method according to one of claims 1-9.
19. 19. A computer data system comprising a computer connected to a reproduction apparatus for reproducing digital information signals recorded in a rewritable and removable disk-type recording medium, the reproduction apparatus comprising: means of receiving recording medium to receive to the removable medium, reading means for reading the digital information signals recorded on the removable medium, means of output for issuing the digital information signals read to the computer, control means for controlling the reading means and means of output, the control means are connected to the computer means, characterized in that, the computer is adapted to control the means of control of the reproduction apparatus to perform the management of defects using the secondary defect table (SDT) obtained in accordance to the method of claim 7 or using the temporary defect table l (TDT) obtained according to the method according to claim 8.
20. 20. A computer program product directly loadable in the internal memory of a digital computer, comprising portions of software code to perform the steps of one of claims 1-11 when said product is operated on a computer.