Non-volatile record medium, recording method, and recording apparatus

4033

PERMANENT RECORDING TOOL, RECORDING METHOD AND RECORDING

DEVICE

BACKGROUND OF THE INVENTION

Area of ​​the Cloud

SUMMARY OF THE INVENTION The present invention is a method of recording a lossless (also protected when not receiving) electrical recording corresponding to the data length of a coding process, the data unit of a correction process, and a recordable time and enabling the recording of compressed digital audio data at a variable block segmentation rate. and a recording device.

Description of Related Art

The electrically rewritable non-volatile memory EEPROM (Electrically Erasable Programmable ROM) requires a large area because each bit consists of two transistors. Therefore, the integration of the EEPROM is limited. To solve this problem, a flash memory has been developed which makes it possible to complete a bit with a transistor using a all-bit-erase system. The flash memory is expected to be a continuation of known recording devices such as magnetic disks and optical disks.

A memory card using a flash memory is also known. The card can be freely inserted into and removed from the device. A known CD (Compact Disc: Trademark) or MD (Mini Disc: Trademark)

-> v

A digital voice recording / reproducing device using a memory card can be realized.

A file management system used for a known type of personal computer is called FAT (File Layout Table). In the FAT system, when a specific file is defined, the predetermined parameters are inserted into the file in succession. Thus, the size of a file becomes variable. A file consists of at least one administrative unit (partition, cluster, or the like). The data corresponding to the management unit is written to a table called FAT. In the FAT file system, a file structure can be easily created, regardless of the physical properties of a recording tool. Therefore, the FAT file system can be used for both a magneto-optical disk and a floppy and hard disk. The above mentioned memory card uses the FAT file system.

However, the FAT system concept is never used with respect to a CD with audio data recorded on it. In the MD era, where audio data can be recorded and reproduced, music programs are recorded and corrected using a modified FAT system called Link-P. Therefore the system itself can be controlled by a low power CPU itself. However, using such a system, data cannot be exchanged with a personal computer. Therefore, the MD system was developed as a stand-alone AV system.

Audio data recorded on an MD is sampled with 16 bits at 44.1 kHz. 512 examples of audio data are compressed into 212 bytes. Thus, the subsequent relationship is satisfied.

212x8 / (512x16) = 0.21

- - ··> ·

X -2 ·

In other words, the audio data recorded on an MD is compressed so that the data amount of the compressed audio data is about 1/5 of the amount of the original data. The data value of 212 bytes essentially varies according to the partition structure of a recording medium. In other words, as long as the data value is an integer, one of 211 bytes, 212 bytes, 213 bytes, 214 bytes, and 215 bytes can be selected.

In the recent past, the rights of copyright holders have been adequately protected with respect to the digital recording of music data. In other words, digital music 10 data can be easily copied using the technologies of personal computers. A new generation of encrypted audio data has been proposed to avoid making illegal copies of digital music data.

When the audio data is encrypted according to DES (Data Encryption Standard), the audio data is encrypted after it is compressed. Since an encryption key used in the encryption process is about 64 bits (= 56 bits + 8 bits (CRC) (thus, 8 bytes), splits occur because of the data units of the compression process when the audio data is encrypted with the 64-bit key. For example, in the case of audio data of an MD, since 212/8 = 26.5, when the encryption process is performed 27 times, the data becomes insufficient.

To compensate for insufficient data, the problem of divisions can be solved when four-byte data is added as surrogate data. However, a data loss of about 2% (4/212 = 0.019) occurs. When 215 bytes are selected as the data compression unit, seven-byte surrogate data is required. A data loss of about 3.3% (7/215 = 0.0326) occurs. When a 64 Mbyte memory card is used, 3.3% data loss is equivalent to 2.1 Mbytes of data.

In today's case, such data loss on such an expensive memory card is a critical problem.

Although it is possible to use added data for splits as sub-data with secondary information, this method does not constitute an effective solution since it is difficult to deal with scattered data.

OBJECTIVES AND SUMMARY OF THE INVENTION Therefore, an object of the present invention relates to a recording means, a recording method and a recording device that enable the efficient execution of an encryption process.

A first feature of the present invention is a non-disappearing recording means for recording a digital audio signal compressed at a selectable compression rate in a predetermined range and divided into block segments of a predetermined data length, wherein the predetermined data length, in which the digital audio data is divided into block segments, is long recording time and the length of data that the digital audio signal is encrypted.

A second feature of the present invention is a recording method for recording a digital audio signal compressed to a selectable compression rate in a predetermined range and divided into block segments of a predetermined data length into a non-disappearing recording means, said method comprising the steps of: deciding on the maximum length of the data, taking into account the maximum recording time and the length of data that the digital audio signal is segmenting the encoded digital audio signal into blocks corresponding to the predetermined data length determined,

r.

and storing the segmented digital audio signal to the non-disappearing recording means.

A third feature of the present invention is a recording device for recording a digital audio signal compressed to a selectable compression rate at a predetermined range and divided into block segments of a predetermined data length into a non-lossing recording means, a memory means having a table for determining the predetermined data length of the segmented digital audio signal corresponding to the maximum recording time and the data length to which the compressed digital audio signal is encoded, a selective device for selecting a predetermined compression rate in the predetermined range, the device for determining the predetermined data length of the encoded digital audio signal, which is divided into block segments with reference to the table of memory means corresponding to the predetermined compression ratio selected by the selector device, the block for segmenting the encoded digital audio signal corresponding to the predetermined data length determined by the decoding device. disassembly device, and the block disassembly device and the recorder for recording the block discrete digital audio signal to the non-disappearing recording means.

These and other objects, features and advantages of the present invention will become apparent from the following detailed description of a best embodiment of the invention as shown in the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Sec. 1 is a block diagram illustrating the structure of a digital audio player using a non-volatile memory card according to the present invention;

6'

Sec. Fig. 2 is a block diagram illustrating the internal structure of a DSP 3O according to the present invention;

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

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

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

Sec. 6 is a data structure of memory card 40 according to the present invention; 10 Fig. 7 is a schematic diagram illustrating the hierarchy of the file structure in the memory card 40;

Sec. Fig. 8 is a schematic diagram illustrating the data structure of a replication management file PBLIST.MSF, a subfolder stored in the memory card 40;

Fig. 9 is a schematic diagram illustrating the data structure when an ATRAC3 data file is divided into blocks of predetermined unit length and the assigned files are added thereto;

Sec. Fig. 10A is a schematic diagram illustrating the file structure before the two files are corrected by a merge process;

Sec. Fig. 10B is a schematic diagram illustrating the file structure after the two files have been corrected by a merge process;

Sec. Fig. 10C is a schematic diagram illustrating the file structure after a file is corrected by a segmentation process;

Sec. Fig. 11 is a schematic diagram illustrating the data structure of a replication management file PBLIST;

Sec. Fig. 12A is a schematic diagram illustrating the data structure of a head portion of the replication management file PBLIST;

Sec. Fig. 12B is a schematic diagram illustrating the data structure of a master data portion of the replication management file PBLIST;

Sec. Fig. 12C is a schematic diagram illustrating the data structure of an additional information data section of the replication management file PBLIST;

Sec. Fig. 13 is a table linking by showing the types of additional information data and their code values;

Sec. 14 is a table linking the types of additional information data and their code values;

Sec. 15 is a table linking the types of additional information data and their code values ​​10;

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

Sec. Fig. 16B is a schematic diagram illustrating the data structure if the additional information data is an artist name;

Sec. Fig. 16C is a schematic diagram illustrating the data structure when the additional information data is a copyright code;

Sec. Fig. 16D is a schematic diagram illustrating the data structure when the additional information data is date / time information;

Sec. Fig. 16E is a schematic diagram illustrating the data structure when the additional information data is a replication log;

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

Sec. 18 is a schematic diagram illustrating the data structure of an upper portion of an assigned header containing an ATRAC3 data file;

Sec. Fig. 19 is a schematic diagram showing the data structure of a central portion of an assigned header containing an ATRAC3 data file;

------_r

X “* ·

Sec. 20 is a table that correlates recording modes, recording time, and the like;

Sec. 21 is a table showing copy control states;

Sec. Fig. 22 is a schematic diagram illustrating the data structure of a subdivision of an assigned header containing an ATRAC3 data file;

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

Sec. 24A to 24C are flowcharts illustrating a method of compensating according to the invention if an FTA domain is destroyed;

Sec. Fig. 25 is a schematic diagram illustrating the file structure of the memory card 40 according to a second embodiment of the present invention;

Sec. Fig. 26 is a schematic diagram illustrating the relationship between a path information management file TRKLIST.MSF and an ATRAC3 data file A3Dnnnn.MSA;

Sec. Fig. 27 is a schematic diagram illustrating the detailed data structure of the path information management file TRKLIST.MSF;

Sec. 28 is a schematic diagram illustrating the detailed data structure of NAME1 for managing a name;

Sec. Fig. 29 is a schematic diagram illustrating the detailed data structure of NAME2 for managing a name;

Sec. 30 is a schematic diagram illustrating the detailed data structure of an ATRAC3 data file A3Dnnnn.MSA;

Sec. Fig. 31 is a schematic diagram illustrating the detailed data structure 25 of the INFLIST.MSF representing additional information;

Sec. Fig. 32 is a schematic diagram illustrating the detailed data structure of INFLIST.MSF representing additional information data;

Sec. 33 are flowcharts illustrating a method of compensation according to a second embodiment of the present invention if an FTA area is destroyed; and

Sec. 34 is a table showing the relationship between data bytes and transmission ratios according to the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

DESCRIPTION

An embodiment of the present invention will now be described. Sec. 1 is a block diagram illustrating the structure of a digital voice recorder / player using a memory card according to an embodiment of the present invention. Digital audio recorder / player records and reproduces a digital audio signal using a removable memory card. In fact, the recording / player comprises an amplifier unit, a speaker, a CD player, an MD recorder, a station seeker and the like, and an audio system. It should be noted, however, that the present invention is applicable to other sound recorders. In other words, the present invention is also applicable to a portable recorder / replicator device. In addition, the present invention can be applied to form an upper box that records digital audio data roaming as a satellite data communication, a digital broadcast or the Internet. Moreover, the present invention is applicable to a system that records / reproduces moving image data and still image data other than audio data. According to the embodiment of the present invention, the system can record and reproduce additional information in the form of images and text other than a digital audio signal.

The recording / reproducing device has an audio encoder / decoder IC 10, a security IC 20, a DSP (Digital Audio Processor) 30. Each of these devices consists of a single chip IC.

The recording / reproducing device includes a removable memory card 40. The single chip IC of the memory card 40 has a flash memory (non-vanishing memory), a memory control block and a security block. The security block includes a DES (Data Encryption Standard) encryption circuit. According to the embodiment, the recording / reproduction device may use a microcomputer instead of the DSP 30.

The audio encoder / decoder IC 10 has an audio interface 11 and an encoder / decoder block 12. The encoder / decoder block 12 encodes a digital audio data according to a highly effective encoding method and writes the encoded data to the memory card 40. In addition, the encoder / decoder block 12 decodes the encoded data read from the memory card 40. The highly effective coding method is the ATRAC3 format, a modified format of the ATRAC (Adaptive Conversion Acoustic Coding) format used on the Mini-Disk.

In the ATRAC3 format, audio data sampled at 44.1 kHz and quantified with 16 bits is highly encoded. In the ATRAC3 format, the smallest data unit of processed audio data is an audio unit (SU). 1 SU is data in which 1024 samples (1024 x 16 bits x 2 channels) are compressed into several hundred bytes of data. 1 The duration of SU is around 23 msec. In the highly effective coding method, the data amount of the audio data is compressed into data which is about 10 times smaller than that of the original data. As with the ATRAC 1 format used in the Mini-Disk, the compressed and decompressed audio signal compared to the ATRAC3 format shows less degradation in sound quality.

A line input selector 13 provides the reproduction output signal of an MD to an A / D converter 14, the output signal of a station selector, or an i.

.i * selectively supplies a reproduction output signal of the band. The A / D converter 14 converts the input line signal to a digital audio signal (sampling frequency = 44.1 kHz; number of quantization bits = 16). A digital input selector 16 selectively supplies a digital output signal of an MD, a CD or a CS (Satellite Digital Broadcast) to a digital input receiver 17. The digital input signal is transmitted, for example, via an optical cable. An output signal of the digital input receiver 17 is sent to a sampling rate converter 15. The sampling rate converter 15 converts the digital input signal to a digital audio signal 10 (sampling frequency = 44.1 kHz; number of quantization bits =

16) Converts.

The encoder / decoder block 12 of the audio encoder / decoder IC 10 transmits the encoded data to a DES encoding circuit 22 via an interface 21 of the security IC 20. DES encryption circuit 22 has 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 22 of the recorder / replicator device has a set of master keys and a device-single storage key. The DES encoding circuit 22 also includes a random number generating circuit. The DES encryption circuit 22 may share an authentication process and a session key with a memory card 40 comprising the DES encryption circuit. In addition, DES encryption circuit 22 may re-encrypt data with the storage key of the DES encryption circuit.

The encrypted audio data, which is the output of the DES encryption circuit 22, is sent to a DSP (Digital Audio Processor) 30. The DSP 30 communicates with the memory card 40 via an interface. In this example, the memory card 40 is inserted into an insertion / removal mechanism of the recording / reproduction device.

..β .r (not shown). The DSP 30 writes the encrypted data to the memory card 40's flash memory. The encrypted data is transmitted in series 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 storage / reproduction device with sufficient storage capacity to control the memory card 40.

An electrical connection interface 32 is connected to the DSP 30. The data is transmitted from an external controller (not shown) to the DSP 30 via an electrical connection 33. The external controller controls all operations of the audio 10 system. The external controller provides data, such as a recording instruction or a reproduction instruction, sent to the electrical connection interface 32 and DSP 30, which occurs in accordance with the operation performed by a user through a processing section. In addition, the electrical connection interface to the external controller DSP 30

32 provides additional information such as image information or character information. The electrical connection 33 is a bi-directional communication path. Additional information read from memory card 40 is sent to the external controller via DSP 30, electrical connection interface 32 and electrical connection 33. In fact, the external controller is located, for example, in an amplifier unit of the audio system. In addition, the external controller checks the presentation additional information of a presentation section, the operation status of the recorder and the like. The presentation part is shared by the audio system. The data exchanged through the electrical connection 33 is not encrypted, since it is not copyrighted.

The encoded audio data read from DSP 30 from the memory card 40 is decoded by the security IC 20. Audio encoder / decoder IC 10 corresponds to the AIRAC3 format?

decodes the encoded data. The output data of the audio encoder / decoder 10 is sent 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 sent to a line output terminal 19.

The analog audio signal is sent to an amplifier unit (not shown) via line output terminal 19. The analog audio signal is amplified from a speaker or a head set. The external controller supplies a muted signal to the D / A converter 18. When the muted signal represents a muting operation, the external controller blocks the audio signal from the line output terminal 19.

Sec. 2 is a block diagram illustrating the internal structure of the DSP 30. Sec. 2, the DSP 30 consists of a core 34, a flash memory 35, an SRAM 36, an electrical connection interface 37, a memory card interface 38, and bridges within the electrical connection. The DSP 30 has the same function as a microcomputer. Core 34 is equivalent to a CPU. The flash memory 35 carries a program which causes the DSP 30 to perform predetermined processes. The SRAM 36 and the external SRAM 31 are used as a RAM of the recording / reproduction device.

The DSP 30 controls a writing process for writing encrypted audio data and additional information corresponding to a processing signal such as a recording instruction received via electrical connection interfaces 32 and 37 to the memory card 40, and a reading process for reading therefrom. In other words, the DSP 30, the application software side and the memory card 40, which record / reproduce the audio data and additional information of the audio system, are inserted into the search. The DSP 30 operates when the memory card 40 is accessed. In addition, the DSP 30 operates in accordance with the software, such as a file system.

14DSP 30 manages files stored in memory card 40 with the FAT system used in known personal computers. In addition to the file system, according to the embodiment of the present invention, a management file is used. The management file will be described later. The management file is used to manage the data files stored in the memory card 40. As the first file management information, the management file is used to manage audio data files. On the other hand, as the second file management information, the FAT is used to manage all files, including audio data files and management files stored in the flash memory of the memory card 40. The management file is stored on the memory card 40. The FAT is written to the flash memory along the path folder and the like before the memory card 40 is loaded. The details of the FAT will be described later.

According to the embodiment of the present invention, compressed audio data is encrypted in accordance with the ATRAC3 format to protect the copyright of the data. On the other hand, since it is not necessary to protect the copyright of the management file, it is not encrypted. There are two types of memory cards, the encryption type and the non-encryption type. However, a memory card for use with a recording / reproduction device that records copyright protected data is limited by the type of encryption.

Audio data and image data recorded by users are saved on non-encryption type memory cards.

Sec. Fig. 3 is a block diagram illustrating the internal structure of the memory card 40. The memory card 40 comprises a control block 41 and a flash memory 42 formed as a single chip IC. The DSP 30 of the recorder / player and the memory card 40 are provided with a pair of directional serial interfaces. A dual-line serial interface, a clock line SCK for transmitting a transmitted clock signal with data, a status line SBS for transmitting a signal representing a state, a data line DIO for transmitting data, an interruption line INT, two GND lines, two INT lines and two reserved lines.

The clock line SCK is used to transmit a clock signal simultaneously with the data. The status line SBS is used to transmit a signal representing the status of the memory card 40. Data line DIO is used to enter and extract an instruction and encrypted audio data. The interrupt line INT is used to transmit an interrupt signal which causes the memory card 40 to interrupt the DSP 30 of the recording / playback device. When the memory card 40 is inserted in the recorder, the memory card 40 emits an interrupt signal. However, according to the embodiment of the present invention, since the interrupt signal is transmitted via the data line DIO, the interrupt line INT is established.

A serial / parallel conversion, parallel / serial conversion and interface block (S / P, P / S, I / F block) 43 is located between the control block 41 of the memory card 40 and the DSP 30. interface. The S / P, P / S and IF block 43 converts serial data received from the DSP 30 of the recording / playback device into parallel data and sends the parallel data to control block 41. In addition, S / P, P / S and IF block 43 convert parallel data received from control block 41 into serial data and send serial data to DSP 30. When the S / P, P / S and IF block 43 receives an instruction and data via the data line DIO, the S / P, P / S and IF block 43 separates them into those that normally access the flash memory 42 and are encrypted.

In the format in which the data is transmitted via the data line DIO, after an instruction is transmitted, the data is transmitted. S / P, P / S and IF block 43 detect the code of an instruction and the instruction and data normally

16 ----- determines whether it is from accessors or encoded. Depending on the determined result, S / P, P / S and IF block 43 normally stores an instruction accessing an instruction register 44 and normally stores data accessing a page buffer 45 and a writing register 46. In connection with the writing register 46, the memory card 40 includes circuit 47 encoding an error correction code. The circuit 47 that encodes the error correction code generates a viscous code which is an error correction code for the data temporarily stored in page buffer 45.

Instruction register 44, page buffer 45, writing register 46, and circuit 47 encoding error 10 correction code are provided to a flash memory interface and sequencer 51 (hereinafter referred to as memory I / F and sequencer). The memory IF and the interleaver 51 is an interface located between the control block 41 and the flash memory 42 and controls the data exchange between them. The data is written to the flash memory via memory IF and serializer 51.

Audio data compressed to the ATRAC3 format and written to the flash memory (hereinafter referred to as ATRAC3 data) is encrypted by the security IC 20 of the recording / playback device and the security block 52 of the memory card 40 to protect the copyright of the ATRAC3 data. The security block 52 consists of 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 a set of authentication keys and a single storage key for each memory card.

The non-lost memory 55 stores a key required to encrypt the data. The key stored in the non-lost memory 55 cannot be analyzed. According to the embodiment, for example, a storage key is stored in non-lost memory 55. The security block 52 also includes a random number generation circuit. The security block 52 recognizes an applicable recording / playback device and shares a session key with it. In addition, the security block 52 re-encrypts the content with the storage key via the DSE encryption circuit 54.

For example, when the memory card 40 is inserted in the recording / playback device, they mutually recognize each other. The security IC 20 of the recording / playback device and the security block 52 of the memory card 4O mutually confirm each other's authenticity. When the recording / playback device approves the inserted memory card 40 T as a viable memory card, and when the memory card 40 confirms the recording / playback device as a viable recording / playback device, they mutually confirm each other's authenticity. Once the mutual authentication process has been successfully performed, the recording / playback device and the memory card 40 generate the corresponding session keys and share them with each other. Each time the recording / playback device and the memory card 40 are authenticated, they form the corresponding session keys.

When the content is written to the memory card 40, the recording device encrypts a content key with a session key and sends the encrypted data to the memory card 40. The memory card 40 decrypts the session key with the content key, re-encrypts the content key with a storage key, and sends the content key to the recording / playback device. The storage key is a single key for each memory card 40. When the recording / receiving device receives the encrypted content key, the recording / playback device performs a formatting process for the encrypted content key and writes the encrypted content key and encrypted contents to the memory card 40.

1 <S.

In the above section, the writing process for the memory card 40 is described. In the following section, the reading process for the memory card 40 will be described. The data read from the flash memory 42 is sent to the page buffer 45, the reading register 48 and the error correction circuit 49 via the memory IF and the serializer 51. Error correction circuit 49 corrects the error of the data stored in page buffer 45. The corrected output data of page buffer 45 and the output data of reading register 48 are sent to S / P, P / S and IF block 43. The output data of S / P, P / S and IF block 43 is sent to the DSP 30 of the 10 recording / playback device via the serial interface described above.

When the data is read from the memory card 40, the content key encrypted with the storage key and the content encrypted with the block key are read from the flash memory 42. The security block 52 decrypts the storage key and the content key. The security block 52 re-encrypts the decrypted content key with the session key and transmits the encrypted content key again to the recording / playback device. The recording / decryption device decrypts the content key with the received session key and generates a block key with the decrypted content key. The recording / playback device consecutively decrypts the encrypted ATRAC3 data.

A config. The ROM 50 is a memory that stores the partition information of the memory card 40, the different assigned information types, and the like. The memory card 40 further comprises a wipe protection switch 60 T. When the key 60 is in the erasure protection position, the memory card

Even if an instruction which causes the 40 to erase the data stored in the flash memory 42, the memory card 40 is blocked for erasing the data stored in the flash memory 42. An OSC check. 61, memory card 4Ö's process

It is an oscillator that generates a clock signal that is a reference to the timing of the WORK ------.

Sec. Fig. 4 is a schematic diagram illustrating the hierarchy of processes of the file system of the computer system using a memory card as a storage means. In the hierarchy, the highest hierarchy level is an implementation process level. The application process level is followed by a file management process level, a logical address management level, a physical address management level, and a flash memory access level. In the hierarchy structure mentioned above, the file management process 10 level is the FAT file system. The physical addresses are assigned to individual blocks of flash memory. The relationship between the blocks of flash memory and its physical addresses does not change. Logic addresses are logic-managed addresses at the file management process level.

Sec. Fig. 5 is a schematic diagram illustrating the physical structure of the data manipulated in the flash memory 42 of the memory card 40. In memory 42, a data unit (referred to as part) is divided into a predetermined number of blocks (fixed length). A block is divided into a predetermined number of pages (fixed length). The data in the flash memory is erased into each block at a time point. The data is written to or read from flash memory 42 as a page at a time point. The size of each block is the same. Similarly, the size of each page is the same. A block of pages consists of pages from 0 to page m. For example, a block has a storage capacity of, for example, 8 KB (kilobytes) or 16 KB. One page, 512

It has a storage capacity of B (bytes). When a block has a storage capacity of 8 KB, the total storage capacity of flash memory 42 is 4 MB (512 blocks) or 8 MB (1024 blocks). When a block has a storage capacity of 16 KB, the total storage capacity of the flash memory 42 is 16 MB (1024 blocks), 32 MB (2048 blocks), or 64 MB (4096 blocks).

A page consists of a 512-byte data section and a 16-byte redundancy section. The first three bytes of the redundancy section form the sections in which the overprint is rewritten when the data is updated. The first three bytes successively contain a block status field, a page status field, and an update status field. The remaining 13 bytes of the redundancy section include fixed data that varies with the content of the data section. 13 the byte includes a management streamer area (1 byte), a logical address area (2 bytes), a format reserve area (5 bytes), a distribution information ECC area (2 bytes), and a data ECC area (3 bytes). The distribution information includes redundant data for the error correction process in the ECC area, management streamer area, logic address area and format reserve area. The data ECC field covers redundancy data for the error correction process of 512-byte data.

The management pennant field is a system pennant (1: user block, 0: boot block), a conversion table pennant (1: invalid, 0: table block), an anti-copy pennant (1: OK, 0: NG), and an access It includes the permission flag (1: free, 0: protection arrow).

The first two blocks - blocks 0 and 1 are the boot blocks. Block 1 is a back-up of block 0. Boot blocks are valid upper blocks on the memory card. When the memory card is inserted into the recording / playback device, the boot blocks are accessed first. The remaining blocks are user blocks. The 0 page of the boot block includes a header field, a system input field, and a boot and assignment information field. 1 page of the boot block contains a forbidden block data field. The 2 pages of the boot block contain a CIS (Card Information Structure) / IDI (Driver Information Recognition) field.

The header area of ​​the plot block contains a plot block ID and the number of effective inputs. The system inputs are the starting position of the forbidden block data, its data size, its data type, the data start position of the CIS / IDI field, its data size and its data type. Drawing and assigned information, memory card type (read type only, rewritable type or hybrid type), block size, number of blocks, total number of blocks, secure / unsafe type, card manufacturing data (date of manufacture), and the like covers.

The flash memory is subject to a limitation in the number of rewritings due to the deterioration of the insulation film, so it is necessary to prevent intensive access to the same storage area (block). Therefore, when the data at a particular logical address is rewritten, the updated data of a particular block is written to an unused block instead of the original block. Thus, after the data is updated, the relationship between the logical address and the physical address changes. This process is called the exchange process. As a result, intensive access to the same block is prevented. Thus, the service life of the flash memory can be extended.

The logical address cooperates with the data written to the block. Even if the original data block is different from the updated data block, the address on the FAT does not change. Access to the same data is therefore possible. However, since the exchange process is performed, a conversion table is required (which is referred to as a logical-physical address conversion table) that associates logical addresses with physical addresses. Regarding the logic-to-physical address conversion table, a physical address corresponding to a logical address designed on the FAT is obtained. Thus, it is possible to access a block designed with a physical address.

·· γ- 2.γ --------- DSP 30 stores the logic-physical address conversion table in SRAM. When the storage capacity of the RAM is small, the logical address conversion table can be stored in flash memory. The logical address conversion table associates logical addresses (2 bytes) sorted from small to large with physical addresses (2 bytes). Since the maximum storage capacity of the flash memory is 128 MB (8192 blocks), 8192 addresses can be assigned with two bytes. The logic-physical address conversion table is managed for each part. Thus, the size of the logic-physical address conversion table is proportional to the storage i0 capacity of the flash memory. When the flash memory has a storage capacity of 8 MB (two parts), two pages are used as the logical-physical address conversion table for each of the parts. When the conversion table is stored in flash memory, a predetermined bit of the management streamer area in the redundancy portion on each page indicates whether the block in question is a block containing the logical-physical address conversion table.

The memory card described above can be used with the FAT file system of a personal computer system as well as with the disk shaped recording means. The flash memory has an IPL area, a FAT area, and a path folder area (not shown in Fig. 5). The IPL field initially contains the address of a program to be stored in the memory of the recording / playback device. In addition, the IPL field contains different types of memory information. The FAT field contains information about blocks (clusters). FAT identifies unused blocks, the next block number, bad blocks, and the last block number. The path folder field contains folder entries, which are a file assignment, a current date [day, month, year], file size, and the like.

-23 ----------- Now, Fig. 6, a management method using a FAT table will be described.

Sec. Fig. 6 is a schematic diagram illustrating a memory map. The upper area of ​​the memory map is a partition table. This partition table is followed by a block area, a boot area, a FAT area, a FAT back-up area, a path folder area, a subfolder area, and a data area. On the memory map, the logical addresses are converted into physical addresses according to the logical-physical address conversion table.

The boot partition, FAT space, FAT back-up space, path folder space, subfolder space, and data space are referred to as FAT sharing space.

The allocation table section covers the start addresses and the end addresses of the FAT share space.

The FAT used for a known floppy disk does not have such a partition 15 table. Because the first track has only one allocation table, there is an empty space. The boot portion includes the size of the FAT structure (12-bit FAT or 16-bit FAT), the cluster size, and the size of each field. FAT is used to manage the position of a file saved in the data field. FAT Copy Space One

FAT is the back-up area. The path folder field contains the file names, its starting cluster addresses, and its different assignments. The path folder space uses 32 bytes per file.

The subfolder field is accessed by assigning a folder as a folder. Sec. In the embodiment shown in FIG.

It covers four files named PBLIST.MSF, CAT.MSF, DOG.MSF and MAN.MFA. The subfolder area is used to manage file names and record positions on FAT. In other words, the location of the CAT.MSF file name is assigned to address “10 üzerinde on the FAT. DOG.MSF file

-₂^!4 The location of the name is assigned to the address “10 üzerinde on the FAT. A field after Cluster 2 is used as a data field. In this embodiment, audio data compressed according to the ATRAC3 format is recorded. The upper part of the MAN.MSA file name is assigned to the address “110 üzerinde on the FAT. According to the embodiment of the present invention, the audio data having the CAT.MSF file name is recorded in clusters 5 to 8. As the first half of the file with the file name DOG.MSF, DOG-1 audio data was recorded in clusters 10 to 12. As the second half of the file with the DOG.MSF file name, DOG-2 audio data was recorded in clusters 100 and 101. The audio data with the file name MAN.MSF is recorded in clusters 110 and III.

In the embodiment of the present invention, an example is described in which a single file is divided into two sections and scattered recording. In the edit, a field within the data field is a recordable field “Blank”. A field after Cluster 200 is used to manage file names. The CAT.MSF file is saved to cluster 200. The DOG.MSF file is saved to Cluster 201. The MAN.MSF file is saved in cluster 202. When the positions of the files change, the field after the set 200 is rearranged. When the memory card is inserted, the start and end of the FAT allocation area is recorded with reference to the upper allocation table section. After the boot partition is replicated, the path folder area and the subfolder area are replicated. The location of the replication management information PBLIST.MSF in the subfolder area is determined. This gives the address of the end of the location of the PBLIST.MSF file. In the embodiment, since address “200 küme is registered to the end of the PBLIST.MSF file, cluster 200 is referenced.

The field after Cluster 200 is used to manage the replication order of files. CAT.MS A file first in the edit

I program. The DOG.MSA file is the second program. The MAN.MSA file is the third program. When the field following the field after cluster 200 is referenced, the locations of the CAT.MSA, DOG.MSA, and MAN.MSA files are referenced. Sec. 6, the end of the CAT.MSA file location is assigned to address “5.. The end of the location of the DOG.MSA file is assigned to address “10.. The end of the location of the MAN.MSA file is assigned to address “110.. When searching for an input address with address “5 FAT on the FAT, the cluster address“ 6 ”is obtained. When searching for an input address with address “6 FAT on the FAT, the cluster address“ 7 ”is obtained. When an input address is searched for the address “8 FAT on the FAT 10, the code“ FFF temsil representing the end is obtained. Thus, the CAT.MSA file uses clusters 5, 6, 7, and 8. Regarding clusters 5, 6, 7 and 8 in the data field, an ATRAC3 data field with the CAT.MSA filename can be accessed.

Next, a method for searching for a dispersed recorded DOG.MSF file will be described. The end of the location of the DOG.MSF file is assigned to address “10.. When searching for an input address with address “10 FAT on the FAT, the cluster address“ 11 ”is obtained. When an entry address is searched with the address ”11 FAT on the FAT, the cluster address“ 12 ”is obtained. When an adresi 12 ”address is searched on the FAT, the cluster address is“ 101 ”. When an input address is searched with the address ”101 üzerinde on the FAT, the code“ FFF temsil representing the end is obtained. Thus, the DOG.MSF file uses clusters 10, 11, 12, 100, and 101. Regarding clusters 10, 11 and 12 in the data field, the first section of an ATRAC3 data with the file name DOG.MSF can be accessed. Regarding clusters 100 and 101 in the data area, the second part of an ATRAC3 data with the file name DOG.MSF can be accessed. In addition, when searching for an ile 110 ”address on FAT,

26-cluster address “101 ir is obtained. When an adresi 111 ”is searched for giriş 101 FAT on FAT, an“ FFF ”code representing the end is obtained. It is therefore clear that the MAN.MSA file uses clusters 110 and III. As described above, flash memory scattered data files can be connected and replicated in series.

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 portions of the music files. The management file is stored in a user block 10 of the flash memory 42 of the memory card 40. Thus, as will be described later, the memory card 40'm

Even if the FAT does not exist, a file can be recovered.

The management file is created by DSP 30. When the recorder is operated, the DSP 30 determines whether the memory card 4O is inserted in the recorder. When the memory card is inserted,

DSP 30 confirms memory card 40T. When the DSP 30 memory card 40T has been successfully verified, the DSP 30 reads the boot block of the flash memory 42. The DSP 30 then reads the physical-logical address conversion table and stores the read data in the SRAM. The FAT and path folder are written to the flash memory of the memory card 40 before the memory card 40 is loaded. When the data is saved to the memory card 40, the management file is created.

In other words, a registration instruction given by the remote controller of the user or the like is sent from the external controller to the DSP 30 via the electrical connection and electrical connection interface 32. The encoder / decoder IC 10 compresses the received audio data and sends the resulting ATRAC3 data to the security IC 20. Security IC 20 encrypts ATRAC3 data. The encrypted ATRAC3 data is stored in the flash memory 42 of the memory card 40. After that, the FAT and the management file are updated. Whenever a file is updated (in fact, when the recording process of audio data is complete), the FAT and management file stored in SRAMs 31 and 36 are rewritten. When the memory card 40 is removed or the recording / playback device is turned off, the management file obtained from the FAT and finally SRAMs and 36 is saved to the flash memory 42. Alternatively, when the recording process of the audio data is complete, the FAT and management file written to the flash memory 42 can be rewritten. When the audio data is corrected, the contents of the management file can be updated.

According to the embodiment, additional information in the data structure is contained in the management file. The additional information is updated and stored in the flash memory 42. In the further data structure of the management file, an additional information management file is created next to the trace management file. Further information is sent from the external controller to the DSP 30 via the electrical connection and the electrical connection interface. The additional information is stored in the flash memory 42 of the memory card 40. Additional information is not encrypted because security is not sent to IC 20. When the memory card 40 is removed from the recording / playback device, or when this device is switched off, additional information is written from the SRAM of the DSP 30 to the flash memory 42.

Sec. Fig. 7 is a schematic diagram illustrating the file structure of the memory card 40. The file structure has a still image folder, a moving image folder, an audio folder, a control folder, and a music (HIFI) folder. Music programs are saved and reproduced according to the arrangement. Then the music folder will be described. The music folder contains two types of files. The first type is a replication management file BLIST.MSF (hereinafter referred to as PBLIST). The other type is an ATRAC3 data file A3Dnnnn.MSA that stores encrypted music data. The music folder can store up to 400 '......... 2K -------- ATRAC3 data file (ie, 400 music programs). ATRAC3 data files are saved in the replication management file and generated by the recording / playback device.

Sec. Fig. 8 is a schematic diagram illustrating the structure of the replication management file. Sec. Fig. 9 is a schematic diagram illustrating the file structure of an ATRAC3 data file. The replication management file is a fixed-length file of 16 KB. An ATRAC3 data file consists of an assigned title and an encrypted music data for each music program. The assigned data has a fixed length of 16 KB. The structure of the assigned header is similar to that of the replication management file.

Sec. The replication management file shown in FIG. 8 is a header, a memory card called NMIS (for a byte code), a memory card called NM-2S (for two byte code), a program replication serial table TRKTBL, and an additional information INF-S memory. card. The assigned title at the beginning of the data file (Fig. 9, a program called NM1 (for a byte code), a program called NM2 (for a two-byte code), TRKINF (such as trace key information), section information PRTINF, and trace additional information INF occurs from. The header contains the number information of the total sections, the assigned name, the size of the additional information, and so on.

The assigned information is followed by ATRAC3 music data. Music data is divided into blocks every 16 KB. Each block starts with a title. The header contains an initial value to decrypt the encrypted data. Only the music data of an ATRAC3 data file is encrypted. Therefore, other data such as the replication management file, title, and so on are not encrypted.

Referring now to FIG. Referring to 10A to 10C, the relationship between music programs and ATRAC3 data files will be described. A track is equivalent to a music program. In addition, a music program consists of an ATRAC3 data (see Fig. 9). The ATRAC3 data file is audio data compressed according to the ATRAC3 format. The ATRAC3 data file is stored in the memory card 40 as a cluster at a time point. A cluster has a capacity of 16 KB. A cluster does not contain a bunch of files. The smallest data erasure unit of flash memory 42 is a block. In case memory card 40 is for music data, a block is synonymous with a set. In addition, a cluster is equivalent to a partition.

A music program basically consists of a piece. However, when a music program is corrected, a music program can consist of many parts. A track is a unit of data recorded consecutively. Normally, a trace consists of a piece. The connection of the tracks of a music program is managed by PRTINF with the track information in the assigned title of each music program. In other words, the part size is represented by the part size PRTSIZE (4 bytes) of the part information PRTINF. Part size The first two bytes of PRTSIZE represent the total number of sets of that part. The next two bytes represent the start audio unit (SU) and the last audio unit (SU) of the start and end sets, respectively. Thereafter, an audio unit will be abbreviated as SU. With such a track notation, the movement of the music data can be suppressed when the music data is corrected. When the music data is corrected for each block, the correction unit of a block is much larger than the correction unit of a SU, although its movement can be suppressed.

- 30,—

SU is the smallest unit of a part. In addition, when audio data is compressed according to the ATRAC3 format, SU is the smallest data unit. 1 SU is compressed audio data of 1024 sample data (1024 x 16 bit x 2 channels) at 44.1 kHz, about 10 times smaller than that of the original data. 1 The duration of SU is about 23 seconds. Normally a piece consists of many thousand SUs. When a cluster 42 consists of SU, a cluster makes it possible to produce a one second sound. The number of parts that make up a track varies with the size of the additional information. Since the number of parts, title, 10 program name, additional information, and the like are obtained by subtracting from a block, the maximum number of parts (645 parts) can be used when no additional information is available.

Sec. Fig. 10A is a schematic diagram illustrating the file structure when two music programs are recorded consecutively on a CD or the like. The first program (file 1) consists of, for example, five clusters. Since a batch cannot contain two files of the first program and the second program, file 2 starts from the beginning of the next batch. Thus, the end of part 1 corresponding to file 1 is in the middle of a cluster and the remaining area of ​​the cluster does not contain data. Similarly, the second music program (file 2) consists of a track. In the case of file 1, the part size is 5. The first set starts at SU 0. The last set ends in 4th SU.

There are four types of correction processes, which are a division process, a gathering process, a deletion process, and a movement process.

The division process is performed by dividing a trail into two parts. When the division process is performed, the total number of traces increases by one. In the split process, one file on the file system is divided into two files. Therefore, in this case, the replication management file and the FAT are updated. The recombination process is carried out to collect two tracks in a single track. When the recombination process is performed, the total number of traces is reduced by one. During the consolidation process, two files on the file system are combined into a single file. Therefore, when the assembling process is performed, the replication management file and the FAT are updated. The deletion process is performed to delete a trace. The number of tracks decreases one by one after the deleted track. The movement process is performed to change the track series. Therefore, when the deletion process or transaction process is performed, the IO replication management file and FAT are updated.

Sec. 10B, FIG. 10A is a schematic diagram showing the result of combining two programs (file 1 and file 2) shown in 10A. As a result of the assembling process, the assembled file consists of two parts. Sec. Fig. 10C is a schematic diagram illustrating the division process of a program (file 1) divided from the center of cluster 2. With the division process, file 1 consists of the initial portion of clusters 0, 1, and cluster 2. File 2 consists of the last part of cluster 2 and clusters 3 and 4.

As described above, according to the embodiment of the present invention, since the part notation is defined as a combined result (see Fig. 10B), the starting position of part 1, the last position of part 1 and the last part of part 2 can be defined by SU. Therefore, it is not necessary to move the music data of part 2 to collect the area bound to the pooled result. In addition, as a divided result (see FIG. 10C), you do not need to move the data at the beginning of file 2 and collect the space.

Sec. Fig. 11 is a schematic diagram illustrating the detailed data structure of the replication management file PBLIST. Sec. 12A and 12B, replication —— 32 ---------, ------- show a header section and the rest of the management file PBLIST. The replication management file is a cluster (one block = 16 KB). Sec. The header shown in 12A is 32 bytes in size. Sec. The remainder of the replication management file PBLIST shown in 12B is a field named NM15 S (256 bytes) (for memory card), a field named NM2-S (512 bytes), a content key field, a MAC field, an S- The YMDhms field includes a replication serial management table TRKTBL field (800 bytes), a memory card additional information field INF-S (14720 bytes), and a header information redundancy field. The initial positions of these fields are defined in the IO replication management file.

Sec. The first 32 bytes of (0x0000) to (0x0010) shown in 12A are used as headers. In the file, 16-byte fields are referred to as places. Sec. 12A, the cap is positioned in the first and second locations. The title contains the following fields. A field called “reserved” is an undefined field. Normally, in a reserved field, nothing (0x00) is written. However, if any data is written to a reserved field, the data written to the reserved section is denied. Reserved fields are available in a future version. In addition, data is prevented from being written to a reserved field. When a probability field is not used, it is treated as a reserved field.

BLKID-TLO (4 bytes)

Meaning: BLOCKED FILE ID

Function: Defines the top part of the replication management file.

Value: Constant value = “TL = 0” (for example, 0x544C2D30) = MCode (2 bytes)

Meaning: MAKER CODE (MANUFACTURER CODE)

33 ------------ Function: Identifies the manufacturer and model of the recording / playback device.

Value: High-rank 10 bit (Manufacturer code); Low-sequence 6 bit (model code).

= REVISION (4 bytes)

Function: increments when the replication management file is rewritten.

Value: starts at 0 and increases by 1.

= S-YMDhms (4 bytes) (Probability) io Meaning: Year, month, day, hour, minute and second recorded by the recording / playback device with a reliable clock.

Function: Defines the last recorded date and time. Value: bit 25 to 31: Year 0 to 99 (1980 to 2079) bit 21 to 24: Month 0 to 12 is bit 16 to 20: Day 0 to 31 bit 11 to 15: Hour 0 to 23 bit 05 to 10: Minute 0 to 59 bits 00 to 04: Seconds 0 to 29 (two bit range) = SY1C + L (2 bytes)

Meaning: Name assignment (one byte code) of the memory card written in the NM1-S field.

Function: Represents the character code and language code as a byte code.

Value: Character code (C): High-order one byte 25 00: No character code, even number

01: ASCII (American Standard Code for Information Exchange)

02: ASCII + KANA

03: Modified 8859-1

81: MS-JIS

82: KSC 5601-1989

83: GB (Great Britain) 2312-80

90: S-JIS (Japanese Industrial Standards) (for Sound)

Language code (L): A low-order byte defines the language based on EBU Tech 3258, standard.

<td> 00:</td><td>Undetermined</td>

<td> 08:</td><td>German</td>

<td> 09:</td><td>The English</td>

<td>0:</td><td>Spanish</td>

<td>UGH:</td><td>French</td>

<td> 15:</td><td>Italian</td>

<td>ID:</td><td>Dutch</td>

<td> 65:</td><td>Korean language</td>

<td> 69:</td><td>Japanese</td>

<td> 75:</td><td>Chinese</td>

When the data is not saved, this field is all 0.

= SN2C + L (2 bytes)

Meaning: Memory card name assignment in the NM2-S field Function: One byte represents the character code and language code as code.

Value: Same as SN1C + L = SINFSIZE (2 bytes)

Meaning: Total size of additional information of the memory card in the INF-S field

Function: Represents the data size as a multiple of 16 bytes. When the data is not saved, this field is all O.

Value: Size: 0x0001 to 0x39C (924) = T-TRK (2 bytes)

Meaning: TOTAL NUMBER OF TRACKS

Function: Represents the total number of tracks.

Value: 1 to 0x0190 (Up to 400 tracks)

When the data is saved, this field is all 0.

= VerNo (2 bytes) io Meaning: Format version number

Function: Represents the actual version number (high order one byte) and the minor version number (low order one byte).

Value: 0x0100 (Ver 1.0)

0x0203 (ver 2.3)

Next, the fields preceding the header (see Fig. 13B) will be described.

= NM1-S

Meaning: Name of memory card (as a byte code)

Function: Represents the name of the memory card as a byte code (up to 256). A final code (0x00) is written at the end of this field. The dimension was calculated from the last code. When data is not saved, zero (0x00) is recorded for at least one byte from the beginning of this field (0x0020).

Value: Different character code = NM2-S

Meaning: Name of memory card (two bytes as code)

Function: Represents the name of the memory card as two-byte code (up to 512). A final code (0x00) is written at the end of this field. The dimension was calculated from the last code. When data is not saved, zero (0x00) is recorded for at least two bytes from the beginning of this field (0x0120).

Value: Different character code

- CONTENT SWITCH

Meaning: Value for the music program. Protected and stored with MG (M). Same as CONTENT SWITCH.

Function: Used as a key to calculate the MAC of S-YMDhms.

Value: 0 to OxFFFFFFFFFFFFFFFF = MAC

Meaning: Future copyright information check value

Function: Represents the value generated by S-YMDhms and CONTENT SWITCH.

Value: 0 to OxFFFFFFFFFFFFFFFF = TRK-nnn

Meaning: SQN (serial) number of the replicated ATRAC3 data file.

Function: Represents the FNO of TRKINF.

Value: 1 to 400 (0x190)

When there is no trace, this field is all.

= INF-S

Meaning: Additional information of the memory card (eg information on photos, songs, manuals, etc.)

Function: Represents additional information of variable length with a header. A set of additional information types is available. Each type of additional information has an ID and a data size. Each additional information area containing a header consists of at least 16 bytes and a multiple of 4 bytes. See the following section for details.

Value: See Veri Data Structure of Additional Information ”.

= S-YMDhms (4 bytes) (Option)

Meaning: year, month, day, hour, minute and second recorded by the recording / playback device with a reliable clock.

Function: Defines the last recorded date and time. In this case of EMD, this field is mandatory.

Value: bit 25 to 31: Year 0 to 99 (1980 to 2079) bit 21 to 24: Month 0 to 12 bit 16 to 24: Day 0 to 31 bit 11 to 15: Hour 0 to 23 bit 05 to 10: Minute 0 to 59 bits 00 to 04: Seconds 0 to 29 (two second interval)

As the last set of replication management file, the same BLKED-TL0, MCode, and REVISION are written as in the header.

When data is being written to a memory card, the card may be accidentally removed or the recorder may turn off. A malfunction should be detected when such improper operation is performed. As described above, the REVISION area is located at the beginning and end of each block. Whenever the data is rewritten, the value of the REVISION field increases. If an error termination occurs in the middle of a block, the value of the REVISION field at the beginning of the block does not match the value of the REVISION field at the end of the block. Therefore, such an error termination can be detected. Because there are two REVISION fields, abnormal termination can be detected with a high probability. When an abnormal termination is detected, an alarm occurs, such as an error message.

-38In addition, since the fixed-value BLKID-TLO is written to the beginning of a block (16 KB), when the FAT is destroyed, the constant value is used as a reference to compensate for the data. In other words, with respect to the constant value, the file type can be specified. Since the fixed value is written as an extra to the BLKID-TLO header and the last part of each block, reliability can be guaranteed. Alternatively, the same replication management file can be saved as redundancy.

The data amount of an ATRAC3 data file is much larger than that of the trace information management file. In addition, a block number BLOCK SERIAL is added to the ATRAC3 data file, as will be described later. However, since most ATRAC3 files are stored on the memory card, both CONNUMO and BLOCK SERIAL are used to prevent them from becoming redundant. Otherwise, when the FAT is destroyed, the file becomes difficult to compensate. In other words, an ATRAC3 data file can consist of a set of many scattered blocks. CONNUMO is used to specify the blocks of the same file. Additionally, BLOCK SERIAL is used to determine the series of blocks in the ATRAC3 data file.

Similarly, the generator code (Mcode) is saved as an extra to the beginning and end of each block to identify the manufacturer and model in the event that a file is improperly recorded and FAT is not destroyed.

Sec. Fig. 12C is a schematic diagram illustrating the structure of the additional information data. Additional information consists of the following header and variable length data. The title contains the following fields.

= INF

Meaning: FIELD ID (FIELD ID)

---. . V? ------------ Function: Represents the start of additional information (constant value).

Value: 0x69

-ID

Meaning: Additional information key code

Function: Represents the category of additional information.

Value: 0 to 0xFF

-SIZE

Meaning: Size of individual additional information

Function: Represents the size of each type of additional information. Although the data size is not limited, it must be at least 16 bytes and a multiple of 4 bytes. The rest of the data must be filled with zero (0x00).

Value: 16 to 14784 (0x39C0) = MCode

Meaning: MAKER CODE (MANUFACTURER CODE)

Function: Determines the manufacturer and model of the recording / playback device.

Value: High rank 10 bits (manufacturer code), low rank 10 bits (machine code)

-C + L

Meaning: Assigning characters starting from byte 12 in the data field.

Function: Represents the character code and language code as a byte code.

Value: Same as SNC + L

-DATA (DATA)

Meaning: Individual additional information

Function: Represents all types of additional information with data of varying length. Actual data always starts from 12 bytes.

...... 40 -, ....... The length (size) of the actual data must be at least 4 bytes and a multiple of 4 bytes. The remainder of the data field must be filled with zero (0x00).

Value: Individually defined to correspond to the content of each type of additional information.

Sec. 13 is a table that associates key code values ​​(0 to 63) of additional information and their types. The key code values ​​(0 to 31) are assigned to the music character information. Key code values ​​32 to 63 are assigned to URLs (Uniform Resource Locator) (network information) 10. The music character information and URL information include the character information of the album title, artist name, CM and the like as additional information.

Sec. 14 is a table that associates key code values ​​(64 to 127) of additional information and their types. Key code values ​​(64 to 95) are assigned to paths / others. The key code values ​​(96 to 127) are assigned to the control / numerical data. For example, ID = 98 represents the TOC-ID as additional information. The TOC-ID shows the number of the first music program, the last music program number, the current program number, the total performance time and a CD (Compact).

Disc) represents the current music program duration corresponding to the TOC information.

Sec. 15 is a table that associates key code values ​​(128 to 129) of additional information and their types. The key code values ​​128 to 159 are assigned to the simultaneous replication information. Sec. 15,

EMD shows electronic music distribution.

Then, fig. With reference to Figures 16A to 16E, actual examples of additional information will be described. Sec. 12C, FIG. 16A shows the data structure of the additional information. Sec. Key code ID = 3 in 16B (artist name as additional information). SIZE = OxlC (28 bytes) indicates that the data length of the additional information, including the header, is 28 bytes; C + L represents the character code C = 0x01 (ASCII) and language code L = 0x09 (English). Variable size data after byte 12 represents one byte data sanatçı SIMON &amp; GARFUNKEL olarak as the artist name. Since the data length of the additional information must be a multiple of 4 bytes, it is populated with the remainder (0x00).

Sec. In 16C, the key code ID = 97 represents the ISRC (International Standard Registration Code: Copyright Code) as additional information, 10 SIZE = 0x14 (20 bytes) represents the data length of the additional information is 20 bytes. C = 0x00 and L = 0x00 indicate that characters and language are not specified. Therefore, the data is a pair of code. Variable-length data is an eight-byte ISRC code representing copyright information (country, copyright owner, registration year, and serial number).

Sec. In 16D, the key code ID = 97 represents the recording date and time as additional information. YOU = 0 x 10 (16 bytes) represents that the data length of the additional information is 16 bytes. C = 0x00 and L = indicates that characters and language are not specified. Variable-length data is a four-byte (32-bit) code that represents the recording date and time (year, month, day, hour, minute, second).

Sec. In 16E, the key code ID = 107 represents a replication log as additional information. YOU = 0 x 10 (16 bytes) represents that the data length of the additional information is 16 bytes. C = 0x00 and L = 0x00 indicate that characters and language are not specified. Variable-length data is a four-byte code that represents a replication log (year, month, day, hour, minute, second). When the recording / playback device has a replication log function, it records 16 bytes of data each time it reproduces the music data.

42şek. 17 is a schematic diagram illustrating a data arrangement of the ATRAC3 data file A3Dnnn when SU ​​is 1 byte (for example, N = 384 bytes). Sec. 17 shows an assigned title (1 block) of a data file and a music data file (1 block). Sec. 17 shows the first byte (0x0000 to 0x7FF0) of each set of two blocks (16 x 2 = 32 kbytes). Sec. 18, the first 32 bytes of the assigned header are used as a header; 256 bytes are used as a music program area NM1 (256 bytes); and 512 bytes are used as a music program title field NM2 (512 bytes). The header 10 of the assigned header contains the following fields.

= BLKID-HD0 (4 bytes)

Meaning: BLOCKID FIELD ID

Function: Specifies the top of an ATRAC3 data file. Value: Constant value: “HD = 0” (For example 0x48442D30) = MCode (2 bytes)

Meaning: MAKER CODE (MANUFACTURER CODE)

Function: Determines the manufacturer and model of the recording / playback device.

Value: High row 10 bit (manufacturer code); low row 6 bits (machine code) = BLOCK SERIAL (4 bytes)

Meaning: Trace serial number

Function: Starts from 0 and increases by 1. Even if a music program is corrected, this value does not change.

Value: 0 to OxFFFFFFFF = N1C + L (2 bytes)

Meaning: A permission (music program title) represents the assigned data (NM1).

Function: One byte represents the character code and language code of NM1 as code.

Value: Same as SN1C + L = N2C + L. (2 bytes)

Meaning: A trace (music program title) represents the assigned data (NM2).

Function: Represents the character code and language code of NM1 as a byte code.

Value: Same as SN1C + L = INFSIZE (2 bytes)

Meaning: The total size of the current permission additional information.

Function: Represents the data size as a multiple of 16 bytes.

When data is not stored, this field must be all 0.

Value: 0x0000 to 0x3C6 (966) = T-PRT (2 bytes)

Meaning: Total number of bytes

Function: Represents the number of parts that make up the current track. Normally, the value of T-PRT is 1.

Value: 1 to 285 (645 dec) = T-SU (4 bytes)

Meaning: Total number of SU

Function: Represents the total number of SUs on a track that corresponds to the program performance time.

Value: 0x01 to 0x001FFFFF = INX (2 bytes) (Possibility)

Meaning: INDEX's relative position

Function: Used as a pointer representing the upper part of a representative part of a music program. The value of INX,

44.

the current position of the program is designed with a value of SU divided by 4. This value of INX is 4 times greater than the number of SU (approximately 93 msec).

Value: 0 to OxFFFF (up to approx. 6048 seconds) = XT (2 bytes) (Possibility)

Meaning: Reproduction of INDEX time

Function: Designs the reproduction time designed by INX-ηηη by a number obtained by dividing the number of SU by 4. The value of INDEX is approximately four times greater than normal SU 10 (about 93 msec).

Value: 0x0000 (no setting); 0x01 to OxFFFF (up to 6084 seconds); OxFFFF (to the end of the music program).

Subsequently the music program title domains NM1 and NM2 will be described.

= NM1

Meaning: String of the music program title Function: Represents a music program title as a byte code (up to 256 characters) (variable length). The header field must be completed with an end code (0x00). The dimension must be calculated from the last code. When data is not stored, zero (0x00) must be recorded from the beginning of the field (0x0020) for at least one byte.

Value: Different character codes = NM2

Meaning: the character sequence of the music program title.

Function: Two bytes represent a music program title as code (up to 512 characters) (variable length). The header field must be completed with an end code (0x00). Dimension from the last code

45.— should be calculated. When data is not registered, zero (0x100) must be recorded from the beginning of the field (0x0120) for at least two bytes.

Value: Different character codes

Starting from the fixed position (0x320) of the assigned header, 80 5-byte data is referred to as a track information area TRKINF. This field is mainly used to fully manage security information and copy control information. Sec. 19 shows part of TRKINF.

The TRKINF field contains the following fields.

= CONTENTS KEY (8 bytes) io Meaning: Value for each music program. CONTENT

The value of the SWITCH is retained in the security block of the memory card and is then stored.

Function: Used as a key to reproduce a music program. Used to calculate the value of the MAC.

Value: 0 to OxFFFFFFFFFFFFFFFF = MAC (8 bytes)

Meaning: Copyright information check value.

Function: Represents the value generated by a set of TRKINF values, including content aggregation numbers and a hidden serial number.

The hidden serial number is a serial number stored in a hidden area of ​​the memory card. A recorder of the copyright non-protection type cannot read data from the hidden area of ​​the memory card. On the other hand, a computer with a copyright protection type recorder and a program that can read data from a memory card can access the hidden area.

= A (1 byte)

Meaning: Assigned to section.

40 ------- Function: Represents information as the compression mode of a partition.

Value: The details will be described in the following section (see Figs. 19 and 20).

Next, the value of area A will be described. In the following description, the monoral mode (N = 0 or 1) is defined as a special insertion mode with bit 7 = 1, sub-signal - 0, and main signal = (L + R). A copyright protection type playback device may not see information of bits 2 and 1.

The bit 0 field of Field A represents the information on the run / stop state. Bit 1 of field A represents fast or normal replication information. Bit 2 of field A represents information of such data, such as audio data, FAX data, or the like. Bit 3 of field A is not defined. With a combination of bits 4, 5 and 6, FIG. 20, the ATRAC3 mode information is identified. In other words, N is a 3-bit mode value. For five types of monoral (N = 0 or 1), LP (N = 2), SP (N = 4), EX (N = 5) and HQ (N = 7) mode, recording time (64 MB memory only) card), data transmission rate, and number of SUs per block. 1 The number of bytes of SU varies with each mode. The number of bytes of 1 SU in monoral mode is 136 bytes. In LP mode, the number of bytes of 1 SU is 192 bytes. In SP mode, the number of bytes of 1 SU is 304 bytes. In EX mode, the number of bytes of 1 SU is 384 bytes. The number of bytes of 1 SU in HQ mode is 512 bytes. Bit 7 of field A represents ATRAC3 modes (0: Duplicate, 1: Joint).

For example, an example will be described in which a 64 MB memory card is used in SP mode. A 64-MB memory card has 3968 blocks. Since 1 SU is 304 bytes in SP mode, a block 53 contains SU. 1 SU is equivalent to (1024/44100) seconds. Therefore, a block is (1024/44100) x 53 x (3968-10) = 4863 seconds = 81 minutes. The transmission rate is (44100/1024) x 304 x 8 = 104737 bps.

= LT (one byte)

Meaning: Replication limiting pennant (bits 7 and 6) and security allocation (bits 5 to 0).

Function: Represents a limitation of the current permission.

Value: bit 7: 0 = no limitation, 1 = limitation bit 6: 0 = not finished, 1 = finished bits 5 to 0: security allocation (replication other than 0 is prohibited) = FNo (2 bytes)

Meaning: File number

Function: Represents the initially registered track number that determines the position of the MAC calculation value stored in the hidden area of ​​the memory card.

Value: 1 to 0x190 (400) = MG (D) SERIAL-nnn (16 bytes)

Meaning: Represents the serial number of the safety block (safety IC 20) of the recording / playback device.

Function: Unique and unique value for each recording / playback device

Value: 0 to OxFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF = CONNUM (4 bytes)

Meaning: Content aggregation count

Function: Represents a unique and unique value stacked for each music program. The value is guided by the safety block of the recorder. Upper limit of value 2³²that is, 4,200,000,000. Used to identify a saved program.

Value: 0 to FFFFFFFF

YMDhms-S (4 bytes) (Possibility)

Meaning: Allow replication to limit replication start date and duration

Function: Represents the date and time during which data reproduction is possible with the EMD.

Value: Same as date and time notation of other fields.

= YMDhms-E (4 bytes) (Possibility)

Meaning: Replication limit allowed replication deadline and duration io Function: Represents the date and time that the data replication ends with the EMD.

Value: Same as date and time notation of other fields = MT (1 byte) (Possibility)

Meaning: Maximum value of the number of possible replication times

Function: Represents the highest number of replication times designed with EMD.

Value: 1 to 0xFF. When not in use, the value of the field MT is OO.

= CT (1 byte) (Possibility)

Meaning: Number of replication times

Function: Represents the number of replication times, in the number of replication times possible. Each time the data is replicated, the value of the field CT decreases.

Value: 0x00 to 0xFF. The value of the CT that receives when not in use is OxOO. Bit 7 of the field LT is 1 and the value of the field CT is OO, replication of the data is prevented.

= CC (1 byte)

-- 49 ·

Meaning: COPY CONTROL (COPY CONTROL)

Function: Controls the copy operation.

Value: bits 6 and 7 represent copy control information, bits and 5 represent copy control information of a high-speed digital copy operation, bits 2 and 3 represent a security block authentication level, bits 0 and 1 are not defined.

CC example:

(bits 7 and 6)

11: Unlimited copying is free Io 01: Copying is prohibited

00: free copy once (bits 3 and 2): analog / digital input recording

MG approval level is 0.

When a digital recording operation using data forward from a CD is performed, it is (bits 7 and 6): 00 and (bits 3 and 2): OO.

= CN (1 byte) (Possibility)

Meaning: Number of copies allowed in a high-speed serial copy management system

Function: Extends the copy permission by the number of copy times, without being limited to once copying permission and copying permission. Only valid for the first copy generation. The value of the field CN decreases each time the copy operation is performed.

Value"

00: Copy prohibited to 0xFE: Times 0xFF: Unlimited copy

5().

Trace information area TRKINF is followed by a 24-byte partition management information area (PRTINF) starting from 0x0370. When a track consists of a set of segments, the areas of the individual segments are arranged such that the values ​​of PRTINF follow one another on the time axis 5. Sec. 22 shows a portion of the field PRTINFTn. Next, the fields in the PRTINF area will be described, respectively.

io = PRTSIZE (4 bytes)

Meaning: Section size

Function: Represents the size of a partition.

Cluster: 2 bytes (highest position), start SU: 1 byte (top), last SU: 1 byte (lowest position).

Value: set: 1 to 0xlF40 (8000) start SU: 0 to 0xA0 (160) last SU: 0 to 0xA0 (16) (note that SU starts from 0) = PRTKEY (8 bytes)

Meaning: Partition encryption value

Function: Encrypts a partition. Initial value = 0. Note that the correction conditions must be applied.

Value: 0 to OxFFFFFFFFFFFFFFFF

CONNUMO (4 bytes)

Meaning: Initial content stack number switch

Function: Designs an ID of the content individually.

Value: The same value as the value of the content stack number initial value key i ----------- 51—

Sec. 17, the assigned 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 replication management file, with the exception that the starting position is not fixed. The last byte position at the end of one or more segments (a multiple of four bytes) is followed by the data of the additional information INF.

= INF

Meaning: Additional information about the trail

Function: Represents additional information of different lengths with a header. A set of additional information of different types can be edited. The additional information fields each have an ID and a data dimension. Each additional information area consists of at least 16 bytes and a multiple of 4 bytes.

Value: Additional information of replication management file same as INF-S

The aforementioned assigned header follows the data of each block of an ATRAC3 data 15 file. Sec. A cap is added for each block as shown in FIG. Next, the data of each block will be described.

• = BLKID-A3D (4 bytes)

Meaning: BLOGKID FILE ID

Function: Defines the upper part of the ATRAC3 data.

Value: Constant value = “A3D” (for example, 0x41334420) = MCode (2 bytes)

Meaning: MAKER CODE (MANUFACTURER CODE)

Function: Identifies the manufacturer and model of the recording / playback device 25.

Value: High-order 10 bit (manufacturer code); low-order 6 bit (model code) = CONNUMO (4 bytes)

Meaning: Number of aggregates of content originally created

Function: Designs a unique and unique ID for content. Even if the contents are corrected, the value of the CONNUMO field does not change.

Value: Number of content aggregates same as start key = BLOCK SERIAL (4 bytes)

Meaning: Serial number assigned to each track

Function: Starts from 0 and increases by 1. The value of the BLOCK SERIAL field does not change even if the contents are corrected.

Value: 0 to OxFFFFFFFF = BLOCK SEED (8 bytes)

Meaning: Key to encrypt a block

Function: The beginning of a block is a random number generated by the safety block of the recording / playback device. The random number is followed by an incrementing value of 1. When the value of the BLOCK-SEED field disappears, the same data is written to the title and end of the block, since there is no sound for about one second corresponding to a block. Even if the contents are corrected, the value of the BLOCK-SEED field does not change.

Value: 8-bit random number as initial = INITIALIZATION VECTOR (8 bytes)

Meaning: Value required to encrypt / decrypt ATRAC3 data

Function: Represents an initial value required to encrypt and decrypt ATRAC3 data for each block. A block starts from O. The next block starts from the last 8-bit value encrypted in the last SU. When a block is split, the last eight bytes just before the start SU are used. Even if the contents are corrected, the value of the INITIALIZATION VECTOR field does not change.

5y

Value: 0 to OxFFFFFFFFFFFFFFFF = SU-nnn

Meaning: Audio unit data

Function: Represents data compressed from 1024 samples. The number of bytes of output data varies with compression mode. Even if the contents are corrected, the value of the SU-nnn field does not change. For example, in SP mode, N = 384 bytes.

Value: data values ​​of ATRAC3

Sec. In 17, since N = 384, 42 SU is written to a block. The first two sets of a block (4 bytes) are used as the title. In the last set (two bytes), the fields BLKID-A3D, MCode, CONNUMO and BLOCK SERIAL are written in redundancy. Therefore, the M byte of the remaining area of ​​a block (16,384 - 384 x 42 - 16 x 3 = 208) is bytes. As described above, the eight-byte BLOCK SEED allam was recorded as redundancy.

When the FAT area is destroyed, all blocks of flash memory are searched. At the beginning of each block, it is determined whether the value of the ID BLKID field is TLO, HDO or A3D. Sec. As shown in 24A to 24C, in step SP1, it is determined whether the value of the FD BLKID field at the beginning of the upper block is BLKID-TLO. If the result determined in stage SP1 is no, the flow proceeds to stage SP2. In Phase SP2, the block number increases. It is then determined in step SP3 whether the last block is searched.

If the result determined in stage SP3 is no, the flow returns to stage SP1.

If the result determined in stage SP1 is yes, the flow proceeds to stage SP4. In phase SP4, the searched block is determined to be the replication management file PBLIST. Thereafter, flow towards phase SP5

54 '------ progresses. In phase SP5, the total number of tracks in the replication management file PBLIST is recorded in the number of T-TRK, N. For example, when memory 10 stores ATRAC3 data files (10 music programs), 10 is stored in the TTRK.

Then, the total traces of the blocks are referenced consecutively, referring to the value of the numbers of T-TRK, TRK-001 to TRK400. In this example, since 10 music programs are recorded, blocks TRK-001 to TRK010 are referenced. In step SP7, since a file number FNO is stored in TRK-XXX (where X = 1 to 400), a file is stored in memory that associates the track number TRK-XXX and the file number FNO. Then, in step SP8, the N stored in the register is reduced. A repetition of steps SP6, SP7 and SP8 is continued until N 0 in step SP9.

If the result determined in stage SP9 is yes, the flow proceeds towards stage SPIO. In Phase SPIO, the display is set back to the upper block. The search process is repeated from the top block. The flow then proceeds to stage SP11. In stage SPI, it is determined whether the value of the ID BLKID field of the upper block is BLKID-HD0. If the result determined in stage SP1 is no, the flow proceeds to stage SP12. In phase SP12, the block number increases. In step SPI3, it is determined whether the last block is searched.

If the result determined in stage SP13 is no, the flow returns to stage SP11. The search process is repeated until the result determined in stage SPI 1 is yes.

When the result determined in stage SP1 is yes, the flow proceeds towards stage SP14. In step SP14, the block is determined to be the title assigned at the beginning of the ATRAC3 data file (see Fig. 8) (0x0000 to 0x03FFF shown in Fig. 18).

Next, in step SP15, with respect to the file number FNO, the serial number BLOCK SERIAL of the same ATRAC data file and the content stack number key contained in the assigned header are stored in CONNUMO memory. When 10 ATRAC3 data files are saved, the search process is continued until 10 blocks are searched, since there are 10 blocks in which the value of the ID BLKID field of the upper block is BLKIDTLO.

When the result determined in stage SP13 is yes, the flow proceeds to stage SP16. In phase SP16, the display is set back to the upper block. The search process is repeated from the top block.

The flow then proceeds to stage SP17. In step SP17, it is determined whether the value of the ID BLKID field of the upper block is BLKID-A3D.

When the result determined in stage SP17 is no, the flow proceeds to stage SP18. In phase SP18, the block number increases. It is then determined in step SP18 whether the last block is searched. When the result determined in stage SP18 is yes, the flow proceeds towards stage SP19. In step SP19, the block is determined to contain ATRAC3 data. The flow then proceeds to stage SP20. In phase SP20, with respect to the serial number BLOCK SERIAL and the content stack number switch CONNUMO stored in the ATRAC3 data block, these are stored in memory.

In the same ATRAC3 data file, the content aggregation number key is assigned the public number as CONNUMO. In other words, when an ATRAC3 data file consists of 10 blocks, a common number is assigned to all values ​​of the CONNUMO fields.

In addition, when an ATRAC3 data consists of 10 blocks, serial numbers 1 to 0 are assigned to the values ​​of the fields of the BLOCK SERIALS of the 10 blocks.

In accordance with the values ​​of the CONNUMO and BLOCK SERIAL fields, it is checked whether the current block consists of the same contents and the replication order in the same contents (ie connection series).

When the ATRAC3 data file (ie 10 music programs) is recorded and each of the ATRAC3 data files consists of 10 blocks, there are 100 data blocks.

Regarding the values ​​of the CONNUMO and BLOCK SERIAL fields, the reproduction order and the connection order of music programs of 100 data blocks can be obtained.

When the result determined in step SP17 is yes, all blocks are searched for the replication management file, the ATRAC3 data file, and the assigned file. Thus, in step SP21, the file link state is obtained based on the values ​​of the CONNUMO, BLOCK SERIAL, FNO and TRK-X fields in the block count order of the blocks stored in memory.

After the connection state is achieved, FAT can be created in a free area of ​​memory.

Next, a management file according to a second embodiment of the present invention will be described. Sec. 25 shows the file structure according to a second embodiment of the present invention, FIG. 25, a music folder is a trace information management file TRKLIST.MSF (hereinafter referred to as IRKLIST), a back-up trace information management file TRKLISTB.MSF (hereinafter referred to as TRKLISTB), an additional information file INFLIST.MSF (an artist name, an ISRC code, a time stamp, a still image data, and so on)

An ATRAC3 data file A3Dnnnn.MSF (hereinafter referred to as A3nnnn). The file contains two fields, TRKLIST, NAME1 and NAME2. NAME1 is a field that contains the memory card name and program name (for a byte code corresponding to the ASCII / 8859-1 character code). The NAME2 field is a field that contains the memory card name and program step (for two byte code corresponding to the MSJIS / Hankul / Chinese code).

Sec. Fig. 26 shows the trace information management file TRKLIST, fields NAME1 and the relationship between NAME2 and ATRAC3 data file A3Dnnnn. The file TRKLIST is a fixed-length file of 64 kbytes (= 16 kx 4). A 32-kbyte area of ​​the file is used to manage traces. The remaining 32 kbytes are used to contain the NAME1 and NAME2 fields. Although the NAME1 and NAME2 fields for program names can be provided in a different file format as a trace information management file on a small storage system, it is convenient to manage the trace information management file and program name files in bulk.

Trace information area TRKINF-mum and PRTINF-nnnn are used to manage the data file A3Dnnnn and additional information INFLIST. The ATRAC3 data file is only encrypted with A3Dmmn. Sec. 26, the data length in the horizontal direction is 16 bytes (0 to F). A hexadecimal number in the vertical direction represents the value at the beginning of the current line.

According to the second embodiment, the track management file TRKLIST (including a program title file), three files with additional information management file INFLIST and data file A3Dnmm are used. According to the first embodiment (see Figs. 7, 8 and 9), the entire memory card

---------58.....

To manage the replication management file PBLIST and programs to store the data file ATRAC3 is used two files.

Next, the data structure according to the second embodiment will be described. For simplicity, the description of sections similar to those of the first embodiment is omitted in the data structure according to the second embodiment.

Sec. 27 shows the detailed structure of the trace information management file TRKLIST. In TRKLIST, the trace information management file, a cluster (block) consists of 16 kbytes. The size and data of the TRKLISTB file are the same as those of the back-up file TRKLISTB. The first 32 bytes of the trace information management IO file are used as a header. As with the title of the replication management file PBLIST, the title of the TRKLIST file is a BLKID-TL0 / TL1 (back-up file ID) field (4 bytes), a field T-TRK (2 bytes), a field code for the total number of tracks. area

MCode (2 bytes), TRKLIST contains a field for the number of rewrite 15 REVISION (4 bytes), and a field for update date and time data S-YMDhms (4 bytes) (enable) field. The meanings and functions of these data fields are the same as those of the first embodiment. In addition, the TRKLIST file contains the following fields.

= YMDhms (4 bytes)

Represents the last updated date (year, month, day) of the TRKLIST file.

= Nl (1 byte) (Possibility)

Represents the serial number of the memory card (numerator side). When a memory card is used, the value of field N1 is 0x01.

= N2 (1 byte) (Possibility)

Represents the serial number of the memory card (numerator side).

When a memory card is used, the value of field N2 is 0x01.

= MSID (2 bytes) (Capability) '* 59

Represents the ID of a memory card. When a set of memory cards is used, the value of the MSID field of each memory card is the same (TBD). (TBD (to be defined) indicates that this value can be defined in the future).

= S-TRK (2 bytes).

It represents a special trace (TBD).

Normally, the value of the S-TRK field is 0x0000.

= PASS (2 bytes) (Possibility)

Represents a password (TBD). io = APP (2 bytes) (Possibility)

Represents the definition (TBD) of a replication application (normally the value of the APP field is 0x0000).

= INF-S (2 bytes) (Possibility)

It represents the additional information display of the entire memory card. When there is no additional information, the value of the INF-S field is 0x00.

The last 16 bytes of the TRKLIST file are used for a BLKID-TLO field, an MCode field, and a REVISION field, which are the same as those of the header. The back-up file TRKLISTB contains the title described above. In this case, the header contains a BLKID-TL1 field, a MCode field, and a REVISION field.

The header includes a track information field for information about each track and a chapter information field PRTINF for information about each part of the tracks (music programs). Sec. 27 Shows the fields that precede the TRKLIST field. The lower part of the TRKLISTB field shows the detailed structure of these fields. Sec. 27, the shaded area indicates an unused area.

The track information field TRKINF-nnn and the segment information field PRTINF-nnn contain the fields of an ATRAC3 data file. In other words, each of the track information area TRKINF-nnn and section information area PRTINF-nnn, a replication limitation streamer area LT (1 byte), a content key area CONTENT SWITCH (8 bytes), a recording / playback device security block serial number field MG (D) SERIAL (16 bytes), a field XT (2 bytes) (possible), a field INX (2 bytes) (possible), a field YMDhms-S (4) to represent a feature part of a music program bytes) (enable), one field YMDhms-E (4 bytes) (enable), one field MT (1 byte) (enable), one field CT (1 byte) (enable), one field CC (1 byte) (enable), one field CN (1 byte) (enable) (these fields are YMDhms-S, IO YMDhms-E, MT, CT, CC and They are used for CN replication limitation information and copy control information), a field A (1 byte) for partition assignment, a partition size field PRTSIZE (4 bytes), a partition key field PRTKEY (8 bytes), and a content stack number field CONNUM (4 bytes). The meanings, functions and values ​​of these fields are the same as those of the first embodiment. In addition, the track information area TRKINF-nnn and the segment information area PRTINF-nnn each contain the following fields.

= TO (1 byte)

Constant value (TO = 0x74) = INF-nim (Possibility) (2 bytes)

Each trace represents the additional information indicator (0 to 409). 00: music program without additional information.

= FNM-rmn (4 bytes)

The file number of an ATRAC3 data file (from 0x0000 to

OxFFFF).

The ATRAC3 data file name (A3Dnnnn) is converted to Oxnnnnn.

= APPCTL (4 bytes) (Possibility)

Represents an application parameter (TBD) (Normally the value of the APP_CTL field is 0x0000).

= P-nnn (2 bytes)

Represents the number of sections (1 to 2039) that make up a music program. This field corresponds to the T-PART field described above.

= PR (1 byte)

Constant value (PR = 0 x 50).

Next, the fields NAME1 (for one byte code) and NAME2 (for two byte code) will be described to manage names. Sec. 28 shows the detailed structure of the NAME1 field (for a byte code field). The NAME 1 and NAME2 fields (which will be described later) are divided into eight bytes each. Therefore, a set of them consists of eight bytes. At the beginning of each of these fields, 0x8000, a header is built. The title is followed by an indicator and a name. The last set of field NAME1 contains the same fields as the header.

= BLKID-NM1 (4 bytes)

Represents the content of a block (constant value) (NM1 = 0x4E4D2D31).

= PNMl-nnn (4 bytes) (Possibility)

The field represents the indication of NM1 (one byte for code).

= PNM1-S

Nnn (= 1 to 408) represents the indication of a music program title.

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

= NM1-nnn (Possibility)

Represents the memory card name and music program title (variable length) for one byte code. A final code (0x00) was written at the end of the field.

Sec. 29 shows the detailed data structure of the NAME2 field (for two bytes). At the beginning of the field, 0x8000 has a header. The title is followed by an indicator and a name. The last set of field NAME2 contains the same fields as the header.

= BLK1D-NM2 (4 bytes)

Represents the content of a block (constant value) (NM2 = 0x4E4D2D32).

= PNM2-nnn (4 bytes) (Possibility)

The field represents the indication of NM2 (for two bytes of code).

The PNM2-S represents a step indicator representing a memory card, mm (= 1 to 408) represents the indicator of a music program title.

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

= NM2-nnn (Possibility)

The two-byte code represents the music program title and memory card name (variable). An end code (0x0000) is written at the end of the field.

Sec. 30, 1 shows the data arrangement (for a block) of the ATRAC3 data file A3Dnnn if SU consists of N bytes. In this file, a cluster consists of eight bytes. Sec. 30 shows the parent values ​​(0x0000 to 0x3FF8) of each set. The first four sets of the file are used for a title. In the first example, a header is placed, as is the case with the data blocks preceding the assigned title of the data file (see Fig. 17). Title is a field BLKID-A3D (4 bytes), a manufacturer code field MCode (2 bytes), to encrypt the process

63 'a required field BLOCK-SEED (8 bytes), a field for the initial content stack number CONNUMO (4 bytes), a serial number field for each trace BLOCK SERIAL (4 bytes), and a field required for the encryption / decryption process INITIALIZATION Contains VECTOR (8 bytes). The second last set of block contains an area BLOCK SEED in redundancy. The final set of fields includes BLKID-A3D and MCode. As in the first embodiment, the title is followed by the audio unit data SU-nnnn.

Sec. 31 shows the detailed data structure of the additional information management file 10 INFLIST containing the additional information. In the second embodiment,

At the beginning of the INFLIST file (0x0000), the following header is built. Indicators and fields following the title are followed.

= BLKID-INF (4 bytes)

Represents the contents of the block (constant value) (INF = 0x494E464F).

- T-DAT (2 blocks)

Represents the total number of data fields (0 to 409).

· MCode (2 bytes) temsil Represents the manufacturer code of the recorder / recorder = YMDhms (4 bytes)

Represents the record update date and duration.

= INF-nnnn (4 bytes)

Represents the indication of the DATA field of the additional information (variable length in 2 bytes (set) at a given time point). The starting position is represented by a high order 16 bit (0000 to FFFF).

= DataSlot-0000 (0x0800)

Represents the deviation from the start (as a set at a given time point)

The data size is represented by a low sequence of 16 bits (0001 to 7FFF). The most obvious bit is a non-capable flag. MSB = 0 (able), MSB = 1 (not able)

The data size represents the total amount of data for the music program.

(Data starts from the beginning of each set. (The non-data field of the set is filled with 00)

The first INF represents an indication of the additional information of the entire album (normally INF-409).

10 Fig. 32 shows the structure of the additional information. An 8-byte header is placed at the beginning of an additional information data field. The structure of the additional information is the same as that of the first embodiment (see Fig. 12C). In other words, additional information, an area IN as an ID (2 bytes), an area key code ID (1 byte), an IS SIZE area (2 bytes) representing the size of each additional information area, and a manufacturer code area MCode (2) byte). In addition, the additional information includes a field SID (1 byte) as a subid.

According to a second embodiment of the present invention, in addition to the file system defined as a format of the memory card, the track information management file TRKLIST music data is used. Therefore, even if FAT is destroyed, the file can be recovered. Sec. 33 shows the flow of a file compensation operation. To compensate for the file, a computer operating with a file compensation program that has access to 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 DSP 30. Next, a file compensation process using the trace management file TRKLIST will be described.

All blocks of flash memory with FAT destroyed are searched for TL-0 as value (BLKED) in the upper position of each block. In addition, in the upper position of each block, all blocks for NM-1 are searched as value (BLKID). After that, all blocks are searched for NM-2 as value (BLKID) in the upper position of each block. The entire contents of the four blocks (trace information management file) are stored with the compensation computer, for example on a hard disk.

The total number of tracks is obtained from the data after the fourth byte of the track information management file. The 20th byte of the track information field TRKINF-OO1, the value of the CONNUM-OO1 field of the first music program and the value of the next field P-001 are obtained. The number of sections is obtained by the value of the P001 field. The values ​​of the PRTSIZE fields of all parts of the 1st trace of the PRTINF field are obtained. The number of total blocks (sets) n is calculated and obtained.

Once the trace information management file is obtained, the flow proceeds to step 102. In step 102, an audio data file (ATRAC3 data file) is searched. All blocks except the management file are searched from the flash memory. Blocks with an upper value (BLKID) of A3D are added.

A block with the value of the CONNUMO field in byte 1 of A3Dnnnn is the same as that of the CONNUM-001 field of the first music program of the track information management file, and the block in which the value starting from the 20th byte of the BLOCK SERIAL is searched. Once the first block is obtained, a block (cluster) with the same CONNUM field value as the first block and the BLOCK SERIAL value is increased by 1 (1 = 0 + 1) is searched. After the second block is obtained, a block with the same value as the CONNUMO field of the second block and the BLOCK SERIAL value is increased by 1 (2 = 1 + 1) is searched.

By repeating the process, the ATRAC3 data file is searched until n blocks (sets) of track 1 are obtained. When all blocks (clusters) are obtained, they are stored on the hard disk in succession.

The same process as for track 1 is performed for track 2. In other words, a block is searched for which the value of the CONNUMO field is the same as that of the CONNUM-002 field of the first music program of the track information management file, and the BLOCK SERIAL field starts from the 20th byte. The ATRAC3 data file is then searched in the same way as track 1 until the last block (set) n 'is detected. After all the blocks (clusters) are obtained, they are stored in succession on the hard disk.

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

In step 103, the FAT-erased memory card is restarted and 15 is then reconstructed. A preset folder is created on the memory card. The trace information management file and the ATRAC3 data file for the m trace are then copied from the hard disk to the memory card. This ends the compensation process.

In the management file and in the data file, important parameters 20 (in particular the codes in the headings) can be saved three times instead of two. When the data is saved as redundancy, the same data can be saved in any position as long as they are one page or more away from each other.

Then, Figs. 34, data bytes and transmission ratios 25 will be described in accordance with the present invention. Sec. 20, the expected compression ratio for known memory cards is about 1/8 to 1/43. In other words, a transmission rate of 705 kbps of a channel of a CD is compressed to 88 kbps to 16 kbps. For ATRAC3

In the case of 1024 samples / channels used, the amount of SU data (hereinafter referred to as the SU value) as the data unit of the compression process is in the range of 256 bytes to 48 bytes. The duration of 1024 bytes is approximately 23 msec. In the known method where the audio data is not encrypted, any SU value within such range can be used.

An appropriate SU value is selected, taking into account an appropriate data unit (eight bytes) for an encryption process corresponding to DES, 16 bytes are suitable for both stereo mode and monoral mode 10 and are independent of the encoding process so as to improve the encoding process . In addition, it is preferable to record audio data of 74 minutes or more, taking into account the recording time of a CD. Alternatively, it is preferred to record the video data in a multiple of 60 minutes for a VCR and a broadcast program. Thus, an appropriate SU value is selected, taking into account the recording time of 74 minutes and 60 minutes.

In the case of two channels (stereo mode), suitable SU φ values ​​are shown in FIG. 512 bytes, 400 bytes from the table shown in FIG.

384 bytes, 320 bytes, 272 bytes, 256 bytes, 192 bytes and 160 bytes can be selected.

Sec. Example 71 in FIG. 34 shows that the transmission rate for each channel is 88.2 kbps. In this case, the number of bytes of each channel is 256 bytes. Therefore, the number of bytes of the two channels is 512 bytes. The compression ratio is represented by (number of bytes per SU 7 number of samples x number of samples per sample) (ie, B / (1024 x 2)). The number of bytes per water is a multiple of 16. In the case of two channels, the transmission rate is 176.4 kbps. The number of SU entered per block (16 kbytes) is 3l.

,.....“6&amp;.

The recording time of stereo audio data recorded with a memory card of Mbytes is 2853,361 seconds (47,556 minutes). Thus, considering a response, 47-minute stereo audio data can be recorded, whereas 95-minute monoral audio data can be recorded. The parts of each block of the memory card are 512 bytes. Because a set consists of eight bytes, the number of remaining sets is 64 (512/8 = 64). Sec. 30, at least five clusters are required as the remaining clusters. Therefore, FIG. In 34, the data bytes and transmission ratios listed just below Example 7 1 cannot be used because the number of clusters remaining is 2.

In Example 72, the transmission rate of a channel is 66.2 kbps. The number of bytes of a channel is 192. The number of bytes of the two channels is 384 bytes. The transmission rate of the two channels is 132.3 kbps. The number of SU is 42. The recording time of stereo audio data is 3865,844 seconds (64,431 minutes). In case of a disregard, 64-minute stereo audio data can be recorded, while 128-minute monoral audio data can also be recorded. The remaining bytes of each block are 256. The number of remaining sets of each block is 32.

In Example 73, the transmission rate of a channel is 52.4 kbps. The number of bytes of a channel is 152. The number of bytes of the two channels is 304 bytes. The transmission rate of the two channels is 104.7 kbps. The number of SU is 53. The recording time of stereo audio data is 4878.327 seconds (81.305 minutes). In case of a disregard, 81-minute stereo audio data can be recorded, while 162-minute monoral audio data can also be recorded. The remaining bytes of each block are 272. The number of remaining sets of each block is 34.

In Example 74, the transmission rate of a channel is 33.1 kbps. The number of bytes of a channel is 96. The number of bytes of the two channels is 192 bytes. The transmission rate of the two channels is 66.2 kbps. The number of SU is 85. The recording time of the stereo audio data is 7823.732 seconds (130.396 minutes). In case of a disregard, 130-minute stereo audio data can be recorded, while 260-minute monoral audio data can also be recorded. The remaining bytes of each block are 64. The number of remaining sets of each block is 8.

Sec. Compared to the tables shown in Figs. 34 and 20, Examples 71, 72, 73 and 74 correspond to HQ mode, EX mode, SP kiipne and LP mode, respectively.

The recorder according to the present invention has a processing section with which compression ratios corresponding to HQ mode, EX mode, SP mode, LP mode and the like can be selected. In accordance with the operation of the processing section, the recorder selects a compression ratio and records the data with the selected compression ratio.

In the recorder according to the present invention, FIG. The table shown in FIG.

The ROM is stored in memory. The number of audio units corresponding to the compression ratio with respect to the ROM memory is selected. In accordance with the number of audio units, the compressed and encoded digital audio data is divided into blocks and stored in a flash memory.

Then, Figs. 1, an example of a method for compressing data in accordance with a selected SU value will be described. In the mode selected by the external operation section, a SU value corresponding to the mode is selected. The mode signal is sent to the DSP 30 via electrical connections 33 and 32. DSP 30 selected SU value encoder / decoder block

12. As described above, the encoder / decoder block

12 performs a highly effective encoding process for a digital audio signal written to the memory card 40. In addition, the encoder / decoder 12 decodes the data read from the memory card 40.

When the audio data of the flash memory is corrected, the data is saved / reproduced in the unit of a page. Therefore, it is appropriate to select the number of bytes per SU as 512 bytes, 256 bytes, or 128 bytes. Since the physical properties of SU correspond to that of the flash memory, the data for each page can be corrected without loss.

An example where the physical properties of the flash memory are compatible with those of SU is Example 71, wherein the number of bytes of the two channels is 71. Using Example 71, a SU is produced in which 2048 samples are compressed to 512 bytes with a compression ratio of (1/8). In this case, the recordability period of a SU becomes:

2048 / 44100 = 46.44 msec

The data can be effectively encrypted even though the correction unit is extended.

According to the present invention, the amount of data of the SU is determined, taking into account the fragmentation of the encrypted data and the correction (erase) unit of the flash memory. Moreover, the compression ratio is selected, taking into account the time it takes to record the audio data to a memory card. Therefore, the data can be effectively encrypted.

Although the present invention has been illustrated and described in the best mode of embodiment, the skilled artisan should understand that the above-mentioned and other modifications, additions or deletions may be made without departing from the scope and spirit of the present invention. April 27 Tfiflü

MEANING OF ARTICLES IN THE FIGURE

FIGURE 1

32, 33 = Electrical connection = Memory card

A = Line is running

B = Station seeker

13 = Band

19 = Line does not work

FIG.

34 = Core

35 = 256K Flash

C = Bridge

FIG.

45 = Page buffer

51 = Flash l / F serializer 42 = Flash memory

61 = osckont.

D = Rearrange

FIG.

E = Application process

F = File management process G = Logic address management H = Philosophical address management l = Flash memory access J = File system process hierarchy

FIG.

K = Boot blocks

L = User blocks

M = Page

N = Title field

0 = Restricted block data area

P = Backup block

R = Information block S = User block T = Boot block

U = Overlapper

V = Logic address space

Y = Format reserve area

Z = Scattered information (ECC) area

A1 = Data ECC field

B1 = Data (512 Bytes)

C1 = Redundancy section (16 bytes)

D1 = Management pennant area

E1 = Update status F1 = Page status

G1 = Block status

FIG.

H1 = Share table (512 bytes) 11 = Empty

J1 = Boot section

K1 = Subfolder

L1 = FAT Share 2G bytes

M1 = FAT copy

N1 = Path folder

2,3,4,5,6,7,8,9,10,11,12,13,100,101,110,111,200,201 = Cluster

FIG.

01 = Path

P1 = Still image folder

R1 = Motion picture folder

S1 = Sound folder

T1 = Control folder

U1 = Music folder

V1 - Replication management file

Y1 = Music program data file

Z1 = Sound

FIG.

A2 = Title

B2 = Bytes

FIG.

C2 = An ATRACK3 Music program data file

D2 = Assigned title

E2 = Data

FIG.

F2 = File 1

H2 = Cluster

12 = Section

J2 = 4th magnified view of cluster K2 = 1. End of music program

L2 = End of section

M2 = File 2

N2 = 1. Music program start

02 = 2. Start of the music program P2 = End of the music program FIGURE 10B

R2 = Start

S2 = End

FIG.

T2 = File 2

FIG.

U2 = Replication management file (BPLIST)

V2 = Reserved

Y2 = Review

Z2 = Content key

FIG.

A3 = Variable length data

FIG.

B3 = Music information (characters)

C3 = Variable

D3 = VRL Information (Network information)

0,32 = Reserved

I, 33 = Album

2.34 = Subtitle

3.35 = Artist

4.36 = Chief

5.37 = orchestra

6.38 = Producer

7.39 = Publisher

8,40 = Composer

9.41 = Song

10,42 = Songwriter

II, 43 = Sponsor

13, 45 = Guide

14,46 = Original music program title 16,48 = Original album title 17,49 = Original music program composer 18,50 = Original music program editor 19,51 = Original music program player

20 = Message

21 = Half

22 = Warning

23 = Type

FIG.

E3 = Road / Others

F3 = Control / numeric data information

64.96 = Reserved

65 = Path to video data

66 = Path to song data

67 = Path to Midi data

68 = Path to guidance data

69 = Data interpretation path

70 = Path to CM data

71 = Path to fax data.

72 = Communication data lead to 1

73 = path to communication data 2

74 = Path to control data

100 = Saved data

101 = Released data

102 = Original music program released data 103 = Recorded data

104 = Lower track

105 = Average sound level

106 = Summary

107 = Replication log

108 = Replication numbers (for learning)

110 = APP Level

111 = Type code

112 = Midi data

113 = Short photo data

114 = Duplicate text feed data

115 = Total number of music programs

116 = Setting number

117 = Number of total settings

118 = Record position information

119, 121 = BP Position information

120 = Record position given

122 = Link orientation phone number 1

123 = Link orientation phone number 2

124 = Input value

125 = Output value

126 = BP Control data

127 = Record control data

FIG.

G3 = Simultaneous replication information

128 = Reserved

129,120,131,132,133,134 = Simultaneous replication information 138,139 = EMD Information FIGURE 16A H3 = Size

I3 = Variable size data

FIG. 16B

J3 = Artist

K3 = English

L3 = Data

FIG. 16C

M3 = Double not set

FIG. 16D

N3 = Saved data

FIG.

03 = Replication log

FIG.

P3 = Data file

S3 = Dimensions of information

FIGURE 20

T3 = Joint

U3 = Mode

V3 = Duration

Y3 = Transmission ratio

Z3 = Mode value

47,58,64,81,90,128,181,258 = Minutes A4 = Rapid replication B4 = Normal multiplication C4 = Other

D4 = Fast

FIG.

E4 = Copy permission

F4 = Copy prevention

G4 = Creation

H4 = First or later copies

I4 = Copy control for high speed digital copy

J4 = Copying is prohibited

K4 = General first copy

L4 = Approval level

M4 = Level

N4 = Copying of the first copy is prohibited

Divide and join at levels other than 04 = 10 are prohibited.

FIGURE 24A P4 = Figure R4 = Process S4 = No

T4 = Yes

SP2 = Block increase

SP4 = Search block PBLIST

SP3 = End of block

SP5 = Corresponds to all TRK — N T-TRK BPLIST

SP6 = TRK-XX in succession from PBLIST

SP7 = TRK-karşı against memory FNO table

U4 = Error

FIG. 24B

SP10 = Return to the top of the block

SP12 = Block increase

SP14 = Search block assigned file

SP13 = Block thread

SP15 = TABULATE FNO CONNUMO and BLOCK SERIAL corresponding to the number of blocks and the storage table in memory

FIG. 24C

SP16 = Leather return to block start

SP18 = End of block

SP21 = Obtains connection status according to each table stored in memory SP19 = Search block ATRAC3 file

SP20 = Associates the number of blocks, CONNUMO and BLOCK SERIAL and stores the results in memory

V4 = End

FIG.

Y4 = Still image folder

Z4 = Motion picture folder

A5 = Sound folder

B5 = Control folder

C5 = Music folder

D5 = Trace information management file

E5 = Indicates track files names and information files for the content key

F5 = Name 1 ... Name and program name block (for one byte code)

G5 = Program name data according to code

H5 = Name 2 ... Name and program name block (for two-byte code)

I5 = Program name data according to MS-JIS ... etc

J5 = Full copy of the BACK-UP trace information management file TRKLIST.MSF

K5 = Artist name, ISRC code, time stamp, still image data, etc. It contains additional information of varying type, such as

L5 = Program data file

M5 = Root .4 ·

N5 = Sound

FIG.

05 = Trace information management file

P5 = Revision

FIGURE 28

R5 = Name and program name block for one byte code

FIG.

T5 = Name and program name block for two-byte code FIGURE 30 U5 = Audio unit

V5 = Core

FIGURE 31

Y5 = Additional information management file

Z5 = Dataset

A6 = Highest value

FIGURE 32

B6 = Additional information data structure

C6 = Variable length data

FIGURE 33

101 = Trace and collect the trace information management file

Obtains the total number of tracks and the number of tracks for each track Obtains TRKLIST

Data name 1 Data name 2

102 = The call audio file collects A3D001 data Collects A30002 data Collects A3D00m data

D6 = Compensation HDD inside

103 = Restarts MS

Copy trace management file and audio tracks of all tracks from HDD to MS

E6 = Compensating MS

FIG. 34

F6 = Relationship between data bytes and transmission rates

G6 = Transmission ratio

H6 = Seconds

I6 = Stero (minutes)

J6 = Mono (minutes)

K6 = Number of bytes remaining

L6 = Number of remaining clusters

M6 = Minutes

<img file="TR200000809A2_D0001.tif" />