RU2303822C2 - Method for recording data on a data carrier - Google Patents

Abstract

FIELD: magneto-optical recording equipment engineering, primarily, minidisk system.

SUBSTANCE: recording method contains stages of: detection of unique information in record carrier outside the given zone, controlled by control data, which control data in data zone on record carrier; generation of unique information, when no unique information recorded on data carrier is found during detection stage; and recording of unique information, generated during generation phase, outside the zone controlled by control data.

EFFECT: expanded functional capabilities of magneto-optical disk with preserved compatibility with common minidisk system.

6 cl, 59 dwg

Description

FIELD OF THE INVENTION

The present invention relates generally to a recording method with enhanced functionality of a magneto-optical disc used in a conventional mini-disk (MD) system, while expanding capabilities while maintaining compatibility with a conventional mini-disk system.

State of the art

The so-called mini-disk (MD), which is a 64 mm diameter magneto-optical disc located in a cassette, is now widely recognized as a data carrier on which digital audio data can be recorded and from which it can be played.

The MD system uses ATRAC (adaptive conversion acoustic coding) as a method of compressing audio data. ATRAC includes encoding with compression of audio data using the so-called MDCT (modified discrete cosine transform). Sound data is received through the specified time window. Typically, music data is compressed using ATRAC to one fifth to one tenth of the original length.

The MD system uses a convolutional code called ACIRC (Advanced Reed-Solomon Cross-Intermittent Code) as an error correction system, and EFM (eight to fourteen modulation) as a modulation technology. ACIRC is a convolutional code that provides double error correction in the C1 and C2 sequences (in the vertical and inclined directions). The method is used for the process of strong error correction in serial data, such as audio data. The disadvantage of ACIRC is that it requires a communications sector for the purpose of updating data. ACIRC and EFM are basically the same as those used in a conventional compact disc (CD) system.

To manage music data in the MD system, U-TOC (User Content Table) is used. Namely, the U-TOC is located on the inside of the recordable area of the disc. In the existing MD system, the U-TOC forms a sequence of track names (audio track / data track) and control information that is updated to track the recording or erasure of such tracks. In the U-TOC scheme, control of each track (i.e., the parts forming each track) is performed with respect to the start position, end position and setting modes.

The disc for the MD system is small, inexpensive, and provides good performance when used in the system for recording or playing back audio data. These advantages have provided the MD system with widespread market acceptance.

However, according to the authors of this invention, MD systems have not fully reached the market potential because they are not compatible with general purpose computers, such as personal computers. In addition, conventional MD systems use different file management schemes than file based table file allocation (FAT) systems.

With an increase in the general use of personal computers and the use of a network based on a personal computer, more and more audio data is distributed through networks based on personal computers. Currently, it is common practice for a user to use a personal computer as an audio server from which selected music files are downloaded to a portable data playback device for playing music. According to the inventors of the present invention, since a conventional MD system is not fully compatible with personal computers, a new MD system that is capable of using a general-purpose control system such as a FAT system (file allocation table) to improve compatibility with a personal computer is desirable.

As explained, for example, in R. White's article "How Computers Work, Millenium Edition" by Que Corporation, 1999, pages 146 and 158, the entire contents of which are included in this description, a file allocation table (FAT) is created by a drive in a special sector of the disk such as sector 0. In this case, the concept of FAT (or FAT system) is used as a whole to describe various file systems based on a personal computer, and is intended to refer to special FAT-based file systems used in DOS, VFAT (virtual FAT) used on Windows 95/98, FAT 32 used on Windows 98 / ME / 200 0, as well as NTFS (the NT file system, sometimes the new technology file system), which is the file system used in the Windows NT operating system, or, optionally, in the Windows 2000 operating system to store and extract files from recording / playback discs. NTFS is the equivalent in Windows NT of the file allocation table (FAT) in Windows 95 and the high-performance file system (HPFS) in OS / 2.

At the same time, a higher degree of compatibility with personal computers means an increased risk of unauthorized copying of copyrighted works, which, in turn, makes more reliable technology necessary to protect sound works from unauthorized copying. One of the copyright protection technologies involves encoding sound works when recording them. It is also desirable to provide more efficient management of musical names and artist names recorded on the disc than at present.

In the existing MD system, a disk with a memory capacity of about 160 MB is used, which, according to the authors of this invention, is insufficient for the requirements of users for data storage. Thus, it is desirable to increase the memory capacity of the new disk while maintaining compatibility with the existing MD system.

SUMMARY OF THE INVENTION

The objective of the invention is to overcome the above and other disadvantages of the prior art and to create a recording method for efficiently managing audio data by integrating the FAT system into the MD medium. Alternatively, other media formats may also be used.

Although the following are the main aspects of the invention, which should not be construed as a complete list of all the new features and combinations of features of this invention. Also, they should not be considered in isolation from other aspects of this description.

According to one embodiment of the invention, the recording method comprises the steps of detecting unique information on a recording medium outside a predetermined area controlled by control data that controls data in a data area on a recording medium; generating unambiguous information when unambiguous information recorded on the recording medium is not detected in the detection stage; and recording unambiguous information generated at the generation stage, outside the area controlled by the control data.

In addition, the method may further comprise the step of generating unique information when the detection stage has found that the unique information is not recorded on the recording medium.

Also, the recording medium may include a control table configured to control a replacement zone for the damaged zone in the data zone in the recording medium; and the method may further comprise the step of writing unique information to the control table.

Another feature of the first embodiment of the present invention is that the method may further comprise the steps of reading a unique identifier from the recording medium and temporarily storing unique information in memory; and writing the unique information stored in the memory to the control table when the unique information is recorded in a predetermined place on the recording medium or control table.

According to another feature of the first embodiment of the present invention, the method further comprises the step of recording unique information upon initialization of the recording medium.

According to yet another feature of the first embodiment of the present invention, the method further comprises the step of managing data in a data area on a recording medium using a file allocation table system, wherein the management data includes a file allocation table.

According to the present invention, a track information file and an audio data file are created on a disk serving as a data medium. These files are files managed by the so-called FAT system.

An audio data file is a file that contains a plurality of audio data elements. From the point of view of the FAT system, the audio data file seems to be a very large file. The composition of this file is divided into parts, so that audio data is treated as a set of such parts.

A track information file is a file that describes various types of information for managing audio data contained in an audio data file. The track index file consists of a play order table, a programmable play order table, a part information table, a track information table, a part information table, and a name table.

The playback order table indicates the default audio playback order. Thus, the playback order table contains information that represents links to track descriptors corresponding to track numbers (i.e., music numbers) in the track information table.

The table of programmable playback order contains the playback order of audio data specified by an individual user. Thus, a programmable play order table describes programmable track information representing links to track descriptors corresponding to track numbers.

The group information table describes group information. A group is defined as a set of one or more tracks having track numbers, or a set of one or more tracks with programmable track numbers.

The track information table describes information about tracks representing musical compositions. Namely, the track information table consists of track descriptors representing the tracks (music). Each track descriptor describes a coding system, copyright management information, content decryption key information, pointer information indicating a number of a part serving as input to a musical work of a given track, artist name, title of a work, information of the original work order and recording time information for a given tracks.

The parts information table describes pointers that provide indication of the location of the current piece of music using part numbers. Namely, the part information table consists of part descriptors corresponding to the individual parts. Parts descriptor entries are specified by a track information table. Each part descriptor consists of the beginning address and the end address of this part in the audio data file and communication with the next part.

When it is desired to reproduce audio data from a particular track, information about the designated track is retrieved from the playback order table. Then, a track descriptor corresponding to the track from which audio data is to be played is obtained.

Then, from the used track descriptor in the track information table, key information is obtained and a part descriptor is obtained indicating a zone containing input data. From the part descriptor, access is made to a place in the audio data file of the first part containing the desired sound data, and data is extracted from the place to which access is obtained. The data reproduced from this place is decrypted using the obtained key information for reproducing audio data. If the part descriptor is associated with another part, then access to the associated part and repeat the above stages.

Brief Description of the Drawings

These and other objects of the invention follow from the description below with reference to the drawings, in which:

figure 1 depicts a disk for use in the next generation MD1 system;

figure 2 - recordable area in the disk for use in the next generation MD1 system;

figa and 3B is a disk for use in the next generation MD2 system;

4 is a recordable area of the disc for use in the next generation MD2 system;

5 is a diagram of an error correction code for use in next-generation MD1 and MD2 systems;

6 is another diagram of an error correction code for use in next-generation MD1 and MD2 systems;

7 is another diagram of an error correction code for use in next generation systems MD1 and MD2;

Fig. 8 is a part of a disk showing generation of an address signal using swings, in isometric view;

Fig.9 - ADIP signal for use in the existing MD system and in the next generation MD1 system;

10 is another ADIP signal for use in an existing MD system and in a next generation MD1 system;

11 is an ADIP signal for use in the next generation MD2 system;

12 is another ADIP signal for use in a next generation MD2 system;

Fig. 13 shows the relationship between an ADIP signal and frames for an existing MD system and a next generation MD1 system;

Fig. 14 shows the relationship between the ADIP signal and frames for the next generation MD1 system;

Fig - control signal for use in the next generation MD2 system;

Fig is a block diagram of a block drive;

Fig is a block diagram of a drive block of the media;

Fig is a graphical diagram of the stages of initialization of the disk MD1 next generation;

Fig. 19 is a graphical diagram of the steps for initializing the next generation MD2 disc;

Fig - a bit array of recording signals;

Fig is a graphical diagram of the stages of reading data from the FAT sector;

Fig is a graphical diagram of the steps of writing data to the FAT sector;

Fig is a graphical diagram of the stages in which the drive unit alone reads data from the FAT sector;

Fig is a graphical diagram of the stages in which the drive unit alone writes data to the FAT sector;

Fig is a graphical diagram of the stages for generating a bitmap of recording signals;

FIG. 26 is another graphical diagram of steps for generating a bitmap of recording signals; FIG.

Fig. 27 is another graphical diagram of steps for generating a bitmap of recording signals;

FIG. 28 is a first embodiment of an audio data management system; FIG.

Fig. 29 is an audio data file for use in a first embodiment of an audio data management system;

FIG. 30 is a track index file for use in a first embodiment of an audio data management system; FIG.

Fig. 31 is a table of a playback order for use in a first embodiment of an audio data management system;

Fig - table of the programmed playback order for use in the first embodiment of the audio data management system;

33A and 33B are a group information table for use in a first embodiment of an audio data management system;

Figa and 34B is a table of track information for use in the first embodiment of the audio data management system;

figa and 35B is a table of information of parts for use in the first embodiment of the audio data management system;

Figa and 36B is a table of names for use in the first embodiment of the audio data management system;

Fig. 37 is a typical process carried out in a first embodiment of an audio data management system;

Fig. 38 shows a process of accessing each position of a name in a table of names using a plurality of pointers;

figa and 39B is a process performed in the first embodiment of the audio data management system, to erase parts of the audio data file;

40 is a second embodiment of an audio data management system;

Fig. 41 is an audio data file for use in a second embodiment of an audio data management system;

Fig. 42 is a track index file for use in the second embodiment of the audio data management system;

Fig. 43 is a table of a playback order for use in a second embodiment of an audio data management system;

Fig - table of the programmed playback order for use in the second embodiment of the audio data management system;

45A and 45B are a group information table for use in a second embodiment of an audio data management system;

Figa and 46B is a table of track information for use in the second embodiment of the audio data management system;

Figa and 47B is a table of names for use in the second embodiment of the audio data management system;

48 is a typical process performed in a second embodiment of an audio data management system;

Fig. 49 shows a process performed in a second embodiment of an audio data management system for dividing an audio data element into a plurality of indexed zones using an index scheme;

FIG. 50 is a process performed in a second embodiment of an audio data management system for connecting tracks using an index scheme; FIG.

51 is a process performed in a second embodiment of an audio data management system for connecting tracks using a different circuit;

Figa and 52B is a process of moving control authority between a personal computer and a drive unit connected to a personal computer, depending on the type of data to be written to the disk installed in the drive unit;

figa, 53B and 53C - the procedure for copying audio data;

Fig - conceptual compatibility of the next-generation MD1 system and the existing MD system in the drive unit;

55 is an external view of a portable drive unit;

Fig. 56 is a graphical diagram of the steps performed in a portable drive unit when formatting a disk installed therein;

Fig. 57 is a graphical diagram of the steps performed in a portable drive unit when formatting a blank disc installed therein;

Fig. 58 is a graphical diagram of the steps performed in a portable drive unit when recording audio data to a disc mounted therein; and

FIG. 59 is a flow chart of steps for switching from a next-generation MD1 system disk format to an existing MD system disk format.

Description of Preferred Embodiments

The following description is divided into the following 10 sections:

1. Scheme recording system

2. Disks

3. Signal formats

4. The structure of the recording / reproducing device

5. Initialization of next-generation MD1 and MD2 drives

6. The first example of a sound data management system

7. Second example of an audio data management system

8. Work during connection with a personal computer

9. Restrictions on copying audio data from disk

10. Next Generation MD1 System Compatibility with Existing MD System

1. Scheme recording system

In the recording / reproducing apparatus according to the present invention, a magneto-optical disc is used as a data carrier. Physical features of the disc, such as the form factor, are essentially similar to the disc used in the so-called MD systems (minidisk). However, the data recorded on the disc and the location of the data on the disc are different from a regular minidisk. In particular, the device according to the invention uses the FAT system (file allocation table) as a file management system for recording or reproducing content data, such as audio data, with compatibility with existing personal computers. The term “FAT” (or “FAT system”) is used in this case as a whole to describe various file systems based on a personal computer, and is intended to describe the special FAT structure used in DOS, VFAT (virtual FAT) used in Windows 95 / 98, FAT 32 used in Windows 98 / ME / 2000, as well as NTFS (NT file system, sometimes a new technology file system), which is a file system used in the Windows NT operating system, or, optionally, in the operating system Windows 2000 for storing and extracting files from read drives i / records. Compared with a conventional MD system, the recording / reproducing apparatus according to the invention has an improved error correction system and an improved modulation technology configured to increase the storage capacity of the data and to increase data protection. In addition, in the device according to the invention, the content data is encrypted, and measures are also taken to prevent illegal copying of the data and to protect copyright of the content data.

In general, there are two kinds of specifications, MD1 and MD2, developed by the present inventors for the next generation MD system. MD1 specifications include the use of the same drive (i.e. physical media) as the drive currently used in the existing MD system. MD2 specifications include the use of a disc that has the same form factor and is outwardly identical to the disc for the existing MD system, but which uses magnetic super resolution (MSR) technology to increase the recording density in the linear direction, thereby increasing storage capacity.

In the existing MD system, a magneto-optical disk with a diameter of 64 mm, closed in a cassette, is used as a data carrier. This disk has a thickness of 1.2 mm and has a central hole with a diameter of 11 mm. The cassette has a size of 68 mm by 72 mm by 5 mm.

The size and shape of the discs and cassettes remain the same on the next-generation MD1 and MD2 systems. In both MD1 and MD2 discs, the initial position of the input zone is the same as in the existing MD system, i.e. starts at 29 mm.

For the next-generation MD2 system, track spacing is exclusively provided in the range of 1.2 μm to 1.3 μm (e.g., 1.25 μm). For the next-generation MD1 system, the disk of which is identical to the disk of the existing MD system, the track spacing is set to 1.6 μm. The bit length is set to 0.44 μm / bit for the MD1 disk and is proposed to be 0.16 μm / bit for the MD2 disk. For both next-generation MD1 and MD2 drives, the redundancy is set at 20.50%.

The next generation MD2 is designed to increase storage capacity in the linear direction through the use of magnetic super resolution (MSR) technology. MSR technology takes advantage of the special effect on the disk that the through layer becomes magnetically neutral when a specific temperature is reached, which allows the magnetic walls to be transported to the regenerative layer to move, so that infinitesimal marks are detected as large under the influence of a spot of light.

That is, the next generation MD2 disc consists of a recording layer for recording at least data, a through layer and a magnetic layer for regenerating data, which are all located on a transparent substrate. The end-to-end layer serves as a layer that regulates the switched connecting force. When a specific temperature is reached, the through layer becomes magnetically neutral, providing a shift of the magnetic walls transferred to the recording layer into the regenerative magnetic layer. This leads to the fact that infinitesimal marks become visible under the influence of a spot of light. To record data, modulation technology using a magnetic field and laser pulses is used to create lowercase marks on the disk.

On the next-generation MD2, the grooves are deeper than on a regular MD, and their slope is also steeper to increase track margins and reduce crosstalk caused by the pad, crosstalk from signal wobble and defocus. For example, in the next generation MD2 disc, the grooves have a depth exclusively in the range of 160 nm to 180 nm, the groove slope is exclusively in the range of 60 degrees to 70 degrees, and the groove width is exclusively in the range of 600 nm to 700 nm.

As part of its optical characteristics, the next-generation MD1 disk has a laser wavelength λ of 780 nm and a numerical aperture NA of the objective lenses in the optical head of 0.45. Similarly, the next-generation MD2 disk has a laser wavelength λ of 780 nm and a numerical aperture NA of the objective lenses in the optical head of 0.45.

Both next-generation MD1 and MD2 systems use the so-called groove recording system as their recording circuit. That is, grooves are formed on the surface of the disc in the form of tracks for recording and reproduction.

As an error correction code system, the existing MD system uses a convolution code based on ACIRC (Advanced Reed-Solomon Cross-Interleaved Code). In contrast, next-generation MD1 and MD2 systems use block full code that combines RS-LDC (long Reed-Solomon code) and BIS (burst indicator subcode). Using a blocky complete error correction code eliminates the need for tie sectors. In an error correction scheme combining LDC and BIS, the location of a possible burst error is detected using BIS. The error location is used to apply the LDC code to perform erasure correction.

As the address system, the so-called track swing system is used, due to which a single spiral track is formed, and swing elements are made on both sides of the track as address information. This address system is called ADIP (address in the pre-groove). The existing MD system and the next generation MD1 and MD2 systems are characterized by linear density. While a convolutional code called ACIRC is used as the error correction code in the existing MD system, the next generation MD1 and MD2 systems are designed to use block full code combining LDC and BIS. As a result, the existing MD system and the next generation MD1 and MD2 systems are redundant and have different relative positions between ADIP and data. For this reason, the next-generation MD1 system, whose physical disk is structurally identical to the disk of the existing MD system, processes the ADIP signal differently from the existing MD system. The next-generation MD2 system is configured to modify the characteristics of its ADIP signal to better match the characteristics of the next-generation MD2 minidisk.

The existing MD system uses EFM (8 by 14 modulation) as a modulation system, while the next-generation MD1 and MD2 systems use the RLL (1, 7) PP method (limiting the distance between parity control of preservation / prohibition of repeated minimum transitions) , called in the subsequent modulation system 1-7 pp. In the MD1 and MD2 systems, the Viterbi decoding method is used as a data detection method based on the partial response PR (1, 2, 1) ML for the MD1 system and the partial response PR (1, -1) ML for the MD2 system.

The drive system uses CLV (constant linear velocity) or ZCAV (constant angular velocity zone). The standard linear velocity is set at 2.4 m / s for the next-generation MD1 system and 1.98 m / s for the next-generation MD2 system. In the existing MD system, the standard linear velocity is set to 1.2 m / s for a 60-minute disc and 1.4 m / s for a 74-minute disc.

In the next-generation MD1 system, the drive of which is structurally identical to the drive of the existing MD system, the total storage capacity of the drive data is about 300 megabytes (for an 80-minute drive). Since a modulation system of 1-7 pp is used as modulation instead of EFM, the window fields are changed from 0.5 to 0.666, due to which the recording density is increased by 1.33 times. Since, as an error correction system, the ACIRC system is replaced by a combination of DIS and LDC, the data efficiency increases, due to which the recording density is additionally increased by 1.48 times. In general, when using the same disk, the storage capacity is approximately doubled compared to the existing MD system.

The next-generation MD2 disc using magnetic superresolution technology has further increased the recording density in the linear direction; total storage capacity is about one gigabyte.

At a standard linear speed, the data rate is set to 4.4 Mbps for the next-generation MD1 system and 9.8 Mbps for the next-generation MD2 system.

2. Disks

1 shows a typical structure of a next-generation MD1 disk. This disk is identical in structure to the disk of an existing MD system. That is, the disk is made of a dielectric film, a magnetic film, another dielectric film and a reflective film located on a transparent polycarbonate substrate. The surface of the disc is covered with a protective film.

In the next-generation MD1 disc, as shown in FIG. 1, the input zone on the innermost side (the recording area, the “innermost” refers to the radial direction, relative to the center of the disc) has a P-TOC zone (mock up table of contents). As a physical structure, this zone forms a zone for creating the layout of the original disk. That is, indented pits are formed here to record control information and other relevant information, such as P-TOC information.

On the other hand, in the radial direction, the input zone including the P-TOC zone is a recordable zone where magneto-optical recording is possible. It is both a recordable and reproducible area including recording tracks provided with grooves as guides. On the inside of the recording area is the U-TOC zone (user table of contents).

The U-TOC zone is the same in structure as in the existing MD system in which disc management information is recorded. In the U-TOC zone, there is a track naming order (audio track / data track) and overwritten control information to track the recording and erasing of such tracks. Namely, the control information includes the positions of the beginning and end of the tracks (i.e., the parts making up the tracks) and setting modes.

A warning track is made on the other side of the U-CBT zone. This track contains a warning sound recorded in it, which is activated (made audible) by the MD player if the disc is installed in an existing MD system. The sound warns that the disc is intended for use in the next-generation MD1 system and cannot be used for playback in an existing system. The rest of the recording zone (shown in more detail in FIG. 2) in the radial direction is followed by the output zone.

Figure 2 shows a typical structure of the recording area of the next-generation disc MD1 shown in figure 1. As shown in FIG. 2, at the beginning of the recording zone (inner side), there is a U-TOC zone and a warning track. In the zone containing the U-TOC zone and the warning track, the data is recorded in EFM format so that the data can be played back using the players of the existing MD system. On the other side of the zone of data stored in the EFM format, there is a zone in which data is recorded in modulation format 1-7 pp for the next-generation MD1 system. There is a gap of a given length, called a "protective strip", between the recording area in the EFM format, on the one hand, and the data storage zone in the modulation format 1-7 pp - on the other hand. The protective strip is designed to prevent the malfunctioning of an existing MD player when the next-generation MD1 system drive is installed in it.

At the beginning of the data recording zone in modulation format 1-7 pp (i.e., on the inside) there is a DDT zone (disk description table) and a backup track. The DDT zone is designed to replace physically damaged areas and includes a unique identifier (UID). A unique identifier is unique to each storage medium, usually based on randomly generated numbers. A backup track is provided for posting information to protect content.

In addition, the data storage zone in modulation format 1-7 pp includes the FAT zone (file allocation table). The FAT zone is a zone that allows the FAT system to manage data according to the criteria of the FAT system used in general purpose computers. Namely, the FAT system manages files based on FAT chains containing both a directory indicating the entry points of root files and directories, and a FAT table indicating the communication information of FAT clusters. The concept of FAT is used in a general sense to refer to many different file management schemes used in personal computer operating systems.

In the U-TOC zone of the next generation MD1 disc, two types of information are recorded: the position of the beginning of the warning track and the position of the beginning of the zone for storing data in modulation format 1-7 pp.

When the next-generation MD1 disc is installed in the next-generation MD1 player, information is read from the U-TOC zone of the installed disc. The extracted U-TOC information indicates the position of the warning track, which provides access to the warning track, so that playback of its data may begin. A warning track contains data that makes an audible warning that the disc is for the next-generation MD1 system and cannot be used for playback in an existing system.

The warning sound may, for example, contain a spoken message, such as "This disc cannot be used in this player." Alternatively, the warning sound may be a simple buzzer, tone, or other warning signal.

When the next-generation MD1 disc is installed in the next-generation MD1 player, information is read from the U-TOC of the installed disc. The extracted U-TOC information shows the position of the beginning of the zone in which the data is stored in modulation format 1-7 pp, and provides read data from the DDT zone, the backup track and the FAT zone. Management of the data storage zone in the modulation format 1-7 pp is carried out not using U-TOC, but using the FAT system.

3A and 3B show a typical structure of a next-generation MD2 disk. This disk is also made of a dielectric film, a magnetic film, another dielectric film and a reflective film located on a transparent polycarbonate substrate. The surface of the disc is covered with a protective film.

In the next generation MD2, as shown in FIG. 3A, the input area on the inside (in the radial direction) has control information recorded using the ADIP signal. In the MD2 disk, the currently used P-TOC zone of the indented pits is replaced by an input zone having control information based on an ADIP signal. The recordable zone starting from the outside of the input zone is both a recordable and reproducible zone having grooves made therein as guides for the recording tracks. The recorded zone has data recorded in modulation format 1-7 pp.

In the next generation MD2, as shown in FIG. 3B, the magnetic film is formed of a magnetic layer 101 serving as a layer for recording data, a through layer 102 and a magnetic layer 103 for regenerating data all located on a substrate. An end-to-end layer 102 serves as a layer that regulates a switchable connecting force. When a specific temperature is reached, the through layer 102 becomes magnetically neutral to provide a shift of the magnetic walls transferred to the recording layer 101 to the regenerative magnetic layer 103. This provides an apparent increase in infinitesimal marks in the recording layer 101 under the influence of a beam spot on the regenerative magnetic layer 103.

Whether the installed disc is a next generation MD1 disc or a next generation MD2 disc can be determined based on information retrieved from the input area. Namely, if P-TOS information in the form of indented pits is detected in the input zone, this means that the disk is a disk of an existing MD system or a next-generation MD1 disk. If the control information based on the ADIP signal is detected in the input zone, and the P-TOS information in the form of indented pits is not detected, this means that this disk is the next generation MD2 disk. However, the invention is not limited to this method of distinguishing an MD1 disc from an MD2 disc. As an alternative solution, to determine the type of disc, you can use phase differences in the signal tracking error between the modes of being in the track and offset relative to the track. As another alternative, the disc may have a hole for disc identification purposes.

4 shows a typical structure of a recordable area in a next-generation MD2 disc. As shown in FIG. 4, all data of the recording area is recorded in a modulation format of 1-7 pp. The DDT zone and the backup track are located at the beginning (i.e., on the inside) of the zone where the data is recorded in modulation format 1-7 pp. A DDT zone is provided for recording alternative zone control data to replace physically damaged zones. In addition, the DDT zone includes a management table that controls the replacement zone, which includes a recordable zone that replaces physically damaged zones. The management table monitors logical clusters that are identified as damaged, and also monitors logical clusters in the replacement zone for replacing physically damaged clusters. The DDT zone also contains the unique identifier (UID) above. The backup track stores information for content protection purposes.

The FAT zone is also located in the zone whose data are recorded in modulation format 1-7 pp. The FAT zone is used by the FAT system to manage data. In this embodiment, the FAT system performs data management in accordance with the criteria of the FAT system applicable to general purpose personal computers.

The next generation MD2 does not have a U-TOC zone. When a next-generation MD2 disc is installed in a next-generation MD2 player, data is read from the DDT zone, the backup track, and the FAT zone located in this manner on the disk. The extracted data is used by the FAT system to manage the data.

Next-generation MD1 and MD2 drives do not require a time-consuming initialization process. Namely, for these disks, the initialization process is not required, except for the preliminary preparation of the DDT zone, the backup track and the minimum set of tables, including the FAT table. Data can be directly recorded in the recordable area of an unused disc and then read from it without resorting to the initialization process.

3. Signal formats

The following is a description of the signal formats for the next-generation MD1 and MD2 systems. The existing MD system uses a convolutional code called ACIRC as an error correction system in which a sector of 2352 bytes corresponding to the data size of a sub-code block is considered as an access increment for read and write operations. Since the convolutional code scheme includes an error correction code sequence spanning several sectors, it is necessary to provide a connecting sector between adjacent sectors where data needs to be updated. As the addressing system in the existing MD system, a track sway circuit called ADIP is used, in which a single spiral track is formed, and both sides of the track have swings made as address information. In the existing MD system, the ADIP signal is optimally positioned to gain access to a sector of 2352 bytes.

In contrast, next-generation MD1 and MD2 systems use a full block code scheme in which LDC and BIS are combined and in which a 64-kbyte block is considered as an access increment for read and write operations. The complete block code does not need connecting sectors. However, for this it is necessary that the next-generation MD1 system using the disc of the existing MD system regroups the ADIP signal in accordance with the new recording method. The next generation MD2 system is configured to change the characteristics of the ADIP signal in accordance with the characteristics of the next generation MD2 system.

5, 6 and 7 show an error correction system for use in next-generation MD1 and MD2 systems. In this error correction system, the LDC-based error correction code scheme shown in FIG. 5 is combined with the BIS scheme shown in FIGS. 6 and 7.

5 shows a typical structure of a code block in an LDC-based error correction code scheme. As shown in FIG. 5, each sector of the error correction code is provided with an error detection code (EDC) of four bytes, and the data is located two-dimensionally in the error correction code block, which has a horizontal length of 304 bytes and a vertical length of 216 bytes. Each sector of the error correction code consists of 2 KB of data. As shown in FIG. 5, an error correction code block with a size of 304 bytes per 216 bytes includes 32 sectors of an error correction code, each 2 kb of data. The 32 sectors of the error correction code filling the block of the error correction code with a size of 304 bytes by 216 bytes are vertically equipped with a 32-bit Reed-Solomon error correction parity.

6 and 7 show a typical BIS structure. As shown in FIG. 6, a 1 byte BIS is inserted in 38 byte data intervals. One frame consists of 152 (38 × 4) bytes of data, BIS data of 3 bytes in length, and frame synchronization data of 2.5 bytes in length and has a length of 157.5 bytes.

As shown in FIG. 7, the BIS block is composed of 496 frames, each of which has the above structure. The BIS data code (3 × 496 = 1488 bytes) includes 576 bytes user control data, a 144 byte block address number, and 768 bytes error correction code.

As mentioned above, the BIS code has an error correction code of 768 bytes in length attached to data of 1488 bytes in length. This code structure provides enhanced error correction. Using this BIS code embedded in 38-byte data intervals, you can easily locate possible errors. Then the error location is used for erasure correction using the LDC code.

The ADIP signal is recorded as swings formed on both sides of a single spiral groove, as shown in FIG. That is, the ADIP signal is recorded by frequency modulating the address data and embedding the grooves in the disk material.

Figure 9 shows a typical sectorial ADIP signal format for the next generation MD1 system.

As shown in FIG. 9, each ADIP signal sector (ADIP sector) consists of 4-bit synchronization data, eight high-order bits of the ADIP cluster number, eight low-order bits of the ADIP cluster number, eight bits of the ADIP sector number, and 14 bits of cyclic redundancy error detection code code (CRC).

The synchronization data constitutes a predetermined signal used to detect the start of an ADIP sector. In the existing MD system, link sectors are needed because this system uses convolutional code. Sector numbers for binding purposes are negative sector numbers for FCh, FDh, FEh, and FFh (h: hexadecimal). The ADIP sector format is the same as in the existing MD system, since the next generation MD1 system uses the same drive as the existing MD system.

The next generation MD1 system, as shown in FIG. 10, has an ADIP cluster structure formed by 36 ADIP sectors from FCh to FFh and from 0Fh to 1Fh. And, as shown in FIG. 10, one ADIP cluster consists of data constituting two recording blocks of 64 kB each.

11 shows the structure of ADIP sectors for use in the next generation MD2 system. This structure contains 16 ADIP sectors, so the number of each ADIP sector can be expressed in four bits. The MD2 system does not require connecting sectors, since the system uses the complete block error correction code.

As shown in FIG. 11, the structure of the ADIP sectors for the next-generation MD2 system includes 4 bits of synchronization data, four high bits of the ADIP cluster number, eight middle bits of the ADIP cluster number, four low bits of the ADIP cluster number, four bits of the ADIP sector number and 18 bits error correction parity code.

The synchronization data constitutes a predetermined signal used to detect the start of an ADIP sector. The ADIP cluster number consists of 16 bits, i.e. 4 high bits, 8 middle bits and 4 low bits. Since 16 ADIP sectors form one ADIP cluster, the number of each ADIP sector is specified by four bits. While the existing MD system uses an error detection code of 14 bits, the next generation MD2 system uses an error correction parity code of 18 bits. In the next generation MD2 system, as shown in FIG. 12, each ADIP cluster is equipped with one 64 kbyte write unit.

13 shows the relationship between an ADIP cluster and BIS frames for a next-generation MD1 system.

As shown in FIG. 10, one ADIP cluster consists of 36 ADIP sectors from FC to FF and from 00 to 1F. A 64-kbyte write block, which is an increment for read and write operations, is made up of two parts in each ADIP cluster.

Each ADIP sector is divided into two parts, i.e. 18 clusters of the first half and 18 sectors of the second half, as shown in Fig.13.

The data in one write block, which constitutes an increment for read and write operations, is located in a BIS block made up of 496 frames, from frame 10 to frame 505. The data of 496 frames that make up the BIS block is preceded by the introduction of 10 frames from frame 0 to frame 9 In addition, the data frames are followed by a conclusion of 6 frames from frame 506 to frame 511. Thus, a total of 512 data frames are placed in each first and second half of the ADIP cluster, with the first half ranging from the ADIP sector FCh to the ADIP sector 0Dh , and the second half - from the ADIP 0Eh sector a sector ADIP 1Fh. Introduction and conclusion are provided to protect data after connecting to adjacent recording blocks. Intro frames are also used to organize PLL data, control the amplitude of the signals, and control the shift of the signals.

The physical address used to record or play back data to or from this recording unit is indicated in two parts: the ADIP cluster and the first half or second half of the cluster. When the physical address for the write or read operation is indicated, the ADIP sector is first read from the corresponding ADIP signal. From the reproduced ADIP sector signal, the ADIP cluster number and the ADIP sector number are extracted to determine the first half or second half of the ADIP cluster.

On Fig shows the relationship between the ADIP cluster and BIS frames for the next generation MD2 system. In the next generation MD2 system, as shown in FIG. 12, 16 ADIP sectors comprise one ADIP cluster. Each ADIP cluster is equipped with a 64 kB data recording unit.

As shown in FIG. 14, data in one write block (64 kB) constituting an increment for read and write operations is located in a BIS block made up of 496 frames arranged in order from frame 10 to frame 505. The entry is preceded by 496 frames of 10 frames from frame 0 to frame 9. In addition, the data frames are followed by a conclusion of 6 frames from frame 506 to frame 511. In total, there are 512 data frames in the ADIP cluster from ADIP 0h to ADIP Fh.

Entry and conclusion frames before and after data frames are provided to protect data after connecting to adjacent recording blocks. Intro frames are also used to organize PLL data, control signal amplitude, and control signal shift.

The physical address used to record or play back data to or from a disc with the above structure is indicated as an ADIP cluster. When a physical address is designated for a write or read operation, the ADIP sector is first read from this ADIP signal. The ADIP cluster number is then extracted from the reproduced ADIP sector signal.

To start writing or reading data to or from a disk, it is necessary to use various kinds of control information for calibrating the laser power and for other purposes. As shown in FIG. 1, the next generation MD1 disk has a P-TOC zone included in the input zone. From the P-TOC zone, various control information elements are obtained.

The R-TOS zone in the form of extruded pits is not provided in the next-generation MD2 disk; instead, control information is recorded using the ADIP signal in the input area. Since next-generation MD2 uses magnetic superresolution technology, laser power control is an important consideration. Therefore, calibration zones are provided for use to control power in the next generation MD2 disc input and output zones.

On Fig shows the structure of the I / O zone in the next generation MD2 disk. As shown in FIG. 15, disk input and output zones have each power calibration zone for controlling the power of the laser beam.

The input zone includes a management zone in which ADIP management information is recorded. ADIP management information describes disk management data using the low-order area of the ADIP cluster number.

Namely, the ADIP cluster number starts at the beginning of the recording zone and forms a negative value in the input zone. As shown in FIG. 15, the ADIP sector in the next generation MD2 disk consists of 4 bits of synchronization data, 8 high bits of the ADIP cluster number, 8 bits of control data (i.e., low bits of the ADIP cluster number), 4 bits of the ADIP sector number and 18 bit error correction parity code. As shown in FIG. 15, the 8 least significant bits of the ADIP cluster number describe control data such as disk type, magnetic phase, density, and read power.

The high bits of the ADIP cluster number remain untouched, which provides detection of the current cluster position with a fairly high degree of accuracy. The ADIP sector “0” and the ADIP sector “8” provide an accurate determination of the position of the ADIP clusters in the given intervals, since the 8 least significant bits of the ADIP cluster number remain untouched.

The process of recording control data using the ADIP signal is described in detail in Japanese Patent Application No. 2001-123535, filed with the Japan Patent Office in 2001, the entire contents of which are incorporated herein.

4. The structure of the recording / reproducing device

The following is a detailed description of a typical structure of a drive unit (recording / reproducing device) that meets the requirements for recording / reproducing discs used in next-generation MD1 and MD2 systems with reference to FIGS. 16 and 17.

On Fig shows the block 1 of the drive, which is configured to connect, for example, with a personal computer 100.

The drive unit 1 contains a media drive unit 2, a memory transfer controller 3, a buffer memory of 4 clusters, auxiliary memory 5, universal serial bus (USB) interfaces 6 and 8, a USB hub 7, a system controller 9, and an audio data processing unit 10.

The media drive unit 2 provides data recording and playback on and off of the installed disk 90. The disk 90 is a next-generation MD1 disk, a next-generation MD2 disk, or an existing MD system disk. A description of the internal structure of the media drive unit 2 will be described below with reference to FIG.

A memory transfer controller 3 controls transfers of write or read data to or from a medium drive unit 2.

Under the control of the memory transfer controller 3, the buffer memory of 4 clusters accumulates in the buffer data that is read with an increment equal to the recording blocks from the data tracks of the disk 90 by the medium drive unit 2.

The auxiliary memory 5 under the control of the memory transfer controller 3 stores various elements of the control information and special information extracted by the medium drive unit 2 from the disk 90.

The controller 9 of the system provides overall control inside the unit 2 of the drive media. In addition, the system controller 9 controls communication with a personal computer 100 connected to the drive unit 1.

Namely, the system controller 9 is connected with the possibility of communication with the personal computer 100 via the USB interface 8 and a USB hub 7. With this connection, the system controller 9 receives commands, such as a write request and a read request, from the personal computer 100, and transmits status information or other necessary information to the personal computer 100.

For example, when the disk 90 is installed in the media drive unit 2, the system controller 9 issues a command to the media drive unit 2 to remove the control information and other information from the disk 90, and a command to the memory transfer controller 3 to place the extracted control information, etc. . to auxiliary memory 5.

Upon receipt of a request from the personal computer 100 to read a specific FAT sector, the system controller 9 issues a command to the media drive unit 2 to read a recording unit containing this FAT sector. The extracted data of the recording unit is recorded in the buffer memory of 4 clusters under the control of the memory transfer controller 3.

From the data of the recording unit recorded in the buffer memory of 4 clusters, the controller 9 of the system retrieves the data forming the desired sector FAT. The extracted data is transmitted to the personal computer 100 via the USB interface 6 and a USB hub 7 under the control of the system controller 9.

Upon receipt of a request from the personal computer 100 to write a specific FAT sector, the system controller 9 instructs the media drive unit 2 to read a recording unit containing the necessary FAT sector. The extracted recording unit is recorded in the buffer memory of 4 clusters under the control of the memory transfer controller 3.

The system controller 9 supplies to the memory transfer controller 3 data of the FAT sector (i.e., recording data) coming from the personal computer 100 via the USB interface 6. In the buffer memory of 4 clusters, the corresponding data of the FAT sector is updated under the control of the controller 9 of the system.

Then, the system controller 9 sends a command to the memory transfer controller 3 to transmit data of the recording unit from the buffer memory of 4 clusters with the updated corresponding FAT sector to the media drive unit 2 as recording data. The media drive unit 2 writes the received data of the recording unit to the disk 90 with the data modulation process.

A switch 50 is connected to the system controller 9. This switch 50 is used to set the operation mode of the drive unit 1 in accordance with a next generation MD1 system or an existing MD system. In other words, the drive unit 1 is configured to record audio data on the disk 90 of the existing MD system in one of two formats: in the format of the existing MD system or in the format of the next generation MD1 system. The switch 50 serves to clearly indicate to the user which operating mode is set in the drive unit 1. Although a mechanical switch is shown, an electric, magnetic, or mixed type switch can also be used.

The drive unit 1 is provided with a display unit 51, such as a liquid crystal display (LCD). When the display control signal is supplied from the system controller 9, the display unit 51 can display text data and simplified icons representing the status information of the drive unit 1, as well as messages intended for the user.

The audio data processing unit 10 comprises, for example, in its input part, an analog input part for an audio signal made of a linear input circuit and an input circuit for a microphone, an analog-to-digital converter, and a digital input part for audio data. The audio data processing unit 10 also contains an ATRAC compression codec and a compressed data buffer memory. In addition, the audio data processing unit 10 includes in its output part an output part for digital audio data, a digital-to-analog converter, and an output part for an analog audio signal, consisting of a linear output circuit and an output circuit for headphones.

If the disk 90 is a disk of an existing MD system and if it is necessary to record audio tracks on the disk 90, then digital audio data (or analog audio signals) is input to the audio data processing unit 10. The input data is digital audio data with linear pulse code modulation (PCM) or analog audio signals that are converted into audio data with linear PCM using an analog-to-digital converter. The linear PCM audio data is then subjected to ATRAC compression coding before being placed in the buffer memory. Then, the data from the buffer memory is read out in a suitable manner over time (i.e., with a data increment equivalent to ADIP clusters) and transferred to the media drive unit 2. The media drive unit 2 subjects the transmitted compressed EFM modulation data before writing the modulated data to disc 90 as audio tracks.

If the disk 90 is the disk of the existing MD system and if you want to play the audio tracks from the disk 90, then the media drive unit 2 demodulates the reproduced data back to the ATRAC compressed data and transmits the demodulated data to the audio data processing unit 10 through the memory transfer controller 3. The audio data processing unit 10 submits the received data to ATRAC compression decoding to obtain linear PCM audio data that is output through the digital audio output portion. As an alternative solution, the received data is converted using a digital-to-analog converter into analog audio signals, which are output through the linear output part or the headphone output part.

The drive unit 1 can be connected to the personal computer 100 not only via a USB system. For example, you can use an external interface such as IEEE 1394 (Institute of Electrical and Electronics Engineers) to connect.

Writing and reading data are managed using the FAT system. The conversion process between the recording units and the FAT sectors is described in detail in Japanese Patent Application No. 2001-289380 to the Japanese Patent Office in 2001, the entire contents of which are incorporated herein.

Updating the FAT sector, as mentioned above, involves first accessing the recording unit (RB) containing the given FAT sector, and then reading the data of the recording unit from the disk. The extracted data is written to the buffer memory of 4 clusters and the FAT sector of this recording block is updated in it. After updating the FAT sector, the recording unit is written again to the disk from the buffer memory of 4 clusters.

The recording zone is not initialized in the next-generation MD1 or MD2 disc. This means that if this FAT sector must be used after updating the FAT sector, then an attempt to read the data of the recording unit will result in a data playback error, since the radio frequency signal will not be received. You cannot update the FAT sector without extracting data from the disk.

Reading the FAT sector also includes first accessing the recording unit containing the given FAT sector, and then reading the data of the recording unit from the disk. The extracted data is written to the buffer memory of 4 clusters to extract data from the intended FAT sector from the recording unit. Since the recorded zone was not initialized, if you need to use this recording unit, then the attempt to extract data will also be unsuccessful or will lead to the reproduction of erroneous data, since no radio frequency signal has been received.

The above failure can be circumvented by determining if the recording unit that was accessed was used sometime in the past. If it is determined that the recording unit has never been used, then the data of the recording unit is not read.

Namely, a recording signal bit array (SRB) is created to indicate whether each of the recording units represented by the number of the recording unit has ever been used, as shown in FIG. In the bitmap of recording signals, bit “0” is set for each recording block into which data has never been written; and bit “1” is set for the recording unit, in which data was recorded at least once.

On Fig shows a graphical diagram of the stages performed when reading by a personal computer connected to a drive unit compatible with the next generation MD1 and MD2 disks, data with an increment equal to the FAT sectors from the disk installed in the drive unit.

In step S1 of FIG. 21, the computer issues a command to read data from the FAT sector and obtains the number of a write block containing the given FAT sector. In this case, the sector number is the absolute sector number, with the number 0 representing the beginning of the user zone in the disk. In step S2, it is checked whether the FAT sector has been replaced by an alternative sector.

If it is concluded at step S2 that the FAT sector was not replaced by an alternative sector, this means that the desired FAT sector is included in the recording block, the number of which is obtained at stage S1. In this case, the process proceeds to step S3, in which a bit (0 or 1) corresponding to the recording unit is obtained from the bitmap of the write signals.

If it is concluded in step S2 that the FAT sector has been replaced by an alternative sector, then the read / write operation must be performed with the alternative sector. In this case, the process proceeds to step S4, in which, from the alternative table DDT, a recording block number representing a valid alternative sector is obtained. Step S4 is followed by step S3, in which a bit (0 or 1) corresponding to a recording unit containing an alternative sector is obtained from the bitmap of the write signals.

The bitmap of the write signals has the structure shown in FIG. If the data has never been written to the write block, then the bit corresponding to this block is, for example, “0”; if the data has been written to the recording unit at least once, then the corresponding bit for this block is, for example, “1”. Step S3 is followed by step S5, in which a bitmap of recording signals is scanned to determine whether data has been written to this recording block in the past.

If it is determined in step S5 that the bit is 1, which corresponds to the number of the recording unit in the bitmap of the recording signals (i.e., data were recorded in the recording unit in the past), the process proceeds to step S6. At step S6, the data of the recording unit is read from the disk and written to the buffer memory of 4 clusters. At step S7, data corresponding to the desired FAT sector is extracted from the buffer memory of 4 clusters and output as read data.

If it is determined in step S5 that the bit is 0, which corresponds to the number of the recording unit in the bitmap of the recording signals (i.e., data were not written to the recording unit in the past), the process proceeds to step S8. At step S8, the entire buffer memory of 4 clusters is filled with zeros. Step S8 is followed by step S7, in which data corresponding to the desired FAT sector is extracted from the buffer memory of 4 clusters and output as read data.

On Fig shows a graphical diagram of the stages performed by a personal computer connected to a drive module compatible with the next generation MD1 and MD2 disks, when writing data with an increment equal to the FAT sector, in the disk mounted in the drive unit.

In step S11 of FIG. 22, the computer instructs to write data to the FAT sector, and the number of the recording block containing the given FAT sector is obtained. In this case, the sector number is also the absolute sector number, with “0” representing the beginning of the user zone on the disk. In step S12, a check is made to see if the FAT sector has been replaced by an alternative sector.

If it is established in step S12 that this sector was not replaced by an alternative sector, this means that the desired FAT sector is contained in the recording block, the number of which was obtained in step S11. In this case, the process proceeds to step S13, in which a bit (0 or 1) corresponding to the number of the recording block is obtained from the bitmap of the write signals.

If it is concluded in step S12 that the FAT sector has been replaced by an alternative sector, then the current read / write operation should be performed with the alternative sector. In this case, the process advances to step S14, in which, from the alternative table DDT, a number of a recording block representing a valid alternative sector is obtained. Step S14 is followed by step S 13, in which a bit (0 or 1) corresponding to the number of the recording block containing the alternative sector is obtained from the bitmap of the write signals.

The array of write signals has the structure shown in FIG. If data has not yet been written to this recording block, then the bit corresponding to this block is, for example, “0”; if the data was written to the recording unit at least once, then the bit corresponding to this block is, for example, “1”. Step S13 is followed by step S15, in which a bitmap of recording signals is scanned to determine whether data has been written to this recording block in the past.

If it is determined in step S15 that the bit is 1, which corresponds to the number of the recording unit in the bitmap of the recording signals (i.e., data were recorded in the recording unit in the past), the process proceeds to step S16. At step S16, the data of the recording unit is read from the disk and written to the buffer memory of 4 clusters. At step S17, the data corresponding to the desired FAT sector in the recording unit is replaced by the recording data located inside the buffer memory of 4 clusters.

If it is determined in step S15 that the bit is 0, which corresponds to the number of the recording block in the bitmap of the recording signals (i.e., no data was written to the recording block in the past), the process proceeds to step S18. At step S18, the entire buffer memory of 4 clusters is filled with zeros. Step S18 is followed by step S17, in which data corresponding to the desired FAT sector in the recording unit is replaced by recording data inside the buffer memory of 4 clusters.

After replacing the data corresponding to the desired FAT sector in step S17, in the block of interest in the recording unit for recording data, the process proceeds to step S19. At step S19, the data of the recording unit is written to the disk.

As indicated above, when data is being written to or read from or to the FAT sector, a check is made to see if a recording unit containing this FAT sector has ever been used. If it is concluded that the recording unit was not used, then the data is not read from the recording unit, and all buffer memory of 4 clusters is filled with zeros. This allows you to treat an unused recording unit as having an initial value of 0. As a result, there is no error when data is being written or read with an increment equal to the FAT sector, even if the recording unit containing the desired FAT sector has never been used and an RF signal has not been received .

In the preceding examples, data is written to or read from the FAT sector when the personal computer is connected to a drive unit compatible with next-generation MD1 and MD2 disks. In these cases, the FAT sector is indicated by a personal computer using the absolute sector number, with the number 0 representing the beginning of the user zone. In contrast, if the drive unit is used alone to write or read data to or from a given FAT sector in the disk, then the FAT sector is identified using the file directory element and the FAT chain, as shown in FIGS. 23 and 24.

On Fig shows a graphical diagram of the stages in which the drive unit itself reads data from the FAT sector of the disk MD1 or MD2 next generation.

In step S21 of FIG. 23, the relative FAT cluster number containing the desired PAT sector is obtained. In step S22, the absolute number of the first FAT cluster is obtained from the file directory entry. At step S23, the entire chain of FAT tables is scanned, starting with the absolute cluster number thus obtained, until the absolute number of the desired FAT cluster is obtained. In step S24, the absolute number of the desired FAT sector is obtained from the absolute number of the desired FAT cluster. After thus obtaining the number of the desired FAT sector, the process proceeds to step S25, in which data is read from the FAT sector. The process of reading sector data is the same as shown in FIG.

On Fig shows a graphical diagram of the stages in which the drive unit itself writes data to the FAT sector of the disk MD1 or MD2 next generation.

In step S31 of FIG. 24, the relative FAT cluster number containing the desired FAT sector is obtained. In step S32, the absolute number of the first FAT cluster is obtained from the file directory entry. In step S33, the entire chain of FAT tables is scanned, starting with the absolute cluster number thus obtained, until the absolute number of the desired FAT cluster is obtained. In step S34, the absolute number of the desired FAT sector is obtained from the absolute number of the desired FAT cluster. After thus obtaining the number of the desired FAT sector, the process proceeds to step S35, in which data is written to the FAT sector. The process of writing data to the sector is the same as shown in FIG.

In the preceding examples, the recording signal bitmap shown in FIG. 20 is used to determine if a recording unit containing the desired FAT sector has ever been used before. Managing a file allocation table (FAT) is performed as an example with an increment equal to a 32 kB FAT cluster. The use of FAT information provides the ability to verify whether a given FAT sector has been used in the past. Based on the FAT information, it is possible to create a bitmap of recording signals, showing, for example, whether each of the 64-kbyte recording blocks has already been used at least once.

On Fig shows a graphical diagram of the stages of generating a bitmap of recording signals using FAT information. In step S41 of FIG. 25, when the disc is installed, the values representing the recording units in the bitmap of the write signals are all reset to 0. In step S42, the FAT information is read. In step S43, access is made to the first FAT element.

From the first FAT element to the last, a check is performed to determine whether each of the FAT clusters has ever been used. A bit in the bitmap of write signals that matches any unused FAT cluster remains untouched by “0”; those bits in the bitmap of the write signals that correspond to the used FAT clusters are each set to “1”.

That is, after accessing the first FAT element, the process proceeds to step S44, in which a check is made whether the current checked element is the last FAT element. If it is determined in step S44 that the current checked item is not the last FAT element, then the process proceeds to step S45. In step S45, a check is made to see if the current FAT to be checked is a used FAT cluster.

If it is determined in step S45 that the current checked FAT element is an unused FAT cluster, the process proceeds to step S46, in which the next FAT element is checked. From step S46, the control process returns to step S44.

If it is determined in step S45 that the current FAT to be checked is the used FAT cluster, the process proceeds to step S47, in which the number of the recording block containing the desired FAT cluster is obtained. In step S48, the bit corresponding to the recording unit in the bitmap of the recording signals is set to “1”. In step S49, the control process returns to step S44.

Repeating steps S44-S49 leads to the creation of a bitmap of write signals in which the bits corresponding to the unused FAT clusters remain unchanged to “0”, while the bits corresponding to the used FAT clusters are each set to “1”.

If it is determined in step S44 that the current FAT element to be checked is the last FAT element, the process proceeds to step S50, in which the bitmap of the write signals is considered complete.

As mentioned above, the use of FAT information provides the ability to create a bitmap of recording signals.

However, depending on the operating system, FAT clusters that are determined to be used based on FAT information do not necessarily indicate clusters to which data in the past was actually written. On such operating systems, some FAT clusters can be identified as already used, although they were not actually used.

The above contradiction is eliminated by writing a bitmap of write signals to disk. As shown in FIGS. 2 and 4, the next generation MD1 and MD2 discs have each backup track between the DDT track and the FAT track. The backup track can be used to hold the bitmap of the recording signals in which the bitmap information of the recording signals shown in FIG. 20 is located.

If the position of the track on which the bitmap of the recording signals is to be recorded is determined by the system in advance, then the bitmap can be accessed directly based on this given position. The DDT track and the FAT track can also be accessed directly if their position is set by the system in advance. Obviously, the position of these special tracks can be recorded as an alternative solution in the control zone (U-TOC zone in the next generation MD1 disk; the control zone containing ADIP-based control information in the next generation MD2 disk). Data from the DDT track and the FAT track are read when a disk is inserted and placed in the buffer memory. The data thus extracted is used as the basis for generating alternative sector information and FAT information. These items of information are updated in the buffer memory during disk use. When a disc is ejected, updated alternative sector information and FAT information are written back to the DDT track and the FAT track. Writing or reading a bitmap of recording signals to or from a recording track is basically the same as writing or reading data from or to the DDT track and the FAT track.

When the disk is installed, the bitmap of the recording signals is read from the track of its recording and placed in memory. With each new recording of data into the recording unit in memory, the corresponding element of the bitmap of the recording signals is updated. When the disc is ejected, the updated bitmap of the write signals is read from the memory and written to the track of the bitmap of the write signals on the disk.

On Fig shows a graphical diagram of the stages for reading information from the track of the bitmap array of recording signals. In step S61 of FIG. 26, when the disc is installed, information is read from the track of the bitmap of the disc recording signals. At step S62, information read from the track of the bitmap of the write signals is recorded in the memory and converted into a bitmap of the write signals.

On Fig shows a graphical diagram of the stages for recording the bitmap of the recording signals back to the track of the bitmap recording signals on the disk. In memory, the bitmap of recording signals is updated each time with each new data recording in any recording unit.

In step S71 of FIG. 27, when the disc is ejected, the updated bitmap of the write signals is read from the memory. In step S72, the thus obtained bitmap of the write signals is recorded in the track of the bitmap of the write signals on the disk.

In its original state, the information contained in the bitmap of the write signals all consists of zeros. After each use of the disk, those bits in the bitmap of recording signals that correspond to the recording blocks subjected to data writing operations are updated all to “1”. This information in the bitmap of the write signals is written back to the track of the bitmap of the write signals on the disk. The next time the disk is installed for use, information is read from the track of the bitmap of the write signals and converted into memory into a bitmap of the write signals. These stages provide the ability to generate a bitmap of write signals without accessing FAT information.

The following is a description of a typical structure of a media drive unit 2 configured to write and read data from both data tracks and audio tracks of a disc, with reference to FIG.

As shown in FIG. 17, the media drive unit 2 has a support disk configured to accommodate three types of disks: an existing MD system disk, a next generation MD1 disk, and a next generation MD2 disk. A disk placed on a support disk is rotated by a drive motor 29 based on a constant linear velocity (CLV). To perform a write or read operation on the disk 90, the optical head 19 emits a laser beam to the surface of the disk.

For the recording operation, the optical head 19 emits a laser beam with a level high enough to heat the recording track to the Curie temperature; for the read operation, the optical head 19 emits a laser beam with a relatively low level sufficient to detect data in the reflected beam based on the magneto-optical Kerr effect. To realize these possibilities, the optical head 19 contains a laser diode as a laser output means, an optical system made of a polarizing beam splitter and objective lenses, as well as a detection device for detecting reflected light (not shown). The lenses of the lens are held in the optical head 19, for example, using a biaxial mechanism with the ability to move relative to the surface of the disk both in the radial direction and in the perpendicular direction.

The magnetic head 18 is located above the disk 90 symmetrically opposite to the optical head 19. The magnetic head 18 acts on the disk 90 with a magnetic field modulated to represent the recorded data. Although not shown, a slide motor and a slide mechanism are provided for moving the entire optical head 19 and the magnetic head 18 in the radial direction of the disk.

The optical head 19 and the magnetic head 18 perform a modulation process using a magnetic field upon pulsed excitation to form infinitely small marks on the next-generation MD2 disk. On the disk of the existing MD system or on the next-generation disk MD1, the optical head 19 and the magnetic head 18 perform a modulation process using a magnetic field with constant radiation.

The media drive unit 2 also comprises a recording process section, a playback process section and a servo section in addition to the recording / reproducing head section consisting of the optical head 19 and the magnetic head 18, and the drive section for rotating the disk formed by the drive motor 29.

One of three types of drive 90 can be installed: the drive of the existing MD system, the drive of the next generation MD1, and the drive of the next generation MD2. Line speed varies with the type of disk. The drive motor 29 is able to rotate the installed disk 90 at a speed compatible with this type of disk. That is, the disk 90 mounted on the support disk rotates at a linear speed corresponding to one of the three indicated types of disk.

The recording process section contains two parts: one uses ACIRC for error correction and EFM for modulating data to record modulated after error correction data in the audio tracks of the existing MD system, and the other part that uses a combination of BIS and LDC for error correction and 1-7 pp modulation for modulating data to record modulated after error correction data on the next generation MD1 disk or the next generation MD2 disk.

The playback process section contains two parts: one uses EFM for data demodulation and ACIRC for error correction when playing data from the disc of an existing MD system, and the other part uses 1-7 pp demodulation based on data detection using a partial response scheme and Viterbi decoding method for reproducing data from a next-generation MD1 or MD2 system disc.

The playback process section further comprises a part for decoding the ADIP signal based addresses used in the existing MD system or in the next generation MD1 system, as well as a part for decoding the ADIP signal used in the next generation MD2 system.

Laser radiation from the optical head 19 creates a reflected laser beam representing information found on the disk. Information discovered, i.e. the photoelectric current obtained by the photodetector detecting the reflected laser beam is sent to the radio frequency amplifier 21.

The RF amplifier 21 subjects the obtained detected information to current-to-voltage conversion, amplification, and matrix computation to extract reproducing information including a reproduced RF signal, tracking error signal TE, focus error signal FE, and groove information (ADIP information recorded as track swings on a disc 90).

When data is reproduced from a disc of an existing MD system, the reproduced radio frequency signal received in the radio frequency amplifier 21 is processed by the EFM demodulation unit 24 and the ACIRC decoder 25. Namely, the EFM demodulation unit 24 binaryizes the reproduced radio frequency signal to obtain a chain of EFM signals before performing their EFM demodulation. The demodulated signal undergoes error correction and a reverse rotation process using the ACIRC decoder 25. Thus, compressed ATRAC data is obtained.

After playing back the data from the disk of the existing MD system, the switch 26 is set to pin B. With this setting, the switch 26 makes it possible to output demodulated ATRAC compressed data from the disk 90 as reproduced data.

When data is reproduced from the next generation MD1 or MD2 disc, the reproduced radio frequency signal obtained by the radio frequency amplifier 21 is supplied to the RLL (1-7) PP demodulation unit 22 and the RS-LDC decoder 23. Namely, after receiving the reproduced radio frequency signal, the RLL (1-7) PP demodulation unit 22 performs data detection using PR (1, 2, 1) ML or PR (1, -1) ML and Viterbi decoding to obtain a chain of RLL (1 -7) as reproduced data. Block 22 exposes the RLL (1-7) demodulation code chain RLL (1-7). The demodulated data is supplied to the RS-LDC decoder 23 for error correction and the reverse rotation process.

After reproducing data from the next-generation disc MD1 or MD2, the switch 26 is set to pin A. With this setting, the switch 26 enables the demodulated data from the disk 90 to be reproduced as reproduced data.

The tracking error signal TE and the focus error signal FE are supplied from the radio frequency amplifier 21 to the servo circuit 27. The groove information is supplied from the radio frequency amplifier 21 to the ADIP demodulation unit 30.

In block 30 of the ADIP demodulation, the received groove information is passed through a band-pass filter to extract the swing components before performing frequency demodulation and two-phase demodulation of the ADIP signal. The demodulated ADIP signal is supplied to address decoders 32 and 33.

In an existing MD system disc or next generation MD1 disc, the ADIP sector number is 8 bits long, as shown in FIG. 9. In the next generation MD2, the ADIP sector number is 4 bits long, as shown in FIG. 11. The address decoder 32 decodes the ADIP address from the disk of the existing MD system or the next generation MD1 disk, while the decoder 33 decodes the ADIP address from the next generation MD2 disk.

The ADIP address decoded by the address decoder 32 or 33 is transmitted to the drive controller 31. After receiving the ADIP address, the drive controller 31 performs the necessary control process. The groove information from the RF amplifier 21 is also supplied to the servo circuit 27 for servo control of the drive.

In the servo circuit 27, phase differences are integrated between the received groove information and the reproduced synchronization signal (the PLL synchronization signal obtained after decoding) to obtain an error signal. Based on the received error signal, the servo circuit 27 generates a drive error signal for servo control CLV or CAV (constant linear velocity or constant angular velocity).

The servo circuit 27 generates various tracking control signals (e.g., a tracking control signal, a focus control signal, a slide control signal and a drive control signal) based on a drive error signal, a tracking error signal and a focus error signal from the radio frequency amplifier 21, or based on a jump command tracks and access commands from the controller 31 of the drive. The servo control signals generated in this manner are provided to the engine driver 28. Namely, in the servo circuit 27, tracking error signals and commands are subjected to such processing as phase compensation, gain control and setting target values for generating various servo control signals.

The motor driver 28 generates servo drive signals based on the servo control signals received from the servo circuit 27. The servo drive signals generated by the motor driver 28 consist of two-axis drive signals to drive a two-axis mechanism (two signals for the drive in focus and tracking directions), a drive signal the slide motor for driving the slide mechanism, and the drive signal of the drive motor for driving the drive motor 29. These servo drive signals provide focus and tracking control on disc 90 and control of the CLV or CAV drive motor 29.

When it is necessary to record audio data on the disc of an existing MD system, the switch 16 is set to pin B. Installing the switch ensures the operation of the ACIRC encoder 14 and the EFM modulation unit 15. With this setting, the compressed data coming from the audio data processing unit 10 is subjected to an interleaving process and error correction coding using the ACIRC encoder 14. The output of the ACIRC encoder is subjected to EFM processing using the EFM modulation unit 15.

The EFM modulated data is supplied to the magnetic head driver 17 through the switch 16. The magnetic head 18 acts on the disk 90 with a magnetic field representing EFM modulated data, whereby the data is recorded on the audio tracks of the disk 90.

When it is necessary to record audio data on the next-generation MD1 or MD2, the switch 16 is installed on pin A. This setting provides the operation of the RS-LDC encoder 12 and the RLL (1-7) PP modulation unit 13. With this setting, high-density data coming from the memory transfer controller 3 is subjected to an interleaving process and error correction coding based on RS-LDC using the RS-LDC encoder 12. The output of the RS-LDC encoder 12 is subjected to RLL (1-7) PP modulation using the RLL (1-7) PP modulation unit 13.

The recorded data in the form of an RLL code chain (1-7) is supplied to the magnetic head driver 17 through the switch 16. The magnetic head 18 acts on the disk 90 with a magnetic field representing modulated data, due to which the data is recorded in the audio tracks on the disk 90.

The laser driver / APC 20 has a dual task: to cause the laser beam to emit a laser diode during these read and write operations and to provide the so-called automatic laser power control (APC).

Although not shown, a detector for monitoring the laser power level is included in the optical head 19. A control signal from the detector is fed back to the laser driver / APC 20. The laser driver / APC 20 compares the current laser power received as a control signal with the set power level laser to determine the difference error. Due to the effect of this difference error on the laser excitation signal, the laser driver 20 keeps the power of the laser diode stabilized at a set level.

Using the controller 31 of the drive, two laser power levels are set, i.e. read laser power level and write laser power level, which are registered in the laser driver / APC 20.

Under the control of the controller 9 of the system, the controller 31 of the drive ensures that the above control operations (access, tracking operations, data write operation and data read operation) are performed correctly.

Shown in Fig.17 parts A and B, circled by a dashed line, can each be made in the form of an integrated circuit.

5. Initialization of next-generation MD1 and MD2 drives

In both the next-generation MD1 and the next-generation MD2, a unique identifier (UID) is written in addition to the FAT to control security, as mentioned above. On each next-generation MD1 or MD2 disc, a unique identifier is recorded in principle at a predetermined location, such as an input area, before the disc is shipped from the factory. Alternatively, a unique identifier can be written elsewhere on the disc. If the UID is recorded in a given place after the disk is initialized, then the UID can be written in this place in advance.

The next generation MD1 system uses the same drive as the existing MD system. This means that a huge number of disks of the existing MD system, already sold without writing UID to them, are to be used in the next generation MD1 system.

Thus, new standards were created for the location of a special protected area on each of these many disks of the existing MD system, which can be used in the next-generation MD1 system. After initializing any of these disks, the disk drive unit 1 writes a random number signal to the protected area for use as the UID of this disk. In accordance with the new standards, users are denied access to the zone occupied by the UID. UID is not limited to random number signals; it can be specified as a combination of the manufacturer’s code, equipment code, equipment serial number and random number. You can also combine at least the manufacturer code, equipment code, or serial number of the equipment with a random number for use as a UID.

On Fig shows a graphical diagram of the steps for initializing the next generation MD1 disk. In a first step S100 of FIG. 18, an access is made to a predetermined disk location to determine if a UID is recorded. If it is determined that the UID is recorded, then the UID is read and temporarily stored in the auxiliary memory 5.

The location that is accessed in step S100 is a zone outside the FAT zone in the next generation MD1 system format, such as an input zone. If this disk 90 has undergone initialization in the past and is already equipped with a DDT zone, then access to this zone can be made. Step S100 may be omitted if not necessary.

In step S101, data is recorded in the U-TOC zone during the EFM modulation. At this time, information is recorded in the U-TOC zone to provide two kinds of zones: a warning track and a track zone following the DDT zone, i.e. zone in which data should be recorded in modulation format 1-7 pp. At step S102, data is recorded in the warning track in EFM format. In step S103, data is recorded in the DDT zone in a modulation format of 1-7 pp.

In step S104, UIDs are recorded outside the FAT zone, such as a DDT zone. If the UID has been read from its predetermined location and located in the additional memory 5 in step S100, then this UID is recorded. If it was determined in step S100 that the UID was not written to the disc at the specified location, or if step S100 was not performed, then UIDs are generated based on the random number signal, and the generated UID is recorded. The UID generates, for example, a system controller 9. The generated UID is supplied to the media drive unit 2 through the memory transfer controller 3 before being written to the disk 90.

In step S105, the FAT and other data are recorded in a data storage area in a 1-7 pp modulation format. In other words, the UID is recorded outside the FAT. In the next-generation MD1 system, as mentioned above, the initialization of a recording zone controlled by the FAT scheme is not mandatory.

On Fig shows a graphical diagram of the stages for initializing the next-generation MD2 disk. In the first step S110 of FIG. 19, access is made to a predetermined location where a pre-recorded UID is assumed, such as an input zone, or to a DDT zone if the disk was initialized in the past to determine if the UID is recorded here. If it is established that the UID is written, then the UID is read and placed, for example, in auxiliary memory 5. Since the recording location of the UID is invariably set in the format, you can access it without accessing any other management information on the disk. This feature also applies to the above process described with reference to FIG.

In step S111, data is recorded in the DDT zone in a modulation format of 1-7 pp. In step S112, the UID is recorded outside the FAT, for example, in the DDT. The UID recorded at this time is the UID that was extracted from the predetermined disk space and placed in the auxiliary memory 5 in step S110. If it is determined in step S110 that the UID has not been written to the disc at a predetermined location, then the UID is generated based on the random number signal, and the generated UID is recorded. The UID generates, for example, a system controller 9. The generated UID is supplied to the media drive unit 2 through the memory transfer controller 3 before being written to the disk 90.

In step S113, FAT and other data are recorded. UIDs are written outside the FAT. For the next-generation MD2 disc, as mentioned above, the initialization of the recorded zone, controlled by the FAT scheme, is not performed.

6. The first example of a sound data management system

As indicated above, in the next generation MD1 and MD2 discs according to the present invention, data is controlled using the FAT system. The audio data to be recorded is compressed using a predetermined data compression method and encrypted to protect copyright. A method for compressing audio data is, for example, ATRAC or ATRAC5. You can also use MP3 (audio level 3 MPEG1), AAC (advanced audio encoding MPEG2), or other suitable compression method. You can process not only audio data, but also still image data and moving image data. Since the FAT system is used, general-purpose data can also be recorded and reproduced using the next-generation MD1 and MD2 systems. In addition, computer-readable and computer-executable instructions can be encoded on a disk, so that MD1 and MD2 can also contain executable files.

The following is a description of a system for managing audio data during recording and playback from or onto next-generation MD1 and MD2 discs.

Since the next-generation MD1 and MD2 systems are capable of reproducing high-quality audio data for a long time, there is a huge number of audio data elements to be controlled on one disc. Since the FAT system is used for data management purposes, it provides better compatibility with computers. However, this feature, as recognized by the authors of this invention, has its advantages and disadvantages. While the ease of operation on the user side is increasing, the possibility of illegal copying to the detriment of copyright arises. These characteristics were especially taken into account when developing the audio data management system according to the invention.

FIG. 28 shows a first embodiment of an audio data management system. As shown in FIG. 28, the audio data management system in its first embodiment generates on the disk a track index file and an audio data file. These files are files managed by the FAT system.

An audio data file is a file in which a plurality of audio data elements are located, as shown in FIG. From the point of view of the FAT system, the audio data file is a very large file. This file is internally divided into parts, so that audio data can be processed as a set of such parts.

A track index file is a file that describes various types of information for managing audio data contained in an audio data file. As shown in FIG. 30, a track index file consists of a play order table, a programmed play order table, a group information table, a track information table, a part information table, and a title table.

The playback order table indicates the default audio playback order. As shown in FIG. 31, the playback order table contains information items TINF1, TINF2, etc., representing links to track descriptors (see FIG. 34a) corresponding to track numbers (i.e., music numbers) in the information table tracks. Track numbers are, for example, serial numbers starting at 1.

The programmed playback order table contains the audio data playback order specified by an individual user. As shown in FIG. 32, the programmed play order table describes the elements PINF1, PINF2, etc. programmed track information representing links to track descriptors corresponding to track numbers.

The group information table, as shown in FIGS. 33A and 33B, describes group information. A group is defined as a set of one or more tracks having track numbers, or a set of one or more tracks with programmed track numbers. Namely, the group information table consists of group descriptors representing groups of tracks, as shown in FIG. 33A. Each group descriptor describes a start track number, an end track number, a group name, and a flag relating to a given group, as shown in FIG. 33B.

The track information table describes track information, i.e. about musical works, as shown in FIGS. 34A and 34B. Namely, the track information table consists of track descriptors representing the tracks (music), as shown in FIG. 34A. Each track descriptor, as shown in FIG. 34B, contains a coding system, copyright management information, content decryption key information, pointer information indicating a number of a part serving as an input to a musical work of a given track, artist name, title of a work, information about the original order of the pieces and information about the recording time of the track The name of the artist and the name of the work do not contain valid names, but describe information of pointers indicating the corresponding elements in the table of names. The coding system represents a codec operation scheme serving as decryption information.

The parts information table describes pointers that provide indication, using part numbers, of the actual locations of musical works, as shown in FIGS. 33A and 35B. Namely, the part information table consists of part descriptors corresponding to the parts, as shown in FIG. 35A. A part represents one complete track or one of a plurality of parts forming one track. FIG. 35B shows part descriptor elements in a parts information table. As shown in FIG. 35B, each descriptor consists of a start address and an end address of a given part in the audio data file and communication with the next part.

The addresses used as part number pointer information, name table pointer information and location pointer information in the audio data file can each be specified as a file byte shift, part descriptor number, FAT cluster number, or physical disk address used as the storage medium. A file byte shift is a special implementation of the shift scheme according to the present invention, where the part pointer information is a shift value in predetermined units (e.g., bytes, bits and blocks of n bits) from the beginning of the audio data file.

A table of names is a table of text constituting valid names. As shown in FIG. 36A, the title table consists of a plurality of title positions. Each position of the name is connected to a pointer and called by a pointer pointing to the desired name. The pointer to call the name may be the name of the artist or the name of the work in the track information table, or the name of the group in the group information table. From a plurality of pointers, one title position can be called. As shown in FIG. 36B, each title position consists of title data constituting text information, such as a title serving as an attribute of text information, and a relationship with a different title position. A name that is too long to be placed in one position of the name can be divided into several positions of the name. Split name positions are tracked one after the other using links describing the full name.

The first exemplary embodiment of the audio data management system according to the invention works as follows: as shown in FIG. 37, the number of the track to be played first is indicated in the playback order table (see FIG. 31). With the indicated track number, access is provided through communication with the track descriptor (see FIGS. 34A and 34B) in the track information table, and the associated track descriptor is retrieved from the table. The following are read from the track descriptor: coding system, copyright management information, content decryption key information, pointer information indicating the number of the part serving as the input of the musical piece of the desired track, artist name pointer, work title pointer, initial title information and information about Recording time of the track.

Based on the part number information read from the track information table, access is provided through communication to the desired part descriptor in the part information table (see FIGS. 35A and 35B). From the parts information table, access to the audio data file is provided in the part corresponding to the beginning of the address of the desired track (piece). When access is obtained to the data in the part, the position of which in the audio data file is indicated by the table of information of the parts, then the playback of the audio data starts from this place. At the same time, the reproduced data is decrypted in accordance with the coding system read from the corresponding track descriptor in the track information table. If the audio data is encrypted, then key information read from the track descriptor is used to decrypt the data.

If there is any other part following this part, then the part descriptor describes the relationship with the destination part. The corresponding part descriptors are read one after the other in accordance with the relationships, so that the audio data in the audio data file is reproduced from the parts whose position is indicated by the descriptors of the parts that are accessed. These stages provide reproduction of audio data from the desired track (musical composition).

The title position (see FIG. 36A) in the title table is called up from the place (or from the title index information) indicated by the artist’s name index or the title of the title read from the track information table. Name data is read from the name position thus called up. The name pointer information may be, for example, a name position number, a cluster number in a file allocation table system, or a physical address of a data medium.

Each position of the name in the table of names can be indicated by a plurality of pointers, as indicated above. For example, when several works of one artist are recorded, then one title position in the title table is indicated by a plurality of pointers in the track information table, as shown in FIG. 38. In the example shown in FIG. 38, the descriptors “1”, “2” and “4” of the tracks represent pieces of music belonging to the same “DEF BAND” artist, so that the same title position is indicated by each of these track descriptors. As also shown in FIG. 38, the “3”, “5” and “6” track descriptors represent pieces of music belonging to the same “GHQ GIRLS” artist, so that the same title position is also indicated by each of these track descriptors. When each position of the name in the name table can be indicated by a plurality of pointers, then the size of the name table can be significantly reduced.

In addition, information about a given artist name can be displayed through the use of links to the table of names. If it is desirable to display a list of musical works relating, for example, to the artist name "DEF BAND", then track descriptors indicating the same position of the name "DEF BAND" are tracked and their information is displayed. In this example, the “1”, “2” and “4” track descriptors are tracked indicating the same position of the “DEF BAND” name, and descriptor information is displayed. The information obtained in this way provides the display of musical works related to the name of the artist "DEF BAND" and located in the disc. In this case, there are no links going from the table of names back to the table of track information, since each position of the name can be indicated by several pointers.

When it is necessary to record new audio data, in accordance with the FAT table, an unused zone consisting of at least a predetermined number of sequentially arranged recording blocks (for example, 4 recording blocks) is reserved. The recording units are arranged sequentially to minimize loss of access to recorded audio data.

When a recordable audio data area is reserved, a new track descriptor is assigned to the track information table, and a content key is generated to encrypt the audio data. The input audio data is encrypted using the key before recording to the reserved unused zone. The area in which the audio data was recorded is connected to the rear end of the audio data file in the FAT file system.

After connecting the new audio data to the audio data file, the attached location information is generated, and the generated new location information of the audio data is recorded in the new assigned part descriptor. The key information and part number are recorded in the new track descriptor. If necessary, the name of the artist and the name of the work are recorded in the corresponding positions of the names. In a track descriptor, pointers are described by relationships with the artist’s name and the title of the work. The number of this track descriptor is recorded in the table of the playback order, and the corresponding copyright management information is updated.

When it is necessary to reproduce audio data from a specific track, information about the indicated track number is extracted from the table of the playback order. Then, a descriptor corresponding to the track with which to reproduce the audio data is obtained.

From the corresponding track descriptor in the track information table, key information is obtained and a part descriptor is obtained indicating the area containing the entered data. From the part descriptor, access is made to a place in the audio data file of the first part containing the desired sound data, and data is extracted from the place to which access is made. The data reproduced from this place is decrypted using the obtained key information for reproducing audio data. If the part descriptor is associated with another part, then access to the associated part and repeat the above stages.

Suppose that it is desirable to change the number “n” of a given track in the table of the playing order to the track number “n + m”. In this case, the track descriptor Dn, first describing the track information, is first obtained from the track information element TINFn in the playback order table. All values representing elements from TINFn + 1 to TINFn + m of track information (i.e., track descriptor numbers) are moved forward one place. Then, the track descriptor number Dn is recorded in the track information element TINFn + m.

Suppose that it is desirable to erase a track with track number "n". In this case, a track descriptor Dn describing the track information is obtained from the track information element TINFn in the playback order table. All valid track descriptor numbers following the TINFn + 1 element of track information in the playback order table are moved forward one place. In addition, since the track “n” needs to be erased, all the track information items following the track “n” are moved forward one place in the playback order table. Based on the Dn descriptor thus obtained for the track to be erased, an encoding system and a decryption key for that track are obtained from the track information table. A part number descriptor Pn is also obtained indicating a zone containing the beginning of the audio data. The audio data block with the range indicated by the part descriptor Pn is separated from the audio data file in the FAT file system. Then, the descriptor Dn of the track is erased from the track information table and the part descriptor is deleted from the part information table to release the part descriptor in the file system.

Assume that parts A, B and C in FIG. 39A were chained together and it is desirable to erase part B. In this case, it is assumed that parts A and B share the same block of audio data (and the same cluster FAT), and that the FAT chain is continuous. It is also assumed that while part C is located immediately after part B in the audio data file, when checking the FAT table, it turns out that parts C and B are located separately.

In this case, as shown in FIG. 39B, erasing part B allows you to separate two FAT clusters that are not shared by the part from the FAT chain (i.e., turn them into free zones). In other words, the audio data file is shortened to 4 blocks of audio data. As a result, the number 4 is subtracted from each of the block numbers of the audio data recorded in part C and in subsequent parts.

You can erase part of a track instead of erasing the entire track. If the track is partially erased, the information about the remaining track can be decrypted using the encoding system and the decryption key corresponding to that track and obtained from the corresponding part descriptor Pn in the track information table.

If it is desirable to combine track "n" with track "n + 1" in the table of the playback order, then the number of the descriptor Dn of the track is obtained from the TINFn elements of the track information in the table of the playback order, wherein the track descriptor describes information about the track "n"; and get the descriptor number Dm from the track information element TINFn + 1, wherein the track descriptor describes the track information “n + 1”. All actual TINF values (track descriptor numbers) following the TINFn + 1 element in the playback order table are moved forward one place. A search is performed in the table of the programmed playback order to erase all tracks related to the track descriptor Dm. A new encryption key is generated, and a list of part descriptors is obtained from the track descriptor Dn. Attached to the back end of this list of part descriptors is another list of part descriptors extracted from the Dm descriptor.

When it is necessary to combine two tracks, it is necessary to compare their track descriptors to confirm that copyright is not infringed. It is necessary to obtain part descriptors from these track descriptors to confirm with reference to the FAT table that the fragmentation requirements are met after the two tracks are connected. It may also be necessary to update the pointers for the name table.

When it is desired to divide track “n” into track “n” and track “n + 1”, the track descriptor Dn number of the track describing the track information “n” is first obtained from the track information element TINFn in the playback order table. From the track information element TINFn + 1 in the playback order table, a descriptor number Dm describing track information “n + 1” is obtained. All actual TINF values (track descriptor numbers) following the TINFn + 1 element in the playback order table are moved forward one place. A new key is generated for the track descriptor Dn. The list of part descriptors is retrieved from the track descriptor Dn. A new part descriptor is registered and the contents of the part descriptor valid before the track is split is copied to the new reserved part descriptor. The part descriptor containing the split point is reduced to that point, and any part descriptor links following the split point are unloaded. The newly assigned part descriptor is set immediately after the split point.

7. Second example of an audio data management system

The following is a detailed description of a second exemplary embodiment of an audio data management system according to the invention. 40 shows a second exemplary embodiment of an audio data management system. As shown in FIG. 40, the audio data management system according to this exemplary embodiment includes generating track indexes and a plurality of audio data files on a disk. These files are managed using the FAT system.

Each sound data file, as shown in FIG. 41, contains in principle sound data forming one musical name (musical work). The audio data file has a header that contains a name, decryption key information, copyright management information and index information. Indexes are used to split a single piece of music on one track into several tracks. The header records the location of the index-separated tracks in conjunction with the index numbers. For example, up to 255 indices can be set for one track.

A track index file is a file that describes various pieces of information for managing audio data held in audio data files. As shown in FIG. 42, the track index file consists of a play order table, a programmed play order table, a group information table, a track information table, and a title table.

The playback order table indicates the default audio playback order. As shown in FIG. 43, the playback order table contains the elements TINF1, TINF2, etc. information representing links to track descriptors (see FIG. 46A) corresponding to track numbers (i.e., music numbers) in the track information table. Track numbers are, for example, serial numbers starting at 1.

The programmed playback order table contains the audio data playback order specified by an individual user. As shown in FIG. 44, the programmed play order table describes the programmed elements PINF1, PINF2, etc. track information representing links to track descriptors corresponding to track numbers.

The group information table shown in FIGS. 45A and 45B describes group information. A group is defined as a set of one or more tracks having track numbers, or a set of one or more tracks with programmed track numbers. Namely, the group information table consists of group descriptors representing groups of tracks, as shown in FIG. Each group descriptor describes a start track number, an end track number, a track name and a flag relating to a given group, as shown in FIG.

The track information table describes track information, i.e. about musical works, as shown in FIGS. 46A and 46B. Namely, the track information table consists of track descriptors representing the tracks (music), as shown in FIG. 46A. Each track descriptor, as shown in FIG. 46B, contains a file pointer pointing to the audio data file of the desired track, track index number, artist name, title of the work, information about the original order of the pieces, and information about the recording time of the track. The name of the artist and the title of the work do not contain valid names, but describes information on pointers pointing to the corresponding elements in the table of names.

The name table is a table of texts that make up the actual name. As shown in FIG. 47A, the title table consists of a plurality of title positions. Each position of the name is associated with a pointer pointing to that name, and is called using this pointer. The pointer to call the name may be the name of the artist or the name of the work in the track information table, or the name of the group in the group information table. One position of a name can be called up by multiple pointers. As shown in FIG. 47B, each title position consists of title data, type of title, and association with a different title position. A title that is too long to fit in one title position can be divided into multiple title positions. Split name positions are tracked one after the other using links describing the full name.

The second exemplary embodiment of the audio data management system according to the invention works as follows: as shown in FIG. 48, the number of the track to be played first is indicated in the playback order table (see FIG. 43). With the indicated track number, access is provided through communication with the track descriptor (see FIGS. 46A and 46B) in the track information table, and the associated track descriptor is retrieved from the table. The following are read from the track descriptor: a file pointer indicating the desired audio data file, the index number of the track searched, the name of the artist, the title of the work, information about the original order of the pieces, and information about the time the track was recorded.

Based on the pointer to the audio data file, access is made to the corresponding audio data file and information from the file header is read. If the audio data is encrypted, then key information read from the header is used to decrypt the data in order to reproduce the audio data. If the index number is indicated, then the location of the indicated index number is determined from the header information, and audio data playback starts from the place of this index number.

The title position is called from the place indicated by the index of the artist’s name or the index of the title of the work, extracted from the table of information tracks. The name data is read from the called position of the name.

When it is necessary to record new audio data, in accordance with the FAT table, an unused zone consisting of at least a predetermined number of sequentially arranged recording blocks (for example, 4 recording blocks) is reserved.

When a recordable area of audio data is reserved, a new track descriptor is assigned to the track information table, and a content key is generated to encrypt this audio data. The audio input data is encrypted using the key, and an audio data file with encrypted audio data is created.

The file pointer of the newly created audio data file and key information are recorded in the newly assigned track descriptor. If necessary, the name of the artist and the name of the work are recorded in the corresponding positions of the names. In a track descriptor, pointers are described by relationships with the artist’s name and the title of the work. The number of this track descriptor is recorded in the table of the playback order, and the corresponding copyright management information is updated.

When it is necessary to reproduce audio data from a specific track, information about the indicated track number is extracted from the table of the playback order. Then, a descriptor corresponding to the track with which to reproduce the audio data is obtained.

Based on the track descriptor in the track information table, a file pointer is obtained indicating the audio data file containing the desired audio data and the index number of the desired track. Then access is made to the audio data file and key information is read from the file header. The reproduced data from the audio data file is decrypted using the key information read from the header to reproduce the audio data. If the index number is indicated, then the playback of sound data starts from the place of the indicated index number.

When it is desired to divide track “n” into track “n” and track “n + 1”, the track descriptor Dn number of the track describing the track information “n” is first obtained from the track information element TINFn in the playback order table. From the track information element TINFn + 1 in the playback order table, a descriptor number Dm describing track information “n + 1” is obtained. All actual TINF values (track descriptor numbers) following the TINFn + 1 element in the playback order table are moved forward one place.

As shown in FIG. 49, the use of an index system provides for dividing data in a single file into multiple indexed zones. Using index numbers, indexed zones are written to the header of a given audio data file. The audio data file pointer and the index number are recorded in one track descriptor Dn, and the other audio data file pointer and the other index number are recorded in another part descriptor Dm. In this case, one piece of music M1 on one track in the audio data file is clearly divided into two pieces of music M11 m12 on two tracks.

If it is desired to combine track “n” with track “n + 1” in the playback order table, then the number of the descriptor Dn of the track describing information about the track “n” is obtained from the track information element TINFn in the playback order table, and the number of the descriptor Dm of the track is obtained describing the track information “n + 1” from the TINFn + 1 item of track information in the track information table. All actual TINF values (track descriptor numbers) following the TINFn + 1 element in the playback order table are moved forward one place.

If track "n" and track "n + 1" are in the same audio data file and are separated by an index, then erasing the index information from the file header allows you to combine the tracks, as shown in Fig. 50. Thus, two pieces of music M21 and M22 on two tracks are combined into one piece of music M23 on one track.

Suppose that track "n" is the last half of the sound data file indexed, and that track "n + 1" is at the beginning of another sound data file. In this case, as shown in FIG. 51, the title is appended to the index-separated track data “n” to create an audio data file in which the music piece M32 is located. Then, the title is erased from the audio data file of the track "n + 1" carrying another piece of music M41, and the sound data of the track "n + 1" with the piece of music M41 is connected to the sound data file of the music piece M32. Thus, two pieces of music M32 and M41 are combined into one piece of music M51 on one track.

The above processes are carried out using two functions. The first function includes adding a title to each of the tracks separated by index, encrypting the track data using a different encryption key for each track, and converting the indexed audio data into a single audio data file. Another function includes erasing header information from a given audio data file and attaching the data of this file to another audio data file.

8. Work during connection with a personal computer

Next-generation MD1 and MD2 systems use the FAT system as a data management system to ensure compatibility with personal computers. Therefore, next-generation MD1 and MD2 discs can be used to record and play back not only audio data, but also general-purpose data processed using personal computers.

In the drive unit 1, audio data is reproduced as it is read from the disk 90. Given the ability of the portable drive unit 1 to access data, the audio data should preferably be recorded on the disk sequentially. In contrast, a personal computer does not take into account the continuity of this data when writing data to disk; the personal computer writes data to any free zones available on the disk.

In the recording / reproducing apparatus according to the invention, the personal computer 100 is connected to the drive unit 1 through a USB hub 7, so that the personal computer 100 can write data to a disk 90 installed in the drive unit 1. With this connection, general-purpose data is recorded under the control of the file system of the personal computer 100, while audio data is recorded under the control of the file system of the drive unit 1.

On figa and 52B shows how the control authority is transferred between the personal computer 100 and the block 1 of the drive connected to it through a USB hub 7 (not shown), depending on the type of data to be written to the disk installed in block 1 of the drive. On figa shows the transfer of general-purpose data from a personal computer 100 in block 1 of the drive for recording to disk 90 in block 1 of the drive. In this case, the file system on the side of the personal computer 100 provides control of the FAT disk 90.

It is assumed that the disk 90 is formatted using a next-generation MD1 system or a next-generation MD2 system.

From the point of view of the personal computer 100, the drive unit 1 connected to it operates clearly as a removable disk under the control of a personal computer. In this case, the personal computer 100 can write and read data to and from the disk 90 in the drive unit 1 in the same way as the personal computer writes and reads data to and from the floppy disk.

The file system of the personal computer 100 can be implemented as part of the capabilities of the operating system (OS) performed by the personal computer 100. As is well known, the operating system can be recorded as suitable program files in the hard disk drive integrated in the personal computer 100. After starting program files are read and executed by the personal computer 100 to implement the capabilities of the operating system.

On figv shows the transfer of audio data from a personal computer 100 to the block 1 of the drive for recording on the disk 90 installed in the block 1 of the drive. As an example, audio data is extracted from a hard disk drive (HDD) contained in a personal computer 100.

It is assumed that the personal computer 100 has service software for performing ATRAC compression encoding of audio data and for issuing commands to the drive unit 1 to record or erase the audio data to or from the disk 90 installed in the drive unit 1. It is also assumed that the service software is also able to access the track index file on the disk 90 installed in the drive unit 1 to view the track information recorded on the disk 90. This service software is contained, for example, in the form of program files in the drive for hard drives of a personal computer 100.

The following is a description of a typical process for transferring and recording audio data recorded on a storage medium of a personal computer 100 to a disk 90 installed in a drive unit 1. It is assumed that the specified service software has been downloaded in advance.

First, the user performs an operation on the personal computer 100 with a command to record the desired audio data (hereinafter referred to as audio data A) from his hard disk drive to the disk 90 installed in the drive unit 1. This operation starts the service software to issue a write request command, requiring the recording of audio data A to disk 90. The write request command is transmitted from the personal computer 100 to the drive unit 1.

Then, the audio data A is read from the hard drive of the personal computer 100. The extracted audio data A is subjected to an ATRAC compression encoding process using service software executed by the personal computer 100. The process converts the audio data A into ATRAC compressed data that is transmitted from the personal computer 100 to drive unit 1.

After receiving the write request command from the personal computer 100, the drive unit 1 starts receiving ATRAC compressed audio data A transmitted from the personal computer 100.

Drive unit 1 recognizes the command as a directive to record the transmitted data to disk 90 as audio data.

Namely, the drive unit 1 receives audio data A from the personal computer 100 through a USB hub 7. The received data is sent to the drive unit 2 via the USB interface 6 and the memory transfer controller 3. When audio data A is supplied to the drive drive unit 2, the system controller 9 records the drive unit A of the drive of the audio data carrier A to the disk 90 under the control of a control circuit based on the FAT of the drive unit 1. That is, the audio data A is recorded on the disk 90 sequentially with an increment of four recording blocks (64 kb × 4) based on the FAT system of the drive unit 1.

Before the write operation to the disk 90 is completed, data, status information and commands are exchanged between the personal computer 100 and the drive unit 1 in accordance with a suitable protocol. Data exchange is performed to control the data transfer rate so that no overload or underload occurs in the cluster buffer 4.

In addition to the specified write request command, the personal computer 100 may use the erase request command. The erase request command is used to request the drive unit 1 to erase the audio data from the disk 90 installed in the drive unit 1.

For example, when the personal computer 100 is connected to the drive unit 1 and the disk 90 is installed in the unit 1, then the service software reads the track index file from the drive 90. The extracted data is transferred from the drive unit 1 to the personal computer 100. Based on the received data, the personal computer 100 may, for example, display a list of names of audio data contained in the disk 90.

Assume that the user views the displayed list of names in the personal computer 1 and performs the operation of erasing certain audio data (hereinafter referred to as audio data B). In this case, information indicating the audio data B to be erased is transmitted to the drive unit 1 together with the erase request command. After receiving the request for the erase request, the drive unit 1, under its own control, erases the audio data B from the disk 90 in accordance with the request.

Since the erasure of the audio data is performed by the drive unit 1 under the control of its own FAT system, it is possible to erase the audio data from, for example, a huge file combining a plurality of audio data files, as described above with respect to FIGS. 39A and 39B.

9. Restrictions on copying audio data from disk

Copyright protection for audio data recorded on disc 90 requires the establishment of appropriate restrictions on their copying to other storage media. Consider the case where the audio data contained in the disk 90 is transferred from the drive unit 1 to a personal computer 100 for recording, for example, to a hard disk of a personal computer.

In this case, it is assumed that the disk 90 is formatted using a next-generation MD1 system or a next-generation MD2 system. It is also assumed that operations such as back copying and copying, which are described below, are performed under the control of said service software executed by the personal computer 100.

The audio data 200 stored on the disk 90 is first transferred to the personal computer 100, as shown in FIG. The “move” operation represents a sequence of actions, including copying the audio data 200 to the personal computer 100 and erasing the audio data from the original data medium (i.e., disk 90). Thus, the move operation includes erasing the data at their original location and moving the data to a new destination.

Copying is defined in this case as the operation of copying data from one data medium to another with a decrease in the count of legitimate copies (i.e., the number of times legal copying of source data is allowed) by one for this data. Backing up is defined as the operation of erasing the data to be copied from the copy destination with an increase in the legal copy count for the original data being copied by one.

When the audio data 200 is transferred to the personal computer 100, the data is sent (as the audio data 200 ′) to a storage medium such as a hard disk of the personal computer 100 for recording therein, and the audio data 200 is erased from the disk 90. Then, the personal computer 100 sets the sample 201 allowed (or specified) copies for roaming audio data 200 ', as shown in figv. In this example, the allowed copy count is set to 3, as shown by the three filled circles in the figure. The audio data 200 'is allowed to be copied from the personal computer 100 to an external storage medium a number of times equal to the set sample of allowed copies.

If the copied audio data 200 remains erased from the original disc 90, then this is inconvenient for the user. A possible inconvenience is corrected when the audio data 200 'copied from the personal computer 100 is recorded back to the disc 90.

When the audio data 200 ′ is recorded back to the original disc 90 from the personal computer 100, the countdown of the allowed copies is reduced by 1 (3-1 = 2), as shown in FIG. At this time, the audio data 200 'held by the personal computer 100 can still be legally copied 2 times and thus not erased from the personal computer 100. As a result, the audio data 200' is copied from the personal computer 100 to the disk 90 and stored therein as audio data 200 ''.

The control of the 201 allowed copy counts is performed using the copyright management information contained in the track descriptors in the track information table (see FIG. 34B). Since each track has its own track descriptor, a copy of allowed copies can be set for each track (each piece of audio data). The track descriptor copied from the disk 90 to the personal computer 100 is used as control information to control the corresponding audio data transferred to the personal computer 100.

For example, when any audio data is transferred from the disk 90 to the personal computer 100, the track descriptor corresponding to the moved audio data is copied to the personal computer 100. The personal computer 100 uses the copied track descriptor to control the audio data transferred from the disk 90. When moved audio data are recorded, for example, on the hard disk of a personal computer 100, then the specified sample 201 of allowed copies (3 in this example) is set in the control information I'm copyrighted in a track descriptor.

In addition to the allowable copy count, the copyright management information includes a hardware identifier for identifying the source copy device and a content identifier for identifying the copied content (i.e., audio data). In the installation shown in FIG. 53C, the equipment identifier of the copy destination device is checked based on the equipment identifier in the copyright management information corresponding to the audio data to be copied. If the equipment identifier in the copyright management information does not match the equipment identifier of the copy destination device, then copying is not allowed.

In the copying processes shown in FIGS. 53A-53C, the audio data contained in the disc 90 is transferred to the personal computer 100 and then recorded back to the disc 90. The procedure seems complicated from the user's point of view and can be considered a waste of time the time required to read the audio data from the disk 90 and write the same data back to the disk 90. In addition, it may seem a mistake to the user to erase the audio data, even temporary, from the disk 90.

This awkwardness can be eliminated by skipping some of the above steps after copying the audio data from the disk 90, so that the result shown in FIG. 53C is achieved in a simpler way. The following is a description of one such simplified procedure that is performed in response to a single command from a user, such as “Copy audio data with name XX from disc 90”.

(1) The specified audio data is copied from the disk 90 to the hard disk of the personal computer 100, and the audio data recorded on the disk 90 is erased by blocking a portion of the control data of the specified audio data. For example, the communication information element TINFn associated with the track descriptor corresponding to the audio data is deleted from the playing order table, and the communication information element PINFn associated with the track descriptor corresponding to the audio data is deleted from the programmed playing order table. As an alternative solution, you can erase the track descriptors themselves corresponding to the specified audio data. This stage makes the audio data on the disk 90 impossible to use after moving the data from the disk 90 to the personal computer 100.

(2) When audio data is copied to the personal computer 100 in the above step (1), track descriptors corresponding to the audio data are also copied to the hard disk of the personal computer 100.

(3) The personal computer 100 writes a predetermined sample of allowed copies (e.g., 3 times) to the copyright management information in the track descriptors corresponding to the audio data copied (i.e., transferred) from the disk 90.

(4) Based on the track descriptors copied from the disc 90, the personal computer 100 obtains a content identifier corresponding to the moved audio data. This content identifier is recorded as an index of audio data that can be subsequently backed up.

(5) Then, the personal computer 100 reduces by 1 the count of allowed copies recorded in step (3) in the copyright management information in the track descriptors corresponding to the moved audio data. In this example, the allowed copy count is reduced to 2 (= 3-1).

(6) In block 1 of the drive (not shown) in which the disk 90 is mounted, track descriptors corresponding to the moved audio data are unlocked. This is done, for example, by re-recording or restoring the TINFn and PINFn of the link information erased in step (1). In this case, previously deleted track descriptors corresponding to audio data are restored. As an alternative, the corresponding track descriptors can be transferred from the personal computer 100 to the drive unit 1 for writing to the disk 90.

Performing the above steps (1) to (6) completes the entire copying procedure. These stages provide for the copying of the desired data from the disk 90 to the personal computer 100, saving the user from unnecessary operations and protecting copyright in the audio data.

The stages (1) to (6) of copying the audio data are preferably applied to the audio data that has been recorded on the disk 90 by the user of the drive unit 1.

The back-up of the copied audio data is carried out as follows: first, the personal computer 100 searches for the desired data among the audio data recorded therein, as well as the management information, such as copyright management information in the respective track descriptors. After finding and examining the audio data and the control information, the data is backed up accordingly.

10. Next Generation MD System Compatibility

existing MD system

In the next-generation MD1 system, the same disk as that used in the existing MD system can be used, although the disk format of the next-generation MD1 system is significantly different from the disk format of the existing MD system. This leads to the need to take measures to protect the user from confusion when using disks of two formats in the same block 1 of the drive.

On Fig schematically shows the compatibility of the next generation MD1 system and the existing MD system in block 1 of the drive. Drive unit 1 corresponds to both digital and analog formats for an audio signal to be input or output.

With the digital audio signal, the next generation MD1 system 70 shown in FIG. 54 detects a “watermark” in the signal using a predetermined method, the encryption unit 72 encrypts the signal using the key information 74, and supplies the encrypted signal to the recording / reproducing unit 73. If an analog signal is supplied, then in the system 70 MD1 an analog-to-digital converter (not shown) converts the signal into a digital audio data signal, then a watermark is detected in the audio data signal, the signal is encrypted, and the encrypted signal is transmitted to the recording / reproducing unit 73. At a recording / reproducing unit 73, encrypted audio data is encoded with ATRAC compression. The encoded compressed audio data is converted to a 1-7 pp modulation format along with key information 74 before being written to disc 90 (not shown).

If the “watermark” detected in the input audio signal contains, for example, copy protection information, then the recording / reproducing unit 73 may accordingly be prohibited from performing any recording operations.

For reproducing audio data, both audio data and key information 74 are read from disc 90 using the recording / reproducing unit 73. The data is decrypted by the decryption unit 75 using the key information 74, whereby a digital audio signal is obtained. The resulting digital audio signal is converted into an analog audio signal using a digital-to-analog converter (not shown) for output. As an alternative, a digital audio signal can be output without conversion and without using a digital-to-analog converter, and a “watermark” can also be detected in the audio signal reproduced from the disc 90.

If it is determined that the detected “watermark” contains copy protection information, then the recording / reproducing unit 73 may be prohibited from correspondingly performing reproduction of the audio data.

In the existing MD system 71 shown in FIG. 54, the digital audio signal is provided with generation control information using a sequential copy management system (SCMS) before being sent to the recording / reproducing unit 76. If an analog audio signal is supplied, it is converted into a digital audio signal using an analog-to-digital converter (not shown) before being fed to the recording / reproducing unit 76. The analog audio signal is not provided with generation management information using SCMS. At a recording / reproducing unit 76, the received audio data is encoded with ATRAC compression. Encoded compressed audio data is converted to EFM format before being written to disc 90 (not shown).

To reproduce the audio data, the desired audio data is read as a digital audio signal from the disc 90 using the recording / reproducing unit 76. The digital audio signal is converted into an analog audio signal using a digital-to-analog converter (not shown) for output. As an alternative, a digital audio signal can be output without conversion and without using a digital-to-analog converter.

In the drive unit 1 described above, in which the next-generation MD1 system and the existing MD system are combined, a switch 50 is provided for explicitly switching between the operating modes of the two MD systems. In particular, the switch 50 is effectively used when audio data needs to be recorded on the disc 90.

On Fig shows the appearance of the block 1 of the portable drive type. The drive unit 1 is provided with a hinge that is located on the rear side and is not visible in FIG. The offset of the slider 52 allows the cover 54 to rotate around the hinge from the housing 55 to the open position. The disk guide appears in the hole through which the disk 90 is inserted. When the disk 90 is inserted along the guide and the cover 54 is turned to the closed position, the disk 90 is installed in the drive unit 1. When the disk 90 is installed, the drive unit 1 automatically reads information from the input zone and the U-TOC zone of the disk 90.

Telephone jack 53 serves as an output terminal for an analog audio signal. A user can connect audio playback means, such as headphones, to the telephone jack 53 to listen to audio data reproduced from the disc 90.

Although not shown in FIG. 55, the drive unit 1 is also provided with various keys for control purposes: keys for designating disc operations such as playing, recording, stopping, pausing, fast forward and rewind; keys for editing audio data and other information contained on the disk 90; and keys for entering commands and data into block 1 of the drive. These keys are located, for example, on the housing 55.

The above switch 50 is attached, for example, to the cover 54 of the drive unit 1. As shown in FIG. 55, the switch 50 is large enough and positioned so as to attract a user's attention. In the drive unit 1 shown in FIG. 55, the switch 50 is shown to switch to the “MD” position for operation in the existing MD system, or to the “next generation MD” position for operation in the next generation MD1 system.

The cover 54 is also provided with a display unit 51. The display unit 51 displays various operating states of the drive unit 1 and track information from the disk 90 installed in the unit 1. The display unit 51 also displays on-screen indications related to the operation mode set using the switch 50.

The following is a description with reference to the graphical diagram shown in Fig. 56 of the operation process of the drive unit 1 when formatting the disk 90. The stages shown in Fig. 56 are used when it is necessary to format an unused disk. In the first step S200 of FIG. 56, the disk 90 of the existing MD system is installed in the drive unit 1. With the disk 90 installed, the process proceeds to step S201, in which information from the input zone is first read, and then from the U-TOC zone on the disk 90.

In step S202, a check is made to see if, using the switch 50, the operating mode of the drive unit 1 is set for the existing MD system or for the next generation MD1 system. If it is determined in step S202 that the operating mode for the existing MD system is set, then the process proceeds to step S203. At step S203, the installed disk 90 is defined as the disk used in the existing MD system without the need for additional formatting, which is characteristic of the existing MD system. Then, the display unit 51 indicates on the screen that the disk 90 is an empty disk.

If it is determined in step S202 that the operating mode is set for the next generation system MD1, then the process proceeds to step S204. In step S204, the display unit 51 shows that the disk 90 is an empty disk, for example, for a few seconds before the process automatically proceeds to step S205.

In step S205, the display unit 51 displays a message asking the user whether or not to continue formatting the disk 90. If the user gives a command indicating the need to format the disk 90, the process proceeds to step S206. For example, the command is entered into the drive unit 1 by the user using the corresponding key on the housing 55 of the drive unit 1.

In step S206, the drive unit 1 performs a disk formatting process for the next-generation MD1 system as described with reference to the graphic circuit in FIG. 18. During formatting of the disk 90, the display unit 51 should preferably indicate that a formatting process is being performed. After completion of the formatting process in step S206, the process proceeds to step S207. In step S207, the display unit 51 issues a message that the installed disc 90 is the next generation blank disc MD1.

If at step S205 the user instructs that the disk 90 should not be formatted, the process proceeds from step S205 to step S208. In step S208, the display unit 51 instructs the user to set the switch 50 to the operating mode of the existing MD system in the drive unit 1. In step S209, after a predetermined period of time, a check is made to see if the position of the switch 50 remains unchanged, despite the indication of the display unit 51. If it is determined in step S209 that the position of the switch 50 has not changed, this is evaluated as a break and the process goes back to step S205.

On Fig shows another graphical diagram of the stages performed in block 1 of the drive when formatting a new disk 90 installed in it. In step S300 of FIG. 57, an empty (unused) disk 90 is installed in the drive unit 1. In step S301, information from the input zone and the U-TOC of the disk 90 is first read. In step S302, based on the received U-TOC information, the display unit 51 indicates that the installed disk 90 is an empty disk.

In step S303, a record key (not shown) is actuated in block 1 of the drive to give a command to write data to disk 90 in block 1 of the drive. A write command can be sent to drive unit 1 not only by activating the write key of unit 1, but also from a personal computer 100 connected to drive unit 1.

After the write command is sent to the drive unit 1 in step S303, the process proceeds to step S304. In step S304, it is checked whether the operating mode of the drive unit 1 is set using the switch 50 for the next generation MD1 system or for the existing MD system. If it is determined in step S304 that the operating mode of the drive unit 1 is set for the existing MD system, the process proceeds to step S306. At step S306, the process of writing the existing MD system to disc 90 begins.

If it is determined in step S304 that the operating mode of the drive unit 1 is set using the switch 50 for the next generation system MD1, the process proceeds to step S305. In step S305, the disk is formatted by the next generation MD1 system in accordance with the procedure described in relation to FIG. Step S305 is followed by step S306, in which the process of writing the next generation MD1 system to the formatted disc 90 begins.

The following is a description with reference to the graphical diagram shown in Fig. 58 of the operation process of the drive unit 1 when recording audio data to the disk 90. The process varies depending on whether the operating mode of the drive unit 1 corresponds to the type of the disk 90, i.e. Is drive 90 formatted with next-generation MD1?

In the first step S210 in FIG. 58, the disk 90 is mounted in the drive unit 1. When the disk 90 is installed, the process proceeds to step S211, in which information from the input zone and the U-TOC zone of the disk 90 is first read.

Based on the extracted U-TOC information, in step S212, it is checked whether the installed disc has a next-generation MD1 system format or an existing MD system format. A check is performed, for example, based on whether FAT data has been extracted from the U-TOC zone. Alternatively, a check can be performed based on whether the location of the start of the warning track has been found in the U-TOC.

In step S213, the display unit indicates the type of disc determined in step S212. In step S214, the display unit 51 shows the status of the installed disc 90 in accordance with the information read from the U-TOC zone. For example, the display unit 51 indicates that the installed disk 90 is an empty disk. If the disc 90 is not an empty disc, then the disc name and track name information are displayed. At step S215, the rotation of the disc is stopped.

In step S216, it is checked whether the disc type determined in step S212 corresponds to the operating mode of the drive unit 1 set with the switch 50. If so, the process proceeds to step S217.

Namely, the process goes to step S217 in two cases: when it is determined that the switch 50 is set to the operating mode of the existing MD system, and the installed disk 90 is the disk of the existing MD system, on the one hand; and when it is determined that the switch 50 is set to the next generation MD1 system, and the installed disk 90 has the next generation system MD1 format, on the other hand.

In step S 217, data from the disc 90 can be recorded or reproduced. Information in the U-TOC area of the disc 90 can also be edited.

At the same time, depending on the type of disk determined in step S212, the system controller 9 issues a command to the media drive unit 2, using the switch 26, of the appropriate signal path in accordance with the modulation system for this type of disk. This provides the ability to automatically switch demodulation formats between the next-generation MD1 system and the existing MD system for reproducing audio data. Similarly, file systems are also switched between the next-generation MD1 system and the existing MD system under the control of the system controller 9 based on the type of disk.

In step S216, it can be determined that the disc type determined in step S212 does not correspond to the operation mode of the drive unit 1 set by the switch 50. In this case, step S216 is followed by step S219.

Namely, the process goes to step S219 in two cases: when it is determined that the switch 50 is set to the operating mode of the existing MD system, and the installed disk 90 has the format of the next generation MD1 system, on the one hand; and when it is determined that the switch 50 is set to the next generation MD1 system, and the installed disk 90 has the format of the existing MD system, on the other hand.

In step S219, it is checked which operation is performed by the user on the disk 90. If it is determined in step S219 that the user intends to perform the operation of reproducing (“PB”) the audio data from the disk 90, the process proceeds to step S220. In step S220, audio data is reproduced from the disc 90 in accordance with a user command.

That is, even if the disc type does not correspond to the operating mode of the drive unit 1 set by the switch 50, it is possible to reproduce audio data recorded on the disk 90, regardless of the position of the switch 50.

Namely, depending on the type of disk determined in step S212, the system controller 9 ensures that the drive unit 2 selects a suitable signal path corresponding to the modulation system of this type of disk using the switch 26. This provides the ability to automatically switch demodulation formats between the next-generation MD1 system and the existing MD system for reproducing audio data. File systems are also switched between the next-generation MD1 system and the existing MD system under the control of the system controller 9 based on the type of disk.

If it is determined in step S219 that the user has selected the operation of recording (“REC”) the audio data to the disc 90 or erasing or editing (“EDIT”) the audio data recorded on the disk 90, the process proceeds to step S218. At step S218, a warning message appears on the display unit indicating that the type of disc 90 does not correspond to the operating mode of the drive unit 1. A message is also displayed indicating that the recording is not possible if the user has designated the recording, or that editing is not possible if the user has specified editing.

If, in step S219, the user attempts to update the U-TOC zone in the editing operation during the playback of audio data, the display unit 51 displays two messages: that the type of the disk 90 does not correspond to the operating mode of the drive unit 1 and that editing is not possible at this stage.

That is, when the disc type does not correspond to the operating mode of the drive unit 1 set by the switch 50, the operation of modifying the information recorded on the disc 90 is not allowed.

The following is a description of the process of changing the format of the disk 90. On the disk 90, you can change the format of the next-generation MD1 system to the format of the existing MD system and vice versa.

On Fig shows a graphical diagram of the stages of switching from the disk format of the next generation MD1 system to the disk format of the existing MD system on the disk 90. It is assumed that the switch 50 is pre-set to the operating mode of the next generation MD1 system.

In the first step S230 of FIG. 59, the disk 90 is mounted in the drive unit 1. With the disk 90 installed, the process proceeds to step S231, in which information is first read from the input zone and the U-TOC of the disk 90. In step S232, it is recognized that the installed disk is formatted using the next generation MD1 system. At step S233, the rotation of the disk 90 is stopped.

In step S234, all data recorded and managed by the FAT system is erased from the disk 90. For example, the user performs an editing operation on the data recorded by the FAT control scheme on the disk 90 and selects the erase all data operation ("ALL ERASE" among the editing alternatives) ) In step S234, the display unit 51 preferably displays a message asking the user to confirm his intention to really erase all data from the disk 90.

After erasing all the data recorded by the FAT control circuit from the disk 90 in accordance with the user command, the process proceeds to step S235. At step S235, a message appears on the display unit 51 indicating that the installed disk has become an empty disk.

Step S235 is followed by step S236, in which the user activates a switch 50 to set the operation mode of the drive unit 1 for the existing MD system. In step S237, information from the U-TOC zone of the installed disk 90 is read. In step S238, the disk 90 is recognized as a disk formatted using the next generation MD1 system.

At step S239, a message appears on the display unit 51 stating that the installed disk is an empty disk of the next generation system MD1. A message also appears on the display unit 51, asking the user whether to cancel the next-generation MD1 system format. Canceling the next-generation MD1 system format means switching from the next-generation MD1 system disk format to the existing MD system's disk format on the installed drive 90.

If it is determined in step S239 that the user has selected the disc format cancellation operation, the process proceeds to step S240. In step S240, the next generation MD1 system format is canceled on the disk 90. For example, the disc format is canceled by erasing the FAT information from the U-TOC zone, as well as the warning track. As an alternative, the next-generation MD1 system format can be canceled by erasing the FAT non-information, but only the warning track.

If it is determined in step S239 that the user has not performed the disc format cancellation operation, the process proceeds to step S241. In step S241, a message appears on the display unit 51, requiring the user to activate the switch 50 to set the drive unit 1 to the operating mode of the next generation system MD1.

In step S242, it is checked whether the user has performed the operation of setting the drive unit 1 to the next generation MD1 system in operation for a predetermined period of time. If the corresponding operation is performed within a predetermined period of time, the process proceeds to step S243, in which the process ends, and the installed disk 90 becomes usable as an empty disk formatted using the next generation MD1 system. If, in step S242, the setting of the switch 50 is not completed within a predetermined period of time, then a break is recognized and control returns to step S239.

Switching from the disk format of the existing MD system to the disk format of the next generation MD1 system is as follows: first, the switch 50 is activated to set the drive unit 1 to the operating mode of the existing MD system. The operation of erasing from the disk 90 all the audio data recorded in the format of the existing MD system is performed. Then, the disk 90 is formatted again using the next-generation MD1 system as described in relation to FIG. 18.

Using the above characteristics, the method and device according to the invention enables the effective management of audio data under the control of the FAT system using a data carrier whose characteristics are equivalent to those of an existing MD system.

Although a description is given of a preferred embodiment of the invention using specific concepts, this description is for illustrative purposes only, and changes and variations are possible without departing from the idea and scope of the following claims.

This document contains an object associated with the object disclosed in Japanese Patent Application P2002-099277 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190812 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099294 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190811 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099274 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190804 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099278 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190805 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099276 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190808 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099296 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190809 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099272 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190802 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099271 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190803 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099270 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190578 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099273 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190810 filed with the Japanese Patent Office on June 28, 2002; Japanese Patent Application P2002-099279 filed with the Japanese Patent Office on April 1, 2002; Japanese Patent Application P2002-190801 filed with the Japanese Patent Office on June 28, 2002, the entire contents of which are incorporated herein.

Claims (6)

1. The recording method containing stage detecting unique information on the recording medium recorded outside a predetermined area controlled by control data that manage data in the data area on the recording medium; generating unique information when no unique information recorded on the recording medium is detected in the detection stage; and recording unique information generated at the generation stage onto a storage medium outside an area controlled by control data. 2. The recording method according to claim 1, characterized in that it further comprises the step of generating unique information when, at the detection stage, it is found that the unique information is not recorded on the recording medium. 3. The recording method according to claim 1, characterized in that the recording medium comprises a control table configured to control a replacement zone for the damaged zone in the data zone on the recording medium; and further comprises the step of writing unique information to the management table. 4. The recording method according to claim 3, characterized in that it further comprises stages reading a unique identifier from the recording medium and temporarily storing the unique information in memory when the unique information is recorded in a predetermined location on the recording medium or in the specified management table; and writing specified unique information stored in memory to the management table. 5. The recording method according to claim 1, characterized in that it further comprises the step of recording unique information upon initialization of the recording medium. 6. The recording method according to claim 1, characterized in that it further comprises the step of managing data in a data area on a recording medium using a file allocation table system, wherein the management data includes a file allocation table.

Images