JP2003162300A - Device for reproducing semiconductor memory card, computer-readable recording medium, and reproducing method therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a semiconductor memory card capable of avoiding reproduction of a duplicated part without newly specifying a reproducing position in the device, when reproducing a music album, which has been reproduced by one reproducing device, by another reproducing device. <P>SOLUTION: A plurality of AOBs constituting a plurality of tracks, and PlayList information presenting the order of reproduction about these tracks are stored in the semiconductor memory card, and the PlayList<SB>-</SB>Number showing the PlayList information which has been used at the preceding reproduction, the Track<SB>-</SB>Number showing the reproduced tracks, and the Playback<SB>-</SB>Time showing the preceding positions of reproduction are stored therein as resume information (PLMG<SB>-</SB>RSM<SB>-</SB>PL). <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a reproducing device for a semiconductor memory card for storing audio data and control data, a computer-readable recording medium, and a reproducing method, and more particularly to a content distribution service such as electronic music distribution. The present invention relates to improvement in storing audio data and control data distributed as contents.

[0002]

2. Description of the Related Art Electronic music distribution, which makes it possible to purchase music contents on the Internet, can be a trigger for activating the music market, and the infrastructure for realizing it is being steadily improved. is there. The above-mentioned semiconductor memory card is a portable recording medium suitable for storing music contents purchased in electronic music distribution and carrying the music contents, and it is expected that the demand thereof will increase dramatically in the future.

A flash ATA is used as a semiconductor memory card.
There are various types such as a card and a compact flash (registered trademark) card. In addition to a semiconductor memory card, a disc type such as a CD-R or a mini disc (MD) can be used for recording music contents. It is recognized by many consumers and traders that there are various kinds of recording media for storing music contents, but where to reproduce the music contents (songs) recorded on those recording media. There are not so many types of methods for designating the so-called "playback location", and there are several patterns.

A typical example of a method of designating a reproduction portion in the case of reproducing a music album including a plurality of music contents (songs) is given as an example. 1), which accepts the input of the music number from the operator and starts the reproduction from the music numbered with the music number (2). Analyzing the method of specifying the playback points of (1) to (2), in the method of specifying (1), the playback is always started from the same song, and the user plays the songs included in the music album in the same order from the beginning. I will listen. Here, after listening to the music album halfway, when the playback is stopped and the music album is played again, the playback device starts playback from the first song of the music album, so the operator once You have to put up with the songs you listen to and keep listening.

In the designation method (2), since the reproduction is started from the music designated by the operator, when the music album is listened to halfway and then the reproduction is stopped and the music album is reproduced again, By inputting the song number of the song to be played next into the playback device, the music album can be played from that song onward, and there is no need to listen to the song once listened to. However, in this case, the user has to perform an operation such as inputting a song number, which causes an extra trouble for the user. Also, if the operator does not remember exactly which song is in which number, it is intended that the song to be listened to is specified, but a different song is specified and the wrong song is played. It is also possible.

As described above, in the designation methods (1) and (2), when the music album is partially listened to and then the reproduction is resumed,
In this respect, it is hard to say that the song is user-friendly because it is necessary to put up with the song once listened to or to input the song number. (1) The method of specifying the playback position other than (2) is to specify the song to start playing and the playback time point in that song by forward search playback or backward search playback (3), Accepts song specification using the jog dial etc. and specification of playback start time from the operator,
There are things such as starting playback from the specified song and playback start time (4), etc., but in terms of letting the operator specify the position where the playback is completed so far, these are
It can be said that it has the same problem as the designation method (2). As a more user-friendly method of designating a reproducing portion as compared with the designation methods (1) to (4), there is a method of designating a reproducing method in a current mini-disc reproducing apparatus (generally called an MD player).

According to this designating method, when a mini disk (MD) is reproduced and the reproduction is stopped, the resume information indicating the stop point is stored in a non-volatile memory built in the MD player, If the reproduction of the MD is instructed again, the reproduction of the music album recorded in the MD is restarted according to the resume information.
With this designation method, the resume information is not erased and maintained even after the power of the MD player is turned off. Therefore, after listening to the music album halfway, the reproduction is stopped, and even when the power is turned off, the music album can be reproduced immediately after the position where the music album was reproduced last time.
At this time, unlike the specification method (1), the playback from the beginning of the music album is not repeated many times, and unlike the specification method (2), there is no need to bother entering the song number. Therefore, it is suitable for viewing a music album including a plurality of songs. Prior art relating to the reproduction of music albums includes those described in Non-Patent Documents 1 and 2 below.

[Non-Patent Document 1] Japanese Unexamined Patent Publication No. 10-097766

[Non-Patent Document 2] DOS / V magazine, March 1998, SoftBank Publishing, P334-P339

[0008]

By the way, in the case of MD, the resume information indicating how much has been played is stored in the hardware of the MD player, so the MD is taken out from the MD player and loaded into another MD player. If this is the case, the other MD player is subject to the M
There is a problem that it plays from the first song of D.
Specifically, after listening to the music album halfway on one playback device, playback is stopped, and on another playback device,
When the music album is played back, the other playback device does not store the resume information indicating the previous stop position, so the playback starts from the first song of the music album, and the operator once You have to put up with the songs you listen to and keep listening.

[0009] However, if it is rare to listen to a music album listened on one playback device on another playback device,
It is thought that the above-mentioned replay of the reproduction is unlikely to occur, and it seems that this will not be a problem,
When the music album to be recorded on the recording medium is a music album distributed by electronic music distribution, there is a possibility that a music album listened to by one reproduction device is frequently heard by another reproduction device.

Delivery of a music album in electronic music distribution is realized by a computer owned by a consumer downloading the music album from a server computer of a music company. When the music album is downloaded in this way, the operator may play the music album on the general-purpose personal computer. This is because the general-purpose personal computer in recent years has a proper music content reproducing ability, and the operator tries to listen to the purchased music album by using this. It is assumed that after the music album is played back on the general-purpose personal computer in this way, the same music album is recorded on the recording medium, and the music album is played back by the portable playback device.

In this case, in the general-purpose personal computer, since the portable playback device cannot know how much the music album has been played back, the portable playback device plays the same music album from the beginning. In this way, if the music album was played from the beginning, you would have to listen to the music from the music album once heard on a general-purpose personal computer again, and the same song would be played repeatedly.
The operator gets tired of it.

As the recording medium becomes smaller, lighter, and has a larger capacity, it will be possible to record a music album consisting of a huge number of songs on one recording medium and reproduce it by various reproducing devices. It is thought to be done frequently. In this case, it is possible that a music album that is listened to by one playback device may be listened to by another playback device frequently (although after playing the music album on one playback device, it is played on another playback device). It is not preferable for the operator to play a music album containing a huge number of songs each time from the beginning.

A first object of the present invention is to reproduce a music album listened to by one reproducing apparatus by another reproducing apparatus,
It is an object of the present invention to provide a reproducing apparatus capable of avoiding reproduction of an overlapping portion in the apparatus without having to specify a reproducing position again. A second object of the present invention is to provide a playback device which, when playing a music album listened to by one playback device by another playback device, causes the playback device to play back the content once played back without duplicating it. It is to be.

[0014]

[Means for Solving the Problems] The first and second objects are to operate a first reproduction operation that specifies any audio object or a second reproduction operation that does not specify any audio object. Receiving means for accepting the first reproduction operation from the user, reproducing the designated audio object in the audio sequence when the first reproduction operation is received, and reading the resume information from the semiconductor memory card when receiving the second reproduction operation, Reproduction means for restarting the reproduction of the audio sequence from the restart position indicated by the first position information or the second position information;
Storage means for storing a flag indicating whether the position information is used or the first position information is used, and the reproducing means, if the flag indicates that the first position information is used, the first position information When the flag indicates that the second position information is used, the reproduction device is characterized in that the reproduction is performed based on the second position information.

[0015]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of a semiconductor memory card (flash memory card) will be described with reference to the drawings. In addition, each subsequent sentence is attached with a classification number having the following system at the beginning of the sentence.

The number of digits of the {x1-x2_x3-x4} classification number means the hierarchical depth of the item. Specifically, x1
Is the figure number quoted in the description. The figures attached to this specification are numbered according to the order in which they are cited in the specification, and therefore the order of the figure numbers is almost the same as the order of description. x2 indicates the order of description when the description is given by citing the diagram shown in x1. x3 indicates the drawing number of the explanatory diagram when the explanatory diagram is cited in order to explain the components of x2 in more detail, and x4 indicates the order of the explanation when citing and explaining the diagram shown in x3 Indicates.

(First Embodiment) {1-1_2} External Shape of Flash Memory Card 31 First, the external shape of the flash memory card 31 will be described. FIG. 1 is a diagram showing the shape of the flash memory card 31 when viewed from the top, and FIG. 2 is a diagram showing the structure when the flash memory card 31 is viewed from the bottom. As shown in FIGS. 1 and 2, the size of the flash memory card 31 is about 32.0 mm in length and about 24.0 in width.
The thickness is about 2.0 mm and the thickness is about 2.0 mm, which is a size (stamp size) that can be held with a fingertip. Nine connectors are provided on the bottom surface for connection with devices, and on the side surface, there is a protect switch 32 that allows the operator to set whether to allow or prohibit overwriting of stored contents. Has been.

{3-1} Physical Structure of Flash Memory Card 31 FIG. 3 shows the semiconductor memory card according to the present embodiment (hereinafter,
FIG. 3 is a diagram showing a hierarchical structure of a flash memory card 31). As shown in the figure, the hierarchical structure of the flash memory card 31 is the same as the hierarchical structure of a DVD (Digital Video Disc) in that it has a physical layer, a file system layer, and an application layer, but the logical structure of each layer is The physical structure is very different.

{3-2} Physical Structure of Flash Memory Card 31 First, the physical layer of the flash memory card 31 will be described. The flash memory is composed of a plurality of sectors, and each sector stores 512 bytes of digital data. For example, in case of 64MByte type flash memory card 31, its memory capacity is 67108864 (= 64 × 1024 × 1024)
The number of valid sectors at this time is 131072 (= 6710
8864/512). Furthermore, if the number of alternative sectors for error is subtracted from this valid sector, the number of remaining valid sectors will be
It will be 128,000, and various data will be recorded here.

{3-2_4A-1} Three areas in the physical layer The area composed of these effective sectors is shown in FIG. 4 (a).
Three areas are provided. FIG. 4A is a diagram showing a “system area”, a “protected area”, and a “user data area” provided in the physical layer of the flash memory card 31. Hereinafter, these three areas will be described.

The "user data area" is an area in which a device connected to the flash memory card 31 can freely write various data and can freely read the data, and its internal area is defined by a file system. It is managed. The “system area” is an area in which a media ID having a unique value for each flash memory card 31 is stored. The user data area is writable, whereas the system area is read-only and the media ID stored therein cannot be rewritten.

The "protect area" is an area in which data can be written, like the user data area. The difference from the user data area is that data can be freely read and written in the user data area, whereas in the protected area, the device connected to the flash memory card 31 is
Reading and writing can be performed only when the flash memory card 31 confirms mutual validity, that is, only when mutual authentication between the flash memory card 31 and a device connected to the flash memory card 31 is successful. This is a possible point.

{3-2_4A-2} Usage of three areas in the physical layer When a device connected to the flash memory card 31 writes data in the flash memory card 31, depending on whether the copyright protection of the data is necessary or not. , These three areas are utilized. Here, when writing data that requires copyright protection to the flash memory card 31, the data is stored in the user data area after being encrypted using a predetermined encryption key (called a FileKey). This File
The Key can be freely set by the copyright holder, and the copyright of the data is protected by this alone, but the FileKey itself used for this encryption is also encrypted for the sake of completeness. When encrypting the FileKey itself, what is used as a key is an arbitrary value obtained by applying the media ID stored in the system area to a predetermined arithmetic expression, and the protected area is the arbitrary value. Store the FileKey encrypted using. Data that requires copyright protection is encrypted using a specified FileKey, and this FileKey itself is also encrypted using a value based on the media ID. Infringement becomes extremely difficult.

{3-2_4B-1} Outline of File System The configuration of the physical layer of the flash memory card 31 is as described above, and it can be seen that the copyright protection is improved. Next, the configuration of the file system layer existing on this physical layer will be described. The file system layer of the DVD is a UDF (universal disk format) type file system, whereas the file system layer of the flash memory card 31 is a FAT type file system (FAT: FAT: FAT: FAT: FAT: FAT).
ile Allocation Table, ISO / IEC 9293), which is different from DVD.

FIG. 4B is a diagram showing the structure of the protect area and the user data area in the file system layer. In FIG. 4B, the protect area and the user data area in the file system include a “partition boot sector”, a “file allocation table (FAT)”, a “root directory entry”, and
It is also apparent from this figure that the data area is included and both the protect area and the user data area have the same structure. FIG. 5 is a diagram showing the details of these file system configurations. Hereinafter, the configuration of the user data area will be described with reference to FIGS. 4 and 5.

{3-2_4B-2} partition boot sector "partition boot sector" is a flash memory card 31 loaded in a general-purpose personal computer,
When the flash memory card 31 is assigned to the boot disk of the operating system of the general-purpose personal computer, this is a sector in which the contents that the general-purpose personal computer should refer to at the time of booting are described.

{3-2_4B-3_5} data area The "data area" is an area that is accessed by the device connected to the flash memory card 31 with the cluster as the minimum unit. The sector size of the flash memory card 31 is 512 bytes, while the cluster size is 16 Kbytes, so 3 in the file system layer.
Data is read and written in units of two sectors. The reason for setting the cluster size to 16K bytes is as follows. That is, when writing data to the flash memory card 31,
The data stored in must be erased once before writing data. In the flash memory card 31, the size in which such data can be erased is 16 Kbytes. Therefore, by setting the cluster size to this erasable size,
Data writing is performed appropriately. Figure 5
The dashed lead line ff2 in (1) indicates a plurality of clusters 002, 003, 004, 005 ... Included in the data area. In the figure, the numbers 002, 003, 004, 005, 006, 007, 008 ... Show the 3-digit hexadecimal notation cluster numbers assigned to identify each cluster. Since the access to the data area is performed with the cluster as the minimum unit, the internal position of the data area is designated using these cluster numbers.

{3-2_4B-4_5} File allocation table "File allocation table" is ISO / IEC 9293
It has a file system structure conforming to
It consists of a FAT value. Each FAT value is associated with each cluster, and when the corresponding cluster is read, it indicates which cluster should be read next. The broken line ff1 in FIG. 5 indicates a plurality of FAT values 002,003,004,005, ... Included in the file allocation table. The numerical value “002,003,004,005 ...” given to this FAT value indicates which cluster each FAT value is associated with, that is, each FAT value.
Indicates the cluster number of the cluster with which the value is associated.

{3-2_4B-5_5-1} Root directory entry "Root directory entry" is information indicating what kind of file exists in the root directory. Specifically, the root directory entry includes the "file name" of the existing file, the "extension" of the file, the "file attribute", the "update time and date" of the file, and the file "The first cluster number of the file" in which the beginning part of is stored is described.

{3-2_4B-5_5-2} Directory Entry of Subdirectory Information about files in the root directory is
Although described in this root directory entry, information about the subdirectory is not described in this root directory entry. Directory entries for subdirectories are created in the data area. The SD_Audio directory entry described in the data area of FIG. 5 is an example of a directory entry for a subdirectory, and this SD_Audio directory entry is similar to the root directory entry as the “file name” of a file existing in that subdirectory. The "extension" of the file, the "file attribute", the "update time and date" of the file, and the "file first cluster number" in which the head of the file is stored are described.

{3-2_4B-5_6-1} AOB file storage method When the file AOB001.SA1 is stored in the SD_Audio directory, how AOB001.SA1 is stored, that is, the file storage method An example will be described with reference to FIG. Since the minimum access unit of the data area is the cluster as described above, AOB001.SA1 must be stored in the data area with the cluster size as the minimum unit. AOB001.SA1 is first divided into cluster size,
Written to each cluster. FIG. 6 is a diagram assuming that AOB001.SA1 is divided into five parts according to the cluster size, and each divided part is stored in the clusters 003,004,005,00A, 00C.

{3-2_4B-5_7-1} When the AOB file storage method AOB001.SA1 is divided and stored, the directory entry and the file allocation table must be set as shown in FIG. FIG. 7 is a diagram showing a setting example of a directory entry and a file allocation table when AOB001.SA1 is recorded in a plurality of clusters. In this figure, when the head part of AOB001.SA1 is recorded in the cluster 003, the "first cluster number" in the SD_Audio directory entry contains the cluster number 003 of the cluster in which the head part is stored. . After that, it can be seen that the subsequent portion of AOB001.SA1 is stored in the cluster 004 and the cluster 005. FAT value 003 (004) corresponds to cluster 003 that stores the first part of AOB001.SA1.
This FAT value indicates the cluster 004 that stores the subsequent portion of the AOB file. In addition, clusters 004 and 005 that store the parts that follow it have a FAT value of 00.
4 (005) and FAT value 005 (00A) correspond, but the FAT value of this indicates the cluster 005,00A storing the next succeeding part of the AOB file.

If the cluster numbers described in these FAT values are sequentially read as shown by arrows fk1, fk2, fk3, fk4, fk5 ..., All the divided parts of AOB001.SA1 can be read. . From the above description, it can be seen that the data area of the flash memory card 31 is accessed with the cluster as the minimum unit, and the FAT value is associated with each cluster. A cluster that stores the end of the AOB file (in the example of FIG. 7, cluster 00C)
In the FAT value associated with, the cluster number "FFF" indicating that the cluster stores the last part of the file is described.

The description of the file system of the flash memory card 31 of the present invention is completed above.
The configuration of the application layer existing on the above-mentioned file system will be described. {3-3} Outline of application layer in flash memory card 31 Outline of application layer in flash memory card 31 is as follows.
As described in FIG. As indicated by the broken line PN1 in FIG. 3, the application layer in the flash memory card 31 is composed of presentation data and navigation data for controlling reproduction of the presentation data.

As shown by the broken line PN2 in the figure, the presentation data includes an audio object group (AOB group) obtained by encoding audio data such as music, and the navigation data is the playlist manager. (PlaylistManager (PLMG)),
Includes Track Manager (TKMG). {3-3_8A, B-1} directory structure FIGS. 8 (a) and 8 (b) show what kind of data is stored in the user data area and protect area in the file system layer when these two data are stored in the application layer. It is a figure which shows a directory is formed and what kind of file is created under the said directory. "SD_AUDIO.PLM" and "SD_AUDIO.TKM" in this figure are files containing navigation data such as playlist manager (PlaylistManager (PLMG)) and track manager (Track Manager (TKMG)).
1 ”“ AOB002.SA1 ”“ AOB003.SA1 ”“ AOB004.SA1 ”
Is a file that stores audio objects that are presentation data (hereinafter referred to as an AOB file).

The extension "SA" in "AOB0xx.SA1" is
Abbreviation of "Secure Audio", and these stored contents indicate that there is a need for copyright protection (note that only eight AOB files are described in Fig. 8 (a). This is just an example, the SD_Audio directory can store up to 999 AOB files.) When the presentation data requires copyright protection as described above, a subdirectory named SD_Audio directory is provided in the protected area, and an encryption key storage file AOBSA1.KEY is created under the SD_Audio directory. FIG. 8B is a diagram showing the encryption key storage file AOBSA1.KEY stored under SD_Audio. The encryption key storage file AOBSA1.KEY contains FileKeys # 1 to # 8, which are encryption key strings formed by arranging multiple encryption keys FileKey in a predetermined order.
Is stored.

In electronic music distribution, the server computer of the music company uses SD_Audio shown in FIGS. 8 (a) and 8 (b).
If the consumer holds a directory and a purchase request for the music content is issued by the consumer, the SD_Audio directory is compressed and encrypted, and then the SD_Audio directory owned by the consumer who issued the purchase request is sent via the public network. To send. When the computer owned by the consumer receives this SD_Audio directory, it decrypts this directory and decompresses it to obtain an SD_Audio directory. Including all networks that are open to the public, such as wireless communication networks typified by mobile phones). The AOB file may be downloaded from the server computer of the music company, and the computer owned by the consumer may create the SD_Audio directory shown in FIGS. 8A and 8B in the flash memory card 31.

Correspondence between {3-3_9-1} AOBSA1.KEY and AOB File FIG. 9 is a diagram showing the correspondence between AOBSA1.KEY and SD file under SD_Audio. In this figure, the Fi used to encrypt the encrypted file in the user data area
leKey is stored in the encryption key storage file corresponding to the protected area.

The encrypted AOB file and the encryption key storage file have a correspondence relationship based on the following fixed rules (1), (2) and (3). (1) The encryption key storage file is placed in the same directory name as the directory in which the encrypted file is stored. Since the AOB file is placed in the SD_Audio directory and the encryption key storage file is also placed in the SD_Audio directory in the user data area of FIG. 9, it can be seen that the files are arranged according to this rule. ..

(2) The encryption key storage file is given a file name in which the first three characters of the file name of the AOB file in the data area are combined with a predetermined extension ".key". If the file name of the AOB file is "AOB001.SA1", the encryption key storage file will contain the first three characters "AOB", "SA1", and the extension ".key" in the encryption key storage file, as indicated by arrows nk1 and nk2. It can be seen that the file name "AOBSA1.KEY" consisting of "" is added.

(3) In the file name of the AOB file, the serial number indicating the position of the Filekey corresponding to the audio object in the encryption key sequence in the encryption key storage file, that is, the order of the corresponding FileKey. A number is assigned. “File Key Entry # 1, # 2, # 3 ... # 8” in the encryption key storage file in FIG. 9 indicates the start position of the area in which each File Key in the encryption key storage file is stored. . On the other hand, the file name of the AOB file is "001", "00
Serial numbers such as 2 "," 003 ", and" 004 "are assigned. The serial number in these AOB files means the position of the corresponding FileKey in the encryption key sequence, so each AOB file Fil used when encrypting the file
eKey has the same serial number as “File Key Entr
y'will exist. Arrows AK1, AK2, AK3 in Fig. 9
Indicates the correspondence between the AOB file and the FileKey. That is,
AOB001.SA1 in the user data area is "File Key Ent
It corresponds to the FileKey stored in "ry # 1", and AOB00
2.SA1 is the FileKe stored in “FileKey Entry # 2” or later.
y and AOB003.SA1 indicate that they correspond to File Keys stored after “File Key Entry # 3”. As can be seen from (3) above, the FileKey used to encrypt the AOB file
Is different for each file, and they are the same as the serial numbers such as "001", "002", "003", "004" embedded in the file name and "File Key Entry ”. Each AOB file is encrypted using a different FileKey, so even if the encryption key of a specific AOB file is exposed,
Other AOB files cannot be decrypted using the exposed FileKey. This will minimize the damage if the FileKey is exposed when the AOB file is encrypted.

{3-3_10-1} Internal Structure of AOB File Next, the internal structure of the AOB file will be described. Figure 1
0 is a diagram hierarchically showing the data structure of the AOB file. The first row of this figure shows an AOB file, and the second row shows an AOB. The third row shows AOB_BLOCK, the fourth row shows AOB_ELEMENT, and the fifth row shows AOB_FRAME.

"AOB_FRAME" in the fifth row of FIG.
Is the smallest unit that composes AOB, and includes ADTS header and ADT
S (Audio Data Transport Stream) format audio data. Audio data in ADTS format is MPEG
16K encoded with 2-AAC [Low Complexity Profile]
Stream data that is played back at a transmission rate of bps to 144 Kbps (Note that PCs recorded on existing compact discs
Since the transmission speed of M data is 1.5 Mbps, it can be seen that it is much lower than that of PCM data. ). These AOB_
The data structure of the FRAME sequence is the same as the audio frame sequence included in the audio data transport distributed by electronic music distribution. That is, the audio data transport stream to be stored as the AOB_FRAME sequence is encoded by MPEG2-ACC, further encrypted, transmitted over the public network, and transmitted to the consumer. The AOB file stores the audio data transport stream thus transmitted by dividing it into AOB_FRAME sequences.

{3-3_10-1_11} About MPEG2-AAC For details of MPEG2-AAC, see ISO / IEC 13818-7: 1997 (E).
Information technology-Generic coding of moving
pictures and associated audio information- Part7
Refer to Advanced Audio Coding (AAC). It should be noted here that the AOB is compressed by the MPEG2-AAC method applied by limiting the parameter table described in ISO / IEC13818-7 as shown in FIG. 11 (a). . Figure 1
1 (a) is a diagram showing a parameter table described in ISO / IEC13818-7, in which a Parameter column, a Value column, and a Comm
It consists of a comment field indicating the contents of the ent field.

The parameter column "profile" is defined in ISO / IEC 138
Indicates that the LC-profile restrictions specified in 38-7 are applied. Parameter field "sampling_frequency # ind
ex ”is“ 48kHz, 44.1kHz, 32kHz, 24kHz, 22.05kHZ, 16kH
z ”indicates that the sampling frequency is applied. Parameter field “number_of_data_block_in_fram
e ”indicates that it is set to 1header / 1raw_data_block.

Although AOB_FRAME has been described as being encoded in the MPEG-AAC system, AOB_FRAME is MPE.
G-Layer3 (MP3) method, Windows (registered trademark) Media Audio
(It may be encoded by another encoding method such as the WMA method. At this time, the parameter tables shown in FIGS. 11B and 11C are used instead of the parameters shown in FIG. 11A. Must be used.

{3-3_10-2_12} Structure of AOB_FRAME "AOB_FRAME" includes audio data encoded under the above restrictions. However, the data length of the audio data included in AOB_FRAME is 20 mm at the reproduction time. It's just data in seconds. However, since the MPEG2-AAC method is a variable length coding method, the data length of audio data included in each AOB_FRAME differs for each AOB_FRAME. Hereinafter, the details of the configuration of AOB_FRAME will be described with reference to FIG. The first row of this figure is AOB_FRAME
And the second row shows how each part of AOB_FRAME is encrypted. By referring to the second row, it can be seen that the ADTS header is not encrypted, that is, is not encrypted. Also, the audio data includes both an encrypted part and a non-encrypted part. The encrypted part consists of multiple 8-byte encrypted data. 8 bytes of encrypted data is 6
It is generated by encrypting 4-bit original data using a 56-bit FileKey. The non-encrypted part is left unencrypted because it is less than 64 bits when the encryption is performed in 64-bit units.

The third level is a diagram showing the contents of the ADTS header which is the non-encrypted part. The ADTS header is 7 bytes and contains a 12-bit sync word (set to FFF),
The data length of audio data included in the same AOB_FRAME and the sampling frequency when encoding the audio data are described. {3-3_10-3_13} Setting the byte length of AOB_FRAME Fig. 13 shows the AOB_FR for each of the three AOB_FRAMEs.
It is a figure which shows how the byte length of the audio data in AME is set. In this figure, AOB_FRAM
Audio data # 1 included in E # 1 has a data length of x1, AOB
The data length of audio data # 2 included in _FRAME # 2 is x
2.The data length of audio data # 3 included in AOB_FRAME # 3 is x3.If the data lengths are different from each other, such as x1, x2, x3, the data length will be written Data length x2 is described in the ADTS header included in AOB_FRAME # 2, and data length x3 is described in the ADTS header included in AOB_FRAME # 3. The audio data itself is encrypted, but the ADTS header itself is not encrypted, so if you read the data length of the audio data from the ADTS header in each AOB_FRAME, you can determine where the subsequent AOB_FRAME exists. You can get it. This is the end of the description of AOB_FRAME.

{3-3_10-4} AOB_ELEMENT Next, in FIG. 10, the AOB_ELEMENT located at the fourth level
Will be described. "AOB_ELEMENT" is a set of consecutive AOB_FRAMEs. Where how many AOBs
Whether _FRAME is included in AOB_ELEMENT changes according to the setting of sampling_frequency_index shown in FIG. 11A and the encoding method. That is, AOB included in AOB_ELEMENT
The number of _FRAME is the AOB_FRAME included in the AOB_ELEMENT.
The playback time is set to about 2 seconds, and the number of playbacks varies depending on the sampling frequency and the encoding method.

AO included in {3-3_10-5_14} AOB_ELEMENT
B_FRAME Number FIG. 14 is a diagram showing the correspondence between sampling_frequency and the number of AOB_FRAME included in AOB_ELEMENT. In the figure, N indicates the reproduction period of AOB_ELEMENT in seconds, and is "2" if the encoding method is MPEG-AAC. If sampling_frequency is 48kHz, AOB_ELEMENT
The number of frames included in is 94 (= 47 × 2), and sampli
When ng_frequency is 44.1kHz, the number of frames included in AOB_ELEMENT is 86 (= 43 × 2) and sampling_frequency is
At 32kHz, the number of frames included in AOB_ELEMENT is
If 64 (= 32 × 2) and sampling_frequency is 24 kHz, the number of frames is 48 (= 24 × 2) and sampling_frequency is
When it is 22.05kHz, the number of frames included in AOB_ELEMENT is 44 (= 22 × 2), and when sampling_frequency is 16kHz, the number of frames included in AOB_ELEMENT is 32 (= 16 × 2).
It becomes an individual. However, if you edit the AOB by splitting it, A
The number of AOB_FRAME of the first and last AOB_ELEMENT of OB is shown in FIG.
May be less than the number of.

Although no special information such as a header is added to AOB_ELEMENT, the data length thereof is shown in the time search table instead. {3-3_10-6_15} Example of time length of AOB_ELEMENT and AOB_FRAME FIG. 15 is a diagram showing an example of time length of AOB_ELEMENT and AOB_FRAME. The first row of this figure shows multiple AOB_BL
The OCK sequence, and the second row shows the sequence of multiple AOB_ELEMENTs. The third row shows the arrangement of multiple AOB_FRAMEs.

Referring to this figure, AOB_ELEMENT is about 2.0.
It corresponds to the playback time length of seconds, and AOB_FRAME in this figure
It can be seen that corresponds to a playback time length of 20 msec. AO
The character string "TMSRT_entry" attached to each B_ELEMENT indicates that the data length of each AOB_ELEMENT is described in the time search table. TM like this
By performing forward search reproduction and reverse search reproduction by referring to SRT_entry, it is possible to realize intermittent reproduction of skipping 2.0 seconds and reproducing for 240 milliseconds.

{3-3_10-7} About AOB_BLOCK Above, the explanation about AOB_ELEMENT is finished, and then AOB_E
A higher order of LEMENT, that is, AOB_BLOCK located in the third row in the diagram showing the data structure of the AOB file in FIG. 10 will be described. "AOB_BLOCK" is a valid AOB_ELEMENT
This is an area consisting of 1 and exists in the AOB file. A
OB_ELEMENT corresponds to a playback time of 2 seconds, while AOB_BLOCK corresponds to a playback time of up to 8.4 minutes. The reason that each AOB is limited to the playback time of 8.4 minutes is that the size of the time search table is suppressed to 504 bytes or less by limiting the number of AOB_ELEMENT included in AOB_BLOCK.

{3-3_10-8} Suppression of Time Search Table Hereinafter, the reason why the time search table can be suppressed by limiting the reproduction time will be described in detail. When performing forward search playback and reverse search playback, "2 second skip 240 millisecond playback" is performed in which reading for 2 seconds is skipped and playback is performed for 240 milliseconds. In this way, when skipping the time length of 2 seconds, as a rule, AOB_FRAM
It is enough to refer to the data length shown in the ADTS header of E in sequence, but in that case, 100 (= 2 seconds / 20 milliseconds) AOB_FRAME to skip the time interval of 2 seconds.
Must be sequentially detected, which imposes an extra processing load on the playback device. In order to reduce such processing load, the read destination address at the interval of 2 seconds is described in the time search table, and when the forward search reproduction and the backward search reproduction are instructed, the reproducing device refers to this. Good. That is,
The time search table contains information for calculating the read destination address 2 seconds ahead and 4 seconds ahead, specifically, each AOB_ELEMEN
The data length for T is described in advance, and the playback device may perform forward search playback-reverse search playback with reference to this. Consider how the data length corresponding to 2 seconds becomes. The bit rate during playback of audio data is 16 Kbps to 144 Kbps as described above.
, The data length that is played back every 2 seconds is 4
Kbyte (= 16Kbps x 2/8) to 36Kbyte (= 144Kbps x 2/8).

If the data length per 2 seconds is 4 Kbytes to 36 Kbytes, the data length of the entry in the time search table for describing the data length of the audio data requires 2 bytes (16 bits). This is because if you assign a 16-bit length to an entry, a numerical value of 0 to 64 KByte can be described. On the other hand, considering the case where the total data size of the time search table is limited to, for example, 504 bytes (this is the data size of TKTMSRT described later), the entry to be provided in this time search table is 252 (= 504 / 2) Must be limited to As described above, since the entry is provided every 2 seconds, the reproduction time corresponding to 252 entries is 504 seconds (= 2 seconds × 252), which is 8 minutes and 24 seconds (= 8.4 minutes). By limiting the playback time in AOB_BLOCK to 8.4 minutes or less, the data size of the time search table can be set to 504 bytes or less.

Regarding {3-3_10-9} AOB Above, AOB_BLOCK has been described, and then AOB will be described. The AOB located in the second row of FIG. 10 is the AOB.
It is an area with invalid area before and after _BLOCK, and AOB
There is one in the file. This invalid area is the AO
This area is stored in the same cluster as B_BLOCK and is read and written together with the AOB_BLOCK. In the AOB, which part of the AOB_BLOCK corresponds to is specified by BIT included in the navigation data (details thereof will be described later).

From the above, it becomes clear what kind of data is stored in each AOB file. Then, in FIG.
The following describes what kind of content is reproduced by continuously reading out the AOB and AOB_BLOCK included in the eight AOB files shown in FIG. {3-3_10-10_16} Figure 16 shows that each AOB and AOB_BLOCK recorded in the AOB file are played back in succession.
It indicates what kind of reproduction content is reproduced. The first row shows eight AOB files in the user data area, and the second row shows the eight AOB files recorded in each AOB file.
Indicates AOB. The third row shows eight AOB_BLOCKs included in each AOB.

The fifth row shows a title composed of five content parts. Five content sections are SongA and Song
Each of the five songs B, SongC, SongD, and SongE is shown, and the title shows a music album composed of these five songs (contents). Dashed line AS1, AS2, AS3 ... AS7, AS8
Shows the correspondence between the divided parts of the music album and AOB_BLOCK, and the fourth row shows in what unit the fifth album music album is divided.

Referring to these broken lines, the AOB_Block included in each AOB # 1 is the song played at a time of 6.1 minutes.
(SongA), AOB_Block included in each AOB # 2 is a song played in 3.3 minutes (SongB), AOB_Block included in each AOB # 3 is a song played in 5.5 minutes (Son
gC). As above, AOB001.SA1 ~ AOB003.SA1
You can see that each corresponds to an independent song. The sixth row shows a track sequence consisting of Tracks A to E. These TrackA to E are SongA, SongB, SongC,
There is a one-to-one correspondence with each of the five songs, SongD and SongE, and they are treated as one independent playback unit.

On the other hand, AOB # 4 is the head portion of the song (Song D) reproduced at a time of 30.6 minutes, and is reproduced at a reproduction time of 8.4 minutes. AOB_BLOC included in AOB # 5 and AOB # 6
K is the middle part of SongD, with a playback time of 8.4 minutes, AOB
AOB_BLOCK included in # 7 is the end part of SongD, and 5.
It is played with a playback time of 4 minutes. Thus, a song with a play time of 30.6 minutes is (8.4 minutes + 8.4 minutes + 8.4 minutes + 5.4 minutes
You can see that each AOB is divided by the unit of minutes. As can be understood from this figure, it can be seen that all the songs included in the AOB file are recorded within the playback time of 8.4 minutes.

From the above description, it became clear that by limiting the reproduction time length of the AOB, the data size of the time search table associated with each AOB is also limited. Next, the navigation data including this time search table will be described. {3-3_8A, B-2} Navigation data is "SD_Audio.PL
As mentioned above, it consists of two files, "M" and "SD_Audio.TKM". File "SD_Audio.PLM"
Includes a playlist manager, and the file "SD_Audio.TKM" is a track manager.
(TrackManager) is included.

As described in the description of the presentation data, the plurality of AOB files record the encoded AOBs, but how long the reproduction time of these AOBs is and how long each AOB is There is no description of what the song name is and who the composer is. On the other hand, since the plurality of AOBs are only recorded in the plurality of AOB files, there is no description about the order in which they are played. The track manager and playlist manager are provided to notify the playback device of such information.

Here, the track manager shows the correspondence relationship between the AOBs recorded in the AOB file and the tracks, how long the reproduction time of these AOBs is, and what song name each AOB has. And includes a plurality of track management information indicating various information such as who the composer is. A track is a unit of reproduction that is meaningful to the user. When a music work is stored in the flash memory card 31, a track corresponds to a song, and a reading book is stored in the flash memory card 31 ( A reading book is not a book but a document work represented by a reading voice.) If it is a book genre, a track corresponds to a chapter / section of a sentence. The track manager is provided to manage a plurality of AOBs recorded in a plurality of AOB files as a set of tracks.

A play list defines a plurality of reproduction orders of tracks, and the play list manager includes a plurality of such play lists. Or later,
The track manager will be described with reference to the drawings. {17-1_18} Detailed Configuration of Playlistmanager and TrackManager FIG. 17 shows the Playlistmanager and Track in the embodiment.
FIG. 19 is a diagram in which the configuration of the Manager is detailed step by step.
FIG. 6 is a diagram showing sizes of PlayListManager and TrackManager. That is, in the figure, the logical format located on the right side is a detailed version of the logical format located on the left side. It clarifies which part of the has been refined.

In accordance with such notation, Tr in FIG.
Referring to the configuration of ackManager, TrackManager indicates that Track Information (TKI
Abbreviated) # 1, # 2, # 3, # 4 ・ ・ ・ ・ ・ #n. These TKIs are AO
This is information for managing the AOB recorded in the B file as a track, and corresponds to each AOB file.

Referring to FIG. 17, each TKI has Track_General_Informatin (TKG as shown by a broken line h2.
I), Track_Text that describes text information specific to TKI
_Infomation_Data_Area (TKTXTI_DA), Track_Time_Serch_Table (TKTMSRT) having the role of time search table
You can see that it consists of. Referring to FIG. 18, TKI itself has a fixed size (1024 bytes), and TKGI and TKTXTI_DA
It can be seen that and have a fixed length of 512 bytes in total. TKTMS
RT also has a fixed length of 512 bytes. In TrackManager, up to 999 TKIs can be set.

This TKTMSRT has TMSRT_Header and TMSRT_etry # 1, # 2, # 3 ... # as shown by the broken line h3.
You can see that it consists of n and. Correlation between {17-2_19} TKI, AOB File and AOB FIG. 19 is a diagram showing a correlation between the TKI shown in FIG. 17 and the AOB file and AOB shown in FIG. The square frame in the first row of FIG. 19 is a track sequence consisting of TrackA to E, and the square frame in the second row of FIG. 19 is Trac.
FIG. 16 shows kManager, and the third and fourth stages show the eight AOB files shown in FIG. 8 frames in the 5th row are 8
Shows one AOB. These eight AOB files are the ones that recorded the eight AOBs shown in FIG. 16, and are TrackA and Trac.
It forms a music album that includes kB, TrackC, TrackD, and TrackE. The second row shows eight TKIs. The numbers "1", "2", "3", "4" assigned to these TKIs are serial numbers for identifying each TKI, and each TKI has the same serial number 0
It is associated with the AOB file with 01,002,003,004,005 .... With this in mind, referring to FIG. 19, TKI # 1 corresponds to AOB001.SA1 and TKI # 2 corresponds to AOB0.
It can be seen that 02.SA1 and TKI # 3 correspond to AOB003.SA1 and TKI # 4 corresponds to AOB004.SA1 (arrows TA1, TA2, TA3,
TA4 ... indicates which AOB file each TKI corresponds to. ). In this way, each TKI has a one-to-one correspondence with the AOB recorded in each AOB file.
Information specific to AOB can be written in detail in KI.

{17-3_20} Data structure of TKTMSRT As information unique to the AOB recorded in the AOB file,
First, TKTMSRT will be described. 20 is shown in FIG.
8 is a diagram showing a detailed data structure of TKTMSRT shown in FIG. The time search table header (TMS
The detailed data structure of (RT_Header) is shown. Figure 20
In, the data size of the time search table header is 8 bytes, and TMSRT_ID (0th byte to 1st byte), reserved (2nd byte to 3rd byte), Total T
It has three fields, MSRT_entry_Number (4th to 7th bytes). "TMSRT_ID" contains TMSRT
Describes the ID that can uniquely identify the. 『Total TMSRT_en
“Try Number” describes the total number of TMSRT_entry in the TMSRT.

{17-3_21-1} Specific Example of TKTMSRT Next, the TKTMSRT will be described in more detail. Figure 21
FIG. 6 is a diagram showing an example of TKTMSRT. AOB is shown on the left side of the figure, and TKTMSRT is shown on the right side. AO on the left side of this figure
B consists of a plurality of AOB_ELEMENTs # 1, # 2, # 3 ... In addition, "0""32000""64200""9700" in the figure
Numerical values such as “0”, “1203400”, and “1240000” are occupied areas AR1 of each AOB_ELEMENT from the beginning of AOB_BLOCK included in AOB.
Indicates the relative address up to AR2, AR3, ARn-1, ARn. AOB_ELE
MENT # 2 indicates that it is recorded at a position separated by "32000" from the beginning of AOB_BLOCK. AOB_ELEMENT # 3 is A
OB_BLOCK AOB at a position separated by "64200" from the beginning
_ELEMENT # n-1 indicates that it is recorded at a position separated by "1203400" from the beginning of AOB_BLOCK.

It should be noted that the interval between the head addresses of each occupied area is not a constant value, that is, the occupied area of each AOB_ELEMENT occupies a plurality of clusters of different sizes. The size of each occupied area is different because the code allocation in each AOB_FRAME is variable length. The occupied size of each AOB_ELEMENT is different, so if you jump to the beginning of each AOB_ELEMENT,
It is necessary to instruct the playback device in advance where the OB_ELEMENT exists in the AOB. With such a purpose,
Multiple TMSRT_entry are listed. Arrow RT1, RT2, RT3
..... RTn-1 and RTn are occupied areas AR of each of these AOB_ELEMENT
1, AR2, AR3 ・ ・ ・ ・ ・ ・ ARn-1, ARn and TMSRT_entry # 1, TMSRT_e
ntry # 2, TMSRT_entry # 3 ・ ・ ・ ・ ・ ・ TMSRT_entry # n-1, TMSRT_e
Indicates the correspondence with ntry # n. That is, the size of the occupied area AR1 of AOB_ELEMENT # 1 occupies TMSRT
_entry # 1 describes the size of the occupied areas AR2 and AR3 of AOB_ELEMENT # 2 and AOB_ELEMENT # 3 in TMSRT_entry # 2 and TMSRT_entry # 3.

Here, the occupied area AR1 is from the beginning of the AOB,
Since it occupies the beginning "32000" of AOB_ELEMENT # 2,
TMSRT_entry # 1 is described as 32000 (= 32000-0), occupied area
AR2 is AOB_ELEME from the beginning "32000" of AOB_ELEMENT # 1.
Since it occupies the beginning "64200" of NT # 2, TMSRT_ent
ry # 2 is described as "32200 (= 64200-32000)", occupied area AR3
Is AOB_ELEMENT # 3 from the beginning "64200"
Since it occupies the beginning of 4 to "97000", TMSRT_entry #
3 is "32800 (= 97000-64200)", occupied area ARn-1 is AOB_E
From the beginning "1203400" of LEMENT # n-1 to the beginning "1240000" of AOB_ELEMENT # n, TMSRT_entry # n-1
Is described as "36600 (= 1240000-1203400)".

{17-3_21-2} Reading method of TKTMSRT It is understood that the data size of AOB_ELEMENT is described in the time search table as described above. On the other hand, AO
As mentioned in the description of B_ELEMENT, the data length of each AOB_BLOCK is set so that the playback time is within 8.4 minutes, so the total number of AOB_ELEMENTs contained in one AOB is the specified number.
(252 shown in FIG. 20) or less. AOB_ELEME
Since the number of NTs is suppressed to a predetermined number or less, the total number of TMSRT_entries corresponding to AOB_ELEMENT is also a predetermined number or less, and the data size of TKTMSRT including these is also a predetermined size or less. Since the size of TKTMSRT is suppressed, the playback device can read and use the TKI as follows.

When a certain AOB is read and its reproduction is started, the corresponding TKI is read and stored in the memory. After that, this TKI is stored in the memory while the reproduction of the AOB continues. When the playback of the AOB ends, the AOB that follows it is read, and when the playback is started, the TKI corresponding to it is read and the TKI stored in the memory until that time is newly read. Overwrite with the issued TKI. After that, this TKI is stored in the memory while the reproduction of the AOB continues.

By reading the TKI and storing it in the memory in this way, even if the amount of memory mounted in the reproducing apparatus is small, it is only necessary to read the TKI to perform forward search reproduction and reverse search. Special playback such as playback can be performed. In this embodiment, the data length from the start address of one AOB_ELEMENT to the start address of the next AOB_ELEMENT is described as TMSRT_entry.
The relative address from the beginning of to the beginning of each AOB_ELEMENT may be described.

{17-3_21-3} Identification of Cluster Containing AOB_ELEMENT Finally, referring to TKTMSRT, how to read an arbitrary AOB_ELEMENT will be described. Each AOB_ELEMEN
When referring to TKTMSRT in which the size of T is described and reading AOB_ELEMENT # y located in the y-th position from the beginning in the AOB, find a cluster u that satisfies the following {Equation 1} and offset from the beginning of the cluster u You need to read v and later. {Formula 1} Cluster u = (sum of TMSRT_entry from AOB_ELEMENT # 1 to AOB_ELEMENT # y-1 + DATA_Offset) / cluster size offset v = (sum of TMSRT_entry from AOB_ELEMENT # 1 to AOB_ELEMENT # y-1 + DATA_Offset) mod When the cluster size is c = a mod b, c indicates the remainder when a is divided by b, and DATA_Offset is information described in BIT, which will be described later.

{17-4} About TKTXTI_DA This is the end of the description of the time search map (TKTMSRT). Next, the Track Text Information Data Area (TKTXTI_DA) described in the upper part of TKTMSRT in FIG. 17 will be described. Track Text Information Data Area (T
In KTXTI_DA), text information indicating an artist name, an album name, an arranger name, a producer name, etc. is described. This area is reserved even if there is no text data.

{17-5} TKGI Next, the TKGI in the upper part of TKTXTI_DA will be described.
In FIG. 17, the TKGI of the TKI is the TKI identifier “TKI_ID”, the TKI number “TKIN”, as shown by the broken line h4.
TKI size "TKI_SZ", link pointer to the next TKI "TKI_LNK_PTR", block attribute "TKI_BLK_ATR", playback time "TKI_PB_TM", TKI audio attribute "TKI_AOB_AT"
It can be seen that a series of information such as "R", "ISRC", and block information "BIT" is recorded. (Note that some fields are omitted in this figure for the sake of simplicity.) .).

{17-5_22-1} TKGI The detailed structure of the TKGI will be described below with reference to FIG. The difference between this figure and FIG. 17 is that TK shown in FIG.
The data structure of GI is located on the left side of the figure, and it has not been revealed in FIG. 17 "TKI_BLK_ATR", "TKI_AOB_"
The bit configuration of "ATR" and "ISRC" is arranged on the right side in the figure.

{17-5_22-2} Regarding TKI_ID In “TKI_ID”, an ID (a 2-byte code “A4” in this embodiment) that can uniquely identify a TKI is described. {17-5_22-3} About TKIN "TKIN" describes TKI numbers in the range of 1 to 999. This TKI number is described in the TKIN of other TKIs.
Must not duplicate TKI number. As such a TKIN, the order of TKI in TrackManager, that is, TrackMana
It shall describe the position of TKI in ger. In the figure, TKI # 1 describes the TKI number as "1", TKI # 2 describes the TKI number as "2", and TKI # 3 describes the TKI number as "3".

{17-5_22-4} Regarding TKI_SZ In "TKI_SZ", the data size of the TKI is described in the number of bytes. In FIG. 22, since the TKI data size is defined as 1024 bytes, it is described as 1024 bytes in this embodiment. {17-5_22-5} About TKI_LNK_PTR “TKI_LNK_PTR” describes TKIN of the TKI linked to the TKI. Here, the correspondence between TKIs will be described.

When a track is composed of a plurality of AOBs and they are recorded in a plurality of AOB files, a plurality of TKIs associated with the plurality of AOB files are united to manage the track. It will be. When a plurality of TKIs are integrated as described above, it is necessary to indicate which TKI corresponds to which AOB file follows the AOB file corresponding to these TKIs. TKI_LNK_PTR is each T
It is used for describing TKIN of TKI that follows KI.

{17-5_22-6_19} TKI_LNK_PTR Hereinafter, in the eight TKIs shown in FIG. 19, TKI_LNK_PTR
Will be described. In TKI # 1 to TKI # 3 and TKI # 8 that make up one track, the T
KI_LNK_PTR is not set, but the four A's that make up TrackD
TKI # 4, TKI # 5, TKI # 6, TKI # 7 corresponding to OB file,
Each TKI_LNK_PTR is set to indicate the next TKI_LNK_PTR. That is, as shown by arrows TL4, TL5, TL6, TKI # 4
TKI_LNK_PTR indicates TKI # 5, and TKI # 5's TKI_LNK
_PTR indicates TKI # 6, and TKI_LNK_PTR of TKI # 6 indicates TKI # 7. All of these form TrackD. These TKI_LNK in TKI corresponding to four AOB files
By referring to _PTR, the four TKIs TKI # 4 to TKI # 7
It can be seen that KI and four AOB files of AOB004.SA1 to AOB007.SA1 collectively form TrackD.

{17-5_22-7} About TKI_BLK_ATR "TKI_BLK_ATR" describes attributes about TKI. In FIG. 22, the bit structure of TKI_BLK_ATR is shown in the frame drawn from TKI_BLK_ATR with a broken line. In this figure, TKI_BLK_ATR is 16 bits, and bits b3 to b15 are reserved for future expansion. The attributes of the TKI are described using 3 bits of bit numbers b2 to b0.

When TKI is used and one TKI is included in one track, a value of "000b" is described in TKI_BLK_ATR (hereinafter, this setting is referred to as "Track"). T
KI is used, one track contains multiple TKIs,
If the TKI is at the beginning, TKI_BLK_ATR contains "001
The value of "b" is described (hereinafter, this setting is "Head_of_Trac
k ”. ). When TKI is used, one track is composed of multiple TKIs, and the TKI is in the middle, a value of "010b" is described in TKI_BLK_ATR (hereinafter,
This setting is called "Midpoint_of_Track"). When the TKI is used, one track is composed of a plurality of TKIs, and the TKI is the end of the TKI, a value of "011b" is described in TKI_BLK_ATR (hereinafter, this setting is referred to as "End_of_Track"). . If the TKI is unused and there is a TKI area,
That is, in the case of the deleted TKI, the value of "100b" is described (hereinafter, this setting is referred to as "Unused"). TKI
Is unused and there is no TKI area, that is, when the TKI is in the initial state, the value of "101b" is described.

{17-5_22-8_19} TKI_BLK_ATR Setting Example In the example of FIG. 19, TKI_BLK_A for each TKI is set.
Explain how TR is set. each
If you refer to TKI_BLK_ATR in TKI, TKI # 1 (AOB001.
SA1), TKI # 2 (AOB002.SA1), TKI # 3 (AOB003.SA1), T
The four pairs of KI # 8 (AOB008.SA1) correspond to independent tracks, so TKI # 1, TKI # 2, TK
TKI_BLK_ATR of I # 3 and TKI # 8 is set to “Track”.

TKI_BLK_ATR in TKI # 4 is “Head_of_Tr
ack ”and TKI_BLK_ATR in TKI # 7 is set to“ End_o
It can be seen that “f_Track” and TKI # 5 and TKI # 6 are set as “Midpoint_of_Track”. This means that TKI # 4 (AOB004.SA1), which has a corresponding relationship with TKI # 4, has a corresponding relationship with TKI # 5 and TKI # 6 (AOB005.AOB004.SA1).
SA1) and TKI # 6 (AOB006.SA1) are in the middle of the truck,
TKI # 7 (AOB007.SA1), which has a corresponding relationship with TKI # 7, means the end of the track.

As described above, if the groups of TKIs (AOB files) are classified according to the description of TKI_BLK_ATR in each TKI,
It can be seen that TKI # 1 (AOB001.SA1) constitutes the first track (TrackA). It can be seen that TKI # 2 (AOB002.SA1) constitutes the second track (TrackB) and TKI # 3 (AOB003.SA1) constitutes the third track (TrackC). TKI # 4 (AOB
004.SA1) constitutes the beginning of the fourth track (TrackD), and TKI # 5 (AOB005.SA1) and TKI # 6 (AOB006.SA1)
Is the middle part of TrackD, and TKI # 7 (AOB007.SA
It can be seen that 1) constitutes the end part of TrackD. T
It can be seen that KI # 8 (AOB008.SA1) independently constitutes the termination part of the fifth Track E.

{17-5_22-9} About TKI_PB_TM "TKI_PB_TM" describes the reproduction time of the track (song) composed of the AOB recorded in the AOB file corresponding to the TKI. When the track is composed of a plurality of TKIs, the playback time of the entire track is described in TKI_PB_TM for the first TKI. For the second and subsequent TKIs,
AOB playback time corresponding to each TKI is described.

{17-5_22-10} About TKI_AOB_ATR In "TKI_AOB_ATR", what sampling frequency is used for the AOB recorded in the AOB file corresponding to TKI, and what bit rate is transferred. Or the number of channels, the encoding conditions for AOB generation are described. 『TKI_AOB_
The frame drawn from the “ATR” with a broken line shows the bit configuration of TKI_AOB_ATR. In the figure, TKI_AOB_ATR is 20 bits, and the coding mode is described in the fields from bit number b16 to bit number b19. MPEG-2
When encoded with AAC (with ADTS header), the value of "0000b", when encoded with MPEG-layer3 (MP3), the value of "0001b" is Windows (registered trademark) Media If encoded with Audio (WMA), "
0010b "is described respectively.

The bit rate is described in the fields from bit number b15 to bit number b8. MPEG-2 AAC
When encoded with (with ADTS header), the value of "16" to "72", when encoded with MPEG1-layer3 (MP3), the value of "16" to "96", MPEG2-layer3
(MP3) "16" to "80" when encoded in LSF
When the value of is encoded by Windows (registered trademark) Media Audio (WMA), the values of "8" to "16" are described respectively.

The sampling frequency is described in the bit numbers b7 to b4. "0000b" for 48kHz,
"0001b" for 44.1kHz, "0010b" for 32kHz, 24kH
A value of "0011b" is described for z, a value of "0100b" for 22.05kHz, and a value of "0101b" for 16kHz. The number of channels is described in the fields from bit number b3 to bit number b1. In the case of 1ch (mono), "000b" is described. 2ch (s
In the case of (tereo), "001b" is described.

The areas from bit number b31 to bit number b20 and bit number b0 are reserved for future expansion. {17-5_22-11} About ISRC "ISRC" includes ISRC (International Stan
dard Recording Code) is described. A frame drawn from “ISRC” in FIG. 22 by a broken line shows the contents of ISRC. As shown in this frame, the ISRC consists of 10 bytes, and the Recording-item code (# 12) is described in the field from bit number b4 to bit number b7.
Recording cod in the field from b8 to bit number b11
e / Recording-item code (# 11) is described.

Recording codes (ISRC # 10, # 9, # 8) are described in the fields from bit number b12 to bit number b23. Year-of-Recording code (ISRC # 6, # 7) is described in the field from bit number b24 to bit number b31.
After that, the fields from bit number b32 to bit number b37, the field from bit number b40 to bit number b45, and the field from bit number b48 to bit number b53 have First Owner Code (ISRC # 3, # 4, # 5 ) Is described.
Fields from bit number b56 to bit number b61 and fields from bit number b64 to bit number b69
Country code (ISRC # 1, # 2, # 3) is described. Bit number
A 1-bit Validity flag is described in the field of b79. For details on ISRC, see ISO3901: 1986.
'' Documentation-International Standard Recording
See Code (ISRC) ''.

Regarding {17-5_22-12_23A-1} BIT The “block information table (BIT)” is a table for managing AOB_BLOCK. 23A and 23B are diagrams showing the detailed configuration of the BIT. As shown in FIG. 23A, BI
T is DATA_OFFS that occupies 60th to 63rd bytes
ET field, SZ_DATA field occupying 64th to 67th bytes, TMSRTE_Ns field occupying 68th to 71st bytes, and 72nd to 73rd bytes
FNs_1st_TMSRTE field occupying up to the byte, and 74
FNs_Last_TMSRTE occupying bytes 75 to 75
Occupies fields and 76th to 77th bytes
It consists of the FNs_Middle_TMSRTE field and the TIME_LENGTH field occupying the 78th to 79th bytes. Hereinafter, each component will be described.

{17-5_22-12_23A-2} Regarding DATA_Offset "DATA_OFFSET" describes the relative address from the cluster boundary to the beginning of each AOB_BLOCK in byte units. This expresses how many invalid areas exist between AOB and AOB_BLOCK. If the music stored in the flash memory card 31 as the AOB is air-checked and recorded, and the disc jockey's voice is mixed in the intro portion of the music, the BIT
By setting DATA_Offset in, it is possible to exclude this unnecessary sound from AOB_BLOCK and prevent it from being reproduced.

{17-5_22-12_23A-3} SZ_DATA In "SZ_DATA", the data length of each AOB_BLOCK is described in bytes. The sum of SZ_DATA and DATA_Offset
By subtracting from the size of the file that contains AOB (an integer multiple of the cluster size), you can determine the size of the invalid area following AOB_BLOCK.

{17-5_22-12_23A-4} Regarding TMSRTE_Ns "TMSRTE_Ns" includes TMSRT_entr included in each AOB_BLOCK.
The total number of y is described. {17-5_22-12_23A-5} "FNs_1st_TMSRTE", "FNs_Last
Regarding “_TMSRTE” and “FNs_Middle_TMSRTE”, “FNs_1st_TMSRTE” describes the number of AOB_FRAME included in the first AOB_ELEMENT in the AOB_BLOCK.

In "FNs_Last_TMSRTE", the number of AOB_FRAMEs included in the last AOB_ELEMENT of AOB_BLOCK is described. "FNs_Middle_TMSRTE" contains the first and last AOBs
AOB_ELEMENT excluding _ELEMENT, that is, the number of AOB_FRAMEs included in AOB_ELEMENT located in the middle part of AOB_BLOCK is described.

"TIME_LENGTH" is a field for describing the reproduction period of AOB_ELEMENT with the time precision of millisecond order in the format shown in FIG. 23 (c). FIG. 23
As shown in (c), the TIME_LENGTH field has a 16-bit length, and the encoding method is MPEG-AAC or MPEG-Layer.
In the case of 3 systems, the reproduction period of AOB_ELEMENT is 2 seconds, so a value of 2000 is described in TIME_LENGTH.

{17-5_22-13_23B} FIG. 23B shows that FNs_Mi
It is a figure which shows how many AOB_FRAMEs are stored in ddle_TMSRTE. This figure shows sampling_frequency and
The correspondence with the number of AOB_FRAME included in AOB_ELEMENT in the middle part is shown. Sampling_frequency in this figure,
It can be seen that the correspondence relationship with the number of frames included in AOB_ELEMENT is exactly the same as that in FIG. 14, and the number is different depending on the sampling frequency. 『FNs_1st_TMSRT
The number of frames in "E" and "FNs_Last_TMSRTE" is
In principle, it is set to the same number of frames as the number of frames in "FNs_Middle_TMSRTE", but when setting an invalid area in AOB_ELEMENT located at the beginning or end of AOB_BLOCK,
"FNs_1st_TMSRTE" and "FNs_Last_TMSRTE" are "FNs
_Middle_TMSRTE ”.

{17-5_22-14_24} Storage Example of AOB_ELEMENT FIG. 24 is a diagram showing clusters 007 to 00E in which AOBs consisting of AOB_ELEMENTs # 1 to # 4 are stored. How the BIT is set when the AOB is stored as shown in FIG. 24 will be described. These clusters
007 ~ AOB_ELEMENT # 1 ~ AOB stored in cluster 00E
Each of _ELEMENT # 4 is provided with a triangular flag-shaped symbol, which indicates that TMSRT_entry included in the TKI is set in each of AOB_ELEMENT # 1 to AOB_ELEMENT # 4.

At this time, the leading end portion of AOB_ELEMENT # 1 at the AOB leading end is stored in the cluster 007, and the ending portion of AOB_ELEMENT # 4 at the AOB end is stored in the cluster 00E. AOB_ELEMENT # 1 to # 4 are in the middle of cluster 007
Occupies from md0 to md4 in the middle of cluster 00E. SZ_DATA in BIT is AOB_ELEMENT # 1 to A as shown by arrow sd1.
OB_ELEMENT # 4 is instructed to the end, and cluster 007,
It is an area within 00E and does not indicate the parts ud0 and ud1 which are not occupied by AOB_ELEMENT.

On the other hand, the AOB is an area within the cluster 007 and the cluster 00E, and has AOB_ELEMENT # 1 and AOB_ELEMEN.
It also includes parts ud0 and ud1 that are not occupied by T # 4. DATA_Offset in BIT indicates a data length of the unoccupied portion ud0, that is, a relative value from the beginning of the cluster 007 to the beginning of AOB_ELEMENT # 1. In this figure, AOB_ELEM
ENT # 1 is in the middle of cluster 007 to in the middle of cluster 008
Occupies up to md1. This AOB_ELEMENT # 1 does not occupy the entire cluster 008, but is occupied by AOB_ELEMENT # 2 after its end portion. AOB_ELEMENT # 4
Occupies the middle part md3 of the cluster 00C to the middle part md4 of the cluster 00E. Thus AOB_ELEMENT
It can be seen that there is something recorded so as to cross the boundary of the cluster. In other words, AOB_ELEMENT is
It is recorded regardless of the boundaries of the clusters. “FNs_1st_TMSRTE” in BIT indicates the number of frames of AOB_ELEMENT # 1 in cluster 007 to cluster 008, and “FNs_Last_TMSRTE” in BIT is in cluster 00C to
The number of frames of AOB_ELEMENT # 4 in the cluster 00E is shown.

As described above, each AOB_ELEMENT is freely arranged regardless of the cluster boundary, and it is understood that the BIT manages the offset from the cluster boundary to the AOB_ELEMENT and the number of frames for each AOB_ELEMENT. . {17-5_22-14_25} Usage of the number of frames for each AOB_ELEMENT 1 The following describes how the number of frames for each AOB_ELEMENT described in BIT is used. The number of frames described in BIT is, first of all, the playback elapsed time of 2
This is used when performing forward search playback and reverse search playback in which the second skip is performed and playback is performed for 240 milliseconds.

FIG. 25 shows the case of performing forward search reproduction from AOB_FRAME # x in any AOB_ELEMENT # y in AOB.
It is a figure which shows how to set AOB_FRAME # x + 1 which should be reproduced next. This figure shows the AOB included in AOB_ELEMENT # y
FIG. 13 is a diagram drawn assuming that a forward search reproduction is instructed at the time when _FRAME # x is reproduced. In this figure, t is the predetermined intermittent playback time (= 240 ms), f
(t) is the number of frames corresponding to the intermittent playback time, the intermittent skip time skip_time is the length of time to skip during intermittent playback (2 seconds in this case), the intermittent skip time sk
Let f (skip_time) be the number of frames corresponding to ip_time.
Here, the intermittent reproduction is performed by repeating the following procedure.

Jump to the beginning of the flag (AOB_ELEMENT) with reference to TMSRT_entry described in TKTMSRT. Jump to the beginning of the next flag (AOB_ELEMENT) that plays for 240 ms. In the present embodiment, a method for realizing more accurate intermittent reproduction of reproducing for 240 milliseconds, jumping to a position 2 seconds later, and reproducing for 240 milliseconds will be described.

AOB_FRAME # x + 1, which is 2 seconds + 240 milliseconds after AOB_FRAME # x included in AOB_ELEMENT # y, is AOB_ELEMENT #
It should be in y + 1. AOB_FRAM after 2 seconds + 240 ms
When specifying E # x + 1, the start address for the next AOB_ELEMENT # y + 1 can be calculated immediately by reading TMSRT_entry in TKTMSRT.
The number of AOB_FRAMEs from the start address of ELEMENT # y + 1 to AOB_FRAME # x + 1 cannot be known only by TMSRT_entry. To calculate such AOB_FRAME number, AOB_F
AOB_EL is calculated from the sum of #x, which indicates the position of RAME # x from the beginning of AOB_ELEMENT # y, f (t), and f (skip_time).
It must be obtained by subtracting the total number of frames included in EMENT # y. As such, the next AOB_ELEMENT # y + 1
In order to easily calculate the relative frame position of AOB_FRAME # x + 1 in, the BIT is set to “FNs_1st_
TMSRTE, FNs_Middle_TMSRTE, FNs_Last_TMSRT
"E" is described.

{17-5_22-15_26A} Usage of the number of frames for each AOB_ELEMENT 2 The number of frames described in BIT is, secondly, a function of starting playback from an arbitrary playback time (time search function) It is used when executing. FIG. 26A is a diagram showing how to specify AOB_ELEMENT and AOB_FRAME corresponding to the designated time when an arbitrary playback start time is designated.

When reproduction is instructed by designating an arbitrary time, assuming that the reproduction designated time is Jmp_Entry (seconds), from AOB_ELEMENT # y and AOB_FRAME position x that satisfy the following formula,
Start playing. {Formula 2} Jmp_Entry (second) = (FNs_1st_TMSRTE ＋ FNs_middle_TMSRTE × y ＋ x) × 20msec These “FNs_1st_TMSRTE” and “FNs_Middle_TMSRTE”
Is described in BIT, so if AOB_ELEMENT # y and AOB_FRAME # x are calculated by applying these to {Formula 2}, refer to TKTMSRT corresponding to this AOB, and y + 2th in AOB The start address of the AOB_ELEMENT # y + 2 located at is searched, the search for AOB_FRAME # x is started from this start address, and if the xth AOB_FRAME is searched, the reproduction is started from this xth AOB_FRAME. This will cause Jmp_E
Playback can be started from the time specified by ntry (seconds).

At this time, the ADTS header portion of the AOB file is not searched, and AOB_ in which TMSRT_entry is described in TKTMSRT
Since it is sufficient to search in ELEMENT units, the playback position corresponding to the designated playback time can be found at high speed. Similarly, when the time search function is executed for tracks consisting of multiple AOBs and Jmp_Entry (seconds) is specified,
AOB_ELEMENT # y and AOB_FRAME that satisfy the following {Equation 3}
#x and should be calculated. {Equation 3} Jmp_Entry (sec) = Sum of playback time from AOB # 1 to AOB # n + (FNs_1st_TMSRTE (# n + 1) + FNs_middle_TMSRTE (# n + 1) ・ y + x) ・ 20msec where AOB # The total playback time of AOB from 1 to AOB # n is
It is as follows. Total playback time from AOB # 1 to AOB # n = ("FNs_1st_TMSRTE"(# 1) + "FNs_Middle_TMSRTE"(# 1) / (TMSRT_entry number # 1-2) + "FNs_Last_TMSRTE"(# 1) + "FNs_1st_TMSRTE ''(# 2) + `` FNs_Middle_TMSRTE ''(# 2) / TMSRT_entry number # 2-2) + `` FNs_Last_TMSRTE ''(# 2) + `` FNs_1st_TMSRTE ''(# 3) + `` FNs_Middle_TMSRTE ''(# 3) / TMSRT_entry number # 3 -2) + 'FNs_Last_TMSRTE'(# 3) ・ ・ ・ ・ ・ ・ ・ ・ ・ + 'FNs_1st_TMSRTE'(# n) + 'FNs_Middle_TMSRTE'(# n) ・ TMSRT_entry number # n-2) + 'FNs_Last_TMSRTE'(# n)) ・ AOB # n, AOB_ELEMENT # y, AOB_FRAME # that satisfies 20 msec {Equation 3}
When x is calculated, the TKTMSRT corresponding to this AOB # n + 1 is referred to, the search for AOB_FRAME # x is started from the address located at the y + 2nd AOB_ELEMENT # y + 2, and the xth AOB_FRAME If is searched, the reproduction is started from the x-th AOB_FRAME.

{17-5_22-16_27A, B} AOB file and TKI
Deleting all of the information included in TKI, when some tracks were deleted (case 1), when some tracks were deleted and new tracks were recorded (case 2),
How TKI is updated when combining any two of multiple tracks into one track (case3), dividing one track to get two tracks (case4) Will be described.

First, the case where some tracks are deleted (case 1) will be described. 27 (a), (b)
[Fig. 6] is a diagram assuming a case where a track is deleted. This figure shows the TrackManager shown in FIG. 19, and it is assumed that the operator desires to delete TrackB in this figure. The AOB corresponding to this TrackB is AOB002.SA
Since it is recorded in 1 and it is associated with TKI # 2, AOB002.SA1 is deleted and TKI_BLK of TKI # 2 is deleted.
_ATR is set to “Unused”. FIG. 27B shows a state in which AOB002.SA1 is deleted and TKI_BLK_ATR of TKI # 2 is set to “Unused”. Since AOB002.SA1 has been deleted,
The area occupied by AOB002.SA1 in the data area is released to a free area. At the same time, in TrackManager, it can be seen that TKI_BLK_ATR of TKI # 2 is set to “Unused”.

{17-5_22-17_28A, B} TKI allocation when newly recording an AOB file A case (case 2) in which a new track is recorded after some tracks are subsequently deleted will be described. FIG. 28
(A) shows TrackM after a track has been deleted multiple times.
It is a figure which shows an anager. In this figure, multiple tracks are deleted and these are TKI # 2, TKI # 4, TKI # 5, TKI # 7, TK.
If it is mapped to I # 8, the TKI_ of these TKIs
BLK_ATR is set to "Unused". AOB files are deleted in the same way as normal files, but TrackManager
Deletes only by setting TKI_BLK_ATR of the corresponding TKI to “Unused”. Then, as shown in this figure, "Unused" TKI will appear like a worm on TrackManager.

FIG. 28B is a diagram showing how an "Unused" TKI exists, and when a new TKI or AOB file is written therein, the writing is performed. Here, it is assumed that a track composed of four AOBs is written. Here, which empty TKI is to be allocated to the recording of the AOB is determined by DPL_TK_SRP described later, or an arbitrary TKI is allocated. The four AOBs
In TrackManager, TKI # 2, TKI # 4, TKI # 7, and TKI # 8 set to “Unused” are assigned to the.

Since these four AOBs make up one track, TKI_BLK_ATR for TKI # 2 is set to “Head_o
f_Track ”and TKI_BLK_ATR for TKI # 4 and TKI # 7 to“ Midpoint_of_Track ”and TKI_BLK_AT for TKI # 8
R is set to “End_of_Track”. Track TrackD
The four TKI # 2, TKI # 4, TKI # 7, and TKI # 8 that compose
_LNK_PTR is the next TKI_LNK_PT that composes the track TrackD.
It is set to indicate R. That is, arrows TL2, TL4, T
As shown in L7, TKI_LNK_PTR of TKI # 2 indicates TKI # 4, TKI_LNK_PTR of TKI # 4 specifies TKI # 7, and TKI_LN of TKI # 7.
K_PTR points to TKI # 8.

After that, four files AOB002.SA1 and A having the same numbers as TKI # 2, TKI # 4, TKI # 7 and TKI # 8, respectively.
OB004.SA1, AOB007.SA1, and AOB008.SA1 are created, and four AOBs that form TrackD are recorded in these four files. By setting such TKI_BLK_ATR and TKI_LNK_PTR, the fourth track TrackD is TKI # 2, TKI # 4, TKI # 7,
It will be managed using TKI # 8.

As described above, the flash memory card 3
If you want to write a new track to 1, use TrackMan until then.
It can be seen that the TKI set to "Unused" in the ager is assigned to the TKI of the track to be newly recorded. {17-5_22-18_29A, B} T when integrating two tracks
KI setting Next, update of TKI when integrating tracks (case 3) is explained.

FIGS. 29A and 29B are diagrams showing how the TKI is set when two tracks are integrated into one. FIG. 29A shows the TrackM shown in FIG.
It is the same as the anager, and in Track (C) in FIG.
It is assumed that the operator desires an editing operation of integrating TrackE and one track. Track C, Trac
AOBs corresponding to kE are recorded in AOB003.SA1 and AOB008.SA1 and they are associated with TKI # 3 and TKI # 8, so TKI_BLK_ATR of these TKI # 3 and TKI # 8 can be rewritten. Be seen. FIG. 29B is a diagram showing a state after rewriting TKI_BLK_ATR of TKI. TKI_ of TKI # 3 and TKI # 8 in this figure
Although BLK_ATR is described as Track, in FIG. 29B, TKI_BLK_ATR of TKI # 3 is rewritten to “Head_of_Track” and TKI_BLK_ATR of TKI # 8 is rewritten to “End_of_Track”. By rewriting TKI_BLK_ATR in this way, TKI # 3, TKI # 8, and AO corresponding to these
B003.SA1 and AOB008.SA1 are handled as one track called TrackC. In addition to this, TKI_LNK_PTR of TKI # 3 is rewritten to point to TKI # 8 as a link destination.

It should be noted that TKI_BLK_ATR of TKI was rewritten, but the process of integrating AOB003.SA1 and AOB008.SA1 was not performed. Because these AOB files are encrypted with different FileKeys, when they are integrated into one, the encrypted AOB files are decrypted and then encrypted again. This is because it is necessary to perform the above two processes for each AOB file, which requires a large processing load. In addition, the AOB file after integration has only one FileKey
This is because it is encrypted by, so the copyright protection is weakened compared to before integration.

In addition, the TKI is originally defined so that the size of TKTMSRT does not become large, but if this is integrated into one in the editing operation, the size of the combined TKI may be too large. Because. As described above, the integrated editing of tracks in this embodiment is performed by AO
It can be seen that this can be achieved only by changing the attribute of TKI_BLK_ATR while maintaining the encryption of the B file.

{17-5_22-18_29A, B-1_30,31} Conditions to be met when tracks are integrated The integration of tracks is realized by changing the attribute of TKI_BLK_ATR, as described above. Upon integration, it is required that the AOBs included in the integrated tracks meet the following conditions. The first condition is that the audio attributes (audio coding mode, bit rate, sampling frequency, number of channels) of the AOB included in the following track and the AOB included in the preceding track match. . this is,
This is because if the audio attributes of the AOB differ between the preceding and following AOBs, the playback device must reset the decoder operation once, making it difficult to play two consecutive AOBs seamlessly (without interruption). .

The second condition is that the AOB_FRAME number is "FNs_Middle_TMSRT" in the track obtained after the integration.
It means that there are no more than three consecutive AOBs consisting only of AOB_ELEMENT that are less than E ”. AOB is 2 depending on whether at least one of AOB_ELEMENT has the same number of AOB_FRAME as the number of frames specified in "FNs_Middle_TMSRTE".
There are two types. The first type of AOB is "FN
s_Middle_TMSRTE ”and the same number of frames A
An AOB that has at least one AOB_ELEMENT with OB_FRAME, and the second type of AOB is'FNs_Middle_TM
It is an AOB that does not have any AOB_ELEMENT that has the same number of AOB_FRAMEs as the number of frames specified in "SRTE".
That is, the AOB_ELEMENT in the second type AOB is less than the number of frames specified by "FNs_Middle_TMSRTE", and the second condition described above is the Type2 AOB.
It prohibits that three or more consecutive. The reason for prohibition is as follows. That is, when sequentially reading AOBs, the buffer in the playback device must have a sufficient number of AOB_FRAMs.
Although it is desirable to be filled with E, if the Type 2 AOB is continuous, the buffer in the playback device is set to AOB_FRAME
Can not be filled with. Then, the buffer in the playback device underflows, and the continuity of AOB playback cannot be maintained. In order to avoid such underflow, the second condition prohibits three or more Type 2 AOBs in a row.

FIG. 30A shows a Type 1 AOB, and FIG.
0 (b) is a diagram showing a Type 2 AOB. Figure 30 (b)
The AOB in consists only of two or less AOB_ELEMENT, and those AOB_ELEMENT of two or less are "FNs_Middle_TMSRTE".
Does not have AOB_FRAME shown in (in this case, BIT
In, only FNs_1st_TMSRTE is described. ). 『FNs_Mi
Since the requirement of Type2AOB is that it does not have AOB_FRAME shown in "ddle_TMSRTE", even an AOB composed of only one AOB_FRAME will be classified into this Type2 AOB.

FIG. 31A shows Type1 + Type2 + Type2 + T.
It is a figure which shows the case where several tracks are integrated into one by the combination of ype1. In this case, three consecutive Type 2 AOBs are avoided, so they are integrated into one track. FIG. 31B shows Type1 + Type2 + Type2.
It is a figure which shows the case where a plurality of tracks are integrated into one by a combination of + Type2 + Type1. In this case, Type 2 AOB
It is prohibited to combine them into one track as they are three consecutive.

{17-5_22-18_29A, B-1_32} Type1, Type2
According to the track integration shown in FIG. 31 (a), if the end of the preceding track is Type1, this track is a track in which a Type2 AOB is placed at the beginning, or the beginning To
It can be integrated with a truck with Type 1 AOB.
FIG. 32 (a) shows a Type 1 AOB at the end of the preceding track.
FIG. 3 is a diagram showing an arrangement pattern in which the AOB of Type 1 is arranged at the beginning of the subsequent track. Also in FIG.
(B) is a diagram showing an arrangement pattern in which a Type 1 AOB is arranged at the end of the preceding track and a Type 2 AOB is arranged at the beginning of the following track. All of these are conditions
Fill 2 so you can combine them into one track.

The end of the preceding track is Type2,
If the Type 1 AOB is placed immediately before that Type 2,
This track can be integrated with a track of which the head is a Type 1 or a track in which a Type 2 AOB is arranged at the head and a Type 1 AOB is arranged immediately after that. FIG. 32 (c)
FIG. 6 is a diagram showing an arrangement pattern in which AOBs of Type1 and Type2 are arranged at the end of the preceding track and AOBs of Type1 are arranged at the beginning of the following track. FIG. 32 (d) shows
FIG. 7 is a diagram showing an arrangement pattern in which AOBs are arranged in the order of Type1 and Type2 at the end of the preceding track, and AOBs of Type2 and Type1 are arranged at the beginning of the succeeding track. These too
Since condition 2 is satisfied, it can be integrated into one track.

The end of the preceding track is Type2,
If a Type 2 AOB is placed immediately before that Type 2,
This track can be integrated with a track that has a Type 1 AOB at the beginning. FIG. 32 (e) is a diagram showing an arrangement pattern in which Type 2 and Type 2 AOBs are arranged at the end of the preceding track and Type 1 AOBs are arranged at the beginning of the following track. Since this also satisfies the condition 2, it can be integrated into one track. As described above, when integrating tracks, it is determined in advance whether the two tracks to be integrated satisfy the above two conditions,
Only if it is determined that these two conditions are met, combine the two tracks into one.

Next, updating of the TKI when dividing the track (case 4) will be described. {17-5_22-19_33A, B} TKI setting when dividing a track FIGS. 33A and 33B are diagrams assuming a case where one track is divided into two tracks. Tr in this figure
The ackManager is the same as the TrackManager shown in FIG. 27, and in this figure, it is assumed that the operator wants to edit TrackC into two tracks, TrackC-TrackF. When TrackC is divided into TrackC-TrackF, AOB002.SA1 corresponding to TrackF is generated. In FIG. 33 (a), TKI # 2 is set to “Unused”, and as a result of the division, “Unused” is displayed as shown in FIG. 33 (b).
TKI # 2 set to is the newly generated AOB002.SA
Assigned to 1.

{17-5_22-19_33A, B-1_34A, B} Update directory entry and FAT value Here, when AOB003.SA1 is divided and AOB002.SA1 is generated, the directory entry and FAT value must be updated. I won't. The following describes how to update these directory entries and FAT values. Figure 34 (a)
FIG. 9 is a diagram showing how an SD_Audio directory entry for an SD_Audio directory to which AOB003.SA1 belongs is described before division. AOB003.S
A1 is divided into multiple clusters 007,008,009,00A ...
-It is assumed to be stored in 00D and 00E. In this case, for AOB003.SA1 in the directory entry, the "file first cluster number" is described as "007", and the FAT value 007,00 corresponding to the cluster 007,008,009,00A ... 00D.
8,009,00A ... 00D is (008), (009), (00A) ...
It is described as (00D) and (00E).

In this state, divide the latter half of AOB003.SA1
When obtaining AOB002.SA1, "file name", "file extension", and "file first cluster number" for AOB002.SA1 are added to the SD_Audio directory entry. FIG. 34 (b) shows AOB003.SA1 after division.
FIG. 6 is a diagram showing how an SD_Audio directory entry for an SD_Audio directory to which is belongs is described.

The cluster 00F in this figure stores a copy of the contents of the cluster 00B including the division boundary designated by the operator. The divided parts following the divided part of AOB002.SA1 stored in the cluster 00B are stored in the clusters 00C, 00D, and 00E and thereafter. Since the first part of AOB002.SA1 is stored in cluster 00F and the remaining part is stored in clusters 00C, 00D, 00E and later, AOB002.SA
In "File first cluster number" for 1, the cluster number 00F indicating the cluster 00F is described.
FAT value 00F, 00C, 00 associated with 00F, 00C, 00D, 00E
(00C), (00D), and (00E) are described in D, 00E.

{17-5_22-19_33A, B-2_35A, B} A by updating the directory entry and FAT value above the setting of the information element in the TKI
After obtaining OB002.SA1, we will describe how to set the information elements in the TKI for AOB002.SA1. When generating a TKI for a divided track, the information element of the TKI can be copied and inherited from the original TKI (1), and must be updated based on the original TKI. There are two types of things that do not (2). The former is TKTXTI_DA, ISRC and the latter is BI.
The remaining components, including T and TKTMSRT. Since both of them exist, in the present embodiment, when the TKI for the divided track is generated, the TKI of the division source is copied.
Then, a new TKI template is created, and TKTMSRT and BIT contained in it are divided and updated, and the remaining information elements are updated.

FIG. 35 (a) is a diagram on the assumption that AOB is divided by arbitrary AOB_FRAME. In the figure, the first row shows four AOB_ELEMENTs, AOB_ELEMENT # 1 and AOB_ELE.
Indicates MENT # 2, AOB_ELEMENT # 3 and AOB_ELEMENT # 4. these
The data length of each of the 4 AOB_ELEMENT is 4 TMSRT
_entry # k-1, # k, # k + 1, # k + 2 (k = 2 here) as TKTM
It is set to SRT. In this figure, if the division boundary bd1 is set in AOB_ELEMENT # 2, AOB_ELEMENT
# 2 is divided into an area composed of a frame before the division boundary bd1 and an area composed of a frame behind the division boundary bd1. In FIG. 35B, the AOB is divided in the middle of AOB_ELEMENT # 2, and two AOBs AOB # 1 and AOB # 2 are divided.
It is a figure which shows the state which was obtained.

{17-5_22-19_33A, B-3_36} BIT Setting FIG. 36 is a diagram showing how the BIT is set when the AOB is divided as shown in FIG. . The AOB shown in FIG. 35 is divided at the division boundary bd1,
The AOB # 1 obtained by the division is AOB_ELEMENT # 1 and AO_ELEMENT # 1.
Contains two AOB_ELEMENTs called B_ELEMENT # 2, AOB # 2 is
AOB_ELEMENT # 1, AOB_ELEMENT # 2, AOB_ELEMENT # 3 3
It can be seen that it contains one AOB_ELEMENT.

[0135] Each of these AOB_ELEMENTs is also provided with a triangular flag-shaped symbol.
Indicates that TMSRT_entry included in TKI corresponding to AOB is set. First, AOB # 1 obtained by division
Will be described. AOB_ELEMENT # 1, AO included in AOB # 1
Since B_ELEMENT # 2 occupies cluster 007 to cluster 00A, AOB # 1 handles cluster 007 to cluster 00A as one unit. Where AOB_ELEMENT # 2 in AOB # 1
Does not occupy the end of cluster 00A,
Since it occupies the division boundary bd1 where cluster 00A exists, SZ_DATA for AOB # 1 is from area md0 to cluster 0
It indicates the data length up to the division boundary bd1 at 0A. AOB # 1's "FNs_1st_TMSRTE" is the same as before the split, but AOB # 1's "FNs_Last_TMSRTE" is AOB_ELEMENT #
It differs from that before division in that the number of frames from the beginning before division 2 to the division boundary bd1 is designated.

Next, AOB # 2 obtained by division will be described. AOB_ELEMENT # 1, AOB_ELEMEN included in AOB # 2
T # 2 and AOB_ELEMENT # 3 occupy cluster 00B to cluster 00F. Cluster 00F is a cluster that stores a copy of the contents of cluster 00A. (The reason for storing a copy of cluster 00A in cluster 00F is cluster 00A.
Is occupied by AOB_ELEMENT # 2 of AOB # 1, so
AOB_E included in AOB # 2 that is different from this cluster
This is because it needs to be assigned to LEMENT # 1. ).

AOB_ELEMENT # 1 in AOB # 2 is a cluster
SZ_DATA for AOB # 2 is from the beginning of cluster 00B to cluster 00 because it does not occupy from the top of 00F but occupies the division boundary bd1 and later where cluster 00F exists.
The sum of the data length up to the middle of E and the data length occupied by AOB_ELEMENT # 1 in cluster 00F is instructed.

Cluster 00A stored in cluster 00F
AOB_ELEMENT # 2 of AOB # 1 is recorded in the copy of AOB # 1, and the part occupied by AOB_ELEMENT # 2 of AOB # 1 must be excluded from AOB # 2.
DATA_Offset for AOB # 1 in cluster 00F
The size occupied by AOB_ELEMENT # 2 of is set.

As can be seen from this figure, in the AOB division, only the AOB_ELEMENT including the division boundary is divided into two, and the AOB_ELEMENT before and after the division boundary are not changed from those before the division. Recognize. Therefore, AOB #
"FNs_Last_TMSRTE" of 2 is set to the same value as "FNs_Last_TMSRTE" of AOB_ELEMENT # 4 before division, and "FNs of AOB # 2"
In “s_1st_TMSRTE”, the number of frames included in AOB_ELEMENT # 1 of AOB # 2, that is, the end portion after the division boundary in AOB_ELEMENT # 2 before division is set.

{17-5_22-19_33A, B-4_37} BIT Setting FIG. 37 is a diagram more specifically showing how the BIT changes before and after the division. BIT on the left side of FIG. 37 shows a setting example of BIT before division. BIT before dividing the track
Data_Offset is set to X, SZ_DATA is "52428",
TMSRTE_Ns is set to "n". It can be seen that FNs_1st_TMSRTE is set to “80 frames”, FNs_Middle_TMSRTE is set to “94 frames”, and FNs_Last_TMSRTE is set to “50 frames”.

The right side of FIG. 37 shows the setting of BIT for two tracks after division. When the AOB corresponding to this BIT is divided as shown in FIG. 35 (a), in the BIT of the first track, Data_Offset is set to the same value “x” as before the division, but up to the division point bd1 in SZ_DATA. The data length is updated to "Q", and the first TMSRT_entr is set in TMSRTE_Ns.
It is updated to "k" which is the number of TMSRT_entries from y to the kth TMSRT_entry. FNs_1st_TMSRTE and FNs_Middl
e_TMSRTE is set to 80,94 frames as before division, but the last AOB_ELEM of the AOB of the first track after division.
Since ENT includes p AOB_FRAMEs in FIG. 35A, FNs_Last_TMSRTE is set to “p frame”.

In the BIT of the second track, Data_Offset is set to R, SZ_DATA is set to the original SZ # DATA52428-data length "Q" up to the dividing point bd1, and TMSRTE_Ns is set to n-k + 1 (k It is the number obtained by adding nk, which is the number of TMSRT_entries from the nth TMSRT_entry to the nth TMSRT_entry, and one, which is the number of the kth TMSRT_entry newly added for division.). FNs_Middle_TMSRTE and FNs_Las
The t_TMSRTE is set to 94,50 frames as before division, but the first AOB_ELEM of the AOB of the second track after division.
ENT contains 94-p AOB_FRAMEs, so FNs_
1st_TMSRTE is set to “94-p frame”.

{17-5_22-19_33A, B-5_38} BIT Setting FIG. 38 is a diagram showing the TKTMSRT after division. First TMSRT
Is as follows. The first track TMSRT is from the beginning of the AOB TMSRT before division to the kth entry
(TMSRT_entry # 1 to TMSRT_entry # k) are included. It should be noted here that AOB_ELEMENT # k including the division boundary only includes the area, and thus the k-th entry includes only the data size of the portion corresponding to this area. Two
TMSRT of the track is n from the kth entry before division.
Including (TMSRT_entry # k to TMSRT_entry # n) up to the second entry. It should be noted here that AOB_ELEMEN including the division boundary
T # k only contains the area on the second track, so
The kth entry before division contains only the data size of the part corresponding to this area.

If the TKI is copied, the TKTMSRT and BIT are divided and updated, and the remaining information elements are updated, the TKI for the new track obtained by the division can be obtained. As in the case of integration, encrypted AOB files remain encrypted without decryption
The track corresponding to an AOB file can be split into two. Since the decryption / re-encryption is not involved when dividing the AOB file, it can be seen that the processing load when dividing the track is reduced. As a result, even if the processing performance of the playback device is low, it is possible to edit the track.

Now that the long sentence has been described, the explanation of the TKI is completed. Next, the play list will be described. {17-6} Playlistmanager The playlistmanager shown in Fig. 17 has a broken line h5
PlaylistManager_Info for managing playlists stored in the flash memory card 31, as shown in FIG.
rmation (PLMGI) and Default_Playlist_Informa that manages all tracks stored in the flash memory card 31.
tion (DPLI) and Playlist Information (PLI) # 1, # 2, # 3, # 4,
Default_Playlist_Gener consists of # 5 ... # n, and Default_Playlist information is
al_Information (DPLGI), Default_Playlist_Track_Serch
It can be seen that _Pointer (DPL_TK_SRP) # 1, # 2, # 3, # 4 ... In addition, each PLI has Playlist_General_Information (PLGI), Playlist_
Track_Serch_Pointer (PL_TK_SRP) # 1, # 2, # 3, # 4 ... It is understood that it consists of #m.

[0146] Here, Default_Playlist information and PlayList
Explain the difference from the information. Default_Playlist
The information is obliged to specify all tracks, whereas the PlayList information does not have such an obligation, and any track may be specified. Therefore, the user can generate PlayList information that specifies only his or her favorite track and store it in the flash memory card 31, or the Flash memory card 3
The playback device automatically generates PlayList information that specifies only a track of a predetermined genre among the plurality of tracks stored in the flash memory card 31.
It is suitable for use as a memory.

{17-7_18} Number of playlists, data size Referring to FIG. 18, the maximum number of playlists is 99. Also, Playlist Manager Information (PLMGI) and Def
The ault playlist information (DPLI) has a fixed length of 2560 bytes in total. Playlist Information (PLI) also has a fixed length of 512 bytes. DPL_TK_SRP included in Default_Playlist information includes DPL_TK_ATR and DPL_TKIN. On the other hand, PL_TK_SRP included in the PlayList information is P
It contains only L_TKIN. These DPL_TK_ATR, DPL_TKI
N, PL_TKIN has the format shown in FIG.

{17-8_39-1} DPL_TK_SRP Format FIG. 39 (a) is a diagram showing the format of DPL_TK_SRP. In FIG. 39 (a), in DPL_TK_SRP, DPL_TKIN is described in 0th to 9th bits, DPL_TK_ATR is described in 13th to 15th bits, and 10th to 12th bits are reserved. It is reserved.

Next, the TKI number is described in DPL_TKIN which occupies the fields from the 0th bit to the 9th bit.
By writing the TKI number here, it is possible to specify the TKI. {17-9_39B} PL_TK_SRP format FIG. 39 (b) is a diagram showing the format of PL_TK_SRP. PL_TK_SRP has a field from the 0th bit to the 9th bit, and PL_TKIN, that is, the TKI number is described therein.

{17-8_39A-2} Configuration of DPL_TK_ATR From “DPL_TK_ATR” in FIG. 39 (a), broken line arrows h51, h52
An example of setting DPL_TK_ATR is shown in the frame extracted in.
As can be understood from the description in this frame, the setting of DPL_TK_ATR for DPL_TK_SRP is TKI_BLK_A for TKI.
It is the same as the TR setting, and "Track", "Head_of_Trac
k ”,“ Midpoint_of_Track ”, or“ End_of_Track ”is set.

Specifically, when the TKI specified by TKIN is in use and the audio object corresponding to one track is recorded in the AOB file corresponding to the TKI ("TKI_BLK_ATR of TKI" Track ”), DPL
The value of "000b" is set in _TK_ATR. If the TKI specified in TKIN is in use and the audio object corresponding to only the beginning of the track is recorded in the AOB file corresponding to that TKI ("Head_of_Track" in TKI_BLK_ATR of TKI), DPL_TK_ATR is " The value of "001b" is set.

The TKI specified by TKIN is in use,
When the audio object corresponding to only the middle part of the track is recorded in the AOB file corresponding to the TKI (“Midpoint_of_Trac in TKI_BLK_ATR of TKI”
k ”), and the value of“ 010b ”is set in DPL_TK_ATR. TKIN
The TKI specified in is in use and corresponds to the TKI.
When the audio object corresponding to only the end of the track is recorded in the AOB file (TKI_BLK of TKI)
"End_of_Track" in _ATR) and "0" in DPL_TK_ATR
The value of 11b "is set.

The TKI specified by TKIN is unused and T
If only the KI area is secured, that is, if it is a deleted TKI (“Unuse in TKI_BLK_ATR of TKI
d)), the value of "100b" is set. T specified by TKIN
When the KI is unused and the TKI area is not secured, that is, when the TKI is in the initial state, the value of "101b" is set.

“DPL_TK_SRP” has a correspondence relationship with any one of a plurality of TKIs by describing the TKI number in DPL_TKIN. Also, the rank of DPL_TK_SRP in the Default_Playlist information indicates the order of reproduction of the AOB (AOB file) corresponding to the TKI having a corresponding relationship with DPL_TK_SRP. By these things, Default_Play
The order of DPL_TK_SRP in the list information defines the order in which a plurality of tracks are played back, that is, the playback order of the tracks.

{17-9_40-1} Default_Playlist information, TK
Mutual Relationship of I and AOB Files FIG. 40 is a diagram showing the mutual relationship of Default_Playlist information, TKI, and AOB files. The second, third, and fourth levels in this figure are the same as the first level, the second level, and the third level in FIG. 19, and show a TrackManager including eight TKIs and eight AOB files. . The difference from FIG. 19 is that the Default_
This is the point where a rectangular frame indicating the Playlist information is described.
Eight small frames included in the first frame are Default_Playlis.
The eight DPL_TK_SRPs included in the t information are shown. The upper part of these small frames shows DPL_TK_ATR, and the lower part shows DPL_TKIN.

By referring to the arrows DT1, DT2, DT3, DT4, ... Between # 2 and DPL_T
It can be seen that there is a corresponding relationship between K_SRP # 3 and TKI # 3, and between DPL_TK_SRP # 4 and TKI # 4. Furthermore, each
If you refer to DPL_TK_ATR in DPL_TK_SRP, DPL_TK_S
RP # 1, DPL_TK_SRP # 2, DPL_TK_SRP # 3, DPL_TK_SRP # 8 are all set to Track. That is, DPL_TK_SRP # 1 → T
KI # 1 (AOB001.SA1), DPL_TK_SRP # 2 → TKI # 2 (AOB002.SA
1), DPL_TK_SRP # 3 → TKI # 3 (AOB003.SA1), DPL_TK_SRP
The four sets of # 8 → TKI # 8 (AOB008.SA1) correspond to independent tracks.

DPL_TK_SRP # 4, DPL_TK_SRP # 5, DPL_TK_SRP
Neither DPL_TK_ATR of # 6 and DPL_TK_SRP # 7 is set to Track, and DPL_TK_ATR of DPL_TK_SRP # 4 is “Head_of_Tr
It can be seen that DPL_TK_ATR in DPL_TK_SRP # 7 is set to “End_of_Track” and DPL_TK_SRP # 5 and DPL_TK_SRP # 6 are set to “Midpoint_of_Track”. This means that TKI # has a correspondence with DPL_TK_SRP # 4.
4 (AOB004.SA1) is the beginning of the track, and DPL_TK_
TKI # 5 (AOB005.SA1) and T which have correspondence with SRP # 5, # 6
KI # 6 (AOB006.SA1) has DPL_TK_S in the middle of the track
This means that TKI # 7 (AOB007.SA1) having a correspondence relationship with RP # 7 is the end of the track.

[0158] The order of DPL_TK_SRP in the DefaultPlaylist indicates in what order the AOBs associated with each TKI are played back. DPL in DefaultPlaylist in this figure
_TK_SRP # 1, # 2, # 3, # 4 ・ ・ ・ ・ ・ ・ # 8 DPL_TKIN is TKI # 1, # 2, #
3, # 4 ・ ・ ・ ・ ・ ・ # 8 is shown, so arrows (1) (2) (3) (4) ・ ・ ・ ・
・ As shown in (8), AOB001.SA1 corresponding to TKI # 1 is played first, AOB002.SA1 corresponding to TKI # 2 is second, TOB # 3
AOB003.SA1 corresponding to 3rd, AOB00 corresponding to TKI # 4
4. SA1 will be played fourth.

{17-10_41} DefaultPlaylist, PlayList
Information Setting Example FIG. 41 is a diagram showing a setting example of DefaultPlaylist and PlayList information in the same notation as in FIG. 40. In the figure, a square frame in the first row shows Default_Playlist information, and three square frames in the second row show PlayList information. The small frame included in DefaultPlaylist is DefaultPlayli
The eight DPL_TK_SRPs included in st indicate the small frames included in the PlayList information indicate three or four PL_TK_SRPs. TKIN of each DPL_TK_SRP included in Default_Playlist information of this figure
Settings are the same as in FIG. However, it can be seen that the setting of TKIN of PL_TK_SRP included in the PlayList information is completely different from that of DPL_TK_SRP.

{17-10_42} Correspondence between DPL_TK_SRP and TKI FIG. 42 uses the same notation as in FIG.
It is a figure which shows the correspondence with I. 42, Playlist # 1
Consists of PL_TK_SRP # 1, # 2, # 3. Of these PL_TK_SRP # 1
PL_TKIN is described as # 3, PL_TK_SRP # 2's PL_TKI
N is described as # 1 and PL_TKIN of PL_TK_SRP # 3 is described as # 2. Therefore, when playing a track using PlayList information # 1, a plurality of tracks are displayed as indicated by arrows (11), (12), and (13). AOB is AOB # 3, #
Played in order of # 1 and # 2.

Playlist # 2 is composed of PL_TK_SRP # 1, # 2 and # 3. Among them, PL_TKIN of PL_TK_SRP # 1 is described as # 8, and PL_TKIN of PL_TK_SRP # 2, # 3 is described as # 3, # 1, so when playing a track using PlayList information # 2, As indicated by arrows (21) (22) (23), multiple AOBs are AOB # 8, #
Playback is performed in the order of 3, # 1, that is, in an order completely different from Playlist # 1.

Playlist # 3 is composed of PL_TK_SRP # 1, # 2, # 3 and # 4. Of these, PL_TK_SRP # 1, # 2, # 3, # 4 PL_TKIN is # 8, #
Since it is described as 4, # 3, # 1, when the tracks are reproduced using the PlayList information # 3, the AOB is reproduced in the reproduction order shown below. First, the AOB # 8 constituting TrackE is reproduced as indicated by the arrow (31), and AOB # 4, AOB # 5, AOB # 6, AOB # 7 constituting TrackD as indicated by the arrow (32) are reproduced in this. It is then played back. Then, as shown by the arrows (33) and (34), TrackC and Trac
Playback is performed in the order of AOB # 3 and AOB # 1 that compose kA. It should be noted here that when a track is composed of multiple TKIs, PL_TK_SRP entry contains
The point is that only the first TKI number is described. Specifically, DPL_TK_SRP in Default_Playlist information
Are the four TKIs for TrackD: TKI # 4, TKI # 5, TK
I # 6 and TKI # 7 were specified, but PL in PlayList information
_TK_SRP need not specify these four TKIs. Pla
This means that PL_TK_SRP # 2 of ylist # 3 specifies only TKI # 4 among TKI # 4 to TKI # 7.

On the other hand, the DPLI including a plurality of DPL_TK_SRP is 1
RAM has a data size that fits in a sector
Resident on top. Therefore, when playing each track based on Playlist, DPL_T resident in RAM
By referring to K_SRP, each TKI can be searched at high speed. That is, in order to play a TKI (AOB) using PL_TK_SRP in which only the first TKI number is written among multiple TKIs, RAM is based on the TKI described in PL_TK_SRP.
Search the DPL_TK_SRP resident above to determine if the track is composed of multiple TKIs. Multiple T
If it is composed of a KI, the procedure of reproducing all the corresponding TKI (AOB) is performed.

As described above, Defau is set in PlayListManager.
ltPlaylist, multiple PlayList information are described, and if DPL_TK_SRP, DPL_TKIN of PL_TK_SRP, and PL_TKIN that compose them have different playback orders, multiple AO
B is reproduced in a different reproduction order. If the reproduction is performed in a completely different reproduction order, the operator can use the flash memory card 31 as if a plurality of music albums are stored.

It should be noted that DPL_TK_ of DPL_TK_SRP and TKI, both of which are associated with the AOB file.
SRP data size is small (only 2 bytes), TKI
The data size of is large (it has 1024 bytes). Swapping the order of TKIs in TrackManager frequently causes access to the flash memory card 31, but even if the order of DPL_TK_SRP in Default_Playlist information and PlayList information is swapped, access to the flash memory card 31 does not become so large. In view of this point, when editing navigation data, the order of DPL_TK_SRP in DefaultPlaylist is positively changed according to the editing operation, while Trac
The order of TKIs in kManager is kept constant regardless of editing operations.

{17-9_40-2_43A, B} Swap Order of DPL_TK_SRP Next, how to perform an editing operation of changing the playback order of tracks by swapping the order of DPL_TK_SRP in the Default_Playlist information will be described.
FIGS. 43 (a) and 43 (b) are diagrams assuming a case where the order of the tracks is exchanged. DPL_TK in FIG. 43 (a)
The settings of _SRP and TKI are the same as in FIG. Figure 40
In (a), DPL_TK_SRP # 3's DPL_TKIN is TKI #
3, DPL_TKIN in DPL_TK_SRP # 8 was set to TKI # 8, but in this state, DPL_TK_SRP # 3 surrounded by a thick frame
And the order of DPL_TK_SRP # 8. Fig. 43 (b)
In (1), (2), (3), (4), (5), (6), (7) and (8), the reproduction order of the tracks after the order change is shown. With this in mind,
The reproduction order in FIG. 43 (a) is TrackA, TrackB, Tr.
ackC, TrackD, and TrackE, but in FIG. 43 (b)
In the Default_Playlist information, DPL_TK_SRP # 3, DPL_TK_SRP
The order of DPL_TKIN for # 8 has been changed, so Tr
It will be played in the order of ackA, TrackB, TrackE, TrackD, and TrackC. As described above, by changing the order of DPL_TK_SRP in the Default_Playlist information, the reproduction order of tracks can be easily changed.

The editing operation called the track changing operation has been described. As in the case of TKI, when some tracks are deleted (case 1), after some tracks are deleted, a new track is recorded. In case (case2), when combining any two of multiple tracks into one track (case3), when dividing one track to obtain two tracks (case4), DPL_TK_SRP and TKI are Explain how it is updated.

{17-9_40-3_44A, B} When deleting tracks First, when some tracks are deleted (case 1)
Will be described. 44 (a) and 44 (b) are DPL_TK_SRP # 2 and TKI # 2 of the DefaultPlaylist shown in FIG.
DefaultPlaylist, TrackManager, AOB when deleting
FIG. 6 is a diagram showing how a file is updated. FIG. 44 has the same parts as FIG. 27 cited in the explanation of TKI deletion. That is, the second, third and fourth steps in FIG. 44 are the same as those in FIG. The difference is that, as in FIG. 40, Default_Playlist information including a plurality of DPL_TK_SRPs is described in the first row. Track consisting of DPL_TK_SRP # 2 → TKI # 2 (AOB002.SA1) surrounded by a thick frame in FIG. 44 (a)
Assume that the user has deleted B. In this case, Default_P
In the laylist information, DPL_TK_SRP # 2 is deleted and DPL_TK_SRP # 2 is deleted.
_TK_SRP # 3 to DPL_TK_SRP # 8 are moved up one by one so that the fields occupied by DPL_TK_SRP # 2 are packed. In this way, the order of each DPL_TK_SRP is advanced, and the last DPL_TK_SRP # 8 is set to “Unused”. On the other hand, the TKI is only set to “Unused” as described with reference to FIGS. 27A and 27B, and TKI # 2 is not moved so as to be packed. Also AOB002.SA1
Can be seen to have been deleted. Although the order has been advanced for DPL_TK_SRP, the order has not been advanced for TKI, so in Figure 44 (b), DP
DPL_TKIN in L_TK_SRP has been updated. That is, the new DPL_TK_SRP # 2 DPL_TKIN is as shown by the arrow DT11.
Instructing TKI # 3, DPL_TKIN of DPL_TK_SRP # 3 is arrow D
As shown in T12, TKI # 4, DPL_TK_SRP # 4 DPL_TKIN is TK
DPL_TKIN of I # 5 and DPL_TK_SRP # 5 indicates TKI # 6, respectively. In addition, DPL_TK_SRP # 8 set to “Unused”
It can be seen that DPL_TKIN sets TKI # 2 set to “Unused” as shown by the arrow DT13.

When the track is deleted, the DPL_TK_SRP that is being used is moved up to the beginning, but it can be seen that the TKI corresponding to it is set to the unused state while maintaining the original arrangement. In this way, since the TKI arrangement is fixed before and after editing, the processing load associated with the editing process can be reduced. {17-9_40-4_45A, B} TKI allocation when recording a track Next, a case where a new track is recorded after some tracks are deleted (case 2) will be described. Figure 45
(A) and (b) are diagrams showing how "Unused" TKI and DPL_TK_SRP exist, and when new TKI and DPL_TK_SRP are written therein, the writing is performed. In FIGS. 45 (a) and 45 (b), "Unused"
When explaining a case of assigning a new TKI to the TKI of FIG. That is, the second, third, and fourth stages in FIGS. 45A and 45B are the same as the first, second, and third stages in FIGS. 28A and 28B. The difference is that there are multiple DPs in the first row of FIG.
This is the point where Default_Playlist information consisting of L_TK_SRP is described. In FIG. 45 (a), DPL_TK_SRP # 4 to DP
L_TK_SRP # 8 is "Unused", while TKI # 2, TKI # 4, TKI # 5, TKI # 7 and TKI # 8 are "U" as shown in FIG. 28 (a).
It turns out that it is'nused '. In TrackManager, "U
While the Nused 'TKI exists like a worm, De
In the fault_Playlist information, the DPL_TK_SRP of "Unused" is summarized as described above.
This is because DPL_TK_SRP other than “Unused” is carried up, whereas TKI is not carried up.

Here, assume a case where a TrackD composed of four AOBs is to be written. The TKI for each of the four AOBs is written in each of TKI # 2, TKI # 4, TKI # 7, and TKI # 8 set to "Unused" in TrackManager. On the other hand, DPL_TK for these four AOBs
_SRP is DPL_TK_SRP # 4 ~ in Default_Playlist information.
Written to DPL_TK_SRP # 7. Since these four AOBs make up one track, DPL_TK_ATR for DPL_TK_SRP # 4 is "Head_of_Track" and DPL_TK_SRP # 5, D
DPL_TK_ATR for PL_TK_SRP # 6 is "Midpoint_of_Tra
ck ”and DPL_TK_ATR for DPL_TK_SRP # 7 is“ End_of
_Track ”is set.

Further, DPL_TKIN for DPL_TK_SRP # 4 is
It is set as TKI # 2 and DPL_TKIN for DPL_TK_SRP # 5 is T
KI # 4, DPL_TK_SRP # 6 DPL_TKIN is TKI # 7, DPL_T
DPL_TKIN for K_SRP # 7 is set to TKI # 8.
By setting DPL_TKIN and DPL_TK_ATR as above, TKI #
2, TKI # 4, TKI # 7, TKI # 8 will be managed as the fourth track TrackD.

In the above processing, the writing to the TKI of "Unused" has been performed, but TKI # 1, TKI # 2, TKI # 3, TKI
Regarding KI # 4, the point that no change is made is shown in FIG. 28.
It is similar to the case of. {17-9_40-5_46A, B} When integrating tracks (case3) Default_Pla when integrating tracks (case3)
Update of ylist information will be described. FIG. 46 (a),
(B) is a diagram assuming a case where tracks are integrated. This figure has the same parts as FIGS. 29 (a) and 29 (b) cited when explaining the TKI integration processing. That is, FIG.
The second, third, and fourth stages in (a) and (b) are shown in FIG.
9 (a) and 9 (b) are the same as the first and second stages. The difference is Default_ in FIGS. 46 (a) and 46 (b).
Playlist information is described and DPL_TK included in it
_SRP # 8 is set to "Unused" and also "Unuse
It has a corresponding relationship with TKI # 2 set in "d". In this figure, when the track integration process as shown in FIG. 29 is performed on the AOB file and the TKI,
The contents of DPL_TK_SRP # 3 to DPL_TK_SRP # 6 are shifted one by one, and the description contents of DPL_TK_SRP # 7 enclosed in a thick frame are DPL_TK_SRP.
Copy to # 3. For TKI, the same update processing as in the case shown in FIG. 29 is performed.

{17-9_40-6_47A, B} Track division (case
4) When performing track division (case 4), Default_Pla
Update of ylist information will be described. FIG. 47 (a),
(B) is a diagram assuming a case where a track is divided. This figure has the same parts as FIGS. 33 (a) and 33 (b) cited when explaining the division processing for TKI. That is, the second and third stages in this figure are the same as those in FIG.
It is the same as the first and second stages in (a) and (b). The difference is Default_Pl in FIGS. 47 (a) and 47 (b).
The aylist information is described and it is included in DPL_TK_S
RP # 8 is set to "Unused" and also "Unused"
It has a corresponding relationship with TKI # 2 set to. In this state, when the TKI # 3 and AOB003.SA1 surrounded by a thick frame are divided into two, as in the case of FIG. 33,
DPL_TK_SRP # 3 to DPL_TK_SRP # 7 are moved down one by one, and "Unused" DPL_TK in Default_Playlist information
Move _SRP to DPL_TK_SRP # 3. DPL_TK_SRP after moving
TKI # 2 obtained by division is associated with # 3. T
AOB002.SA1 associated with KI # 2 was originally AOB003.S
Although the latter half of A1 is stored, DPL_TK_SRP # 2 exists before DPL_TK_SRP # 3 associated with TKI # 2, and this DPL_TK_SRP # 2 corresponds to TKI # 2-AOB002.SA1. It is attached. That is, AOB002.SA1 and AOB003.SA1 store the latter half and the first half of the original AOB003.SA1.
DPL_TK_SRP # 2 and DPL_TK_SRP # 3 that specify these are
Since the playback order is specified to play these AOB files in the order of AOB003.SA1 and AOB002.SA1, the original AO
The second half portion and the first half portion of B003.SA1 are reproduced in the order of the first half portion and the second half portion by the reproduction order designation of DPL_TK_SRP.

{17-9_40-8} Application of Editing Process By combining the above four editing operations, the operator can perform various editing operations. That is, if there is a disc jockey announcement at the beginning of a track and you want to delete it, the above-mentioned track division process divides the announcement part into one track, and then deletes that track. For example, you can only partially remove the disc jockey announcement.

[0175] Above, the description of the navigation data has been completed.
A playback device configured to play presentation data will be described. {48-1} Appearance of Playback Device FIG. 48 shows the flash memory card 3 according to the present embodiment.
FIG. 3 is a diagram showing a portable playback device for No. 1. In the figure, the reproducing device includes a key panel for receiving a key operation such as an insertion slot into which the flash memory card 31 is inserted, reproduction, forward search reproduction, reverse search reproduction, fast forward, rewind, stop and the like from an operator. , And has an appearance similar to a normal portable audio device. The key panel has a Playlist key that accepts playlist / track selection, a "| <<key" that accepts skipping to the beginning of the track, a ">>> | key" that accepts skipping to the beginning of the next track, fast forward, and winding. ">>key","<<key" for accepting return, forward search playback, and reverse search playback, and Display key for accepting operation to display a still image when the flash memory card 31 stores a still image. , Rec key that accepts recording operation from the operator, Stereo / Monoral selection, Audio key that accepts sampling frequency selection from the operator,
It has a Mark key that accepts bookmarks, an Edit key that accepts track editing, and title input.

{48-2} Improvements in Portable Playback Device of Flash Memory Card 31 The portable playback device of the flash memory card 31 is different from ordinary portable audio equipment in the following improvements (1) to
It is (4). That is, the Default_Playlist information from the operator, P
In order to accept the layList information and the designation of the track, the LCD display shall show a list of playlists and tracks (1), and any one of the playlists or tracks listed as such. A key has been assigned to specify as a playback target or edit target (2), along with the playback progress of the track,
The LCD display shows the elapsed playback time of the track (3), and the time search function and the jog dial used to set the playback start time when performing split editing (4). Is.

{48-2_49_50} Details of Improvement (2) Details of the improvement (2) are as follows. FIG. 49 is a diagram showing an example of display contents of the liquid crystal display when a playlist is selected, and FIG. 50 is a diagram showing an example of display contents of the liquid crystal display when a track is selected. . 49 "DEFAULTPLAYLIST""PLA
YLIST # 1 ”, PLAYLIST # 2”, “PLAYLIST # 3”, “PLAYLIST #
4 ”indicates a default playlist stored in the flash memory card 31 and four playlists A
It is a SCII string. In addition, “TRAC in FIG.
K # 1 ”, TRACK # 2”, “TRACK # 3”, “TRACK # 4”, “TRACK # 5”
Is an ASCII character string indicating five tracks whose playback order is designated in the default playlist stored in the flash memory card 31. 49 and 50
In (a), these hatched playlists and tracks are designated to be reproduced or edited. As shown in FIG. 50 (b), when the >>> | key is pressed with TRACK # 1 designated as the playback target, a list of tracks whose playback order is defined in the playlist is displayed on the liquid crystal display. Among the plurality of tracks listed as shown in, TRACK # 2 under the track is designated as the reproduction target. When the TRACK # 2 is specified as the reproduction target and the >>>> key is pressed, the state shown in FIG.
Among the plurality of tracks listed as shown in, TRACK # 3 in the lower row is designated as the reproduction target. If the | << key is pressed while TRACK # 3 is designated as the playback target, one of the plurality of tracks displayed in FIG.
As shown in, TRACK # 2 one level higher is designated as the reproduction target. As described above, since any track is selected as the reproduction target in response to the pressing of the >>>> key or the | << key, when any track is selected as the reproduction target, FIG. When the playback key is pressed as shown in, playback of the track is started, and when the Edit key is pressed, the track is designated as an edit target.

{48-3_51} Details of Improvement (4) Next, details of the improvement (4) will be described. FIG. 51 shows
It is a figure which shows the operation example of a jog dial. The jog dial accepts a rotation operation by the operator, and the reproduction elapsed time displayed on the liquid crystal display is increased or decreased according to the rotation amount. For example, as shown in FIG. 51A, it is assumed that the reproduction start time is displayed as "00:00:20" on the liquid crystal display. In this case, as shown in FIG. 51B, if the jog dial is rotated counterclockwise, the reproduction start time decreases to "00:00:10" according to the rotation amount. If the jog dial is rotated clockwise as shown in FIG. 51 (c),
The playback start time increases according to the amount of rotation, and the playback time starts at "00:00:
30 ”.

The reason why the playback time is increased or decreased in this way is to designate an arbitrary playback time on the track. If the arbitrary playback time is designated by the rotation of the jog dial and the playback key is pressed, {Formula 2}
Play the AOB from the position specified according to {Equation 3}. In addition, in split editing, the jog dial is used for finely adjusting the split boundary when specifying an arbitrary reproduction start time as the split boundary.

{52-1} Internal Configuration of Playback Device Next, the internal configuration of the playback device will be described. Figure 52
FIG. 3 is a diagram showing an internal configuration of a playback device. In the figure, the reproducing apparatus includes a card connector 1 for connecting a flash memory card 31, a user interface section 2 connected to a key panel and a jog dial, and a RAM 3
A ROM 4, a liquid crystal display 5 having a play list, a list display frame for displaying a list of tracks, and a reproduction elapsed time frame for displaying the reproduction elapsed time, an LCD driver 6 for driving the liquid crystal display, and each AOB file Different to
Descrambler 7 for decrypting AOB_FRAME using FileKey, and if descrambling of AOB_FRAME is performed by the descrambler 7, refer to the ADTS header of the AOB_FRAME to decrypt the AOB_FRAME. AAC decoder 8 that obtains PCM data by
It is provided with a D / A converter 9 for D / A converting the PCM data obtained by decoding and outputting it to a speaker via a headphone terminal, and a CPU 10 for performing an integrated process in the reproducing apparatus. As can be seen from this hardware configuration, there is no new configuration for processing the TrackManager and Default_Playlist information in this playback device. TrackManager, Defa
What is provided for processing ult_Playlist information is
The playback control program and the edit control program stored in the ROM 4 are the DPLI resident area 11, the PLI storage area 12, the TKI storage area 13, the FileKey storage area 14, the double buffer 15, which are secured in the RAM 3.

{52-2} DPLI resident area 11 The DPLI resident area 11 is Default_Play which is connected to the card connector 1 and read from the flash memory card 31.
This is an area reserved for resident list information. {52_12} PLI storage area 12 The PLI storage area 12 is an area that is reserved for storing PlayList information that is selected by the operator and is a reproduction target.

{52-3} TKI storage area 13 The TKI storage area 13 includes a plurality of TKIs included in TrackManager.
T corresponding to the AOB file that is the playback target
This area is reserved for storing only KI and has a data size of one TKI. {52-4} FileKey storage area 14 FileKey storage area 14 is AOBSA1.KE in the protected area.
This area is reserved for storing only the FileKey corresponding to the AOB file that is the reproduction target among the plurality of FileKeys included in Y.

{52-5} Double buffer 15 The double buffer 15 stores the cluster data read from the flash memory card 31 (data stored in each cluster) in sequence and stores it. Encrypted from clustered data AOB_FRAM
This is an input / output buffer used when the output process of reading E and sequentially outputting it to the descrambler 7 is performed in parallel. The double buffer 15 sequentially releases the area occupied by the cluster that has been output as AOB_FRAME to a free area, and uses this free area to store the newly read cluster, that is, a ring. A cyclic area is secured using a pointer.

{52-5_53_54A, B} Input / Output in Double Buffer 15 FIG. 53 is a diagram showing how data input / output in the double buffer 15 is performed. FIG. 54 (a),
(B) is a diagram showing how a cyclic area is secured using a ring pointer. In these drawings, an arrow pointing downward to the left indicates a pointer for the write destination address of the cluster data, that is, a write destination pointer. An arrow pointing to the upper left indicates a pointer for the read destination address of the cluster data, that is, a read destination pointer. These pointers are used as ring pointers.

{54-6_53} Flash memory card 31
Is connected to the card connector 1, the cluster data in the user data area of the flash memory card 31 is read from the flash memory card 31 as indicated by arrows w1 and w2. The read cluster data is stored in the double buffer 15 in the write destination pointer WP1,
The data is sequentially stored in the position indicated by WP2.

{52-7_54A} Of the AOB_FRAME included in the cluster data thus stored, the AOB_FR existing at the position designated by the read destination pointer
The AME is sequentially de-selected as indicated by arrows r1, r2, r3, r4, r5 ...
It is output to the scrambler 7. Here, the cluster data 002,003 is stored in the double buffer 15,
If the read destination indicated by the read destination pointer moves as shown in (5) in FIG.
Since all of the AOB_FRAMEs included in are read out, the cluster 004 is newly read out, and the area occupied by the cluster 002 is overwritten as indicated by the arrow w6 in FIG. 54 (a).

{52-8_54B} Also, if the reading destination indicated by the reading destination pointer moves as indicated by and reaches to, it means that all AOB_FRAMEs included in the cluster 003 have been read. Read cluster 005 to
As shown by an arrow w7 in FIG. 54B, the area occupied by the cluster 003 is overwritten. As above, AOB_FRAM
The output of E and the overwriting of cluster data are repeated many times, and AOB_FRAME included in the AOB file is sequentially output to the descrambler 7 and the AAC decoder 8.

{52-9_55 to 58} Playback Control Program Stored in ROM 4 Next, the playback control program stored in the ROM 4 will be described. FIG. 55 is a flowchart showing the processing procedure of the AOB file read processing, and FIGS.
7, FIG. 58 is a flowchart showing the processing procedure of the AOB_FRAME output processing.

{52-9_55-1} In these flowcharts, the variable w is a variable for instructing each of a plurality of DPL_TK_SRPs, and the variable z is each AOB file, its corresponding TKI, and its included. This is a variable for uniquely indicating the AOB to be stored. The variable y is a variable for designating each AOB_ELEMENT included in the AOB # z designated by the variable z, and the variable x is the AO designated by the variable y.
This is a variable that indicates each AOB_FRAME included in B_ELEMENT # y. First, the processing procedure of the AOB file reading processing will be described with reference to FIG.

{52-9_55-2} In step S1, the CPU 1
0 reads PlayListManager, Default_Playlist
List information and PlayList information. In step S2, the CPU 10 waits for specification of which of Default_Playlist information and PlayList information is used to reproduce the AOB. Here, if Default_Playlist information is specified, the process proceeds from step S2 to step S3, the variable w is initialized (# w ← 1), and in step S4, by DPL_TKIN associated with DPL_TK_SRP # w in Default_Playlist information. Specified TKI # z is specified and only that TKI # z is TKI
Read to storage area 13. Then, in step S5, the AOB file #z having the same number as the TKI #z is specified.
By the steps so far, the AOB file to be played is finally specified. The identified AOB file is
Since it has been encrypted, the processing of steps S6 and S7 is performed thereafter to cancel the encryption of this AOB file. That is, in step S6, the protected area is accessed and the AOB file #
The FileKey # z stored in the File Key Entry # z having the same number as z is read. CPU10 in step S7
Sets FileKey # z to descrambler 7. Since the FileKey is set in the descrambler 7 by such setting, if the AOB_FRAMEs included in the AOB file are sequentially input to the descrambler 7 thereafter, the AOB_FRAMEs are sequentially reproduced.

After {52-9_55-3}, each cluster storing the AOB file is sequentially read out. Step S8
Then, the "file first cluster number" for the AOB file #z in the directory entry is specified, and in step S9, the CPU 10 reads the data stored in the cluster from the flash memory card 31. In step S10, it is determined whether or not the cluster number is described as FFF in the FAT value, and if the FAT value is
If the value is other than FFF, the data stored in the cluster designated by the FAT value is read in step S11. After such reading, the process proceeds to step S10. Here, when reading the data stored in any of the clusters and referring to the FAT value associated with that cluster, as long as any cluster number other than FFF is described in the FAT value, The processing from step S10 to step S11 is repeated. This allows that FA
The clusters designated by the T value are sequentially read out. When the cluster number is described as FFF in the FAT value, it means that all the clusters forming the AOB file #z have been read out, so that steps S10 to S
Move to 12.

{52-9_55-4} The CPU in step S12
10 determines whether or not the variable #w matches the total number of DPL_TK_SRP. If they do not match, the process proceeds to step S13, increments the variable #w (# w ← # w + 1), and then proceeds to step S4. Default_Pl in step S4
The TKI # z specified by the DPL_TKIN # w of the DPL_TK_SRP # w in the aylist information is specified, and only the TKI # z is read into the TKI storage area 13. At this time, the TKI that has been used until then is stored in the TKI storage area 13, but the CPU 1
0 overwrites the TKI already stored in the TKI storage area 13 with the newly read TKI. Due to such overwriting, only the latest TKI is stored in the TKI storage area 13. If the TKI is overwritten in this way, the processes of steps S5 to S12 are repeated for the AOB file #z. The processing of Step S5 to Step S12 is repeated, and all the Default_Playlist information includes
If the TKI and AOB files corresponding to DPL_TK_SRP are read, the variable #w and the total number of DPL_TK_SRP match, step S12 becomes Yes, and this flowchart ends.

{52-9_56_57_58} AOB_FRAME output processing In parallel with the AOB file reading processing, the CPU 10 executes AOB_FR according to the flowcharts of FIGS. 56, 57 and 58.
Perform AME output processing. In this flowchart, play_ti
“Me” is a variable indicating the elapsed playback time, that is, the playback elapsed time, and the display contents of the time in the time display frame of the liquid crystal display 5 are rewritten according to this update of play_time. Also, play_data is the data length that has been played so far.

{52-9_56-1} In step S21, C
The PU 10 monitors whether the cluster data for AOB file #z has been accumulated in the double buffer 15. This step S21 is repeated unless the cluster data is accumulated. However, if the cluster data is accumulated, #x and #y are initialized in step S22 (# x ← 1, # y
← 1), then in step S23, AOB file
BIT # z included in TKI # z in the cluster about #z
AOB_FRAM in AOB_ELEMENT # y from Data_Offset onwards
Detect E # x. Assuming that the 7 bytes from SZ_DATA are occupied by the ADTS header, refer to the ADTS header, analyze that the data length indicated in the ADTS header is the audio data of the main body, and And the audio data of the main body are read and output to the descrambler 7. If the descrambler 7 decrypts the AOB_FRAME and the AAC decoder 8 decrypts it, it will be reproduced as voice.

{52-9_56-2} After detection, in step S24, AOB_FRAME # x is output to the descrambler 7, and in step S25, the reproduction elapsed time play_time is AOB_F.
The playback time corresponding to RAME # x is incremented, and the number of played data play_data is incremented by the number of data corresponding to AOB_FRAME # x. Here, since the reproduction time length of AOB_FRAME is 20 msec, 20 msec is added to the reproduction elapsed time play_time.

If the first AOB_FRAME is output to the descrambler 7, the A of AOB_FRAME # x is determined in step S26.
Refer to the DTS header to identify where the next AOB_FRAME is. In step S27, the variable #x is incremented (# x ← # x + 1), and the next AOB_FRAME is AOB_FRAME.
#x. In step S28, AOB_FRAME # x is put into the descrambler 7. Then, in step S29, play_time is incremented by the playback time corresponding to AOB_FRAME # x, and play_data is incremented by the number of data corresponding to AOB_FRAME # x. AOB_FRAME #
After incrementing x, in step S30, the CPU
10 determines whether or not #x has reached "FNs_1st_TMSRTE". If #x does not reach "FNs_1st_TMSRTE", it is checked in step S31 whether a key other than the Play key has been pressed, and then the process proceeds to step S26. After that, until #x reaches “FNs_1st_TMSRTE”, or Pl
Until a key other than the ay key is pressed, step S26-
The process of step S31 is repeated. Play here
When any key other than the key is pressed, this flowchart is ended and the process corresponding to the pressed key is performed. If the pressed key is the stop key, the reproduction process is stopped, and if the pressed key is the pause key, the playback process is paused.

{52-9_57-1} On the other hand, #x is "FNs_1st_TMSRT.
If “E” is reached, step S30 becomes Yes, and FIG.
Then, the process proceeds to step S32. In the processing from step S26 to step S30, all AOB_FRAMEs included in AOB_ELEMENT have been input to the descrambler 7,
In order to shift the processing target to the next AOB_ELEMENT, step S
At step 32, #y is incremented and #x is initialized (# y ← # y + 1, # x ← 1).

Then, in step S33, TKTMSRT
Calculate the start address for AOB_ELEMENT # y by referring to. After that, the processing including steps S34 to S42 is performed. The process of steps S34 to S42 can be said to be the same as the process of steps S24 to S31 in that the AOB_FRAME included in the AOB_ELEMENT is read one after another. The difference from the processing of steps S24 to S31 is that the end condition of the loop processing in the latter is #x reaches “FNs_1st_TMSRTE”, whereas the end condition of the loop processing in the former is #FNs_Middle_TMSRTE. 』Is reached. #
When x reaches "FNs_Middle_TMSRTE", step S34-
When the loop process including step S42 ends, step S41 becomes Yes and the process proceeds to step S43.
In step S43, the CPU 10 increments #y and initializes #x (# y ← # y + 1, # x ← 1). After that, in step S44, the variable y is TMSRT_ of TKI # z.
It is determined whether the value equal to (TotalTMSRT_entry_Number-1) in Header has been reached. #y is (TotalTMSRT_entry_Numb
er-1), AOB_ELEMENT # y is still the last AO
Since B_ELEMENT has not been reached, the process moves from step S44 to step S32, and thus step S3
The process of 2 to step S42 is continuously performed. #y is (Total
TMSRT_entry_Number-1), the last AOB_ELEME
It is considered that the reading process of AOB_FRAME has been completed up to AOB_ELEMENT one before NT, so step S44 is Yes.
Therefore, the process proceeds to step S45 of FIG.

{52-9_57-2} The processing of steps S45 to S54 is performed by the plurality of A's included in the last AOB_ELEMENT.
It can be said that the processing is the same as the processing of steps S33 to S42 described above in that it is the processing of reading each OB_FRAME. The difference is that the loop processing in steps S33 to S42 is performed in step S41.
While the end condition of the loop processing is that #x reaches “FNs_Middle_TMSRTE”, in step S53,
The point where #x is “FNs_Last_TMSRTE” and Play_data indicating the data size read so far reaches SZ_DATA is the end condition of the loop processing.

The processes of steps S49 to S54 are repeated until the condition of step S53 is satisfied. If this condition is satisfied, step S53 is Ye.
s, and the process proceeds to step S55. Step S5
In 5, the CPU 10 increments #z and then moves to step S21 (# z ← # z + 1) to wait for the next AOB file to be stored in the double buffer 15. If accumulated, the process proceeds from step S21 to step S22,
The processes of steps S22 to S54 are repeated for the next AOB file. That is, the next DPL_TK_SRP
The TKI specified by DPL_TKIN is specified, and the AOB file corresponding to that TKI, that is, the AO having the same number as the TKI
Identify the B file. After that, access the protected area, identify the FileKey that has the same number as the TKI in the encryption key storage file, read the FileKey, set the FileKey in the descrambler, and then use the same number as that TKI. AOB_FR included in AOB file with
The AME is read out in sequence and played back.

{52-9_57-3_59} Update of playback elapsed time FIG. 59 is a diagram showing that the playback elapsed time displayed in the time display frame of the liquid crystal display 5 increases as the variable Play_Time is updated. is there. In the figure (a), the playback elapsed time is 00: 00: 00.000, but when the playback of AOB_FRAME # 1 is completed, the playback length is 2 hours of AOB_FRAME.
0msec is added and updated to 00: 00: 00.020. AOB
When the playback of _FRAME # 2 ends, AOB_
FRAME time length of 20msec is added to 00: 00: 00.040, AOB
When the playback of _FRAME # 6 is finished, the playback elapsed time is 00: 0
You can see that it is 0: 00.120.

The above is the whole picture of the AOB_FRAME output processing.
As described above, in step S31 of this flowchart, when a key other than the Play key is pressed, the processing of this flowchart is interrupted, and there is a pause key or a stop key as such a key other than the Play key. Has also been explained, but in addition to the pause key and stop key,
Even when a key for causing the playback device to perform special playback is pressed, the processing of the flowcharts of FIGS. 56, 57, and 58 is interrupted, and the processing corresponding to the pressed key is executed. After that, the time search function is executed by operating the jog dial after the processing procedure of the CPU 10 when the >> key is pressed to execute the forward search reproduction and the pause key or the stop key is pressed. CP in case of
The processing procedure of U10 will be described.

{52-10_60} Forward search reproduction FIG. 60 is a flowchart showing the processing procedure of the CPU 10 when performing forward search reproduction. When the >> key is pressed by the operator, step S in FIG. 56, FIG. 57, or FIG.
This flowchart is executed by the CPU 10 when Yes in step 31, step S42, and step S54.

At step S61, the CPU 10 sends AOB_E
LEMENT # y AOB_FRAME # x to x + f (t) -1 are thrown into the descrambler 7. Here, "t" is the intermittent playback time, and f (t) is the number of frames corresponding to the intermittent playback time, d
Assuming that (t) is the number of data corresponding to the intermittent reproduction time, in step S62, play_time indicating the reproduction elapsed time and play_data indicating the number of reproduced data are defined as t: intermittent reproduction time, f
(t): update based on the number of frames corresponding to the intermittent playback time, d (t): update based on the number of data corresponding to the intermittent playback time (x ← x + f
(t), play_time ← play_time + t, play_data ← play_data +
d (t) Generally, the intermittent playback time is 240 milliseconds (12 AOB_
It corresponds to the playback time length of FRAME). ).

{52-10_60-1_61A, B} FIG. 61 (a),
FIG. 7B is a diagram showing how the reproduction elapsed time is incremented during forward search reproduction. Figure 6
1 (a) shows the initial state of the playback elapsed time, and indicates that the playback point is AOB_FRAME # 1 of AOB_ELEMENT # 51.
It can be seen that the reproduction elapsed time in this case is 00: 00: 01.000. Here, as the intermittent playback time, the 1st to 12th AOB_FRAMEs are thrown into the descrambler 7,
When 240 milliseconds, which is the time length of 1AOB_FRAME, is added to the playback elapsed time, the playback elapsed time becomes 00: 00: 01.240, as shown in FIG. 61 (b).

{52-10_60-2} After updating these, the CPU 10 in step S63 updates the AOB after the increment.
_FRAME # x is compared with the total number of frames in AOB_ELEMENT # y, and AOB_FRAME # x after increment is AOB_ELEMENT
Determine if it exists in #y. Specifically, the number of frames of AOB_ELEMENT located at the beginning of AOB is "FNs_1st_TMSRT
E ”, and the number of frames in the middle is“ FNs_Middle_TM
SRTE ”, the number of frames of the last one is“ FNs_Last_TMSRT
E ”, the determination is made by comparing these with AOB_FRAME # x. If updated AOB_FRAME # x
Is not present in AOB_ELEMENT, step S64
At, it is determined whether there is an AOB_ELEMENT following AOB_ELEMENT # y. Where AOB_ELEMENT # y is the last AOB_ELE
If it is MENT and there is no following AOB_ELEMENT,
When step S64 is No and the process of this flowchart ends, but when there is a subsequent AOB_ELEMENT, in step S65, AOB_FRAME # x to AOB_ELEMENT # y.
Reduce the number of frames in
By updating (y ← y + 1), AOB_FRAME # x is converted to the frame position of AOB_FRAME in the subsequent AOB_ELEMENT # y. If the updated AOB_FRAME # x exists in AOB_ELEMENT, these steps S65 to S6.
Skip 6 and move to step S67.

{52-10_60-3} Subsequently, AOB_FRAME # x, reproduction elapsed time play_time, and the number of reproduced data play_data are updated according to the intermittent skip interval. Here, the time corresponding to the intermittent skip interval is skip_time (2 seconds), and the number of frames corresponding to the intermittent skip interval skip_time is f (skip_
time), the number of data equivalent to the intermittent skip interval skip_time
Assuming that d (skip_time), AOB_FRAME # x, playback elapsed time play_time, and number of played data play_data are updated using these in step S67 (x ← x + f (skip_tim)
e), play_time ← play_time + skip_time, play_data ← play_
data + d (skip_time)).

{52-10_60-4_61C} As shown in FIG. 61 (c), AOB_FRAM indicating the frame position in AOB_ELEMENT # 51.
It is assumed that the intermittent skip interval is added to E # x. If #x after this addition exceeds the number of frames of AOB_ELEMENT # 51, AO
B_ELEMENT is updated to the next AOB_ELEMENT, and AOB_FRAME # x is converted to the frame position in AOB_ELEMENT # 52 by subtracting the number of frames of AOB_ELEMENT # 51 from #x after addition. In this case, AOB_ELEMENT # y is AOB_ELE
MENT # 52, and the elapsed playback time is 2.000 at 00: 00: 01.240.
By adding, it becomes 00: 00: 03.240. AOB_FRAM
E # x is AOB_FRAME # 62 (= (3240ms
ec-2000msec) / 20msec).

{52-10_60-5_61 (d)} After that, AOB_ELEMEN
If AOB_FRAME # 62 in T # 52 is input to the descrambler 7, the reproduction elapsed time is as shown in FIG. 61 (d).
By adding 0.240 to 00: 00: 03.240, 00:00:03.
It will be 480. If updating is performed according to the intermittent skip time in step S67, steps S68 to S
The process of 71 is performed. This step S68 to step S7
The process of No. 1 is the same as the process of steps S63 to S66, and it is determined whether AOB_FRAME exists in AOB_ELEMENT # y after the number of frames corresponding to the intermittent skip interval skip_time is added, and it is determined that the AOB_FRAME exists. If so, set the next AOB_ELEMENT to AOB_ELEMENT # y and set AOB_FR
Convert AME # x to the frame position in the new AOB_ELEMENT # y.

If AOB_FRAME # x and AOB_ELEMENT # y are incremented according to the intermittent playback time and the intermittent skip time, the CPU 10 at step S72 determines that TKTMSRT
AOB_FRAME # x is detected by calculating the start address for AOB_ELEMENT # y by referring to, and starting the ADTS header search from the start address in AOB_ELEMENT # y in step S73. Then, in step S74
In step S61, after it is determined whether or not any key other than the forward skip key is pressed, AOB_ELEM is determined.
AOB_FRAME # x to x + f (t) -1 of ENT # y are input to the descrambler 7, and the processes of steps S62 to S73 are repeated.

With the above processing, AOB_FRAME # x, AOB_ELEME
NT # y is incremented and the playback position advances.
After that, if the operator presses the reproduction key, step S74 becomes No, and the processing of this flowchart ends. {52-11} Execution of the time search function The processing when the time search function is performed will be described. A list of tracks in the Default_Playlist information is displayed, and designation of any track is accepted. When the track is specified and the jog dial is operated, the playback start time is updated. When the playback key is pressed after the playback start time has increased or decreased, the time specified for that playback will be changed to Jmp_Entry.
Specify (seconds). On the other hand, the specified track has multiple AO
Determine if it consists of B or a single AOB. single
If it consists of AOB, AOB_ELEMENT # y that satisfies {Equation 2}
And AOB_FRAME # x are calculated. AOB that satisfies {Equation 2}
If _ELEMENT # y and AOB_FRAME # x are calculated, in TKTMSRT corresponding to this AOB, the search for AOB_FRAME # x is started from the address located at the y + 2nd position, and if the xth AOB_FRAME is searched, this Playback starts from the xth AOB_FRAME.

{52-12} When a plurality of AOBs are included, AOB_n, AOB_ELEMENT # y and AOB_FRAME # x that satisfy {Equation 3} are calculated. AOB # n, AOB_ELEMENT # that satisfies {Equation 3}
If y and AOB_FRAME # x are calculated, T corresponding to this AOB # n
In KTMSRT, from the address located at the y + 2nd position, AOB
The search for _FRAME # x is started, and if the xth AOB_FRAME is searched, the reproduction is started from this xth AOB_FRAME.

Next, FNs_1st_TMSRTE in BIT is 80 frames, FNs_Last_TMSRTE is 50 frames, and FNs_Mid.
In the AOB in which dle_TMSRTE is 94 frames, a case where reproduction is started from an arbitrary reproduction time will be described. {52-13_62A, B} Here, as a specific example when the time search function is performed, AOB_ELEMENT that should start playback when the playback start time is specified by the jog dial,
How to specify the frame position where the reproduction should be started will be described. FIG. 62 is a diagram showing a specific example when the time search function is performed. Here, FIG. 62 (a)
As shown in, while the playback device is gripped and a certain AOB is designated as the playback target, the thumb of the right hand
The jog dial is rotated, and the playback start time is 0.
It is assumed that 0: 04: 40.000 (= 280.00sec) is specified. If the BIT in the TKI for this AOB has the content shown in FIG. 62 (b), the playback start time = 00: 04: 40.000 (= 280.00 sec)
When is applied to {Formula 2}, 280sec = (FNs_1st_TMSRTE ＋ FNs_middle_TMSRTE ・ y ＋ x)
× 20msec = (80 + 94 ・ 148 + 8) × 20msec, so AOB_ELEMENT # y, AOB_F that satisfies {Equation 2}
As RAME # x, AOB_FRAME with y = 148 and x = 8 is obtained.

Since y = 148 is specified in this way, the entry address of the y + 2nd AOB_ELEMENT # 150 (= 148 + 2) is T
Get it from KTMSRT and from the 8th AOB_FRAME from here,
If you start playback, playback elapsed time = 00: 04: 40.000 (= 280.
Playback can be started from (00 sec). When the Play key is pressed with more than {52-14_63_64_65},
The description of the processing content of the CPU 10 is finished. Next, the edit control program stored in the ROM will be described. This edit control program is executed when the Edit key is pressed, and its processing procedure is shown in FIGS. 63, 64, and 65. Hereinafter, the processing contents of the edit control program will be described with reference to these flowcharts.

{52-14_63-1} Edit control program Dialog that presents to the operator which of the typical edit operations such as deletion, division, and integration to be performed in step S101 of FIG. 63 when the Edit key is pressed The screen is displayed, and then, in step S102, it is determined whether the process for the interactive screen is designated. Here, in the operation of the interactive screen, the >> | key and the | << key are respectively used as keys for accepting the up / down cursor operation, that is, the up / down cursor keys. When the deletion process is designated, the process moves to the loop process including steps S103 and S104. In step S103, the >>> key, | <
<It is determined whether or not the key is pressed, and step S104
Then, it is determined whether or not the edit key is pressed. >>
If the | and | << keys are pressed, the process proceeds from step S103 to step S105, and the instructed track is designated as an editing target. On the other hand, if the edit key is pressed, it is determined that the track to be deleted is specified, and the process shown in FIG. 44 is performed to execute the TKI for the specified track.
The specified track is deleted by setting TKI_BLK_ATR of "Unused".

{52-14_63-2} Integrated Editing Process When integrated editing is designated, the process proceeds from step S102 to loop processing including steps S107 to S109. In the loop process including steps S107 to S109, pressing of the >>>> key, the | << key, and the pressing of the edit key are accepted. If the >>> ||, | << keys are pressed, steps S107 to S110
Then, the highlighted display is performed for the designated track. If the edit key is pressed, step S108
Is Yes, and the process proceeds to step S111. In step S111, the track designated by the cursor key is designated as an editing target, and steps S107-
The process moves to the loop process including step S109.

When the edit target of the second track is specified,
If step S109 becomes Yes, the process proceeds to step S112. In step S112, the preceding track,
AOBs located at the end and beginning of both tracks by referring to the TKI BIT for the following tracks
(If there are AOBs before and after that, A before and after that
OB) type is Type1 or Type2.

If the type of each AOB is known, it is determined in step S113 which layout pattern shown in the layout image of the AOB of each type. 32A to 32D corresponds to any one of the arrangement patterns,
If it is clear that three Type2AOBs do not continue even after integration, the preceding track and the following track are integrated into one track in step S115. That is, by performing the operation shown in FIG. 46 on the TKI and DPL_TK_SRP associated with these, and rewriting TKI_BLK_ATR of the TKI, a plurality of tracks selected as those operation targets are integrated into one track. Figure 32
If none of the arrangement patterns (a) to (d) applies and three Type 2 AOBs continue after integration, there is a possibility that underflow may occur in the tracks after integration in step S114. Is displayed and the integration process is interrupted.

{52-14_64-1} Track division processing When the division of a track is designated, the processing shifts from step S102 to step S116 to step S117. In the loop processing including steps S116 to S117, the pressing of the >>> key, the | << key, and the pressing of the edit key are accepted. >>> ||, | <<
If the key is pressed, steps S116 to S116
In step 118, the designated track is designated as an edit target. If the edit key is pressed, step S11
7 is Yes, and the process proceeds to step S119. In step S119, the track designated by the cursor key is designated as the editing target. Then, step S12
At 0, playback of the track specified for division is started,
In step S121, the depression of the Mark key is accepted. When the Mark key is pressed, the reproduction of the track is temporarily stopped, and the process proceeds to the loop process including steps S122 to S123. In step S122, the rotation operation for the jog dial is accepted, and when the rotation operation is performed for the jog dial, the reproduction start time is increased or decreased in accordance with the rotation operation in step S124. After that, the process returns to the loop process including steps S122 to S123. If the edit key is pressed with the playback start time increased or decreased by the rotation operation,
The process proceeds from step S123 to step S125, and in step S125, the reproduction time when the edit key is pressed is specified as the division boundary (note that the undo function (cancellation of editing) can be used when specifying the division boundary). . After that, in step S126, the processing explained in FIG. 47 is performed, and DPLI and TKI are updated to divide the track.

{52-14_65-1} Play list setting / editing processing When play list setting / editing is designated, the flow shifts to the flowchart in FIG. Variables in this flowchart
k is a variable for designating each track whose playback order is defined by the playlist to be set, and in the flowchart of FIG.
After setting 1 to this variable k in 131, step S
Then, the process proceeds to the loop process including 132 to step S134. In the loop process including steps S132 to S134, the pressing of the >> | and | << keys, the pressing of the edit key, and the pressing of the stop key are accepted. If the >>> key or | << key is pressed, the process proceeds from step S132 to step S135 to specify the track designated by the >>> key or | << key. If the edit key is pressed, step S133 becomes Yes, and step S
Move to 136. In step S136, the track designated by the edit key is specified as the k-th track to be reproduced. Then, in step S137, the variable k is incremented, and steps S132-
The process moves to the loop process of step S134. By repeating such processing, the second track, the third track, and the fourth track are sequentially specified. In this way, when the stop key is pressed while a plurality of tracks to be reproduced are specified in the newly created playlist, the process proceeds from step S134 to step S138 and is associated with these. PL_TK that identifies the TKI
Generate PlayList information consisting of _SRP.

(Recording Device) {66-1} Recording Device Next, an example of the recording device of the flash memory card 31 will be described. FIG. 66 is a diagram showing an example of a recording device of the flash memory card 31. The recording device in the figure is capable of communication via the Internet, and when the SD_Audio directory is encrypted by electronic music distribution and is transmitted via a communication line,
Alternatively, it is a general-purpose personal computer capable of receiving audio data transport streams when they are delivered by electronic music delivery.

{67-1} Hardware Configuration of Recording Device FIG. 67 is a diagram showing the hardware configuration of the recording device. In the figure, the recording device includes a card connector 21 for connecting a flash memory card 31, and a RAM 22.
, A fixed disk device 23 storing a recording control program for performing integrated control of the recording device, an A / D converter 24 for A / D converting voice input from a microphone to obtain PCM data, and unit time ACC encoder 25 that obtains AOB_FRAME by encoding per PCM data and adding ADTS header, and FileKey for each AOB file
Scrambler 26 for encrypting AOB_FRAME using
And when SD_Audio directory is encrypted and transmitted via the communication line by electronic music distribution,
Alternatively, when the audio data transport stream is transmitted through the communication line by electronic music distribution, the modem device 27 that receives the audio data transport stream and the CP that performs integrated control in the recording device
U28 and keyboard 2 that accepts operations from the operator
9 and a display 30.

{67-2} Input paths RT1 to RT4 When the SD_Audio directory to be written in the data area and the protected area by electronic music distribution is transmitted via the communication line in an encrypted state, the recording device sets It is sufficient to write the data in the data area and the protect area of the flash memory card 31 at the time of legally receiving. However, if the audio data transport stream itself is transmitted by electronic music distribution instead of the SD_Audio directory, or if it is input to the recording device in the PCM data state, it is input to the recording device in the original sound state. If it comes, the recording device is
The audio data transport stream is written to the flash memory card 31 via one input path.

When the recording device in this figure stores the audio data transport stream in the flash memory card 31, the input route RT1 shown in FIG.
There are an input route RT2, an input route RT3, and an input route RT4. {67-3} Input route RT1 The input route RT1 is used when the SD_Audio directory is encrypted by electronic music distribution and transmitted over the communication line, or when the audio data transport stream is transmitted over the communication line. This is an input path for the case of being transmitted as an AOB_FRAME included in the transport stream, which is different for each AOB_FRAME belonging to one AOB.
It is encrypted using FileKey. Since there is no need to re-encrypt or encode the encrypted transport stream, the SD_Audio directory or audio data transport stream is stored in the RAM 22 in an encrypted state.

{67-4} Input Route RT2 The input route RT2 is an input route when voice is input from a microphone. In this case, the A / D converter 24 is caused to perform A / D conversion on the voice input from the microphone to obtain PCM data. Then, by causing the AAC encoder 25 to encode the PCM data and adding the ADTS header,
Get AOB_FRAME. After that, each AOB is sent to the scramble unit 26.
By encrypting AOB_FRAME using the FileKey for each file, encrypted audio data is obtained. After that, the audio data is stored in the RAM 22.

{67-5} Input Path RT3 The input path RT3 is an input path when the PCM data read from the CD is input to the device. Since it is input in the state of PCM data, the PCM data is A
It is input to the AC encoder 25. So typed
AOB_FRAME is obtained by causing the AAC encoder 25 to encode the PCM data and adding the ADTS header. After that, the scramble unit 26 is configured to fill the Fil for each AOB_FRAME.
By encrypting AOB_FRAME using eKey, encrypted audio data is obtained. After that, the audio data is stored in the RAM 22.

{67-6} Input Path RT4 The input path RT4 is an input path for writing the transport stream input in the three input paths RT1, RT2, RT3 into the flash memory card 31. With the storage of such audio data, TKI, Default_Playlist
Information is generated. Similar to the case of the reproducing apparatus, the functional entity of the recording apparatus is also the recording program recorded in the ROM. That is, AOB recording, TrackManager, PlayListM
The processing peculiar to this embodiment such as recording of an anager is realized by a recording program recorded in the fixed disk device.

{67-7_68} After the processing procedure of the recording processing, referring to the flow chart, the input path RT
A description will be given of a processing procedure of recording processing when the transport stream is written in the flash memory card 31 in 1, RT2, RT3, and RT4. FIG. 68 is a flowchart showing the processing procedure of the recording processing. Frame_Number and Data_S are variables that are referred to in this flowchart.
There is something like ize. Frame_Number is so far A
Data_Size is a variable for managing the total number of AOB_FRAME recorded in the OB file, and Data_Size is a variable for managing the data size of AOB_FRAME recorded in the AOB file so far.

When this flowchart is executed, in step S200, the CPU 28 determines DefaultPlaylist, Track
Manager is created, and in step S201, the variable #z,
Initialize #w (z ← 1, w ← 1). In step S202, the AOB file #z is created and stored in the data area of the flash memory card 31. In this state, the directory entry of the SD_Audio directory in the data area is set with the file name, file extension, and first cluster number of the AOB file #z.
In the following step S203, the CPU 28 creates TKI # z and stores it in TrackManager, and in step S204, the CPU 28 creates DPL_TK_SRP # w and DefaultPlaylist.
Store in information. Thereafter, in step S205, the variable #y
Is initialized (y ← 1), and in step S206, Fram
Initialize each of e_Number and Data_Size (Frame_N
umber ← 0, Data_Size ← 0).

[0230] In step S207, the CPU 28 causes the AOB
It is judged whether the input of the audio data transport stream to be written in the file #z is completed. AAC
The scrambler 26 is encoded by the encoder 25.
If the audio data transport stream encrypted by is successively stored in the RAM 22 and it is necessary to continue writing the cluster data, step S207 becomes No and the process proceeds to step S209. In step S209, the CPU 28 sets A for the cluster size.
It is determined whether the AC audio data is accumulated in the RAM 22. When the cluster data is accumulated in the RAM 22, step S209 becomes Yes, the process proceeds to step S210, the AAC audio data of the cluster size accumulated in the RAM 22 is written in the flash memory card 31, and then the process proceeds to step S211. When the accumulation of cluster data is not completed, step S210 is skipped and the process proceeds to step S211. In step S211, the CPU 28 increments Frame_Number (Frame_Number
Number ← Frame_Number + 1), Data_Size to its AOB_FRAME
Increment by the data size of. After performing such update, in step S212, Frame_Number is
It is determined whether the number of frames defined as "FNs_Middle_TMSRTE" has been reached. Here, "FNs_Middle_TMSRT
Since “E” has a value according to the sampling frequency when the audio data transport stream is encoded, when Frame_Number reaches “FNs_Middle_TMSRTE”, step S212 is Yes, but otherwise. Step S212 becomes No, and step S20
Move to 7. After that, step S207 and step S2
Until S12 becomes Yes, steps S207 to S207
Step 212 is repeated.

If the Frame_Number reaches “FNs_Middle_TMSRTE” and the step S212 becomes Yes, the process moves from the step S212 to the step S213, and the Data_Size is set to A.
TK of TKI # z as TMSRT_entry # y about OB_ELEMENT # y
After storing in TMSRT and incrementing #y in step S214 (y ← y + 1), it is determined in step S215 whether or not the variable y has reached 252. Here, the value 252 is a value indicating the total number of AOB_ELEMENTs that can be stored in one AOB. If the variable y does not reach 252, step S2
Move to 16. In step S216, it is determined whether or not the silent state has continued for a predetermined time or longer and the audio data has reached the boundary between the tracks. When there is no silent state, the processes of steps S206 to S215 are repeated. When the variable y reaches 252, or when the silent state continues for a predetermined time or more, step S215,
Either one of step S216 becomes Yes, and the process proceeds to step S217 to increment the variables #z and #w (z ← z + 1, w ← w + 1). Then the incremented #z
For, the processing of steps S202 to S216 is repeated. By repeating this, multiple AOB_EL
AOBs including EMENTs are written in the flash memory card 31 one after another.

[0232] Here, when the transmission of the audio data transport stream from the AAC encoder 25, the scrambler 26, and the modem device 27 is finished, the input of the audio data transport stream to be written in the AOB file #z is finished. Therefore, step S207 becomes Yes and the process moves to step S208. In step S208, the CPU 28 sets Data_Size
T of TKI # z as TMSRT_entry # y about AOB_ELEMENT # y
After the audio data stored in the KTMSRT and stored in the RAM 22 is stored in the AOB file corresponding to AOB # z, the processing of this flowchart ends.

By the above processing, the encrypted audio data transport stream is stored in the flash memory card 31, and the FileKey for canceling this encryption is protected by the following processing. Stored in. In the case of the input paths RT2 and RT3, the CPU 28 changes the Fi each time when the encoding of one AOB is started.
Generate a leKey, set it in the scramble unit 26, and set F
The scrambling unit 26 is encrypted by ileKey, and those FileKeys are stored after FileKey Entry of the encryption key storage file existing in the protected area.

On the other hand, in the case of the input route RT1, an AOB file,
File containing TKMG, file containing PLMG, AO
The encryption key storage file that stores a different FileKey for each B
Sent from an electronic music distribution provider. CPU 28
Upon receiving them, the AOB file, the file storing the TKMG, and the file storing the PLMG are written in the user data area, and the encryption key storage file storing a different FileKey for each AOB is written in the protect area.

As described above, according to the present embodiment, the files storing the AOB are encrypted with different encryption keys, so the encryption key used to encrypt one file is decrypted, AOB that can be decrypted even if exposed is stored in one file
Only the AOB has no effect on the AOB stored in other files. The loss when the encryption key is exposed can be minimized.

The above embodiment has been described only as an example of a system in which the best effect can be expected at present. The present invention can be implemented and modified without departing from the gist thereof. Specifically, the modifications as shown in the following (a) to (f) are possible. (A) In the present embodiment, the description has been given assuming that the recording medium is a semiconductor memory (flash memory card), but the recording medium is not limited to this, and can be replaced with an optical disk such as a DVD-RAM or a hard disk.

(B) In this embodiment, AAC is used as music data, but the present invention is not limited to this.
(MPEG 1 Audio Layer 3), Dolby-AC3, DTS (Digital
Theater System) or the like. (C) Instead of distributing the file storing TKMG and the file storing PLMG by electronic music distribution,
TKMG, PLMG source information, AOB file, distributed with the encryption key storage file that stores different encryption key for each AOB, in the recording device, by processing the TKMG, PLMG source information TKMG, You may obtain PLMG and record it in a flash memory card.

(D) For convenience of explanation, the recording device and the reproducing device are separate devices, but the portable reproducing device may have the function of the recording device, or the personal computer type recording device may have the function of the reproducing device. May be provided. In addition to the portable playback device and the personal computer recording device, a communication device capable of downloading content from a network may be provided with the functions of the playback device and the recording device. For example, a mobile phone that can access the Internet is provided with the functions of the playback device and the recording device described in the first embodiment, and the content downloaded by the mobile phone via the wireless network is described in the first embodiment. As shown, it may be stored in the flash memory card 31. Further, in the present embodiment, the recording device has the modem device 27 for connecting to the Internet, but instead of this, it may have a terminal adapter or the like for connecting to the ISDN line. Good.

(E) FIGS. 55-58, 60, 63-
The procedure described with reference to the flowcharts of FIGS. 65 and 68 may be realized by an executable program, and the program may be recorded in a recording medium to be distributed or sold. Such recording media include IC cards, optical disks, flexible disks, and the like, and the machine language programs recorded on these are provided for use by being installed in a general-purpose computer. This general-purpose computer sequentially executes the installed executable programs to realize the functions of the reproducing apparatus and the recording apparatus shown in this embodiment.

(F) In this embodiment, a plurality of AOBs and a plurality of FileKeys are stored in the flash memory card 31, but one AOB is stored in the flash memory card 31.
You can store two FileKeys. Further, the AOB of the AAC method may be stored in the flash memory card 31 without encrypting the AOB. (Second Embodiment) {69-1} Overall Configuration of PlayListManager in Second Embodiment The second embodiment is an improvement regarding a semiconductor memory card that causes a playback device to play back content that has been played once without being duplicated. is there. FIG. 69 shows Pl in the second embodiment.
It is a figure which shows the internal structure of ayListManager and TrackManager. PlayListManager and TrackMana shown in this figure and FIG.
The configuration of the ger is different from that of ger in that the configuration of the Playlist Manager Information (PLMGI), which is not shown in FIG. 17, is shown in FIG. 69. This PLMG
In the configuration of I, PLMG_RSM_PL is particularly noteworthy, and by indicating the playback restart position in this, a semiconductor memory card can be used for the purpose of allowing the playback device to play back the content that has been played once without duplication. It is stored.

{70-1} Detailed Configuration of PlaylistManager Information FIG. 70 is a diagram showing a detailed configuration of PlaylistManager information. As shown in FIG. 70, the PlaylistManager information is PLMG_ID occupying the first 0th byte to the first byte.
Field, reserved area (reserved) occupying 2nd to 3rd bytes, SDA_ID field occupying 4th to 11th bytes, VERN field occupying 12th to 13th bytes, 14th to 15th bytes PLMG_PL_Ns field occupying up to eyes, PLMG_AP_PL field occupying from 16th to 19th bytes, PLMG_RSM_PL field occupying from 20th to 27th bytes, 28
PLMG_APP_ATR field occupying bytes 29 to 29, PLMG_F occupying bytes 30 to 31
CA field, occupying bytes 32 to 33
The TKI_Ns field consists of a reserved area (reserved) that occupies the 34th to 35th bytes. This PlaylistManage
In r information, PLMG_ is the main focus of the second embodiment.
AP_PL and PLMG_RSM_PL.

{70-2} Regarding information elements other than PLMG_AP_PL and PLMG_RSM_PL, PLMG_AP_PL and PLMG_RSM will be described below with reference to FIG.
Information elements other than _PL are explained first, and then PLMG_
AP_PL and PLMG_RSM_PL will be described. 『PLMG_I
In the "D" field, "A1", which is an ISO646 character string and which can uniquely identify PLMGI, is described.

In the "SDA_ID" field, a character string of "SD-AUDIO", which is an ISO646 character code and indicates that this PlayListManager is data based on the SD-AUDIO standard, is described. In the "VERN" field, the version number in this SD-AUDIO standard is described. The detailed bit configuration of the version number is shown in the broken line h71 in the figure. In this detail, information indicating the version number is described in the fields occupying the bit numbers b7 to b0. For example, when the version of this PlayListManager is version 0.9, "09h" is described,
When the version is 1.0, the value of "10h" is described. The fields from bit number b15 to bit number b8 are reserved as reserved areas for future expansion.

[0244] In the "PLMG_PL_Ns" field, the number of playlists handled by PLMG and the number of playlists recorded in this flash memory card are described. 『PLMG_APP
In the “_ATR” field, an application category ID indicating which category the application stored in this flash memory card belongs to is described. As shown in the first embodiment, when the genre of the application stored in the flash memory card is the music genre, "01h" is described in this field. On the other hand, "02h" is displayed when the genre of the application stored in this flash memory card is karaoke software, and "0h" when it is presentation data.
3h ”and“ 04h ”in the case of a reading book are described.

This application category ID is set to "02
If h ”is described, this flash memory card is
Since the audio data is stored as karaoke data, the audio data is recorded in the flash memory card such that the right channel is music and the left channel is voice. If the audio data is recorded like this,
The playback device can realize karaoke performance by outputting only the right channel to the left and right channels.

The “PLMG_FCA” field is an area prepared for future expansion. In the "TKI_Ns" field, the TKI number shown in the first embodiment is described by an integer value. The TKI is described as a value up to 999. This is the end of the description of the information elements other than PLMG_AP_PL and PLMG_RSM_PL. Then PLMG_AP_PL and PLMG_RSM_P
Explain L.

{70-3} About PLMG_AP_PL The "PLMG_AP_PL" field indicates that when this flash memory card is loaded in the playback device and the player is started up.
This is a field in which a playlist to be automatically read and a track number to be automatically reproduced in the playlist are described. In FIG. 70, the bit structure of PLMG_AP_PL is shown in the frame drawn out by the broken line h72. In this bit configuration, bit number b31
To bit number b26 and bit numbers b15 to b8 are reserved as reserved areas for future expansion.

In the Playlist Number field, which occupies bit number b7 to bit number b0, the playlist numbers assigned to the playlists to be automatically read are from 1 to 9
Described in the range of 9. The number described in this field is the Playlist Information (PLI) shown in the first embodiment.
Is the number. When specifying the default playlist in this field, describe "0".

In the Track Number field occupying the bit numbers b25 to b16, the track number of the track to be reproduced among the plurality of tracks whose reproduction order is specified in the read playlist is described ( This is the track number (T which indicates the track shown in the first embodiment.
rack_Number). ). PLMG_AP_PL is an item set by the user, but if it is not used, all the above fields must be set to "0".

{70-4} About PLMG_RSM_PL "PLMG_RSM_PL" is a Pl indicating the playlist used at the immediately preceding reproduction when the AOB file stored in the flash memory card is already reproduced by the reproducing apparatus.
The aylist Number and the Track Number that indicates the track that was played immediately before among the tracks whose playback order was specified by the playlist, and the time after the playback start time of the track with that track number It consists of Playback Time that indicates whether the playback has stopped. In FIG. 70, the bit structure of PLMG_RSM_PL is shown in the frame drawn out by the broken line h73. In this bit configuration, the bit configuration from bit number b31 to bit number b0 is the same as PLMG_AP_PL, and the Playlist Number field that occupies bit number b7 to bit number b0 is Track number that the assigned playlist number is described in the range of 0 to 99 and occupies bit number b25 to bit number b16
In the field, the track number of the track reproduced immediately before is described from among the plurality of tracks whose reproduction order is specified in the read playlist.

The difference from the bit configuration of PLMG_AP_PL is that the fields from bit number b32 to bit number b63 have Play
The point is that the "Playback Time" field for describing the back time is assigned. The fields from bit number b32 to bit number b63 are assigned to the description of Playback_Time in order to specify the previous playback stop point with time accuracy of millisecond. Note that the user is PLMG_R
If SM_PL is not used, all the above-mentioned fields in PLMG_RSM_PL must be set to "0".

{70-4_71} P at the time of transition between playback devices
Setting of LMG_RSM_PL Then, when the flash memory card shown in the second embodiment transfers between a plurality of playback devices, PLMG_AP_PL and PL
Describe how MG_RSM_PL is set. 71 shows PLMG_AP_ when the flash memory card shown in the second embodiment is transferred between a plurality of playback devices.
It is a figure which shows how PL and PLMG_RSM_PL are set. This figure assumes a case where a flash memory card is transferred between a plurality of playback devices such as a general-purpose personal computer → a portable playback device → a vehicle-mounted playback device (these devices are the same as those in the first embodiment). It has the functions of the reproducing apparatus and recording apparatus shown. The AOB file stored in this flash memory card constitutes TrackA to TrackE.
Is the same as that shown in.

First, the flash memory card in the second embodiment is loaded into the personal computer 200, and after the presentation data and navigation data shown in the first embodiment are recorded therein, the personal computer 200 sets PLMG_AP_PL. (Here, the Default_Playlist information is shown.
Playlist_Number "0" and Track_Number "3" indicating TrackC
And shall be set). After that, the AOB files recorded on the semiconductor memory card are changed to TrackA, TrackB, and T.
It is assumed that the operator stops the reproduction when the reproduction of the TrackC having the reproduction time of 5.5 minutes and the reproduction of the order of rackC reaches 3 minutes and 31 seconds. In this case, PLMG_RSM_P
In the L field, by the personal computer 200, Playlist_Number “0” indicating Default_Playlist information.
And Track_Number "3" indicating TrackC are described. At the same time, the point at which playback stopped is 3 minutes 3 from the beginning of TrackC.
"00: 03: 31.000" indicating that one second has passed is PLMG_RS
It is described in the Playback_Time field in M_PL. After that, the flash memory card is assumed to be removed from the personal computer 200 and loaded into the portable player 100 as shown by an arrow my71.

[0254] The portable player 10 in the first embodiment.
The playback device that is 0 started playback from the first AOB_FRAME of Track A specified by Default_Playlist information,
In the second embodiment, PLMG_AP_PL is added to the PlaylistManager information.
And PLMG_RSM_PL are described, it is determined by referring to which AOB_FRAME the reproduction is started.
Here, when the reproduction by the personal computer 200 is stopped, the PLMG_RSM_PL has a Playlist_Number “0” indicating Default_Playlist information and a Track_Numb indicating TrackC.
er "3" and Playback_Time indicating "00: 03: 31.000" are described, the portable player 100 already has the Defa.
It is possible to know that the TrackC specified in the ult_Playlist information has already been played by 3 minutes 31 seconds.
You can know that it is good to play from 3 minutes 31.001 seconds.

It is assumed that the operator wears the headphones attached to the portable player 100 and goes out while listening to the Track C whose reproduction has started. During this time Tr
It is assumed that the operator stops the reproduction when TrackD is reproduced in order such as ackC and TrackD and has a reproduction time of 30.6 minutes until 10 minutes and 30 seconds have elapsed. In this case, PLMG_RSM_PL is set to Default_Pla by the portable player 100.
Playlist_Number "0" indicating ylist information and T indicating TrackD
rack_Number is updated to "4" and "00: 10: 30.000" indicating that the time when the playback is stopped is 10 minutes and 30 seconds after the beginning of TrackD. On the other hand, PLMG_AP_PL is not rewritten, and Playlist_Number "indicating Default_Playlist information is displayed.
0 "and Track_Number" 3 "indicating Track C remain written.

After that, the flash memory card is assumed to be removed from the portable player 100 and loaded into the vehicle-mounted player 300 as shown by the arrow my72. PL
MG_RSM_PL contains a Playlist_ that indicates Default_Playlist information.
Number "0", Track_Number "4" indicating TrackD, and "00: 1
Since Playback_Time indicating 0: 30.000 "is described, the in-vehicle player 300 has already set Default_Playlist.
It is possible to know that the TrackD specified in the information has already been played by 10 minutes and 30 seconds.
You can know that you can play from 01 seconds. It is assumed that the TrackD is played back from this point and then the operator stops the playback when 9 minutes and 30 seconds have passed. In this case, there is an unplayed part left in TrackD.
st_Number and Track_Number are the same, but PLMG_RSM_PL
Playback_Time in is updated to "00: 20: 00.000".

As described above, when the flash memory card is taken out from the personal computer 200 and the reproduction is started in the portable player 100, the reproduction is started from the reproduction time next to the final reproduction time in the personal computer 200. You can see that
Similarly, a flash memory card is a portable player 10.
When it is taken out from 0 and the reproduction is started in the in-vehicle player 300, it is understood that the reproduction is started from the reproduction time next to the final reproduction time in the portable player 100. Even when the flash memory card is transferred from the personal computer 200 to the portable player 100 to the in-vehicle player 300, the portion overlapping with the portion reproduced up to that point is not reproduced.

PLMG_AP_PL when editing the {70-5} TKI,
Update of PLMG_RSM_PL After the description of PLMG_AP_PL and PLMG_RSM_PL is completed, four editing cases described in the first embodiment, when some tracks are deleted (case 1), any two of a plurality of tracks are deleted. How to update PLMG_AP_PL and PLMG_RSM_PL when combining into one track (case3), dividing one track to get two tracks (case4), and changing the order of tracks (case5). Will be explained.

[0259] When the tracks specified by PLMG_AP_PL and PLMG_RSM_PL are deleted (case 1), PlaylistManager
Track in PLMG_AP_PL and PLMG_RSM_PL in information
Set _Number to the track located next to the deleted track. For Playback_Time, the playback start time of the track "00: 00: 00.000"
Set to.

When the track specified by PLMG_AP_PL and PLMG_RSM_PL is integrated with another track (case
3), PLMG_AP_PL and PLMG_ in PlaylistManager information
Track_Number in RSM_PL is updated to the rank after the integration. When the track specified by PLMG_AP_PL and PLMG_RSM_PL is divided (case 4), Track_Num in PLMG_AP_PL and PLMG_RSM_PL in PlaylistManager information
The ber is updated to the first half track and the second half track obtained by the division. That is, the division boundary and Playback_Time are compared, and if Playback_Time exists ahead of the division boundary, the Track_Number of the first half track of the tracks obtained by the division is set to PLMG_RSM_PL. Split boundary and P
Compared with layback_Time, if Playback_Time exists behind the division boundary, set Track_Number of the latter half track among the tracks obtained by division to PLMG_RSM_PL.

When the order of the tracks designated by PLMG_AP_PL and PLMG_RSM_PL is exchanged (case 5), Playlis
Track_Number in PLMG_AP_PL and PLMG_RSM_PL in tManager information is updated to the order after the replacement. PLMG_AP_PL and PLMG_RSM_P along with track editing
Although the case of updating L has been described, when an edit operation is performed, PLMG_AP_PL and PLMG_RSM_PL that have been set so far may be simply deleted.

{72-1} Setting of Which of PLMG_RSM_PL and PLMG_AP_PL to be Referenced Next, the reproducing apparatus according to the second embodiment will be described. The reproducing apparatus in the second embodiment differs from that shown in the first embodiment in three main points. The first difference is that the setting of PLMG_AP_PL and the start setting are accepted from the operator. FIG. 72 shows the operator PLMG_AP_
It is a figure which shows the menu screen for accepting PL setting and starting setting from an operator. In this figure, the character strings "immediately after the previous playback is stopped" and "favorite track" are PL when the flash memory card is loaded.
It is displayed to receive a setting as to which of MG_AP_PL and PLMG_RSM_PL is to be started to reproduce the track (“favorite track” is a track specified by Playlist_Number and Track_Number specified by PLMG_AP_PL. ). By setting via this string,
The playback device sets a flag. This flag is PLMG_A
Playlist_Number, Track_Number described in P_PL
Playback is restarted from P or P described in PLMG_RSM_PL
It is a flag that indicates whether to restart playback from laylist_Number, Track_Number, Playback_Time (called a startup flag). If "immediately after the last playback was stopped" is set, the startup flag is set to ON and the flash memory card At the time of loading, the PLMG_RSM_PL is referred to and the reproduction is started immediately after the point at which the previous reproduction was stopped.

If the "favorite track" is set, the start flag is set to off, and when the flash memory card is loaded, the reproduction can be started from the track described in PLMG_AP_PL. Also, in this menu screen, "Favorite tracks" can be set, and by performing an input operation via the key panel, PLMG_A indicating the Playlist and track specified by the operation.
P_PL will be written to the flash memory card. In addition to the menu screen, the playback device may be provided with a DIP switch or a push-button switch, and these switches may be used to switch the start flag.

Update of {56_57_58-1} PLMG_RSM_PL The above is the first difference. The second difference after this is that if the stop key is pressed during playback, PLMG_RSM_P
This is the point of performing the update process of L. When the stop key is pressed during reproduction in the first embodiment, any one of step S31, step S42, and step S54 in the flowcharts of FIGS. 56, 57, and 58 becomes Yes, and the processing of the flowchart ends. . At this time, PLMG shown below
Write _RSM_PL. That is, when the stop instruction is accepted, the Playli
The Playlist_Number indicating st and the Track_Number corresponding to the audio block being played are specified and PLMG
Write to _RSM_PL and play_shown in the first embodiment.
The playback elapsed time Play_Time at the time when the stop instruction is accepted is identified with reference to time, and this is written in PLMG_RSM_PL as Playback_Time.

PLMG_RSM_PL may be updated not only when the stop key is pressed but also when the pause key is pressed, as in the case of pressing the stop key. In addition, the PlayLi selected when the battery level is low
The st information, Track_Number, and elapsed playback time may be described in PLMG_RSM_PL. In this case, the valid PLMG_RSM_PL is written in the flash memory card even when the reproducing device stops the reproducing process due to the exhaustion of the battery instead of the operator pressing the stop key.

{73-1} Reproduction Position Identification Processing Next, the third difference will be described. In the first embodiment, the AOB files are reproduced in the order specified by the playlist, but in the second embodiment, the reproduction is performed from the specified reproduction position according to the flowchart shown in FIG. Hereinafter, the reproduction position specifying process based on PLMG_AP_PL and PLMG_RSM_PL will be described according to this flowchart.

When the processing of this flowchart is activated,
In step S301, the CPU 10 refers to the activation flag set via the menu shown in FIG.
It is determined which of MG_AP_PL and PLMG_RSM_PL is used when the flash memory card is loaded. Startup flag is PLMG_A
If it indicates P_PL, the process proceeds from step S301 to step S302. CPU1 in step S302
0 refers to PLMG_AP_PL and Play described in this
Track of the playlist specified by list_Number
TKI for the track specified by _Number,
It is specified as TKI # z shown in the first embodiment, and reproduction is started from the AOB file #z corresponding to this.

At step S301, the start flag is
If it is indicated that PLMG_RSM_PL is prioritized, then in step S303, from the PlaylistManager information to PLMG_RSM_PL
Is read, PLMG_RSM_PL is read in step S303, and PLMG read in step S304
Playlist_Number, Track_Numb described in _RSM_PL
er and Playback_Time are judged to be valid. If the writing of PLMG_RSM_PL was not properly performed at the time of the previous playback stop, or if the cluster in which PLMG_RSM_PL is described has a read error, PLMG_RSM_PL is considered to be invalid, and therefore steps S304 to S302 are performed. Then, the playback is started by referring to PLMG_AP_PL.

Playlist_Number, Track_Nu in PLMG_RSM_PL
If mber and Playback_Time are legally described, the process moves from step S304 to step S305, and PLMG
Playback_Time described in _RSM_PL and PLMG_RSM_P
It is determined whether or not the track reproduction time (TKI_PB_TM) for the Track_Number described in L is equal. Pla
If yback_Time and TKI_PB_TM are not equal, Track_N
Since the unplayed portion remains in the track designated by umber, the CPU in step S306
10 identifies the TKI specified by Track_Number in PLMG_RSM_PL as TKI # z, and in step S307,
AOB_ELEME that should start playback from that AOB file based on Playback_Time described in PLMG_RSM_PL
Specify NT # y and AOB_FRAME # x at which playback should start. AOB_ELEMENT # y, A corresponding to the arbitrary playback start time of the track
The process of specifying OB_FRAME # x has already been described in the first embodiment using {Formula 1} to {Formula 3}, and therefore AOB_ELEMENT # is used using these formulas.
y, AOB_FRAME # x is calculated, and then, in step S308, AOB_FR in AOB_ELEMENT # y of AOB file #z.
Playback starts from AME # x.

[0270] If Playback_Time and TKI_PB_TM are equal, step S305 becomes Yes and step S309.
Move to. TKI_PB_TM and Playback_Time are equal, but Track_Number in PLMG_RSM_PL and PlaylistMan
It is determined whether TKI_Ns described in the ager information is equal. If they are not equal, there is an unreproduced track in the Playlist specified by Playlist_Number, so the process moves from step S309 to step S311. In step S311, Track in PLMG_RSM_PL
The TKI next to the TKI specified by _Number is specified as TKI # z, and in step S312, the AOB corresponding to the TKI # z is specified.
AOB playback starts from the beginning of file #z.

TKI_PB_TM and Playback_Time are equal,
In addition, Track_Number in PLMG_RSM_PL and TKI_Ns
If is equal to, it is considered that the reproduction of the playlist specified by the Playlist_Number of PLMG_RSM_PL is completed, so the specification of which playlist is to be reproduced is accepted. As described above, according to the present embodiment, since how much data has been reproduced at the time of the previous reproduction is stored as PLMG_RSM_PL in the semiconductor memory card as the reproduction restart position, the semiconductor memory card is taken out from the reproducing apparatus and another reproducing apparatus is used. , The other playback device can start playback immediately after the previous playback time. Therefore, in some playback devices TrackA ~ Tr
After listening to the music album consisting of ackE halfway, when the playback is stopped and another playback device plays the music album, the other playback device refers to PLMG_RSM_PL described when the previous playback was stopped. Then, at the time of the immediately preceding reproduction, it is possible to specify how much has been reproduced and where has not been reproduced with a time accuracy of millisecond. Therefore, the music album can be played immediately after the already played portion, and even if the semiconductor memory card is transferred, the operator does not listen to the track once listened to. .

(Third Embodiment) {74-1} DPLI_RSM_PL, PLI_RSM_PL In the third embodiment, Default_Playlist information, PLI_RSM_PL, DPLI_RSM_PL are provided for each PlayList information, and PlayList information,
In this embodiment, when the Default_Playlist information is reproduced immediately before, the end of the reproduction range is indicated as the reproduction restart position. In FIG. 74, De that stores DPLI_RSM_PL in DPLGI
fault_Playlist information and PLI_RSM_PL stored in PLGI
It is a figure which shows PlayList information.

DPLI_RSM_PL (PLI_RSM_PL) is Track_Numbe
It differs from PLMG_RSM_PL in that only r and Playback_Time are described, and Playlist_Number need not be described. Also, P
If all the tracks whose reproduction order is specified by the layList information are reproduced, the difference is that the Track_Number in PLI_RSM_PL is set to the FF value indicating that the track is completed.

Next, a reproducing apparatus according to the third embodiment will be described. When the playback of the track specified by the playback order of the PlayList information is interrupted midway, the playback device uses the Playlist_Number of that PlayList information and the Track of the track.
Writing _Number and Playback_Time to PLMG_RSM_PL is the same as in the second embodiment, but in the third embodiment,
In the Playlist_Number PLI_RSM_PL, the track Track
Write _Number and Playback_Time.

[0275] Also, via the menu, any PlayList
Information can be specified as in the first embodiment, but in the third embodiment, PLI_of the specified PlayList information is specified.
Refer to RSM_PL, Track_Number of that PLI_RSM_PL, Play
If no value is written to back_Time, the PlayL
The tracks whose playback order is specified by the ist information are played back from the beginning. PLI_RSM_PL of the specified PlayList information
If values are written in Track_Number and Playback_Time, the tracks whose reproduction order is specified by the PlayList information are reproduced according to Track_Number and Playback_Time.

{74-2_75_76} FIG. 75 is a diagram showing a track sequence having the reproduction order designated by the play list shown in FIG. 41 of the first embodiment. See also FIG.
Is Default_Playlist information, DPLI_RSM of each PlayList information
It is a figure which shows how _PL is set. Def
Since the ault_Playlist information, PLI # 1, and PLI # 2 are specified, the track sequence is the playback range of FIG.
It is assumed that partial reproduction is performed as indicated by (1), reproduction range (2), and reproduction range (3). Play range (1) -Play range (3)
After being played like Default_Playlist info, PLI #
The range from which the reproduction of each track sequence is restarted when 1 and PLI # 2 are respectively specified will be described.

When the {74-3_75_76} Default_Playlist information is specified, the reproduction of the track sequence is interrupted during the reproduction of TrackC, so the Track_Number and Playback_Time "4" indicating the reproduction restart position (4) at the end of the reproduction range (1) are set. Trac
kC 00: 03: 31.0000 ”is DPLI_RS of Default_Playlist information.
It is set to M_PL.

As for PLI # 1, as shown in the playback range (3), the playback of the track sequence has been completed, so PLI # 1
Track_Number of PLI_RSM_PL is set to “FF”. When PLI # 2 is specified, the playback of the track sequence was interrupted during the playback of TrackA, so the playback range (2)
Track_Number, Pla indicating the playback restart position (5) at the end of the
yback_Time “TrackA 00: 01: 11.0000” is PLI_RS of PLI # 2
It is set to M_PL.

Since PLI # 3 is not specified and the track sequence is not reproduced, Track_Num of PLI_RSM_PL of PLI # 3
ber is set to "00". Since Default_Playlist information and DPLI_RSM_PL of each PlayList information are set as shown in FIG. 75, after specifying PLI # 1, Default_Playlis
If you specify the t information, Defau will start immediately after the playback range (1) (4).
Playback of the track sequence for the lt_Playlist information will be resumed.

By specifying Default_Playlist information, Defaul
After all track sequences of t_Playlist information have been played, if PLI # 2 is specified, from the point (5) immediately after the playback range (2), the P
Playback of the LI # 2 track sequence will start. As described above, according to the present embodiment, when the operation is performed by the operator and the playlist to be reproduced is designated, the PLGI (or DPLGI) for the playlist is specified.
The PLMG_RSM_PL is taken out from and the playback of the track is restarted according to the Track_Number and Playback_Time indicated in this PLMG_RSM_PL. Therefore, even if playback is performed by specifying PlayList information, duplicate playback can be avoided. .

In the present embodiment, Default_Playli
Since reproduction of st information and each PlayList information is restarted based on Track_Number and Playback_Time indicated in DPLI_RSM_PL, when accepting designation of each PlayList information from the operator, as shown in FIG. 49 of the first embodiment. It is desirable to accept the designation from the user via the menu as shown in FIG. 77, rather than simply displaying the list of playlists. FIG. 77 is a diagram showing an example of a menu screen in which the setting contents of DPLI_RSM_PL at the time when the reproduction range (1) to the reproduction range (3) are reproduced are displayed in association with each play list. DPLI_RSM_P for PlayList information that has tracks that have not been played
Track number specified by Track_Number of L and P
The playback time based on layback_Time is displayed.
Regarding the PlayList information in which the reproduction of all the designated tracks is completed, the Track_Number of DPLI_RSM_PL is set to the FF value, and accordingly, it is displayed that the reproduction of the PlayList information is completed. By referring to such a menu screen, the operator can easily remember how much each playlist has been listened to. Also, PLI #
As in 1, it is possible to know how many playlists have completed the reproduction of the track sequence, and which playlist has not yet reproduced the track sequence.

(Fourth Embodiment) In the first to third embodiments, the music application is stored in the flash memory card 31.
Stored in the flash memory card 31, the present invention relates to an improvement in storing a temporary application in the flash memory card 31. A transient application is an application such as a news application, a speech at a performance, a magazine, etc., which is sufficient to listen to once, and is not of the nature of repeated listening, such as a music application, especially a magazine or the like. For weekly and monthly updates, for news, daily updates will be sent.

When the recording device downloads such a transient application via the network, the audio data forming the transient application is stored in the flash memory card 31 as a plurality of AOBs, and the TKI for each AOB is stored. Are generated and stored in the flash memory card 31. In addition, PlayList information that specifies a TKI for a transient application is also generated and stored in the flash memory card 31, like the TKI.

[0284] Next, Default_Pl in the fourth embodiment.
The improvements in aylist information, PlayList information, and TKI will be described. In the second embodiment, PLI_APP_ATR is provided in the PlayListManager as information indicating the application attribute, but in the fourth embodiment, PLI_APP_ATR, TK is set as information indicating the application attribute in DPLGI, PLGI, TKGI.
I_APP_ATR is provided. FIG. 78 is a diagram showing data formats of DPLGI, PLGI, and TKGI according to the fourth embodiment. Like PLI_APP_ATR in the second embodiment, PLI_APP_ATR in PLGI describes an application category ID indicating which category the PlayList information belongs to. When the genre of the application stored in this flash memory card is a music genre, "01h" is described in this field. On the other hand, "02h" is described when the genre of the application stored in the flash memory card is karaoke software, "03h" is described when it is presentation data, and "04h" is described when it is a reading book. For other genres, other values are described. PlayLi about transient applications
In the st information, PLI_APP_ATR in PLGI is set to "04h" indicating a reading book.

[0285] In this way, the PlayList information about the transient application is generated, and the transient application is stored in the flash memory card 31 in association with it. Next, a problem that occurs when a temporary application is stored in the flash memory card 31 will be described. The latest application of the news genre is sent every day. Therefore, if these applications are accumulated in the flash memory card 31 one by one, the limited storage capacity of the flash memory card 31 will be instantly reached. It is occupied only by the transient application.

[0286] In order to prevent the occupation due to such a transient application, it is desirable to perform the following control with reference to PLI_RSM_PL and PLI_APP_ATR. Since such a transient application is stored in the flash memory card 31 together with PlayList information in which PLI_APP_ATR is set as the reading book genre, this PLI_APP_AT
If you refer to R, you can use P for transient applications.
It becomes clear which is the layList information, TKI, or AOB. On the other hand, with regard to PlayList information that is PlayList information set for a transient application and has already completed playback of a track whose playback order has been specified, Track_Number in PLI_RSM_PL for PlayList information becomes the value of the FF value. For tracks whose playback order has been set and whose playback order has been specified, since Track_Number in PLI_RSM_PL for Default_Playlist information is set to a value other than FF, Track_Number in DPLI_RSM_PL is set to F.
By checking whether or not the value is the F value, it is possible to determine whether the reproduction of the transient application is completed or incomplete. After these checks, if the TKI, AOB, and PlayList information for the transient applications for which track playback has been completed is erased, a large number of transient applications will be stored and stored in the flash memory card 31. Can avoid pressure. Note that the explanation of the above control is PLI_RSM_PL and PL.
I did for I_APP_ATR, but DPLI_RSM_PL and DPLI
Similar control may be performed for _APP_ATR.

As described above, according to the present embodiment, when a temporary application such as news is downloaded and stored in the flash memory card 31, the temporary applications are reproduced in order from the reproduced one. Since the temporary application is erased, even if the temporary application is transmitted every day, it is possible to prevent the flash memory card 31 from being occupied by only the temporary application.

[0288]

According to the reproducing apparatus for the semiconductor memory card of the present invention, the operator performs the first reproducing operation with any audio object specified or the second reproducing operation with no audio object specified. And a first reproducing operation, the specified audio object in the audio sequence is reproduced, and a second reproducing operation is received, the resume information is read from the semiconductor memory card, and the first reproduction operation is performed. Playback means for restarting playback of the audio sequence from the restart position indicated by the position information or the second position information, and storage means for storing a flag indicating whether to use the second position information or the first position information. If the flag indicates that the first position information is to be used, the reproducing means includes the first position. When the reproduction is performed based on the information, and the flag indicates that the second position information is used, the reproduction is performed based on the second position information. Therefore, the audio sequence corresponds to the music album. It is assumed that the audio sequence is listened to halfway in the reproducing apparatus having this audio sequence. After that, if the semiconductor memory card is loaded into another playback device, this other playback device restarts playback of the audio sequence from the playback restart position indicated in the resume information.

Since the reproduction restart based on the resume information is performed without any operation by the operator, when the semiconductor memory card is loaded into another reproducing device, the reproducing operation is performed in the other reproducing device. There is no need to bother the operator to specify a music piece (audio object) to be played.

[0290] In addition, after listening to a music album halfway through a certain playback device, the playback is stopped, and when that playback device plays that music album, the other playback device will not play back the already played portion. Immediately after that, the music album can be played back, and even if the semiconductor memory card is transferred, the operator does not endure listening to the song once listened to.

[0291] Even when frequently listening to a music album listened to by one playback device, such as when listening to a music album obtained by electronic music distribution, is performed by another playback device, another playback is performed. The device can avoid duplicate reproduction of the reproduced portion.

[Brief description of drawings]

FIG. 1 is a diagram showing a shape of a flash memory card 31 when viewed from above.

FIG. 2 is a diagram showing a shape of a flash memory card 31 when viewed from the bottom surface thereof.

FIG. 3 shows a flash memory card 31 according to this embodiment.
It is a figure which shows the hierarchical structure of.

FIG. 4A is a diagram showing a configuration of a system area, a protect area, and a user data area provided in a physical layer of the flash memory card 31. FIG. 6B is a diagram showing a configuration of a protect area and a user data area in the file system layer.

FIG. 5 is a diagram showing details of a configuration in a file system layer.

[Figure 6] AOB001.SA1 is divided into five parts according to the cluster size, and each divided part is divided into clusters 003,004,005,00A, 00C
It is the figure which assumed the state stored in.

FIG. 7 is a diagram showing a setting example of a directory entry and a file allocation table when AOB001.SA1 is recorded in a plurality of clusters.

FIG. 8A and FIG. 8B, when storing these two data in the application layer, what directory is configured in the user data area and protect area in the file system layer, and what file is the directory. It is a figure which shows whether it is created under the control of.

[Figure 9] AOBSA1.KEY under the SD_Audio directory
It is a figure which shows the correspondence with AOB file.

FIG. 10 is a diagram hierarchically showing the data structure of an AOB file.

FIG. 11A is a diagram showing, in a tabular form, parameters described in ISO / IEC13818-7. (B) It is a figure which shows the parameter which should be used when encoding by a MPEG-Layer3 (MP3) system in a table format. (C) It is a figure which shows the parameter which should be used when encoding by a Windows (trademark) Media Audio (WMA) system in a table format.

FIG. 12 is a diagram showing details of the configuration of AOB_FRAME.

[Fig. 13] AOB_FR of three AOB_FRAMEs
It is a figure which shows how the byte length of the audio data in AME is set.

FIG. 14 is a diagram showing a correspondence between sampling_frequency and the number of AOB_FRAME included in AOB_ELEMENT.

FIG. 15 is a diagram illustrating an example of a time length of AOB_ELEMENT and a time length of AOB_FRAME.

FIG. 16: AOB and AOB_BL recorded in the AOB file
It is a figure which shows what kind of reproduction content is reproduced by reproducing OCK continuously.

FIG. 17: Playlist manager and T in the first embodiment
It is the figure which detailed the structure of rackManager in steps.

FIG. 18 is a diagram showing sizes of PlayListManager and TrackManager.

19 is a diagram showing a mutual relationship between the TKI shown in FIG. 17 and the AOB file and AOB shown in FIG.

20 is a diagram showing a detailed data structure of TKTMSRT shown in FIG.

FIG. 21 is a diagram showing an example of TKTMSRT.

FIG. 22 is a diagram showing a detailed configuration of TKGI.

FIG. 23 is a diagram showing a detailed configuration of (a) and (b) BIT. It is a figure which shows the data format of (c) TIME_LENGTH field.

[Fig. 24] Fig. 24 is a diagram illustrating clusters 007 to 00E in which AOBs composed of AOB_ELEMENT # 1 to # 4 are stored.

Figure 25: AOB_FR in any AOB_ELEMENT # y in AOB
FIG. 11 is a diagram showing how to set AOB_FRAME # x + 1 to be reproduced next when performing forward search reproduction from AME # x.

26A and 26B are AOB, AOB_ELEMENT, and AO corresponding to the designated time when an arbitrary playback start time is designated.
It is a figure which shows how to identify B_FRAME.

FIG. 27 is a diagram assuming a case where (a) and (b) tracks are deleted.

FIG. 28A shows a track after the track is deleted a plurality of times.
It is a figure which shows TrackManager. (B) There is a TKI of "Unused", and there is a new T here.
It is a figure which shows how the writing is performed, when writing a KI and AOB file.

29 (a) and 29 (b) are diagrams showing how TKIs are set when two tracks are integrated.

FIG. 30 is a diagram showing (a) Type 1 AOB. (B) It is a figure which shows AOB of Type2.

FIG. 31A is a diagram showing a case where a plurality of tracks are integrated into one by a combination of Type1 + Type2 + Type2 + Type1. (B) A diagram showing a case where a plurality of tracks are integrated into one by a combination of Type1 + Type2 + Type2 + Type2 + Type1.

[FIG. 32] (a) Type 1 AOB at the end of the preceding track
FIG. 3 is a diagram showing an arrangement pattern in which the AOB of Type 1 is arranged at the beginning of the subsequent track. (B) A Type 1 AOB is placed at the end of the preceding track,
FIG. 7 is a diagram showing an arrangement pattern in which a Type 2 AOB is arranged at the beginning of a subsequent track. (C) AO in the order of Type1 and Type2 at the end of the preceding track
FIG. 9 is a diagram showing an arrangement pattern in which B is arranged and a Type 1 AOB is arranged at the beginning of the subsequent track. (D) AO at the end of the preceding track in the order of Type1 and Type2
B is arranged and Type2 and Type1 are added at the beginning of the following tracks.
It is a figure which shows the arrangement pattern in which the AOB of FIG. (E) Type2, Type2 AOB at the end of the preceding track
FIG. 3 is a diagram showing an arrangement pattern in which the AOB of Type 1 is arranged at the beginning of the subsequent track.

33 (a) and (b) are diagrams assuming a case where one track is divided into two tracks.

FIG. 34 (a) and (b) before and after division, AOB003.SA1
FIG. 3 is a diagram showing how an SD_Audio directory entry for an SD_Audio directory to which is belongs is described.

[Fig. 35] Fig. 35 (a) is a diagram assuming a case where an AOB is divided in the middle part of AOB_ELEMENT # 2. (B) AOB is divided in the middle of AOB_ELEMENT # 2, and AO
It is a figure showing the state where two AOBs, B # 1 and AOB # 2, were obtained.

FIG. 36 is a diagram showing how BIT is set when the AOB is divided as shown in FIG. 35.

FIG. 37 is a diagram specifically showing how BIT changes before and after division.

[Fig. 38] Fig. 38 is a diagram specifically showing how TKTMSRT changes before and after division.

FIG. 39 (a) is a diagram showing a format of DPL_TK_SRP. (B) It is a figure which shows the format of PL_TK_SRP.

[Fig. 40] Fig. 40 is a diagram illustrating a mutual relationship between Default_Playlist information, a TKI, and an AOB file.

[Fig. 41] Fig. 41 is a diagram illustrating a setting example of DefaultPlaylist and PlayList information in the same notation as in Fig. 40.

[FIG. 42] DPL_TK_SRP and TK using the same notation as in FIG.
It is a figure which shows the correspondence with I.

43 (a) and 43 (b) are diagrams assuming a case where the order of the tracks is changed.

44 (a) and (b) DefaultPlaylis shown in FIG. 40.
Deta when deleting DPL_TK_SRP # 2 and TKI # 2 of t
It is a figure which shows how ultPlaylist, TrackManager, and an AOB file are updated.

[Fig. 45] (a) and (b) TKI of "Unused" and DPL_TK_SR
FIG. 14 is a diagram showing how P and P exist and write a new TKI, DPL_TK_SRP, here.

46 (a) and 46 (b) are diagrams assuming a case where tracks are integrated.

47A and 47B are diagrams supposing a case where tracks are divided.

FIG. 48 is a flash memory card 3 according to the present embodiment.
FIG. 3 is a diagram showing a portable playback device for No. 1.

FIG. 49 is a diagram showing an example of display contents of a liquid crystal display when a playlist is selected.

FIG. 50 is a diagram showing an example of the display contents of the liquid crystal display when the tracks (a) to (e) are selected.

FIG. 51 is a diagram showing an operation example of the jog dials (a) to (c).

[Fig. 52] Fig. 52 is a diagram illustrating an internal configuration of a playback device.

FIG. 53 is a diagram showing how data input / output is performed in the double buffer 15.

54 (a) and 54 (b) are diagrams showing how a cyclic area is secured using a ring pointer.

FIG. 55 is a flowchart showing a processing procedure of AOB file reading processing.

FIG. 56 is a flowchart showing a processing procedure of AOB_FRAME output processing.

FIG. 57 is a flowchart showing a processing procedure of AOB_FRAME output processing.

FIG. 58 is a flowchart showing a processing procedure of AOB_FRAME output processing.

59 (a) to (d) are diagrams showing a state in which the elapsed playback time displayed in the time display frame of the liquid crystal display 5 increases as the variable Play_Time is updated.

FIG. 60 is a flowchart showing a processing procedure of the CPU 10 at the time of forward search reproduction processing.

FIG. 61 (a) to (d) are diagrams showing how the reproduction elapsed time is incremented during forward search reproduction.

FIG. 62 is a diagram showing a specific example of the case where the time search function is performed in (a) and (b).

FIG. 63 is a flowchart showing a processing procedure of an edit control program.

FIG. 64 is a flowchart showing a processing procedure of an edit control program.

FIG. 65 is a flowchart showing a processing procedure of an editing control program.

66 is a diagram showing an example of a recording device of the flash memory card 31. FIG.

FIG. 67 is a diagram illustrating a hardware configuration of a recording device.

FIG. 68 is a flowchart showing a processing procedure of recording processing.

[FIG. 69] PlayListManager and Tra in the second embodiment
It is a figure which shows the internal structure of ckManager.

[Fig. 70] Fig. 70 is a diagram illustrating a detailed configuration of Playlist Manager information.

FIG. 71 is a diagram showing how PLMG_AP_PL and PLMG_RSM_PL are set when the flash memory card shown in the second embodiment transfers between a plurality of playback devices.

[Fig. 72] Fig. 72 is a diagram illustrating a menu screen for accepting the setting of PLMG_AP_PL and the activation setting from the operator.

[Fig. 73] Fig. 73 is a flowchart illustrating a processing procedure of playback position identification processing based on PLMG_AP_PL and PLMG_RSM_PL.

Fig.74 DPLGI, Pla about Default_Playlist information
It is a figure which shows the data structure when the upper 6 bytes of PLMG_RSM_PL are stored in PLGI about yList information.

[Fig. 75] Default_Playlist information, DP of each PlayList information
It is a figure which shows how LI_RSM_PL is set.

[Fig. 76] Fig. 76 is a diagram showing a track sequence having a reproduction order designated by the play list shown in Fig. 41 of the first embodiment.

[Fig. 77] Fig. 77 is a diagram illustrating an example of a menu screen in which the setting contents of DPLI_RSM_PL at the time when the reproduction ranges (1) to (3) are reproduced are displayed in association with each play list.

FIG. 78 is a diagram showing data formats of DPLGI, PLGI, and TKGI according to the fourth embodiment.

[Explanation of symbols]

1 card connector 2 User interface section 3 RAM 4 ROM 5 LCD display 6 LCD driver 7 De Scrambler 8 AAC decoder 9 A / D converter 11 DPLI resident area 12 PLI storage area 13 TKI storage area 14 FileKey storage area 15 double buffer 21 card connector 22 RAM 23 Fixed disk device 24 converter 24 A / D step S 25 AAC encoder 26 Scrambler 27 Modem equipment 28 CPU 29 keyboard 30 Display 31 flash memory card 32 Protect switch 100 portable players 200 personal computer 300 car player

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Tomokazu Ishikawa             1006 Kadoma, Kadoma-shi, Osaka Matsushita Electric             Sangyo Co., Ltd. (72) Inventor Shinji Inoue             1006 Kadoma, Kadoma-shi, Osaka Matsushita Electric             Sangyo Co., Ltd. (72) Inventor Hideki Matsushima             1006 Kadoma, Kadoma-shi, Osaka Matsushita Electric             Sangyo Co., Ltd. (72) Inventor Masayuki Kozuka             1006 Kadoma, Kadoma-shi, Osaka Matsushita Electric             Sangyo Co., Ltd. F-term (reference) 5B035 BA02 BB09 BB11 BC05 CA29                       CA38                 5D045 DB01 DB02

Claims (9)

[Claims] 1. An audio sequence formed by arranging a plurality of audio objects, and resume information indicating a restart position in the case of automatically restarting playback from the middle of the audio sequence after playback interruption, are stored. , Including first position information and second position information,
A semiconductor memory card in which the first position information indicates a first restart position set through a user operation, and the second position information indicates a second restart position automatically set at a previous playback stop. And a receiving means for receiving from the operator a first reproduction operation that specifies any audio object or a second reproduction operation that does not specify any audio object, and a first reproduction operation. Is received, the designated audio object in the audio sequence is played back, and when the second playback operation is received, the resume information is read from the semiconductor memory card and displayed in the first position information or the second position information. Whether to use the reproduction means for restarting the reproduction of the audio sequence from the restarted position and the second position information And a storage means for storing a flag indicating whether to use the first position information, said reproducing means, if the flag indicates that the use of the first location information,
If the reproduction is performed based on the first position information and the flag indicates that the second position information is used,
A playback device that plays back based on the second position information. 2. The second position information indicates a restart position in an audio sequence by using identification information of any one audio object and time information indicating an offset from the head of the audio object to the restart position, When restarting the reproduction of the audio sequence based on the second position information, the reproducing means performs the reproduction process from the midway position indicated by the time information in the audio object indicated by the identification information included in the second position information. The playback device according to claim 1. 3. The reception means further includes second position information,
The reproduction according to claim 1, further comprising a setting unit that receives an operation indicating which one of the first position information is used from the operator, and sets a flag stored in the storage unit according to the operation received by the reception unit. apparatus. 4. An audio sequence formed by arranging a plurality of audio objects, and resume information indicating a restart position in the case of automatically restarting playback from the middle of the audio sequence after the playback is interrupted are stored. , Including first position information and second position information,
A semiconductor memory card in which the first position information indicates a first restart position set through a user operation, and the second position information indicates a second restart position automatically set at a previous playback stop. Is a recording medium having a computer-readable format recording a program for causing a computer to perform the reproduction procedure for, the first reproduction operation specifying any audio object, or specifying any audio object. An accepting step for accepting a second reproducing operation that is not performed from the operator; and, when accepting the first reproducing operation, reproducing the designated audio object in the audio sequence, and accepting the second reproducing operation, the semiconductor memory card The resume information is read out and displayed in the first position information or the second position information. And a storage step of storing a flag indicating whether the second position information is used or the first position information is used, the reproduction step including: If it indicates that 1 position information is used,
If the reproduction is performed based on the first position information and the flag indicates that the second position information is used,
A computer-readable recording medium on which is recorded a program that causes a computer to perform a procedure of performing reproduction based on the second position information. 5. The second position information indicates a restart position in an audio sequence by using identification information of any one audio object and time information indicating an offset from the head of the audio object to the restart position, In the reproducing step, when the reproduction of the audio sequence is resumed based on the second position information, the reproduction process is performed from the midway position indicated by the time information in the audio object indicated by the identification information included in the second position information. The computer-readable recording medium according to claim 4. 6. The accepting step further accepts an operation indicating whether to use the second position information or the first position information from an operator, and the storage means stores the operation according to the operation accepted by the accepting step. 5. The computer-readable recording medium according to claim 4, further comprising a setting step of setting a flag that is ON. 7. An audio sequence formed by arranging a plurality of audio objects, and resume information indicating a restart position in the case of automatically restarting playback from the middle of the audio sequence after playback interruption, are stored. , Including first position information and second position information,
A semiconductor memory card in which the first position information indicates a first restart position set through a user operation, and the second position information indicates a second restart position automatically set at a previous playback stop. And a second reproducing operation in which any audio object is specified, or a second reproducing operation in which no audio object is specified, and a first reproducing operation. Is received, the designated audio object in the audio sequence is played back, and when the second playback operation is received, the resume information is read from the semiconductor memory card and displayed in the first position information or the second position information. The reproduction step for restarting the reproduction of the audio sequence from the restarted position, and the second position information. Dolphin, and a storage step of storing a flag indicating whether to use the first position information, said reproduction step, if the flag indicates the fact of using the first position information,
If the reproduction is performed based on the first position information and the flag indicates that the second position information is used,
A reproducing method of reproducing based on the second position information. 8. The second position information indicates a restart position in an audio sequence by using identification information of any one audio object and time information indicating an offset from the head of the audio object to the restart position, In the reproducing step, when the reproduction of the audio sequence is resumed based on the second position information, the reproduction process is performed from the midway position indicated by the time information in the audio object indicated by the identification information included in the second position information. The reproducing method according to claim 7. 9. The receiving step further receives from the operator an operation indicating whether to use the second position information or the first position information, and the storage means stores the operation according to the operation received by the receiving step. The reproducing method according to claim 7, further comprising a setting step of setting a flag indicating that the flag is set.