WO2004109687A1

WO2004109687A1 - File transmission system and file transmission method

Info

Publication number: WO2004109687A1
Application number: PCT/JP2004/008296
Authority: WO
Inventors: Takashi Kawakami
Original assignee: Sony Corporation
Priority date: 2003-06-09
Filing date: 2004-06-08
Publication date: 2004-12-16
Also published as: US20060161584A1; JP2005025729A; KR20060059850A

Abstract

It is possible to effectively and easily perform content management and use. A disc ID database composed of information related to disc ID unique for each disc is built in advance. The disc ID database is updated when an unregistered new disc is used or when check out or check in is performed. When ripping a CD or the like, the disc of check out reservation is specified in correlation with the disc ID registered in the disc ID database. After the check out reservation is complete, check out is automatically performed when the disc having the disc ID used for the reservation is connected. Thus, it is possible to effectively and easily perform content management and use.

Description

Specification

File transfer system and file transfer method

The present invention relates to a file transfer system and a file transfer method, and more particularly to a file transfer system and a file transfer method for transferring information such as music and video. Background art

In recent years, a portable recording / reproducing apparatus for recording / reproducing music or the like, which has a built-in hard disk drive and is extremely small in size, has appeared. Such a portable recording / reproducing apparatus usually manages recorded music data by connecting to a personal computer.

For example, a library is constructed by storing a large amount of music data in a hard disk drive of a personal computer, and a music server is configured by a personal computer. Music data is generally acquired by ripping from a CD (Compact Disc) or downloading from a network using a music distribution system deployed on a network such as the Inuichi Net. It is a target.

A cable is connected between the personal computer and the portable recording / reproducing apparatus, and the music data stored in the library of the personal computer is transferred to the portable recording / reproducing apparatus. In a portable recording / reproducing apparatus, the transferred music data is recorded on a built-in hard disk drive. By carrying a portable recording / reproducing device, a user can transfer music data stored in a library configured in a personal convenience store, for example, to a store. You can enjoy it outside.

Various proposals have been made to make such an environment more comfortable. For example, Japanese Unexamined Patent Application Publication No. 2003-77214 discloses a personal computer that executes a program for managing content such as music, based on an external device ID and a media ID using a memory card as an example. It describes that data related to content is automatically stored from a computer to a portable device that uses the content.

Japanese Patent Application Laid-Open No. 2003-29795 describes that information about music is transferred from a personal computer to a digital memory player based on the memory capacity of the digital memory player and the ID of the memory. Is described.

On the other hand, as a recording medium for recording and reproducing digital audio data, a mini disk (MD), which is a magneto-optical disk having a diameter of 64 mm, housed in a cartridge, is widely used. In the MD system, ATRAC (Adaptive TRansform Acoustic Coding) is used as a compression method for audio data, and U-TOC (User TOC (Table Of Contents)) is used for music data management. That is, a recording area called U-T〇C is provided on the inner periphery of the disk recordable area. U—TOC is management information that can be rewritten in the current MD system in accordance with the order of tracks (audio tracks / data tracks), recording, erasing, etc. For each track or its constituent parts, It manages the start position, end position, and mode.

In the MD system, a file system based on the FAT (File Allocation Table) that is common in personal computers is thus described. Since it uses a different file management method, it was not compatible with a data recording management system of a general-purpose computer such as a personal computer. Therefore, a system has been proposed in which a general-purpose management system such as a FAT system is introduced to enhance compatibility with personal computers.

Such a portable recording / reproducing apparatus using a disc in consideration of compatibility with a personal computer as a recording medium is connected to a music server using a personal computer as described above, and a library in the music server is connected. Recording on a disk is conceivable.

Here, the disk of the current MD system has a recording capacity of about 160 MB, but as described above, using a disk with an increased recording capacity while ensuring compatibility with the current MD. It is thought that it is possible to realize the same function as a portable recording / reproducing device using a hard disk drive. In order to increase the capacity of disks in current MD systems, it is necessary to improve the laser wavelength and the numerical aperture NA of the optical head. However, there is a limit in improving the laser wavelength and the numerical aperture NA of the optical head. For this reason, systems for increasing the capacity using technologies such as magnetic super-resolution have been proposed.

By the way, when a personal computer is used as a music server as described above and music data is transferred from a personal computer to a portable recording / reproducing device, music data is downloaded by CD riving or downloading from a network. It requires the work of importing an evening into a personal computer and the work of checking the imported music data into a portable recording / reproducing device.

Devices such as portable recording / reproducing devices and recording media, which are the checkout destinations for music data, are usually small in size, so they can be used in a corner or in a corner of a room. Sometimes you can't find it. Therefore, the work of importing music data and the check-out of music data could not be completed at once, resulting in a problem that the operation was performed twice and the efficiency was low. For example, when the portable recording / reproducing apparatus uses the above-mentioned MD system disc as a recording medium, music data newly imported from the personal computer to the portable recording / reproducing apparatus is automatically checked. If you do so, you will have various genres of music on the same disc. Therefore, if the number of music data that can be checked out to a portable recording / reproducing apparatus on a personal computer increases, the management and use of the music data becomes complicated. Disclosure of the invention

Therefore, an object of the present invention is to provide a file transfer system and a file transfer method that can efficiently and easily manage and use contents.

In order to achieve the above object, the present invention provides a file transfer system for transferring content data recorded on a first recording medium to a second recording medium. Recording / reproducing device that reproduces data from the recording medium 2, a content supply device that supplies the content data, and content data that outputs the content data supplied from the content data supplying device to the recording / reproducing device. A recording device for recording the content data supplied from the content data supply device on the first recording medium in association with a different content identifier for each content data; and a content identification device. The code supplied in association with the identifier and the different recording medium identifier provided for each second recording medium. Tentsude management recording on the second recording medium Isseki Transfer management information updating means for updating the transfer management information to perform the transfer management information, and a recording medium identifier of the second recording medium attached to the recording / reproducing apparatus to be reproduced by the recording / reproducing apparatus. A file transfer system comprising: control means for controlling transfer of content data to a recording / reproducing device so that content data recorded on one recording medium is recorded on a second recording medium.

The present invention also relates to a file transfer method for transferring content data recorded on a first recording medium to a second recording medium, wherein the content data supplied from the content supply device is different for each content data. The content data is recorded on the first recording medium in association with the identifier, and the content data supplied in association with the content identifier and a recording medium identifier for identifying a different second recording medium provided for each second recording medium. The transfer management information for managing the recording on the second recording medium in the evening is updated, and the recording is performed on the first recording medium based on the received recording medium identifier and the transfer management information of the second recording medium. This is a file transfer method for controlling transfer of content data to a recording / reproducing device so that the content data is recorded on a second recording medium.

As described above, according to the present invention, the content data recorded on the first recording medium is recorded on the second recording medium based on the received recording medium identifier of the second recording medium and the transfer management information. The content data can be easily transferred by controlling the transfer of the content to the recording / reproducing apparatus in such a manner. Also, the transfer management information can be updated in parallel with the recording of the content data on the first recording medium. That is, according to the present invention, when introducing new content and storing it in the second recording medium, the transfer management information updating means reserves the checkout using a different recording medium identifier for each recording medium. With Therefore, when the recording medium of the recording medium identifier used at the time of the reservation is connected, it is possible to automatically perform a check-out on the recording medium. In addition, since the checkout to the second recording medium can be performed using a different recording medium identifier for each recording medium, the content can be easily managed.

Therefore, introduction of new contents and designation of a recording medium of a checkout destination can be performed at the same time, and there is an effect that the management and use of contents such as audio data can be performed efficiently and easily. BRIEF DESCRIPTION OF THE FIGURES

Fig. 1 is a diagram used to describe the disk of the next-generation MD1 system specification, Fig. 2 is a diagram used to describe the recording area of the disk of the next-generation MD1 system specification, Figs. 3A and 3 Figure B is a diagram used to describe the disk for the next-generation MD2 system specification, Figure 4 is a diagram used to describe the recording area of the disk in the next-generation MD2 system specification, and Figure 5 is an example of the UID FIG. 6 is a schematic diagram schematically illustrating the format of the next-generation MD 1 and the next-generation MD 1, and FIG. 7 is a diagram used to explain the error correction encoding process of the next-generation MD 1. Fig. 8 is used to explain the error correction encoding process of the next generation MD 2, Fig. 8 is a diagram used to explain the error correction encoding process of the next generation MD 1 and MD 2, and Fig. 9 is A perspective view used to explain the generation of the address signal, and FIG. 10 shows the current MD system and Diagram used to explain the AD IP signal of the next-generation MD 1 system, Fig. 11 shows the diagram used to describe the AD IP signal of the current MD system and the next-generation MD 1 system, and Fig. 12 shows the next-generation MD 2 system. Figure used to explain the AD IP signal of Fig. 13, Fig. 13 is a figure used to explain the AD IP signal of the next-generation MD2 system Fig. 14 shows the relationship between ADIP signals and frames in the current MD system and the next-generation MD1 system. Fig. 15 shows the relationship between ADIP signals and frames in the next-generation MD1 system. Fig. 16 is a diagram used to explain control signals in the next-generation MD2 system, Fig. 17 is a block diagram of a disk drive, and Fig. 18 is a block diagram of the media drive. FIG. 19 is a block diagram showing the configuration, FIG. 19 is a flowchart showing an example of a disk initialization process by the next-generation MD 1, and FIG. 20 is a flowchart showing an example of a disk initialization process by the next-generation MD 2. Fig. 21 is used to explain the first example of the audio data management method, and Fig. 22 is used to explain the audio data file according to the first example of the audio data management method. Figure, Figure 23, Audio FIG. 24 is a diagram used for describing a track index file according to the first example of the data management method. FIG. 24 is a diagram used for describing a play order table according to the first example of the audio data management method. Fig. 5 is a diagram used to explain the programmed play order table according to the first example for the audio data management method. Figs. 26A and 26B are diagrams according to the first example of the audio data management method. FIG. 27A and FIG. 27B are diagrams used to explain the group information table, and FIG. 28A is a diagram used to explain the track information table according to the first example of the audio data management method. And Fig. 28B are diagrams used to explain the parts information table according to the first example of the audio data management method. Figs. 29A and 29B are FIG. 30 is a diagram illustrating a name table according to a first example of the audio data management method. FIG. 30 is a diagram illustrating an example of a process according to the first example of the audio data management method. The figure is for explaining that multiple name slots in the name table can be referred to. Fig. 32A and Fig. 32B are for the audio data management method. 200 A diagram used to explain the process of deleting parts from an audio data file in the first example. Fig. 33 is a diagram used to explain a second example of the audio data management system. The figure shows the structure of the audio data file according to the second example of the audio data management method. Fig. 35 shows the description of the track index file according to the second example of the audio data management method. Fig. 36 is a diagram used to explain the play order table according to the second example of the audio data management method, and Fig. 37 is a program play order according to the second example of the audio data management method. FIGS. 38A and 38B are used to explain the table, FIG. 38A and FIG. 38B are used to explain the group information table according to the second example of the audio data management method, and FIG. Figure A And Fig. 39B is a diagram used to explain the track information table according to the second example of the audio data management method. Figs. 40A and 40B are the second diagram of the audio data management method. Diagram used to explain the name table according to the example. Fig. 41 is a diagram illustrating an example of processing according to the second example of the audio data management system. Fig. 42 is a diagram illustrating the audio data management system. Fig. 43 is a diagram for explaining that data of one file is divided into a plurality of index areas by an index, and Fig. 43 is a diagram of a second example of an audio data management method. Fig. 44 is a diagram used to explain the connection of tracks, Fig. 44 is a second example of the audio data management method, and Fig. 45 is a diagram used to explain the connection of tracks by another method. Figure B shows par A diagram for explaining that the management authority is transferred according to the type of data to be written while the narcomputer is connected to the disk drive. FIG. 46 is a sequence of audio data checkpoints. FIG. 47 is a schematic diagram showing an example of a software configuration applicable to an embodiment of the present invention, and FIGS. 48A and 48B are Juke models. FIG. 49 is a schematic diagram illustrating an example of a configuration of a database managed by the W-box application. FIG. 49 is an example of processing performed when ripping is performed by an example of software applicable to an embodiment of the present invention. FIG. 50 is a flowchart showing an example of processing of a reservation check by an example software applicable to an embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, an embodiment of the present invention will be described. First, prior to the description of an embodiment of the present invention, a disk system applicable to the present invention will be described in accordance with the following 10 section.

1. Outline of recording method

2. About the disc,

3. Signal format

4. Configuration of recording and playback device

5. Disk initialization processing by next-generation MD1 and MD2

6. About the first management method of music data

7. Second example of music data management method

8. Operation when connecting to a personal computer

9. Restrictions on Copying Audio Data Recorded on Disc 10. Software Configuration

1. Outline of recording method

In one embodiment of the present invention, a magneto-optical disk is used as a recording medium. The physical attributes of the disc, such as the form factor, are substantially the same as the disc used by the so-called MD (mini-disc) system. The same. However, the data recorded on the disk and how the data is arranged on the disk differ from the conventional MD.

More specifically, an apparatus applied to an embodiment of the present invention includes a FAT (File Allocation Table) system as a file management system for recording and reproducing content data such as audio data. I use it. This ensures that the device is compatible with the file system used in current personal computers.

As used herein, the term "FAT" or "FAT system" is used generically to refer to various PC-based file systems, and refers to the specific FAT base used in the Disk Operating System (DS). File system, VFAT (Virtual FAT) used in Windows 95/98, FAT 32 and NT FS (NT File) used in Windows 98 / ME / 2000. System (also called the New Technology File System))). NTFS is a Windows NT operating system, or (optionally) a file system used in Windows 2000, which records and retrieves files when reading and writing to disk.

Further, in one embodiment of the present invention, by improving the error correction method and the modulation method with respect to the current MD system, the data recording capacity is increased and the data reliability is improved. I have. Further, in this embodiment, the content data is encrypted, and illegal copy is prevented, so that the copyright of the content data can be protected. The format for recording and playback is the next-generation MD1 specification that uses a disk (ie, physical medium) that is exactly the same as the disk used in the current MD system, and the format used in the current MD system Although the disk has the same form factor and outer shape, the use of magnetic super resolution (MSR) technology has increased the recording density in the linear recording direction and increased the recording capacity of next-generation MD2 specifications. And these have been developed by the present inventor.

In the current MD system, a magneto-optical disk with a diameter of 64 mm stored in a cartridge is used as a recording medium. The thickness of the disc is 1.2 mm, and a center hole with a diameter of 11 mm is provided in the center. The shape of the cartridge is 68mm in length, 72mm in width and 5mm in thickness.

The shape of these discs and the shape of the cartridge are all the same regardless of the specifications of the next-generation MD1 and the specifications of the next-generation MD2. Regarding the start position of the lead-in area, the disks of the next-generation MD 1 specification and the next-generation MD 2 specification also start at a position 29 mm from the center of the disk and are the same as the disks used in the current MD system It is.

For the next-generation MD2, the track pitch is under consideration from 1.2 m to 1.3 m (eg, 1.25 m). On the other hand, the track pitch of the next-generation MD1, which uses the disc of the current MD system, is 1.6 m. The bit length of the next-generation MD1 is 0.44 mZ bits, and that of the next-generation MD2 is 0.16 m / bit. The redundancy is 20.5% for both next-generation MD1 and next-generation MD2.

For next-generation MD2 discs, magnetic super-resolution technology is used to increase the recording capacity in the linear density direction. Magnetic super-resolution technology At a certain temperature, the cutting layer becomes magnetically neutral, and the domain wall transferred to the reproducing layer moves, so that the minute mark becomes large in the beam spot. It is a thing using. That is, in a next-generation MD2 disc, a magnetic layer serving as at least a recording layer for recording information, a cutting layer, and a magnetic layer for reproducing information are laminated on a transparent substrate. The cutting layer becomes a layer for adjusting the exchange coupling force. At a predetermined temperature, the cutting layer becomes magnetically neutral, and the domain wall transferred to the recording layer is transferred to the magnetic layer for reproduction. As a result, minute marks can be seen in the beam spot. At the time of recording, a minute mark can be generated by using a laser pulse magnetic field modulation technique.

Also, in the next-generation MD2 specification disc, the group is deeper than the conventional MD disc in order to improve detrack magazine, crosstalk from the land, crosstalk of wobble signals, and focus leakage. The slope of the is increased. In the next-generation MD2 specification disc, the group depth is, for example, 160 nm to 180 nm, the group inclination is, for example, 60 degrees to 70 degrees, and the group width is, for example, 6 degrees. It is from 0 nm to 700 nm.

Regarding optical specifications, in the specifications of the next-generation MD1, the laser wavelength λ is set at 780 nm, and the numerical aperture NA of the objective lens of the optical head is set at 0.45. Similarly, the specifications of the next-generation MD 2 also specify that the laser wavelength λ is 78 O nm and the numerical aperture NA of the optical head is 0.45.

As the recording method, both the next-generation MD1 specification and the next-generation MD2 specification adopt the group recording method. That is, a group of grooves formed on the disk surface is used as a track for recording and reproduction. As the error correction coding method, in the current MD system, the extension code based on AC IRC (Advanced Cross Interleave Reed-Solomon Code) was used, but in the specifications of the next-generation MD 1 and next-generation MD 2, In addition, a block complete type code combining RS-LDC (Reed Solomon-Long Distance Code) and BIS (Burst Indicator Subcode) is used. The adoption of a block-completed error correction code eliminates the need for a linking sector. With the error correction method that combines LDC and BIS, when a burst error occurs, the BIS can detect the error location. Using this error location, erasure correction can be performed by LDC code.

As an address system, a single spiral group is formed, and then a double-glued single system in which a double as address information is formed on both sides of the group is adopted. Such an address system is called ADIP (Address in Pregroove). The line density differs between the current MD system and the specifications of the next-generation MD1 and next-generation MD2, and the current MD system uses a convolution code called AC IRC as an error correction code. In contrast, the next-generation MD1 and next-generation MD2 specifications use block-completed codes that combine LDC and BIS, resulting in different levels of redundancy, and a difference between ADIP and data. The relative positional relationship has changed. Therefore, the specification of the next-generation MD1, which uses a disk with the same physical structure as that of the current MD system, handles the ADIP signal differently from that of the current MD system. In the specifications of the next-generation MD2, the specifications of the ADIP signal have been changed so as to be more consistent with the specifications of the next-generation MD2.

Regarding the modulation method, while the current MD system uses EFM (8 to 14 Modulation), the next-generation MD1 and next-generation MD1 are used. The specification 2 adopts RLL (1, 7) PP (RL L; Run Length Limited, PP '' Parity Preserve / Prohibit rmtr (repeat ed minimum transition runlength)), which is referred to as 11 pp modulation. . The data detection method is the Viterbi decoding method using the partial response PR (1, 2, 1) ML in the next-generation MD 1 and the PR (1, 1, 1) ML in the next-generation MD 2. ing.

The disk drive method is CLV (Constant Linear Verocity) or ZCAV (Zone Constant Angular Verocity), and its standard linear velocity is 2.4 m / s in the next-generation MD 1 specification, According to the specification, it is 1.98mZ seconds. According to the specifications of the current MD system, it is 1.2 msec for a 60-minute disc and 1.4 mZ for a 74-minute disc.

According to the specifications of the next-generation MD1, which uses the disk used in the current MD system as it is, the total recording capacity per disk per disk is approximately 300 M when using a disk called an 80-minute disk. Bytes (when using an 80-minute disc). Since the modulation method is changed from EFM to 1–7 pp modulation, the window margin changes from 0.5 to 0.666. In this regard, a 1.33-fold higher density can be realized. In addition, by using BIS and LDC in combination with the ACIRC method as the error correction method, data efficiency is increased, and in this regard, 1.48 times higher density can be realized. Overall, the data capacity is about twice that of the current MD system using exactly the same disk.

Next-generation MD2 discs that use magnetic super-resolution will have even higher densities in the linear density direction, and the total data storage capacity will be about 1 GB.

The data rate is the standard linear speed, and the next-generation MD1 has a 4.4 Mbit Second-generation MD2, which is 9.8 Mbit / s.

2. About discs

Fig. 1 shows the structure of the next-generation MD1 disc. The next-generation MD1 disc is a direct copy of the current MD system disc. That is, the disk is formed by laminating a dielectric film, a magnetic film, a dielectric film, and a reflective film on a transparent poly-polycarbonate substrate. Further, a protective film is laminated thereon.

As shown in Fig. 1, in the next-generation MD1 disc, P-T〇C (Plymouth Table TOC (Table Of Contents)) is placed in the lead-in area on the innermost circumference of the recording area of the disc. An area is provided. The innermost circumference of this recording area is the innermost in a direction radially extending from the center of the disk. This is a pre-mastered area as a physical structure. In other words, control information and the like are recorded as embossed pits, for example, as P-TOC information.

The outer periphery of the lead-in area where the P-TOC area is provided is a recordable area, which is a recording / reproducing area in which groups are formed as guide grooves for recording tracks. A U-TOC (user TOC) is provided on the inner periphery of the recordable area. Here, the outer circumference is an outer circumference in a direction radially extending from the center of the disk. The recordable area is an area where magneto-optical recording is possible.

The U-T〇C has the same configuration as the U-TOC used to record disc management information in the current MD system. U—TOC is management information that can be rewritten in the current MD system in accordance with the track order, recording, and erasure of tracks. The start position, end position, and mode of each track and its constituent parts are specified. It is managed. Here, a track is an audio track and a no or data track. W collectively refers to racks.

An alert track is provided around the U-TOC. This track contains an audible alert that is activated and output by the MD player when the disc is loaded into the current MD system. This beep indicates that the disc is being used in the next generation MD1 format and cannot be played on current systems. The remaining part of the recordable area extends in a radially extending direction to the lead-out area. Details of the rest of the recordable area are shown in Figure 2. Fig. 2 shows the structure of the recordable area of the disc of the next-generation MD1 shown in Fig. 1. As shown in Fig. 2, a U-TOC and an alert track are provided at the head located on the inner peripheral side of the recordable area. The area that includes the U-TOC and alert track is recorded with EFM data modulation so that it can be played back on current MD system players. On the outer periphery of the area where data is modulated and recorded by EFM modulation, there is provided an area where data is modulated and recorded by 117 pp modulation of the next-generation MD1 system. The area where data is modulated and recorded by EFM and the area where data is modulated and recorded by 1-7 pp modulation are separated by a predetermined distance, and a “guard band” is provided. It has been done. With such a guard band, it is possible to prevent the current MD player from being mounted with a next-generation MD1 disc and causing problems.

A DDT (Disc Description Table) area and a reserved track are provided on the inner peripheral side, which is the head of the area where data is modulated by the 17 pp modulation and recorded. The DDT area is provided to perform replacement processing for a physically defective area. In the DDT area, an identification code unique to each disc is further recorded. Hereafter, a unique identification for each disc The code is called UID (Unique ID). In the case of the next-generation MD1, the UID is generated based on, for example, a randomly generated random number, and is recorded, for example, when the disk is initialized. Details will be described later. By using the UID, it is possible to perform security management on the recorded contents of the disk. The reserve track stores information for protecting the content. Further, a FAT (File Allocation Table) area is provided in an area where data is modulated and recorded by 117 pp modulation. The FAT area is an area for managing data in the FAT system. The FAT system performs data management based on the FAT system used in general-purpose personal computers. The FAT system performs file management by a FAT chain using a directory indicating an entry point of a file or directory at a root and a FAT table in which connection information of a FAT class is described. Note that the term FAT is used generically to refer to the different file management methods used in PC operating systems, as described above. In the next-generation MD1 specification disc, the U-TOC area contains information on the start position of the alert track and information on the start position of the area where data is modulated and recorded using 17 pp modulation. Is recorded.

When the next-generation MD1 disc is loaded into the player of the current MD system, the U-TOC area is read, the alert track position is determined from the U-TOC information, and the alert track is accessed. The alert track starts playing. The alert track contains a warning sound that indicates that this disc is used in the next-generation MD1 format and cannot be played on current MD system players. This alert sounds that the disc cannot be used with current MD system players. Note that the warning sound may be a warning in a language such as "Not available for this player". Of course, a simple beep, tone, or other warning signal may be used.

When a next-generation MD1 disc is loaded into a player that complies with the next-generation MD1, the U—TOC area is read, and data is recorded using the U—T〇C information with a 17-PP modulation. The start position of the area is known, and the DDT, reserve track, and FAT area are read. In the data area of l—7 pp modulation, data is managed using a FAT system without using U—TOC.

Figures 3A and 3B show the next-generation MD2 disc. The disk is formed by laminating a dielectric film, a magnetic film, a dielectric film, and a reflective film on a transparent polycarbonate substrate. Further, a protective film is laminated thereon. ,

In the next-generation MD2 disc, as shown in Fig. 3A, control information is recorded by an AD IP signal in the lead-in area on the inner circumference of the disc, which is the inner circumference in the direction extending radially from the center of the disc. Has been done. The next-generation MD2 disc does not have a P-TOC with embossed pits in the lead-in area, and instead uses control information based on ADIP signals. The recordable area starts from the outer periphery of the lead-in area, and is a recordable / reproducible area in which groups are formed as guide grooves for recording tracks. In this recordable area, data is modulated and recorded by means of 117pp modulation.

In the next-generation MD2 disc, as shown in Fig. 3B, as the magnetic film, a magnetic layer 101 serving as a recording layer for recording information, a cutting layer 102, and a magnetic layer for information reproduction are provided. A stack of 103 is used. The cutting layer 102 serves as an exchange coupling force adjusting layer. When a certain temperature is reached, the cutting layer 1 02 becomes magnetically neutral, and the domain wall transferred to the recording layer 101 is transferred to the reproducing magnetic layer 103. As a result, in the recording layer 101, the minute mark can be seen enlarged in the beam spot of the reproducing magnetic layer 103.

Although not shown, in a disk using the next-generation MD2, the above-mentioned UID is set in advance in an area on the inner peripheral side of the recordable area, which can be reproduced by a recording / reproducing apparatus for a consumer but cannot be recorded. Be recorded. In the case of the next-generation MD2 disc, the UID is recorded in advance when the disc is manufactured by a technique similar to the technique of BCA (Burst Cutting Area) used in DVD (Digital Versatile Disc). Since the UID is generated and recorded when the disk is manufactured, it is possible to manage the UID, which improves security compared to the case where the UID is generated based on a random number when the disk is initialized by the next-generation MD1 described above. it can. Details such as the format of U ID, will be described later.

In order to avoid complexity, this area in which the UID is recorded in advance in the next-generation MD2 is hereinafter referred to as BCA.

Whether it is the next-generation MD 1 or the next-generation MD 2 can be determined, for example, from the lead-in information. In other words, if P-TOC due to embossed pits is detected in the lead-in, it can be determined that the disc is a current MD or a next-generation MD1 disc. If control information based on the ADIP signal is detected in the lead-in and no P-TOC due to embossed pits is detected, it can be determined that it is the next-generation MD2. It is also possible to determine whether or not UID is recorded in BCA described above. The discrimination between the next-generation MD1 and the next-generation MD2 is not limited to such a method.

Fig. 4 shows the structure of the recordable area of the next-generation MD2 disc. As shown in Fig. 4, all 1 W

-The data is modulated and recorded by the 7 pp modulation, and the DDT area and the reserved track are provided on the inner peripheral side at the beginning of the area where the data is modulated and recorded by the 17 pp modulation. The DDT area is provided for recording replacement area management data for managing a replacement area for a physically defective area.

Specifically, the DDT area records a management table for managing a replacement area including a recordable area that replaces the physically defective area. This management table records the logical class that has been determined to be defective, and also records one or more logical clusters in the replacement area assigned as replacements for the defective logical cluster. Further, the above-mentioned UID is recorded in the DDT area. The reserved track stores information for protecting content.

Further, a FAT area is provided in an area where data is modulated by 1-7 pp modulation and recorded. The FAT area is an area for managing data in the FAT system. The FAT system manages data in accordance with the FAT system used in general-purpose personal computers.

The next-generation MD2 disc does not have a U-TOC area. When a next-generation MD2 disc is loaded into a next-generation MD2 compliant player, the DDT, reserved track, and FAT area at the specified position are read, and data is managed using the FAT system. . Next-generation MD1 and MD2 discs eliminate the need for time-consuming initialization. In other words, next-generation MD 1 and next-generation MD 2 discs require no initialization work other than creating minimal tables such as DDT, reserved tracks, and FAT tables, and record from unused disks. It is possible to directly record and reproduce the area. As mentioned above, the next-generation MD2 disc can generate and record a UID at the time of disc production, thus enabling more powerful security management. The number of layers of the film is larger and the cost is higher than that of a disc. Therefore, the recordable area of the disc and the lead-in and lead-out areas are common to the next-generation MD1, and only the UID is used, using the same BCA as the DVD. A disk called next-generation MD 1.5 has been proposed as a disk system that records during manufacturing.

The description of the next-generation MD 1.5 will be omitted below unless it is particularly necessary. In other words, the next-generation MD 1.5 conforms to the next-generation MD 2 for UID, and conforms to the next-generation MD 1 for recording and reproducing audio data.

U ID will be described in more detail. As described above, in the next-generation MD2 disc, the UID is recorded in advance at the time of manufacturing the disc by a technique similar to the technique called BCA used in DVD. FIG. 5 schematically shows an example of the format of this UID. The entire UID is called a UID record block.

In the UID block, the first two bytes are the UID code field. For the UID code, the upper 4 bits of 2 bytes, that is, 16 bits, are used for disc identification. For example, if these 4 bits are [0000], it indicates that the disc is a next-generation MD2 disc, and [00 01] indicates that the disc is a next-generation MD1.5 disc. It is. Other values of the upper 4 bits of the UID code are reserved, for example, for future expansion. The lower 12 bits of the UID code are used as application IDs and can support 40 96 types of services Next to the UID code is a 1-byte version number field, followed by a 1-byte data length field. This data length indicates the data length of the field of the UID record data arranged next to the data length. The UID record data field is allocated 4 m (m = 0, 1, 2, · · · ·) bytes within the range that the total length of the UID does not exceed 188 bytes. A unique ID generated by a predetermined method can be stored in the field of the UID record data, whereby the individual disk can be identified.

In the next-generation MD1 disc, an ID generated based on a random number is recorded in the field of the UID record data.

A plurality of UID record blocks can be created with a data length of up to 188 bytes.

3. Signal format,

Next, the signal formats of the next-generation MD1 and MD2 systems will be described. In the current MD system, ACIRC, which is a convolutional code, is used as an error correction method, and a sector consisting of 2352 bytes corresponding to the data amount of a subcode block is used as an access unit for recording and reproduction. . In the case of convolutional codes, since the error correction coding sequence spans multiple sectors, it is necessary to prepare a linking sector between adjacent sectors when rewriting data. As an address method, an ADIP, which is a wobbled group method in which a single spiral group is formed and a wobbled as address information is formed on both sides of the dub, is used. In the current MD system, the ADIP signal is arranged so as to be optimal for accessing a sector consisting of 2352 bytes.

In contrast, next-generation MD1 and next-generation MD2 system specifications A block complete type code combining LDC and BIS is used, and 64 Kbytes are used as an access unit for recording and reproduction. Linking sectors are not required for block-completed codes. Therefore, the specifications of the next-generation MD1 system that uses the disk of the current MD system change the handling of ADIP signals to correspond to the new recording method. Also, in the specifications of the next-generation MD2 system, the specifications of the ADIP signal have been changed so as to conform to the specifications of the next-generation MD2. FIG. 6, FIG. 7, and FIG. 8 illustrate the error correction scheme used in the next-generation MD1 and MD2 systems. In the next-generation MD1 and next-generation MD2 systems, the error correction coding method using LDC as shown in Fig. 6 and the BIS method as shown in Figs. 7 and 8 are combined.

FIG. 6 shows a configuration of a code and a coded block for error correction coding by LDC. As shown in Fig. 6, a 4-byte error detection code EDC is added to the data of each error correction coding sector, 304 bytes in the horizontal direction and 2 16 bytes in the vertical direction. The data is two-dimensionally arranged in the error correction coding block. Each error correction coding sector consists of 2 Kbytes of data. As shown in Fig. 6, the error correction coding block consisting of 304 bytes in the horizontal direction and 2 16 bytes in the vertical direction has 32 error correction coding sectors consisting of 2K bytes. Minutes. In this way, the error correction coding block data of 32 error correction coding sectors arranged two-dimensionally in 304 bytes in the horizontal direction and 211 bytes in the vertical direction is And a 32-bit error correction lead-Solomon code parity is added.

FIG. 7 and FIG. 8 show the configuration of BIS. As shown in Fig. 7, one byte of BIS is inserted for every 38 bytes of data. One frame consists of a total of 37.5 X 4 = 15 2 bytes), 3 bytes of BIS data, and 2.5 bytes of frame sync.

As shown in FIG. 8, 496 frames composed as described above are collected to form a BIS block. The BIS data (3 X 496 = 1488 bytes) includes 576 bytes of user control data, 144 bytes of address unit number, and 768 bytes of error correction code.

As described above, since the BIS data has the error correction code of 768 bytes added to the data of 1488 bytes, the error correction can be performed strongly. By embedding this BIS code every 38 bytes, when a burst error occurs, an error location can be detected. Using this error location, erasure correction can be performed using the LDC code.

The ADIP signal is recorded by forming a wobble on both sides of a single spiral groove as shown in FIG. That is, the ADIP signal has FM-modulated address data, and is recorded by being formed as a dubble on a disc material.

FIG. 10 shows the sector format of the ADIP signal in the case of the next-generation MD1.

As shown in Fig. 10, the ADIP sector corresponding to one sector of the AD IP signal has a 4-bit sync, the upper bits of an 8-bit AD IP class naming device, and the lower bits of an 8-bit AD IP cluster naming device. It consists of bits, an 8-bit AD IP sector number, and a 14-bit error detection code CRC.

The sink uses a predetermined pattern of signal to detect the beginning of the AD IP sector. No. Conventional MD systems use convolutional codes, so linking sectors are required. The sector number for linking is a sector number having a negative value, which is “FCh”, “FDh”, “FEh”, or “FFh” (h indicates a hexadecimal number). In the next-generation MD1, the format of this AD IP sector is the same as that of the current MD system because the disk of the current MD system is diverted. In the next-generation MD1 system, as shown in Fig. 11 Next, the AD IP cluster consists of 36 sectors from “FC h” to “F Fh” and “0 F h” to “l F h”. Then, as shown in Fig. 10, two ADs (64K bytes) are allocated to one AD IP cluster.

FIG. 12 shows the configuration of the ADIP sector in the case of the next-generation MD2. According to the specification of the next-generation MD2, 16 ADIP sectors constitute ADIP sectors. Therefore, the sector number of ADIP can be represented by 4 bits. In the next-generation MD, a linking sector is not necessary because a block-completed error correction code is used.

As shown in Fig. 12, the AD IP sector of the next-generation MD 2 consists of a 4-pit sync, the upper bits of the 4-bit AD IP cluster number, and the middle bits of the 8-bit AD IP cluster number. It consists of the lower bits of a 4-bit AD IP cluster picker, a 4-bit AD IP sector picker, and an 18-bit error correction parity.

The sync is a signal of a predetermined pattern for detecting the head of the AD IP sector. The 16 bits of the upper 4 bits, the middle 8 bits, and the lower 4 bits are described as the AD IP class evening picker. 1 Since the AD IP class is composed of six AD IP sectors, the sector The number of members is 4 bits. The current MD system has a 14-bit error detection code, but has an 18-bit error correction parity. In the next-generation MD2 specifications, as shown in Fig. 13, one recording block (64K bytes) of data is allocated to one AD IP class.

Fig. 14 shows the relationship between the A DIP class and the BIS frame for the next-generation MD1.

As shown in Fig. 11, the next-generation MD1 specification requires that the AD IP sectors "FC" to "FF" and the AD IP sectors "0" to "1F" have one sector. AD IP class evening is composed. The data of one recording block (64 Kbytes), which is the unit of recording and playback, is arranged in two in one ADIP cluster.

As shown in FIG. 14, one ADIP sector is divided into the first 18 sectors and the second 18 sectors.

The data of one recording block, which is a unit of recording and playback, is arranged in a BIS block consisting of 496 frames. A preamble (frame “0” to frame “0”) of 10 frames is preceded by a 49-frame de-night frame (frame “10” to frame “505”) corresponding to this BIS block. 9)), and a 6-frame postamble frame (frame 5) after this data frame.

From frame 06, frames 5 1 1) are added, and a total of 512 frames of data is transferred from AD IP sector “F Ch” to AD IP sector “0 Dh”.

It is located in the first half of the 1P class evening and is located in the second half of the AD IP sector “1Fh” from the AD IP sector “0Eh”. The frame of the preamble before the data frame and the frame of the postamble after the data are linked to the adjacent recording block. Used to protect data when king. The preamble is also used for pulling in a data PLL, signal amplitude control, signal offset control, and the like.

The physical address at the time of recording and reproducing the data of the recording block is specified by the AD IP cluster and the first half or the second half of the class. If a physical address is specified at the time of recording / reproduction, the AD IP sector is read from the AD IP signal, the AD IP class number and the AD IP sector number are read from the playback signal of the AD IP sector, and the AD IP class number is read. The first half and the second half are determined.

Fig. 15 shows the relationship between the ADIP class and the BIS frame in the case of the next-generation MD2 specification. As shown in Fig. 13, in the next-generation MD2 specification, one AD IP cluster consists of 16 AD IP sectors. One recording block (64 Kbytes) of data is allocated to one AD IP cluster.

As shown in Fig. 15, data of one recording pro- cess (64K bytes), which is a unit of recording and reproduction, is arranged in a BIS block consisting of 496 frames. Before the 496 frames of data (frames “10” to “505”) corresponding to this BIS block, there are 10 frames of preambles (frame “0” to frame 9000). Also, after this data frame, 6 postamble frames (frames 506 to 5111) are added, and a total of 512 frames of data is added to the AD IP sector “0”. h) to the AD IP sector “The preamble frame before the data frame and the postamble frame after the data located in the AD IP class consisting of F hj are linked to the adjacent recording block. Used to protect data when king. The preamble is also used for the pull-in of the demultiplexing PLL, signal amplitude control, signal offset control, and the like.

The physical address at the time of recording and reproducing the data of the recording block is specified by the ADIP cluster. If a physical address is specified at the time of recording / reproducing, the ADIP sector is read from the ADIP signal, and the ADIP cluster number is read from the reproduced signal of the ADIP section.

By the way, in such a disk, various types of control information are required to control laser power and the like when recording and reproduction are started. In the next-generation MD1 disc, as shown in Fig. 1, P-TOC is provided in the read-in area, and various control information is obtained from this P-TOC.

The next-generation MD2 disc does not have P-TOC by embossing, and control information is recorded by the ADIP signal in the lead-in area. In addition, next-generation MD2 specification disks use magnetic super-resolution technology, so laser power control is important. In the next-generation MD2 specification disc, a calibration area for power control adjustment is provided in the lead-in area and lead-out area.

That is, FIG. 16 shows the structure of lead-in and lead-out of the disk of the next-generation MD2 specification. As shown in FIG. 16, a power calibration area is provided in the lead-in and read-out areas of the disc as a laser beam power control area.

In the lead-in area, a control area in which control information by ADIP is recorded is provided. Control information by AD IP The W record describes the control information of the disk using the area allocated as the lower bits of the AD IP cluster picker.

That is, the AD IP cluster number starts from the start position of the recordable area, and has a negative value in the lead-in area. As shown in Fig. 16, the AD IP sector of the next-generation MD2 consists of a 4-bit sink, the upper bits of an 8-bit AD IP class naming device, and 8-bit control data (AD IP class data). It consists of a lower-order bit of the picker, a 4-bit AD IP sector picker, and 18-bit parity for error correction. As shown in FIG. 16, control information such as the disk type, magnetic phase, strength, and read power is described in the eight bits assigned as the lower bits of the AD IP cluster picker.

Since the upper bits of the ADIP cluster are left as they are, the current position can be known with a certain degree of accuracy. The ADIP sector “0” and the ADIP sector “8” can know the ADIP cluster accurately at predetermined intervals by leaving the lower 8 bits of the ADIP cluster number.

The recording of the control information by the ADIP signal is described in detail in the specification of Japanese Patent Application No. 2001-123535 previously proposed by the present applicant.

4. Configuration of recording / playback device

Next, the configuration of the recording / reproducing apparatus will be described with reference to FIGS. 17 and 18 as an example of a disc drive apparatus corresponding to a disc used for recording / reproducing Z in the next-generation MD1 and MD2 systems.

FIG. 17 shows that the disk drive device 1 can be connected to, for example, a personal computer 100. The disk drive 1 has a media drive 2, memory transfer controller 3, cluster buffer memory 4, auxiliary memory 5, USB (Universal Serial Bus) interfaces 6, 8, USB hub 7, system controller 9, audio The processing unit 10 is provided.

The media drive unit 2 performs recording Z playback on the loaded disc 90. The disc 90 is a next-generation MD1, a next-generation MD2 disc, or a current MD disc. The internal configuration of the media drive unit 2 will be described later with reference to FIG.

The memory transfer controller 3 controls transfer of playback data from the media drive unit 2 to recording data supplied to the media drive unit 2.

The cluster buffer memory 4 buffers the data read from the data tracks of the disks 9 and 0 by the media drive unit 2 in recording block units based on the control of the memory transfer controller 3. .

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

The system controller 9 controls the entire inside of the disk drive device 1 and controls communication with the connected personal computer 100.

That is, the system controller 9 can communicate with the personal computer 100 connected via the USB interface 8 and the USB hub 7, and receives commands such as write requests and read requests. It transmits evening information and other necessary information.

The system controller 9 is, for example, the disk 90 is a media drive. In response to being loaded into the unit 2, it instructs the media drive unit 2 to read management information and the like from the disk 90, and stores the management information and the like read by the memory transfer controller 3 in the auxiliary memory 5.

When a request to read a certain FAT sector is issued from the personal computer 100, the system controller 9 causes the media drive unit 2 to read a recording block including the FAT sector. The read data of the recording block is written to the class buffer memory 4 by the memory transfer controller 3.

The system controller 9 reads the data of the requested FAT sector from the data of the recording block written in the cluster buffer memory 4 and transmits the data to the personal computer 100 via the USB interface 6 and the USB hub 7. Is performed.

When there is a request to write a certain FAT, sector from the personal computer 100, the system controller 9 first causes the media drive unit 2 to read a recording block including the FAT sector. The read recording block is written to the cluster buffer memory 4 by the memory transfer controller 3.

The system controller 9 supplies the data (recording data) of the FAT sector from the personal computer 100 to the memory transfer controller 3 via the USB interface 6 and stores the data in the corresponding FAT sector in the class buffer memory 4. Rewrite the data in the sector.

The system controller 9 instructs the memory transfer controller 3 to transfer the recording block data stored in the class buffer memory 4 to the media drive unit 2 as recording data with the necessary FAT sectors rewritten. Let it. The media drive unit 2 modulates the recording data of the recording block and writes it to the disc 90. Put in. 'Switch 50 is connected to system controller 9. The switch 50 sets the operation mode of the disk drive 1 to one of the next-generation MD1 system and the current MD system. In other words, the disk drive device 1 can record audio data in both the format of the current MD system and the format of the next-generation MD 1 system for the disc 90 using the current MD system. . The switch 50 allows the user to explicitly indicate the operation mode of the disk drive device 1 to the user. Switches with mechanical structure are shown, but electric or magnetic switches or hybrid switches must be used; Can also be.

A display 51 made of, for example, an LCD (Liquid Crystal Display) is provided for the disk drive device 1. The display 51 is capable of displaying a text display or a simple icon. Based on a display control signal supplied from the system controller 9, information on the state of the disk drive 1 and information for the user are provided. Displays a message.

The audio processing unit 10 includes, as an input system, for example, an analog audio signal input unit such as a line input circuit and a microphone phone input circuit, an AZD converter, and a digital audio data input unit. The audio processing unit 10 includes an ATRAC compression encoder / decoder and a buffer memory for compressed data. In addition, the audio processing unit 10 includes a digital audio data output unit and an analog audio signal output unit such as a DZA converter and a line output circuit headphone output circuit as an output system. In the case of Digital audio data (or analog audio signal) is input to the audio processing unit 10 when an audio track is recorded by performing W. Linear PCM audio data, which is input as input linear PCM digital audio data or analog audio signals and is converted by an AZD converter, is subjected to ATRAC compression encoding and stored in a buffer memory. Then, the data is read from the buffer memory at a predetermined timing (a data unit corresponding to the AD IP cluster) and transferred to the media drive unit 2. The media drive section 2 modulates the transferred compressed data by EFM and writes it on the disk 90 as an audio track.

When the disc 90 is a disc of the current MD system, when the audio track of the disc 90 is reproduced, the media drive unit 2 demodulates the reproduced data into an ATRAC compressed data state, and transmits the demodulated data through the memory transfer controller 3. To the audio processing unit 10. The audio processing unit 10 performs ATRAC compression decoding to obtain linear PCM audio data, and outputs the data from the digital audio data output unit. Alternatively, a line output Z headphone output is performed as an analog audio signal by a D / A converter.

The connection with the personal computer 100 is not limited to the USB, and another external interface such as IEEE (Institute of Electrical and Electronics Engineers) 1394 may be used. The connection with the personal computer 100 is not limited to a wired connection, but may be a wireless connection using radio waves, infrared rays, or the like.

The recording / reproducing data management is performed using a FAT system, and the conversion between the recording block and the FAT sector is described in detail in the specification of Japanese Patent Application No. 2001-289380 previously proposed by the present applicant. Have Next, the configuration of the media drive unit 2 having a function of recording and reproducing both the data track and the audio track will be described with reference to FIG.

FIG. 18 shows the configuration of the media drive unit 2. The media drive unit 2 has a turntable in which a disc of the current MD system, a next-generation MD1 disc, and a next-generation MD2 disc are loaded. The media drive unit 2 has a turntable. The disc 90 loaded in the unit is rotated by the spindle motor 29 in the CLV system. The disk 90 is irradiated with laser light by the optical head 19 during recording and reproduction.

The optical head 19 provides a high-level laser output for heating the recording track to the Curie temperature during recording, and a relatively low-level laser for detecting data from reflected light by the magnetic Kerr effect during reproduction. Performs one-time output. For this reason, the optical head 19 includes a laser diode as a laser output means, an optical system including a polarization beam splitter and an objective lens, and an optical system for detecting reflected light. A detector is mounted. The objective lens provided in the optical head 19 is held, for example, by a two-axis mechanism so as to be displaceable in a radial direction of the disk and in a direction of coming and coming from the disk.

Further, a magnetic head 18 is disposed at a position facing the optical head 19 with the disk 90 interposed therebetween. The magnetic head 18 performs an operation of applying a magnetic field modulated by recording data to the disk 90. Although not shown, a thread motor and a thread mechanism are provided for moving the entire optical head 19 and the magnetic head 18 in the disk radial direction.

Optical Head 19 and Magnetic Head 18 are the next generation of VID 2 disks In this case, fine marks can be formed by performing pulse drive magnetic field modulation. In the case of the current MD disc and the next-generation MD1 disc, the magnetic field modulation method of DC emission is used.

The media drive unit 2 includes a recording / reproducing head system using an optical head 19 and a magnetic head 18, a disk rotation driving system using a spindle motor 29, a recording processing system, a reproducing processing system, A system or the like is provided. As the disc 90, there is a possibility that a disc of the current MD specification, a disc of the next-generation MD1 specification, and a disc of the next-generation MD2 specification will be mounted. These disks have different linear velocities. The spindle motor 29 can be rotated at a rotational speed corresponding to a plurality of types of disks having different linear velocities. The disk 90 loaded in the evening table has the linear velocity of the current MD specification disk, the linear velocity of the next-generation MD1 specification disk, and the disk velocity of the next-generation MD, 2 specification disk. Rotated according to speed.

'In the recording processing system, in the case of the disc of the current MD system, when recording the audio track, the error correction coding is performed by AC IRC, and the data is recorded by modulating by EFM, In the case of next-generation MD1 or next-generation MD2, error correction coding is performed by a method combining BIS and LDC, and a part for recording by modulating with 1-7 pp modulation is provided.

In the playback processing system, EFM demodulation and error correction processing by AC IRC are performed during playback of the current MD system disc, and partial response and Viterbi decoding are performed during playback of the next-generation MD1 or next-generation MD2 system disc. There will be a part to perform 17 demodulation based on data detection using, and error correction processing by BIS and LDC.

It also decodes the address of the current MD system and the next-generation MD1 AD IP signal, and decodes the next-generation MD2 AD IP signal. Parts are provided.

The information (photocurrent obtained by detecting the laser reflected light by the photodetector) detected by the laser irradiation of the optical head 19 to the disk 90 by the laser irradiation is supplied to the RF amplifier 21.

The RF amplifier 21 performs current-voltage conversion, amplification, matrix calculation, etc. on the input detection information, and reproduces the reproduced RF signal, tracking error signal TE, focus error signal FE, and group information (reproduced information). Extract AD IP information recorded on disk 90 by track wobbling).

When reproducing a disc of the current MD system, the reproduced RF signal obtained by the RF amplifier is processed by the EFM demodulation unit 24 and the AC IRC decoder 25. That is, the reproduced RF signal is binarized by the EFM demodulation unit 24 to form an EFM signal train, EFM demodulated, and further subjected to error correction and interleaving processing by the AC IRC decoder 25. . That is, at this point, the state of the ATRAC compressed data is established.

When playing back a disc of the current MD system, the selector 26 selects the B contact side, and the demodulated ATRAC compressed data is output as playback data from the disc 90.

On the other hand, next-generation M. When reproducing the D1 or next-generation MD2 disc, the reproduced RF signal obtained by the RF amplifier is processed by the RLL (1-7) PP demodulation unit 22 and the RS-LDC decoder 23. That is, the reproduced RF signal is output to the RLL (1-7) PP demodulation unit 22 by PR (1, 2, 1) ML or PR (1, -1) ML and RLL (1-7) by data detection using Viterbi decoding. -7) Reproduced data is obtained as a code string, and RLL (1-7) demodulation is performed on this RLL (1-7) code string. Error correction and interleaving are further performed by the RS-LDC decoder 23. It is processed.

When the next-generation MD1 or next-generation MD2 disc is reproduced, the selector 26 selects the A contact side, and the demodulated data is output as reproduction data from the disc 90.

The tracking error signal TE and the focus error signal FE output from the RF amplifier 21 are supplied to the servo circuit 27, and the group information is supplied to the ADIP demodulation unit 30.

The ADIP demodulation unit 30 performs band limitation on the group information with a bandpass filter to extract a wobble component, and then performs FM demodulation and pi-phase demodulation to demodulate the ADIP signal. The demodulated ADIP signal is supplied to the address decoder 32 and the address decoder 33.

On the disk of the current MD system or the disk of the next-generation MD1, the ADIP sector number is 8 bits, as shown in Fig.10. On the other hand, in the disk of the next-generation MD2 system, as shown in FIG. 12, the ADIP sector picker has 4 bits. The address decoder 32 decodes the current MD or next-generation MD1 ADIP address. The address decoder 33 decodes the address of the next-generation MD2.

The ADIP addresses decoded by the address decoders 32 and 33 are supplied to the drive controller 31. The drive controller 31 executes necessary control processing based on the ADIP address. The group information is supplied to a servo circuit 27 for spindle servo control.

The servo circuit 27 generates a spindle error for CLV or CAV servo control based on, for example, an error signal obtained by integrating a phase error between the group information and a reproduction clock (PLL system clock at the time of decoding). Isshin Generate a number.

Further, the support circuit 27 is based on a spindle error signal, a tracking error signal supplied from the RF amplifier 21, a focus error signal, a track jump command from the drive controller 31, an access command, and the like. To generate various servo control signals (tracking control signal, force control signal, thread control signal, spindle control signal, etc.) and output them to the driver 28. That is, necessary processing such as phase compensation processing, gain processing, and target value setting processing is performed on the above-mentioned signal and command to generate various servo control signals.

The motor driver 28 generates a required servo drive signal based on the servo control signal supplied from the servo circuit 27. The servo drive signals here include a two-axis drive signal for driving the two-axis mechanism (two types of focus direction and tracking direction), a thread motor drive signal for driving the thread mechanism, and a spindle for driving the spindle motor 29. It becomes the motor drive signal. By such a servo drive signal, focus control and tracking control for the disc 90 and CLV or CAV control for the spindle motor 29 are performed.

When recording audio data on a disc of the current MD system, the selector 16 is connected to the B contact, so that the ACIRC encoder 14 and the EFM modulator 15 function. In this case, the compressed data from the audio processing unit 10 is subjected to an interleave and an error correction code at the ACIRC encoder 14 and then EFM modulation is performed at the EFM modulation unit 15. Is

Then, the EFM modulated data is supplied to the magnetic head driver 17 via the selector 16, and the magnetic head 18 applies a magnetic field to the disk 90 based on the EFM modulated data, thereby forming an audio track. Recording is done It is.

When recording data on the next-generation MD1 or next-generation MD2 disc, the selector 16 is connected to the A contact, and therefore the RS-LD C encoder 12 and RLL (1-7) PP modulator 13 will work. In this case, after the high-density data from the memory transfer controller 3 is interleaved by the RS-LDC encoder 12 and an error correction code of the RS-LDC method is added, the RLL (1-7)? At 1 3, 1 LL (1-7) modulation is performed. 'Then, the recording data as the RLL (1-7) code string is supplied to the magnetic head driver 17 via the selector 16 and the magnetic head 18 applies a magnetic field to the disk 90 based on the modulation data. By doing this, the overnight track is recorded.

The laser driver / APC 20 causes the laser diode to perform a laser emission operation at the time of reproduction and recording as described above, but also performs a so-called APC (Automatic Lazer Power Control) operation.

That is, although not shown, a detector for a laser power monitor is provided in the optical head 19, and the monitor signal is fed back to the laser driver Z APC 20. The laser driver ZAP C20 compares the current laser power obtained as a modal signal with the set laser power and reflects the error in the laser drive signal to output from the laser diode. The controlled laser power is controlled to be stable at the set value.

As the laser power, values as the reproduction laser power and the recording laser power are set by the drive controller 31 in a register inside the laser driver / APC 20.

Drive controller 31 responds to instructions from system controller 9. Based on the above, control is performed so that the above operations of access, various services, data writing, and data reading are executed.

Note that, in FIG. 18, the portions A and B surrounded by a dashed line can be configured as, for example, a one-chip circuit portion.

5. About disk initialization processing by next-generation MD1 and next-generation MD2

As described above, a UID (unique ID) is recorded outside the FAT on the next-generation MD1 and next-generation MD2 discs, and security management is performed using the recorded UID. In principle, disks compatible with the next-generation MD1 and next-generation MD2 are shipped with the UID pre-recorded at a predetermined position on the disk. In a disc corresponding to the next-generation MD1, the U ID is recorded in advance, for example, in a lead-in area. In this case, the position where the UID is recorded in advance is not limited to the lead-in area.For example, if the position where the UID is written after the disk is initialized is fixed, it may be recorded in that position in advance. it can. In a disc compatible with the next-generation MD2 and the next-generation MD1.5, UID is recorded in advance in BCA described above.

On the other hand, next-generation MD1 discs can use discs based on the current MD system. Therefore, a large number of disks using the current MD system, which have already been circulated without recording the U ID, will be used as disks for the next generation MD1.

Therefore, for such a disk by the current MD system in which the UID is recorded without being recorded, an area compliant with the standard is provided, and the disk drive device is placed in that area when the disk is initialized. The random number signal is recorded in step 1, and this is used as the UID of the disc. Also, when a user accesses the area where this UID is recorded, Prohibited by W standard. Note that the UID is not limited to a random number signal. For example, a combination of a manufacturer code, a device code, a device serial number, and a random number can be used as a UI D. Further, any one or more of the manufacturer code, the device code and the device serial number, and a random number can be combined and used as a UID.

FIG. 19 is a flowchart showing an example of initialization processing of a disc by the next-generation MD1. In a first step S100, a predetermined position on the disc is accessed to check whether a UID is recorded. If it is determined that the U ID has been recorded, the U ID is read and temporarily stored in, for example, the auxiliary memory 5.

The location accessed in step S100 is outside the FAT area of the format by the next-generation MD1 system, such as the lead-in area. If the disk 90 has already been provided with a DDT, for example, a disk that has been initialized in the past, the area may be accessed. It is to be noted that the processing in step S100 can be omitted.

Next, in step S101, U-TOC is recorded by EFM modulation. At this time, information for securing an alert track and a track after the DDT in FIG. 2 described above, that is, an area where data is modulated and recorded by 117 pp modulation is written to the U-TOC. . In the next step S102, an alert track is recorded by EFM modulation in the area secured by the U-TOC in step S101. Then, in step S103, 0 bits are recorded by 1-7 ρ modulation.

In step S104, the UID is recorded in an area outside the FAT, for example, in the DDT. If the UID is read from a predetermined location on the disk and stored in the auxiliary memory 5 in step S100 described above, the UID is recorded. Is recorded. If it is determined in step S100 that the UID is not recorded at a predetermined position on the disk, or if step S100 is omitted, the random number signal is output. A UID is generated based on the UID, and the generated UID is recorded. The UID is generated by, for example, the system controller 9, and the generated UID is supplied to the media drive 2 via the memory transfer controller 3 and is recorded on the disk 90.

Next, in step S105, data such as FAT is recorded in an area where data is modulated and recorded by 1-7 pp modulation. That is, the area where the UID is recorded is an area outside the FAT. Also, as described above, in the next-generation MD1, it is not always necessary to initialize the recordable area to be managed by FAT.

FIG. 20 is a flowchart showing an example of the initialization processing of a disc by the next-generation MD 2 and the next-generation MD 1., 5. In the first step S110, an area corresponding to the BCA on the disc is accessed, and it is confirmed whether the UID is recorded. If it is determined that the U ID is recorded, the U ID is read and temporarily stored in, for example, the auxiliary memory 5. Since the recording position of the UID is fixedly determined in the format, it can be directly accessed without referring to other management information on the disk. This can be applied to the processing described with reference to FIG. 19 described above.

In the next step S 11 1, 00 bits are recorded with 1-7p modulation. Next, in step S112, the UID is recorded in an area outside the FAT, for example, in the DDT. As the UID recorded at this time, the UID read from the predetermined position on the disk in step S110 described above and stored in the auxiliary memory 5 is used. Here, in the above-described step S110, a predetermined position on the disc is determined. If it is determined that no UID is recorded in the device, a UID is generated based on the random number signal, and the generated UID is recorded. The UID is generated by, for example, the system controller 9. The generated UID is supplied to the media drive 2 via the memory transfer controller 3 and recorded on the disk 90.

Then, in step S113, FAT and the like are recorded. That is, the area where the UID is recorded is an area outside the FAT. As described above, in the next-generation MD2, the recordable area to be managed by FAT is not initialized.

6. About the first management method of music data

As described above, in the next-generation MD 1 and next-generation MD 2 systems applicable to the embodiment of the present invention, data is managed by the FAT system. The audio data to be recorded is compressed by a desired compression method, and is encrypted to protect the rights of the author. For example, ATRAC 3 and ATRAC 5 have been considered as audio data compression methods. Of course, other compression methods such as MP3 (MPEG1 Audio Layer-3) and AAC (MPEG2 Advanced Audio Coding) can be used. It is also possible to handle not only audio data, but also still image data and video data. Of course, since the FAT system is used, general-purpose data can be recorded and played back overnight. In addition, the instructions that are readable and executable by the computer can be encoded on disk, so that the next-generation MD1 or MD2 can also contain executable files. .

A management method for recording and reproducing audio data on a disk of the next-generation MD1 and MD2 specifications will be described.

With the next-generation MD1 system and the next-generation MD2 system, Since music data with sound quality can be played back, the number of songs managed on a single disc has become enormous. In addition, by using a FAT system for management, compatibility with computers is achieved. According to the recognition of the inventor of the present application, this has the advantage that the usability can be improved, but the music data may be copied illegally and the copyright holder may not be protected. . The management system to which the present invention is applied takes such points into consideration.

FIG. 21 shows a first example of an audio data management method. As shown in FIG. 21, in the management method in the first example, a track index file and an audio data file are generated on a disc. The track index file and audio data file are files managed by the FAT system.

An audio data file is composed of multiple music data as shown in Fig. 22.

—Evening is stored as one file, and when you look at the audio data file on the FAT system, it looks like a huge file. The audio data file is internally divided as parts, and the audio data is treated as a set of parts.

The track index file is a file in which various information for managing the music data stored in the audio data file is described. As shown in Fig. 23, the track index file includes a preorder table, a programmed play order table, a group information table, a track information table, a parts information table, and a name table. I have it.

The play order table is a table indicating the playback order defined by default. As shown in Fig. 24, the play order table Stores information TINF1, TINF2, ... indicating the link destination to the track desk rib (Fig. 27A and Fig. 27B) in the track information table for the rack pick-up (track number). The track number is a continuous number, for example, starting from “1”.

The programmed play order table is a table in which the reproduction procedure is defined by each user. As shown in FIG. 25, the programmed play order table describes information track information P INF 1, P INF 2,... Of the link destination to the track description for each track nampa.

The group information table describes information about the group as shown in FIGS. 26A and 26B. A group is a set of one or more tracks with a continuous track number, or a set of one or more tracks with a continuous programmed track number. The group information table is described in the group desk of each group as shown in Fig. 26A. As shown in Fig. 26B, the group describ- ing describes the track number at which the group starts, the number of the ending track, the group name, and the flags.

The track information table describes information about each song as shown in FIG. 27A and FIG. 27B. As shown in Fig. 27A, the track information table is composed of track desk ribs for each track (each song). At each track desk rib, as shown in Fig. 27B, the encoding method, copyright management information, content decryption key information, It describes the artist name, title name, original song order information, recording time information, and so on. Artist name, title name is Neem It is not the information itself, but the information about the name of the boyfriend. The encoding method indicates the codec method, and serves as decoding information. As shown in Fig. 28A and Fig. 28B, the part information table describes a pointer for accessing the actual music position from the part picker. The parts information table consists of parts descriptors for each part as shown in Fig. 28A. Parts are all of one track (song) or each part obtained by dividing one track. Figure 28B shows the entry of the pad slip in the information table. Each part descriptor describes the start address of the part in the audio data file, the end address of the part, and the link destination to the part following the part, as shown in Fig. 28B. Is done.

The addresses used as the pointer information of the part picker, the pointer information of the name table, and the pointer information indicating the position of the audio file include the byte offset of the file, the parts desk picker, the cluster picker of the FAT, and the disk used as the recording medium. Physical address or the like can be used. File byte offset is a particular embodiment of the offset method that can be implemented in the present invention. Here, the part pointer information is an offset value from the start of the audio file, and the value is expressed in a predetermined unit (for example, byte, bit, n-bit block).

The name table is a table for representing characters that are the substance of the name. The name table is composed of a plurality of name slots as shown in Fig. 29A. Each name slot is linked and called from each pointer to the name. The pointer for calling the name is the artist name in the track information table, the title name, and the group. There is a group name in the information table. Each name slot can be called from more than one. As shown in Fig. 29B, each name unit is composed of name information that is character information, a name type that is an attribute of the character information, and a link destination. A long name that cannot be accommodated in one name slot can be described by dividing it into multiple name slots. If it does not fit in one name slot, the link destination to the name slot in which the subsequent name is described is described.

In the first example of the audio / video management system in the system to which the present invention is applied, as shown in FIG. 30, the play order table (FIG. 24) specifies the track number to be reproduced. Then, the track descriptor (Fig. 27A and Fig. 27B) linked to the track information table is read out, and the encoding method, copyright management information, and content The decryption key information, the pointer information to the part picker where the music starts, the artist name and the title name pointer, the original music order information, the recording time information, etc. are read. '' The part information table (Fig. 28A and Fig. 28) is linked from the part number information read from the track information table, and the track (song) starts from this part information table. The audio data file of the position of the part corresponding to the position is accessed. When the data of the part at the position specified in the part twin table of the audio data file is accessed, the reproduction of the audio data is started from that position. At this time, decoding is performed based on the encoding method read from the track description table of the track information table. If the audio data is encrypted, read it from the track desk The extracted key information is used.

If there is a part following that part, the link destination of that part is described as a pad slip, and according to this link, the pad slip is read out in order. By following the link of this part descriptor, the audio data of the part at the position specified by the part descriptor is reproduced on the audio day data file, and the desired track (music ) Audio data can be played.

Also, the name slot of the name table at the position (name pointer information) pointed to by the artist name or title name read from the track information table (Fig. 29A and Fig. 29B) Is called, and the name data is read from the name slot at that position. The name pointer information may be, for example, a name slot number, a class number in a FAT system, or a physical address of a recording medium.

As described above, a plurality of name slots in the name table can be referred to. For example, there are cases where a plurality of music pieces of the same artist are recorded. In this case, as shown in FIG. 31, the same name table is referred to as an artist name from a plurality of track information tables. In the example of Fig. 31, track descriptor "1", track desk rib "2" and track descriptor "4" are all songs of the same artist "DEFBAND", and have the same name slot as the artist name. Is referred to. Also, the track descriptor “3”, the track descriptor “5” and the track desk rib “6” are all songs of the artist “GHQGIRLS” at the same position, and refer to the same name slot as the artist name. . This If the name slot of the name table can be referred to by multiple pointers, the capacity of the name table can be saved.

Along with this, for example, a link to this name table can be used to display information for the same artist name. For example, if you want to display a list of songs whose artist name is “DEF BAND”, the track descriptor that refers to the address of the naming slot of “DEF BAND” is deleted. In this example, the information of track descriptor "1", track descriptor "2" and track desk rib "4" is obtained by extracting the track descriptor referring to the address of the name slot of "DEF BAND". can get. As a result, a list of songs whose artist name is “DEF BAND” can be displayed among the songs stored on this disk. Note that since multiple references can be made to the name table, no link is provided from the name table to the track information table.

'When newly recording audio data, the FAT table prepares an unused area continuous with a desired number of recording blocks or more, for example, four or more recording blocks. The reason why a continuous area equal to or larger than a desired recording block is secured is that recording audio data in a continuous area as much as possible will not waste access. When an area for recording audio data is prepared, a new track descriptor is allocated on the track information table, and a content key for encrypting the audio data is generated. You. Then, the input audio data is encrypted, and the encrypted audio data is recorded in the prepared unused area. The area where the audio data is recorded is linked to the end of the audio data file on the FAT file system. As new audio data is linked to the audio file, information on the linked position is created, and the newly secured audio description contains the newly created audio file location. Information is recorded. The key information and the part number are described in the newly secured track descriptor. Further, if necessary, an artist name or a title name is described in the name unit, and a pointer linking to the artist name or the title name is described in the name unit of the track descriptor every track descriptor. You. Then, the pick-up of the track descriptor is registered in the play order table. Also, copyright management information is updated.

When reproducing the audio data, information corresponding to the designated track number is obtained from the play order table, and the track descriptor of the track to be reproduced is obtained. ,

Key information is obtained from the track description table in the track information table, and a part description indicating an area in which the entry description is stored is obtained. From the part description, the position in the audio data file at the head of the part where the desired audio data is stored is not obtained, and the data stored at that position is extracted. Then, the data reproduced from that position is decrypted using the obtained key information, and the audio data is reproduced. If there is a link in the parts description, it is specified and linked to the part, and the same procedure is repeated.

In the case where the track number “n” is changed to track number “n + m” in the play order table, the information of the track is described from the track information TINF n in the play order table. The track descriptor D n is obtained. Track information TINF n + From 1 to the value of TI NFn + m (Track Desk Rib Yuichi Nampa) is all moved to the previous position. Then, in the track information TI NFn + m, the pick-up of the track descriptor Dn is stored.

When deleting a track whose track number was “n” in the play order table, the track descriptor D n describing the information of the track is obtained from the track information TI NF n in the play order table. You. All valid track descriptor pick-ups after the track information entry in the play order table, TIN Fn + 1, are moved to the previous position. In addition, since track "n" is to be erased, all track information entries after track "n" are moved forward in the play order table. From the track descriptor Dn acquired along with the erasure of the track, an encoding method and a decryption key corresponding to the track are acquired in the track information table, and the first music data is stored. The part number of the parts descriptor P n indicating the area where the part is located is obtained. The audio block in the range specified by Parts Desk Pn is separated from the audio data file on the FAT file system. Further, the track descriptor Dn of the track in the track information table is deleted. Then, the parts desk rib is deleted from the parts information table, and the parts description is released in the file system.

For example, in FIG. 32A, it is assumed that parts A, parts; B, and parts C have been connected to each other, and that part B is to be deleted. Part A part B shares the same audio block (and the same FAT cluster) and the FAT chain is continuous. Packet C is located immediately after Part B in the audio data file, If you look at the FAT table, you'll find that it's actually far away.

In this case, as shown in Fig. 32B, when part B is deleted, the current part and cluster can only be removed from the FAT chain (returned to the free space). Not sharing, two FAT classes in the evening. In other words, the file is reduced to 4 audio blocks as a file. The number of audio dips recorded on parts C and subsequent parts are all reduced by four.

Deletion can be performed on a part of a track instead of the entire track. When a part of a track is deleted, the information of the remaining tracks is obtained by using the encoding method and decoding key corresponding to the track obtained from the part descriptor P n in the track information table. It is possible to decrypt. ,

When linking track n and track n + 1 in the play order table, the track descriptor number D n describing the information of the track is obtained from the track information TINF n in the play order table. You. Also, from the track information TINF n +} in the play order table, a track descriptor pick-up Dm describing the information of the track is obtained. All valid TINF values (track desk rib nampa) after TINF n + 1 in the play order table are moved to the previous TINF. By searching the programmed play order table, all tracks that refer to the track descriptor Dm are deleted. A new encryption key is generated, a list of the track descriptors is taken out from the track descriptor Dn, and a part descriptor taken out from the track descriptor Dm is placed at the end of the list of the part desk ribs. Are concatenated. When connecting trucks, compare both truck desk ribs to confirm that there is no problem with copyright management, obtain parts desk slips from the track desk ribs, and link both trucks. In such a case, it is necessary to check the FAT table to determine whether the rules regarding fragmentation are satisfied. Also, it is necessary to update the pointer to the name table as needed.

When the track n is divided into the track n and the track n + 1, the track descriptor pick-up Dn in which the information of the track is described is obtained from TINF Fn in the play order table. From the track information TINF n + 1 in the player table, a track descriptor Namer Dm in which the information of the track is described is obtained. Then, the effective track information T INF value (track desk rib nampa) subsequent to T INF n +1 in the play order table is moved by one. A new key is generated for track descriptor D n. A list of parts desk ribs is retrieved from the track desk rib D n. A new parts desk part is assigned, and the contents of the parts part before the division are copied there. The part desk rib that includes the division point is shortened to just before the division point. Also, the link of the part script after the dividing point is cut off. A new parts descriptor is set immediately after the split point.

7. Second example of music data management method

Next, a second example of the audio data management method will be described. FIG. 33 shows a second example of the audio data management method. As shown in FIG. 33, in the management method in the second example, a track index file and a plurality of audio data files are generated on a disc. Track index file and multiple audio data The file is a file managed by the FAT system.

As shown in Fig. 34, in principle, an audio data file contains music data for one song per file. This audio data file has a header. In the header, a title, decryption key information, and copyright management information are recorded, and index information is provided. The index divides the music of one track into multiple pieces. In the header, the position of each track divided by the index is recorded corresponding to the index number. For example, 255 indexes can be set.

The track index file is a file in which various information for managing the music data stored in the audio data file is described. As shown in FIG. 35, the track index file includes a preorder table, a programmed play order table, a group information table, a track information table, and a name table.

The play order table is a table indicating a playback order defined by default. As shown in Fig. 36, the play order table is linked to the track desk rib (Fig. 39A and Fig. 39B) of the track information table for each track pick-up (track number). The information TINF 1, TINF 2,... The track number is, for example, a continuous number that starts with “1”.

The programmed play order table is a table in which the reproduction procedure is defined by each user. As shown in FIG. 37, the programmed play order table describes information track information PINF 1, PINF 2,... Of a link destination to a track description for each track pick-up. As shown in FIG. 38A and FIG. 38B, the group information table describes information about the group. A group is a set of one or more tracks with consecutive track numbers, or a set of one or more tracks with consecutive programmed track numbers. The group information table is described in the group desk of each group as shown in Fig. 38A. As shown in Fig. 38B, on the group desk rib, the track number where the group starts, the number of the end track, the group name, and the flags are described.

As shown in FIG. 39A and FIG. 39B, the track information table describes information about each song. Track information-As shown in Fig. 39A, the track table consists of track desk ribs for each track (each song). At the end of each track desk rib, as shown in Fig. 39B, a pointer to the file of the audio data file containing the song, index number, artist name, title name, original song order information, Recording time information and the like are described. The key name is not the name itself, but the name of the boyfriend to the name table.

The name table is a table for representing characters that are the substance of names. The name table is composed of a plurality of name ports as shown in Fig. 40A. Each name slot is linked and called from each pointer to the name. The pointer for calling the name includes the artist name in the track information table, the title name, the group name in the group information table, and the like. Each name slot can be called from more than one. Each naming unit has a name data, a name type, It consists of a link destination. Long names that do not fit in one name slot can be described by being divided into multiple name slots. If it does not fit in one name slot, the link destination to the name slot in which the subsequent name is described is described.

In the second example of the audio data management method, as shown in FIG. 41, when a track number to be reproduced is specified by a play order table (FIG. 36), a link destination of the track information table is designated. The rack descriptors (Fig. 39A and Fig. 39B) are read out, and from this track descriptor, the file pointer and index pick-up for that song, the artist and evening name pointers, and the original song Order information, recording time information, etc. are read.

The audio data file is accessed from the beginning of the song file, and the header information of the audio file is read. If the audio data is encrypted, the key information read from the header is used. Then, the audio data file is reproduced. At this time, if the index naming is specified, the position of the specified index naming is detected from the information of the header, and the reproduction is started from the position of the index naming. Also, the name slot of the name table at the position indicated by the artist name or title name read from the track information table is called, and the name data is read from the name slot at that position.

When recording new audio data, the FAT table prepares an unused area that is continuous with a desired number of recording blocks or more, for example, four recording blocks or more.

Once the area for recording the audio overnight has been prepared, A new track desk rib is assigned to the information table, and a content key is generated to encrypt this audio day data. Then, the input audio data is encrypted, and an audio data file is generated.

The file pointer and key information of the newly generated audio overnight file are described in the newly secured track desk rib. Further, if necessary, an artist name, a title name, and the like are described in the name slot, and a bus descriptor linked to the artist name or the title name is described in the name slot in the track descriptor. Then, the number of the track descriptor is registered in the play order table. Also, the copyright management information is updated.

When playing back audio data, information corresponding to the designated track number is obtained from the play order table, and the track descriptor of the track to be played back in the track information table is obtained.

The file descriptor and the index pick-up of the audio file in which the music data is stored are obtained from the track descriptor. Then, the audio data file is accessed, and key information is obtained from the header of the file. Then, the data of the audio data file is decrypted using the obtained key information, and the audio data is reproduced. If an index pick-up is specified, playback starts from the position of the specified index pick-up.

When the track n is divided into the track n and the track n + 1, the track desk rib pick-up D n describing the information of the track is obtained from TINF n in the play order table. Play order From the track information TI NF n + 1 in the table, a track descriptor pick-up Dm describing the information of the track is obtained. Then, the value of the valid track information TI NF (track descriptor nampa) subsequent to TI NF n + 1 in the play order table is all moved by one.

As shown in Fig. 42, by using an index, the data of one file can be divided into multiple index areas. The position of the index number and index area is recorded in the header of the audio track file. The track descriptor D n describes the file pointer of the audio file and the index number. In the track descriptor Dm, the file pointer of the audio data and the index number are described. Thus, the music M1 of one track of the audio file is apparently divided into the music M11 and M12 of the two tracks.

'When linking track n and track n + 1 on the play order table, the track information TI NF n in the play order table is used to describe the track descriptor that describes the track. Is obtained. Also, from the track information T INF n + 1 in the player table, a track descriptor Nm Dm describing the information of the track is obtained. All valid TINF values (Track Descriptor Nampa) after TINF n + 1 in the play order table are moved forward by one.

Here, when track n and track n + 1 are in the same audio data file and are divided by an index, the index information of the header is deleted as shown in FIG. 43. , Consolidation is possible. As a result, the songs M2 1 and M2 2 on the two tracks Connected to the track M23.

If track n is the second half of one audio data file divided by index and track n + 1 is at the beginning of another audio data file, it is divided by index as shown in Fig. 44. A header is added to the data of track n, and an audio data file of music M32 is generated. To this, the header of the audio data of the track n + 1 is removed, and the audio data of the track n + 1 of the song M41 is concatenated. As a result, the songs M32 and M41 of the two tracks are linked as a song M51 of one track. To realize the above processing, add a header to the track divided by the index, encrypt it with another encryption key, and convert the audio data by the index into one audio data file It has a function and a function to connect to other audio data files except for the header of the audio data file.

8. Operation when connecting to a personal computer

In the next-generation MD1 and the next-generation MD2, the FAT system has been adopted as a data management system in order to provide compatibility with personal computers. Therefore, next-generation MD1 and MD2 discs can read and write not only audio data but also data commonly used in personal computers.

Here, in the disk drive device 1, audio data is reproduced while being read from the disk 90. Therefore, in consideration of the accessibility of the portable disk drive device 1 in particular, it is preferable that a series of audio streams be continuously recorded on the disk. On the other hand, general data writing by a personal computer is performed by allocating free space on the disk as appropriate without considering such continuity. It is.

Therefore, in the recording / reproducing apparatus applicable to the embodiment of the present invention, the personal computer 100 and the disk drive 1 are connected by the USB hub 7, and the personal computer 100 is connected to the disk drive 1 When writing to a disc 90 mounted on a disc, general data writing is performed under the control of the file system on the personal computer, and writing for audio data is performed on the disk drive. It is performed under the control of the file system on the device 1 side.

FIG. 45A and FIG. 45B show the types of data to be written when the personal computer 100 and the disk drive 1 are connected by the USB hub 7 (not shown). FIG. 9 is a diagram for explaining that the management authority is moved by using FIG. FIG. 45A shows an example in which general data is transferred from the personal computer 100 to the disk drive 1 and recorded on the disk 90 mounted on the disk drive 1. In this case, the FAT management on the disc 90 is performed by the file system on the personal computer 100 side.

It is assumed that the disc 90 is a disc formatted by either the next-generation MD1 or the next-generation MD2 system.

That is, on the personal computer 100 side, the connected disk drive device 1 looks like one removable disk managed by the personal computer 100. Therefore, data can be read / written from / to the disk 90 mounted on the disk drive device 1 as if, for example, the personal computer 100 reads / writes data from / to a flexible disk.

The file system of such a personal computer 100 side The system can be provided as a function of an operating system (OS), which is basic software installed in the personal computer 100. As is well known, 〇S is recorded as a predetermined program file in, for example, a hard disk drive of the personal computer 100. This program file is read at the time of activation of the personal computer 100 and executed in a predetermined manner, so that each function as an OS can be provided.

FIG. 45B shows an example in which the audio data is transferred from the personal computer 100 to the disk drive 1 and recorded on the disk 90 mounted on the disk drive 1. For example, in the personal computer 100, audio data is recorded on a recording medium such as a hard disk drive (HDD) of the personal computer 100, for example. ,

The personal computer 100 encodes the audio data with ATRAC compression encoding, writes the audio data to the disk 90 attached to the disk drive 1, and records the audio data on the disk 90. It is assumed that utility software for requesting the deletion of an audio file is installed. The utility software further has a function of referring to the track index file of the disc 90 mounted on the disc drive device 1 and browsing the track information recorded on the disc 90. This utility software is recorded as a program file on the HDD of the personal computer 100, for example.

— As an example, a case where audio data recorded on a recording medium of a personal computer 100 is recorded on a disc 90 mounted on the disc drive device 1 will be described. Utility software mentioned above The key has been activated in advance.

First, the user records predetermined audio data (referred to as audio data A) recorded on the HDD to the personal computer 100 on the disk 90 mounted on the disk drive device 1. The operation is performed as follows. Based on this operation, a write request command for requesting recording of the audio data A on the disk 90 is output by the utility software. The write request command is transmitted from the personal computer 100 to the disk drive 1.

Subsequently, audio data A is read from the HDD of the personal computer 100. The read audio data A is subjected to ATRAC compression encoding processing by the above-described utility software mounted on the personal computer 100, and is converted into ATRAC compressed data. The audio data A converted to the ATRAC compressed data is transferred from the personal computer 100 to the disk drive 1.

Upon receiving the write request command transmitted from the personal computer, the disk drive 1 transfers the audio data A converted to ATRAC compressed data from the personal computer 100 and transfers the audio data. It is recognized that the recorded data is recorded on the disc 90 as audio data.

The disk drive 1 receives the audio data A transmitted from the personal computer 100 from the USB hub 7 and sends it to the media drive 2 via the USB interface 1 and the memory transfer controller 3. . In the system controller 9, when sending the audio data A to the media drive unit 2, the audio data A is written to the disk 90 based on the FAT management method of the disk drive 1. W control. That is, based on the FAT system of the disk drive 1, the audio data A is continuously written in units of four recording blocks, that is, 64 kbytes X 4 as the minimum recording length. .

Until the writing of data to the disc 90 is completed, the computer, the disc drive 1, and the computer 100 exchange data, status, and commands according to a predetermined protocol. . As a result, the data transfer rate is controlled so that, for example, the cluster buffer 4 does not overflow or underflow on the disk drive device 1 side.

Examples of commands that can be used on the personal computer 100 include a deletion request command in addition to the write request command described above. This deletion request command is a command for requesting the disk drive 1 to delete the audio data recorded on the disk 90 mounted on the disk drive 1.

For example, when the personal computer 100 is connected to the disk drive 1 and the disk 90 is mounted on the disk drive 1, the track index file on the disk 90 is read by the above-mentioned utility software. The read and read data is transmitted from the disk drive 1 to the personal computer 100. The personal computer can display a title list of audio data recorded on the disc 90, for example, based on this data. When an attempt is made to delete an audio file (audio data B) based on the displayed title list on the personal computer 100, the information indicating the audio file B to be deleted is deleted. Is transmitted to the disk drive 1. Disced When the live device 1 receives this delete request command, the requested audio data B is deleted from the disc 90 under the control of the disc drive device 1 itself.

Since the deletion of the audio data is performed by the control based on the FAT system of the disk drive device 1 itself, a plurality of audio data as described with reference to FIG. 32A and FIG. It is also possible to delete certain audio data in a huge file that is compiled as a file.

9. Restrictions on Copying Audio Data Recorded on Disc 90 In order to protect the copyright of audio data recorded on Disc 90, audio data recorded on Disc 90 and other data must be protected. It is necessary to set restrictions on copying to a recording medium. For example, suppose that the audio data recorded on the disc 90 is transferred from the disc drive device 1 to the personal computer 100 and recorded on the HDD of the personal computer 100.

Here, it is assumed that the disk 90 is a disk formatted by the next-generation MD1 or MD2 system. The operations such as check-out and check-in described below are performed under the management of the above-mentioned utility software mounted on the personal computer 100.

First, as shown in step A of FIG. 46, audio data 200 recorded on the disc 90 is moved to a personal computer (PC) 100. The move here refers to a series of operations in which the target audio data 200 is copied to the personal computer 100 and the target audio data is deleted from the original recording medium (disk 90). In other words, the move deletes the original data of the The data moves to the destination.

It should be noted that data is copied from one recording medium to another recording medium, and that the right to copy, which indicates the permitted number of copies of the original data, is reduced by one.

, Referred to as checkout. Deleting the checked-out data from the check-out destination and granting the copy number right of the check-out source data is called check-in.

When the audio data 200 is moved to the personal computer 100, the audio data 200 is moved to the recording medium of the personal computer 100, for example, an HDD (audio data 2). 0 0 ′), the audio data 200 is deleted from the original disc 90. Then, as shown in step B of FIG. 46, the personal computer 100 can check out (CO) the audio data 200 ′ that has been moved (no or a predetermined value). The number of times 20 and 1 are set. Here, the number of possible check-outs 201 is set to three as indicated by "@". That is, the audio data 200 ′ is permitted to perform a further check-out from the personal computer 100 to the external recording medium the number of times set to the check-out permitted number 201. Is done.

Here, if the checked-out audio file 200 is still deleted from the original disk 90, it may be inconvenient for the user. Then, the audio data 2000 'checked out to the personal computer 100 is written back to the disk 90.

When the audio data 200 'is written back from the personal computer 100 to the original disc 90, as shown in step C of Fig. 46, the number of times that checkout is possible is consumed once and checkout is possible. Times Number is (3-1 = 2) times. In step C of Fig. 46, the number of checkouts consumed is indicated by the symbol "#". At this time, audio data 200 'of the personal computer 100 is not deleted from the personal computer 100 because the right to check out remains for the next two times. That is, the audio data 200 ′ on the personal computer 100 is copied from the personal computer to the disc 90, and the audio data 200 ′ on which the audio data 200 ′ is copied is written on the disc 90. 0 "will be recorded.

Note that the number of possible check-outs 201 is managed by the copyright management information of the track descriptor in the track information table (see FIG. 27B). Since the track descriptor is provided for each track, the number of checkouts 201 that can be performed can be set for each track such as music data. The track description copied from the disc 90 to the personal computer 100 is used as control information of the corresponding audio data recorded on the personal computer 100.

For example, when audio data is transferred from the disc 90 to the personal computer 100, a track description corresponding to the audio data thus copied is copied to the personal computer 100. You. On the personal computer 100, management of the audio data moved from the disc 90 is performed by this track descriptor. As the audio data is moved and recorded on the HDD of the personal computer 100, the number of possible check-outs 201 in the copyright management information during the track description is the specified number of times (3 in this example). Times).

In addition, as the copyright management information, the above-mentioned check-out possible number of times 2 0 1 In addition, a device ID for identifying the check-out source device and a content ID for identifying the checked-out content (audio data) are also managed. For example, in the procedure C of FIG. 46 described above, the device ID of the copy destination device is authenticated based on the device ID in the copyright management information corresponding to the audio data to be copied. If the device ID in the copyright management information and the device ID of the copy destination device are different, copying can be prohibited.

In the above-described series of checkout processes in steps A to C in FIG. 46, the audio data on the disc 90 is moved once to the personal computer 100, and the data is again transferred from the personal computer 100. Since writing back to disk 90, the procedure is cumbersome and cumbersome for the user, and the time to read audio data from disk 90 and the time to write audio data back to disk 90 are reduced. For this reason, time may be wasted. Further, once the audio data is deleted from the disk 90, it is considered that the audio data does not conform to the user's feeling.

Therefore, when the audio data recorded on the disc 90 is checked out, it is considered that the above-described processing has been performed, and the process is omitted, and only the result shown in the procedure C in FIG. 46 may be realized. Make it possible. An example of the procedure is shown below. The procedure shown below is executed by a single instruction from the user, for example, "Check out audio data of audio file A recorded on disk 90".

(1) Copy the audio data recorded on the disc 90 to the HDD of the personal computer 100 and copy the audio data on the disc 90 to the management data of the audio data. Disable some To erase. For example, the link information TINF from the play order table to the track desk rib corresponding to the audio data, and the link information PINF n from the programmed file order table to the track desk rib corresponding to the audio data. Delete. The track desk rib itself corresponding to the audio data may be deleted. As a result, the audio data is disabled on the disk 90, and the audio data is transferred from the disk 90 to the personal computer 100. (2) In step (1), when the audio data is copied to the personal computer 100, the track descriptor corresponding to the audio data is also copied to the HDD of the personal computer 100. You.

(3) Next, in the personal computer 100, the number of check-outs in the copyright management information in the track descriptor corresponding to the moved audio data copied from the disc 90 is specified. The number of times, for example, three times, is recorded.

(4) Next, the personal computer 100 obtains a content ID corresponding to the recorded audio data based on the track description copied from the disc 90, and obtains the content ID. The ID is recorded as the content ID indicating the audio data that can be checked in.

(5) Next, in the personal computer 100, the number of check-outs in the copyright management information in the track description corresponding to the recorded audio data is set in the above-mentioned procedure (3). It is reduced by one from the specified number of times. In this example, the number of checkouts allowed is (3-1 = 2). (6) Next, in the disk drive device 1 (not shown) on which the disk 90 is mounted, the track descriptor corresponding to the moved audio data is activated. For example, the track information corresponding to the audio data is activated by restoring or reconstructing the link information TINF n and PINF n deleted in the above procedure (1). When the track descriptor corresponding to the audio data is deleted in the above procedure (1), the track desk rib is reconstructed. The corresponding track descriptor recorded on the personal computer 100 may be transferred to the disk drive device 1 and recorded on the disk 90.

According to the above steps (1) to (6), it is considered that a series of checkout processing is completed. By doing so, the copy of the audio data from the disc 90 to the personal computer 100 can be realized while protecting the copyright of the audio data, and the user's trouble can be saved. Copying of audio data according to the steps (1) to (6) is applied to audio data recorded (recorded) on the disk 90 by the user using the disk drive device 1. , Is preferred.

When checking in after checking out, the personal computer 100 stores control information in its own recorded audio data and track descriptors, for example, copyright management information. A search is performed, a judgment is made based on the searched audio data and control information, and a check-in is performed.

10. Software configuration

FIG. 47 shows an example of a file transfer system according to an embodiment of the present invention. 1 shows a possible example software configuration. It should be noted that the “system” in the present specification is a system in which a plurality of devices are logically aggregated, and it does not matter whether or not each device is in the same housing.

The personal computer 100, which is a content server, is equipped with a jukebox application 300. The jukebox application 300 is used for ripping from CDs (Compact Discs) or for downloading music from a music distribution server via the Internet or other sources, such as music data obtained by downloading. It builds a library by accumulating data and provides a user interface for operating the library. The jukebox application 300 further controls the connection between the personal computer 100 and the disk drive 1. Further, the functions of the utility software described above can be included in the jukebox application 300. That is, the software shown in FIG. 47 is composed of a personal computer, which is the first recording medium, and a recording medium, such as a hard disk drive, of the first recording medium 100, and a disk 90, which is the second recording medium. Transfer and data return. The jukebox application 300 has a database management module 301, and the database management module 301 stores a disk ID for identifying the disk 90 and a duplication in the library in a disk ID. Manage by associating with database or disk ID list. In this embodiment, U ID is used as disk ID. The group managed by the database management module 301 and the details of the disk ID database or the disk ID list will be described later.

The jukebox application 300 runs the security module 302 on the OS 303 on personal computer 100. Work through. The security module 302 has a license conforming module (LCM) specified by Secure Digital Music Initiative (SDMI), and performs authentication processing between the jukebox application 300 and the disk drive 1. Do. The security module 302 also checks the consistency between the content ID and the UID. All content exchanges between the jukebox application 300 and the disk drive device 1 are performed via the security module 302.

On the other hand, the disk drive device 1 is equipped with a next-generation MD drive firmware program 320 as software for controlling the operation of the disk drive device 1 itself. The control of the disk drive 1 by the personal computer 100 and the exchange of data between the personal computer 100 and the disk drive 1 are performed between the next-generation MD drive firmware 320 and the OS 303. It is controlled by communicating via the next-generation MD device driver 304.

The next-generation MD drive firmware 320 is transmitted via a communication interface 310 such as a predetermined cable network connecting the personal computer 100 and the disk drive 1, for example. Version up etc. can be performed from the Sonal Computer 100 side.

The jukebox application 300 is provided by being recorded on a recording medium such as a CD-ROM (Compact Disc-Read Only Memory). By loading this recording medium into the personal computer 100 and performing a predetermined operation, for example, the jumpbox application 300 recorded on the recording medium is stored in a predetermined manner in the personal computer 100, for example, in a hard disk drive. You. Not limited to this, Jyuk The box application 300 (or the installer of the jukebox application 300) may be provided to the personal computer 100 via a network such as the Internet. Next, the database management module 301 will be described. In the library, groups can be set up, and content can be classified by associating the content with duplication based on appropriate criteria. In the embodiment of the present invention, a disk ID for identifying each of the disks 90 can be associated with a group. The above-mentioned UID is used as the disk ID.

The database managed by the database management module 301 included in the jukebox application 300 will be schematically described with reference to FIGS. 48A and 48B. FIG. 48A shows an example of the structure of a disk ID database or a disk ID list. In this disk ID database or disk ID list, a group is associated with the disk ID and managed. As a more specific example, as illustrated in FIG. 48A, a disk ID is associated with a group, information on the capacity of the disk 90 identified by the disk ID, and checkout reservation information. Can be Other attributes such as album name, album genre, artist name, data (compression) format, registration date in the database, and content acquisition source may be associated with the disc ID.

The configuration of the database illustrated in FIGS. 48A and 48B is an example enabling one embodiment of the present invention, and is not limited to this configuration.

The field “disk ID” shown in FIG. 48A is a field in which the disk ID is registered. The disc ID is unique for every disc 90 Recording medium identifier.

The field "group name" is a field in which the name of the group is registered. The group name is the name of the user

It can be set using 300. A group name prepared in advance in the jukebox application 300 may be used. The group may wish to listen to lovers, drive (drive), commute, etc. by scene, by singer, performer, etc., by genre such as classical or jazz, or by the latest content. It consists of content classification.

The field “disk capacity” is a field in which information on the capacity of the disk 90 is registered. The information on the capacity of the disc 90 is, for example, information on the remaining capacity of the disc 90. From this information, the amount of data that can be recorded on the disc 90 is known. ,

The field “reservation information” is a field in which information on check-out reservation is registered. Based on this checkout reservation information, it is possible to determine whether or not a checkout reservation has been made, and to specify the checkout destination disk. It is possible to determine whether or not a checkpoint reservation has been made, for example, by checking for the presence or absence of data in the field “reservation information” or by using a specific bit. Further, by using the specific bit, it is possible to cope with a case where a new disk not registered is set as a reservation destination. The check destination disk can be specified, for example, by registering information on the disk ID in the field “reservation information”. In the field “reservation information”, information on check-in reservation may be registered in the same manner as check-out.

On the other hand, content that is a unique content identifier for each content W

For each ID, information about the disk ID and the content is associated. FIG. 48B shows an example of the configuration of a content ID database or a content ID list to which information regarding the content is related. The content ID database or the content ID list is dynamically generated by the database management module 301 based on, for example, the disk ID database or the disk ID list.

The field “Content ID” is a field where the content ID is registered. The content ID has a data length of, for example, 128 bits, and is assigned by the security module 302 when the content is taken into the jukebox application 300 and stored in the library. Each piece of content stored in the library can be identified by a content ID. ,

The field "Disk ID" in FIG. 48B is the field "Disk ID" in FIG. 48A. Therefore, the disc ID database or disc ID list is associated with the content ID database or content ID list by the disc ID, and the information about the content is uniquely determined by the disc ID and the content ID. It is managed.

Further, the attribute of the content and the disc ID are associated with each of the content IDs. In the example of Fig. 48B, the disk ID is registered in the field "Disk ID", and the number of possible COs (check-outs) is registered in the field "CO count", and the field "Size" Then, the size of the content, that is, the data amount is registered, and is associated with the content ID stored in the field “content ID”. Of course, other information can be associated with the content ID. In FIG. 48B, a disk ID is associated with each content ID registered in the library, but a content ID may be associated with the disk ID. In addition, a configuration in which a group is associated with a content ID or a configuration in which a possible number of COs is associated with a disc ID may be adopted. The present invention is not limited thereto, and the library can be managed based on the above-described first management method and second management method of music data. Hereinafter, an embodiment of the present invention will be described. In the embodiment described below, a check-out reservation is made when new audio data is introduced by the above-described software. Introducing new content does not only mean taking in new content by ripping, etc., but also includes using new content for other purposes, such as playing back new content.

FIG. 49 and FIG. 50 show an example of the operation of software according to the embodiment. Hereinafter, an embodiment of the present invention will be described with reference to FIGS. 49 and 50.

Fig. 49 shows the operation of software when new content is stored by ribbing. Ripping means reading out content as digital data from an original recording medium containing content such as music CDs and extracting it as a computer file.

The content is imported to the personal computer 100 by ripping, and the disk ID database or the disk ID list is updated by the data base management module 301, and the disk ID of the new content imported by ripping is obtained. Disk information such as, group, and disk capacity is registered. In addition, the content ID database or content ID list is updated, and the content is Content ID, disc ID, size,

Content information such as the number of possible COs is registered.

Here, ripping is applied to store new content.

The same can be applied to downloading contents from a network using an electronic music distribution service using a network such as the Internet. Therefore, the content supply source is a recording medium such as a CD or DVD, and the recording medium is not only used to store the content from the recording medium on a daily basis, but also the content is supplied from an Internet-based content distribution service server or the like. As a server on this network, content can be stored in a database by downloading.

As shown in FIG. 49, when rubbing is started or during ripping, the user is inquired through a user interface as to whether or not to make a checkout reservation (step S200). ). For example, a message such as “Do you want to make a check-out reservation? (Y / N)” is displayed on the screen of the personal computer 100, and the user requests YE.

Receive instructions from S Z N O.

In step S201, the result of the inquiry in step S200 is determined. At step S201, the reservation of the checkout is not performed, that is, when it is determined to be "N", the rubbing is performed as usual, and the processing ends when the rubbing is completed.

In step S201, a checkout is reserved, ie, "Y E S

If J is determined, the disk ID database or disk I

An inquiry is made to the D list (step S202). Then, the user is caused to designate a disk for which a checkout is reserved through the user interface (step S203). The content being ribbed is the content for which the checkout is reserved. Checkout may be performed for all contents, that is, for each album, or may be performed for each song. It should be noted that the content for which the checkpoint is reserved is not limited to the content being liberated, and content that already exists in the library may be selectable. As a result, the time during ripping can be used more effectively. If the target of checkout reservation is an album unit, the content can be identified by the disk ID or the content ID. If the check-out reservation is for each song, the content can be identified by the disc ID and the content ID.

When new content is introduced in the personal computer 100, such as in the case of riveting, information on the new content is added to the disk ID database or the disk ID list described above. At this time, for example, an inquiry such as “Do you want to register a new disc in the database? (YZN)” is made to the user through the user interface, and the registration of the disc information and content information of the new content is performed. You may ask for permission.

The disk to be checked out is identified by the disk ID. In the disk ID database or the disk ID list described above, since the disk ID and the group are managed in association with each other, it is possible to specify a check-out destination disk based on the group. The check-out destination disk is specified by providing the user with information such as the group associated with the disk ID through the user interface, and specifying the disk for which check-out is reserved from the provided information. .

Therefore, in step S203, the content ID and disc ID And a reservation for a checkout of the content identified by the content ID is made.

Also, there are optional items such as `` for new disk '' that check out to a new disk so that you can check out to a new group that is not registered in the disk ID database or disk ID list. You may. If this “for new disk” is selected as the check-destination disk, for example, a profile for the new disk may be set.

In step S203, when the content for which the checkout reservation is to be made and the disk for the checkout destination are designated, the size of the content for which the checkout reservation is made is compared with the recordable capacity of the checkout destination disk. At the time of checking out, it is determined whether or not the capacity of the disk at the checkout destination is sufficient (step S204). If the check destination disk is registered in the disk ID database or disk ID list, information on the capacity of disk 90 in the disk ID database or disk ID list and the size of the content to be checked Is compared with If the destination disk is a new disk, the available disk capacity is determined from the disk type, data (compression) format, etc., and the determined disk capacity is compared with the size of the content to be checked. .

If it is determined in step S204 that the recording capacity is insufficient and shortage, that is, "NO", it is determined whether or not the user reserves a check-in through the user interface so as to eliminate the shortage of the recording capacity. Is performed (step S206). For example, a message such as “Do you reserve a check-in? (YZN)” is displayed on the personal computer overnight screen, and the user receives an instruction from YES ZNO. You.

At step S207, the result of the inquiry at step S206 is determined. In step S207, the reservation for check-in is not made, that is, if it is determined to be "N リ", the rubbing is performed as usual, and the process ends when the riving is completed. After the user has reduced the checkout target or changed the checkout destination disk, the process may return to step S204.

In step S207, a check-in reservation is made. That is, if "YESJ" is determined, a check-in reservation is made (step S208). Contents and check in check-in reservation The designation of the in-destination is performed in the same manner as in the case of the check-out reservation described above, except that the flow of the content is opposite to that in the case of the check-out.

After the check-in reservation, the process returns to step S204. In some cases, the contents are deleted on the disk drive device 1 and the contents are checked in as a deemed check-in, which produces the same effect as the resulting checked-in state. The processing from step S206 to step S208 is not essential. In this case, if it is determined in step S204 that the recording capacity is insufficient, that is, “N〇”, the rubbing is performed as usual, and the process ends when the rubbing is completed. After warning the user to reduce the number of checkout targets or changing the checkout destination disk, the process may return to step S204.

If it is determined in step S204 that the recording capacity is sufficient, that is, "YES", a check-out reservation is made (step S205). For example, register information such as reserved and reserved disk in the “Reservation Information” field of the disk ID database or disk ID list, and By updating the disk ID database or the disk ID list by the overnight base management module 301, checkpoint reservation processing is performed.

When the check-out reservation and ribbing are completed, the process ends. The reservation processing at the time of this rubbing is performed by identifying a disk using a disk ID registered in a disk ID database or a disk ID list, or instructing a new disk. It is not necessary to connect to the personal computer 100.

After ripping is completed, if check-out is reserved, the status of disk drive 1 and the disk in disk drive 1 is checked, and if the reserved conditions are met, the reserved check-out (hereinafter referred to as reservation check) Out) is performed. The process of the reservation checkout shown in FIG. 50 described below is performed in the disk drive device 1 in which the disk is inserted immediately after this ribbing (in FIG. 50, PD: Portable Device). Is connected automatically, when the disk drive device 1 in which the disk is inserted is newly connected after the end of the riveting, or when the disk 90 is replaced.

In the reservation checkout process, first, the user is inquired through a user interface as to whether or not to perform checkout (step S209). For example, a message such as "Do you want to check out? (YZN)" is displayed on the screen of the personal computer 100, and the user receives an instruction from the user.

In step S210, the result of the inquiry in step S209 is determined. If it is determined in step S210 that check-out is not performed, that is, "N〇", the reservation check-out process for the disk inserted in the disk drive 1 ends. In step S210, check-out is performed, that is, if it is determined to be "YES", whether the disk ID of the disk in the disk drive 1 is registered in the disk ID database or the disk ID list Is determined (step S211). It should be noted that the confirmation of whether or not to execute the check-out for the user in step S209 and step S210 can be omitted.

If the disk ID read from the disk in the disk drive 1 is not registered in the disk ID database or the disk ID list in step S211, that is, if it is determined to be “N〇”, Then, it is determined whether or not the content, that is, the audio data exists in the disk in the disk drive device 1 (step S218). If the disk ID of the disk in the disk drive cannot be read normally in step S 211, the reservation checkout process for the disk inserted in disk drive 1 is completed. I do.

In step S218, if the audio disk exists in the disk in the disk drive device 1, that is, if it is determined to be "YES", it is determined that the disk is an unregistered disk such as a friend's disk, and Through one interface, an inquiry is made to the user as to whether or not to register the disk ID of the disk in the disk drive device 1 (step S221). For example, a message such as "Do you want to register the disk inserted in the drive? (YZN)" is displayed on the screen of the personal computer 100, and a user's instruction of YSZNO is received.

In step S222, the result of the inquiry in step S221 is determined. In step S222, the registration of the disk ID is not performed, that is, when it is determined that the disk ID is "N", the disk drive 1 is inserted. The processing of the reservation checkout for the disc being set is completed.

In step S222, the disk ID is registered. In other words, if "YES" is determined, the disk ID of the disk in the disk drive 1 is added to the disk ID database or the disk ID list. Disk information such as a loop and a capacity is registered (step S2223). Then, the process returns to step S209.

If it is determined in step S218 that there is no content in the disk in the disk drive device 1, that is, that there is no audio data, that is, "NO", it is determined that the disk is a new disk (blank disk) and the disk is The disk information such as the disk ID, group, and capacity of the disk in the disk drive 1 is registered in the ID database or the disk ID list (step S219). Note that even if there is data other than audio data in the disc and the disc is not empty, if there is no audio data, it is determined to be “NO” in step S218.

After the registration of the blank disk information, it is determined whether a check-out reservation for the new disk has been made (step S220). This determination can be made by referring to the field “reservation information” in the disk ID data base or the disk ID list. If it is determined in step S220 that the reservation for the new disk has not been made, that is, it is determined to be "NO", the processing of the reservation checkout for the disk inserted into the disk drive 1 ends. I do.

In step S220, the reservation for the new disk has been made, that is, if it is determined to be "YES", the content for which the checkout reservation has been made for the disk in disk drive unit 1 Is checked out (step S2 17). At this time, The consistency between the capacity and the capacity of the content to be checked out may be checked, and whether or not the free space is sufficient may be checked. By checking out, the contents of the database consisting of the disk ID database or disk ID list are updated to the latest information. Then, the processing of the reservation checkout is completed.

If the disk ID read from the disk in the disk drive 1 is registered in the disk ID database or the disk ID list in step S211, that is, if it is determined to be “YES”, It is determined whether the read disk ID of the disk in the disk drive device 1 matches the reserved disk ID by referring to the disk ID database or the disk ID list (step S21). 2). That is, here, it is determined whether or not the disc 90 identified by the discs I and D associated with the content ID of the content reserved for check-out is connected.

If it is determined in step S212 that the read disk ID of the disk in the disk drive 1 does not match the disk ID of the reserved disk, that is, if it is determined to be "N「 ", the disk drive The processing of the reservation checkout on the disk inserted in the device 1 ends.

In step S212, if the read disk ID of the disk in disk drive 1 matches the disk ID of the reserved disk, that is, if it is determined to be "YES", check-in is continued. It is determined whether or not a reservation has been made with reference to the disk ID database or the disk ID list (step S213).

If it is determined in step S213 that check-in has not been reserved, that is, if “NO” has been determined, the content for which check-out has been reserved for the disk in the disk drive 1 will be executed. check It is out (step S2 17). At this time, the consistency between the free space of the disc and the capacity of the content to be checked out may be checked to determine whether the free space is sufficient. By checkout, the contents of the disk ID database or disk ID list are updated to the latest information. Then, the processing of the reservation checkout is completed.

If check-in is reserved in step S213, that is, if it is determined to be “YE S”, the user is inquired via the user interface as to whether or not to perform check-in. (Step S2 1 4). For example, a message such as “Do you want to check in? (YZN)” is displayed on the screen of the personal computer 100 and the user receives the instruction of YE SZNO.

In step S215, the result of the inquiry in step S214 is determined. In step S215, if the check-in is not performed, that is, if it is determined to be "NO", the reservation checkout processing for the disk inserted in the disk drive 1 ends.

In step S215, check-in is performed, that is, if "YE S" is determined, the content corresponding to the content ID reserved for check-in is checked in from the disk in the disk drive device 1. (Step S2 16). The confirmation of whether or not to perform check-in to the user in step S214 and step S215 can be omitted. Check-in updates the contents of the disk ID database or the database consisting of the disk ID list and the like to the latest information.

After the check-in is completed, the contents of the disk in the disk drive 1 for which the check-reservation has been made are checked. The user is locked out (step S2 17). At this time, the consistency between the free space of the disk and the capacity of the content to be checked may be checked to determine whether the free space is sufficient. By the checkout, the contents of the disk ID database or the database composed of the disk ID list and the like are updated to the latest information. Then, the reservation checkout process is completed.

As described above, the reservation checkout process shown in FIG. 50 is performed not only immediately after the end of the ripping but also after the end of the ripping, the disk drive device 1 is newly connected or the detachable disk is removed. It is executed every time the disc 90 as a state recording medium is replaced.

As described above, according to the embodiment of the present invention, a check-out reservation can be made at the time of rubbing, so that wasteful time during ripping can be efficiently used. Also, by using the disk ID at the time of reservation, it is possible to specify the check-out destination disk even if there is no check-out disk during the riveting. Since the check-out destination can be specified during ripping, it is possible to automatically perform a check-out when the disk identified by the disk ID used to specify the check-out destination is connected. By managing the disc IDs in association with the groups classified by artist, scene, genre, etc., it is possible to easily create discs for each of these groups, Management becomes easy.

In addition, by managing information about the capacity of the disc together with the disc ID, the size of the content to be checked out is compared with the recordable capacity of the disc to be checked out, and the check Thus, it can be determined whether or not the capacity is insufficient. If the capacity is insufficient, it is possible to check out efficiently by making a reservation for check-in as well as check-out.

Also, when a check-out is reserved, a new disk can be specified as the check-out destination disk so that the disk ID is not registered in the disk ID list or the disk ID list. Checkpoints can be reserved for blank discs as well.

The present invention is not limited to the embodiment of the present invention described above, and various modifications and applications are possible without departing from the gist of the present invention. For example, each step in the operation of the software according to the above-described embodiment is not limited to performing the processing in chronological order in the described order, and the processing is not necessarily performed in chronological order. Even if not, processing may be performed in parallel and individually.

'Also, it is explained that the group of 1 is checked out for the disk 90, but this is not limited to this example. For example, if there is enough room for the recording capacity of the disc 90, a plurality of groups can be checked for one disc 90. On the disc 90, a plurality of groups can be identified by referring to the group information table.

In such a case, for example, when the disk drive device 1 loaded with the disk 90 is connected to the personal computer 100, the disk ID of the disk 90 is changed by the jukebox application 300. It is checked whether it is registered in the ID database or the disk ID list. Along with that, a group information table on disk 90 by jukebox application 300 Is checked to see if there is a group checked as a dynamic group in the group description. If any group is checked out as a dynamic group, the library is synchronized for that group in the manner described above. If a plurality of groups on the disk 90 are groups that have been checked out as dynamic groups, the libraries are synchronized for each of the groups by the method described above. Of course, this method can also be applied to the case where only one group of contents is recorded on the disc 90.

The processing by the software according to the above-described embodiment is performed by executing a program such as a jukebox application 300 included in the software, which is recorded on a computer-readable recording medium such as a CD or a DVD. It is assumed that the program can be executed by installing the software in a storage device such as an HDD and storing it in a recording device such as an HDD. However, another information processing device such as a computer in which a program constituting software is installed may be used. In addition, a part or all of the processing by the software can be executed by hardware.

In the above-described embodiment, the MD 90 having a unique identifier such as the next-generation MD 1 or the next-generation MD 2 has been described as the disc 90 as the recording medium of the check-out destination. However, the present invention is not limited to this, and other recording media having a unique identifier, such as rewritable optical disks, magnetic disks, magnetic tapes, and memory cards, can be used.

Claims

The scope of the claims

1. In a file transfer system for transferring content data recorded on a first recording medium to a second recording medium,

A recording and reproducing device for recording data on the second recording medium and reproducing data from the second recording medium;

A content data supply device for supplying content data; and a content data management device for outputting the content data supplied from the content data supply device to the recording / reproducing device.

Recording means for recording the content data supplied from the content overnight supply device on the first recording medium in association with a different content identifier for each content data;

Update the transfer management information for managing the recording of the supplied content data on the second recording medium by associating the content identifier with the different recording medium identifiers provided in the second recording medium. Means for updating transfer management information;

Receiving a recording medium identifier of a second recording medium attached to the recording / reproducing apparatus to be reproduced by the recording / reproducing apparatus, and converting the content data recorded on the first recording medium based on the transfer management information to the Control means for controlling transfer of the content data to the recording / reproducing apparatus so that the content data is recorded on the second recording medium; and

A file transfer system comprising:

2. The content data recorded on the first recording medium is managed such that the number of times that the content data can be copied to another recording medium is limited for each content data. The file transfer according to claim 1, wherein the number of copies that can be made is reduced when transferring the content data to the recording medium. Feeding system.

3. The file transfer system according to claim 1, wherein the second recording medium on which recording and reproduction are performed by the recording and reproduction device is detachable from the recording and reproduction device.

4. The transfer management information includes transfer reservation information,

The transfer management information updating means updates the transfer reservation information of the transfer management information in association with a recording medium identifier of a second recording medium for transferring the content data supplied from the content data supply device. The described file transfer system.

5. The recording / reproducing device and the content data management device each include a communication unit for performing communication, and the content data is transferred by the recording / reproducing device connected to the content data management device by the communication unit. The file transfer system according to claim 1, which is performed when it is determined that the file transfer has been performed.

6. The transfer management information updating means requests the content data to be reserved for transfer of the content data to the second recording medium having a recording medium identifier not registered in the transfer management information while the content data is not recorded. File transfer system according to range 1.

7. The transfer management information includes the recordable capacity information of the second recording medium, and when the transfer from the first recording medium to the second recording medium is reserved, the content reserved for the transfer. Compare the capacity required for data recording with the recordable capacity of the second recording medium managed by the transfer management information, and if the recordable capacity of the second recording medium is insufficient, 2. The file transfer system according to claim 1, wherein a content data recorded on said second recording medium is erased to make a reservation to increase the recordable capacity of said second recording medium.

8. The content data recorded on the first recording medium is The number of times that data can be copied to another recording medium is managed for each data, and the content data recorded on the second recording medium and transferred from the first recording medium is deleted. 8. The file transfer system according to claim 7, wherein the number of times that the file can be copied is increased when the file transfer is performed.

9. In the file transfer method for transferring the content data recorded on the first recording medium to the second recording medium,

The content data supplied from the content data supply device is recorded on the first recording medium in association with a different content identifier for each content data,

Recording the supplied content data on the second recording medium by associating the content identifier with a different recording medium identifier provided for each of the second recording media for identifying the second recording medium. Update the transfer management information that manages the

A recording / reproducing apparatus which records content data recorded on the first recording medium on the second recording medium based on the received recording medium identifier of the second recording medium and the transfer management information. Transfer of content data to

File transfer method.

10. The content data recorded on the first recording medium is managed so that the number of times that content data can be copied to another recording medium is limited each time the content is recorded. 10. The file transfer method according to claim 9, wherein the number of permitted copies is reduced when transferring the content data to the second recording medium.

1 1. The transfer management information includes transfer reservation information,

The transfer management information is associated with the recording medium identifier of the second recording medium to which the content data supplied from the content data supply device is transferred. 10. The file transfer method according to claim 9, wherein the transfer reservation information is updated.

12. The file transfer method according to claim 9, wherein the second recording medium is detachable from a recording / reproducing device that records / reproduces data on / from the second recording medium.

13. The file transfer method according to claim 9, wherein the file transfer is performed when the recording / reproducing apparatus recognizes the second recording medium.

10. The file transfer method according to claim 9, wherein the reservation of the transfer of the content data to the second recording medium having the recording medium identifier which has not been recorded in the transfer management information and has not been registered in the transfer management information is made.

15. The transfer management information includes recordable capacity information of the second recording medium, and when the transfer from the first recording medium to the second recording medium is reserved, the content for which the transfer is reserved. Compare the capacity required for data recording with the recordable capacity of the second recording medium managed by the transfer management information, and if the recordable capacity of the second recording medium is insufficient, 10. The file transfer method according to claim 9, wherein the content data recorded on the recording medium is erased to make a reservation for increasing the recordable capacity of the second recording medium.

16. The content data recorded on the first recording medium is managed so that the number of times that the content data can be copied to another recording medium is limited for each content data, and is recorded on the second recording medium. 16. The file transfer method according to claim 15, wherein when the content data transferred from the first recording medium is deleted, the permitted number of copies is increased.