DE10010497A1 - Audio record-replay unit with provision for reproducing images and text, includes system limiting replay of data selected from memory card, by use of counter and comparator - Google Patents

Abstract

A device determines legality of replay frequency-limiting information, the data being selected through the operating unit. A counter is used in this determination. A comparator checks whether replay duration measured by the counter exceeds a predetermined value. An editor changes the information limiting reproduction frequency stored in memory, once the measured duration of replay, exceeds the previously determined result from the comparator. An Independent claim is included for the corresponding method of reproducing the data recorded.

Description

Background of the Invention Field of the Invention

The present invention relates to a reproducing apparatus and a re Playback method for playing back files that have playback limit information have from a record carrier.

State of the art

An EEPROM (Electrically Erasable Programmable ROM) is an electrical um Writable memory that takes up a lot of space because each bit is made up of two transistors consists. This limits the integration of the EEPROM. To solve this difficulty. A flash memory has been developed that allows a bit to be represented by a transistor a total bit erase system was developed. The flash memory is called Successor to conventional recording media, such as magnet plates and optical plates.

In addition, a memory card using a flash memory is be knows. The memory card can be freely attached to and detached from a device. A digital audio recorder / player that uses a memory card instead a conventional CD (Compact Disc: trademark) or MD (Mini-Disc: trademark) character) can be used.

On the other hand, if the audio / video information is digitized and for multi media is used, their copyright protection becomes important. In the field of computer science Onsdiensten the user is provided with a record carrier on which one digitized audio / video information, which has special playback limitation information tion has been recorded. In addition, the digitized audio / video information that has certain playback limit information to the user via the digital Broadcasting or the Internet brought. The user can ge the delivered or in circulation brought audio / video information (content) for the duration or with the frequency reproduzie ren, which is shown by the playback limit information. If necessary  the user previously with the desired audio / video information on a memory card record fixed costs.

A conventional audio playback device must have the playback operation for the Audio / video information that is recorded on a recording medium, not be restrict. However, as mentioned above. Music programs as opposed to package carriers, for example CD's. In such a case, in contrast to a conventional one Chen device in which the user freely reproduces the audio / video information from a carrier that he has bought, the playback operation of data on a carrier which the user has bought are recorded. So it is necessary dig, clearly define the playback operation for the audio / playback information, and the Frequency of playback and the playback time according to the definition Zen. In other words, when the user listens to a particular music program for 30 seconds who listens long or more, it may be stipulated that the music program reproduces once has been. If, on the other hand, the user listens to the particular music program for 25 seconds heard and then jumped to the next music program, it can be determined that the particular music program was not reproduced. If the user is a music program, if he listens to it only three times, the user can buy it inexpensively fen.

In contrast, the user who has bought a compact carrier can usually freely reproduce music programs from it. In the very near future, however, there could be another output device various playback limit information assigned to the carriers are, check. In other words, a playback device, which according to a sol Chen playback limit information does not work, music programs that a re have limit information, do not reproduce. The playback device should Playback frequency, playback time, etc. according to the determination of the replay Manage operations. Of course, values that are managed should be adequately secured his.

Task and overview of the invention

It is therefore an object of the present invention to provide a playback device and to provide a rendering method that allows the content to be reproduced until the playback frequency matches the playback limit information a certain playback mode is exceeded.  

A first feature of the present invention is a playback device comprising:
a memory for recording a plurality of files and their reproduction frequency limitation information;
an actuator for selecting a desired file from the plurality of files stored in the memory to reproduce the desired file;
determination means for determining whether or not the reproduction frequency limitation information has been set on the file selected by the actuator;
counting means for counting the playback elapsed time of the file selected by the actuator when the playback frequency limit information is set to the selected file as the result of the determination by the determining means;
a comparison device as to whether the playback elapsed time counted by the counter exceeds a predetermined value; and
an editing means for editing the reproduction frequency limitation information stored in the memory when the playback elapsed time counted by the counter exceeds the predetermined value as a result of the determination by the comparing means.

A second feature of the present invention is a method for reproducing a selected file from a recording medium, which comprises the following steps:

• a) Have the selected file saved on the storage medium is drawn, reproduced;
• b) determining whether reproduction frequency limitation information is on the selected file is set or not;
• c) Counting the play time of the selected file when the replay Gabe frequency limitation information on the selected file as the result of the determination is set in step (b);
• d) Compare whether the counted playback elapsed time is a predetermined one Value exceeds; and
• e) Editing the playback frequency limit information on the Record carrier is stored when the playback elapsed time that in step (c) ge  was counted, the predetermined value as the determination result in step (d) increases.

These and other tasks. Features and advantages of the present invention are in view of the following detailed description of a preferred embodiment approximately clearer, which is shown in the accompanying drawings.

Brief description of the drawings

Fig. 1 is a block diagram showing the construction of a digital audio reproducing apparatus using a non-volatile memory card according to the present invention;

Fig. 2 is a block diagram showing the internal structure of a DSP 30 according to the present invention;

Fig. 3 is a block diagram showing the internal structure of a memory card 40 according to the present invention;

Fig. 4 is a schematic diagram showing a file management structure of a memory card as a storage medium according to the present invention;

Fig. 5 is a schematic diagram showing the real structure of data in a flash memory 42 of the memory card 40 according to the present invention;

Fig. 6 is a data structure of the memory card 40 according to the present dung OF INVENTION;

Fig. 7 is a schematic diagram showing the hierarchy of the file structure in the memory card 40 ;

Fig. 8 is a schematic diagram showing the data structure of the playback management file PBLIST.MSF, which is a sub-directory which is stored on the memory card 40 ;

Fig. 9 is a schematic diagram showing the data structure in the case that an ATRAC3 data file is divided into blocks with a predetermined unit length and that attribute files are added;

Fig. 10A is a schematic diagram showing the file structure before two files are edited with a combination process;

Fig. 10B is a schematic diagram showing the file structure after two files are edited by the one combining process;

Fig. 10C is a schematic diagram showing the file structure after a file is edited with a dividing process;

Fig. 11 is a diagram showing the data structure of a playback management file PBLIST;

Fig. 12A is a diagram showing the data structure of a header area of the playback management file PBLIST;

Fig. 12B is a schematic diagram showing the data structure of a main data area of the playback management file PBLIST;

Fig. 12C is a diagram showing the data structure of an additional information data area of the playback management file PBLIST;

Fig. 13 is a table that concatenates showing the types of additional information data and their code values;

Fig. 14 is a concatenation table showing types of additional information data and their code values;

Fig. 15 is a concatenation table showing types of additional information data and their code values;

Fig. 16A is a schematic diagram showing the data structure of additional information data;

Fig. 16B is a schematic diagram showing the data structure in the case where the additional information data is an artist name;

Fig. 16C is a schematic diagram showing the data structure in the case where additional information data is a copyright code;

Fig. 16D is a schematic diagram showing the data structure in the case where additional information data is the date / time information;

Fig. 16E is a schematic diagram showing the data structure in the case where the additional information data is a reproduction protocol;

Fig. 17 is a schematic diagram showing a detailed data structure of an ATRAC3 data file;

Fig. 18 is a diagram showing the data structure of an upper portion of an attribute header that constitutes an ATRAC3 data file;

Fig. 19 is a schematic diagram showing the data structure of a middle area of the attribute header that forms an ATRAC3 data file;

Fig. 20 is a table that concatenates recording modes, recording time, etc.;

Fig. 21 is a table showing copy control states;

Fig. 22 is a diagram showing the data structure of a lower portion of the attribute header that constitutes an ATRAC3 data file;

Fig. 23 is a schematic diagram showing the data structure of a header of a data block of an ATRAC3 data file;

Fig. 24 is a flowchart showing a recovery process according to the present invention in the event that a FAT area has been destroyed;

Fig. 25 is a schematic diagram showing the data structure in the memory card 40 according to a second embodiment of the present invention;

Fig. 26 is a diagram showing the relationship between a track information management file TRKLIST.MSF and an ATRAC3 data file A3Dnnnnn.MSA;

Fig. 27 is a diagram showing in detail the data structure of the track information data file TRKLIST.MSF;

Fig. 28 is a diagram showing in detail the data structure of NAME1 for managing a name;

Fig. 29 is a diagram showing in detail the data structure of NAME2 for managing a name;

Fig. 30 is a diagram showing the data structure of an ATRAK3 data file A3Dnnnnn.MSA in detail;

Fig. 31 is a diagram showing in detail the data structure of INFLIST.MSF showing the additional information;

Fig. 32 is a diagram showing in detail the data structure of INFLIST.MSF showing the additional information data;

Fig. 33 is a flowchart showing a recovery process according to the second embodiment of the present invention in the event that a FAT area has been destroyed;

Fig. 34 is a block diagram showing the construction of the reproducing apparatus according to the present invention; and

Fig. 35 is a flow chart showing a reproducing limitation information updating method according to the present invention.

Detailed description of the preferred embodiments

Then, an embodiment of the present invention will be described. Fig. 1 is a block diagram showing the construction of a digital audio recording / reproducing apparatus using a memory card according to an embodiment of the present invention. The digital audio recorder / player records and reproduces a digital audio signal using a removable memory card. In reality, the recording / reproducing apparatus consists of an audio system, that is, an amplifier, a speaker, a CD player, an MD recorder, a tuner, etc. However, it should be noted that the present invention is also applicable to others Audio recorders can be applied. In other words, the present invention can be used in a portable recording / reproducing apparatus. In addition, the present invention can be applied to a set-top box that records digital audio data that is circulated, such as satellite data communication, digital broadcasting, or the Internet. In addition, the present invention can be applied to a system that preferably records / reproduces moving picture data and still picture data to audio data. The system according to the embodiment of the present invention can record and reproduce additional information such as an image or a text other than a digital audio signal.

The recording / reproducing apparatus has an audio coding / decoding IC 10 , a security IC 20 , a DSP 30 (digital signal processor). Each of these devices consists of an IC chip. The recording / playback device has a removable memory card 40 . The IC chip of the memory card 40 has a flash memory (non-volatile memory), a memory control block and a security block. The security block has a DES encryption circuit (Data Encryption Standard). According to the embodiment, the recording / reproducing apparatus can use a microcomputer in place of the DSP 30 .

The audio encoder / decoder IC 10 has an audio interface 11 and a coding / decoding block 12 . The encoding / decoding block 12 encodes digital audio data in accordance with a highly effective encoding method and writes the encoded data to the memory card 40 . In addition, the encoding / decoding block 12 decodes encoded data read from the memory card 40 . The ATRAC3 format, ie a modification of the ATRAC (Adaptive Transform Acoustic Coding) format, which is used in Mini Disc, is used as a highly effective coding method.

With the ATRAC3 format, audio data are sampled at 44.1 kHz and with 16 bits are quantized, coded highly effectively. With the ATRAC3 format, the minimum Da  unit of audio data being processed, a sound unit (SU). 1 SU are data at data from 1024 samples (1024 × 16 bits × 2 channels) on data from several hundred bytes are compressed. The duration of 1 SU is approximately 23 ms. At that high effective coding method, the amount of data is compressed from audio data to data, which is about 10 times smaller than the original data. In contrast to ATRAC1 format, which is used for the mini disk, is used for the audio signal, which is compressed and decompressed according to the ATRAX3 format, the audio quality less deteriorated.

A line input selector 13 selectively supplies the playback output of an MD, the output of a tuner, or the playback output of a tape to an A / D converter 14 . The A / D converter 14 converts the input line signal into a digital audio signal (sampling frequency = 44.1 kHz; the number of quantization bits = 16). A digital input selector 16 optionally supplies a digital output signal from an MD, a CD or a CS (Satellite Digital Broadcast) to a digital input receiver 17th The digital input signal is transmitted via an optical cable, for example. An output signal of the digital input receiver 17 is supplied to a sampling rate converter 15 . The sampling rate converter 15 converts the digital input signal into a digital audio signal (sampling frequency = 44.1 kHz; the number of quantization bits = 16).

The coding / decoding block 12 of the audio coding / decoding IC 10 supplies the coded data to a DES encryption circuit 22 via an interface 21 of the security IC 20 . The DES encryption circuit 22 has a FIFO 23 . The DES encryption circuit 22 is arranged to protect the copyright of the content. The memory card 40 also has a DES encryption circuit. The DES encryption circuit of the recording / playback device has several master keys and a device-specific storage key. The DES encryption circuit 22 also has a random number generation circuit. The DES encryption circuit 22 can share an authorization process and a dialog key with the memory card 40 that the DES encryption circuit has. In addition, the DES encryption circuit 22 can decrypt data with the storage key of the DES encryption circuit.

The encrypted audio data output from the DES encryption circuit 22 is supplied to a DSP 30 (Digital Signal Processor). The DSP 30 communicates with the memory card 40 via an interface. In this example, the memory card 40 is attached to an attachment / detachment mechanism (not shown) of the recording / playback device. The DSP 30 writes the encrypted data into the flash memory of the memory card 40 . The encrypted data is transmitted serially between the DSP 30 and the memory card 40 . In addition, an external SRAM (Static Random Access Memory) 31 is connected to the DSP 30 . The SRAM 31 provides the recording / playback device with a sufficient storage capacity so as to control the memory card 40 .

A bus interface 32 is connected to the DSP 30 . The data is supplied from an external controller (not shown) to the DSP 30 via a bus 33 . The external control controls all operations of the audio system. The external controller supplies data, for example a recording command or a playback command, which is generated in accordance with a user actuation, via an actuating part to the DSP 30 via the bus interface 32 . In addition, the external controller supplies additional information, for example image information and character information, via the bus interface 32 to the DSP 30 . The bus 33 is a bidirectional communication path. The additional information read from the memory card 40 is supplied for external control via the DSP 30 , the bus interface 32 and the bus 33 . In reality, the external control is arranged in an amplification unit of the audio system, for example. In addition, the external control causes a display part to display the additional information, the operational status of the recorder, etc. The display part is part of the audio system. Since data exchanged via bus 33 is not copyright-protected data, it is not encrypted.

The encrypted audio data read from the memory card 40 by the DSP 30 is decrypted by the security IC 20 . The audio encoding / decoding IC 10 decodes the encoded data according to the ATRAC3 format. Output data from the audio encoder / decoder 10 are supplied to a D / A converter 18 . The D / A converter 18 converts the output data of the audio encoder / decoder 10 into an analog signal. The analog audio signal is supplied to a line output terminal 19 .

The analog audio signal is supplied to an amplifier (not shown) via the line output terminal 19 . The analog audio signal is reproduced by a speaker or headphones. The external controller supplies a mute signal to the D / A converter 18 . When the mute signal shows a mute on state, the external controller prevents the audio signal from the line output terminal 19 from being output.

Fig. 2 is a block diagram showing the internal structure of the DSP 30. Referring to FIG. 2, the DSP 30 comprises a core memory 34, a flash memory 35, an SRAM 36, a bus interface 37, a memory card interface 38 and Interbus-bridges. The DSP 30 has the same function as a microcomputer. The core memory 34 is equivalent to a CPU. The flash memory 35 stores a program that causes the DSP 30 to perform predetermined processes. The SRAM 36 and the external SRAM 31 are used as the RAM of the recording / reproducing apparatus.

The DSP 30 controls a writing process for writing encrypted audio data and the additional information on the memory card 40 in accordance with an operation signal, such as a recording command received via the bus interfaces 32 and 37 , and a reading process for reading them therefrom. In other words, the DSP 30 is arranged between the application software side of the audio system, which records / reproduces audio data and additional information, and the memory card 40 . The DSP 30 operates when the memory card 40 is accessed. In addition, the DSP 30 is operated in accordance with the software, for example a file system.

The DSP 30 manages files stored in the memory card 40 with the FAT system used in conventional personal computers. In addition to the file system, a management file is used according to the embodiment of the present invention. The management file will be described later. The management file is used to manage data files stored in the memory card 40 . The management file as the first file management information is used to manage audio data files. On the other hand, the FAT is used as the second file management information to manage all files including audio files and management files stored in the flash memory of the memory card 40 . The management file is stored in the memory card 40 . The FAT is written into the flash memory along with the route directory etc. before the memory card 40 is sent. The details of the FAT will be described later.

According to the embodiment of the present invention, the copy Right to protect data, audio data compressed according to the ATRAC3 format were encrypted. On the other hand, since it is not necessary, the copyright of the administrator protect file, not encrypted. There are two types of memory cards, and an encryption type and a non-encryption type. However, one is  Memory card for use with the recorder / playback device, which copyright-ge records protected data, limited to the encryption type.

Sound data and image data recorded by users are recorded on Memory cards of the non-encryption type recorded.

Fig. 3 is a block diagram showing the internal structure of the memory card 40. The memory card 40 comprises a control block 41 and a flash memory 42 , which are constructed as a one-chip IC. A bidirectional serial interface is arranged between the DSP 30 of the recorder / playback device and the memory card 40 . The bidirectional serial interface consists of 10 lines, ie a clock line SCK for transmitting a clock signal that is transmitted together with data, a status line SBS for transmitting a signal that shows a status, a data line DIO for transmitting data, a separating line INT , two GND lines, two INT lines and two reserved lines.

The clock line SCK is used to transmit a clock signal in synchronism with data. The status line SBS is used to transmit a signal which shows the status of the memory card 40 . The DIO data line is used to input and output a command and encrypted audio data. The separation line INT is used to transmit a separation signal which causes the memory card 40 to be disconnected from the DSP 30 of the recorder / player. When the memory card 40 is mounted in the recorder / player, the memory card 40 generates the disconnect signal. However, since the disconnect signal is transmitted over the data line DIO according to the embodiment of the present invention, the disconnect signal INT is grounded.

A serial / parallel conversion block, a parallel / serial conversion block and an interface block (S / P, P / S, I / F block) 43 is an interface between the DSP 30 of the recorder / playback device and the control block 41 of the memory card 40 is arranged. The S / P, P / S and IF block 43 converts serial data received from the DSP 30 of the recorder / player into parallel data and supplies parallel data to the control block 41 . In addition, the S / P, P / S and IF block 43 converts parallel data received from the control block 41 into serial data and supplies the serial data to the DSP 30 . When the S / P, P / S and IF block 43 receives a command and data over the data line DIO, the S / P, P / S and IF block 43 separates them into those which are normally referred to the flash memory 42 is accessed and those that are encrypted.

The data is transmitted in the format in which data is transmitted over the data line DIO after a command has been transmitted. The S / P, P / S and IF block 43 determines the code of an instruction and determines whether the instruction and data are those that are normally accessed or those that are encoded. According to the determination result, the S / P, P / S, and IF block 43 stores an instruction that is normally accessed in an instruction register 44 and stores data that is normally accessed in a page (data). buffer 45 and a write register 46 . In connection with the write register 46 , the memory card 40 has an error correction code coding circuit 47 (ECC). The error correction code encoding circuit 47 generates a redundant code which is an error correction for data temporarily stored in the page (data) buffer 45 .

Output data from the command register 44 , the page buffer 45 , the write register 46 and the error correction code encoding circuit 47 are supplied to a flash memory interface and sorter 51 (hereinafter referred to as a memory I / F sorter). The memory IF sorter 51 is an interface located between the control block 41 and the flash memory 42 and controls data exchanged therebetween. The data is written into the flash memory via the memory IF sorter 51 .

Audio data which is compressed in accordance with the ATRAC3 format and written into the flash memory (hereinafter, this audio data is referred to as ATRAC3 data) is encrypted by the security IC 20 of the recorder / player and the security block 52 of the memory card 40 , and so on to protect the copyright of the ATRAC3 data. The security block 52 comprises a buffer memory 53 , a DES encryption circuit 54 and a non-volatile memory 55 .

The security block 52 of the memory card 40 has several authorization keys and a unique memory key for each memory card. The non-volatile memory 55 stores a key that is necessary for encrypting the data. The key stored in the non-volatile memory 45 cannot be analyzed. According to the embodiment, for example, a memory key is stored in the non-volatile memory 55 . The security block 52 also has a random number generation circuit. Security block 52 authorizes a suitable recorder / playback device and thus shares a dialog key. In addition, the security block 52 again encrypts the content with the storage key via the DSE encryption circuit 54 .

If, for example, the memory card 40 is attached to the recorder / playback device, these are mutually authorized. The security IC 20 of the recorder / playback device and the security block 52 of the memory card 40 are mutually authorized. If the recorder / playback device has the attached memory card 40 as a suitable memory card and the memory card 40 has authorized the recorder / playback device as a suitable recorder / playback device, they are mutually authorized. If the mutual authorization process has been carried out successfully, the recorder / playback device and the memory card 40 generate corresponding dialog keys which they share with one another. If the recorder / playback device and the memory card 40 mutually authorize each other, they generate corresponding dialog keys.

When the content is written on the memory card 40 , the recorder / playback device encrypts a content key with a dialog key and delivers the encrypted data to the memory card 40 . The memory card 40 decrypts the content key with the dialog key, encrypts the content key again with a storage key and delivers the content key to the recorder / playback device. The memory key is a unique key for every memory card. When the recorder / player receives the encrypted content key, the recorder / player performs a formatting process for the encrypted content key and writes the encrypted content key and the encrypted content on the memory card 40 .

In the above section, the writing process for the memory card 40 has been described. Then, the reading process for the memory card 40 will be described. Data read from the flash memory 42 is supplied to the page buffer 45 , the read register 48 (RD. Reg) and the error correction circuit 49 via the memory IF sorter 51 . The error correction circuit 49 (ECC) corrects an error of the data stored in the page buffer 45 . Output data from page buffer 45 , which has been error corrected, and output data from read register 48 are supplied to S / P, P / S and IF block 43 . The output data of the S / P, P / S and IF blocks 43 are supplied to the DSP 30 of the recorder / playback device via the serial interface described above.

When data is read from the memory card 40 , the content key encrypted with the memory key and the content encrypted with the block key are read from the flash memory 42 . The security block 52 decrypts the content key with the storage key. The security block 52 decrypts the decrypted content key with the dialog key and transmits the decrypted content key to the recorder / playback device. The recorder / playback device decrypts the content key with the received dialog key and generates a block key with the decrypted content key. The recorder / playback device gradually decrypts the encrypted ATRAC3 data.

A configuration ROM 50 (CONFIG ROM) is a memory that stores the partition information, various types of attribute information, etc. of the memory card 40 . The memory card 40 also has an erase protection switch 60 . When the switch 60 is in the erase protection position, even if a command that causes the memory card 40 to erase data stored in the flash memory 42 is supplied from the recorder / player side to the memory card 40 prevents data stored in the flash memory 42 from being erased from the memory card 40 . An OSC cont. 61 is an oscillator which generates a clock signal which forms the reference of the time clock of the process of the memory card 40 .

Fig. 4 is a schematic diagram showing the hierarchy of processes of the file system of the computer system using a memory card as a storage medium. In the hierarchy, the upper hierarchy level is an application process level. The application process level is followed by a file management process level, an administrative level for logical addresses, an administrative level for a real address and an access level for a flash memory. With the above hierarchical structure, the file management process level is the FAT file system. Real addresses are assigned to the individual blocks of the flash memory. The relationship between the blocks of the flash memory and its real addresses does not change. Logical addresses are addresses that are handled logically at the level of the file management process.

Fig. 5 is a schematic diagram showing the real structure of data that the memory card 40 to be handled in the flash memory 42. In the memory 42 , a data unit (referred to as a segment) is divided into a predetermined number of blocks (fixed length). A block is divided into a predetermined number of data pages (fixed length). In the flash memory, data is deleted as a block at the same time. Data is written into the flash memory 42 or read from it page by page at the same time. The size of each block is the same. Likewise, the size of each page is the same. A block consists of page 0 to page m. For example, a block has a storage capacity of 8 KB (kilobytes) or 16 KB, for example. One page has a memory capacity of 512 bytes. If a block has a storage capacity of 8 KB, the total storage parity of the flash memory 42 is 4 MB (512 blocks) or 8 MB (1024 blocks). If a block has a memory capacity of 16 KB, the total memory capacity of the flash memory 42 is 16 MB (1024 blocks), 32 MB (2048 blocks) or 64 MB (4096 blocks).

One side consists of a data area of 512 bytes and a redundant one Range of 16 bytes. The first three bytes of the redundant area are an overwrite Area that is rewritten when data is updated. The first three bytes ent hold a block status area, a page status area and an update in succession status area. The remaining 13 bytes of the redundant area are fixed data, that depend on the content of the data area. The 13 bytes contain an administration flag rich (1 byte), a logic address area (2 bytes), a format reserve area (5 bytes), a distribution information ECC area (2 bytes) and a data ECC area (3rd Bytes). The distribution information ECC area contains redundant data for a failure correction process against the management flag area, the logic address area and the Format reserve area. The data ECC area contains redundant data for an error corpus correction process against 512-byte data.

The management flag area contains a system flag (1: user block, 0: boot block), a conversion table flag (1: invalid, 0: table block), a copy prohibition flag (1: OK, 0: NG) and an access permission flag (1: free, 0: read protection).

The first two blocks - blocks 0 and 1 - are boat blocks. Block 1 is a Fuse block of block 0. The boot blocks are header blocks that are in the memory card are valid. If the memory card is attached to the recorder / playback device, will next accessed the boat blocks. The remaining blocks are user blocks. The Page 0 of the boot block contains a header area, a system entry address area and a boot and attribute information area. Page 1 of the boot block contains one Prohibition block data area. Page 2 of the boot block contains a CIS (Card Infor mation Structure) / IDI (identify Drive Information) area.

The header of the boot block contains a boot block ID and the number of effective input addresses. The system input addresses are the starting position of the Prohibition block data, their data size, their data type, their data start position of the CIS / IDI area, their data size and their data type. The boat information and the Attribute information contains the memory card type (read-only type, rewritable type pus or hybrid type), the block size, the number of blocks, the number of all Blocks, the security / non-security type, the card manufacturing data (manufacturing date) etc.

Since the flash memory has a limit on the frequency of the order writing due to the deterioration of the insulation film, it is necessary to ver prevent the same memory area (block) from being accessed in a concentrated manner. If  thus data at a certain logical address, in a certain real address Stored, rewritten, updated data of a specific block written in an unused block, preferably to the original block. After the data is updated, the relationship between the logical address changes and the real address. This process is referred to as a swap process net. This prevents concentrated access to the same block. In order to the lifespan of the flash memory can be extended.

The logical address is associated with data written in the block. Even if the block of original data differs from the block of updated data below the address on the FAT does not change. This means that the same data can be matched send can be accessed. However, since the reordering process is in progress, one is Conversion table that relates logic addresses and real addresses is required (This table is called the logic real address translation table). Regarding the Logic-real address translation table becomes a real address, which corresponds to the logical address speaks, which will be determined at the FAT. This means that a block that is marked by a real address is determined to be accessed.

The DSP 30 stores the logic real address translation table in the SRAM. If the storage capacity of the RAM is small, the logic real address translation table can be stored in the flash memory. The logic real address translation table correlates logical addresses (2 bytes) sorted in ascending order with real addresses (2 bytes). Since the maximum memory capacity of the flash memory is 128 MB (8192 blocks), 8192 addresses can be assigned to 2 bytes. The logic real address conversion table is managed for each segment. The size of the logic real address conversion table is therefore proportional to the storage capacity of the flash memory. If the storage capacity of the flash memory is 8 MB (2 segments), 2 pages are used as the logic real address translation table for each of the segments. When the conversion table is stored in the flash memory, a predetermined bit of the management flag area in the redundant area in each page shows whether the current block is a block that contains the logic-real address translation table or not.

The memory card described above can be used with the FAT file system of a personal computer system such as the disk-shaped recording medium. The flash memory has an IPL area, a FAT area and a route directory area (not shown in Fig. 5). The IPL area contains the address of a program that is initially to be loaded into the memory of the recorder / playback device. In addition, the IPL area contains various types of storage information. The FAT area contains information related to blocks (clusters). The FAT has defined unused blocks, the next block number, defective blocks and the last block number. The path directory area contains directory entry addresses that have a file attribute. Update dates (day, month, year), the file size, etc.

Next, an administrative procedure using the FAT table will be described with reference to FIG. 6.

Fig. 6 is a schematic diagram showing a memory card. The header area of the memory card is a partition table area. The partition table area is followed by a block area, a boot sector, a FAT area, a FAT save area, a path directory area, a sub-directory area and a data area. On the memory card, logical addresses are converted into real addresses according to the logic real address conversion table.

The boat sector, the FAT area, the FAT protection area, the way ver Drawing area, the subdirectory area and the data area are as FAT partiti designated area.

The partition table area contains the start address and the end address of the FAT partition area.

The FAT used in a conventional floppy disk has no such partition table. Since the first track is just a partition table, this is an empty Be rich. The boot sector contains the size of the FAT structure (12 bit FAT or 16 bit FAT) Cluster size and the size of each area. The FAT is used for the Posi tion of a file that is recorded in the data area. The FAT copy area is a FAT protection area. The path directory area contains file names whose start Cluster addresses and various attributes thereof. The route directory area is used 32 bytes per file.

The subdirectory area is obtained as a directory through a directory attribute file. In the embodiment shown in Fig. 6, the sub-directory area has 4 files named PBLIST.MSF, CAT.MSF, DOG.MSF and MAN.MFA. The subdirectory area is used to manage file names and recording positions in the FAT. In other words, the slot of the file name CAT.MSF is assigned the address "5" in the FAT. The slot of the file name DOG.MSF is assigned to the address "10" in the FAT. An area after cluster 2 is used as a data area. In this embodiment, audio data compressed according to the ATRAC3 format is recorded. The header slot of the file name MAN.MSA is assigned to the address "110" in the FAT. According to the embodiment of the present invention, audio data with the file name CAT.MSF is recorded in cluster 5 to 8. Audio data from DOG-1 as the first half of the file with the file name DOG.MSF is recorded in clusters 10 to 12. Audio data DOG-2 as the second half of the file with the file name DOG.MSF are recorded in clusters 100 and 101. Audio data with the file name MAN.MSF is recorded in clusters 110 and 111.

In the embodiment of the present invention, an example in which a single file is divided into two areas and recorded scattered. At In the embodiment, an "Empty" area in the data area is a writable area. An area after cluster 200 is used to manage file names. The Da tei CAT.MSF is recorded in cluster 200. The file DOG.MSF is in cluster 201 recorded. The MAN.MSF file is recorded in cluster 202. If the positions the files are changed, the area is rearranged after the cluster 200. If the Memory card is attached, the beginning and end of the FAT partition area will be in train recorded on the header partition table area. After the boot sector area is reproduced, the route directory area and the sub-directory area are repro induced. The slot of the playback management information PBLIST.MSF in the subdirectory range is determined. This will be the address of the end of the slot of the file PBLIST.MSF received. In this embodiment, since the address "200" is at the end of the PBLIST.MSF file is referenced to cluster 200.

The area after cluster 200 is used to manage the order of playback of files. In the embodiment, the CAT.MSA file is the first program. The DOG.MSA file is the second program. The MAN.MSA file is the third program. After referring to the area after cluster 200, the slots of the files CAT.MSA, DOG.MSA and MAN.MSA are referenced. In Fig. 6, the end of the slot of the CAT.MSA file is assigned the address "5". The end of the slot of the DOG.MSA file is assigned to the address "10". The end of the slot in the MAN.MSA file is assigned to the address "110". If an input address is searched for on the FAT with the address "5", the cluster address "6" is obtained. If an input address on the FAT with the address "6" is sought, the cluster address "7" is obtained. When an input address on the FAT with the address "8" is searched, the code "FFF" showing the end is obtained. The file CAT.MSA thus uses clusters 5, 6, 7 and 8. With regard to clusters 5, 6, 7 and 8 in the data area, a region of the ATRAC3 data with the file name CAT.MSA can be accessed.

Then there is a procedure to locate the DOG.MSF file that is scattered was recorded. The end of the slot in the DOG.MSA file is the Assigned address "10". If an input address on the FAT with the address "20" ge the cluster address "11" is obtained. If an input address on the FAT is searched with the address "11" as a reference, the address "12" is obtained. When a Input address on the FAT with address "12" is searched for, the clu Received address "101". If reference is made to the input address "101", received the code "FFF", which shows the end. So the file DOG.MSF uses Cluster 10, 11, 12, 100 and 101. When reference is made to clusters 10, 11 and 12, the first part of the ATRAC3 data of the DOG.MSF file can be accessed. When on the clu ster 100 and 101 can be referred to the second part of the ATRAC3 data DOG.MSF file can be accessed. If also an input address on the FAT with the address "110" is searched, the cluster address "101" is obtained. If an on address "101" on which FAT is searched with the address "101", the code "FFF", that shows the end. It is therefore clear that the MAN.MSA file contains clusters 110 and 111 used. As described above, data files that are scattered in flash memory can linked and reproduced one after the other.

According to the embodiment of the present invention, in addition to the file management system defined in the format of the memory card 40 , the management file is used to manage tracks and parts of music files. The management file is recorded on a user block of the flash memory 42 of the memory card 40 . Thus, as will be described later, even if the FAT of the memory card 40 is destroyed, a file can be restored.

The management file is generated by the DSP 30 . When the power supply of the recorder / player is turned on, the DSP 30 determines whether the memory card 40 is attached to the recorder / player or not. When the memory card has been attached, the DSP 30 authorizes the memory card 40 . If the DSP 30 has successfully authorized the memory card 40 , the DSP 30 reads the boot block of the flash memory 42 . With this, the DSP 30 reads the real logic address translation table and stores the read data in the SRAM. The FAT and the route directory have been written into the flash memory of the memory card 40 before the memory card 40 is sent. When the data is recorded on the memory card 40 , the management file is created.

In other words, a record command issued by the user's remote control or the like is supplied to the DSP 30 from the external controller via the bus and the bus interface 32 . The encoder / decoder IC 10 compresses the received audio data and supplies the resulting ATRAC3 data to the security IC 20 . The security IC 20 encrypts the ATRAC3 data. The encrypted ATRAC3 data is recorded in the flash memory 42 of the memory card 40 . Then the FAT and the administration file are updated. When a file is updated (actually, when the audio data recording process is completed), the FAT and the management file stored in the SRAMs 31 and 36 are rewritten. When the memory card 40 is removed or the voltage of the recorder / playback device is switched off, the FAT and the management file, which are ultimately provided by the SRAMs 31 and 36 , are stored in the flash memory 42 . Alternatively, when the recording process of the audio data is finished, the FAT and the management file written in the flash memory 42 can be rewritten. When audio data is edited, the contents of the management file are updated.

In the data structure according to the embodiment, the additional information is contained in the management file. The additional information is updated and recorded in the flash memory 42 . In another data structure of the management file, the additional information management file is generated next to the track management file. The additional information is supplied by the external control via the bus and the bus interface 32 to the DSP 30 . The additional information is recorded in the flash memory 42 of the memory card 40 . Since the additional information is not supplied to the security IC 20 , it is not encrypted. When the memory card 40 is removed from the recorder / playback device or its voltage is switched off, the additional information from the SRAM of the DSP 30 is written into the flash memory 42 .

Fig. 7 is a schematic diagram showing the file structure of the memory card 40 . As a file structure there is a still picture directory, a moving picture directory, a sound directory, a control directory and a music directory (HIFI). According to the embodiment, music programs are recorded and reproduced. Then the music directory is described. The music directory has two types of files. The first type is a playback management file BLIST.MSF (hereinafter referred to as PBLIST). The other type is an ATRAC3 data file A3Dnnnn.MSA, which stores encrypted music data. The music directory can store up to 400 ATRAC3 files (ie 400 music programs). The ATRAC3 data files are registered in the playback management file and are generated by the recorder / playback device.

Fig. 8 is a schematic diagram showing the structure of a playback management file. Fig. 9 is a schematic diagram showing the file structure of an ATRAC3 data file. The playback management file is a file with a fixed length of 16 KB. An ATRAC3 data file consists of an attribute header and an encrypted music data area for each music program. The attribute data has a fixed length of 16 KB. The structure of the attribute header is similar to that of the playback management file.

The playback management file shown in Fig. 8 consists of a header, a memory card name NM-1S (for the one-byte code), a memory card name NM2-S (for the two-byte code), a program play sequence table TRKTBL, and one Additional memory card information INF-S. The attribute data header (shown in FIG. 9) at the beginning of the data file consists of a data header, a program name NM1 (for the one-byte code), a program name NM2 (for the two-byte code), the track information TRKINF (for example, the track key information), the partial information PRTINF, and the track additional information INF. The data header contains information on the number of total parts, the attribute of the name, the size of the additional information, etc.

The ATRAC3 music data follow the attribute data. The music data are each block segmented at 16 KB. Each block begins with a header. The data header contains an initial value for decrypting encrypted data. Only music data one ATRAC3 data files are encrypted. So the other data, for example the Playback management file, header, etc. not encrypted.

Then, the relationship between music programs and ATRAC3 data files will be described with reference to Figs. 10A to 10C. A track is equivalent to a music program. In addition, a music program consists of an ATRAC3 data word (see Fig. 9). The ATRAC3 data file is audio data that has been compressed in accordance with the ATRAC3 format. The ATRAC3 data file is simultaneously recorded on the memory card 40 as a cluster. A cluster has a capacity of 16 KB. Multiple files are not included in a cluster. The minimum data erase unit of flash memory 42 is one block. In the case of the memory card 40 for music data, a block is a synonym for a cluster. In addition, a cluster is equivalent to a sector.

A music program basically consists of one part. However, if a Mu sic program is edited, a music program can be composed of several parts  his. A part is a unit of data that is recorded sequentially. Usually be there is a track from one part. The connection of parts of a music program is with of the partial information PRTINF managed in the attribute data header of the music program. On The partial size is expressed by the partial size PRTSIZE (4 bytes) of the partial information mation PRTINF shown. The first two bytes of the PRTSIZE part size indicate the number of all clusters of the current part. The next two bytes show the positions the starting unit (SU) and the end tone unit (SU) from the beginning or last cluster. Here a sound unit is abbreviated as SU. With such a partial representation, if Mu music data are edited, the shifting of the music data is suppressed. If Mu sikdaten be edited for each block, although their shift are suppressed the editing block of a block is much larger than the editing unit of an SU.

The SU is the minimum unit of a part. The SU is also the Mini Data unit in the event that audio data is compressed in accordance with the ATRAC3 format be lubricated. A SU is audio data, of which data from 1024 samples at 44.1 kHz (1024 x 16 bits x 2 channels) are compressed into data that is approximately 10 times smaller than the original data. The duration of an SU is approximately 23 ms. Usually part consists of several thousand SU. If a cluster consists of 42 SU, it allows one Cluster that a tone of one second is generated. The number of parts that make up a track form depends on the size of the additional information. Since the number of tracks by Sub traction of the data header, the program name, the additional data etc. from a block can hold, if there is no additional information, the maximum number of parts (645 parts) can be used.

Fig. 10A is a schematic diagram showing the file structure in the case where two music programs on a CD or the like are sequentially recorded. For example, the first program (file 1) consists of 5 clusters. Since a cluster cannot contain two files from the first and second programs, file 2 starts from the beginning of the next cluster. Thus, the end of part 1 (part 1) corresponding to file 1 is in the middle of a cluster, and the remaining area of the cluster contains no data. In the same way, the second piece of music (file 2) consists of one part. In the case of file 1, the partial size is 5. The first cluster begins at the 0th SU. The last cluster ends at the 4th SU.

There are four types of editing processes; H. a sub-process, a combination process, an erase process and a move process. The subprocess is carried out by a track is divided into two areas. When the sub-process is carried out, it increases Number of total tracks by one. In the sub-process, one file is divided into two files in the  File system divided. Thus, in this case, the playback management file and the FAT updated. The combining process is done to make two tracks into one track to combine. When the combination process is carried out, the number of Total traces by one. In the combination process, two files become one file in the File system combined. Thus, when the combination process is carried out, the Playback management file and the FAT updated. The deletion process is carried out to delete a track. Take the track numbers after the track that was deleted one after the other. The shifting process is performed to change the track sequence. Thus, when the deleting process or the moving process is performed, the how delivery management file and the FAT updated.

Fig. 10B is a schematic diagram showing the combination result of two programs (file 1 and file 2) shown in Fig. 10A. As a result of the combination process, the combination file consists of two parts (part 1, part 2). Fig. 10C is a schematic illustration showing the division result, wherein a program (file 1) is divided in the center of the cluster. 2 Through this sub-process, the file consists of clusters 0, 1 and the start area of cluster 2. File 2 consists of the end area of cluster 2 and clusters 3 and 4.

As described above, according to the embodiment of the present invention, since the partial display is fixed, the combination result (see FIG. 10B), the start position of the part 1, the end position of the part 1 and the end area of the part 2 can be determined with SU. Thus, in order to pack the space due to the combination result, it is not necessary to shift the music data of part 2. In addition, as a dividing result (see FIG. 10C), it is not necessary to move data and to pack the space at the beginning of file 2.

Fig. 11 is a schematic diagram showing the detailed data structure of the playback management file PBLIST. FIG. 12A and 12B show a Datenkopfbe rich and the remaining portion of the reproduction management file PBLIST recovery. The size of the playback management file is a cluster (1 block = 16 KB). The size of the header shown in Fig. 12A is 32 bytes. The rest of the playback management file PBLIST shown in Fig. 12B contains a name area NM1-S (256 bytes) (for the memory card), a name area NM2-S (512 bytes), a content key area, a MAC area, an S -YMDhms area, a playback sequence management table area TRKTBL (800 bytes), a memory card additional information area INF-S (14720 bytes) and a header redundancy area. The starting positions of these areas are defined in the playback management file.

The first 32 bytes (0x0000) through (0x0010) shown in Fig. 12A are used for the header. In the file, 16-byte areas are called slots. Referring to Figure 12A, the header is located in the first and second slots. The data head contains the following areas. An area designated by "reserved" (res.) Is an unspecified area. Usually a zero (0x00) is written in a reserved area. However, when data is written to a reserved area, the data written in that area is ignored. In a future version, some reserved areas can be used. In addition, data is prevented from being written to a reserved area. If an option area is not used, it is treated as a reserved area.

• - BLKID-TLO (4 bytes)
  Meaning: BLOCKID FILE ID
  Function: identifies the head of the playback management file
  Value: Fixed value = "TL = 0" (for example, 0x544C2D30)
• - MCode (2 bytes)
  Meaning: MAKER CODE (manufacturer code)
  Function: identifies the manufacturer and model of the recorder / player
  Value: "Higher order 10 bits (manufacturer code); Lower order 6 bits (model code).
• - REVISION (4 bytes)
  Meaning: Number of rewriting frequencies of PBLIST
  Function: incremented when the playback management file is rewritten.
  Value: Start at 0 and increment by 1.
• - S-YMDhms (4 bytes) (option)
  Meaning: year, month, day, hour, minute and second, which are recorded by the recorder or the playback device with a reliable clock.
  Function: identifies the last recording date and time.
  Value: Bits 25 to 32: Year 0 to 99 (1980 to 2079)
  Bits 21 to 24: month 0 to 12
  Bits 16 to 20: day 0 to 31
  Bits 11 to 15: hour 0 to 23
  Bits 05 to 10: minute to 59
  Bits 00 to 04: seconds 0 to 29 (two-bit interval)
• - SY1C + L (2 bytes)
  Meaning: Attribute of the name (one-byte code) of the memory card, which was written in the NM1-S area.
  Function: shows the character code and the language code as a one-byte code.
  Value: Character code (C): higher-order one byte
  00: no character code, binary number
  01: ASCII (American Standard Code for Information Interchange)
  02: ASCII + KANA
  03: modified 8859-1
  81: MS-JIS
  82: KS C 5601-1989
  83: GB (Great Britain) 2312-80
  90: S-JIS (Japanese Industrial Standards for Voice)
  Language code (L): low-value one-byte identifies the language based on the EBU-Tech 32 58 standard.
  00: no setting
  08: German
  09: English
  0A: Spanish
  0F: French
  15: Italian
  1D: Dutch
  65: Korean
  69: Japanese
  75: chinese
  If data is not recorded, the area is always 0.
• - SN2C-L (2 bytes)
  Meaning: Attribute of the name of the memory card in the NM2-S area.
  Function: shows the character code and the language, coded as a one-byte code.
  Value: like SN1C + L
• - SINFSIZE (2 bytes)
  Meaning: Total size of the additional information on the memory card in the INF-S area.
  Function: shows the data size as an increment of 16 bytes. If data is not recorded, this area is always 0.
  Value: Size: 0x0001 to 0x39C (924)
• - T-TRK (2 bytes)
  Meaning: TOTAL TRACK NUMBER (total number of tracks)
  Function: shows the total number of tracks
  Value: 1 to 0x0190 (max. 400 tracks)
  When data is recorded, this area is always 0.
• - VerNo (2 bytes)
  Meaning: format version number
  Function: shows the major version number (high-order one-byte) and the minor version number (low-order one-byte)
  Value: 0x0100 (Ver 1.0)
  0x0203 (Ver 2.3)
  Subsequently, areas (see Fig. 13B) which are preceded by the header are described.
• - NM1-S
  Meaning: Name of the memory card (as a one-byte code)
  Function: shows the name of the memory card as a one-byte code (maximum 256). An end code (0x00) is written at the end of this area. The size is calculated from the end code. If data is not recorded, zeros (0x00) from the beginning (0x00) of this area are recorded for at least one byte.
  Value: different character code
• - NM2-S
  Meaning: Name of the memory card (as a two-byte code)
  Function: shows the name of the memory card as a two-byte code (maximum 512). A code (0x00) is written at the end of this area. The size is calculated from the end code. If data is not recorded, zeros (0x00) from the beginning (0x0120) of this area are recorded for at least two bytes.
  Value: different character code
• - CONTENTS KEY
  Meaning: Value for music program. Protected with MG (M) and saved as CONTENTS KEY
  Function: used as a key, which is necessary for the MAC calculation of S-YMDhms.
  Value: 0 to 0xFFFFFFFFFFFFFFFF
• - MAC
  Meaning: copyright information check value that takes the lead
  Function: shows the value generated with S-YMDhms and CONTENTS KEY.
  Value: 0 to 0xFFFFFFFFFFFFFFFF
• - TRK-nnn
  Meaning: SQN (sequence) number of the ATRAC3 data file that was reproduced.
  Function: shows FNo from TRKINF.
  Value: 1 to 400 (0x190)
  if there is no track, this area is 0 in total.
• - INF-S
  Meaning: Additional information on the memory card (for example in relation to photos, songs, tours, etc.)
  Function: shows the additional information with a variable length with a data header. Several types of additional information can be used. Each of the types of additional information has an ID and a data size. Each additional information area including a data header consists of at least 16 bytes and a multiple of 4 bytes. See the following section for details.
  Value: see section "Data structure of the additional information".
• - S-YMDhms (4 bytes) (option)
  Meaning: year, month, day, hour, minute and second, which are recorded by the recorder or the playback device with a reliable clock.
  Function: identifies the last recording date and the recording time. In the case of EMD, this area is the administrator.
  Value: Bits 25 to 31: Years 0 to 99 (1980 to 2079)
  Bits 21 to 24: month 0 to 12
  Bits 16 to 24: day 0 to 31 bits 11 to 15: hour 0 to 23
  Bits 05 to 10: minute 0 to 59
  Bits 00 to 04: second 0 to 29 (two-second interval).

As the last slot of the playback management file, the same BLKID TLO, MCode and REVISION like those written for the data header.

While data is being recorded on a memory card, it can can be solved accidentally or unintentionally or the power supply to the Recorder / playback device. If such an improper loading drive is carried out, an error should be determined. As described above is a Revi area (REVISION) at the beginning and end of each block. If When data is rewritten, the value of the revision area is incremented. When a faulty termination takes place in the middle of a block, the value of the revision code fits at the beginning of the block does not match the value of the revision area at the end of the block. Such an incorrect termination can thus be determined. Since there are two revision areas non-normal termination can be determined with a high probability become. If a abnormal termination is detected, an alarm, for example generated an error message.

Since the fixed value BLKID-TLO at the beginning of a block (16 KB) ge is written, when the FAT is destroyed, the fixed value becomes the reference for data again manufacturing used. In other words, the reference to the fixed value can Type of file can be determined. Because the fixed value BLKID-TLO redundant in the data head and the tail of each block is written, reliability can be assured be put. Alternatively, the same playback management file can be set up redundantly be drawn.

The amount of data in the ATRAC3 data file is much larger than that in the Spurinfor mation management file. In addition, as will be described later, becomes a block number BLOCK SERIAL added to the ATRAC3 data file. However, since several ATRAC3-Da files are recorded on the memory card to avoid them redundant, both CONNUMO and BLOCK SERIAL are used. Otherwise it will if the FAT is destroyed, difficult to restore the file. In other words, can an ATRAC3 data file consist of several blocks that are scattered. Around the blocks to identify the same file, CONNUMO is used. To continue the order BLOCK SERIAL is used to identify blocks in the ATRAC3 data file.

In the same way, the manufacturer code (MCode) is at the beginning and at the end of each block recorded redundantly, so that the manufacturer and the model in one  Identify case that a file has been improperly recorded in the state where the FAT was not destroyed.

Fig. 12C is a schematic illustration showing formation data to build additional Add. The additional information consists of the following data header and variable length data. The head has the following areas.

• - INF
  Meaning: FIELD-ID
  Function: represents the beginning of the additional information (fixed value)
  Value: 0x69
• - ID
  Meaning: Additional information key code
  Function: represents the category of additional information.
  Value: 0 to 0xFF
• - SIZE
  Meaning: size of the individual additional information
  Function: shows the size of each type of additional information. Although the data size is not limited, it should be at least 16 bytes and a multiple of 4 bytes. The rest of the data should be filled with zeros (0x00).
  Value: 16 to 14784 (0x39C0)
• - MCode
  Meaning: MAKER CODE
  Function: identifies the manufacturer and model of the recorder / player
  Value: higher order 10 bits (manufacturer code), lower order 10 bits (device code).
• - C + L
  Meaning: Attribute of characters in the data area starting from byte 12.
  Function: shows the character code and the language code as a one-byte code.
  Value: like SNC + L
• - DATA
  Meaning: individual additional information
  Function: shows each type of additional information with variable length data. Real data always start from byte 12. The length (size) of the real data should be at least 4 bytes and a multiple of 4 bytes. The rest of the data area should be filled with zeros (0x00).
  Value: determined individually according to the content of each type of additional information.

Fig. 13 is a table that relates key code values (0 to 63) of the additional information to their types. The key code values (0 to 31) are assigned to the musical character information. The key code values (32 to 63) are assigned to URLs (Uniform Resource Lactor) (web information). The musical character information and the URL information contain the character information of the album title, the subtitle, the name of the artist, the CM, etc. as additional information.

Fig. 14 is a table relating key code values (64 to 127) of the additional information and their types. The key code values (64 to 95) are assigned to paths / others. The key code values (96 to 127) are assigned control data / numerical data. For example, ID = 98 shows the TOC-ID as additional information. The TOC-ID shows the first music program number, the last music program number, the running program number, the total duration of the performance and the running music program duration according to the TOC information of a CD (Compact Disc).

Fig. 15 is a table which relates key code values (128 to 159) of the additional information to the types thereof. Key code values (128 to 159) are associated with the synchronous playback information. In Fig. 15 EMD is representative of electronic music distribution (electronic music distribution).

Subsequently, real examples of additional information are described with the aid of FIGS. 16A to 16E. As with FIG. 12C, FIG. 16A shows the data structure of the additional information. In Fig. 16B, the key code ID = 3 (artist name as additional information). SIZE = 0x1C (28 bytes), which shows that the data length of the additional information including the data header is 28 bytes; C + L show that the character code C = 0x01 (ASCII) and the language code L = 0x09 (English). The variable length data after byte 12 show one-byte data "SIMON &GRAFUNKEL" as artist name. Since the data length of the additional information should be a multiple of 4 bytes, the rest is filled with (0x00).

In Fig. 16C, the key code ID = 97, which shows this ISRC (International Standard Recording Code: Copyright Code) as additional information. Size (SIZE) = 0x14 (20 bytes), which shows that the data length of the additional information is 20 bytes. C = 0x00 and L = 0x00, which shows that the characters and language are not set. So the data is the binary code. The variable length data is an eight-byte ISRC code that shows the copyright information (nation, copyright owner, year of record and manufacturer number).

In Fig. 16D, the key code is ID = 97, which shows recorded data and time as additional information. SIZE = 0x10 (16 bytes), which shows that the data length of the additional information is 16 bytes. C = 0x00 and L = 0x00, which shows that the characters and language are not set. The variable length data is a four-byte code (32 bits) that shows the recording date and time (year, month, day, hour, minute, second).

In Fig. 16E, the key code is ID = 107, which shows a playback log as set information. SIZE = 0x10 (16 bytes), which shows that the data length of the additional information is 16 bytes. C = 0x00 and L = 0x00, which shows that the characters and the language are not set. The length data variables are a four-byte code that shows a replay log (year, month, day, hour, minute, second). If the recorder / player has a playback log function, it records 16 bytes of data each time it reproduces music data.

Fig. 17 is a diagram showing a data arrangement of the ATRAC3 data file A3Dnnnn in the case that 1SU is N bytes (for example, N = 384 bytes). Fig. 17 shows an attribute header (1 block) of a data file and a music data file (1 block). Fig. 17 shows the first byte (0x0000 to 0x7FF0) of each slot of the two blocks (16 × 2 = 32 kBytes). As shown in Fig. 18, the first 32 bytes of the attribute header are used as the header; 256 bytes are used as the music program area NM1 (256 bytes); and 512 bytes are used as the music program title area NM2 (512 bytes). The header of the attribute header contains the following areas.

• - BLKID-HD0 (4 bytes)
  Meaning: BLOCKID FIELD ID
  Function: identified header of an ATRAC3 data file.
  Value: Fixed value = "HD = 0" (e.g. 0x48442D30)
• - MCode (2 bytes)
  Meaning: MAKER CODE (manufacturer code (MCode))
  Function: identifies the manufacturer and model of the recorder / player
  Value: higher order 10 bits (manufacturer code); least significant 6 bits (device code)
• - BLOCK SERIAL (4 bytes)
  Meaning: serial track number
  Function: starts from 0 and increments with 1. Even when editing a music program, this value does not vary.
  Value: 0 to 0xFFFFFFFF
• - N1C + L (2 bytes)
  Meaning: shows the attribute of data (NM1) of a track (music program title).
  Function: shows the character code and the language code of NM1 as a one-byte code.
  Value: like SN1C + L
• - N2C + L (2 bytes)
  Meaning: shows the attribute of data (NM2) of a track (music program title)
  Function: shows the character code and the language code of NM1 as a one-byte code.
  Value: like SN1C + L
• - INFSIZE (2 bytes)
  Meaning: Total size of the additional information of a running track.
  Function: shows the data size as a multiple of 16 bytes. If data is not recorded, this area should always be 0.
  Value: 0x0000 to 0x3C6 (966)
• - T-PRT (2 bytes)
  Meaning: Number of total bytes
  Function: shows the number of parts that make up the running track, normally the value of T-PRT is 1.
  Value: 1 to 285 (645 dec).
• - T-SU (4 bytes)
  Meaning: Number of total SU.
  Function: shows the total number of SUs in a track, which is equivalent to the program execution time.
  Value: 0x01 to 0x001FFFFF
• - INX (2 bytes) (option)
  Meaning: relative position of INDEX
  Function: used as a pointer that shows the head of a representative area of a music program. The value of INX is determined with a value in which the number of SU is divided by 4 as the current position of the program. This value of INX is equivalent to four times and greater than the number of SU (approximately 93 ms).
  Value: 0 to 0xFFFF (maximum about 6084 s)
• - XT (2 bytes) (option)
  Meaning: Playback time of INDEX
  Function: determines the playback time determined by INX-nnn with a value at which the number of SU is divided by 4. The value of INDEX is equivalent and greater than four times the normal SU (about 93 ms).
  Value: 0x0000 (no setting); 0x01 to 0xFFFE (up to 6084 s); 0xFFFF (until the end of the music program).
  Then the music program title areas NM1 and NM2 be described.
• - NM1
  Meaning: String of the music program title.
  Function: shows a music program title as a one-byte code (up to 256 characters) (variable length). The title area should end with an end code (0x00). The size should be calculated from the end code. If data is not recorded, zeros (0x00) from the beginning (0x0020) of the range should be recorded for at least one byte.
  Value: different character codes
• - NM2
  Meaning: String of the music program title
  Function: represents a music program title as a two-byte code (up to 512 characters) (variable length). The title area should end with an end code (0x00). The size should be calculated from the end code. If data is not recorded, zeros (0x100) from the beginning (0x0120) of the area should be recorded for at least two bytes.
  Value: different character codes

Data of 80 bytes from the beginning of the fixed position (0x320) of the attribute data header is called the track information area TRKINF. This area is mainly used to manage the security information and the copy control information. Fig. 19 shows a part of TRKINF. The TRKINF area contains the following areas.

• - CONTENTS KEY (8 bytes) (content key)
  Meaning: Value for each music program. The value of CONTENTS KEY is protected in the security block of the memory card and then saved.
  Function: used as a key to reproduce a music program. It should be used to calculate the value of MAC.
  Value: 0 to 0xFFFFFFFFFFFFFFFF
  = MAC (8 bytes)
  Meaning: copyright information check value that takes the lead
  Function: shows the value generated with multiple values of TRKINF, including the content accumulation numbers and the secret sequence number.

The secret sequence number is a sequence number recorded in a secret area of the memory card. A non-copyright protection recorder cannot read data from the secret area of the memory card. On the other hand, a copyright protection recorder and a computer that works with a program that can read data from a memory card can access the secret area.

• - A (1 byte)
  Meaning: partial attribute
  Function: shows the information as compression mode of a part.
  Value: the details are described below (see Fig. 19 and 20).

First, the value of area A is described. In the following description the mono-aural mode (N = 0 or 1) is defined as the special connection mode, at which the bit 7 = 1, the subsignal = 0, the main signal = (L + R). A playback device with no copyright protection can ignore the information of bits 2 and 1.

Bit 0 of area A shows the information on the on / off status of the emphasis. Bit 1 of area A shows the reproduction information of a skip or normal reproduction. Bit 2 of area A shows the information of the data type, for example audio data, FAX data or the like. Bit 3 of area A is not determined. The mode information of ATRAC3 is determined by a combination of bits 4, 5 and 6, as shown in FIG. 20. In other words, N is a mode value of 3 bits. For 5 modes that are mono-aural (N = 0 or 1), LP (N = 2), SP (N = 4), EX (N = 5) and HQ (N = 7), the recording time is (only 64 MB memory card), the data transfer rate and the number of SU per block. The number of bytes of 1 SU depends on each mode. The number of bytes of 1 SU in mono-aural mode is 136 bytes. The number of bytes of 1 SU in LP mode is 192 bytes. The number of bytes of 1 SU in SP mode is 304 bytes. The number of bytes of 1 SU in EX mode is 384 bytes. The number of bytes of 2 SU in HQ mode is 512 bytes. Bit 7 of area A shows ATRAC3 modes (0: dual, 1: connection).

For example, an example using a 64MB memory card in SP mode is described. A 64 MB memory card has 3968 blocks. In SP mode, since 1 SU is 304 bytes, a block has 53 SU. 1 SU is equivalent (1024/44100) seconds. So one block (1024/44100) × 53 × (3968-10) = 4863 seconds = 81 minutes. The transmission rate is (44100/1024) × 304 × 8 = 104737 bps.

• - LT (1 byte)
  Meaning: Playback limitation flag (bits 7 and 6) and security partition (bits 5 to 0).
  Function: shows a limitation of the current track.
  Value: Bit 7: = no limitation, 1 = limitation.
  Bit 6: 0 = not expired, 1 = expired
  Bits 5 to 0: security partition (no playback except 0).
• - FNo (2 bytes)
  Meaning: file number
  Function: shows the track number initially recorded, which determines the position of the MAC calculation value recorded in the secret area of the memory card.
  Value: 1 to 0x190 (400)
• - MG (D) SERIAL-nnn (16 bytes)
  Meaning: shows the serial number of the security block (security IC 20 ) of the recorder / player.
  Function: unique value for each recorder / player
  Value: 0 to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
  = CONNUM (4 bytes)
  Meaning: content accumulation number
  Function: shows a unique value that is accumulated for each music program. The value is managed by the security block of the recorder / playback device. The upper limit of the value is 2 ³² , that is, 4,200,000,000. Used to identify a recorded program.
  Value: 0 to 0xFFFFFFFF
  YMDhms-S (4 bytes) (option)
  Meaning: Playback start date and time of the track with playback limitation
  Function: shows the date and time at which data reproduction with EMD is permitted.
  Value: like the representation of the date and time of other areas
• - YMDhms-F (4 bytes) (option)
  Meaning: Reproduction of end dates and the time of the track with playback limitation.
  Function: shows the date and time at which data reproduction with EMD expired.
  Value: like the date and time of the other areas
• - MT (1 byte) (option)
  Meaning: Maximum value of the number of allowed playback frequencies
  Function: shows the maximum number of plays determined by EMD
  Value: 1 to 0xFF. If not used, the value of the range MT is 00.
• - CT (1 byte) (option)
  Meaning: Number of playback frequencies
  Function: shows the number of playback frequencies for the number of permitted playbacks. When data is reproduced, the value of the area CT is decremented.
  Value: 0x00 to 0FF. If not used, the value of the area CT is 0x00. If bit 7 of area LT is 1 and the value of area CT is 00, data is prevented from being reproduced.
• - CC (1 byte)
  Meaning: COPY CONTROL
  Function: controls the copy operation
  Value: Bits 6 and 7 show the copy control information. Bits 4 and 5 show the copy control information of a high speed digital copy operation. Bits 2 and 3 show a security block authorization value. Bits 0 and 1 are not determined.
  Example of CC:
  (Bits 7 and 6)
  11: unlimited copy operation allowed
  01: Copying prohibited
  00: one-time copying allowed (bits 3 and 2)
  00: analog / digital input record MG permission value is 0.
  When the digital recording operation using data from a CD is performed, (bits 7 and 6) = 00 and (bits 3 and 2) = 00.
• - CN (1 byte) (option)
  Meaning: Number of permitted copy frequencies in the high-speed serial copy management system.
  Function: extends the copy approval with the number of copies, not limited to a one-time copy approval and free copy approval. Valid only in the first generation of copies. The value of the area CN is decremented when the copying operation is performed.
  Value:
  00: copy prohibited
  01 to 0xFE: frequency
  0xFF: unlimited copying frequency

The track information area TRKINF is followed by a 24-byte sub-management information area (PRTINF) starting from 0x0370. When a track is composed of several parts, the values of the areas PRTINF of the individual parts are arranged one after the other on the time axis. Fig. 22 shows a part of the area PRTINF. The areas in the PRTINF area are then described in the order of their arrangement.

• - PRTSIZE (4 bytes)
  Meaning: part size
  Function: shows the size of a part.
  Cluster: 2 bytes (highest position), start SU: 1 bytes (upper position), end SU: 1 bytes (lowest position).
  Value: Cluster: 1 to 0x1F40 (8000)
  Start SU: 0 to 0xA0 (160)
  End SU: 0 to 0xA0 (16) (note that SU starts from 0).
• - PRTKEY (8 bytes)
  Meaning: partial encryption value
  Function: encrypts a part. Initial value = 0. Note that editing rules should be applied to.
  Value: 0 to 0xFFFFFFFFFFFFFFFF
• - CONNUMO (4 bytes)
  Meaning: initially generated content accumulation number key
  Function: uniformly determines an ID of the content
  Value: same value as the value of the content accumulation number start value key.

As shown in Fig. 17, the attribute header of an ATRAC3 data file contains additional information INF. The additional information is the same as the additional information INF-S (see Figs. 11 and 12B) of the reproduction management file except that the start position is not fixed. The last byte position (a multiple of 4 bytes) at the end of one or more parts is followed by data of the additional information INF.

• - INF
  Meaning: Additional information regarding the track
  Function: shows the additional variable length information with a data header. Several different types of additional information can be arranged. Each of the additional information areas has an ID and a data size. Each additional information area consists of at least 16 bytes and a multiple of 4 bytes.
  Value: as the additional information INF-S of the playback management file.

The attribute header described above is followed by data from each block of the ATRAC3 data file. As shown in Fig. 23, a header for each block is added. Then data of each block is written.

• - BLKID-A3D (4 bytes) </ 45550 00070 552 001000280000000200012000285914543900040 0002010010497 00004 45431DL <Meaning: BLOCKID FILE ID
  Function: identifies the header of the ATRAC3 data.
  Value: Fixed value = "A3D" (e.g. 0x41334420)
• - MCode (2 bytes)
  Meaning: MAKER CODE (manufacturer code)
  Function: identifies the manufacturer and model of the recorder / playback device
  Value: higher order 10 bits (manufacturer code); least significant 6 bits (model code)
• - CONNUMO (4 bytes)
  Meaning: cumulative number of initially formed content
  Function: determines a unique ID for the content. Even when the content is edited, the value of the CONNUMO area is not changed.
  Value: equal to the content of the accumulation-number-initial key
• - BLOCK SERIAL (4 bytes)
  Meaning: serial number assigned to each track.
  Function: starts from 0 and is incremented by 1. Even if the content is edited, the value of the Block SERIAL area is not changed.
  Value: 0 to 0xFFFFFFFF
• - BLOCK-SEED (8 bytes)
  Meaning: Key for encrypting a block
  Function: The beginning of the block is a random number that is generated by the security block of the recorder / playback device. The random number is followed by a value that is incremented by 1. If the value of the BLOCKSEED area is lost because the sound is not generated equivalent to a block for about one second, the same data is written into the header and the end of the block. Even when the content is edited, the value of the data BLOCK-SEED area is not changed.
  Value: initial 8-bit random number = INITIALIZATION VECTOR (8 bytes)
  Meaning: Value required to encrypt / decrypt ATRAC3 data
  Function: shows an initial value which is necessary for encrypting and decrypting ATRAC3 data for each block. One block starts from 0. The next block starts from the last encrypted 8-bit value in the last SU. If a block is divided, the last 8 bytes immediately before the start SU are used. Even when the content is edited, the value of the INITIALIZATION VECTOR area is not changed.
  Value: 0 to 0xFFFFFFFFFFFFFFFFF
• - SU-nnn
  Meaning: data of the sound unit
  Function: shows data compressed from 1024 samples.
  The number of bytes of output data depends on the compression mode.
  Even when the content is edited, the value of the area SU-nnn is not changed. For example in SP mode, N = 384 bytes.
  Value: Data value from ATRAC3

, Since N = 384 is written, SU 42 in a block according to Fig. 17. The first two slots (4 bytes) of a block are used as data headers. The areas BLKID-A3D, MCode, CONNUMO and BLOCK SERIAL are written redundantly in the last slot (2 bytes). Thus, M bytes of the remaining area of a block are (16,384-384 × 42-16 × 3 = 208) bytes. As described above, the 8-byte block BLOCK SEED is recorded redundantly.

If the FAT area is destroyed, all blocks of the flash memory are searched. It is determined whether the value of the area ID BLKID at the beginning of each block is TLO, HDO or A3D. As shown in FIGS. 24A to 24C, it is determined in step SP1 whether or not the value of the area ID BLKID at the beginning of the header is BLKID-TO. If the determination result in step SP1 is NO, the flow proceeds to step SP2. In step SP2, the block number is incremented. It is then determined in step SP3 whether or not the last block was searched for.

If the determination result in step SP3 is NO, the flow returns to step SP1.

If the determination result in step SP1 is YES, the flow proceeds to step SP4. In step SP4, it is determined that the searched block is the reproduction management file PBLIST. After that, the flow proceeds to step SP5. In step SP5, the number of total tracks T-TRK in the reproduction management file PBLIST is stored as N in the register. For example, if the memory has 10 ATRAC3 data files (10 music programs), 10 has been stored in the T-TRK.

Thereafter, with respect to the value of the number of total tracks T-TRK on the Blocks TRK-001 to TRK-400 referenced one after the other. In this example, there 10 music programs were recorded referring to blocks TRK-001 to TRK-010 taken. Since a file number FNO in TRK-XXX (where X = 1 to 400) in step SP7 has been recorded, a table will be created, the track number TRK-XXX with the file number always relates FNO, stored in memory. Then in step SP8 N, which in Register has been saved, decremented. A loop of steps SP6, SP7 and SP8 is made repeated until N becomes 0 in step SP9.

If the determination result in step SP9 is YES, the flow advances to Step SP10. In step SP10, the pointer is reset to the header. The search pro zeß is repeated from the head block. After that, the flow proceeds to step SP11. in the Step SP11 determines whether the value of the area ID BLKID of the header is equal BLKID-HDO is or not. If the determination result in step SP11 is NO, runs the flow continues to step SP12. In step SP12, the block number is incremented. in the Step SP13 determines whether the last block has been searched or not.

If the determination result in step SP13 is NO, the flow returns to Return to step SP11. The search process is repeated until the determination result in Step SP11 becomes YES.  

If the determination result in step SP11 is YES, the flow proceeds to step SP14. In step SP14, it is determined whether the block is the attribute header (see Fig. 8) (0x0000 to 0x03FFF as shown in Fig. 8) at the beginning of the ATRAC3 data file.

Then, in step SP15, the file number FNO, the sequence number BLOCK SERIAL of the same ATRAC3 data file and the content accumulation numbers key CONNUMO contained in the attribute header is stored in memory. When 10 ATRAC3 data files are recorded, since there are 10 blocks, of which the value of the area ID BLKID of the header is BLKID-TLO, the search process continued until 10 blocks are searched.

If the determination result in step SP13 is YES, the flow advances to Step SP16. In step SP16, the pointer is reset to the header. The search process is repeated from the head block.

After that, the flow proceeds to step SP17. In step SP17, it is determined whether the value of the ID BLKID area of the header is BLKID-A3D or not.

If the determination result in step SP17 is NO, the flow continues to step SP18. The block number is incremented in step SP18. Then in Step SP18 'determines whether the last block has been searched or not. If the determ If the result of the step SP18 is' NO, the flow returns to step SP17.

If the determination result in step SP17 is YES, the flow advances to Step SP19. In step SP19, it is determined that the block contains ATRAC3 data. After that the flow continues to step SP20. In step SP20, reference is made to the serial number mer BLOCK SERIAL, which is recorded in the ATRAC3 data block, and the content accumulation tion number key CONNUMO stored in the memory.

In the same ATRAC3 data file, the common number is the content Cumulation number key assigned to CONNUMO. In other words, if one ATRAC3 data file consists of 10 blocks, a common number all values of Allocated to CONNUMO areas.

In addition, if ATRAC3 data consists of 10 blocks, the serial numbers 1 to 0 assigned to the values of the BLOCK SERIAL areas of 10 blocks.

According to the values of the CONNUMO and BLOCK SERIAL areas determines whether the current block has the same content and play order of the current block in the same content (i.e. connection sequence).

When 10 ATRAC3 data files (i.e., 10 music programs) have been recorded Since each ATRAC3 data file consists of 10 blocks, there are 100 data blocks.  

With regard to the values of the CONNUMO and BLOCK SERIAL ranges, the Playback order of music programs from 100 data blocks and their connection of the regulations.

If the determination result in step SP19 is YES, all blocks are after Playback management file, the ATRAC3 data file and the attribute data file been searched. Thus, in step SP21, based on the values of the CONNUMO areas, BLOCK SERIAL, FNO and TRK-X in the order of block numbers of the blocks that are in the Memory is saved, the file link state maintained.

If the link state is maintained, the FAT can be in a free Be rich in memory.

Then, the management file according to a second embodiment of the present invention will be described. Fig. 25 shows the file structure according to the second embodiment of the invention. Referring to Fig. 25, a music directory contains a track information management file TRKLIST.MSF (hereinafter referred to as TRKLIST), a backup track information management file TRKLISTB.MSF (hereinafter referred to as TRKLISTB), an additional information file INFLIST.MSF (which is an artist name, an ISRC- Code, a timestamp, still image data, etc. (this file is called INFIST)), an ATRAC3 data file A3Dnnnn.MSF (hereinafter referred to as A3nnnn). The TRKLIST file contains two areas, NAME1 and NAME2. The area NAME1 is an area that contains the memory card name and the program name (for one-byte code corresponding to ASCII / 8859-1 character code). The area NAME2 is an area that contains the memory card name and the program name (for the two-byte code corresponding to MS-JIS / Hankul / Chinese Code).

Fig. 26 shows the relationship between the track information management file TRKLIST, the areas NAME1 and NAME2 and the ATRAC3 data file A3Dnnnn. The file TRKLIST is a file with a fixed length of 64 kBytes (= 16 k × 4). An area of 32 kBytes of the file is used to manage the tracks. The remaining area of 32 bytes is used to accommodate the areas NAME1 and NAME2. Although the areas NAME1 and NAME2 for program names can be provided as a different file as a track information management file, in a system which has a small storage capacity, it is convenient to manage the track information management file and program name files as a whole.

The track information area TRKINF-nnnn and partial information area PRTINF-nnnn of the track information management file TRKLIST are used to manage the data file A3Dnnnn and the additional information INFLIST. Only the ATRAC3 data file A3Dnnnn is encrypted. In Fig. 26, the data length in the horizontal direction is 16 bytes (0 to F). A hexadecimal number in the vertical direction shows the value at the beginning of the current line.

According to the second embodiment, three files, that is, the track management file TRKLIST (including the program title file), the additional information management file INFLIST and the data file A3Dnnnn are used. According to the first embodiment (see FIGS . 7, 8 and 9), two files, ie the playback management file PBLIST for managing the memory card and the data file ATRAC3 for storing programs, are used.

Then, the data structure according to the second embodiment is explained tert. For the sake of simplicity, the data structure according to the second embodiment the description of parts similar to the first embodiment is omitted.

Fig. 27 shows the detailed structure of the track information management file TRKLIST. In the track information management file TRKLIST, a cluster (block) consists of 16 kbytes. The size and data of the TRKLISTB file is the same as that of the TRKLISTB backup file. The first 32 bytes of the track information management file are used as the data header. As with the data header of the playback management file PBLIST, the data header of the TRKLIST file contains a BLKID-TLO / TL1 area (backup file ID) (4 bytes), a T-TRK area (2 bytes) for the number of total tracks, a manufacturer code area MCode (2 bytes ), an area REVISION (4 bytes) for the number of TRKLIST rewriting frequencies, and an area S-YMDhms (4 bytes) (option) for updating the date and time data. The meanings and functions of these data areas are the same as those of the first embodiment. The TRKLIST file also contains the following areas.

• - YMDhms (4 bytes)
  shows the last update date (year, month, day) of the TRKLIST file.
• - N1 (1 byte) (option)
  shows the logical number of the memory card (meter side). If a memory card is used, the value of the area N1 is 0x01.
• - N2 (1 byte) (option)
  shows the logical number of the memory card (denominator side). If a memory card is used, the value of the area N2 is 0x01.
• - MSID (2 bytes) (option)
  shows the ID of a memory card. If multiple memory cards are used, the value of the MISD area of each memory card is the same (TBD). (TBD) (what needs to be defined) shows that this value can be defined in the future).
• - S-TRK (2 bytes)
  shows a special track (TBD)
  Usually the value of the S-TRK range is 0x0000.
• - PASS (2 bytes) (option)
  shows a password (TBD).
• - APP (2 bytes) (option)
  shows the definition of a replication application (TBD) (normally the value of the area APP is 0x0000).
• - INF-S (2 bytes) (option)
  shows the additional information pointer of the entire memory card. If there is no additional information, the value of the area INF-S is 0x00.

The last 16 bytes of the TRKLIST file are for an area BLKID-TLO uses a MCode area and a REVISION area that are the same as the data header. The backup file TRKLISTB contains the data header described above. In this way, the data header contains an area BLKID-TL1, an area MCode and a REVISION area.

The data header is followed by a track information area TRKINF for information relating to each track and a partial information area PRTINF for information relating to each part of the tracks (music programs). Fig. 27 shows the areas that precede the TRKLIST area. The lower part of the TRKLISTB area shows the detailed structure of these areas. In Fig. 27, a hatched area shows an unused area.

The track information area TRKINF-nnn and the partial information area PRTINF-nnn contain areas of an ATRAC3 data file. In other words, the track information area TRKINF-nnn and the partial information area PRTINF-nnn each contain a playback limitation flag area LT (1 byte), a content encryption area CONTENTS KEY (8 bytes), a recorder / player backup block serial number area MG (D) SERIAL (16 bytes), an area XT (2 bytes) (option) for displaying a feature area of a music program, an area INX (2 bytes) (option), an area YMDhms-S (4 bytes) (option), a B Area YMDhms-E (4 bytes) (option), area MT (1 byte) (option), area CT (1 byte) (option), area CC (1 byte) (option), area CN (1 Byte) (option) (these areas YMDhms-S, YMDhms-E, MT, CT, CC and CN are used for reproduction limitation information and for the copy control function), an area A (1 byte) for the part attribute, a part size range PRTSIZE (4th Bytes), a partial key area PRTKEY (8 bytes), and a content cu Simulation number range CONNUM (4 bytes). The meaning, functions and values of these areas are the same as those of the first embodiment. In addition, the track information area TRKINF-nnn and the partial information area PRTINF-nnn each contain the following areas.

• - T0 (1 byte)
  fixed value (T0 = 0x74)
  = INF-nnn (option) (2 bytes)
  shows the additional information pointer (0 to 409) of each track. 00: Music program without additional information
• - FNM-nnn (4 bytes)
  shows the file number (0x0000 to 0xFFFF) of an ATRAC3 data file.
  The number nnnn (in ASCII) of the ATRAC3 data file (A3Dnnnn) is converted to 0xnnnnn.
• - APP_CTL (4 bytes) (option)
  shows an application parameter (TBD) (normally the value of the APP_CTL area is 0x0000).
• - P-nnn (2 bytes)
  shows the number of parts (1 to 2039) that make up a music program. This area corresponds to the T-PART area described above.
• - PR (1 byte)
  fixed value (PR = 0x50).

The areas NAME1 (for the one-byte code) and NAME2 (for the two-byte code) for managing the names are then described. Fig. 28 shows the detailed structure of the area NAME1 (for the one-byte code area). Each of the areas NAME1 and NAME2 (which will be described later) is segmented by 8 bytes. So one slot of them consists of 8 bytes. At 0x8000, ie a data header is arranged from the beginning of each of these areas. A pointer and a name follow the data header. The last slot of area NAME1 contains the same areas as the header.

• - BLKID-NM1 (4 bytes)
  shows the content of a block (fixed value) (NM1 = 0x4E4D2D31)
• - PNM1-nnn (4 bytes) (option)
  shows the pointer to the area NM1 (for one-byte code)
• - PNM1-S
  points the pointer to a name that shows a memory card
  nnn (= 1 to 408) shows the pointer to a music program title

The pointer shows the starting position (2 bytes) of the block, the character code type (2 bytes) and the data size (14 bits).

• - NM1-nnn (option)
  shows the memory card name and music program title for one-byte code (variable length). An end code (0x00) is written at the end of the range.

Fig. 29 shows the detailed data structure of the area NAME2 (for two-byte code). At 0x8000, ie at the beginning of the area, a data header is arranged. A pointer and a name follow the data header. The last slot of area NAME2 contains the same areas as the header.

• - BLKID-NM2 (4 bytes)
  shows the content of a block (fixed value) (NM2 = 0x4E4D2D32).
• - PNM2-nnn (4 bytes) (option)
  shows the pointer to the area NM2 (for two-byte code).

PNM2-S points the pointer to the name that shows the memory card. nnn (= 1 to 408) shows the pointer to a music program title.

The pointer shows the starting position (2 bytes) of the block, the character code type (2 bits) and the data size (14 bits).

• - NM2-nnn (option)
  shows the name of the memory card and the title of the music program for two-byte code (variable). An end code (0x0000) is written at the end of the range.

Fig. 30 shows the data arrangement (for one block) of the ATRAC3 data file A3Dnnnn in the case where 1 SU consists of N bytes. In this file, a slot consists of 8 bytes. Fig. 30 shows the values of the header area (0x0000 to 0x3FF8) of each slot. The first four slots in the file are used for a header. As with the data block preceding the attribute data header of the data file (see FIG. 17) of the first example, a data header is arranged. The data header contains an area BLKID-A3D (4 bytes), a manufacturer code area MCode (2 bytes), an area BLOCK SEED (8 bytes) which is necessary for the encryption process, an area CONNUMO (4 bytes) for the initial content accumulation number, a serial number area BLOCK SERIAL (4 bytes for each track, and an area INITIALIZATION VECTOR (8 bytes), which is necessary for the encryption / decryption process. The second last slot of the block contains redundantly an area BLOCK SEED. The last slot contains areas BLKID- A3D and MCode: As in the first embodiment, the data header is followed by the sound unit data SU-nnnn.

Fig. 31 shows the detailed data structure of the additional information management file INFLIST, which contains additional information. In the second embodiment, the following data header is arranged at the beginning (0x0000) of the INFLIST file. The pointer and the areas follow the data header.

• - BLKID-INF (4 bytes)
  shows the content of the block (fixed value) (INF = 0x494E464F).
• - T-DAT (2 blocks)
  shows the number of total data areas (0 to 409).
• - MCode (2 bytes)
  shows the manufacturer code of the recorder / playback device
• - YMDhms (4 bytes)
  shows the updated recording data and time.
• - INF-nnnn (4 bytes)
  shows the pointer to the DATA area of the additional information (variable length, as two bytes (slot) at the same time). The start position is represented with high-order 16 bits (0000 to FFFF).
• - DataSlot-0000 (0x0800) (data slot)
  shows the offset value from the beginning (as a slot at the same time).

The data size is shown by low order 16 bits (0001 to 7FFF). On The switch-off flag is set to the most significant bit. MSB = 0 (switch on), MSB = 1 (from switch).

The data size shows the total amount of data in the music program.
(The data starts from the beginning of each slot. The non-data area of the slot is padded with 00).

The first INF shows a pointer to the additional information of the entire album (usually INF-409).

Fig. 32 shows the structure of the additional information. An eight-byte data header is arranged at the beginning of an additional information data area. The structure of the additional information is the same as that in the first embodiment (see Fig. 12C). In other words, the additional information contains an area IN (2 bytes) as an ID, an area key code ID (1 byte), an area SIZE (2 bytes) which shows the size of each additional information area, and a manufacturer code area MCode (2 bytes) . The additional information also contains an area SID (1 bytes) as a sub-ID.

According to the second embodiment of the invention, in addition to the file system which is set as the format of the memory card, the track information management file TRKLIST is used for music data. Even if the FAT is destroyed, the file can be recovered. Fig. 33 shows a flow of a file recovery process. In order to recover the file, a computer which works with a file recovery program and which can access the memory card and a storage device (hard disk, RAM or the like) connected to the computer are used. The computer has a function equivalent to the DSP 30 . Then, a file recovery process using the track management file TRKLIST will be described.

All blocks of flash memory whose FAT have been destroyed become TL-0 searched as a value (BLKID) at the head position of each block. In addition, everyone Searched blocks for NM-1 as value (BLKID) at the head position of each block. After that, all blocks according to NM-2 as value (BLKID) at the head position of each Blocks searched. The entire contents of the four blocks (lane information management file) for example, is saved to a hard disk by a recovery computer.

The number of all tracks is based on the data after the fourth byte of the track information management file recorded. The twentieth byte of the track information area TRKINF-001, the value of the CONNUM-001 area of the first music program and the Value of the next area P-001 is acquired. The number of parts is with the value of the area P-001. The values of the areas PRTSIZE of all parts of track 1 of the Be Reichs PRTINF are recorded. The number of total blocks (clusters) n is calculated and captured.

If the lane information management file is acquired, the flow proceeds to step 102 . In step 102 , a voice data file (ATRAC3 data file) is searched. All blocks with the exception of the management file are searched for by the flash memory. Blocks whose header value (BLKID) is A3D are detected.

A block whose value of the CONNUMO area at the 16th byte of A3Dnnnn the same as that of the CONNUM-001 area of the first music program of the Track information management file and its value of the BLOCK SERIAL area, the  starting from the 20th byte, 0 is being searched. After the first block is won a block (cluster) with the same value of the CONNUM area as the first block and where the value of BLOCKSERIAL is incremented by 1 (1 = 0 + 1). If the second block is won, a block with the same value of the CONNUMO area as a second block and of which the value of the BLOCKSERIAL range by 1 (2 = 1 + 1) in is incremented.

By repeating the process, the ATRAC3 data file is searched until n Blocks (clusters) of track 1 are obtained. When all blocks (clusters) are won, who which they saved one after the other on the hard disk.

The same process as for track 1 is carried out for track 2. Different is expressed a block of which the value of the CONNUMO area is equal to that of the loading reichs CONNUM-002 of the first music program of the track information management file and from which the value of the BLOCK SERIAL area starting at the 20th byte Is zero, wanted. After that, the ATRAC3 data is in the same way as for track 1 file searched until the last block (cluster) n 'is determined. If all blocks (clusters) won, they are saved one after the other on the hard disk.

By repeating the process described above for all tracks (the number of tracks: m) all ATRAC3 data are saved on the hard disk by the Recovery computer is controlled.

In step 102 , the memory card whose FAT has been destroyed is reinitialized and then the FAT is restored. A predetermined directory is formed on the memory card. Then the track information management file and the ATRAC3 data file for m tracks are copied from the hard disk to the memory card. This completes the manufacturing process.

Important parameters (in particular whose codes in data heads) are preferably recorded three times as two. If Data are recorded redundantly, the same data can be placed anywhere are drawn as long as they are spaced apart by one page or more.

According to the present invention, when a data file (ATRAC3 file) reproduced from a memory card has reproduction limit information regarding the number of reproduction frequencies, a reproduction operation is determined. If the number of playback frequencies exceeds a predetermined value, the playback operation is prohibited. Then, an area related to the reproduction limit will be described, which corresponds to the track management file TRKLIST, which has been explained with reference to FIGS . 25 to 32. However, such an area can also be applied in accordance with the reproduction limit information contained in the track information TRKINF of the attribute header of the ATRAC3 data file shown in FIG. 9.

Fig. 34 is a block diagram showing the construction of a range feature of the present invention in the digital audio recorder described above. The area according to the present invention includes a DSP 30 , a memory card 40 , a CPU 90 , an operation input area 91 , an SRAM 31 (or 36 ), an audio decoder 12 , an interface 11 and a D / A conversion circuit 18 . The CPU 90 and the operation input section 91 are arranged in an amplifier or the like which is connected to the outside of the digital audio recorder via the bus 32 described above. The CPU 90 and the operation input section 91 allow various commands to be entered and all operations to be controlled. The operation that follows is handled as a software process of the DSP 30 or the CPU 90 .

The operation input area 91 has a normal play key, a stop key, a fast forward key, a pause key, a rewind key, an automatic program selection key, etc. The automatic music program selection operation is one of the file search operations. With the automatic music program selection operation, a music program (track) recorded in the memory card 40 is automatically selected. The operation input section 91 generates an operation signal corresponding to the status of each switch / button. The operation signal is supplied to the CPU 90 . With a control signal corresponding to the operation signal received from the operation input section 91 , the playback operation, etc. is performed.

When the memory card 40 is attached to the playback device and the playback button is pressed, the memory card is authorized (namely, it is determined whether the attached memory card is valid or not). If the authorization process has been successfully carried out, the DSP 30 reads the track information management file TRKLIST.MSF from the flash memory of the memory card 40 into the SRAM 31 or 36 . In addition, the DSP 30 reads a playback limit value group from the track information management file TRKLIST.MSF into the SRAM 31 or 36 .

The DSP 30 simultaneously transmits an audio file read from the memory card 40 to the audio decoder 12 for an SU. The audio decoder 12 decodes the audio file. In this case, an encrypted audio file is decrypted. In Fig. 34, the encryption area is omitted for the sake of simplicity. A decoded output signal is supplied to the D / A conversion circuit 18 via the interface circuit 11 .

The D / A conversion circuit 18 generates a playback audio signal. The playback audio signal is obtained via an output connection 19 . The playback audio signal is supplied to an amplifier (not shown) or the like and reproduced as an audio sound thereof.

The DSP 30 controls the permission / prohibition of the playback operation according to the playback start date, the playback expiration date, the number of track playback frequencies CT, the information determining flag to take the guide, etc. When the playback limitation information to take the guide is detected, the DSP 30 prohibits the playback operation. If the number of playback frequencies is less than the allowable value and the guidance information is not determined, the DSP 30 allows the playback operation.

Conversely, if the DSP 30 has determined that the lead taking information, the DSP 30 generates the control information, and prohibits the playback mode. Even if the DSP 30 has not detected the information taking the lead, if the number of playback frequencies exceeds the playback limit value, the DSP 30 prohibits the playback operation. In order to determine whether the number of playback frequencies exceeds the playback limit value, it is necessary for the DSP 30 to specify a playback operation.

To do this, the DSP 30 converts the value of the SU of the playback data transmitted to the audio decoder 12 into the playback time and assumes that when the playback operation accumulation time of the same track (same music program file) becomes a predetermined value the track has been reproduced once. Since 51 SU is equivalent to one second in a particular mode, for example, in the case that when a track is reproduced for 30 seconds, the track is reproduced once when the reproduced data from 51 × 30 = 1530 SU to the audio decoder 12 are transmitted, assume that the playback operation has been performed once.

Once a track has been reproduced, the playback frequency number CT stored in SRAM 31 or 36 is decremented by 1 (namely CT = CT-1). When the playback command is supplied to the DSP 30 through the CPU 90 , the DSP 30 again calculates a sum value corresponding to the number of reproduction frequencies CT and determines whether or not the current sum value matches the previous sum value. If they match, the DSP 30 determines that the number of playback frequencies CT as the playback limit information has not taken the lead. If these do not match, the DSP 30 determines that the number of playback frequencies CT is likely to have taken the lead. If the number of playback frequencies CT has not taken the lead, the playback operation is performed and the number of playback frequencies CT is decremented by 1. If the memory card 40 is detached from the playback device and then attached to it, or if the power supply of the playback device is switched off before a track is reproduced, the total value is calculated. The total value obtained is stored in a specific area of the non-volatile memory of the encryption circuit 22 in such a way that the total value cannot be accessed from outside. In other words, the DSP 30 only receives the comparison result and does not read the total value itself. According to the present invention, a process for determining whether the reproduction limit information has taken over or not is not always required.

When the user performs the fast forward, rewind, or pause operation with the operation input area 91 while a track is being produced, the counting of the playback time of the track to be reproduced is temporarily stopped. If the user performs the stop operation or the automatic selection operation for the music program while a track is being reproduced, the counting of the playback time of the track to be reproduced is reset.

Then, the playback operation according to the embodiment will be described in detail. Fig. 35 is a flowchart showing a process of managing a partial playback operation for about 30 seconds as a playback operation.

In step S1, it is cyclically determined whether the playback command has been received or not. If the determination result in step S1 is YES, the flow proceeds to step S2. In step S2, it is determined whether the current track (music program) having playback limit information is reproduced with respect to the track information management file TRKLIST stored in the SRAM 31 or 36 (in step S2). If the determination result in step S2 is NO, the flow proceeds to step S9. In step S9, the track file is reproduced normally.

If the determination result in step S2 is YES, the flow proceeds to step S3. In step S3, the previous value of playback frequencies CT is set. In addition, the value m of SU (sound unit), which is transmitted from the DSP 30 to the audio decoder 12 , is set to 0 (namely m = 0). The previous value of the number of reproductions CT is recorded in the track information management file TRKLIST of the SRAM 31 or 36 . The value m of SU is recorded in a predetermined area of the SRAM 31 or 36 . The information taking over the guidance is checked with a sum value in steps S2 and S3.

After that, the flow proceeds to step S4. In step S4, the current audio file is read from the memory card 40 . The audio file is simultaneously transmitted to the audio decoder 12 via the DSP 30 for 1 SU. The audio file is decoded by the audio decoder 12 . The decoded output data is supplied to a D / A conversion circuit 18 via the interface circuit 11 . A reproduced audio signal output from the D / A conversion circuit 18 is obtained through the output terminal 19 . The audio signal obtained is supplied to an amplifier (not shown) and reproduced as an audio sound.

In parallel with the reproduction process, the CPU 90 monitors the operational status of the operational input area 91 . In step S5, it is determined whether or not a key other than the play key has been pressed. If the determination result in step S5 is NO, the flow proceeds to step S11. In step S11, the value m of the number of SUs transmitted is counted. In other words, the value m of the number of transmitted SUs is incremented by 1 (namely m = m + 1).

In step S12, it is determined whether the value m of the number of SUs transmitted one exceeds 1500 (about 30 seconds). If the determination result in step S12 is NO the flow returns to step S4. The next SU is transmitted in step S4. When a button other than the play button is not pressed and the value m is the Number of SUs transmitted does not exceed 1500, the number of SUs transmitted is around 1 incremented.

If the determined result in step S12 is YES, the flow proceeds to step S14. In step S14, assuming that the file has been reproduced once, the number of reproductions CT is decremented by 1 (namely, CT = CT-1) and the value m of the number of transmitted SU (tone units) is reset to 0 (namely m = 0). The decremented value (CT-1) is rewritten in the track information management file of the memory card 40 .

After that, the flow goes to step S15. In step S15, it is determined whether the number of reproductions CT that has been decremented is 0. If the determination result in step S15 is YES (namely CT = 0), the flow proceeds to step S16. In step S16, a process for prohibiting the reproduction operation is performed. In other words, the DSP 30 controls the control information prohibiting the playback operation and supplies the control information to each area of the playback device. In this case, the user is informed of an audio and / or optical information which shows that the playback operation is prohibited because the number of reproductions CT exceeds the set value. If the determination result in step S15 is NO (namely, CT = 0), the process for the number of reproductions is completed. Thus, the playback operation continues.

If the determination result in step 55 is YES, the flow advances to step 6 . In step S6, it is determined whether the fast forward button, the rewind button or the pause button has been pressed for the fast forward playback operation, the rewind operation or the pause operation. If the determination result in step S6 is YES, the flow proceeds to step S7. In step S7, the value m of the number of SUs transmitted is stored. After that, the flow returns to step S5.

If the determination result in step S6 is NO, the flow proceeds to step S8. In step S8, it is determined whether the stop operation or the automatic selection operation has been carried out for the music program. When the automatic selection operation for the music program is performed, the current track that is being reproduced is stopped and the next track is reproduced. Thus, when the automatic selection program for the music program has been selected, a playback request is transferred from the CPU 90 to the DSP 30 . Thus, the flow returns to step S1. In step S1, it is determined that the playback command for the automatic selection operation for the music program has been received. If the determination result in step S8 is NO, the process for the number of reproductions is completed.

In the example described above, when the reproduction operation is performed, the number of reproductions CT is decremented by 1. When the value of the number of reproductions CT becomes 0 (namely, CT = 0), the reproduction operation is prohibited. Alternatively, the number of reproductions CT can be incremented by 1 when the reproduction operation is performed. If the number of reproductions CT becomes equal to the number of permitted reproductions MT (namely MT = CT), the reproduction operation can be prohibited. As another alternative method, the number of allowed reproductions MT can be decremented by 1 when the reproduction operation is performed. In this case, the number of reproductions CT is not used. The values of the number of reproductions CT and the number of permitted reproductions MT are changed in the above-mentioned process. If the memory card 40 is removed from the playback device or the power supply of the playback device is switched off, these values are rewritten in the track information management file TRKLIST of the memory card 40 .

In the embodiment described above, if the value m is the number of transmitted SU exceeds 1500 (about 30 seconds) assumed that the current File was reproduced once. However, it should be noted that the value m is not 1500 is limited. In addition, the playback time can be calculated with a different time unit become.

In the above description, the invention was for a digital audio korder applied. However, the present invention can be applied to other video / audio devices be applied. It is also clear that the present invention is for a medium which uses a flash memory regardless of its memory capacity and shape.

According to the present invention, when the accumulation period of the nor paint playback time of content by the number of playback limitation times exceeds a predetermined value, determines that the content has been reproduced once. The specified number of plays is counted with the number of play time limits compared. The playback operation can be frequent for the number of playback limits be carried out. This allows the content to be limited in terms of playback tion information can be reproduced.

Although the present invention relates to a best mode shows and has been described, it should be understood by those skilled in the art that with respect to Various changes, omissions and additions in form above and detail can be performed without departing from the scope of the present invention leave.

Claims (11)

1. A playback device comprising:
a memory for recording a plurality of files and their reproduction frequency limitation information;
an actuator for selecting a desired file from the plurality of files stored in the memory to reproduce the desired file;
determination means for determining whether or not the reproduction frequency limitation information has been set on the file selected by the actuator;
counting means for counting the playback elapsed time of the file selected by the actuator when the playback frequency limit information is set to the selected file as the result of the determination by the determining means;
a comparison device as to whether the playback elapsed time counted by the counter exceeds a predetermined value; and
an editing means for editing the reproduction frequency limitation information stored in the memory when the playback elapsed time counted by the counter exceeds the predetermined value as a result of the determination by the comparing means. 2. A playback device according to claim 1, wherein the memory consists of a non-volatile storage exists. 3. Playback device according to claim 1 or 2, wherein the memory of a Ge housing of the playback device is detachable. 4. Playback device according to one of claims 1-3, wherein the count of Counter is reset when a playback stop command for the selected one File is output in the state that the playback elapsed time by the count device is counted, does not exceed the predetermined value.   5. A playback device according to claim 4, wherein the playback stop command for the selected file is a playback stop command. 6. The playback device according to claim 4, wherein the playback stop command for the selected file is a file search command. 7. A playback device according to claim 4, wherein the playback stop command for the selected file is a pause command. 8. A playback device according to claim 4, wherein the playback stop command for the selected file is a high speed playback command. 9. Playback device according to one of claims 1-9, wherein the editing process the Playback frequency limit information value decremented by 1. 10. Playback device according to one of claims 1-9, wherein it is prevented the selected file is reproduced when the playback frequency limit is limited formation becomes a limit. 11. A method for reproducing a selected file from a recording medium, comprising the following steps:

• a) causing the selected file recorded on the storage medium to be reproduced;
• b) determining whether or not playback frequency limitation information is set on the selected file;
• c) counting the playback elapsed time of the selected file when the playback frequency limit information is set to the selected file as the determination result in step (b);
• d) comparing whether the counted playback elapsed time exceeds a predetermined value; and
• e) Editing the playback frequency limit information stored on the recording medium when the playback elapsed time counted in step (c) exceeds the predetermined value as the determination result in step (d).