JP2001229114A - Information processing device and method, and program storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To use plural devices of the same kind which are connected through a network as a virtual multiple-drive device. SOLUTION: A multiAVDISCFCM sends commands through the processing of an application program of an IRD 1 to read out information recorded on tracks of MD drives and generate an inner table. The MultiAVDISCFCM sends commands for reading out information recorded on the MD drives 2 and 3 recorded in the inner table, reading out a track recorded in the inner table, and reproducing the specific track. An AVDISCFCM outputs an AV/C command for reproducing a specific track of an MD drive specified with a DCM to the MD drive. The MD drive reproduces the specific track according to the AV/C command.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus and method, and a program storage medium, and more particularly, to controlling a plurality of information devices connected via a network.
The present invention relates to an information processing apparatus and method, and a program storage medium, in which a plurality of information devices can be used as one virtual multiple-connected information device by managing information recorded in each information device. .

[0002]

2. Description of the Related Art A technique using a home network system configured by using an IEEE1394 serial bus is becoming popular. In a home network system configured using the IEEE1394 serial bus, one information processing device (for example, an IRD (Integrated Receiver D
ecoder)) to multiple information devices of the same type (for example, MD (Mini
Disc) drive, the information processing apparatus can control a plurality of information devices and record or reproduce information.

[0003]

However, even if each of the information devices of the same type can be individually controlled,
There has been a problem that a plurality of information devices cannot be controlled like one virtual multiple-mounted information device.

The present invention has been made in view of such a situation, and enables a plurality of information devices of the same type to be used as one virtual multiple-connected information device, thereby facilitating operation and information management. It is to be.

[0005]

According to the present invention, there is provided an information processing apparatus comprising: a recording medium information acquiring unit for acquiring information on a recording medium mounted on a plurality of information devices connected via a network; Storage management means for centrally storing and managing the information of the recording medium obtained by the means,
A control unit for controlling a plurality of information devices based on the information of the recording medium stored by the storage management unit.

[0006] The information processing apparatus may further include control information acquisition means for acquiring control information for controlling each of the information devices from the plurality of information devices via a network. , A plurality of information devices can be controlled based on the control information acquired.

[0007] The recording medium can be made to be able to reproduce only or to be able to record and reproduce.

[0008] The network may be constituted by an IEEE1394 serial bus.

[0009] The information processing apparatus may further include display means for displaying the information on the recording medium stored by the storage management means, and selection means for selecting the information on the recording medium displayed by the display means. , The control means include:
The information device can be controlled in accordance with the content selected by the selection unit out of the information of the recording medium displayed by the display unit.

When the information device is turned on, when the information device is plugged in, when a recording medium is mounted on the information device, or when a content is recorded on the recording medium, May store the information of the recording medium acquired by the recording medium information acquiring means.

When the power of the information device is turned off, when the information device is unplugged, when the recording medium is detached from the information device, or when the content is erased from the recording medium, the storage management means includes: In addition, the information of the recording medium stored by the user can be deleted.

[0012] The information of the recording medium is management information of recording contents of the recording medium, and may include a device ID, a track number, a track name, a recording time, an HAVi media format, or an MIC.

[0013] Model information acquiring means for acquiring model information of a plurality of information devices connected via the network may be further provided.

The type of the information device can be identified by the type of FCM.

[0015] The plurality of information devices may include the same type of information devices.

An information processing apparatus according to the present invention is obtained by a recording medium information obtaining step of obtaining information of a recording medium mounted on a plurality of information devices connected via a network, and a recording medium information obtaining step. And a control step of controlling a plurality of information devices based on the information of the recording medium stored in the processing of the storage management step. Features.

The recording medium program according to the present invention includes a recording medium information acquisition control step for controlling acquisition of information on a recording medium mounted on a plurality of information devices connected via a network, and a recording medium information acquisition control step. Centralized storage of the information of the recording medium obtained in the processing of the above, a storage management control step of controlling the management, and controlling the plurality of information devices based on the information of the recording medium stored in the processing of the storage management control step And a controlling step.

According to the information processing apparatus and method and the recording medium of the present invention, information of a recording medium attached to a plurality of information devices connected via a network is acquired, and the acquired information of the recording medium is acquired. Focused and remembered,
A plurality of information devices are controlled based on the managed and stored information of the recording medium.

[0019]

FIG. 1 is a block diagram showing the configuration of a network system when a plurality of information devices are connected to an information processing apparatus.

Upon receiving a broadcast signal from a satellite (not shown) via an antenna (not shown), the IRD 1 demodulates an image,
An image is displayed on the monitor 11. The IRD 1 extracts an audio signal from the received broadcast signal, outputs the audio signal to the MD drives 2 and 3 via the IEEE1394 serial bus 4, and
Drives 2 and 3 are controlled.

The MD drive 2 can mount two MDs, and the MD drive 3 can mount one MD. When the MD drives 2 and 3 are connected to the IEEE 1394 serial bus 4, the MD (Device Control) of each device is transmitted to the IRD 1 via the IEEE 1394 serial bus 4.
ol Module) and FCM (Functional Component Module) (details of DCM and FCM will be described later).

The IRD 1 detects device control information of devices connected to the IEEE1394 serial bus 4 from DCMs and FCMs sent from the MD drives 2 and 3, and controls a GUI (Graphical) for controlling those devices. User Interf
ace) is displayed on the monitor 11.

FIG. 2 is a block diagram showing a detailed configuration of the IRD 1. The input / output interface 21 is a CRT 31
And is connected to the internal bus 25.

The tuner 22 outputs the demodulated broadcast signal to the monitor 11 via the internal bus 25, the IEEE 1394 I / F (interface) 29, and the IEEE 1394 serial bus 4.

The touch panel 23 is provided on the surface of the IRD 1 main body.
When the touch panel 23 is operated on the basis of the display, the CPU 26 generates a control signal based on the
Various instructions are issued to the MD drives 2 and 3 via the serial bus 4. In addition, the above-described instruction content is transmitted to the CRT 31 via the input / output interface 21 in accordance with the instruction content.
Will be displayed. Based on this, MD drives 2 and 3
According to the input control signal, the IEEE1394 serial bus 4
Sending or receiving data via
Execute processing such as recording.

The HDD 24 stores application programs to be executed by the CPU 26, middleware, and the like.

The internal bus 25 includes an input / output interface 21, a tuner 22, an HDD 24, a CPU 26, a RAM 27, a ROM
28 and the IEEE1394 interface 29,
It enables mutual transmission and reception of data.

The CPU 26 controls the overall operation of the IRD 1, and executes various application programs as needed. In the RAM 27, various application programs executed by the CPU 26 and the IE
The latest information on the processing executed by the device connected to the EE1394 serial bus 4 is written. The ROM 28 stores a program for loading and activating an OS (Operation System) required for the processing of the CPU 26. The IEEE1394 interface 29 functions as an interface with the IEEE1394 serial bus 4 and
94 Data transfer with the serial bus 4 is executed.

A semiconductor memory 41, a magneto-optical disk 42, an optical disk 43, a magnetic disk 44, and the like can be mounted on the drive 30.

FIG. 3 is a block diagram showing the internal configuration of the MD drive 2. The signal transmitted from IRD1 is IEEE1
394 is input to the CPU 55 via the serial bus 4, the IEEE1394 interface 58 and the internal bus 54. When the user operates the touch panel 52 while viewing the display content displayed on the LCD (Liquid Crystal Display) 51, a signal corresponding to the user's operation is sent to the CPU 55 via the input / output interface 59 and the internal bus 54. Based on the input, the CPU 55
3 is controlled.

The recording / reproducing unit 53 sends the inserted MDs 61 and 62 to the inserted MDs 61 and 62 according to the control signal input from the CPU 55.
The data input through the 1394 interface 58 and the IEEE1394 serial bus 4 is recorded, the recorded data is read, and connected to the network via the internal bus 54, the IEEE1394 interface 58 and the IEEE1394 serial bus 4. To an amplifier (not shown). Further, the recording / reproducing unit 53 outputs the read data such as a track name, which will be described later, to the LCD 51 via the internal bus 54 and the input / output interface 59 for display.

The CPU 55 reads the ROM 5 according to the input signal.
7 is read out, expanded in the RAM 56 and executed, and the recording / reproducing unit 5 is read via the internal bus 54.
3 and outputs its own DCM and FCM stored in the ROM 57 to the internal bus 54 and the IEEE 13
94 to the IRD 1 via the interface 58 and the IEEE1394 serial bus 4. The RAM 56 temporarily stores data generated by the execution of the program by the CPU 55 and other data necessary for the MD drive 2 to execute processing.

The MD drive 3 has the same configuration as the MD drive 2 shown in FIG. 3 except that the number of MDs that can be mounted is two, whereas the MD drive 2 shown in FIG. The description is omitted.

In order for devices on a network as shown in FIG. 1 to operate in cooperation, middleware for controlling and managing the network (lower software such as an OS, a network control program or a database system, Software that is located between applications and provides various services to the applications). Furthermore, even when devices of different manufacturers are connected to the network, a common specification that the middleware must conform to is essential for the network to operate normally and for the devices to interoperate. Here, HAVi ™ (Home A) is used as middleware for network control and management.
A network system to which the udio / Video Interoperability Architecture is applied will be described.

FIG. 4 shows the hard disk drive 2 of FIG.
4 shows an example of software stored. 13
94 Except for the driver and application programs, the software modules corresponding to HAVi are included.

The 1394 driver is an IEEE1394 serial bus 4
This is a module that describes a part that depends on, and is a software for providing higher-level software with a sharing procedure for device access.

The CMM (Communication Media Manager)
The interface serves as an interface between the IEEE1394 serial bus 4 and each HAVi software module and application. The CMM provides a transmission mechanism for transmitting and receiving signals between devices connected to the IEEE1394 serial bus 4,
The operation status of the software module and provide the information to other software modules.

The messaging system has an API (Application Programming) for communicating software modules of each device on the network.
Interface), and serves to transmit messages between software modules. For this reason, in a network employing HAVi, a messaging system assigns a SEID (Software Element Identifier: software element identification value) to a software element in the same device, and the transmitting side and receiving side of the message communicate with each other. Messages can be transmitted without knowing the location on the network.

The DCM (Device Control Module) manager includes the DCM and F corresponding to each device on the network.
It installs a CM (Functional Component Module). In networks employing HAVi,
When a new device is connected to the network, the DCM manager starts the DCM corresponding to the newly connected device.
If the device is removed from the network after installing the FCM and FCM, DCM corresponding to the removed device
And uninstall FCM.

The application program is software for executing various processes. In this example, in particular, control contents (functions) input through a GUI for controlling a virtual multiple device are described in MultiA (described later).
This is software that makes VDISCFCM recognize and output commands and executes them.

The DCM controls the devices, and the application program does not directly control each device connected to the network, but controls the devices via the DCM. The FCM indicates the content (function) of control performed by the application program on each device, and transmits an AV / C (Audio Video / Control) command to the device specified by the DCM. D
Since CM and FCM function as APIs, application programs themselves do not need to consider differences between individual devices. Therefore, in a network adopting HAVi, a device on the network can recognize the function of another device, and can operate the other device from a remote place.

The MultiAVDISCFCM is located between AVDISCFCM1 to AVDISCFCM3 and the application program.
An FCM that manages M1 to M3 in an integrated manner. That is, Mu
The ltiAVDISCFCM integrally controls and manages AVDISCFCMs 1 to 3 based on commands as shown in Table 1 below. For this reason, the application program
Through the ltiAVDISCFCM, devices connected to the network (here, the MD drives 2 and 3) can be handled as a single virtual multiple device.

<Table 1> init Initialization setting getTable Acquires the inner table setTable Sets the inner table getTrack Acquires to display the currently selectable track information setTrack setTrack Sets the track with the specified track number getDisc Gets the currently selectable Disc information. SetDisc The specified DISC number is set. SortTable Sorts the inner table (as an argument, column header [0, 1, 2], random or not (boolean)) regidterAVDISC network Add the above MD to the group of multiple devices (Argument: SEID) unregisterAVDISC Remove the MD on the network from the group of multiple devices (Argument: SEID) Play Play current disk and track Stop Stop playback of virtual multiple MD Pause Pause playback of virtual multiple MD. RandomPlay Random play of virtual multiple MD. Setrepeat Pete mode on / off setting ForwardTrack Track forward of virtual multiple MD PreviousTrack Track reverse of virtual multiple MD Forward Forward fast forward reproduction of virtual multiple MD Reverse Reverse fast reverse playback of virtual multiple MD

Of these, "init", "gettable" and "settable" will be described in more detail.
"Init" is a MultiAVD
This is a command to the ISCFCM or AVDISCFCM, and the FCM executes a predetermined initialization process by this command.

"Gettable" is a command from the application program to MultiAVDISCFCM or AVDISCFCM.
Returns the acquired information of the inner table to the application program, and the application generates a display screen based on this information.

Further, "settable" indicates that MultiAVDISCFCM or AVDISCFCM
Command to the FCM
Means that if the compatible device has a storage medium,
An inner table is generated based on the content management information of the recording medium.

Therefore, when displaying the inner table, "gettable" is executed after "settable".

The inner table, as shown in FIG.
ltiAVDISCFCM reads tracks of each MD from AVDISCFCM1 to 3 (TOC: Read Table of Contents),
It is a list to be generated. In this example, the number, track name, DISC, device ID, time (recording time), and attribute of each track are recorded from the left. The display of each disk includes DISC1 to DISC3. As the device ID, "MDS-DL1-1" is displayed for DISC1, and "MDS-DL1-1" is displayed for DISC2.
-DL1-2 "and DISC3 indicate" MDS-DLL ".
This is because the MD drive 2 is a two-unit MD drive, and for example, “MDS-DL1-1” of DISC1 is MD6
1 and “MDS-DL1-2” of DISC2 indicate MD62.

For example, the track number 1 is "AAA" as the track name, the DISC name is "DISC1", and the device ID is
Is recorded as “MDS-DL1-1”, recording time of 4 minutes and 30 seconds, and “ST” (meaning stereo recording) as an attribute. For example, track number 8 has track name "KOUGI2", disc name "DISC2", device ID "MDS-DL1-2", recording time 43 minutes and 30 seconds, and attribute "MONO" ( (Meaning monaural recording).

Further, although not shown, the inner table also includes information for identifying the type of the recording medium called the HAVi media format. In this case, the identification information indicating the MD is recorded as the recording medium. become. In addition, MIC (Memory in Cassett)
It is also possible to record information indicating the content of the recorded content, which is called e).

The event manager plays a role of generating an event and transmitting it to another software module when the state of the network changes, for example, when a new device is connected to or disconnected from the network. This makes it possible to realize plug-and-play in a network employing HAVi.

The registry holds and updates information about devices, such as what devices are connected on the network and what functions the devices have, and enables interaction between different devices. It is to be. The application program obtains necessary information (SEID and attribute information) from this registry. Each device on the network can confirm the location of the basic software module of another device on the network by referring to the registry.

The stream manager monitors the flow of stream data (continuous data) on the network.
It manages and enables real-time transmission of stream data. The stream manager manages the connection of streams inside and between devices, secures and releases network resources, and provides connection information for the entire network. In addition, the stream manager may support reconnection after a network reset.

The resource manager manages a device use right collision problem, manages scheduled events such as a process reserved for a connected device, and checks whether a device is removed after registration. , Monitor the network.

The DCMs 1 and 2 are DCMs corresponding to the respective devices installed from the MD drives 2 and 3, respectively. AVDISCFCM1 and AVDISCFCM2
Is the FC corresponding to each device installed from the MD drive 2 and AVDISCFCM3 is the FC
M.

Further, such a software module is owned by each device connected to the network according to the device class defined in HAVi.
HAVi defines four classes of devices.

FAV (Full AV Device) is a device having a function of managing a network,
(In some cases, DCM and FCM are not possessed, but can be installed from, for example, a BAV described later). FAV
Is Java (trademark) adopted as HAVi bytecode
It is possible to execute an application using. In this way, FAV can be used for DCM and FCM of other devices.
, And owning the DCM and FCM of the other device allows the other device to be under control.

An IAV (Intermediate AV Device) is a device having a function of managing a network similarly to an FAV, but unlike an FAV, an application using Java (trademark) adopted as HAVi bytecode is executed. It is an environment that cannot be done. Therefore, in order to control another device, it is necessary to incorporate DCM and FCM corresponding to the device in advance.

The BAV (Base AV Device) corresponds to a controlled device that can be directly connected to the HAVi network, and has its own DCM and FCM. LAV (Legacy AV Device) has only a function as a device connectable to the IEEE1394 serial bus 4. In order to respond to AV / C commands, it can operate as a controlled device in addition to operating alone.

Here, IRD1 is FAV, MD drives 2 and 3
Is described as a device corresponding to BAV. As shown in FIG. 4, the FAV IRD 1 is the BAV MD drive 2,
By installing the DCM 3 and the FCM 3, the MD drives 2 and 3 can be controlled. This allows HA
IRD1, the device that manages the Vi network,
For example, the stream manager can generate a connection with the MD drives 2 and 3 that are controlled devices, and allow stream data to flow.

Next, referring to FIGS. 6 to 9, the CR of FIG.
GUI (Graphical User) of IRD1 displayed on T31
Interface) will be described. The GUI operates on an application program, and a command generated by operating the GUI is output to the MultiAVDISCFCM. The MultiAVDISCFCM sends commands to the AVDISCFCMs 1 to 3 based on the commands in Table 1 described above, and
And 3 send AV / C to MD drives 2 and 3 based on this command.
Output a command.

The disk to be selected is displayed in the disk display column 71 of FIG. 6. Move the cursor to the button 71a and click it to drop down the list 71b.
Is displayed, and a list of currently selectable disks via the network recorded in the inner table of FIG. 5 is displayed. When a desired disk is selected and clicked from this list, the drop-down list 71b disappears, and the selected disk is displayed in the disk display column 71. In this example, drop-down list 71
“DISC1: MDS-DL1-1” is selected from b (displayed in white).

A track display section 72 is provided below the disk display section 71. The disk (MD) in the disk display section 71 is provided.
The currently selected track is displayed, and the track name and the recording time are displayed. When the button 72a is clicked, a drop-down list 72b is displayed as shown in FIG. The drop-down list 72b represents the contents of all the tracks recorded on the disc in the disc display column 71. When a desired track is selected and clicked from the drop-down list 72b, it is displayed in the track display column 72. The drop-down list 72b disappears at the same time as the selection is made. In this example, [03] CCC12: 05 is selected (displayed in white).

The Play button 73 at the upper right moves the cursor to that position and clicks it to open the disc display field 7.
The track displayed in the track display field 72 of the disc displayed in 1 is reproduced. Below the Play button 73, from the left, a Rev (Reverse) button 74 and a Forwd (For
ward) button 75, Pause button 76, Stop button 7
7, and further below, a Prev (Previous) Track button 78, a Forwd Track button 79, and an Eject button 80
Is displayed. When the Rev button 74 is clicked, the currently playing track is played back in reverse while the button is clicked. When the Forwd button 75 is clicked, the currently reproduced track is fast-forward reproduced while the button is clicked. When the Pause button 76 is clicked, the reproduction is paused. When the Play button 73 is clicked again, the reproduction is started from the paused position. When the Stop button 77 is clicked, the reproduction is stopped. When the Prev Track button 78 is clicked, it moves to the previous track of the current track,
Playback starts. The Forwd Track button 79, on the contrary,
Move to the next track and playback is started. Ejec
The t button 80 is operated when instructing removal of the disk displayed in the disk display field 71.

When the Random button 81 is clicked once, the display turns black, random reproduction is turned on, and when it is clicked again, it turns white and random reproduction is turned off. When the random reproduction is turned on, the reproduction order of each track of the specified disc is rearranged at random and reproduced. In the example of FIG. 6, since the Random button 81 is white, it indicates that the random playback is off.

When the Repeat button 82 is clicked once, the display turns black, repeat playback is turned on, and when the button is clicked again, it turns white and the repeat playback is off. In the repeat reproduction, the track specified in the track display field 72 is repeatedly reproduced. In this example,
Since the Repeat button 82 is black, it indicates that the repeat playback is on.

Add registration button 83 displayed as “Add”
When clicked, acquires all media information that can be acquired by the same type of FCM and creates an inner table. Then, the screen display changes from the GUI of FIG. 7 to the GUI of FIG. 8, and a desired disk is selected (clicked) from the registrable disk display column 83a and registered by clicking a registration button 83b. When the end button 83c is clicked, the disc is updated to the registered disc and
The GUI will be displayed.

A registration deletion button 8 displaying “Remove”
When the button 4 is clicked, the screen display changes from the GUI of FIG. 7 to the GUI of FIG. 9, a desired disk is selected (clicked) from the disk display column 84a for deletion, and a delete button 84b is selected.
Click to delete. Then, the end button 84
When c is clicked, the deleted disk is updated and the GUI shown in FIG. 7 is displayed.

In the above description, the GUI in the multiple connection mode (a mode in which a plurality of devices of the same type connected via a network function as one device) has been described. If only 3 are connected via the network, the same type of disk is not connected to a plurality of disks.
1, no button 71a is displayed and no drop-down list 71b appears.

Next, the network management processing executed by the IRD 1 will be described with reference to the flowchart of FIG. This processing flow is performed when a device is connected to the network (plug-in), disconnected (unplugged), or when a bus reset occurs due to turning on or off the main power of the connected device. Always executed. Although not described below, each software module described with reference to FIG. 4 is read from the hard disk drive 24 by the CPU 26 and executed.

In step S1, the CMM determines whether or not a new device has been inserted into the network (whether or not a new device has been connected). DCM
Notify the manager to that effect.

In step S2, the DCM manager installs DCM and FCM from the inserted new device, and proceeds to the processing in step S3. In this example, since the MD drives 2 and 3 are newly inserted, the DCMs 1 and 2 and the AVDISCFCMs 1 to 3 are installed from the MD drives 2 and 3.

In step S3, the event manager notifies each software module that a new device has been connected, based on a message from the CMM, and the registry determines, based on this notification, that the new device has been connected. Register information. In this example, the event manager notifies that the MD drives 2 and 3 have been newly added, and the registry determines that the MD drives 2 and 3 have been added.
3 will be registered.

In step S4, the event manager determines whether there is still a new device in the network. If it is determined that there is no new device, the process proceeds to step S5.

At step S5, the CMM and the resource manager determine whether a new device has been disconnected from the network (whether there is any device that has been removed).

In step S5, when it is determined that a new device has been disconnected from the network, for example, when the MD drive 2 has been disconnected, the CMM notifies the event manager to that effect.
This is notified to each software module. In step S6, the DCM manager, based on this notification, DCM 1 and AV
Uninstall DISCFCM1 and 2.

In step S7, the registry stores the MD
Erase the information in drive 2. In step S8,
The event manager determines whether or not there is any device that has been further disconnected from the network, and if it determines that there is no device that has been disconnected, the process ends.

If it is determined in step S1 that a new device has not been inserted, the processing in steps S2 to S4 is skipped, and the processing proceeds to step S5.
Proceed to. If it is determined in step S4 that there is still a new device, the process returns to step S2.

If it is determined in step S5 that a new device has not been disconnected from the network,
The processing of steps S6 and S7 is skipped, and the processing ends. If it is determined in step S8 that the removed device exists, the process returns to step S6, and the subsequent processes are repeated.

Note that FC in steps S2 and S3 described above is used.
The process of installing M and DCM and registering them in the registry is performed, not only when a new device is inserted, but also when, for example, the MD drives 2 and 3 are powered on or plugged in. You may do it. Further, the process of uninstalling the FCM and the DCM in steps S6 and S7 and deleting the FCM and the DCM from the registry may be performed, for example, in addition to the case where the attached device is removed.
It may be executed when the power of the MD drives 2 and 3 is turned off or when the MD drives are unplugged.

Next, the operation when the IRD 1 generates the inner table will be described with reference to the flowchart of FIG.

At step S11, the application program reads device information recorded in the registry.

In step S12, based on the read registry information, it is determined whether or not a device having the AVDISCFCM function exists. That is, the application program identifies the device type by comparing the FCM type corresponding to each device, and
It is determined whether there is a device having the DISCFCM function. In this example, the MD drives 2 and 3 are AVDISC
Since the device has the FCM function, it is determined that the device exists, and the process proceeds to step S13.

In step S13, the application program determines whether there are a plurality of detected devices. In this example, MD drives 2 and 3
It is determined that there are a plurality of devices having the AVDISCFCM function, and the process proceeds to step S14.

In step S14, the application program displays a selection screen as shown in FIG.

In step S15, the application program determines whether MultiMD in FIG. 14 has been selected. For example, when MultiMD is selected and clicked, the application program executes the command setTab
le is output to MultiAVDISCFCM, and the flow advances to step S16.

In step S 16, the application program executes each application under the control of MultiAVDISCFCM.
Get SEID of AVDISCFCM. In step S17, the MultiAVDISCFCM outputs an instruction to each AVDISCFCM to acquire media information based on the settable command from the application program, and acquires the information (when a medium is mounted).

In step S18, the obtained media information is stored in a memory under the control of each AVDISCFCM, and an inner table is generated. That is, in step S18, the MultiAVDISCFCM issues an AVDISC :: GetFormat command (HAVi standard command) to the AVDISCFCM1 to 3 in order to read the media information recorded on the disk of the detected device. AVDISCFCM1 to 3
Outputs to the MD drives 2 and 3 an AV / C command instructing reading of the media information of each disk of the MD drives 2 and 3 based on the AVDISC :: GetFormat command. each
The MD drives 2 and 3 read the respective media information from the respective MDs in response to the AV / C command and output the respective media information to the respective AVDISCFCMs 1 to 3. Upon receiving the media information read from the MD drives 2 and 3, each of the AVDISCFCMs 1 to 3
Send to CM. Then, the MultiAVDISCFCM generates an inner table based on the read media information.

As a result, in step S19, the application program stores the AVDIS
When the C :: GetFormat command is output, MultiAVDISCFCM
Reads the information in the inner table and returns it to the application program. Then, the application program causes the monitor 11 to display a GUI as shown in FIG. 6 based on the received information of the inner table.

If it is determined in step S12 that there is no device having the AVDISCFCM function, in step S19, the application program
The display "NOAVDISC" is displayed in the disk display column 71 of FIG. 6, and after a certain period of time, the processing is terminated.

If it is determined in step S13 that there are not a plurality of devices having AVDISCFCM, in step S20 (FIG. 12), the application program obtains the SEID of only one AVDISCFCM. In step S21, the AVDISCFCM acquires media information based on the settable command from the application program (provided that the media is mounted). In step S22, the obtained media information is stored in the memory under the control of AVDISCFCM, and an inner table is generated. The process proceeds to step S19.

If it is determined in step S15 that MultiMD is not selected, step S23 (FIG. 13)
In, the application program
Get SEID of AVDISCFCM of MD drive. Step S
At 24, AVDISCFCM of the designated MD drive is
Acquires media information based on the settable command from the application program (provided that the media is loaded). In step S25, the acquired media information is stored in the AV drive of the designated MD drive.
The information is stored in the memory under the control of the SCFCM, and the inner table is generated.
Proceed to. That is, the GUI display in the multiple mode is not performed. However, when only the MD drive 2 is detected, the MD drive 2 is a double MD drive, so G
The button 71a is displayed on the display of the UI.

The inner table generation processing involves turning on / off the power of each device, plugging / unplugging, attaching / detaching the MD of the device / writing to the disk, and erasing the Mu.
It may be executed every time the ltiAVDISCFCM detects, thereby updating the inner table.

Next, with reference to the flowchart of FIG. 15, an operation for reproducing a predetermined track from the GUI display of FIG. 6 will be described.

[0095] Based on the GUI display, the user operates the touch panel 23 to move the cursor to the Play button 73 and clicks on it to start the process.

When a playback operation command is input from the application program, the MultiAVDISCFCM executes step S
At 31, the track specified by the GUI (in this case,
[03]: CCC 12:05) Play command to play AVDISCFC
The process is output to M1, and the process proceeds to step S32.

In step S32, AVDISCFCM1
Based on the received Play command, an AV / C command for instructing reproduction of the designated track is output to the MD drive 2.

Here, with reference to the flowchart of FIG. 16, when the AV / C command for instructing the reproduction is received.
The operation of the MD drive 2 will be described. Upon receiving the playback AV / C command, the MD drive 2 starts processing, and in step S41, the CPU 55 transmits the IEEE1394 serial bus 4, the IEEE1394 interface 58, and the internal bus 5
4 based on the playback AV / C command input via
By controlling the recording / playback unit 53, the MD (device ID: MDS-DL1-
The MD 61 corresponding to 1 is reproduced.

At the step S42, when the reproduction is completed, the CPU 55 sends an AV / C response of the reproduction completion to the internal bus 54, the IEEE1394 interface 58, the IEEE1394.
The signal is output to the IRD 1 via the serial bus 4, and the process is terminated. In the following description, the MD drives 2 and 3 perform the same reproduction operation, and thus the description is omitted.

Now, the description returns to the flowchart of FIG. In step S33, the MultiAVDISCFCM determines whether or not an AV / C response indicating the end of reproduction has been received.

In step S33, the reproduction end AV / C
If it is determined that the response has been received, the process ends.

Next, the operation of the IRD 1 when the Random button 81 is turned on / off (black / white display) in the GUI of FIG. 6 will be described with reference to the flowchart of FIG.

The user operates the touch panel 23 to
GUI on the application program in the state shown in Fig. 6
When the Random button 81 is clicked, the process is started.

In step S51, the application program determines whether the random mode is on or off. For example,
If it is determined that the switch is on, the process proceeds to step S
Go to 52.

In step S52, the application program stores the command sortTabl in MultiAVDISCFCM.
e () is sent, and a command is sent to shuffle (randomly rearrange) the order of the tracks in the inner table, and the process proceeds to step S53.

In step S53, MultiAVDISCFCM
Shuffles and rearranges the inner table based on a command from the application program, and proceeds to the process of step S54.

In step S54, the application program updates the disk display field 71 and the track display field 72 in FIG. 7 based on the inner table, displays the GUI, and ends the processing.

If it is determined in step S51 that the random mode is not on, in step S55, the application program executes the MultiAVDISCFCM
Then, a command is issued to rearrange the inner table in the order of the disk and the track.

In step S56, MultiAVDISCFCM
Reorders the inner table in the order of disk and track based on a command from the application program, proceeds to the processing in step S54, and the subsequent processing is repeated.

Next, after the random mode on process of FIG. 17 (the processes of steps S51 to S54), the process when the MD drive 2 performs reproduction in the random mode on state is shown in the flowchart of FIG. I will explain.

[0111] Based on the GUI display, the user operates the touch panel 23 to move the cursor to the Play button 73 and clicks to start the process.

When a playback operation command is input from the application program, the MultiAVDISCFCM executes step S
At 61, the current track of the inner table is read.

In step S62, MultiAVDISCFCM
For example, when the current track is in the AVDISCFCM3, a Play command for reproducing the read track is issued to the AVDISCFCM3 of the current track, and step S
Proceed to 63.

In step S63, AVDISCFCM3
Is the MD drive 3 based on the received Play command.
Output an AV / C command for instructing reproduction of the designated track.

In step S64, MultiAVDISCFCM
Determines whether an AV / C response indicating the end of playback has been received from the MD drive 3. When it is determined that the AV / C response has not been received, the apparatus is in a reception waiting state until the AV / C response indicating the end of reproduction is received. If it is determined that the AV / C response has been received, the process proceeds to step S65.
Proceed to processing.

In step S65, MultiAVDISCFCM
Refers to the rearranged inner table and determines whether there is a next track. If it is determined in step S65 that there is a next track, the process proceeds to step S65.
Returning to the process of 61, the subsequent processes are repeated. If it is determined in step S65 that there is no next track, the process ends.

Next, referring to the flowchart of FIG. 19, the track to be reproduced is changed to the previous track.
The processing of IRD1 will be described.

The user operates the touch panel 23 to
GUI Prev on the application program shown in Fig. 6
The process is started when the cursor is moved to the Track button 78 and clicked.

From the application program, Prev T
When receiving a signal corresponding to the operation of the rack button 78, the MultiAVDISCFCM determines in step S71 whether or not the specified device is being played. If it is determined in step S71 that the specified device is not being played, the process proceeds to step S72.

In step S72, MultiAVDISCFCM
Refers to the inner table to determine whether the previous track exists. For example, the currently specified track is [03] CCC 12:05, and if [02] BBB 5:11 exists in the previous track, it is determined that the previous track exists, and The process proceeds to S73.

In step S73, MultiAVDISCFCM
Outputs a PreviousTrack command to reproduce the previous track [02] BBB 5:11 with reference to the inner table to AVDISCFCM1, and proceeds to the process of step S74.

In step S74, AVDISCFCM1
Is the D of MD drive 2, which is the device specified in DCM 1.
An AV / C command for reproducing the track [02] BBB 5:11 of ISC1 is output to the MD drive 2.

The MD drive 2 executes the processing shown in the flowchart of FIG. 16 in response to the AV / C command.

In step S75, MultiAVDISCFCM
Determines whether an AV / C response indicating completion of reproduction has been received from the MD drive 2. When it is determined that the AV / C response has not been received, the reception wait state is received until the AV / C response indicating the completion of the reproduction is received. Then, when it is determined that the AV / C response has been received, the processing is ended.

If it is determined in step S71 that the specified disc is being reproduced, the process proceeds to step S76, where the MultiAVDISCFCM sends a stop command for stopping reproduction to the AVDISCFCM1. AVDISCFCM1 outputs the AV / C command of the reproduction stop to MD drive 2 based on this,
The process proceeds to step S72, and the subsequent processes are repeated.

If it is determined in step S72 that the previous track does not exist by referring to the inner table, the flow advances to step S77 to execute MultiAVDISCFCM.
Issues to AVDISCFCM1 a Play command for reproducing the last track of the disk with the previous device ID, and the processing from step S74 is repeated.

In the above description, the operation for changing to the previous track has been described.
The same applies when changing to the next track. In step S72, if there is no previous track and there is no previous disc, the previous track reproduction process ends.

Next, the operation of the IRD 1 when changing the disk will be described with reference to the flowchart of FIG. For example, the user operates the touch panel 23, clicks the GUI button 71a on the application program in FIG. 6, and further selects the currently specified DISC based on the displayed drop-down list 71b.
After moving from 1: MDS-DL1-1 to DISC2: MDS-DL1-2 (moving the position shown in white) and clicking, the Play button 73 is clicked to start processing.

In step S81, MultiAVDISCFCM
Determines whether DISC1 is being reproduced. If it is determined that DISC1 is being reproduced, the process proceeds to step S82, and the MultiAVDISCFCM sends a Stop command to AVDISCFCM1. AVDISCFCM1 determines, based on this, the AV /
A C command is issued to the MD drive 2, and the process proceeds to step S83. If it is determined in step S81 that reproduction is not being performed, the process of step S82 is skipped, and the process proceeds to step S83.

In step S83, MultiAVDISCFCM
Refers to the inner table and executes a Play command to play the first track “KOUGI1” of the specified DISC2 by AVDI
The data is output to SCFCM2, and the process proceeds to step S84.

In step S84, AVDISCFCM2
Outputs an AV / C command for reproducing “KOUGI1” of the designated track on the MD drive 2 and proceeds to the process of step S84.

The MD drive 2 executes the processing of the flowchart in FIG. 16 in response to this command.

In step S85, AVDISCFCM2
Waits for a playback completed AV / C response from the MD drive 2, and upon receiving a playback completed AV / C response, the process ends.

In this example, the example of changing to the next disk has been described, but the same applies to the immediately preceding disk. When changing from DISC1 to the previous disk, change to DISC3. Will be done.

Next, the reproduction operation of the IRD 1 when the Repeat button 82 is clicked and the repeat reproduction is turned on will be described with reference to the flowchart of FIG. The user operates the touch panel 23 to display a GUI Repeat button 82 on the application program shown in FIG.
Click to turn on repeat playback.
Sent to ltiAVDISCFCM. The MultiAVDISCFCM sets “Repeat” to “ON” based on the information of the “ON” setting of the repeat playback from the application program. Then, when the Play button 73 is clicked in this state, the processing is started.

In step S91, MultiAVDISCFCM
Selects a track specified by the application program from the inner table, and issues a Play command for playback to the AVDISCFCM (eg, AVDISCFCM) corresponding to the track.
CM1), and the process proceeds to step S92.

In step S92, AVDISCFCM1
MD / AV command to play the specified track
Output to drive 2.

The MD drive 2 executes the processing of the flowchart of FIG. 14 in response to the AV / C command.

In step S93, the CPU 26 of the IRD 1
Waits for an AV / C response from the MD drive 2, and upon receiving the AV / C response, proceeds to the process of step S94.

In step S94, MultiAVDISCFCM
Determines whether Repeat is set to ON.
In this example, since Repeat is set to ON, the process returns to step S92, and the subsequent processes are repeated.

If it is determined in step S94 that Repeat is not set to ON (the setting has been canceled), the process ends.

Next, the media information management processing will be described with reference to the flowchart in FIG.

In step S101, the event manager determines whether a new medium (recording medium) has been inserted (including whether the main power has been turned on or the bus has been reset), and a new medium has been inserted. If not, the FCM is notified.

At step S102, the application program acquires the content management information from the inserted new medium. In step S103, the application program stores the acquired content management information in the memory in the FCM management. In step S104, the event manager determines whether the inserted medium has been disconnected from the device (including whether the main power has been turned off or the bus has been reset), and has determined that the medium has been removed from the device. In this case, in step S105, the media information is deleted from the memory placed under the management of the FCM.

When it is determined in step S101 that a new medium has not been inserted, the processing is
Proceed to step S104. If it is determined in step S104 that the inserted medium has not been removed, the process ends.

In the above description, the operation at the time of reproduction has been described. However, this operation can be performed not only at the time of reproduction but also at the same time as recording. Processing such as dubbing is also possible by processing to reproduce one of the connected information devices and record the other.

In the above description, an example in which a plurality of information devices of the same type are MD drives has been described. However, the information devices may be a magnetic recording medium, an optical recording medium, a magneto-optical recording medium, or a semiconductor recording medium. Any device capable of recording or reproducing information on a recording medium such as a medium may be used. For example, in addition to an MD drive, a DV (Digital Video) recording and reproducing device, a VHS (Video Home System) recording and reproducing device, an S-VHS
(Super-Video Home System) recording / playback device, CD (Compa
ct Disc) drive, DVD (Digital Versatile Disc) drive, D-VHS (Digital-Video Home System) recording / reproducing device, Hi8 recording / reproducing device, etc. You may make it connect.

The above-described series of processing can be executed by hardware, but can also be executed by software. When a series of processing is executed by software, a program constituting the software may be executed by a computer built into dedicated hardware or by installing various programs to execute various functions. It is installed from a program storage medium to a possible general-purpose personal computer or the like.

This program storage medium is provided not only to the hard disk drive 27 in which the program is recorded but also provided to the user in a state of being incorporated in the IRD 1 in advance as shown in FIG. A magnetic disk 44 (including a floppy (registered trademark) disk) on which a program is recorded and an optical disk 43 (CD-ROM (Compa
ct Disk-Read Only Memory), DVD (Digital Versatile)
Disk), magneto-optical disk 42 (MD (Mini-Dis
k)) or a package medium including the semiconductor memory 41 or the like.

In the present specification, the steps of describing a program recorded on a program storage medium are not necessarily performed in chronological order, but are not necessarily performed in chronological order in the order described. Both include processes executed in parallel or individually.

In the present specification, the system refers to the entire device including a plurality of devices.

[0152]

According to the information processing apparatus and method and the recording medium of the present invention, information of a recording medium attached to a plurality of information devices connected via a network is acquired, and Information is centrally stored and managed, and multiple information devices are controlled based on the stored information on the recording medium, so that multiple information devices can be used as a virtual multiple device of one information device. It can be used, and its operation and management of information can be facilitated.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a network system.

FIG. 2 is a block diagram illustrating a detailed configuration of an IRD in FIG. 1;

FIG. 3 is a block diagram showing a detailed configuration of the MD drive in FIG. 1;

FIG. 4 is a diagram illustrating software stored in a hard disk drive in FIG. 2;

FIG. 5 is a diagram illustrating an inner table.

FIG. 6 is a diagram illustrating an example of a GUI displayed on the monitor of FIG. 2;

FIG. 7 is a diagram showing an example of a GUI displayed on the monitor of FIG. 2;

8 is a diagram illustrating a GUI displayed when an additional registration button in FIG. 7 is clicked.

9 is a diagram illustrating a GUI displayed when a registration deletion button in FIG. 7 is clicked.

FIG. 10 is a flowchart illustrating a network management process.

FIG. 11 is a flowchart illustrating an operation when an inner table is generated.

FIG. 12 is a flowchart illustrating an operation when an inner table is generated.

FIG. 13 is a flowchart illustrating an operation when an inner table is generated.

FIG. 14 is a diagram illustrating a GUI displayed as an initial screen when an inner table is generated.

FIG. 15 is a flowchart illustrating an operation when the IRD of FIG. 2 reproduces a specified track.

FIG. 16 is a flowchart illustrating an operation when the MD in FIG. 3 performs a reproduction process.

FIG. 17 is a flowchart illustrating an operation when the IRD 2 of FIG. 2 performs random processing.

FIG. 18 is a flowchart illustrating an operation when the IRD 2 of FIG. 2 performs random playback processing.

FIG. 19 is a flowchart illustrating an operation when the IRD of FIG. 2 performs reproduction by changing tracks.

FIG. 20 is a flowchart illustrating an operation when the IRD of FIG. 2 performs playback by changing the DISC.

21 is a flowchart illustrating an operation when the IRD of FIG. 2 performs reproduction in a repeat state.

FIG. 22 is a flowchart illustrating an operation when the IRD of FIG. 2 performs a media information management process.

[Explanation of symbols]

1 IRD, 2, 3 MD drive, 4 IEEE1394 serial bus, 11 monitor, 21 input / output interface,
22 tuner, 23 touch panel, 24 HDD, 25
Internal bus, 26 CPU, 27 RAM, 28 ROM, 29
IEEE1394 interface, 30 drives, 51
LCD, 52 touch panel, 53 recording and playback unit, 54
Internal bus, 55 CPU, 56 RAM, 57 ROM, 58 I
EEE1394 interface, 61, 62 MD, 71 Device display field, 72 Track display field

Claims (13)

[Claims] 1. A recording medium information acquiring means for acquiring information of a recording medium attached to a plurality of information devices connected via a network, and a recording medium information acquired by the recording medium information acquiring means. An information processing apparatus comprising: a storage management unit configured to centrally store and manage; and a control unit configured to control the plurality of information devices based on information of the recording medium stored by the storage management unit. apparatus. 2. The information processing apparatus according to claim 1, further comprising control information acquisition means for acquiring control information for controlling each of the information devices from the plurality of information devices via a network. The information processing apparatus according to claim 1, wherein the plurality of information devices are controlled based on the acquired control information. 3. The information processing apparatus according to claim 1, wherein the recording medium can only be reproduced, or can be recorded and reproduced. 4. The information processing apparatus according to claim 1, wherein said network is constituted by an IEEE 1394 serial bus. 5. The control device further comprises: display means for displaying information on the recording medium stored by the storage management means; and selection means for selecting information on the recording medium displayed by the display means. 2. The information processing apparatus according to claim 1, wherein the control unit controls the information device in accordance with the content selected by the selection unit from the information of the recording medium displayed by the display unit. . 6. When the information device is powered on,
When the information device is plugged in, when the recording medium is mounted on the information device, or when content is recorded on the recording medium, the storage management unit is acquired by the recording medium information acquisition unit. The information processing apparatus according to claim 1, wherein the information of the recording medium is stored. 7. When the information device is turned off,
When the information device is unplugged, when the recording medium is detached from the information device, or when the content is erased from the recording medium, the storage management unit stores the information of the recording medium stored by itself. The information processing apparatus according to claim 1, wherein the information processing apparatus deletes the information. 8. The information of the recording medium is management information of recording contents of the recording medium, and includes device ID, track number, track name, recording time, HAVi media format, or MIC. 2. The information processing device according to 1. 9. The information processing apparatus according to claim 1, further comprising a model information acquisition unit configured to acquire model information of a plurality of information devices connected via the network. 10. The information processing apparatus according to claim 9, wherein the model of the information device is identified by a type of FCM. 11. The information processing apparatus according to claim 1, wherein the plurality of information devices include information devices of the same type. 12. A recording medium information acquisition step of acquiring information of a recording medium attached to a plurality of information devices connected via a network, and a recording medium information acquisition step of acquiring the information of the recording medium acquired in the processing of the recording medium information acquisition step. A storage management step of centrally storing and managing information; and a control step of controlling the plurality of information devices based on the information of the recording medium stored in the processing of the storage management step. Information processing method. 13. A recording medium information acquisition control step of controlling acquisition of information of a recording medium attached to a plurality of information devices connected via a network; and a recording medium information acquisition control step of acquiring the information. Centralized storage of information of the recording medium, a storage management control step of controlling management, and control of controlling the plurality of information devices based on the information of the storage medium stored in the processing of the storage management control step And a program storage medium storing a computer readable program.