US20100002874A1 - Information processing apparatus and method - Google Patents

Abstract

The present invention relates to an information apparatus and method suitable for use in upgrading control programs readily by a user. In step S501, a storage area to store an upgraded firmware is determined. In step S502, the upgraded firmware is provided. In step503, the provided firmware is decrypted and re-encrypted. In step S504, re-encrypted firmware is written into the storage area determined in step S501. In step S505, a maximum marker is detected. In step S506, a value obtained by adding 1 to the maximum marker provides the marker corresponding to the storage area in which the firmware was stored in step S504. The present invention is applicable to, for example, an audio data server.

Description

CROSS REFERENCES TO RELATED APPLICATIONS
• The present invention is a continuation application of U.S. application Ser. No. 10/399,299, filed Apr. 15, 2003, which claims priority under 35 U.S.C. 371 and 37 CFR 1.495 to International Application Serial No. PCT/JP02/006800, filed Jul. 4, 2002, which, in turn, claims priority under 35 U.S.C. §119 to Japanese Patent Application No. JP 2001-252912, filed in the Japanese Patent Office on Aug. 23, 2001, the entire contents of which being incorporated herein by reference.
TECHNICAL FIELD
• The present invention relates to an information processing apparatus and method and, more particularly, to an information apparatus and method suitable for use in upgrading prepared control programs.
BACKGROUND ART
• Information processing apparatuses are known in which various processes are executed in accordance with a control program.
• However, conventional information processing apparatuses are not adapted to allow users themselves to upgrade (rewrite) control programs.
• To be more specific, if users of earlier-version apparatuses want to use the functions of newly developed control programs, the user must eventually purchase the apparatuses installed with the newly developed control programs.
• In addition, because the users cannot upgrade control programs, if control programs have bugs or the like, the manufacturers of the affected information processing apparatuses must recall them for the rewriting of the control programs.
• Namely, the manufacturers of these information processing apparatuses must use time and labor for apparatus recall and control program rewriting and be extremely careful in fixing the bugs, which requires a great deal of time for control program development.
DISCLOSURE OF INVENTION
• It is therefore an object of the present invention to provide an apparatus that allows users to upgrade control programs with ease.
• The first information processing apparatus according to the present invention is characterized in that it includes:
• detection means for detecting either one of two or more storage areas each storing a program, the one storage area having the oldest update information, or a storage area storing no program; and
• storage means for storing another program into the storage area detected by the first detection means.
• The first information processing apparatus according to the present invention may further include:
• second detection means for detecting one of the programs that has most recent update information in a predetermined timed relation; and
• instruction means for instructing the execution of the program detected by the second detection means.
• The predetermined timed relation may be immediately after a power-on sequence.
• The storage areas are arranged in a first information storage medium, and the instruction means may load the program detected by the second detection means into a second information storage medium and then may execute the loaded program.
• The first information storage medium may be a flash RAM and the second information storage medium may be a synchronous DRAM.
• The first information processing apparatus according to the present invention may further include:
• decryption/encryption means for decrypting the encrypted another program and encrypting the decrypted another program again, and the instruction means may decrypt the encrypted program detected by the second detection means, may load the decrypted program into the second information storage medium, and then may instruct the execution of the loaded program.
• The another program is updated one of the programs, and may further include input means for inputting the updated program.
• The first information processing method according to the present invention is characterized in that it includes:
• a detection step for detecting either one of two or more storage areas each storing a program, the one storage region storage area having the oldest update information, or a storage area storing no program; and
• a storage step for storing another program into the storage area detected by the first detection step.
• The first program of the storage medium according to the present invention is characterized in that it includes:
• a detection step for detecting either one of two or more storage areas each storing a program, the one storage region storage area having the oldest update information, or a storage area storing no program; and
• a storage step for storing another program into the storage area detected by the first detection step.
• The first program according to the present invention is characterized in that it causes a computer to execute:
• a detection step for detecting either one of two or more storage areas each storing a program, the one storage region storage area having the oldest update information, or a storage area storing no program; and
• a storage step for storing another program into the storage area detected by the first detection step.
• The second information processing apparatus according to the present invention is characterized in that it includes:
• a first information storage medium having a control program for controlling the entire apparatus, a load program for reading the control program and loading the control program into another information storage medium, an execution instruction program for instructing the execution of the loaded program, update information indicative of an update situation of an area in which programs are stored, a read program for reading a program from an external information storage medium, and a write program for writing the program read by the read program into the program storing area;
• a second information storage medium for storing the program loaded by the load program; and
• a controller for performing control such that the load program loads, when power is turned on, a part of the program into the second information storage medium in accordance with update information stored in the first information storage medium, the execution instruction program executes the loaded control program, the read program loaded in the second information storage medium reads a program from an external information storage medium in response to a user request during the execution of the control program, and the write program loaded in the second information storage medium writes the program read by the read program into the first information storage medium.
• The first information storage medium has a first area and a second area, and the first area may have at least the load program for reading a program stored in the second area and loading this program into the second information storage medium, the execution instruction program, and update information indicative of an update situation of the second area and the second area may have at least the read program, the write program, and the control program.
• The controller, when power is turned on, may perform control such that the update information stored in the first area of the first information storage medium for most recent update information is searched, and the load program loads the program corresponding to the searched area into the second information storage medium, and the execution instruction program executes the loaded control program.
• The controller, in response to a user request, may search the update information stored in the first information storage medium for the oldest update information or update information indicative that the area is still free, may read a program from an external information storage medium as executed by the read program loaded in the second information storage medium, may write the program as executed by the write program loaded in the second information storage medium into a predetermined area, corresponding to the retrieved update information, in the first information storage medium, and may rewrite the update information corresponding to the predetermined area to most recent update information.
• The first area may have at least a first read program for reading an encrypted program from an external information storage medium and instructing the decryption thereof, the load program for reading an encrypted program in the second area from the first information storage medium, instructing the decryption thereof, and loading the decrypted program in the second information storage medium, the execution instruction program, and update information indicative of update situations of all areas subsequent to the second area, and the second area may have at least a second read program for reading an encrypted program from an external information storage medium and instructing the decryption thereof, the write program for encrypting again the program read and decrypted by the second read program and writing the encrypted program to the second area, and an encrypted control program for controlling the entire apparatus.
• The controller, in response to a user request, may search the update information in the first information storage medium for the oldest update information or update information indicative that the area is still free, may read an encrypted program from an external information storage medium and instructs the decryption thereof as executed by the read program loaded in the second information storage medium, may encrypt again the decrypted program and writes the encrypted program to a predetermined area corresponding to the retrieved update information, in the first information storage medium as executed by the write program loaded in the second information storage medium, and may rewrite the update information corresponding to the predetermined area to most recent update information.
• The second information processing method according to the present invention is characterized in that it includes the steps of:
• when power is turned on, loading, by the load program, a part of the program into the second information storage medium in accordance with update information stored in the first information storage medium, executing the loaded control program by the execution instruction program, and in response to a user request during the execution of the control program, reading a program from an external information storage medium as executed by the read program loaded in the second information storage medium, and
• writing the program read by the read program to the first information storage medium as executed by the write program loaded in the second information storage medium.
• The second program of the storage medium according to the present invention is characterized in that it includes the steps of:
• when power is turned on, loading, by the load program, a part of the program into the second information storage medium in accordance with update information stored in the first information storage medium, executing the loaded control program by the execution instruction program, and
• in response to a user request during the execution of the control program, reading a program from an external information storage medium as executed by the read program loaded in the second information storage medium, and
• writing the program read by the read program to the first information storage medium as executed by the write program loaded in the second information storage medium.
• The second program according to the present invention is characterized in that it causes a computer to execute the steps of:
• when power is turned on, loading, by the load program, a part of the program into the second information storage medium in accordance with update information stored in the first information storage medium, executing the loaded control program by the execution instruction program, and
• in response to a user request during the execution of the control program, reading a program from an external information storage medium as executed by the read program loaded in the second information storage medium, and
• writing the program read by the read program to the first information storage medium as executed by the write program loaded in the second information storage medium.
• In the first information processing apparatus according to the present invention, either one of two or more storage areas each storing a program, the one storage area having the oldest update information, or a storage area storing no program is detected, and
• another program is stored into the storage area detected by the first detection means.
• In the second information processing apparatus according to the present invention, the load program loads, when power is turned on, a part of the program into the second information storage medium in accordance with update information stored in the first information storage medium, the execution instruction program executes the loaded control program, the read program loaded in the second information storage medium reads a program from an external information storage medium in response to a user request during the execution of the control program, and the write program loaded in the second information storage medium writes the program read by the read program into the first information storage medium.
BRIEF DESCRIPTION OF DRAWINGS
• FIG. 1 is a schematic diagram illustrating an overview of anaudio server1 practiced as one embodiment of the invention.
• FIG. 2 is an external view of theaudio server1.
• FIG. 3 is a top view of theaudio server1.
• FIG. 4 is a rear view of theaudio server1.
• FIG. 5 is an elevational view of theaudio server1.
• FIG. 6 is a block diagram illustrating an exemplary hardware configuration of theaudio server1.
• FIG. 7 is a diagram illustrating firmware which is executed by theaudio server1.
• FIG. 8 is a diagram illustrating a FAT file system (data format) applied to aHDD58.
• FIG. 9 is a diagram illustrating a logical structure of afile recording area121.
• FIG. 10 is a diagram illustrating a configuration of aFAT141.
• FIG. 11 is a diagram illustrating one example of theFAT141.
• FIG. 12 is a diagram illustrating an exemplary record of afile recording area121.
• FIG. 13 is a diagram illustrating a structure of asize recording area151.
• FIG. 14 is a flowchart describing a file creating process.
• FIG. 15 is a flowchart describing a free cluster retrieving process.
• FIG. 16 is a flowchart describing FAT entry reading process.
• FIG. 17 is a flowchart describing a linking process.
• FIG. 18 is a flowchart describing a file X reading process.
• FIG. 19 is a flowchart describing a file X searching process.
• FIG. 20 is a flowchart describing a file X reverse reading process.
• FIG. 21 is a diagram illustrating a logical structure of anobject recording area122.
• FIG. 22 is a diagram illustrating a structure of an objecttype recording area163.
• FIG. 23 is a diagram illustrating an areainformation recording area164.
• FIG. 24 is a diagram illustrating anobject managing block124.
• FIG. 25 is a diagram illustrating asession managing information181.
• FIG. 26A is a diagram illustrating abasic object type1.
• FIG. 26B is a diagram illustrating abasic object type2.
• FIG. 27 is a diagram illustrating a structure an object identifier.
• FIG. 28 is a flowchart describing an object creating process.
• FIG. 29 is a flowchart describing a session opening process.
• FIG. 30 is a flowchart describing a free entry allocating process.
• FIG. 31 is a flowchart describing a write session establishing process.
• FIG. 32 is a flowchart describing a session discarding process.
• FIG. 33 is a flowchart describing an object searching process.
• FIG. 34 is a flowchart describing an entry retrieving process.
• FIG. 35 is a flowchart describing an object updating process.
• FIG. 36 is a flowchart describing a stream object creating process.
• FIG. 37 is a flowchart describing a stream object searching process.
• FIG. 38 is a diagram illustrating an object directory structure.
• FIG. 39 is a diagram illustrating a folder list object format.
• FIG. 40 is a diagram illustrating a folder object format.
• FIG. 41 is a diagram illustrating an album object format.
• FIG. 42 is a diagram illustrating a track object format.
• FIG. 43 is a diagram illustrating details of AC of a track object.
• FIG. 44 is a diagram illustrating a content data format.
• FIG. 45 is a diagram illustrating a CC object format.
• FIG. 46 is a diagram illustrating a CC data format.
• FIG. 47 is a diagram illustrating a data flow at a time when CD ripping is executed.
• FIG. 48 is a diagram illustrating a data flow at a time when CD recording is executed.
• FIG. 49 is a diagram illustrating a data flow at a time when HD recording for digital input is executed.
• FIG. 50 is a diagram illustrating a data flow at a time when HD recording for analog input is executed.
• FIG. 51 is a diagram illustrating a data flow at a time when HD play is executed.
• FIG. 52 is a diagram illustrating a data flow at a time when CD play is executed.
• FIG. 53A is a diagram illustrating a data flow at a time when MS play is executed.
• FIG. 53B is a diagram illustrating a data flow at a time when MS play is executed.
• FIG. 54 is a diagram illustrating a data flow at a time when MS check-out/move-out is executed.
• FIG. 55 is a diagram illustrating a data flow at a time when MS import/move-in is executed.
• FIG. 56 is a diagram illustrating a data flow at a time when a PD check-out is executed.
• FIG. 57 is a diagram illustrating CD ripping.
• FIG. 58 is a diagram illustrating CD recording.
• FIG. 59 is a diagram illustrating the partitioning of abuffer56 in CD ripping or CD recording.
• FIG. 60 is a diagram illustrating buffer transition states.
• FIG. 61 is a diagram illustrating aring buffer241 arranged in aHDD58.
• FIG. 62 is a diagram illustrating a data flow between buffers at the time of CD ripping.
• FIG. 63 is a flowchart describing a recording speed setting process.
• FIG. 64 is a flowchart describing a CD recording process.
• FIG. 65 is a flowchart describing a ring buffer information initializing process.
• FIG. 66 is a flowchart describing a recording process for one piece of music.
• FIG. 67 is a flowchart describing a monitor sound outputting process.
• FIG. 68 is a flowchart describing a ring buffer writing process.
• FIG. 69 is a flowchart describing a ring buffer reading process.
• FIG. 70A is a diagram illustrating an exemplary display on adisplay15 at a time when music to be recorded is set.
• FIG. 70B is a diagram illustrating an exemplary display on thedisplay15 when recording is on.
• FIG. 71 is a diagram illustrating the setting of a playback area.
• FIG. 72 is a diagram illustrating an exemplary play list.
• FIG. 73 is a diagram illustrating another exemplary play list.
• FIG. 74 is a diagram illustrating still another exemplary play list.
• FIG. 75 is a diagram illustrating yet another exemplary play list.
• FIG. 76 is a flowchart describing a play list creating process.
• FIG. 77 is a flowchart describing an all music repeat playback process.
• FIG. 78 is a flowchart describing a move-out process.
• FIG. 79 is a diagram illustrating a move-out processing state transition.
• FIG. 80 is a diagram illustrating an exemplary display on thedisplay15 at the time of a move-out process.
• FIG. 81 is a diagram illustrating an exemplary display on thedisplay15 at the time of a move-out process.
• FIG. 82 is a flowchart describing a move-in process.
• FIG. 83 is a diagram illustrating a move-in process state transition.
• FIG. 84 is a diagram illustrating an exemplary display on thedisplay15 at the time of a move-in process.
• FIG. 85 is a diagram illustrating another exemplary display on thedisplay15 at the time of a move-in process.
• FIG. 86 is a flowchart describing a restore process.
• FIG. 87 is a flowchart describing a move-out restore process.
• FIG. 88 is a flowchart describing a move-in restore process.
• FIG. 89 is a flowchart describing a check-out process.
• FIG. 90 is a diagram illustrating an exemplary display on thedisplay15 at the time of a check-out process.
• FIG. 91 is a diagram illustrating another exemplary display on thedisplay15 at the time of a check-out process.
• FIG. 92 is a flowchart describing a check-in process.
• FIG. 93 is a diagram illustrating an exemplary display on thedisplay15 at the time of a check-in process.
• FIG. 94 is a flowchart describing an exchanging process.
• FIG. 95 is a diagram illustrating an exemplary display on thedisplay15 at the time of an exchanging process.
• FIG. 96 is a diagram illustrating another exemplary display on thedisplay15 at the time of an exchanging process.
• FIG. 97 is a diagram illustrating still another exemplary display on thedisplay15 at the time of an exchanging process.
• FIG. 98 is a block diagram illustrating an exemplary hardware configuration of aPD5.
• FIG. 99 is a diagram illustrating the types of directories and files recorded on anMS4.
• FIG. 100 is a diagram illustrating archive file recording positions.
• FIG. 101 is a flowchart describing storing process.
• FIG. 102 is a diagram illustrating an exemplary display on thedisplay15 at the time of a storing process.
• FIG. 103 is a diagram illustrating another exemplary display on thedisplay15 at the time of a storing process.
• FIG. 104 is a diagram illustrating still another exemplary display on thedisplay15 at the time of a storing process.
• FIG. 105 is a flowchart describing a restoring process.
• FIG. 106 is a diagram illustrating an exemplary display on thedisplay15 at the time of restoring process.
• FIG. 107 is a diagram illustrating another exemplary display on thedisplay15 at the time of restore process.
• FIG. 108 is a diagram illustrating an area configuration of a flash ROM shown inFIG. 6.
• FIG. 109 is a flowchart describing a program rewriting process.
• FIG. 110 is a flowchart describing a boot program process.
BEST MODE FOR CARRYING OUT THE INVENTION
• Now, with reference toFIG. 1, an audio server practiced as one embodiment of the invention will be outlined below. Anaudio server1 reads PCM (Pulse Code Modulation) data from amusic CD3, encodes the PCM data based on the ATRAC (Adaptive Transform Acoustic Coding)3 technique, records the encoded data to a hard disk drive58 (FIG. 6), and manages the recorded encoded data by relating them with hierarchical objects such as, from the higher layer, folder list, folder, album, and track.
• The folder list can include a plurality of folders at a layer one step below. Each folder can include a plurality of albums at a layer one step below. Each album can include a plurality of tracks at a layer one step below. Each track located at the bottom layer of this hierarchical structure corresponds to the encoded data for one piece of music, one to one.
• In what follows, encoded data are also referred to as content data. Each of the folder list, folders, albums, and tracks is also referred to as an object. Each user specifies any of these objects and issues a variety of commands to the specified objects. It should be noted that the details of the hierarchical structure of the objects will be described later with reference toFIG. 38.
• Theaudio server1 also plays back themusic CD3 or decodes the encoded data recorded to the hard disk drive (hereafter referred to as an HDD)58 to output obtained audio signals from aspeaker2.
• In addition, theaudio server1 records the encoded data recorded to theHDD58 to a Memory Stick (trademark) (hereafter referred to as an MS4) compatible with the Magic Gate (trademark) loaded in an MS slot45 (FIG. 5) or a portable device (hereafter referred to as a PD)5 such as the Network Walkman (trademark) connected to a connector43 (FIG. 5) by a check-out or check-in process and, at the same time, records the encoded data recorded to theMS4 or thePD5 to theHDD58 by a check-in or check-out process or an import process.
• The Magic Gate is a data copyright protection technology based on two technologies of encrypting data to be recorded to theMS4 compatible with the Magic Gate and cross-certifying theaudio server1 on whichMS4 is loaded, thereby preventing digital audio data from being copied, played back, and tampered in an unauthorized manner. The Magic Gate is compliant with the SDMI (Secure Digital Music Initiative) standard.
• It should be noted that a check-out process, a check-in process, a move-out process, a move-in process, and an import process to be executed between theaudio server1 and theMS4 or thePD5 will be described later.
• TheMS4 recorded with encoded data is detached from theaudio server1 and loaded, for example, in apersonal computer6, upon which the recorded encoded data are read to be decoded.
• ThePD5 recorded with encoded data decodes them and outputs resultant audio signal from a headphone.
• Aremote controller7 receives an operation signal from the user and transmits a corresponding control signal to theaudio server1.
• The following describes an external view of theaudio server1 with reference toFIGS. 2 through 5.FIG. 2 is an elevational view of theaudio server1.FIG. 3 is a top view of theaudio server1.FIG. 4 is a rear view of theaudio server1.FIG. 5 is a top view.
• On top of theaudio server1, acover40 of a CD tray (not shown) on which a CD is loaded is provided. As shown inFIG. 3, thecover40 is arranged with buttons such as apower button11 and adisplay15 for displaying various kinds of information. The power (POWER)button11 is operated to turn on/off the power to theaudio server1. A function (FUNCTION)button12 is operated to select, as a source, one of themusic CD3,HDD58, an AUX INterminal31, theMS4, and thePD5.
• A play mode (PLAY MODE)button13 is operated to switch the playback mode to normal playback in which all tracks included in a playback area are played back each once sequentially, all-music repeat in which all tracks included in the playback area are repetitively sequentially played back, single-music repeat in which only one track is repetitively played back, random repeat in which random selection is performed on all tracks included in the playback area and the selected tracks are repetitively played back at random, or slot machine playback in which an animation indicative of random section of all tracks included in the entire HDD is displayed and the selected tracks are repetitively selected. The playback area will be described later with reference toFIG. 71.
• A display (DISPLAY)button14 is operated to switch between the display contents of thedisplay15. Thedisplay15, which is constituted by an LCD (Liquid Crystal Display) for example, displays operational situations and information associated with audio data.
• A volume (VOLUME)button16 is operated to increase or decrease the volume to be outputted. Acursor button17 is operated to move the cursor displayed on thedisplay15. A select (SELECT)button18 is operated to select an object displayed on thedisplay15 or switch between ascending order and descending order in a search operation. An erase (ELASE)button19 is operated to erase an object such as a track.
• An enter (ENTER)button20 is operated to determine a displayed menu or an object such as a selected track. A menu/cancel (MENU/CANCEL)button21 is operated to display various operator menus hierarchically arranged or cancel the display. An exchange (EXCHANGE)button22 is operated to automatically perform check-in process or check-out process on theMS4 or thePD5.
• A record (RECORD)button23 is operated to record the audio data in themusic CD3 to theHDD58 while playing them. A high-speed record (HI SPEED RECORD)button24 is operated to record the audio data in themusic CD3 to theHDD58 in a high-speed record mode. It should be noted that, in this high-speed record mode, the audio data to be recorded are audibly outputted from thespeaker2 for example.
• Astop button25 is operated to stop an on-going play or recording operation. A play/pause button26 is operated to start playback, pause playback, or clear pause of playback. Acue button27 is operated to cue to a current track or any of preceding tracks or cause rewind and play.
• Acue button28 is operated to cue to a next track or cause fast forward and playback.
• It should be noted that, although not shown, theremote controller7 has buttons which are functionally equivalent to the buttons such as thepower button11 disposed on thecover40.
• On the rear side of theaudio server1, the AUX Interminal31, aLine Out terminal32, asub woofer terminal33, a speaker (L, R)terminal34, areset button35, and a DC Interminal36 are disposed.
• The AUX Interminal31 can connect theaudio server1 to audio output equipment (not shown) and input the digital audio data or analog sound signal from the connected audio output equipment into theaudio server1. TheLine Out terminal32 can connect theaudio server1 to an amplifier (not shown) for example and output analog sound signals to the connected amplifier. Thesub woofer terminal33 can connect theaudio server1 to a sub woofer (not shown) and output the low frequency component of a reproduced sound signal to the connected sub woofer. The speaker (L, R) terminal34 can connect theaudio server1 to thespeaker2 and output reproduced sound signals therefrom. Thereset button35 is operated to reset theaudio server1. To the DC Interminal36, the DC power is supplied from an AC power adaptor (not shown).
• On the front of theaudio server1, anopen lever41, aphotoreceptor42, theconnector43, anaccess light44, theMS slot45, an eject lever46, and aheadphone terminal47 are disposed as shown inFIG. 5. Theopen lever41 is slid to open thecover40. Thephotoreceptor42 receives control signals transmitted from theremote controller7. Theconnector43 has a USB (Universal Serial Bus) terminal to which thePD5, an external HDD, or a keyboard for example may be connected by use of a USB cable.
• It should be noted that theconnector43 may have an IEEE 1394 terminal to which thePD5 for example may be connected by use of an IEEE 1394 cable. Alternatively, a connector compliant with Bluetooth (trademark) or IEEE 802.11b (so-called wireless LAN) may be provided to connect thePD5 for example in a wireless manner.
• The access light44 blinks when a data read/write operation is being executed on theMS4 loaded in theMS slot45 or thePD5 connected to theconnector43 for example. TheMS slot45 is loaded with theMS4. The eject lever46 is operated to eject theMS4 from theMS slot45. Theheadphone47 is connected to a headphone and output reproduced sound signals therefrom.
• The following describes an exemplary hardware configuration of theaudio server1 with reference toFIG. 6. Theaudio server1 incorporates a main CPU (Central Processing Unit)51 which controls theaudio server1 in its entirety. Themain CPU51 is connected to aflash ROM52, anSDRAM53, aUSB host controller54, aDMA controller55, asignal processor60, an Ethernet (trademark) controller/connector67, and aPCMCIA controller68 via abus line66.
• Whenflash ROM52 stores a device ID and an encryption key in addition to an RTOS (Real Time Operating System)71 (FIG. 7) of which starting is completed by theCPU51 as soon as the power is turned on and the firmware (to be described later with reference toFIG. 7) which is executed on the RTOS71 for implementing a variety of functions.
• The SDRAM (Synchronous Dynamic Random Access Memory)53 temporarily stores predetermined data and programs when themain CPU51 executes a variety of processes. TheUSB host controller54 controls the data communication with thePD5 for example connected via theconnector43.
• The DMA (Direct Memory Access)controller55 controls the data transfer between the HDD58 abuffer56, a CD-ROM drive57 and an encoder/decoder59. Thebuffer56 based on SDRAM for example temporarily buffers the data of which transfer is controlled by theDMA controller55. The CD-ROM drive57 reads audio data from themusic CD3 at the speed of CAV8. TheHDD58 stores the encoded data generated by the encoder/decoder59.
• The encoder/decoder59 encodes the PCM data read by the CD-ROM drive57 or the audio data inputted from the AUX Interminal31 at a maximum speed of 8× and an average speed of 5× by use of the ATRAC3 technique of 132 Kbps mode, 105 Kbps mode, or 66 Kbps mode, thereby generating encoded data. Also, the encoder/decoder59 decodes the encoded data stored in theHDD58. In addition, the encoder/decoder59 has the DES (Data Encryption Standard) engine to encrypt the encoded data by use of an encryption key to be generated on the basis of the device ID of a predetermined component of theaudio server1 and a time.
• For example, if theHDD58 has a storage capacity of 9 gigabytes and the encoder/decoder59 encodes by the ATRAC3 technique of 105 Kbps mode, about 100 music CDs 3 (60 minutes/disc) may be recorded to theHDD58.
• Thesignal processor60 is composed of a Magic Gate Memory Stick interface (hereafter referred to as an MGMS I/F)60-1, a watermark screen (hereafter referred to as a WM screen)60-2, an audio I/F60-3, and a sampling rate converter (hereafter referred to as an SRC)60-4.
• The MGMS I/F60-1 cross-certificates theMS4 loaded in theMS slot45 via anMS connector61 and accordingly encrypts the data and decrypts the encrypted data. The WM screen60-2 detects an SDMI-compliant watermark (an electronic watermark or the information indicative of the permission or inhibition of copy) embedded in the audio data that pass thesignal processor60.
• The audio I/F60-3 gets digital audio data via the AUX Interminal31 and supplies the obtained data to the SRC60-4. Also, the audio interface60-3 appropriately buffers the digital audio data transferred from thebuffer56 for example into an incorporated buffer251 (FIG. 62) and then outputs the buffered data to an AD/DA62.
• The SRC60-4 converts the sampling rate of the digital audio data from the audio I/O60-3 into 44.1 KHz and outputs the resultant digital audio data to the encoder/decoder59.
• It should be noted that, although not shown, thesignal processor60 also incorporates an ATRAC3 encoder/decoder which operates at a speed of 1×.
• TheMS connector61 relays the data communication between theMS4 inserted therein and the MGMS I/F60-1. The AD/DA62 converts the digital audio data inputted from the audio I/F60-3 of thesignal processor60 into an analog sound signal and outputs it to theLine Out terminal32, thespeaker terminal34, or theheadphone terminal47. The AD/DA62 also digitize the analog sound signal inputted from the AUX Interminal31 to output a resultant digital signal to the encoder/decoder59.
• The Ethernet controller/connector67 controls the data communication with other electronic equipment connected via Ethernet (trademark). The PCMCIA (Personal Computer Memory Card International Association)controller68 has an IC card interface compliant with the PCMCIA standard.
• Themain CPU51 is connected to adisplay driver63 and asub CPU64. Thedisplay driver63 controls a display operation performed on thedisplay15. Thesub CPU64 controls, especially when the power is off, apower supply section65, controls a main frame reset operation, counts an incorporated clock, detects an operation performed on thepower button11 for example, controls thephotoreceptor42, and controls the AD/DA62. Thepower supply section65 converts the DC voltage supplied from the DC Interminal36 into a predetermined voltage and supplies it to theaudio server1 in its entirety.
• The following describes, with reference toFIG. 7, the firmware which themain CPU51 reads from theflash ROM52 to actually execute the functions of theaudio server1 which are described below. It should be noted that the functions of theaudio server1 include CD ripping, CD recording, HD recording (digital input), HD recording (analog input), HD play, CD play, MS play, check-out/check-in, import, and move-out/move-in for example, their details and relationship with the firmware being described later with reference toFIGS. 47 through 56.
• The firmware has four layers, namely, an application layer (APP)72, an upper-middleware layer (UMW)73, a lower-middleware layer (LMW)74, and a device driver layer (DD)75.
• The application layer72 includes a main application (hereafter referred to as a main APP)76, a hard disk application (hereafter referred to as an HD APP)77, a CD application (hereafter referred to as a CD APP)78, a Memory Stick application (hereafter referred to as an MS APP)79, a portable device application (hereafter referred to as a PD APP)80, and a front-end processor (hereafter referred to as an FEP)81.
• Each module of the application layer72 requests the corresponding module of the upper-middleware layer73 in accordance with the user operation associated with a function executable by theaudio server1 and provides a user interface by controlling the display of processing situations.
• The main APP76 controls each module of the application layer72. For example, at the time of starting up, the main APP76 creates a startup screen to start up each module. In response to a user operation transmitted from an input middleware97, main APP76 notifies the corresponding module thereof. The main APP76 supplies the display data from each module to a display device driver105. The main APP76 executes switching between modules. In response to a volume change operation done by the user, the main APP76 notifies an audio IO middleware (AIO)94. In response to a setup operation done by the user, the main APP76 notifies each module of settings. The main APP76 holds the setting information (play mode for example) common to the modules. In response to a power-off operation, the main APP76 ends each module and requests a system control middleware (SYSTEM)98 for a power-off sequence.
• Upon reception of aHDD58 driving operation, the HD APP77 notifies a hard disk middleware82 thereof and gets an operation state of the hard disk middleware82 to generate display data.
• Upon reception of a CD-ROM drive57 driving operation, the CD APP78 notifies a CD middleware88 thereof and gets an operation state of the CD middleware88 to generate display data.
• Upon reception of an operation associated with theMS4 loaded in theMS slot45, the MS APP79 notifies the MS middleware89 thereof and gets an operation state of the MS middleware89 to generate display data.
• Upon reception of an operation associated with thePD5 connected to theconnector43, the PD APP80 notifies a PD middleware90 thereof and gets an operation state of the PD middleware90 to generate display data.
• TheFEP81 executes kana-kanji conversion when inputting the title, for example, of themusic CD3 to be recorded.
• The upper-middleware layer73 is composed of the following modules obtained by modeling the functions of theaudio server1. Namely, the upper-middleware layer73 includes the hard disk middleware (hereafter referred to as an HD MW)82, the CD middleware (hereafter referred to as a CD MW)88, the MS middleware (hereafter referred to as an MS MW)89 and the PD middle ware (hereafter referred to as a PD MW)90.
• The HD MW82 is composed of an HDCC83 which manages the encoded data stored in theHDD58, a CD RIPPING84 which compresses and encrypts the audio data stored themusic CD3 in cooperation with the CD MW88 to record the resultant data to theHDD58, an HD PLAY85 which decrypts and decompresses the encoded data stored in theHDD58 in cooperation with the audio IO middleware94, an HD REC86 which compresses and encrypts the audio data inputted from the AUX Interminal31 in cooperation with the audio IO middleware94, and a C IN/C OUT87 which controls the check-in and check-out operations with theMS4 or thePD5 in cooperation with the MS MW89 or the PD MW90.
• The CD MW88 realizes a function as a CD player by causing the CD device driver102 to control the CD-ROM drive57. The MD MW89 realizes a function as an MS player in cooperation with an audio IO middleware94 and an MSfile system middleware95. The PD MW90 controls thePD5 in cooperation with an USB host middleware96 and a USB host device driver104.
• The lower-middleware layer74 includes the following modules obtained by modeling the functions which can be shared by the modules of the upper-middleware layer73, namely, a hard disk object database middleware (hereafter referred to as an HD DB)91, a hard disk file system middleware (hereafter referred to as an HD FS)92, an MGR middleware (MGR)93, the audio IO middleware (AIO)94, the Memory Stick File System Middleware (MS FS)95, the USB host middle ware (USB)96, the input handle middleware (INPUT)97, and the system control middleware (SYSTEM)98. Each module constituting the lower-middleware layer74 is called by each module constituting the upper-middleware layer73.
• The device driver layer (DD)75 includes the following modules which are obtained by modeling hardware devices, namely, a harddisk device driver99, a decoder/encoder device driver100, a DMA device driver101, a CD device driver102, a signal processor device driver103, a USB host device driver104, a display device driver105, anaudio device driver106, a key device driver107, a power device driver108, and a clock device driver109. It should be noted that, inFIG. 7, theaudio device driver106 through the clock device driver109 enclosed by dashed lines are executed by thesub CPU64. Each module is constituted mainly by libraries, its API (Application Program Interface) being called by each module included in the upper-middleware layer73 or the lower-middleware layer74.
• The following describes a FAT (File Allocation Table)-type file system (data format) applied to theHDD58 with reference toFIGS. 8 through 20. As shown inFIG. 8, theHDD58 has afile recording area121 for recording encoded data (content data) as a file and anobject recording area122 for recording an object including the information for identifying a position at which the content data recorded to thefile recording area121 are recorded.
• Afile managing block123 executes all file-associated processes such as file creation, issuance of ID to newly created file, and read, write and delete operations on thefile recording area121. Thefile managing block123 is equivalent to theHD FS92 included in the lower-middleware layer74.
• Anobject managing block124 recognizes the physical location of an object in theobject recording area122 and executes object write, read, and delete operations. Theobject managing block124 is equivalent to theHD DB91 included in the lower-middleware layer74. It should be noted that the management of objects by a database will be described later with reference toFIGS. 21 through 37.
• FIG. 9 shows a logical structure of thefile recording area121. Thefile recording area121 is divided into sectors having a predetermined capacity, which is the minimum unit of writing and reading in thefile recording area121. Each sector is assigned with a serial sector number. Thefile recording area121 is formed by a FAT area, a system area, and a plurality of clusters, configured by the predetermined number of sectors. Each cluster is assigned with a cluster number having a fixed length. Each file to be recorded in thefile recording area121 is formed by a plurality of interlinked clusters.
• The linking relationship between the clusters is recorded to a table called a FAT141 (FIG. 10). TheFAT141 is recorded in the FAT area of thefile recording area121 and, when thefile managing block123 operates, transferred to theSDRAM53.
• FIG. 10 shows a structure of theFAT141. TheFAT141 is configured by aFAT header142 and a plurality ofFAT entries144 corresponding to the clusters respectively. Theheader142 includes a free cluster list startnumber recording area143. The start cluster numbers of the sequence of free clusters recording no data are recorded to the free cluster list startnumber recording area143. If there is no free cluster, −1=0xFFFFFFFF is recorded to the free cluster list startnumber recording area143.
• EachFAT entry144 is assigned with the entry number which is the same number as the cluster number assigned to the corresponding cluster. For example, the FAT entry corresponding to clusternumber 1 is assigned withentry number 1. In what follows, the FAT entry havingentry number 1 is also written as FAT entry E(1). TheFAT entry144 is divided intocolumn P145 andcolumn N146.
• To theP column145 of theFAT entry144, the cluster number assigned to the cluster linked before the corresponding cluster is recorded. If there is no cluster to be linked before, namely, if the corresponding cluster is located at the head of the file, 0xFFFFFFFF is recorded to theP column146.
• To theN column146 of theFAT entry144, the cluster number assigned to the cluster linked after the corresponding cluster is recorded. If there is no cluster linked after, namely, if the corresponding cluster is located at the end of the file, 0xFFFFFFFF is recorded to theN column146.
• For example, if only one cluster is recorded to five clusters havingcluster numbers1,5,6,8, and12 in thefile recording area121, then, as shown inFIG. 11, 0xFFFFFFFF indicative of that there is no cluster to be linked before is recorded to column P of FAT entry E(1) of entry number 1 (0x00000001) and cluster number 5 (0xFFFFFFFF) is assigned to the cluster linked after is recorded to column N.
• To column P of FAT entry E(5) of entry number 5 (0x00000005), cluster number 1 (0x00000001) assigned to the cluster linked before is recorded and, to column N, cluster number 6 (0x00000006) assigned to the cluster linked after is recorded.
• The like recording is performed to the FAT entries E(6) and E(8) ofentry numbers6 and8.
• To column P of FAT entry E(12) of entry number 12 (0x0000000C), cluster number 8 (0x00000008) assigned to the cluster linked before is recorded and, to column N, 0xFFFFFFFF indicative of that there is no cluster linked after is recorded.
• In this case, a sequence of clusters from cluster number (0x00000002) to cluster number (0x00000014) are free clusters, so that the cluster number (0x00000002) indicative of its head is recorded to the free cluster list startnumber recording area143.
• FIG. 12 shows a manner in which one file is recorded to five clusters assigned withcluster numbers1,5,6,8, and12. The file start cluster (in this case, cluster1) has asize recording area151 for recording information associated with file size. The data contained in this file are recorded to the second (in this case, cluster5) and subsequent clusters. It should be noted that thesize recording area151 may be arranged in the cluster at the end of file (in this case, cluster12).
• FIG. 13 shows an exemplary configuration of thesize recording area151. Thesize recording area151 has a validsize recording area152, a last clusternumber recording area153, and an occupied clustercount recording area154. To the validsize recording area152, the number of valid bytes of the end cluster (in this case, cluster12) is recorded. Normally, its value is 1 or more, a value below cluster size being recorded. To the last clusternumber recording area153, the cluster number (in this case, 0x0000000C) of the end cluster (in this case, cluster12) is recorded. To the occupied clustercount recording area154, the number of clusters forming the data recording portion of file (in this case,4) is recorded.
• The following describes a file creating process (namely, a content data recording process), a file reading process, and a file reserve reading process (namely, a process of reading content data in reverse direction), which use FAT, with reference to the flowcharts shown inFIGS. 14 through 20. It should be noted that these processes are controlled by theHD FS92 belonging to thefile managing block123, namely the lower-middleware layer74.
• First, the file creating process will be described with reference to the flowchart shown inFIG. 14. In step S1, theHD FS92 transfers the content data to be recorded to theHDD58 from the CD-ROM drive57 for example to thebuffer56 on a cluster size basis (let the data amount transferred be S bytes). In step S2, theHD FS92 searches thefile recording area121 for free clusters and retrieves (or allocates) them.
• This free cluster retrieving process will be described with reference to the flowchart shown inFIG. 15. In step S21, theHD FS92 reads value Q recorded to the free cluster list startnumber recording area143 recorded to theFAT header141. In step S22, theHD FS92 determines whether or not value Q is −1, namely, whether there is no free cluster. If value Q is not −1, namely, if there is a free cluster, then the procedure goes to step S23. In step S23, theHD FS92 reads FAT entry E(Q) corresponding to value Q (the cluster number of the free cluster).
• The following describes a process of reading FAT entry E(X) corresponding to given cluster number X in relation to the process of reading FAT entry E(Q) with reference to the flowchart shown inFIG. 16. In step S41, theHD FS92 adds a known FAT header size to a known FAT entry start address and then adds a product obtained by multiplying a value obtained by subtracting 1 from value X (X−1) by a known entry size, thereby computing address A. In step S42, theHD FS92 reads the data by one entry size with address A as the start address. This is the process of reading FAT entry E(X) corresponding to given cluster number X.
• Returning toFIG. 15, theHD FS92 determines whether or not the value of column N of FAT entry E(Q) is −1 (0xFFFFFFFF) in step S24. If the value of column N of FAT entry E(Q) is not −1, then the procedure goes to step S25.
• In step S25, theHD FS92 substitutes the value of column N of FAT entry E(Q) into variable M. In step S26, theHD FS92 reads FAT entry E(M) corresponding to cluster number M. In step S27, theHD FS92 records −1 (0xFFFFFFFF) to column P of FAT entry E(M).
• In step S28, theHD FS92 records −1 (0xFFFFFFFF) to column N of FAT entry E(Q) and −1 (0xFFFFFFFF) to column P of FAT entry E(Q). In step S29, theHD FS92 returns toFIG. 14 because there is a free cluster of cluster number Q. This is the process of free cluster retrieval.
• It should be noted that, in step S24, if the value of column N of FAT entry E(Q) is found −1, the processes of steps S25 through S27 are skipped.
• If value Q recorded to the free cluster list startnumber recording area143 is found −1 in step S22, then the procedure goes to step S30. In step S30, theHD FS92 returns toFIG. 14 because there is no free cluster. It should be noted that, if no free cluster is found, it is regarded that theHDD58 is full, and the file creating process shown inFIG. 14 comes to an end.
• In what follows, the description will be continued by reading the retrieved free cluster having cluster number Q as the free cluster having cluster number V. In step S3, theHD FS92 substitutes cluster number V of free cluster into variables X and A. In step S4, theHD FS92substitutes 0 into occupied cluster count T. In step S5, theHD FS92 retrieves a new free cluster in the same manner as the above-mentioned process of step S2. Let the cluster number of the retrieved free cluster be V. If no new free cluster is retrieved, this file creating process comes to an end.
• In step S6, theHD FS92 substitutes value V into variable B. In step S7, theHD FS92 increments occupied cluster count T by 1. In step S8, theHD FS92 converts cluster number B into sector numbers (for example, if sectors are related to clusters as shown inFIG. 9,cluster number 2 is converted intosector numbers28 through35). Sector numbers corresponding to cluster number B are determined. In step S9, theHD FS92 records the content data buffered in step S1 to the converted sector numbers in thefile recording area121.
• After the recording of the buffered content data has ended, theHD FS92 links the cluster of cluster number B to the cluster of cluster number A (at this point of time, this cluster is a free cluster) in step S10. The following describes this linking process with reference to the flowchart ofFIG. 17.
• In step S51, as with the above-mentioned process described with reference toFIG. 16, theHD FS92 reads FAT entry E(A) corresponding to cluster number A and, in step S52, reads FAT entry E(B) corresponding to cluster number B. In step S53, theHD FS92 records cluster number B to column N of FAT entry E(A) and cluster number A to column P of FAT entry E (B). It should be noted that the process of step S53 is executed on theFAT141 developed in theSDRAM53. This is the process of linking the cluster having cluster number A and the cluster having cluster number B.
• Returning toFIG. 14, in step S11, theHD FS92 determines whether or not data amount S of the content data recorded in step S9 is equal to the cluster size. If data amount S of the content data recorded in step S9 is found equal to the cluster size, then it indicates that the recording of the content data to be recorded has not completed, so that the procedure goes to step S12.
• In step S12, the remaining portion of the content data recorded before is transferred to thebuffer56 by the cluster size. In step S13, cluster number B is substituted into variable A. In step S14, theHD FS92 retrieves a new free cluster as with the above-mentioned process of step S2. Let the cluster number of the newly retrieved cluster be V. It should be noted that, if no new free cluster is retrieved in step S14, then the procedure goes to step S17. In step S15, theHD FS92 substitutes value V into variable B. In step S16, theHD FS92 increments occupied cluster count T by 1.
• Then, the procedure returns to step S8 to repeat the above-mentioned processes. If, in step S11, data amount S of the content recorded in step S9 is found unequal to the cluster size, it indicates that the recording of the content data to be recorded has been completed, so that the procedure goes to step S17.
• In step S17, theHD FS92 arranges thesize recording area151 in the free cluster having cluster number X retrieved in step S2, records data amount S recorded to the last cluster to the validsize recording area152, records the value of variable B to the last clusternumber recording area153, and records the value of variable T to the occupied clustercount recording area154.
• In step S18, theFAT141 recorded to the FAT area of thefile recording area121 is updated by theFAT141 rewritten by the process of step S10. Thus, a new file is created. It should be noted that a file identifier having the same value as the start cluster number of a sequence clusters recorded with content data is issued to the newly created file.
• The following describes a process of reading a file of which file identifier is X (hereafter referred to as file X) with reference to the flowchart shown inFIG. 18. In step S61, theHD FS92 executes a search process for determining whether or not there is file X.
• The following describes a file X search process with reference to the flowchart shown inFIG. 19. In step S81, theHD FS92 gets FAT entry E(X) corresponding to entry number X. In step S82, theHD FS92 determines whether or not the value of column P of FAT entry E(X) is −1 (0xFFFFFFFF). If the value of column P of FAT entry E(X) is found −1, then the procedure goes to step S83. In step S83, file X is found existing because the cluster of entry number X (=cluster number X) is the start cluster among a sequence of clusters on which the file is recorded, so that the procedure returns to the file reading process shown inFIG. 18.
• Conversely, if the value of column P of FAT entry E(X) is found not −1 in step S82, the procedure goes to step S84. In step S84, theHD FS92 determines that there is no file X because the cluster of entry number X (=cluster number X) is not the start cluster among a sequence of clusters on which the file is recorded, so that the procedure returns to the file reading process shown inFIG. 18. Thus, the file X search process is executed.
• In what follows, the description will be continued on the assumption that file X exists. In step S62, theHD FS92 determines whether or not the value of column N of FAT entry E(X) is −1 (0xFFFFFFFF). If the value of FAT entry E(X) is found −1, then it indicates that file X has no data, so that the reading process comes to an end.
• If the value of column N of FAT entry E(X) is found not −1 in step S62, then the procedure goes to step S63. In step S63, theHD FS92 converts cluster number X (the start cluster) into sector numbers. In step S64, theHD FS92 controls theDMA controller55 to read thesize recording area151 recorded to the converted sector numbers to buffer this area in thebuffer56. In step S64, theHD FS92 reads valid size S (the data amount recorded to the last cluster among a sequence of clusters on which file X is recorded) recorded to the validsize recording area152 of thesize recording area151 buffered in step S63.
• In step S66, theHD FS92 substitutes the value of column N of FAT entry E(X) into variable C. In step S67, theHD FS92 reads FAT entry E(C) corresponding to cluster number C, namely the second cluster, as with the above-mentioned process described with reference toFIG. 16. In step S68, theHD FS92 converts cluster number C into sector numbers. In step S69, theHD FS92 controls theDMA controller55 to read the content data recorded to the sectors having the converted sector numbers by one cluster to buffer the content data in thebuffer56.
• In step S70, theHD FS92 determines whether or not the value of column N of FAT entry E(C) is −1 (0xFFFFFFFF). If the value of column N of FAT entry E(C) is found not −1, then the procedure goes to step S71. In step S71, theHD FS92 controls theDMA controller55 to output all data buffered in thebuffer56 to the encoder/decoder59 and so on. Because the content data of file X have not all been read, so that the procedure goes to step S72. In step S72, theHD FS92 substitutes the value of column N of FAT entry E(C) into variable C. Then, the procedure returns to step S67 to repeat the above-mentioned processes.
• Then, in step S70, if the value of column N of FAT entry E(C) is found −1, it indicates that the reading starting with the last cluster recorded with the content data of file X has been completed, so that the procedure goes to step S73. In step S73, theHD FS92 controls theDMA controller55 to output the data for valid size S which are the last of the content data buffered in thebuffer56 to the encoder/decoder59 and so on.
• If no file X is found existing in the file search process of step S61, the procedure goes to step S74, in which an error is determined, upon which the file X reading process comes to an end. Thus, the file X reading process is executed.
• The following describes a file X reverse reading process with reference to the flowchart shown inFIG. 20. The reverse reading herein denotes a process in which content data are played back every several second retrospectively such that certain content data of which play time is 100 seconds are played back for about 100 milliseconds from 90th second and then played back for 100 milliseconds from 80th second and then played back for 100 milliseconds from 70th second, for example.
• In step S91, theHD FS92 converts the file identifier (=X, hereafter referred to as ID(X)) into sector numbers. It should be noted that ID(X) is the same as the cluster number of the start cluster among a sequence of clusters on which file X is recorded.
• In step S92, FAT entry E(X) corresponding to cluster X is read. In step S93, theHD FS92 controls theDMA controller55 to read thesize recording area151 recorded to the sector having the sector number converted in step S91 to buffer it in thebuffer56. In step S94, theHD FS92 reads valid size S from the validsize recording area152 of thesize recording area151 buffered in step S93 and last cluster number Z from the last clusternumber recording area153.
• In step S95, theHD FS92 determines whether or not last cluster number Z is equal to ID(X). If last cluster number Z is found equal to ID(X), it indicates that file X has no content data, so that the reverse reading process comes to an end.
• If last cluster number Z is found unequal to ID(X), then the procedure goes to step S96. In step S96, theHD FS92 converts last cluster number Z to sector numbers. In step S97, theHD FS92 controls theDMA controller55 to read the data including the end portion of the content data recorded to the sector numbers converted in step S96 to buffer the data in thebuffer56. In step S98, theHD FS92 controls theDMA controller55 to output only the data for S bytes of the data buffered in thebuffer56, namely, the end portion of the content data to the encoder/decoder59 and so on.
• In step S99, theHD FS92 reads FAT entry E(Z) corresponding to last cluster number Z. In step S100, theHD FS92 determines whether or not the value of column P of FAT entry E (Z) is equal to ID (X). If the value of column P of FAT entry E(Z) is found equal to ID(X), the reverse reading process comes to an end because the content data of file X have been recorded to the last one cluster.
• If the value of column P of FAT entry E(Z) is found unequal to ID(X), then the procedure goes to step S101 to read the data by one cluster from the end retrospectively. In step S101, theHD FS92 substitutes the value of column P of FAT entry E(Z) into variable C.
• In step S102, theHD FS92 reads FAT entry E(C) corresponding to cluster number C. In step S103, theHD FS92 converts cluster number C into sector numbers. In step S104, theHD FS92 controls theDMA controller55 to read the content data recorded to the sector numbers converted in step S103 to buffer the content data in thebuffer56. In step S105, theHD FS92 controls theDMA controller55 to output the content data for one cluster buffered in thebuffer56 to the encoder/decoder59 and so on.
• In step S106, theHD FS92 determines whether or not the value of column P of FAT entry E(C) corresponding to cluster number C is equal to ID (X). If the value of column P of FAT entry E(C) is found unequal to ID(X), it indicates that file X has not all been read, so that the procedure goes to step S107 to read by one cluster retrospectively. In step S107, theHD FS92 substitutes the value of column P of FAT entry E(C) into variable C. Then, the procedure returns to step S102 to repeat the above-mentioned processes.
• If the value of column P of FAT entry E(C) is found equal to ID(X) in step S106, it indicates that file X has been read up to its beginning, so that the reverse reading process comes to an end. Thus, the file X reverse reading process is executed.
• As described and according to theHD FS92 of theaudio server1, for a file identifier for identifying a particular file, a cluster number, which is a fixed-length value, of the start cluster of the area to which this file is recorded is assigned, so that the recording position of the file may be identified with ease. Consequently, as compared with the case in which a file name is not fixed in length, the file search time may be significantly reduced.
• In addition, because of the fixed file length, the time required for a file search operation may be made uniform.
• Further, according to theHD FS92 of theaudio server1, there is no limitation to the size of a file to be recorded, so that not only audio data but also video data, which are greater in size may be recorded as a file.
• Still further, according to theHD FS92 of theaudio server1, if one file is recorded over a plurality of clusters, the clusters are used in the forward direction, so that, at the time of recording and playback, a seek operation is performed in a constant direction. Consequently, the recording drops at recording and sound drops at playback are prevented from occurring.
• The following describes objects corresponding to folder, album or track with reference toFIGS. 21 through 27.FIG. 21 shows a logical structure of theobject recording area122 to which an object is recorded. Theobject recording area122 is formed by asystem area161 and a plurality of chunks divided so as to have a predetermined capacity. Each object is recorded to chunks.
• Thesystem area161 has aheader162, an objecttype recording area163, and an areainformation recording area164. To the plurality of chunks, serial numbers beginning with 1 are applied in order from the top one of them. In the following description, for example, the chunk to which thenumber 1 is applied is referred to aschunk 1, the chunk to which thenumber 2 is applied is referred to aschunk 2, and so forth.
• Each chunk is divided into pages having a predetermined capacity. The pages forming each chunk are assigned with serial numbers, 0 to the start page and subsequent numbers to the subsequent pages. For example, the page assigned withnumber 0 ispage 0, the page assigned withnumber 1 ispage 0, and so on.
• FIG. 22 shows the structure of the objecttype recording area163 of thesystem area161, which is formed by aheader165 and T entries. T is a preset constant. Theheader165 has an entrycount recording area166. The entrycount recording area166 records the number of currently registered entries (the maximum value is T).
• Each entry of the objecttype recording area163 has asize recording area167, a basic object typenumber recording area168, and aparameter recording area169. For example, entry t records the information associated with object type number t. Namely, thesize recording area167 of entry t records the size of the object having object type number t. The basic object typenumber recording area168 of entry t records the basic object type number indicative of the basic object type to which the object having object type number t belongs. Theparameter recording area169 of entry t records the information associated with the size as it is when the size of the object having object type number t is variable in length.
• FIG. 23 shows the areainformation recording area164 of thesystem area161. The areainformation recording area164 is formed by the bit sequences indicative of the total number of pages of the object recording area122 (a value obtained by multiplying the total number of chunks by the number of pages forming one chunk). It should be noted that, for the convenience of description,FIG. 23 shows a matrix of (the total number of chunks) column X (the number of pages forming one chunk) row. For example, as shown inFIG. 23, the bit indicated by “◯” at column q, row p corresponds to page p of chunk q. If page p of chunk q is in use, 1 is recorded to the bit indicated by “◯”. Conversely, if page p of chunk q is in use, 0 is recorded to the bit indicated by “◯”.
• FIG. 24 shows an exemplary configuration of theobject managing block124 equivalent to theHD DB91 included in the lower-middleware layer74. Theobject managing block124 is formed by an objecttype registering block171, a storagearea managing block172, asession managing block173, and acache managing block174.
• The objecttype registering block171 performs the registration of object types (the writing to the object type recording area163). Further, the objecttype registering block171 performs the response to the enquires for object types (the reading from the object type recording area163).
• The storagearea managing block172 inverts predetermined bits in the areainformation recording area164. Further, the storagearea managing block172 also searches for a continuous unused area of the predetermined number of pages by reading the bit of the areainformation recording area164. In addition, the storage area managing block172 issues an identifier to each object.
• The session managing block173 issues a session number to the currently executed session and manages session managing information181 (FIG. 25). Term session herein denotes a process for controlling data read and write operations for example.
• FIG. 25 shows an exemplary configuration of thesession managing information181. Thesession managing information181 is formed by a current sessioncount storage area182 for storing the number of currently opened sessions (hereafter referred to as the number of current sessions) and S entries corresponding to objects and in each of which information of a session having the access right to the object is recorded. The maximum value of the number of current sessions and value S are predetermined.
• Each entry of thesession managing information181 is formed by an objectidentifier storage area183, a read/write sessionnumber storage area184, a read-only sessionnumber storage areas185 through188, an objectstate storage area189, a read cacheaddress storage area190, a write cacheaddress storage area191, and an accesstime storage area192.
• The objectidentifier storage area183 stores the object identifier of the corresponding object (FIG. 27). The read/write sessionnumber storage area184 stores the session number of the session having write access right to the corresponding object. The read-only sessionnumber storage areas185 through188 store the session numbers having read access right to the corresponding object. It should be noted that a plurality of sessions having read access right to an object may exist.FIG. 25 shows an example in which there are up to four sessions having read access right and one session having read/write access right.
• The objectstate storage area189 stores information indicative of the state of the corresponding object (“CREATE” indicative of creation, “UPDATE” indicative of update, and “REMOVE” indicative of removal). The read cacheaddress storage area190 stores the address of the read cache in which an object to be read is temporarily stored. The write cacheaddress storage section191 stores the address of the write cache in which an object to be written is temporarily stored. The accesstime storage area192 stores the last access time for the corresponding object.
• It should be noted that, if there is no information to be stored in the objectidentifier storage area183 through the accesstime storage area192,0 is stored in these storage areas.
• FIG. 26A andFIG. 26B show the exemplary configurations ofbasic object type1 andbasic object type2, which are the two basic object types to be recorded to chunks.
• As shown inFIG. 26A,basic object type1 is formed by an objectidentifier recording area201 for recording own object identifier and an arbitrarydata recording area202 for recording given data (for example, the data such as the name of the object to be set by the user). Thebasic object type1 includes objects such as folder list, folder, and album.
• As shown inFIG. 26B,basic object type2 is formed by the objectidentifier recording area201 for recording own object identifier, the arbitrarydata recording area202 for recording arbitrary data, and a fileidentifier recording area203 for recording the file identifier of the file corresponding to the own (object).Basic object type2 includes a track object.
• The object identifier to be recorded to the objectidentifier recording area201 is formed by a chunk number indicative of the head of a sequence of pages in which a corresponding object is stored, the number of the head page, and a type number as shown inFIG. 27. The type number is formed by basic object type number to which the corresponding object belongs (eitherbasic object type1 or basic object type2) and the entry number of the objecttype recording area163 in which the type of the corresponding object is registered.
• The following describes an object creating process, an object searching process, an object updating process, a stream object creating process, and a stream object searching process with reference to the flowcharts shown inFIGS. 28 through 37. Term stream object herein denotes the object which corresponds, one to one, to the content data stored in thefile recording area121, namely the stream object indicates a track. The stream object belongs to basic object type2 (FIG. 26B). Therefore, any other objects than the stream object are folder or album objects, which belong tobasic object type1.
• It should be noted that the above-mentioned processes are controlled by theobject managing block124, namely theHD DB91 belonging to the lower-middleware layer74 of the firmware.
• First, the object creating process not for stream objects will be described by use of an example in which an object of object type number t with reference to the flowchart shown inFIG. 28. It should be noted that object type number t includes basic type number (in this example, basic object type1) and entry number as shown inFIG. 27.
• In step S121, theHD DB91 opens a write session. The write session opening process will be described below with reference to the flowchart shown inFIG. 29. In step S141, theHD DB91 reads the number of current sessions from the current sessioncount storage area182 to determine whether or not the number of retrieved current sessions is smaller than the preset maximum value. If the number of current sessions is found smaller than the preset maximum value, the procedure goes to step S142.
• In step S142, theHD DB91 increments the number of current sessions stored in the current sessioncount storage area182 of thesession managing information181 by 1. In step S143, theHD DB91 opens a write session and issues session number Z by use of random numbers for example. The procedure returns toFIG. 28.
• It should be noted that, if, in step S141, the number of current sessions is found not smaller than the preset maximum value, no more session can be opened, so that the procedure goes to step S144, in which theHD DB91 determines an error. Then, the session opening processing comes to an end and the object creating process shown inFIG. 28 is discontinued.
• In step S122 shown inFIG. 28, in order to allocate pages of a chunk to which an object of object type number t is recorded, theHD DB91 reads the size of the object of object type number t from thesize recording area167 of entry t of objecttype recording area163 to compute the number of pages of the chunk equivalent to the computed size. Let the computed number of pages be g.
• In step S123, theHD DB91 allocates a free entry among the plurality of entries forming thesession managing information181. The following describes a process of free entry allocation with reference to the flowchart shown inFIG. 30.
• In step S151, theHD DB91 initializes variable M to 1. In step S152, theHD DB91 determines whether or not variable M is equal to or smaller than the number of entries S forming thesession managing information181. If variable M is found equal to or smaller than the number of entries S, then the procedure goes to step S153. In step S153, theHD DB91 reads the value of the objectidentifier storage area183 forming thesession managing information181. In step S154, theHD DB91 determines whether or not the value of the objectidentifier storage area183 of retrieved entry M is 0. If the value of objectidentifier storage area183 of entry M is found 0, it indicates that entry M is a free entry, so that entry M is allocated, upon which the procedure returns toFIG. 28.
• In step S154, if the value of the objectidentifier storage area183 of entry M is found not 0, then the procedure goes to step S155. In step S155, theHD DB91 increments variable M by 1. The procedure returns to step S152 to repeat the above-mentioned processes. Then, if the value of objectidentifier storage area183 of entry M is found not 0 in step S154 and variable M is found not equal to or smaller than the number of entries S in step S152, it indicates that there is currently no free entry, so that the procedure goes to step S156 to create a free entry.
• In step S156, theHD DB91 determines whether or not, among the entries forming thesession managing information181, there is any entry that the values of the read/write sessionnumber storage block184 and the read-only session number storage blocks185 through188 are all 0s. If such an entry is found, the procedure goes to step S157. In step S157, theHD DB91 extracts, from among the entries that the values of the read/write sessionnumber storage block184 and read-only session number storage blocks185 through188 are all 0s, the entry that the value of the accesstime storage area192 is the smallest (namely, the entry of the least recent access time).
• In step S158, theHD DB91 clears the values of the current sessioncount storage area182 through accesstime storage area192 of the extracted entry to 0s and allocates this entry as free entry M. The procedure returns toFIG. 28.
• It should be noted that, in step S156, among the entries forming thesession managing information181, if there is no entry that the values of the read/write sessionnumber storage block184 and the read-only session number storage blocks185 through188 are all 0s, it indicates that no free entry can be allocated, so that the procedure goes to step S159. In step S159, theHD DB91 determines an error. The free entry allocating processing comes to an end and the object creating process shown inFIG. 28 is discontinued.
• Returning toFIG. 28, in step S124, theHD DB91 searches the areainformation recording area164 for a bit sequence recorded with 0s by g bits continuously. Let the start position of the retrieved bit sequence recorded with 0s by g bits continuously be column q, row p. In step S125, theHD DB91 stores, in the objectidentifier storage area183 of allocated entry M, object identifier OID (q, p, t) formed by chunk number q, page number p, and object type number t as shown inFIG. 27. In addition, theHD DB91 stores session number Z into the read/write sessionnumber storage area184 of the entry M insession managing information181 and records “CREATE” indicative of the object creation into the objectstate storage area189.
• In step S126, theHD DB91 allocates a write cache area d equal to the number of pages g indicative of the size of the object, into thebuffer56. In step S127, theHD DB91 stores the address of the write cache area d allocated in thebuffer56 into the write cacheaddress storage area191 of entry M of thesession managing information181.
• In step S128, theHD DB91 starts recording object X of objectbasic type1 shown inFIG. 26A to the write cache area d allocated in thebuffer56. In doing so, theHD DB91 first records the object identifier OID (q, p, t) to the objectidentifier recording area201 in the write cache area d. In step S129, theHD DB91 records the arbitrary data of the object to be created (for example, the name of the object to be created) to the arbitrarydata recording area202 in the write cache area d.
• Instep130, theHD DB91 waits for the input of signal I representative of a user operation. In step S131, theHD DB91 determines whether or not signal I is “commit,” namely whether or not signal I is for establishing the session creation. If signal I is found a commit, then the procedure goes to step S132 to establish write session Z. If signal I is fount not a commit, then the procedure goes to step S133 to discard write session Z.
• The following describes a process of establishing the write session shown in step S132 with reference to the flowchart shown inFIG. 31. It should be noted that “establishment of a session” herein denotes to reflect the recording in theobject recording area122 upon creation, updating and moving or the like of an object performed after opening of the session concerned and enter the results of the reflection.
• In step S171, theHD DB91 initializes variable M to 1. In step S172, theHD DB91 determines whether or not variable M is equal to or smaller than the number of entries S forming thesession managing information181. If variable M is found equal to or smaller than the number of entries S, then the procedure goes to step S173. In step S173, theHD DB91 reads the value of read/write sessionnumber storage area184 of entry M forming thesession managing information181 to determine whether or not this value matches session number Z. If the value of the read/write sessionnumber storage area184 of entry M is found not matching session number Z, the procedure goes to step S174 to search for an entry that the value of the read/write sessionnumber storage area184 of entry M matches session number Z.
• In step S174, theHD DB91 increments variable M by 1. The procedure returns to step S172 to repeat the above-mentioned processes. If the value of the read/write sessionnumber storage area184 of entry M is found matching session number Z in step S173, then the procedure goes to step S175. Namely, only the entry in which session number Z is stored in the read/write sessionnumber storage area184 is extracted to be processed in steps S175 and on.
• In step S175, theHD DB91 reads the object identifier from the objectidentifier storage area183 of entry M in which session number Z is stored in the read/write sessionnumber storage area184. In step S176, theHD DB91 reads information J indicative of object state from the objectstate storage area189 of entry M in which session number Z is stored in the read/write sessionnumber storage area184. In step S176, theHD DB91 determines whether information J indicative of object state is “CREATE”, “UPDATE”, or “REMOVE”.
• If information J indicative of object state is found “CREATE”, then the procedure goes to step S178. In step S178, theHD DB91 records the object recorded to the write cache area d allocated in thebuffer56 to pages q and on of chunk p in theobject recording area122. In step S179, theHD DB91records 1 to g bits subsequent to column q, row p in the areainformation recording area164.
• In step S180, theHD DB91 copies the value of write cacheaddress storage area191 of entry M to the read cacheaddress storage area190. If a value other than 0 is stored in the read cacheaddress storage area190, then the read cache area in which thebuffer56 indicated by that value is arranged is freed.
• In step S181, theHD DB91 stores 0s into the read/write sessionnumber storage area184 of entry M and the write cacheaddress storage area191 of entry M. In step S182, theHD DB91 updates the value of the accesstime storage area192 of entry M by the current time.
• If information J indicative of object state is found “UPDATE” in step S177, the procedure goes to step S183. In step S183, theHD DB91 records the object recorded to write cache area d allocated in thebuffer56 to pages q and on of chunk p inobject recording area122. The procedure goes to step S180.
• If information J indicative of object state is found “REMOVE” in step S177, the procedure goes to step S184. In step S184, theHD DB91 records 0s to g bits subsequent to column q, row p of the areainformation recording area164. In step S185, theHD DB91 frees the write cache and read cache allocated in thebuffer56 by entry M. In step S186, theHD DB91 stores 0s into the objectidentifier storage area183 through the accesstime storage area192 of entry M. The processing goes to step S174.
• Then, the processes subsequent to step S172 are repeated until variable M is found not equal to or smaller than the number of entries S in step S172. If variable M is found not equal to or smaller than the number of entries S, the process for establishing the write session is completed.
• The following describes the process of step S133 shown inFIG. 28, namely, the process of discarding a write session with reference to the flowchart shown inFIG. 32. In step S191, theHD DB91 initializes variable M to 1. In step S192, theHD DB91 determines whether or not variable M is equal to or smaller than the number of entries S forming thesession managing information181. If variable M is found equal to or smaller than the number of entries S, the procedure goes to step S193.
• In step S193, theHD DB91 reads the value of the read/write sessionnumber storage area184 of entry M forming thesession managing information181 to determine whether or not the value matches session number Z. If the value of the read/write sessionnumber storage area184 of entry M is found not matching session number Z, then the procedure goes to step S194 to search for an entry in which the value of the read/write sessionnumber storage area184 of entry M matches session number Z. In step S194, theHD DB91 increments variable M by 1. The procedure returns to step S192 to repeat the above-mentioned processes.
• If the value of the read/write sessionnumber storage area184 of entry M is found matching session number Z in step S193, then the procedure goes to step S195. Namely, only the entry in which session number Z is stored in the read/write sessionnumber storage area184 is extracted and processed insteps195 and on.
• In step S195, theHD DB91 frees the write cache area allocated in thebuffer56 by entry M. In step S196, theHD DB91 determines whether or not the object state stored in the objectstate storage area189 is “CREATE”. If the object state is found not “CREATE”, the procedure goes to step S197.
• In step S197, theHD DB91 stores 0s into the read/write sessionnumber storage area184 and the write cacheaddress storage area191 of entry M. In step S198, theHD DB91 updates the value of the accesstime storage area192 of entry M by the current time. The procedure goes to step S194.
• It should be noted that, if the object state stored in the objectstate storage area189 of entry M is found “CREATE” in step S196, then the procedure goes to step S199. In step S199, theHD DB91 stores 0s in the areas other than the read/write sessionnumber storage area184 and the write cacheaddress storage area191 of entry M, namely stores 0s into the objectidentifier storage area183, read-only sessionnumber storage areas185 through188, the objectstate storage area189, the read cacheaddress storage area190, and the accesstime storage area192. Then, the procedure goes to step S194.
• Then, until variable M is found not equal to or smaller than the number of entries S in step S192, the above-mentioned processes are repeated. If variable M is found not equal to or smaller than the number of entries S, the write session discarding process comes to an end.
• The following describes an object search process by use of an example in which an object having object identifier OID=X (hereafter referred to as object X) with reference to the flowchart shown inFIG. 33. It should be noted that the session is assumed to have already been opened.
• In step S201, theHD DB91 gets entry M corresponding to object X. The process of getting the entry for object X will be described below with reference to the flowchart shown inFIG. 34.
• In step S211, theHD DB91 initializes variable M to 1. In step S212, theHD DB91 determines whether or not variable M is equal to or smaller than the number of entries S forming thesession managing information181. If variable M is determined equal to or smaller than the number of entries S, then the procedure goes to step S213.
• In step S213, theHD DB91 reads the value of the objectidentifier storage area183 of entry M forming thesession managing information181 to determine whether or not this value matches identifier OID=X of object X. If the value of the objectidentifier storage area183 of entry M is found not matching object identifier OID=X of object X, then the procedure goes to step S214 to search for an entry in which the value of the objectidentifier storage area183 matches object identifier OID=X of object X.
• In step S214, theHD DB91 increments variable M by 1. The procedure returns to step S212 to repeat the above-mentioned processes. If the value of the objectidentifier storage area183 of entry M is found matching object identifier OID=X of object X in step S123, it indicates that entry M corresponding to object X has been retrieved, so that this process comes to an end, the procedure returning toFIG. 33.
• It should be noted that, in step S213, the decision in which the value of the objectidentifier storage area183 of entry M does not match object identifier OID=X of object X is repeated and variable M is not equal to or smaller than the number of entries S in step S212, the procedure goes to step S215. In step S215, theHD DB91 determines an error, namely, theHD DB91 has failed to get entry M for object X, thereby ending this process. The procedure returns toFIG. 33.
• Returning toFIG. 33, if entry M for object X is retrieved in step S201, then the procedure goes to step S202. In step S202, because entry M for object X has been retrieved, theHD DB91 determines that object X is in thebuffer56, thereby ending this process.
• Conversely, if entry M for object X is not retrieved in step S201, the procedure goes to step S203. In step S203, theHD DB91 resolves object identifier OID=X of object X to get the chunk number, page number, and object X type number t of theobject recording area122 in which the object is recorded.
• In step S204, theHD DB91 reads the value of thesize recording area167 corresponding to type number t from the objecttype recording area163 and, on the basis of the retrieved value, computes the number of pages g necessary for recording object X.
• In step S205, theHD DB91 references the areainformation recording area164 to determine whether or not g bits subsequent to column q, row p are 1s. If the g bits subsequent to column q, row p of the areainformation recording area164 are found is, then the procedure goes to step S206. In step S206, theHD DB91 sets read cache area c equivalent to the number of pages g to thebuffer56. In step S207, theHD DB91 copies the data recorded to the pages g subsequent to page p of chunk q in theobject recording area122 to the read cache area c of thebuffer56.
• In step S208, theHD DB91 determines whether or not the object identifier recorded to a portion equivalent to the objectidentifier recording area201 of the data copied to the read cache area c matches object identifier X. If a match is found, it indicates that the data cached in the read cache area c is object X, so that the procedure goes to step S202.
• If the object identifier recorded to the portion equivalent to the objectidentifier recording area201 of the data copied to the read cache area c is found not matching object identifier X, the procedure goes to step S209. In step S209, theHD DB91 determines that object X does not exist in theobject recording area122 either, upon which this process comes to an end.
• The following describes an object X updating process with reference to the flowchart shown inFIG. 35. The object X updating process herein denotes the rewriting given data of object X.
• In step S221, theHD DB91 opens write session Z as with the above-mentioned process of step S121 described with reference toFIG. 29. In step S222, theHD DB91 gets entry M for object X as with the above-mentioned process of step S201 described with reference toFIG. 34.
• If entry M for object X is retrieved in the process of step S222, then theHD DB91 determines that object X is cached in the read cache area c set to thebuffer56, upon which the procedure goes to step S223. In step S223, theHD DB91 determines whether or not the value of the read/write sessionnumber storage area184 of entry M is 0. If the value of the read/write sessionnumber storage area184 of entry M is found 0, then the procedure goes to step S224.
• In step S224, theHD DB91 stores session number Z of the write session opened in step S221 into the read/write sessionnumber storage area184 of entry M. In step S225, theHD DB91 resolves object identifier OID=X of object X to get the chunk number, page number, and object X type number t of theobject recording area122 in which the object is recorded.
• In step S226, theHD DB91 reads the value of thesize recording area167 of the entry corresponding to type number t from the objecttype recording area163 and, on the basis of the retrieved value, computes the number of pages g necessary for recording object X. In step S227, theHD DB91 sets write cache area d equivalent to the number of pages g to thebuffer56. In step S228, theHD DB91 stores the address of write cache area d into the write cacheaddress storage area191 of entry M.
• In step S229, theHD DB91 copies the data in the read cache area c inbuffer56 to the write cache area d. In step S230, theHD DB91 records given data of object X to be updated to the arbitrarydata recording area202 of object X copied to the write cache area d.
• In step S232, theHD DB91 waits for the inputting of signal I corresponding to a user operation. In step S233, theHD DB91 determines whether or not signal I is commit, namely whether signal I establishes the session update operation. If signal I is found commit, then, the procedure goes to step S234. In step S234, theHD DB91 establishes write session Z as with the process of step S132 described above with reference toFIG. 31. Conversely, if signal I is found not commit, the procedure goes to step S235. In step S235, theHD DB91 discards write session Z as with the process of step S133 as described above with reference toFIG. 32.
• It should be noted that, if the value of the read/write sessionnumber storage area184 of entry M is found not 0 in step S223, it indicates that object X is being updated by a session other than session Z, so that the procedure goes to step S235.
• If, in step S222, entry M corresponding to object X is not retrieved, the procedure goes to step S236. In step S236, theHD DB91 allocates free entry M as with the process of step S123 described above with reference toFIG. 30.
• In step S237, theHD DB91 resolves object identifier OID=X of object X to get the chunk number, page number, and object X type number t of theobject recording area122 in which the object is recorded. In step S238, theHD DB91 reads the value of thesize recording area167 of the entry corresponding to type number t from the objecttype recording area163 and, on the basis of the retrieved value, computes the number of pages g necessary for recording object X. In step S239, theHD DB91 sets the read cache area c and write cache area d corresponding to the number of pages g to thebuffer56.
• In step S240, theHD DB91 stores the address of the read cache area c into the read cacheaddress storage area190 of entry M, the address of the write cache area d into the write cacheaddress storage area191 of entry M, and object identifier IOD=X of object X into the objectidentifier storage area183 of entry M.
• In step S241, theHD DB91 copies the data of object X recorded up to the number of pages g subsequent to page p of chunk q in theobject recording area122 to the read cache area c in thebuffer56. The procedure goes to step S229.
• As described, the file X updating process copies the data of file X from the read cache area c to the write cache area d, rewrites the data of file X cached in the write cache area d, and records the rewritten data to theobject recording area122 by the session establishing operation.
• The following describes a process of creating an object of a track corresponding, one to one, to the content data to be recorded to thefile recording area121, namely an stream object having object type number t′ with reference to the flowchart shown inFIG. 36. It should be noted that object type number t′ includes a basic type number (in this example, basic object number 2) and an entry number.
• In step S251, theHD DB91 opens a write session as with the process of step S121 described above with reference to the flowchart ofFIG. 29. In step S252, in order to allocate the pages of a chunk to which the stream object of object type number t′ is to be recorded, theHD DB91 reads the size of the object having object type number t′ from thesize recording area167 of entry t′ of the objecttype recording area163 to compute the number of pages of the chunk equivalent to the retrieved size. Let the computed number of pages be g.
• In step S253, theHD DB91 allocates free entry M among a plurality of entries forming thesession managing information181 as with the process of step S123 described above with reference to the flowchart ofFIG. 30. In step S254, theHD DB91 searches the areainformation recording area164 for a bit sequence in which g bits are continuously 0s. Let the start position of the retrieved bit sequence in which g bits are continuously 0s be column q, row p. In step S255, theHD DB91 stores object identifier OID (q, p, t′) formed by chunk number q, page number p, and object type number t′ as shown inFIG. 27 into the objectidentifier storage area183 of allocated entry M. Further, theHD DB91 stores session number Z into the read/write sessionnumber storage area184 of entry M of thesession managing information181 and records “CREATE” indicative of creation to the objectstate storage area189.
• In step S256, theHD DB91 allocates write cache area d equal to the number of pages g, which is the size of the stream object, into thebuffer56. In step S257, theHD DB91 stores the address of the allocated write cache area d in thebuffer56 into the write cacheaddress storage area191 of entry M of thesession managing information181.
• In step S258, theHD DB91 starts recording stream object X of objectbasic type2 shown inFIG. 26B to the write cache area d allocated in thebuffer56. To begin with, theHD DB91 records object identifier OID (q, p, t′) to the objectidentifier recording area201 of the write cache area d. In step S259, theHD DB91 gets file identifier F (the same value as the cluster number of the start cluster of a cluster sequence to which the present content data are recorded) of the content data to be created by theHD FS92, which corresponds to the stream object. In step S260, theHD DB91 records file identifier F to the fileidentifier recording area203 of the write cache area d.
• In step S261, theHD DB91 starts getting given data (for example, the name of a stream object to be created) of a stream object to be created. In step S262, theHD DB91 waits until the data retrieval is completed. It should be noted that, while the processes of steps S261 and S262 are performed, a file of the content data having file identifier F corresponding to the stream object concerned is created and recorded to thefile recording area121 by theHD FS92.
• In step S263, theHD DB91 records the retrieved given data to the arbitrarydata recording area202 of the write cache area d.
• In step S264, theHD DB91 waits for the inputting of signal I corresponding to a user operation. In step S265, theHD DB91 determines whether or not signal I is commit, namely, whether or not signal I establishes the session creation. If signal I is found commit, the procedure goes to step S266. In step S266, theHD DB91 establishes write session Z as with the process of step S132 described above with reference toFIG. 31.
• Conversely, if signal I is found not commit, then the procedure goes to step S267. In step S267, theHD DB91 discards write session Z as with the process of step S133 described above with reference toFIG. 32. In step S268, theHD DB91 requests theHD FS92 to delete file F. Thus, the process of stream object creation is performed.
• The following describes a process of searching for a stream object having object identifier OID=X (hereafter referred to as stream object X) with reference to the flowchart shown inFIG. 37. It should be noted that the session has already been opened.
• In step S271, theHD DB91 executes the same process as the object X search process described above with reference toFIG. 33. In step S272, theHD DB91 gets the object type number included in object identifier OID=X of object X retrieved in the process of step S271. Let the retrieved object type number be t. Further, theHD DB91 gets the object basic type number included in object type number t.
• In step S273, theHD DB91 determines whether or not the basic object type number of retrieved object X isbasic object type2. If the basic object type number of the retrieved object X is foundbasic object type2, it indicates that the retrieved object X is a stream object, so that the procedure goes to step S274. In step S274, theHD DB91 reads the file identifier from the fileidentifier recording area203 of the retrieved stream object X and supplies the retrieved file identifier to theHD FS92.
• It should be noted that, if the object having object identifier OID=X could not be retrieved in step S271, the procedure goes to step S275. Further, if the basic object type number of the retrieved object X is found notbasic object type2 in step S273, the procedure also goes to step S275. In step S275, theHD DB91 determines an error, namely that there is no stream object X, thereby ending the stream object search process.
• Now, referring toFIG. 38, there is shown a directory structure of the objects recorded to theobject recording area122. Theobject recording area122 is hierarchically formed by aroot211, folder list objects212, folder objects213, album objects214, and trackobjects215 in this order.
• TheHD DB91 can create a plurality of folder objects below eachfolder list object212. TheHD DB91 can create a plurality of album objects214 below eachfolder object213. TheHD DB91 can create a plurality of track objects215 below eachalbum object214. Eachtrack object215 corresponds to the content data for one piece of music.
• Eachfolder object213,album object214, andtrack object215 are objects which are presented to the user when selecting music to be played back. TheHD DB91 can create information objects (for example, a CC (Content Control) object216) other than the objects to be presented to the user, below theroot211, thefolder list object212, or thefolder object213.
• If thefolder object213 is created below thefolder list object212, theHD DB91 prohibits any other objects than thefolder object213 to be created below the samefolder list object212. If thealbum object214 is created below thefolder object213, theHD DB91 prohibits any other objects than thealbum object214 below thesame folder object213. TheHD DB91 also prohibits any other objects thantrack object215 to be created below thealbum object214.
• Each of the above-mentioned objects is recorded in accordance with the above-mentioned rules, so that afolder group217, analbum group218, and atrack group219 are constructed in theobject recording area122.
• The following describes the data format of each of the above-mentioned objects.
• FIG. 39 shows the data format of thefolder list object212. Because thefolder list object212 belongs tobasic object type1 shown inFIG. 26A, it is formed by the objectidentifier recording area201 and the arbitrarydata recording area202. To the objectidentifier recording area201 of thefolder list object212, a 4-byte object identifier OID is recorded.
• To the arbitrarydata recording area202 of thefolder list object212, the maximum number MAX (4 bytes) of folder objects213 that can be created below thisfolder list object212, the number of folder objects213 N (4 bytes) created below thisfolder list object212, and 4×100-byte Folder indicative of the matrix of IDs of folder objects213 created below thisfolder list object212 are recorded. The arbitrarydata recording area202 of thefolder list object212 has a 612-byte reserved area.
• FIG. 40 shows the data format of thefolder object213. Because thefolder object213 belongs tobasic object type1 shown inFIG. 26A, it is formed by the objectidentifier recording area201 and the arbitrarydata recording area202. To the objectidentifier recording area201 of thefolder object213, a 4-byte object identifier OID is recorded.
• To the arbitrarydata recording area202 of thefolder object213, the maximum number MAX (4 bytes) of album objects214 that can be created below thisfolder object213, the number of album objects214 N (4 bytes) created below thisfolder object213, 4×200-byte Album indicative of the matrix of IDs of album objects214 created below thisfolder object213, and 36-byte Title indicative of the folder name of thisfolder object213 are recorded. The arbitrarydata recording area202 of thefolder object213 has a 176-byte reserve area.
• FIG. 41 shows the data format of thealbum object214. Because thealbum object214 belongs tobasic object type1 shown inFIG. 26A, it is formed by the objectidentifier recording area201 and arbitrarydata recording area202. To the objectidentifier recording area201 of thealbum object214, a 4-byte object identifier OID is recorded.
• To the arbitrarydata recording area202 of thealbum object214, the maximum number MAX (4 bytes) of track objects215 that can be created below thisalbum object214, the number N (4-bytes) of track objects215 created below thisalbum object214, 4×400-byte Track indicative of the matrix of IDs of track objects215 created below thisalbum object214, 516-byte Title indicative of the name of thisalbum object214, 260-byte Artist indicative of the artist name of thisalbum object214, 8-byte Creation Date indicative of the date of creation of thisalbum object214, and 32-byte media key indicative of the media key of themusic CD3, which is the source of thisalbum object214 are recorded. The arbitrarydata recording area202 of thealbum object214 has a 1660-byte reserve area.
• FIG. 42 shows the data format of thetrack object215. Because thetrack object215 belongs tobasic object type2 shown inFIG. 26B, it is formed by the objectidentifier recording area201, the arbitrarydata recording area202, and fileidentifier recording area203. To the objectidentifier recording area201 of thetrack object215, a 4-byte object identifier OID is recorded. To the fileidentifier recording area203 of thetrack object215, a 4-byte SOID indicative of the file identifier of the content data (recorded to the file recording area121) corresponding on a one-to-one basis.
• To the arbitrarydata recording area202 of thetrack object215, 516-byte Title indicative of the music title of thistrack object215, 260-byte Artist indicative of the artist name of thistrack object215, 8-byte Time indicative of the playback time of thisalbum object214, 8-byte Last Access Date indicative of the date on which thistrack object215 was accessed last, 4-byte play counter (PC) indicative of the playback count of thistrack object215, 8-byte Creation Date on which thistrack object215 was created, and 12544-byte AC indicative of the music attribute and playback control information (the information for copyright protection) of the content data corresponding to thistrack object215 are recorded. The arbitrarydata recording area202 of thetrack object215 has a 980-byte reserved area.
• FIG. 43 shows the details of the 12544-byte AC to be recorded to the arbitrarydata recording area202 of thetrack object215. To the AC, 8-byte Ckey indicative of a content key, 1-byte Codec indicative of codec identification value, 1-byte Coded Attr indicative of codec attribute, 1-byte LT indicative of playback limitation information, 1-byte VLD indicative of validity check flag, 1-byte LCMLOGNUM indicative of the number of check-out destinations, 16-byte CDI indicative of codec dependency information, 20-byte CID indicative of content serial number, 8-byte PBS indicative of playback permission start date, 8-byte PBE indicative of playback permission end date, 1-byte XCC indicative of extended CC, 1-byte CT indicative of remaining playback count, 1-byte CC indicative of content control information, 1-byte CN indicative of remaining check-out count, 40-byte SRC indicative of source information, and 48×256-byte LCMLOG indicative of information including check-out destination device ID and flag are recorded.
• Especially, in the 1-byte CC indicative of content control information,bit1 from the MSB (Most Significant Bit) side is indicative of the presence of copyright (0=copyrighted; 1=not copyrighted).Bit2 from the MSB side is indicative of generation (0=original; 1=not original).Bits3 and4 from the MSB side are not in use.
• The meanings of the information indicated bybits5 through7 from the MSB side of CC are as follows. If 010 are recorded tobits5 through7 from the MSB side of CC, it indicates the check-out is enabled (edit is enabled). If 011 are recorded tobits5 through7 of the MSB side of CC, it indicates that move is enabled (the edit onPD5 is disabled). If 100 are recorded tobits5 through7 of the MSB side of CC, it indicates that import is enabled (the edit onPD5 is enabled). If 110 are recorded tobits5 through7 from the MSB side of CC, it indicates import is enabled (the edit on thePD5 is disabled).
• FIG. 44 shows the data format of the content data corresponding to thetrack object215 on a one-to-one basis. The content data are configured by 16-KB AT3H indicative of the header of ATRAC3, 16-KB PRT indicative of ATRAC3 part, and AT3SU-1 through AT3SU-N each being 16 KB long indicative of a sound unit sequence.
• FIG. 45 shows the data format of theCC object216. The CC object216 belongs tobasic object type2 shown inFIG. 26B. Therefore, theCC object216 is formed by the objectidentifier recording area201 and the arbitrarydata recording area202. To the objectidentifier recording area201 of theCC object216, a 4-byte object identifier OID is recorded.
• The arbitrarydata recording area202 of theCC object216 has a 16-byte reserved area. To the fileidentifier recording area203 of theCC object216, a 4-byte SOID indicative of the file identifier of the corresponding CC data (recorded to the file recording area121) is recorded.
• FIG. 46 shows the CC data format to be recorded to thefile recording area121. The CC data includes 10-KB CatFolder, 200-KB CatAlbum, and 600-KB CatTrack. CatFolder records the information indicative of the object identifier OID of thefolder object213 corresponding to the folder selected by the user. CatAlbum records the information indicative of the object identifier OID of thealbum object214 corresponding to the album selected by the user. CatTrack records the information indicative of the object identifier OID of thetrack object215 corresponding to the track selected by the user.
• Consequently, if the user selects a track to be played at the time of playback for example, the object identifier OID of thetrack object215 corresponding to the track selected by the user is determined on the basis of CatTrack of the CC data, the corresponding file identifier is retrieved from thedetermined track object215, and the content data are read for playback.
• The following describes the relationship between the data flow and the firmware at the time of the execution of each function of theaudio server1 with reference toFIGS. 47 through 56.
• FIG. 47 shows the data flow at the time when CD ripping is executed. In CD ripping in which themusic CD3 is recorded at high speeds, the digital audio data in themusic CD3 are read by the CD-ROM drive57 at a speed of CAV8x to be buffered in thebuffer56 under the control of the CD MW88. At the same time, under the control of the HD MW82, the digital audio data buffered in thebuffer56 are inputted in the WM screen60-2 for watermark detection. Next, under the control of the HD MW82, the digital audio data buffered in thebuffer56 are encoded by theencoder59 at an average speed of 5× in the ATRAC3 technique for encryption, the resultant encrypted data are buffered in thebuffer56, and then the buffered encrypted data are transferred to theHDD58 for recording. It should be noted that, although not shown, during CD ripping, the sound corresponding to the digital audio data under recording is outputted from thespeaker2.
• FIG. 48 shows the data flow at the time of CD recording. In CD recording in which themusic CD3 is recorded while being played, the digital audio data in themusic CD3 are read by the CD-ROM drive57 at a speed of CAV8x to be buffered in thebuffer56 under the control of the CD MW88. Then, under the control of the HD MW82, the digital audio data buffered in thebuffer56 are encoded by theencoder59 at an average speed of 5× in the ATRAC3 technique for encryption, the resultant encrypted data are buffered in thebuffer56, and then transferred to theHDD58 for recording. At the same time, under the control of the HD MW82, the audio data buffered in thebuffer56 are supplied to the WM screen60-2 for watermark detection.
• On the other hand, for monitor sounding, the buffered digital audio data are temporarily recorded in a ring buffer241 (FIG. 61) arranged in theHDD58 and then read into the audio I/F60-3 under the control of the HD MW82. Next, under the control of the AIO MW94, the digital audio data are transferred to the AD/DA62 to be converted in analog data, and the corresponding sound is output from thespeaker2.
• The details of CD ripping and CD recording will be described later with reference toFIGS. 57 through 70B.
• FIG. 49 shows the data flow at the time of HD recording for digital input. In HD recording in which digital input is encoded for recording on theHDD58, the digital audio data inputted from the AUX Interminal31 are supplied to theencoder59 via thesignal processor60 under the control of the AIO MW94. Next, under the control of the HD MW82, the digital audio data are encoded by theencoder59 for encryption on the basis of the ATRAC3 technique and the encrypted data are transferred to thebuffer56 and then to theHDD58 for recording. Further, under the control of the HD MW82, the watermark is detected by the WM screen60-2 of thesignal processor60. In addition, under the control of the AIO MW94, the digital audio data are transferred to the D/A62 by the audio I/F60-3 of thesignal processor60 to be converted into analog data, which are outputted from thespeaker2.
• FIG. 50 shows the data flow at the time of HD recording for analog input. In HD recording in which analog input is encoded to be recorded on theHDD58, the analog audio data inputted from the AUX Interminal31 are digitized by the A/D62 to be supplied to theencoder59 under the control of the AIO MW94. Next, under the control of the HD MW82, the digital audio data are encoded by theencoder59 for encryption on the basis of the ATRAC3 technique and the encrypted data are transferred to thebuffer56 and then to theHDD58 for recording. Further, under the control of HD MW82, the watermark is detected by the WM screen60-2 from the digital output of the A/D62. Then, under the control of the AIO MW94, the analog audio data inputted from the AUX Interminal31 are outputted from thespeaker2.
• FIG. 51 shows the data flow at the time of HD play. In HD play in which encoded data recorded to theHDD58 are played back, the encoded data read from theHDD58 are buffered in thebuffer56 and then decrypted and decoded by thedecoder59 under the control of the HD MW82. The resultant digital audio data are buffered in thebuffer56 and then transferred to the audio I/F60-3. Next, the digital audio data are transferred to the D/A62 by the audio I/F60-3 to be converted into analog data, which are outputted from thespeaker2.
• FIG. 52 shows the data flow at the time of CD play. In CD play in which themusic CD3 is played, the digital audio data stored in themusic CD3 are read by the CD-ROM drive57 and buffered in thebuffer56 to be transferred to the audio I/F60-3 under the control of the CD MW88. Next, under the control of the AIO MW94, the digital audio data are transferred to the D/A62 by the audio I/F60-3 to be converted into analog data, which are outputted from thespeaker2.
• FIGS. 53A and 53B show each the data flow at the time of MS play. In the MS play in which the encoded data stored in theMS4 are played, the encoded data stored in theMS4 are supplied to the MGMS I/F60-1 to be cross-certified and then decrypted and the resultant data are decoded by a decoder incorporated in thesignal processor60 under the control of the MS MW89 as shown inFIG. 53A. Next, under the control of the AIO MW94, the decoded digital audio data obtained by decoding are transferred to the D/A62 by the audio I/F60-3 to be converted into analog data, which are outputted from thespeaker2.
• As shown inFIG. 53B, the encoded data area read from theMS4 to be supplied to the MGMS I/F60-1 to be cross-certified and then decrypted under the control of the MS MW89. The decrypted encoded data are buffered in thebuffer56 and decoded by thedecoder59, the resultant digital audio data being outputted to the D/A62 via thebuffer56. Next, under the control of the AIO MW94, the audio data converted into analog data by the D/A62 are outputted from thespeaker2.
• FIG. 54 shows the data flow at the time of MS check-out/move-out. In the MS check-out in which the encoded data stored in theHDD58 are copied to theMS4 and in the MS move-out in which the encoded data stored in theHDD58 are moved to theMS4, the encoded data read from theHDD58 are buffered in thebuffer56 under the control of the HD MW82. Next, under the control of the MS MW89, the buffered encoded data are transferred to the MGMS I/F60-1 to be recorded to theMS4. It should be noted that the check-out and move-out operations will be detailed later.
• FIG. 55 shows the data flow at the time of MS import/move-in. In the MS import/move-in in which the encoded data stored in theMS4 are moved to theHDD58, the encoded data stored in theMS4 are transferred to thebuffer56 via the MGMS I/F60-1 under the control of the MS MW89. Next, under the control of the HD MW82, the buffered encoded data are transferred to theHDD58 for recording. It should be noted that the import/move-in operations will be detailed later.
• FIG. 56 shows the data flow at the time of PD check-out. In the PD check-out in which the encoded data stored in theHDD58 are copied to thePD5, the encoded data read from theHDD58 are buffered in thebuffer56 and then decrypted by the encoder/decoder59 and encrypted again for thePD5 to be buffered in thebuffer56 under the control of the HD MW82. Next, under the control of the PD MW90, the buffered encoded data are recorded to thePD5 via theUSB host controller54 and theUSB connector43.
• The following describes the details of CD ripping and CD recording with reference toFIGS. 57 through 70B. CD ripping is performed when the user presses the high-speed recording button24. The CD recording is performed when the user presses therecording button23.
• The following describes the difference between CD ripping and CD recording with reference toFIGS. 57 and 58. The upper portion ofFIG. 57 shows the monitor sound output period in CD ripping. The lower portion ofFIG. 57 shows the period of recording process (recording after encoding) in CD ripping. The upper portion ofFIG. 58 shows the period of monitor sound output in CD recording. The lower portion ofFIG. 58 shows the period of recording process (encoding and then recording) in CD recording.
• As clearly seen from the comparison betweenFIG. 57 andFIG. 58, CD ripping and CD recording are the same in the total time necessary for recording process. Namely, the process in which the audio data (PCM data) stored in themusic CD3 are recorded to theHDD58 by encoding the data on the basis of the ATRAC3 technique is performed at an average speed of 5× relative to the playback speed of the audio data.
• For example, if themusic CD3 storing six pieces of music each taking 10 minutes for its play, totaling 60 minutes, is recorded by CD ripping or CD recording, these pieces of music are sequentially recorded taking about two minutes each.
• The difference between CD ripping and CD recording lies in the period of monitor sound output.
• In the case of CD ripping, monitor sound is outputted only in a period in which the corresponding audio data are being recorded. In the above-mentioned example of themusic CD3, from the beginning of the first piece of music, sound for about two minutes is outputted at a normal playback speed, from the beginning of the second piece of music, sound for about two minutes is outputted at a normal speed, and, subsequently, from the beginning of each of the remaining pieces of music, sound for about two minutes is outputted at a normal speed. Therefore, monitor sound output ends upon the end of the recording process.
• In the case of CD recording, monitor sound is outputted regardless of the progress of the recording of the corresponding audio data. In the above-mentioned example of themusic CD3, all sound of the first piece of music is outputted at a normal playback speed, all sound of the second piece of music is outputted at a normal playback speed, and, subsequently, all sound of each of the remaining pieces of music is outputted at a normal playback speed. Therefore, even when the recording process ends, the monitor sound output of the corresponding audio data is continued until the end of the last sixth piece of music.
• It should be noted that CD ripping and CD recording may be switched between as required in the course of the process.
• FIG. 59 shows a state of thebuffer56 at the time when CD ripping or CD recording is performed. Thebuffer56 has a PCMdata reading buffer231 for buffering the audio data (PCM data) read from themusic CD3 before encoding and a encodeddata buffer232 for buffering the data encoded and encrypted by the encoder/decoder59.
• FIG. 60 shows the state transitions of the PCMdata reading buffer231 and the encodeddata buffer232 arranged in thebuffer56 and a PCMdata playback buffer251 arranged in the audio I/F60-3. Each of the PCMdata reading buffer231, the encodeddata buffer232, and PCMdata playback buffer251 is one of the transition states, the initial write enabled state, the writing state which is entered when data writing starts, the read enabled state which is entered when data writing ends, and the reading state which is entered when data reading starts. It should be noted that, when data reading ends from the reading state, the state returns to the write enabled state.
• FIG. 61 shows the structure of thering buffer241 arranged in theHDD58 for buffering the PCM data for monitor sound output when CD ripping or CD recording is performed.
• Thering buffer241 having a predetermined capacity (address0 through address max for the convenience of description) has a readpointer242 for pointing a read start address and awrite pointer243 for pointing a write start address. Thering buffer241 is divided into a read enabledarea244 from the address pointed by theread pointer242 to the address pointed by thewrite pointer243 in the forward direction and a write enabledarea245 from the address pointed by thewrite pointer243 to the address pointed by theread pointer242 in the forward direction. The capacity of the read enabledarea244 is referred to as a read margin. The capacity of the write enabled area is referred to as a write margin.
• FIG. 62 shows the data flow between the buffers at the time of CD ripping and CD recording. The PCM data stored in themusic CD3 are read by the CD-ROM drive57 to be buffered in the PCMdata reading buffer231 arranged in thebuffer56. The PCM data buffered in the PCMdata reading buffer231 are transferred to the encoder/decoder59 to be encoded and encrypted. The resultant encoded data are buffered in the encodeddata buffer232 arranged in thebuffer56. The encoded data buffered in the encodeddata buffer232 are transferred to theHDD58 to be recorded to thefile recording area121.
• On the other hand, the PCM data buffered in the PCMdata reading buffer231 are transferred to theHDD58 to be buffered in thering buffer241 arranged in theHDD58. The PCM data buffered in thering buffer241 are transferred to the PCMdata playback buffer251 incorporated in the audio I/F60-3 to be buffered and then transferred to the AD/DA62 to be converted into analog data, which are outputted from thespeaker2.
• The following describes a recording speed setting process associated with CD ripping and CD recording with reference to the flowchart shown inFIG. 63. This recording speed setting process is repetitively executed while themusic CD3 is selected as a sound source, namely while themusic CD3 is loaded on the CD-ROM drive57 and the CD is selected by operating thefunction button12.
• In step S281, the input handle middleware97 starts monitoring user's operation on the various buttons. In step S282, the input handle middleware97 waits until a user's operation is performed on the various buttons. If a user's operation on the various buttons is determined, the information thereof is transmitted to the main APP76. The main APP76 determines whether or not the operation is an operation performed on therecording button23. If the operation is found an operation performed on therecording button23, then the procedure goes to step S283.
• In step S283, the main APP76 notifies the HD APP77 of the operation of therecording button23. The HD APP77 transmits the information that therecording button23 has been operated to the CD RIPPING84 of the HD MW82. The CD RIPPING84 turns off the high-speed recording flag arranged by itself in theSDRAM53 for example. The procedure returns to step S281.
• If a user's operation on the various buttons is determined and this operation is found not on therecording button23 in the S282, the procedure goes to step S284. In step S284, the main APP76 determines whether or not the user's operation is on the high-speed recording button24. If the operation is found an operation on the high-speed recording button24, the procedure goes to step S285.
• In step S285, the main APP76 notifies the HD APP77 of the operation of the high-speed recording button24. The HD APP77 transmits the information that the high-speed recording button24 has been operated to the CD RIPPING84 of the HD MW82. The CD RIPPING84 turns on the high-speed recording flag, upon which the procedure returns to step S281.
• If the operation is found not the operation on the high-speed recording button24 in step S284, then the procedure returns to step S281.
• By the above-mentioned recording speed setting process, when the high-speed recording button24 is operated and the high-speed recording flag is turned on, the CD ripping as shown inFIG. 57 is executed. Conversely, when therecording button23 is operated and the high-speed recording flag is turned off, the CD recording as shown inFIG. 58 is executed. It should be noted that the switching from CD ripping to CD recording and vice versa may be performed any time in accordance with the user's button operation.
• The following describes a CD recording process with reference to the flowchart shown inFIG. 64. This CD recording process is a process which is controlled by the CD RIPPING84 included in the HD MW82, which starts when the music CD is loaded, and thefunction button12 is pressed to set the sound source to the CD and then therecording button23 or the high-speed button24 is operated.
• In step S291, the user selects a piece of music to be recorded from themusic CD3 during the recording pause state set by operating therecording button23 or the high-speed button24. To be more specific, the user operates acursor button17 to select a piece of music from the pieces of music recorded to themusic CD3 and establishes the selection by operating theenter button20. By repeating these operations, the user selects all pieces of music to be recorded. It should be noted that, if no music selecting operation is performed, it is assumed that all pieces of music recorded to themusic CD3 be selected.
• When the music selection has been completed, the user operates the play/pause button26. The procedure goes to step S292.
• In step S292, the CD RIPPING84 initializes the ring buffer information formed by the read start address and the like pointed by theread pointer242 set to thering buffer241. The following describes this ring buffer information initializing process with reference to the flowchart shown inFIG. 65. In step S301, the CD RIPPING84 sets the read start address pointed by theread pointer242 and the write start address pointed bywrite pointer243 to address0 of thering buffer241. In addition, the CD RIPPING84 sets the read margin of thering buffer241 to 0 and the write margin to the maximum value max. Thus, the ring buffer information initializing process is performed.
• Returning toFIG. 64, in step S293, the CD RIPPING84 sequentially selects the pieces of music selected in step S291 and executes the recording of one piece of music. The following describes the recording process for recording one piece of music with reference to the flowchart shown inFIG. 66. In step S311, the CD RIPPING84 requests the CD MW88 to buffer the PCM data of the piece of music to be recorded to themusic CD3 into the PCMdata reading buffer231 in the write enabled state in units of predetermined data amount (for example, in units of two seconds). When the PCM data of a predetermined data amount has been written (buffered), the state of the PCMdata reading buffer231 moves to the read enabled state.
• In step S312, the CD RIPPING84 causes the encoder/decoder59 to encode (encode and then encrypt) the PCM data of a predetermined amount buffered in the PCMdata reading buffer231. When the reading of the PCM data of a predetermined data amount from the PCMdata reading buffer231 has been completed, the state of the PCMdata reading buffer231 moves to the write enabled state.
• Also, the CD RIPPING84 starts a monitor sound output process. The monitor sound output process will be described later with reference toFIG. 67.
• In step S313, the CD RIPPING84 buffers the encoded data of a predetermined amount obtained by encoding into the encodeddata buffer232 in the write enabled state in thebuffer56. When the writing (buffering) of the encoded data of a predetermined amount (for example, equivalent to two seconds) has been completed, the state of the encodeddata buffer232 moves to the read enabled state.
• In step S314, the CD RIPPING84 records the encoded data of a predetermined amount buffered in the encodeddata buffer232 to thefile recording area121 of theHDD58. It should be noted that the process for recording the encoded data to thefile recording area121 in units of a predetermined amount is equivalent to the above-mentioned file creating process described with reference toFIG. 14. The object creating process described with reference to FIG.28 is also performed.
• In step S315, the CD RIPPING84 determines whether or not the encoded data for one piece of music have been recorded. If the encoded data for one piece of music are found not recorded, then the procedure returns to step S311 to repeat the above-mentioned processes. Then, if the encoded data for one piece of music have been recorded in step S315, the recording process for recording one piece of music comes to an end.
• After executing the recording process for one piece of music as described above, the procedure returns to step S294 shown inFIG. 64. In step S294, the CD RIPPING84 determines whether or not all pieces of music selected in step S291 have been recorded. If all selected pieces of music are found not recorded, the procedure returns to step S293 to record the next piece of music.
• Next, if all selected pieces of music are found recorded in step S294, this CD recording process comes to an end.
• The following describes the monitor sound output process started in step S312 with reference to the flowchart shown inFIG. 67. In step S321, the CD RIPPING84 determines whether or not the high-speed recording flag is on. If the high-speed recording flag is found on, then the procedure goes to step322.
• In step S322, the CD RIPPING84 determines whether or not the recording process for one piece of music of the corresponding PCM data has ended. If the recording process for one piece of music of the corresponding PCM data is found not ended, the procedure goes to step S323 to output monitor sound of the PCM data for which the recording of one piece of music is being executed.
• In step S323, the CD RIPPING84 starts writing the PCM data buffered in the PCMdata reading buffer231 to thering buffer241. Without waiting for the end of the process in step S323, the CD RIPPING84 starts reading the PCM data recorded to thering buffer241 in step S324.
• The following describes the writing process for writing to thering buffer241 in step S323 with reference to the flowchart shown inFIG. 68.
• In step S331, the CD RIPPING84 determines whether or not the high-speed recording flag is on. If the high-speed recording flag is found on, the procedure goes to step S332. In step S332, the CD RIPPING84 executes the buffer information initializing process described with reference toFIG. 65.
• In step S333, the CD RIPPING84 starts writing the PCM data recorded to the PCMdata reading buffer231 to the write enabledarea245 subsequent to the write start address pointed by thewrite pointer243 of the ring buffer information. In step S334, the CD RIPPING84 increments in the forward direction the write start address value pointed by thewrite pointer243 included in the ring buffer information by the amount of the PCM data written in step S333, thereby accordingly updating the write margin value and the read margin value.
• It should be noted that, if the high-speed recording flag is found not on in step S331, the procedure goes to step S335. In step S335, the CD RIPPING84 determines whether or not the size of the PCM data recorded to the PCMdata reading buffer231 is equal to or smaller than the write margin of thering buffer241 by referencing the ring buffer information. If the size of the PCM data recorded to the PCMdata reading buffer231 is found equal to or smaller than the write margin of thering buffer241, then the procedure goes to step S333.
• It should be noted that, if the size of the PCM data recorded to the PCMdata reading buffer231 is found not equal to or smaller than the write margin of thering buffer241 in step S335, then the procedure returns to step S331 to repeat the processes of step S331 and step S335 until the high-speed recording flag is found on in step S331 by changing the recording speed settings by the user or the size of the PCM data recorded to the PCMdata reading buffer231 is found not equal to or smaller than the write margin of thering buffer241 in step S335 due to the increase in the write margin of thering buffer241. Thus, the process of writing to thering buffer241 is performed.
• The following describes the process of reading from thering buffer241 in step S324 with reference to the flowchart shown inFIG. 69. In step S341, the CD RIPPING84 determines whether or not the PCMdata playback buffer251 incorporated in the audio I/F60-3 is in the write enabled state and waits until the PCM data playback buffer is in the write enabled state. If the PCM data playback buffer is found in the write enabled state, then the procedure goes to step S342.
• In step S342, the CD RIPPING84 reads the PCM data recorded to the read enabledarea244 of thering buffer241 in accordance with the read start address pointed by theread pointer242 of thering buffer241, and writes the PCM data to the PCMdata playback buffer251.
• In step S343, the CD RIPPING84 increments in the forward direction the value of the read start address pointed by theread pointer242 included in the ring buffer information by the amount of the PDM data read in step S342, thereby accordingly updating the write margin value and the read margin value.
• In step S344, the CD RIPPING84 moves the state of the PCMdata playback buffer251 to the read enabled state. Thus, the process of reading from thering buffer241 is performed.
• Returning toFIG. 67, the AIO MW94 outputs the PCM data buffered in the PCMdata playback buffer251 to the AD/DA62 in step S325. The AD/DA62 starts reproducing the inputted PCM data to output the corresponding sound from thespeaker2.
• In step S326, the CD RIPPING84 determines whether or not the PCM data for one piece of music has been played back. If the PCM data for one piece of music are found not completely played back, the procedure returns to step S321 to repeat the above-mentioned processes. If the PCM data for one piece of data are found not completely played back, the monitor sound output process comes to an end.
• It should be noted that, if the PCM data for one piece of music is found completely recorded in step S322, this monitor sound output process is immediately discontinued. Thus, the CD recording process is performed.
• It should be noted that, in the course of the CD recording process, CD ripping may be switched to CD recording and vice versa in accordance with the user's operation on therecording button23 or the high-speed recording button24.
• The following describes display examples to be displayed on thedisplay15 when CD ripping is performed, with reference toFIGS. 70A and 70B.FIG. 70A show an example of information associated with recording setting which is displayed immediately before starting recording. At this moment,display areas261 through267 are arranged on thedisplay15. In this display example, thedisplay area261 displays the information indicative of recording source and recording destination. Thedisplay area262 displays that the information associated with recording setting is displayed. Thedisplay area263 displays a folder name indicative of storage location. Thedisplay area264 displays the album name and artist name of the album to be recorded. Thedisplay area265 displays the bit rate to be used at the time of recording. Thedisplay area266 displays the recording level to be used at the time of recording. Thedisplay area267 displays the information that the recording starts when the play/pause button26 is pressed. The recording level at the time of recording is displayed.
• FIG. 70B shows a display example which is displayed during recording. At this moment,display areas271 through278 are arranged on thedisplay15. In this display example, the display are271 displays the information indicative of recording source and recording destination. Thedisplay area272 blinks a character string “In high-speed recording” indicative that CD ripping is being executed. Thedisplay area273 displays the album name and artist name of music being recorded. The display area274 displays the music number in themusic CD3 of the music being recorded. Thedisplay area275 displays the playback elapsed time of the music being recorded. Thedisplay area276 displays the remaining playback time of themusic CD3. Thedisplay area277 displays aprogress bar279 variable in length in accordance with the recording progress relative to the total number of pieces of music to be recorded. Thedisplay area278 displays the total number of pieces of music to be recorded and the number of pieces of music already recorded and during recording.
• For example, if CD ripping is being executed on all pieces music in an album of which playback time is 60 minutes, the length of theprogress bar279 displayed in thedisplay area277 becomes longer from the start of recording and extends up to the full length of thedisplay area277 in about 12 minutes because the recording is executed at the speed of about 5×.
• It should be noted that the length of theprogress bar279 in thedisplay area277 may be elongated in proportion to the music playback elapsed time rather than the recording progress.
• The following describes a method of reproducing the content data recorded to theHDD58 with reference toFIGS. 71 through 77. As described, theaudio server1 encodes the music recorded to themusic CD3 and records the content data as a file to theHDD58. In the case of specifying particular music to be played back, the user specifies the hierarchically arranged objects of folder, album, and track.
• Specifying the entire HDD, a given folder, or a given album as a playback area allows the specification of a plurality of music pieces collectively as the music pieces to be recorded. The playback of music is realized by decoding the content data corresponding to the tracks included in the play list to be created on the basis of the specified playback area.
• FIG. 71 shows an exemplary playback area. If the entire HDD enclosed by dashedlines281 is specified as a playback area, all track numbers in theHDD58 are registered in the play list as shown inFIG. 72.
• If a my select folder F1 enclosed by dashedlines282 is specified as the playback area, the album numbers of all albums belonging to the my select folder F1 are registered in the play list as shown inFIG. 73.
• If an album A1 of the my select folder F1 enclosed by dashedlines283 is specified as the playback area, the track numbers of all tracks belonging to the album A1 of the my select folder F1 are registered in the play list as shown inFIG. 74.
• If a track T1 of the album A1 belonging to a temporary folder F2 is specified as the music to be played back, the track T1 of the album A1 belonging to the temporary folder F2 is registered in the play list shown inFIG. 75.
• The following describes a process of creating the play list corresponding to the specified playback area with reference to the flowchart shown inFIG. 76.
• This play list creating process is controlled by the HD PLAY85 included in the HD MW82 and starts when thefunction button12 is operated to set the sound source to the HDD.
• In step S351, the HD PLAY85 determines whether or not the layer of the object indicative of the playback area selected by the user is the entire HDD. If the layer of the selected object is found not the entire HDD, then the procedure goes to step S352. It should be noted that the user selects a playback area by operating a playback area switching button (not shown) arranged on theremote controller7 or by operating thecursor button17, theenter button20, and the menu/cancelbutton21 arranged on thecover40 in a predetermined sequence.
• In step S352, the HD PLAY85 determines whether or not the layer of the object selected by the user is a folder. If the layer of the object selected by the user is found not a folder, then the procedure goes to step S353.
• In step S353, the HD PLAY85 determines that the layer of the object selected by the user is an album and the procedure goes to step S354.
• In step S354, the HD PLAY85 determines whether or not the play/pause button26 has been operated. If the play/pause button26 is found operated, the procedure goes to step S355. In step S355, the HD PLAY85 determines whether or not the play list belonging to the layer of the selected object has already been created. If the play list is found not created, the procedure goes to step S356. If the play list is found already created, step S356 is skipped.
• In step S356, the HD PLAY85 creates a play list corresponding to the layer of the selected object.
• It should be noted that, the play/pause button26 is found not operated in step S354, then the procedure returns to step S351 to repeat the above-mentioned processes.
• It should be noted that, if the layer of the selected object is found the entire HDD in step S351 or the layer of the selected object is found a folder in step S352, then the procedure goes to step S354. Thus, the play list creating process is performed.
• It should be noted that a plurality of play lists corresponding to various supposed playback areas may be created beforehand and recorded at a predetermined location and a corresponding play list may be read from among these play lists when the a play list is selected by the user.
• The following describes a playback process to be executed after the end of the above-mentioned play list creating process, taking the example where the play mode is set to the all music repeat, with reference to the flowchart shown inFIG. 77.
• In step S361, the HD PLAY85 determines whether or not the end of playback has been instructed by operating thestop button25. If the end of the playback is found not instructed, the procedure goes to step S362. In step S362, the HD PLAY85 sequentially specifies all tracks included in the play list each as a playback track.
• In step S363, the HD PLAY85 plays back the content data corresponding to each specified playback track. To be more specific, a track object corresponding to the playback track is identified on the basis of CC data, the file identifier of the corresponding content data is identified on the basis of the value of the fileidentifier recording area203 of the identified track object, and the content data are read on the basis of the identified file identifier (=the cluster number of the file recording area121). Next, the retrieved content data are decoded and outputted.
• When the playback of the content data corresponding to the playback track ends, the procedure returns to step S361 to repeat the above-mentioned processes. Then, in step S361, if the end of the playback is determined instructed upon operation of thestop button25, the playback process with the playback mode being all music repeat ends.
• It should be noted that, in the playback modes other than the all music repeat, only the method of specifying playback area and playback track differs from that of the all music repeat, so that the processes are the same between these modes.
• The following describes a process of moving out the content data recorded to theHDD58 of theaudio server1 to theMS4 with reference toFIGS. 78 through 81.
• The process of moving out the content data recorded to theHDD58 to theMS4 includes copying the content data from theHDD58 to theMS4 and deletes the copied content data from theHDD58.
• The following describes the move-out process with reference to the flowchart shown inFIG. 78. It should be noted that the move-out process is controlled by the MS MW89.
• This move-out process starts when the user displays the menu by operating the menu/cancelbutton21, selects “edit” by operating thecursor button17, displays the edit menu by operating theenter button20, selects “move out” by operating thecursor button17, operates theenter button20, selects the track to be moved out by operating thecursor button17 and theselect button18, displays the list of tracks to be moved out by operation theenter key20, and then operating theenter key20 with theMS4 loaded in theMS slot45.
• In step S371, the MS MW89 requests the C IN/C OUT87 to copy the content data recorded to theHDD58 to be moved out as rightless data (playback disabled data) to theMS4. It should be noted that, to provide rightless data, a rightful/rightless flag included in the attribute information of the content data is turned off. Namely, the attribute information indicative of right invalidity and the content data are copied to theMS4.
• In step S372, the C IN/C OUT87 generates a move-out log information indicative that the move-out process has started and records the generated log information to theHDD58. The move-out log information includes the information for identifying the track to be moved out. In step S373, the C IN/C OUT87 turns off the flag indicative whether the content data recorded to theHDD58 have the right or not to render the content data in theHDD58 rightless.
• In step S374, the MS MW89 turns on the flag indicative whether the content data copied to theMS4 have the right or not to render the content data in theMS4 rightful.
• In step S375, the C IN/C OUT87 deletes the content data from theHDD58. In step S376, the C IN/C OUT87 deletes the move-out log information generated in the process of step S372.
• The above-mentioned processes of steps S371 through S376 are the move-out processes for the content data corresponding to one track. These processes of steps S371 through S376 are repeated for each of the selected tracks.
• It should be noted that, if a move-out process is discontinued due to power outage for example during the process is on, a restore process for restoring the discontinued process is executed after the power is resumed. The restore process will be described later with reference toFIGS. 86 through 88.
• FIG. 79 shows the state transitions of a move-out process.State1 is the state before the stating of a move-out process. Namely, in this state, content data are recorded to theHDD58 of theaudio server1 and these content data have the right.
• State2 is a state after the execution of the process of step S371. Namely, instate2, the content data have been copied from theHDD58 to theMS4, resulting in the recording of the content data to both theHDD58 and theMS4 and the content data in theHDD58 have the right while the content data in theMS4 have no right.
• State3 is a state after the execution of the process of step S373. Namely, instate3, content data are recorded to both theHDD58 and theMS4 and the content data in theHDD58 and the content data inMS4 have no right.
• State4 is a state after the execution of the process of step S374. Namely, instate4, content data are recorded to both theHDD58 and theMS4 and the content data on theHDD58 has no right while the content data in theMS4 has the right.
• State5 is a state after the execution of the process of step S375. Namely, instate5, the content data recorded to theHDD58 have been deleted and therefore only theMS4 records the content data, which have the right.
• FIG. 80 shows a display example on thedisplay15 at the time of selecting tracks to be moved out. The display shows only the pieces of music that can be moved out.
• FIG. 81 show a display example on thedisplay15 during a move-out process. Adisplay area291 on thedisplay15 blinks a character string “Move out” indicative that a move-out process is being executed. Acheck marker292 is displays by each moved out track. Adisplay area293 displays the information indicative of the progress of the move-out process (the number of tracks being moved out or already moved out/the total number of tracks to be moved out).
• The following describes a process of moving in the content data recorded to theMS4 to theHDD58 of theaudio server1 with reference toFIGS. 82 through 81.
• The process of moving in the content data recorded to theMS4 to theHDD58 denotes a sequence of processes in which the content data recorded to theMS4 are copied to theHDD58 and then the content data recorded to theMS4 are deleted.
• The following describes this move-in process with reference to the flowchart shown inFIG. 82. It should be noted that the moving-in process is controlled by the MS MW89.
• This move-in process starts when the user displays a menu by operating the menu/cancelbutton21, selects “edit” by operating thecursor button17, displays the edit menu by operating theenter button20, selects “move in” by operating thecursor button17 and then operates theenter button20, selects the content data to be moved in from the content data recorded to theMS4 by operating thecursor button17 and theselect button18, displays the list of content data to be moved in by operating theenter key20, and, after operating theenter key20, operates the play/pause button26 with theMS4 loaded in theMS slot45.
• In step S381, the MS MW89 requests the C IN/C OUT87 to generate move-in log information indicative of the starting of a move-in process and record the generated log information to theHDD58. The move-in log information includes the information for identifying the content data to be moved in.
• In step S382, the C IN/C OUT87 copies the content data to be moved in from theMS4 to theHDD58 as the data having no right. In step S383, the MS MW89 turns off the flag indicative whether the content data recorded to theMS4 have the right or not to render the content data in theMS4 rightless.
• In step S384, the C IN/C OUT87 turns on the flag indicative whether the content data copied to theHDD58 have the right or not to render the content data in theHDD58 rightful.
• In step S385, the C IN/C OUT87 requests the MS MW89 to delete the content data from theMS4. In step S386, the C IN/C OUT87 deletes the move-in log information generated in the process of step S382.
• The above-mentioned processes of steps S381 through S386 are the move-in process for the content data corresponding to one track. The processes in steps S381 through S386 are repeated for each of the selected tracks.
• It should be noted that, if a move-in process is discontinued due to power outage for example during the process is on, a restore process for restoring the discontinued process is executed after the power is resumed.
• FIG. 83 shows the state transitions of a move-in process.State11 is a state before a move-in process starts. Namely, instate11, content data are recorded to theMS4 and the content data in theMS4 have the right.
• State12 is a state after the execution of the process of step S382. Namely, instate12, by copying the content data from theMS4 to theHDD58, the content data are recorded to both theMS4 and theHDD58 and the content data in theMS4 are rightful while the content data in theHDD58 are rightless.
• State13 is a state after the execution of the process of step S383. Namely, the content data are recorded to both theMS4 and theHDD58 and the content data in theMS4 and the content data in theHDD58 are both rightless.
• State14 is a state after the execution of the process of step S384. Namely, instate14, the content data are recorded to both theMS4 and theHDD58 and the content data in theMS4 are rightless while the content data in theHDD58 are rightful.
• State15 is a state after the execution of the process of step S385. Namely, by deleting the content data from theMS4, the content data are recorded only to theHDD58 and therefore the content data in theHDD58 are rightful.
• FIG. 84 shows a display example on thedisplay15 at the time of selecting content data to be moved in. Of the content data recorded to theMS4, only the content data that can be moved in are displayed on thedisplay15.
• FIG. 85 shows a display example on thedisplay15 during the move-in process. Adisplay area301 of thedisplay15 blinks a character string “Move in” indicative that a move-in process is being executed. Acheck marker302 is displayed by the content data which have been moved in. Adisplay area303 displays the information indicative of the progress of the move-in process (the number of tracks being moved in or already moved in/the total number of tracks to be moved in).
• Thus, the move-in process is performed. A process for importing content data from theMS4 to theHDD58 is performed in substantially the same manner. The difference between move-in process and import process lies in the handling of the content data recorded to theHDD58 by these processes.
• Theaudio server1 may move out the content data recorded to theHDD58 by a move-in process toother MS4 orPD5 and check out these content data. However, althoughaudio server1 may check out the content data recorded to theHDD58 by an import process toother MS4 orPD5, but is disabled to move out these content data.
• The following describes a restore process for compensating the discontinuation of a move-out process or a move-in process due to power outage for example during the execution of these processes, with reference toFIG. 86. This restore process is started by the MS MW89 as soon as the power supply is resumed.
• In step S391, the MS MW89 determines whether or not there is move-out log information in theHDD58. If the move-out log information is found in theHDD58, the procedure goes to step S392 to compensate the discontinued execution of the move-out process.
• In step S392, the MS MW89 executes a move-out restore process. The following describes the move-out restore process with reference to the flowchart shown inFIG. 87.
• In step S401, the MS MW89 determines whether or not the content data of theHDD58 are rightless or not. If the content data of theHDD58 are found rightless, the procedure goes to step S402. The content data of theHDD58 being rightless indicatesstate3 orstate4 inFIG. 79.
• In step S402, the MS MW89 deletes the content data from theHDD58. If the content data in theHD58 are deleted instate4, the state shifts tostate5 in which the move-out process has been completed. If the content data are deleted from theHDD58 instate3, the state shifts to the state in which the content data having the rightless data remain in theMS4.
• At this moment, the user loses the content data, but the copyright of the content data is protected. The content data having the rightless data in theMS4 may be deleted by the user by use of a general-purpose file editing application, so that no wasted data need be left in theMS4, which are the content data having rightless data.
• Conversely, if a restore process is performed such that the content data having rightless data in theMS4 are deleted to make the content data having rightless data remain inHDD58, the wasted data which are the content data having rightless data remain recorded to theHDD58. Because the content data having rightless data do not occur as a result of normal operations, thededicated audio server1, one embodiment of the present invention, does not have a function for deleting the content data having rightless data as instructed by the user.
• Therefore, to protect the copyright of content data and prevent theaudio server1 from recording invalid data, it is desired to delete the content data from theHDD58 as shown in step S402.
• It should be noted that, if the content data in the58 are determined not rightless in step S401, step S402 is skipped. Namely, if the content data in theHDD58 are not rightless, it indicatesstate2 shown inFIG. 79. At this moment, the content data having rightless data remain in theMS4; however, as described above, the content data having rightless data in theMS4 are deletable by the user by use of a general-purpose file editing application, so that there main no wasted data which are the content data having rightless data in theMS4.
• In step S403, the MS MW89 deletes the move-out log information from theHDD58.
• The procedure returns toFIG. 86. In step S393, the MS MW89 determines whether or not there is move-in log information in theHDD58. If the move-in log information is found in theHDD58, then the procedure goes to step S394 to compensate the discontinued move-in process.
• In step S394, the MS MW89 executes a move-in restore process. The following describes a move-in restore process with reference to the flowchart shown inFIG. 88.
• In step S421, the MS MW89 determines whether or not the content data in theHDD58 are rightless or not. If the content data in theHDD58 are found rightless, then the procedure goes to step S422. If the content data in theHDD58 are rightless, it indicatesstate12 orstate13 shown inFIG. 83.
• In step S422, the MS MW89 deletes the existing content data from theHDD58.
• If the state isstate12, the deletion of the content data existing in theHDD58 causes the state to shift tostate11, which is before the execution of move-in process. If the content data existing in theHDD58 are deleted instate13, the content data having rightless data remain in theMS4.
• At this moment, the user loses the content data, but the copyright of the content data is protected. The content data having rightless data in theMS4 may be deleted by the user by use of a general-purpose file editing application, so that there remain no wasted data which are the content data having rightless data in theMS4.
• Conversely, if a restore process is performed such that the content data having rightless data in theMS4 are deleted to make the content data having rightless data remain inHDD58, the wasted data which are the content data having rightless data remain recorded to theHDD58. Because the content data having rightless data do not occur as a result of normal operations, thededicated audio server1, one embodiment of the present invention, does not have a function for deleting the content data having rightless data as instructed by the user.
• Therefore, to protect the copyright of content data and prevent theaudio server1 from recording invalid data, it is desired to delete the content data from theHDD58 as shown in step S422.
• It should be noted that, if the content data in the58 are determined not rightless in step S421, step S422 is skipped. Namely, if the content data in theHDD58 are not rightless, it indicatesstate14 orstate15 shown inFIG. 83.State15 presents no problem because the move-in process has been completed therein. Instate14, however, the content data having rightless data remain in theMS4; as described above, the content data having rightless data in theMS4 are deletable by the user by use of a general-purpose file editing application, so that there remain no wasted data which are the content data having rightless data in theMS4.
• In step S423, the MS MW89 deletes the move-in log information from theHDD58. Thus, the move-in restore process is performed. The procedure returns toFIG. 86, upon which the restore process comes to an end.
• It should be noted that, if the move-out log information is found not existing in theHDD58 in step S391 ofFIG. 86, it may indicate that the move-out process has normally ended or the state isstate1 orstate2 shown inFIG. 79. If the move-out process has normally ended or instate1 which is before the execution of the move-out process, the move-out restore process may be skipped.
• Instate2, too, the content data having rightless data remain in theMS4. However, because the content data having rightless data may be deleted by the user by use of a general-purpose file editing application, no wasted data which are the content data having rightless data remain in theMS4. Therefore, the process of step S392 is skipped.
• If the move-in log information is determined not existing in theHDD58 in step S393, then it may indicate that the move-in process has normally ended or the state isstate11 shown inFIG. 83. If the move-in process has normally ended and instate11 which is the state before the execution of a move process, the move-in restore process may be skipped, so that the process of step S394 is skipped.
• Even if a restore process is discontinued due to power outage, the process is executed from step S391 again upon power resumption, the discontinued process may be compensated. Thus, the restore process is performed.
• The following describes a process of checking out content data from theHDD58 of theaudio server1 to theMS4 with reference toFIGS. 89 through 91.
• The process of checking out content data from theHDD58 denotes a process of temporarily creating a copy of the content data recorded to theHDD58 into theMS4 for example and using this copy recorded to theMS4. The check-out permission count of the content data is set beforehand and this check-out permission count is decremented by 1 every time a check-out process is executed. However, by executing a check-in process to be described later, the check-out permission count is incremented by 1.
• The following describes a check-out process with reference to the flowchart shown inFIG. 89. It should be noted that a check-out process is controlled by the C IN/C OUT87 of the HD MW82.
• This check-out process starts when the user displays the menu by operating the menu/cancelbutton21, selects “edit” by operating thecursor button17, displays the edit menu by operating theenter button20, selects “check out” by operating thecursor button17, and operates theenter button20 with theMS4 loaded in theMS slot45.
• In step S441, the C IN/C OUT87 controls theHD DB91 to get the check-out permission count (the number of times content data may still be checked out) for the content data corresponding to all tracks belonging to a currently selected album. The check-out permission count of content data is recorded to the CN included in the AC (FIG. 42) of each corresponding track object (FIG. 43).
• In step S442, the C IN/C OUT87 requests the associated firmware to display, on thedisplay15, the information (music title, check-out permission count, and so on) about the tracks of which check-out permission count is 1 or more.FIG. 90 shows a display example on thedisplay15. Adisplay area311 on thedisplay15 displays “HDD” as the information indicative of the sound source of check-out. Adisplay area312 shows the check-out permission count of the content data corresponding to each track.
• In step S443, the C IN/C OUT87 determines whether or not a track to be checked out has been selected from among the displayed check-out enabled tracks by the user operating thecursor button17 and theselect button18. If a track to be checked out is found selected, the procedure goes to step S444.
• In step S444, the C IN/C OUT87 adds the selected track to the check-out list. In step S445, the C IN/C OUT87 decrements the check-out permission count of the content data corresponding to the selected track by 1. The procedure returns to step S441 to repeat the above-mentioned processes.
• It should be noted that, if the track to be checked out is found not selected in step S443, the procedure goes to step S446. In step S446, the C IN/C OUT87 discriminates whether or not the user issues an instruction to execute check-out by operating theenter key20 so that the list of tracks to be checked out is displayed and then operating theenter key20. If the execution of check-out is found not instructed, the procedure returns to step S441 to repeat the above-mentioned processes.
• Next, in step S446, if the execution of check-out is found instructed, the procedure goes to step S447. In step S447, the C IN/C OUT87 reads from theHDD58 the content data corresponding to the track included in the check-out list and requests the MS MW89 to copy the retrieved content data into theMS4. It should be noted that the copy of the content data includes the information for identifying theHDD58, the check-out source.
• In step S448, the C IN/C OUT87 decrements the check-out permission count recorded to the CN of the AC of the track object corresponding to the copied content data by 1 to update the value of the CN. Also, the C IN/C OUT87 records the information for identifying theMS4 as the check-out destination information to LCMLOG of the AC.
• Although the description is omitted here, a flag indicative of playback enabled or disabled (the validity or invalidity of the right) is used in the same manner as the above-mentioned move-out process, thereby compensating power outage for example and preventing the unauthorized creation of copies from occurring.
• FIG. 91 shows a display example on thedisplay15 during the execution of a check-out process. Adisplay area321 blinks a character string “Check out” indicative that a check-out process is being executed. Acheck mark322 is displayed by each track that has been checked out. Apointer323 is displayed by the track which is currently being checked out. Adisplay area324 displays the information indicative of the progress situation of the check-out process (the number of pieces of content data being check out or already checked out/the total number of pieces of content data included in the check-out list). Thus, the check-out process is performed.
• The following describes a process of checking in the content data checked out to theMS4 into theHDD58 with reference toFIGS. 92 and 93.
• A process of checking out the content data recorded to theMS4 denotes a process in which the copy of the content data temporarily reproduced on theMS4 is deleted from theHDD58 and the check-out permission count of theHDD58 is incremented by 1 to restore the check-out permission count to the original value.
• The following describes a check-in process with reference to the flowchart shown inFIG. 92. It should be noted that a check-in process is controlled by the C IN/C OUT87 of the HD MW82.
• This check-in process starts when the user displays the menu by operating the menu/cancelbutton21, selects “Edit” by operating thecursor button17, displays the edit menu by operating theenter button20, selects “Check in” by operating thecursor button17, and operates theenter button20 with theMS4 loaded in theMS slot45.
• In step S451, the C IN/C OUT87 requests the MS MW89 to identify the content data which can be checked in (the content data checked out from theHDD58 of the audio server1) from among the data recorded to theMS4 and requests the associated firmware to display on thedisplay15 the information about the content data which can be checked in.
• In step S452, the C IN/C OUT87 displays on thedisplay15 the information (music title and so on) about the tracks which can be checked in.FIG. 93 shows a display example on thedisplay15. Adisplay area331 on thedisplay15 displays “MS” as the information indicative of the sound source of check-in. Anarrow332 displayed after the information such as the music title name of the content data denotes that the content data can be checked in.
• In step S452, the C IN/C OUT87 determines whether or not the content data to be checked in have been selected from among the displayed content data which can be checked in by the user operating thecursor button17 and theselect button18. If the content data to be checked in are found selected, the procedure goes to step S453.
• In step S453, the C IN/C OUT87 adds the selected content data to the check-in list. The procedure returns to step S451 to repeat the above-mentioned processes.
• If the content data to be checked in are found not selected in step S452, then the procedure goes to step S454. In step S454, the C IN/C OUT87 discriminates whether or not an instruction to execute check-in is issued by the user operating theenter key20 to display a list of contents data to be checked in and further operating theenter key20. If the execution of check-in is found not instructed, the procedure returns to step S451 to repeat the above-mentioned processes.
• Next, if the execution of check-in is found instructed in step S454, the procedure goes to step S455. In step S455, the C IN/C OUT87 requests the MS MW89 to delete the content data in theMS4 included in the check-in list (or may only turn off the flag indicative whether playback is enabled or disabled; namely, may only render the content data rightless).
• In step S456, the C IN/C OUT87 increments the check-out permission count recorded to the CN of the AC of the track object corresponding to the original content data recorded to theHDD58 by 1 to update the value of the CN. At the same time, the C IN/C OUT87 deletes the information for identifying theMS4 recorded as the check-out destination information from the LCMLOG of the AC. Thus, the check-in process is performed.
• The following describes, with reference toFIGS. 94 through 97, an exchange process for continuously executing a process of check-in the content data recorded to theMS4 and a process of collectively checking out a plurality of tracks belonging to an album including a track last played back by the HD play function.
• This exchange process starts when the user operates theexchange button22 with theMS4 loaded in theMS slot45.
• In step S461, the C IN/C OUT87 requests the MS MW89 to identify the content data which can be checked in from among the data recorded to theMS4. In step S462, the C IN/C OUT87, in cooperation with the MS MW89, checks in, piece by piece, the content data recorded to theMS4 which can be checked in, in the same manner as the above-mentioned check-in process described with reference toFIG. 92.
• FIG. 95 shows a display example on thedisplay15 during the execution of the process of step S462. A display area381 on thedisplay15 displays “MS” as the information indicative of the sound source of check-in. Adisplay area382 blinks a character string “Now Check in” indicative that check-in is being executed. An “X”marker383 displayed before the information such as music title name of content data indicates that the content data concerned are disabled for check-in. Acheck marker384 indicates that the content data concerned have already been checked in. Apointer385 indicates that the check-in of the content data concerned is being executed.
• In step S463, the C IN/C OUT87 determines whether or not the content data enabled for check-in in theMS4 have all been checked in. If the content data enabled for check-in in theMS4 are found not all checked in, then the procedure returns to step S462 to check in next content data. Then, in step S463, if the content data in theMS4 enabled for check-in are found all checked in, the procedure goes to step S464.
• In step S464, the C IN/C OUT87, in cooperation with theHD DB91, determines an album of which tracks are all checked out together. To be more specific, for example, theHD DB91 identifies the track played back last on the basis of the last access date (FIG. 42) of each track object recorded to theobject recording area122 to determine the album to which the identified track belongs as a check-out album.
• In step S465, the C IN/C OUT87 selects one track (namely, content data) from the check-out album. In step S466, the C IN/C OUT87 determines whether or not the selected content data are enabled for check-out. If the selected content data are found enabled for check-out, the procedure goes to step S467.
• In step S467, the C IN/C OUT87 requests the MS MW89 to determine whether or not theMS4 has enough capacity for checking out the selected content data. If theMS4 is found having an enough capacity for checking out the selected content data, the procedure goes to step S468.
• In step S468, the C IN/C OUT87 checks out the selected content data in the same manner as the check-out process described with reference toFIG. 89.
• FIG. 96 shows a display example on thedisplay15 during the execution of the process of step S468. Adisplay area391 on thedisplay15 shows “HDD” as the information indicative of the sound source of check-out. Adisplay area392 blinks a character string “Now Check out” indicative that check-out is being executed. An “X” marker displayed before the information such as music title name of content data indicates that the content data concerned are disabled for check-out. A check marker indicates that the content data concerned have already been checked out.
• In step S469, the C IN/C OUT87 determines whether or not all tracks (namely, content data) included in the check-out album have been selected in step S465. If all content data are found not selected in step S465, the procedure returns to step S465 to repeat the above-mentioned processes. If all content data are found selected in step S465, this exchange process comes to an end.
• It should be noted that, if the selected content data are found not enabled for check-out in step S466, then steps S467 and S468 are skipped. If theMS4 is found not having enough capacity for checking out the selected content data in step S467, step S468 is skipped.
• FIG. 97 shows a display example on thedisplay15 immediately after the completion of an exchange process. Adisplay area401 on thedisplay15 shows a character string “COMPLETE” indicative of the completion of an exchange process.
• As described, the user may only operate theexchange button22 to automatically execute the check-in process for checking in fromMS4 to theHDD58 and the check-out process for checking out from theHDD58 to theMS4. Thus, the exchange process is performed.
• It should be noted that the above-mentioned move-out process, move-in process, import process, check-out process, and check-in process may be executed not only between theHDD58 and theMS4 but also between theHDD58 and thePD5 connected to theconnector43.
• FIG. 98 shows an exemplary configuration of the hardware of thePD5. An LSI (Large Scale Integration)410 for implementing thePD5 incorporates aCPU411 for controlling theentire PD5. TheCPU411 is connected to aROM412, aRAM413, aDMA controller414, a DSP (Digital Signal Processor)415, abuffer416, an LCD interface (I/F)417, a serial interface (I/F)418, and interfaces419 and420 via abus421.
• TheROM412 stores the programs for realizing various functions of thePD5, device ID and encryption key and the like. TheRAM413 temporarily stores predetermined data and programs when theCPU411 executes various processes. TheDMA controller414 controls the data transfer with aUSB controller424 via thebuffer416, aflash memory426, and theserial interface418. TheDSP415 decodes the content data recorded to theflash memory426 for example. TheDSP415 has a DES engine to encrypt/decrypt content data by use of the encryption key. Thebuffer416 temporarily buffers the data of which transfer is controlled by theDMA controller417.
• TheLCD interface417 is followed by anLCD driver422 and anLCD423. Theserial interface418 is followed by theUSB controller424 and aUSB connector425. TheUSB controller424 controls the data communication with theaudio server1 connected via theUSB connector425. Theflash memory426 connected viainterface419 stores the content data moved out for example from theaudio server1 and additional information such as music titles. Theinterface420 is followed by aDAC427 and an amplifier (AMP)428. Apower supply section429 supplies power to theLSI410.
• The audio data obtained by a decoding process by theDSP415 are outputted to a headphone for example via theinterface420, theDAC427, and the amplifier (AMP)428.
• The move-out process and so on between theHDD58 and theMS4 and the move-out process and so on between theHDD58 and thePD5 are substantially the same, so that the following describes only the differences between them.
• The content data to be recorded to theMS4 are encrypted by use of the same encryption key as that for the encryption of the content data stored in theHDD58 of theaudio server1. Therefore, between theHDD58 and theMS4, the encrypted content data can be moved out as it is without being decrypted.
• On the contrary, the content data to be recorded to thePD5 are encrypted by use of an encryption key which is different from the encryption key for encrypting the content data stored in theHDD58 of theaudio server1. Therefore, as described with reference toFIG. 56, between theHDD58 and thePD5, the content data recorded to theHDD58 are decrypted and then encrypted again by use of a different encryption key for thePD5 and the resultant content data are moved out.
• Thus, the move-out process, move-in process, import process, check-out process, and check-in process are executed between theHDD58 and thePD5.
• The following describes a store function and a restore function of theaudio server1 with reference toFIGS. 99 through 107.
• The store function is a function for temporarily storing, where the recording capacity of theMS4 is running short because of presence of data (for example, a still picture file or a voice file) which cannot be played back by theaudio server1 other than contents data recorded already in theMS4, the data recorded already in theMS4 other than the contents data as a single archive file which includes files of the same type recorded simultaneously into theHDD58.
• The restore function denotes the function for restoring the corresponding directory and its files into theMS4 by use of the archive file generated by the store function on theHDD58.
• FIG. 99 shows the types of directories and data files which are possibly recorded to theMS4.
• File MEMSTICK.ind indicates that the recording medium to which a file concerned is recorded is the Memory Stick. Directory DCIM is a directory storing still picture files generated by a digital still camera for example. Directory VOICE is a directory for storing voice files generated by an IC recorder for example. Directory HIFI is a directory for storing the content data attached with copyright information checked out or moved out from theaudio server1 for example. Directory CONTROL is a directory for storing control information files. Directory TEL is a directory for storing telephone and facsimile information files. Directory OPEN-R is a directory for storing entertainment robot information files. Directory POSITION is a directory for storing positional information files. Directory PALM is a directory for storing PALM OS data files. Directory MP3 is a directory for storing MP3 files. Directory MSxxxxxx is a directory for storing vendor-unique information files (“xxxxxx” is information for identifying the vendor).
• FIG. 100 shows the recording positions of archive files which are generated, by the store function, under the directory structure of theobject recording area122 in theHDD58. On the layer on which folder objects217 are arranged, an MS data object501 is arranged. On the layer below the MS data object501, an MS store/restoreobject502 is arranged. The archive files (inFIG. 100, MS data #1.DCIM, MS data #2.VOICE, and MS data #3.DCIM) are recorded on the layer below the MS store/restoreobject502.
• It should be noted that the name of archive file such as “MS data #1” may be set by the user in an arbitrary manner.
• The following describes a store process by the HD MW82 for implementing the store function with reference to the flowchart shown inFIG. 101. This store process starts when the user selects theMS4 as sound source by repetitively pressing thefunction button12, selects “Edit” by operating thecursor button17 after pressing the menu/cancelbutton21, presses theenter button20, selects “Store (MS HDD)” by operating thecursor button17, and then presses theenter button20.
• In step S501, the HD MW82 requests the MS MW89 to search the directories recorded to theMS4 for a directory to be stored, namely, a directory other than directory HIFI, computes the capacity of the retrieved directory, and displays the computed capacity on thedisplay15.
• FIG. 102 shows a display example on thedisplay15 when theMS4 is selected as sound source.Display areas511 and512 show character strings “MS” and “Memory Stick” indicative of sound sources. Adisplay marker513 indicates a still picture file storage directory; in this example, its capacity is 8 MB. Adisplay marker514 indicates a voice file storage directory; in this example, its capacity is 1 MB.
• Returning toFIG. 101, in step S502, the HD MW82 accepts the user operation for selecting the directory to be stored and waits until the user performs a select operation.FIG. 103 shows an display example on thedisplay15 in which a list of directories which can be stored is displayed. Adisplay area521 shows the information that the list of directories which can be stored is displayed. Adisplay area522 shows that there is a still picture file storage directory which can be stored and its capacity is 8 MB. Adisplay area524 shows that there is a voice file storage directory which can be stored and its capacity is 1 MB. Acursor524 points the still picture file storage directory or the voice file storage directory in accordance with the operation of thecursor button17.
• Returning toFIG. 101, instep502, if a user operation for selecting a directory to be stored is performed, the procedure goes to step S503. Instep503, the HD MW82 requests the MS MW89 to read all files belonging to the directory to be stored and records them as one archive file into the layer below the MS store/restoreobject502 of theobject recording area122 of theHDD58. In step S504, the HD MW82 records the original directory (for example, directory DCIM) and the archive file name (for example, “2001/08/11”) to the recorded archive file by relating the original directory and the archive file name.
• It should be noted that the archive file name may be set by the user in an arbitrary manner; however, if no file name is set, the date of the store process concerned is automatically set as the archive file name such as “2001/08/11”.
• FIG. 104 shows a display example in thedisplay15 when an archive file being generated. Adisplay area531 shows the information that the still picture file storage directory of theMS4 is stored in theHDD58. Adisplay area532 shows the file name (in this example, “2001/08/11”) of the generated archive file. Adisplay area533 shows a variable-length bar534 which extends in proportion to the progress of the store processing concerned. Adisplay area535 blinks a character string “Store” indicative that a store process is being executed.
• Returning toFIG. 101, instep505, the HD MW82 requests the MS MW89 to delete, from theMS4, the directory in theMS4 with the archive file generated in theHDD58. Thus, the store process is performed.
• It should be noted that the retrieved directory which can be stored may be automatically selected for executing the subsequent processes rather than waiting for the user operation for selecting the directory to be stored as the process instep502.
• As described, a store process allows the searching of the directories and files recorded to theMS4 for directories which can be stored. A store process also allows the selecting and storing of a directory in which the files generated by particular electronic equipment are stored. In addition, a store process prevents any ill-intentioned user who tries to copy the content data stored in the HIFI file in an unauthorized manner from using this store function because the HIFI directory in which files having copyright information in theMS4 are stored is not processed by this store function.
• The following describes a restore process for restoring, on theMS4, a directory equivalent to an archive file stored in theHDD58 with reference to the flowchart shown inFIG. 105.
• This restore process starts when the user selects theHDD58 as sound source by repetitively pressing thefunction button12, selects “Edit” by operating thecursor button17 after pressing the menu/cancelbutton21, presses theenter button20, selects “Restore (MS→HDD”) by operating thecursor button17, and then pressing theenter button20.
• Instep501, the HD MW82 displays, on thedisplay15, the list of archive files belonging to the layer below the MS store/restoreobject502 of theobject recording area122 of theHDD58.
• FIG. 106 shows a display example on thedisplay15 for displaying the list of archive files. Adisplay area541 shows a character string “HDD” indicative of sound source. Adisplay area542 shows a character string “Restore List”. Adisplay area543 shows the information about the archive files which can be restored (file type marker, file name, and data capacity). Acursor544 points the still picture file storage directory or the voice file storage directory in accordance with the operation of thecursor button17.
• Returning toFIG. 105, in step S512, the HD MW82 accepts a user operation for selecting an archive file to be restored in step S502 and waits until the user performs the select operation. To be more specific, the HD MW82 waits until the user selects an archive file by moving thecursor544 up or down by operating thecursor button17 and presses theenter button20 to establish this selection. When the user performs these operations, the procedure goes to step S513.
• FIG. 107 shows a display example on thedisplay15 when the original directory and its files are being restored on the basis of the archive file. Adisplay area551 shows information “Restore (HDD MS)” indicative that the still picture file storage directory is restored from theHDD58 to theMS4. Adisplay area552 shows the file name (in this example, “2000/08/11”) of the restored archive file. Adisplay area553 shows a variable-length bar554 which extends in proportion to the progress of the restore process concerned. Adisplay area555 blinks a character string “Restore” indicative that the restore process is being executed.
• Returning toFIG. 105, instep513, the HD MW82 requests the MS MW89 to restore the original directory and all its files into theMS4 on the basis of the archive file selected to be restored. In step S514, the HD MW82 deletes the selected archive file from the layer below the MS store/restoreobject502 in theobject recording area122 of theHDD58. Thus, the restore process is performed.
• It should be noted that the subsequent processes may executed by automatically selecting the archive file to be restored rather than waiting for the user to select the archive file to be restored as the process instep512.
• FIG. 108 shows an exemplary configuration of theflash ROM52. Theflash ROM52 stores a boot program which will be described later.
• Theflash ROM52 has three storage areas, first through third storage areas, in which the firmware shown inFIG. 7 is stored on a so-called version basis. Namely, in this example, firmware of three generations of versions may be stored.
• Amarker1 indicative of the version of the firmware to be stored in the first storage area, amarker2 indicative of the version of the firmware to be stored in the second storage area, and amarker3 indicative of the version of the firmware to be stored in the third storage area are included in the boot program.
• It should be noted that, although details will be described later, each marker is incremented by 1 every time the firmware is upgraded in version. If no firmware is stored in the corresponding area, each maker has a value indicative of “INVALID”.
• The following describes a processing procedure for upgrading firmware in version (rewriting a program) with reference to the flowchart shown inFIG. 109.
• It should be noted that, this firmware version upgrading process is executed by the firmware specified by the boot program which will be described later when the user performs a predetermined operation on theaudio server1. For example, if the firmware to be upgraded in version and the firmware of a later version are stored in a CD-ROM, the CD MW88 executes this process; if these firmware programs are stored in theMS4, the MS MW89 executes this process. In this example, this version upgrading process is executed by the CD MW88.
• In step S531, the CD MW88 determines an area in which the upgraded firmware is stored.
• To be more specific, one “INVALID” marker of themarker2 and on of the flash ROM52 (themarker2 and themarker3 in the example ofFIG. 108) is detected and the storage area pointed by this marker provides the area for storing the upgraded firmware. If no “INVALID” marker exists in themarker2 and on, the minimum marker is detected and the area pointed by this marker provides the area for storing the upgraded firmware.
• In this example, the storage area pointed by the minimum marker stores the firmware of the least recent version.
• In step S532, the CD MW88 gets the firmware of the most recent version from the CD-ROM loaded in the CD-ROM drive57. It should be noted that, in addition to the CD-ROM, the firmware of the most recent version may also be obtained from theMS4 or the electronic equipment which performs data communication via the Ethernet controller/connector67.
• In step S533, the CD MW88 supplies the firmware obtained in step S532 to the encoder/decoder59 for decryption and, in this example, re-encryption by use of the encryption key stored in theflash ROM52 is performed.
• In step S534, the CD MW88 writes the firmware re-encrypted in step S533 to the storage area determined in step S531.
• In step S535, the maximum marker is detected from themarker2 and on (except for “INVALID” marker). In step S536, the value obtained by adding 1 to the maximum marker provides the marker corresponding to the storage area in which the firmware was stored in step S534. Then, this upgrading process comes to an end.
• As described, only by performing a predetermined operation by the user on theaudio server1, the version of firmware may be upgraded.
• The following describes a processing procedure in the boot program with reference to the flowchart shown inFIG. 110. It should be noted that this boot program is executed immediately after the power is supplied from thepower supply section65 to each component of the system (upon execution of a power-on sequence).
• In step S541, the boot program executes a predetermined initializing process such as register initialization for example.
• In step S542, the boot program determines whether or not all of themarker2 and on (themarker2 and the marker3) in theflash ROM52 are “INVALID”. If all these markers are not “INVALID”, the procedure goes to step S543.
• In step S543, the maximum marker m which is not “INVALID” is detected from themarker2 and on. In step S544, the boot program supplies the firmware stored in the storage area pointed by the marker m to the encoder/decoder59 for decryption. In step S545, the boot program writes the decrypted firmware to theSDRAM53.
• If themarker2 and on are all found “INVALID” in step S542, then the procedure goes to step S547, in which the boot program determines whether or not themarker1 is “INVALID”. If themarker1 is found not “INVALID”, the procedure goes to step S548.
• In step S548, the boot program supplies the firmware in the storage area pointed by themarker1 to the encoder/decoder59 for decryption. In step S549, the boot program writes the decrypted firmware to theSDRAM53.
• When the firmware is written to theSDRAM53 in step S545 or S549, the procedure goes to step S546, in which the boot program instructs the execution of the firmware written to theSDRAM53. Consequently, the firmware developed in theSDRAM53 is executed.
• If themarker1 is found “INVALID” in step S547, namely, if none of the storage areas stores the firmware and all markers are “INVALID”, then the procedure goes to step S550, in which error is determined.
• If the firmware is executed in step S546 or if an error is determined in step S550, then the process comes to an end.
• It should be noted that, in the above-mentioned example, only three storage areas for storing firmware are arranged in theflash ROM52; the number of storage areas for storing the firmware is not limited to three as long as it is more than one. If there are two storage areas, the marker of the storage area in which the firmware is stored may be set to “INVALID” and, after storing the firmware in that storage area, set to “VALID” (to be correct, a value not INVALID). This prevents the firmware under rewriting from being developed into theSDRAM53 for execution.
• In the above-mentioned example, the firmware is upgraded in version. It will be apparent that the present invention is also applicable to a configuration in which other programs are upgraded in version. The present invention is also applicable to a configuration in which program forms are changed (for example, programs for the Japanese language and the English language).
• The above-mentioned sequences of processes may be executed not only by dedicated equipment such as theaudio server1 but also by installing the firmware as shown inFIG. 7 on a general-purpose personal computer for example and executing the installed firmware.
• This firmware is constituted not only by package media storing firmware such as the magnetic disk (including a floppy disk), the optical disk (including CD-ROM (Compact Disk-Read Only Memory) and a DVD (Digital Versatile Disk)), and the magneto-optical disk (including MD (Mini Disc), and the semiconductor memory which are distributed to users to provide programs independently of the general-purpose computer, but also by a ROM and a hard disk storing firmware to be provided to users as installed in the computer.
• It should be noted that, in the present specification, the steps for describing the program (firmware) include not only the processing operations to be executed sequentially in time but also the processing operations to be executed in parallel or discretely.
INDUSTRIAL APPLICABILITY
• As described above, according to the present invention, it is possible to automatically perform a processing to temporarily exchange data in a predetermined format.

Claims (17)

1. An information processing apparatus comprising:

a first information storage medium for storing programs loaded into and being executable from the first information storage medium;

a second information storage medium for storing

a set of programs comprising

a control program for controlling the information processing apparatus,

a load program for loading at least a part of said set of programs into said first information storage medium,

an execution instruction program for instructing execution of at least a part of said set of programs loaded into the first information storage medium,

a read program for reading data from an external information source and

a write program for writing data into said second information storage medium, and

a version information of at least a part of said set of programs; and

a controller for

loading at least a part of said set of programs into said second information storage medium by means of said load program when the information processing apparatus is turned on,

executing said loaded part of said set of programs by means of said execution program,

reading an upgrade version of a program from said external information source by means of said read program in accordance with said version information and a user request during the execution of at least one of said set of programs, and

writing said read program into said second information storage medium by means of said writing program.

2. An information processing apparatus ofclaim 1, wherein

said set of programs comprising real time operating system of the information processing apparatus.

3. An information processing apparatus ofclaim 1, wherein

said set of programs being configured with four layers structure.

4. An information processing apparatus ofclaim 1, wherein

said set of programs being configured with multiple layers structure, one of the layers including an application, other one of the layers including a middleware and other one of the layers including a plurality of device drivers.

5. An information processing apparatus ofclaim 1, further comprising a display,

wherein said set of programs being configured with multiple layers structure, one of the layers including an application, other one of the layers including a middleware and other one of the layers including a plurality of device drivers,

wherein a module of said application being capable of requesting corresponding module of said middleware in accordance with user operation on the information processing apparatus and providing user interface by controlling said display.

6. An information processing apparatus ofclaim 1, wherein

said set of programs being configured with multiple layers structure, one of the layers including an application, other one of the layers including a middleware and other one of the layers including a plurality of device drivers,

wherein said application capable of creating a startup screen at the time of start up of the information processing apparatus.

7. An information processing apparatus ofclaim 1 further comprising a DMA (Direct memory Access) controller.

8. An information processing apparatus ofclaim 1 further comprising an encryption engine for encrypting data by use of an encryption key.

9. An information processing apparatus ofclaim 8, wherein the encryption engine capable to handle a DES (Data Encryption Standard) encryption.

10. An information processing apparatus ofclaim 8, wherein the encryption engine encrypting data by use of an encryption key generated based on a device ID of a predetermined component of the information processing apparatus.

11. An information processing apparatus ofclaim 8, wherein the encryption engine encrypting data by use of an encryption key generated based on a time information.

12. An information processing apparatus ofclaim 1 further comprising a connector for performing data communication with other electronic equipment.

13. An information processing apparatus ofclaim 1, wherein

said set of programs comprising a character conversion program.

14. An information processing apparatus ofclaim 13, wherein

said character conversion program is a kanji-kana conversion program.

15. An information processing apparatus ofclaim 1, wherein

said set of programs comprising a USB (Universal Serial Buss) middleware.

16. An information processing apparatus ofclaim 1, wherein

said set of programs comprising a USB (Universal Serial Buss) driver.

17. An information processing apparatus ofclaim 1, wherein

said set of programs comprising an audio driver.

Images