JP2002057683A - Control equipment and control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically utilize application software which utilizes control information (DCM) for controlling equipment to be controlled. SOLUTION: When digital AV equipment as the equipment to be controlled is connected to an IEEE1394 bus 2, the CPU 10 of a receiver 3 as this control equipment acquires DCM included in the configuration ROM of the digital AV equipment and stores it in a RAM 12. Further, the CPU 10 acquires the application software from digital satellite broadcasting or the Internet or the like for instance based on identification information(ID) for identifying the application software which utilizes the DCM and acquisition place information present in the DCM or the other part of the configuration ROM and stores it in the RAM 12. Thus, in the receiver 3, the application software can be automatically utilized.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a control device for controlling a controlled device via a communication bus and a control method therefor. More specifically, the present invention relates to a control device or the like that automatically uses an application software by acquiring application software that uses control information for controlling the controlled device from the controlled device or another network. .

[0002]

2. Description of the Related Art In recent years, in a home network system, HAVi (Home Audio Video interop) has been used as middleware for comprehensively managing and controlling a plurality of digital AV devices connected to an IEEE1394 bus.
A mutual specification called rability) has been proposed.

[0003]

In such a home network system, a plurality of digital AV devices connected to the IEEE 1394 bus include a digital AV device to be controlled (hereinafter referred to as a "control device") and a controlled device. Digital AV equipment (hereinafter, referred to as “controlled equipment”). The control device can hold control information for controlling the controlled device in advance, or can acquire the control information from the controlled device or another network.

[0004] However, even if the control device can acquire the control information of each controlled device, it cannot use the control information as it is, and application software for using the control information is required.

[0005] Therefore, the control device needs to store the application software in a secondary storage medium such as a memory or a hard disk in advance in order to make the application software usable.
It was very troublesome for the user.

[0006] It is an object of the present invention to provide a control device and a control method for automatically using application software in a home network system.

[0007]

A control device according to the present invention is a control device for controlling a controlled device via a communication bus, and a first device for storing control information for controlling the controlled device. Storage means, first information acquisition means for acquiring application software using control information stored in the first storage means, and first information acquisition means for storing the application software acquired by the first information acquisition means. 2 storage means.

[0008] A control method according to the present invention is a control method of a control device for controlling a controlled device via a communication bus, for controlling the controlled device stored in a first storage means. And a step of storing the obtained application software in the second storage means.

In the present invention, control information for controlling the controlled device is stored in the first storage means.
The control information stored in the first storage means is stored in advance in the first storage means or obtained from the controlled device or another network such as digital satellite broadcasting or the Internet. is there. The acquisition of the control information is performed, for example, when the controlled device is connected to the communication bus.

[0010] Application software utilizing the control information stored in the first storage means is obtained from the controlled device or another network such as digital satellite broadcasting or the Internet, and the second storage means. Is stored. As a result, application software that uses control information for controlling each controlled device can be automatically used. The acquisition of the application software is performed, for example, when the controlled device is connected to the communication bus.

In the case where control information for controlling a controlled device and application software using the control information are obtained from another network such as digital satellite broadcasting or the Internet, the control information and the application software When there is a change in the software, by notifying the fact or acquiring the control information and the application software after the change, it is possible to immediately cope with a software update due to a bug correction or addition of a new function.

[0012] Further, the information is stored in a second storage means,
When the controlled device corresponding to the available application software is not connected to the communication bus, the user is prompted to connect the display control device to the communication bus by notifying that fact.

[0013]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 shows an AV system 1 as an embodiment. This AV system 1 is based on IEEE13
A first receiving device (IRD: integra
tedReceiver and Decoder) 3, CD (Compact Disc)
Player 4, second receiving device (IRD) 5, digital VTR (Digital Video Tape Recorder) 6, MD (Mini
Disc) Deck 7, DVD (Digital Versatile Disc)
Player 8 and digital TV (Digital Televisio
n) 9 are connected to each other.

In the AV system 1, the first receiving device 3 as a control device usually includes a digital VTR 6, an MD deck 7, and a DVD player 8 as controlled devices.
By controlling the CD player 4 and the digital TV 9 as other controlled devices by executing HAVi software described later as necessary.

In the AV system 1, the second receiving device 5 as a control device controls the CD player 4 and the digital TV 9 as controlled devices, respectively, and executes HAVi software described later as necessary. By executing, the digital VTR 6, the MD deck 7, and the DVD player 8 as other controlled devices are controlled respectively.

Next, the IEEE 1394 bus will be described. The communication protocol connecting the above AV devices is as follows:
FIG. 2 shows an IEEE 1394 bus.
FIG. 4 is a diagram showing a cycle structure of data transmission of the devices connected by No. 4; In IEEE 1394, data is divided into packets and transmitted in a time division manner on the basis of a cycle having a length of 125 μs. This cycle is created by a cycle start packet supplied from a node having a cycle master function (any device connected to the bus). In the isochronous transfer, a band (a time unit but called a band) necessary for transmission is secured from the beginning of every cycle. Therefore, in the isochronous transfer, transmission of data within a certain time is guaranteed. However, if a transmission error occurs, there is no protection mechanism and data is lost. Asynchronous transfer, in which the node that has secured the bus as a result of arbitration and transmits an asynchronous packet during the time that is not used for isochronous transfer in each cycle, uses an acknowledge and retry, ensures reliable transmission. However, the transmission timing is not constant.

In order for a given node to perform isochronous transfer, the node must be compatible with the isochronous function. At least one of the nodes corresponding to the isochronous function must have a cycle master function. In addition, IEEE 1394
At least one of the nodes (AV devices) connected to the bus must have an isochronous resource manager function.

IEEE 1394 is an ISO / IEC13 standard.
213 based on the CSR (Control & Status Register) architecture having a 64-bit address space. FIG. 3 is a diagram illustrating the structure of the address space of the CSR architecture. The upper 16 bits are
This is a node ID indicating a node on each IEEE 1394, and the remaining 48 bits are used to specify an address space given to each node. The upper 16 bits further comprise 10 bits of the bus ID and 6 bits of the physical ID (node ID in a narrow sense).
Split into bits. Since a value in which all bits are 1 is used for a special purpose, it is possible to designate 1023 bust 63 nodes.

The space defined by the upper 20 bits of the address space of 256 terabytes defined by the lower 48 bits is an initial register space (2048 bytes) used for CSR-specific registers and IEEE 1394-specific registers. Initial Register Space), a private space (Private Space), an initial memory space (Initial Memory Space), etc., and the space defined by the lower 28 bits is replaced by the space defined by the upper 20 bits. , The configuration ROM (Co
nfiguration read only memory), Initial unit space used for node-specific applications (Initial Unit)
Space), Plug Control Register (Plug Control)
Register (PCRs)).

FIG. 4 is a view for explaining offset addresses, names, and functions of main CSRs. The offset in FIG. 4 is the FF where the initial register space starts.
FFF00000000h (The number with h at the end is 16
(Representing a hexadecimal display). Bandwidth Available Register with Offset 220h
ster) indicates a band that can be allocated to isochronous transfer, and only the value of the node operating as an isochronous resource manager is valid. That is, although each node has the CSR in FIG. 3, only the isochronous resource manager of the bandwidth available register is valid. In other words, the bandwidth available register has substantially only the isochronous resource manager.
The maximum value is stored in the bandwidth available register when no band is allocated to the isochronous transfer, and the value decreases every time the band is allocated.

Channel Available Registers at offsets 224h to 228h
In (r), each bit corresponds to each of the channel numbers from 0 to 63, and when the bit is 0, it indicates that the channel has already been allocated. Only the channel available register of the node operating as the isochronous resource manager is valid.

Returning to FIG. 3, a general ROM is stored at addresses 200h to 400h in the initial register space.
(Read only memory) A configuration ROM based on the format is arranged. FIG. 5 is a diagram illustrating a general ROM format. IEEE13
The node as a unit of access on the node 94 may include a plurality of units that operate independently while using an address space in common in the node. The unit directory (unit_directories) can indicate the version and location of software for this unit. The locations of the bus info block and the root directory (root_directory) are fixed,
Other block positions are specified by offset addresses.

FIG. 6 is a diagram showing details of the bus info block, the root directory, and the unit directory. Company_ID in the bus info block includes
An ID number indicating the manufacturer of the device is stored. Chip_ID stores a unique ID unique to the device and unique in the world that does not overlap with other devices. In addition, according to the standard of IEC61883, the unit specification ID (unit_spec_id) of the unit directory of the device satisfying IEC61883 is
00h is written in the first octet, A0h is written in the second octet, and 2Dh is written in the third octet. Furthermore, the first octet of the unit switch version (unit_sw_version) contains 0
1h is the third octet LSB (Least Significan)
1 is written in (t Bit).

In order to control the input / output of the device via the interface, the node stores IEC6 addresses at addresses 900h to 9FFh in the initial unit space shown in FIG.
PCR (Plug Control Registe
r). This implements the concept of a plug to form a signal path logically similar to an analog interface. FIG. 7 is a diagram illustrating the configuration of the PCR. PCR is an oPC representing an output plug
R (output Plug Control Register) and iPCR (input Plug Control Register) representing an input plug. The PCR is a register oMPR (output Maste) indicating information of an output plug or an input plug unique to each device.
r Plug Register) and iMPR (input Master Plug R)
egister).

Although each device does not have a plurality of oMPRs and iMPRs, each device has a corresponding oMPR and iMPR.
It is possible to have a plurality of PCRs and iPCRs depending on the capability of the device. The PCR shown in FIG. 7 has 31 oPCRs and iPCRs each. The flow of isochronous data is controlled by manipulating registers corresponding to these plugs.

FIG. 8 shows oMPR, oPCR, iMPR,
FIG. 3 is a diagram illustrating a configuration of an iPCR. FIG. 8A shows oMP
FIG. 8B shows the structure of oPCR, and FIG.
FIG. 8D shows the configuration of the PR, and FIG. 8D shows the configuration of the iPCR. The 2-bit data rate capability on the MSB side of the oMPR and iMPR stores a code indicating the maximum transmission rate of isochronous data that can be transmitted or received by the device. oMP
R broadcast channel base (broadcast chan
nel base) specifies the number of the channel used for broadcast output.

5-bit number of output plugs on the LSB side of oMPR
Indicates the number of output plugs of the device, ie, oPC
A value indicating the number of R is stored. 5 on the LSB side of iMPR
Number of input plugs
input plugs) contains the number of input plugs the device has,
That is, a value indicating the number of iPCRs is stored. non-pers
istent extension field and persistent extension f
The ield is an area defined for future extensions.

The on-line of the MSB of the oPCR and iPCR indicates the usage status of the plug. That is, if the value is 1, the plug is ON-LINE,
0 indicates OFF-LINE. oPCR and iPCR Broadcast Connection Counter (br
An oadcast connection counter value indicates whether a broadcast connection exists (1) or does not exist (0).
A point-to-point c counter having a 6-bit width of oPCR and iPCR
The value that the onnection counter has is the point-to-point connection that the plug has.
connection).

The value of the channel number having a 6-bit width of oPCR and iPCR indicates the number of the isochronous channel to which the plug is connected. The value of the data rate (data rate) having a 2-bit width of the oPCR indicates the actual transmission speed of the packet of the isochronous data output from the plug. Overhead ID having 4-bit width of oPCR
The code stored in (overhead ID) indicates the over bandwidth of the isochronous communication. The value of a 10-bit payload of the oPCR indicates the maximum value of data included in an isochronous packet that can be handled by the plug.

FIG. 9 is a diagram showing the relationship between plugs, plug control registers, and isochronous channels. AV devices (AV-devices) 71 to 73 are IEEE
They are connected by an E1394 serial bus. AV
Of the oPCR [0] to oPCR [2] in which the transmission speed and the number of oPCRs are defined by the oMPR of the device 73,
The isochronous data whose channel is specified by the oPCR [1] is transmitted to the channel # 1 (channel # 1) of the IEEE 1394 serial bus. AV device 71
Of the iPCR [0] and iPCR [1] whose transmission speed and the number of iPCRs are defined by the iMPR, the input device # 1 has the transmission speed and the iPCR [0]. 1
Read the isochronous data sent to. Similarly, the AV device 72 sends the isochronous data to the channel # 2 (channel # 2) specified by the oPCR [0], and the AV device 71 transmits the data from the channel # 2 specified by the iPCR [1]. Read the isochronous data.

In this manner, data transmission is performed between devices connected by the IEEE 1394 serial bus. In the system of this embodiment, the IEEE 1394 serial bus is used.
Using an AV / C command set defined as a command for controlling a device connected via a serial bus, control of each device, determination of a state, and the like can be performed. Next, the AV / C command set will be described.

First, the AV / AV used in the system of this embodiment
SubunitIdentifier Descript in C command set
The data structure of or will be described with reference to FIGS. Figure 10 shows the Subunit Identifier Descripto
The data structure of r is shown. As shown in FIG.
It is formed by a list of the hierarchical structure of the unit identifier descriptor. The list represents, for example, a receivable channel in the case of a tuner, and a tune recorded therein in the case of a disc. The list in the highest layer of the hierarchical structure is called a root list, and for example, list 0 is the root for the lower list. Lists 2 to (n-1) are also route lists. There are as many route lists as objects. Here, the object is, for example, each channel in digital broadcasting when the AV device is a tuner. Also,
All lists in one hierarchy share common information.

FIG. 11 shows the format of the General Subunit Identifier Descriptor used in the existing system. Subunit Identifier Descrip
In tor, attribute information about the function is described in contents. The value of the descriptor_length field itself is not included. The generation_ID indicates the version of the AV / C command set, and its value is currently “00h” (h represents hexadecimal) as shown in FIG. Here, “00h” indicates that the data structure and command are
It means that it is version 3.0 of AV / C General Specification. Also, as shown in FIG.
All values except 0h "are reserved and reserved for future specifications.

The size_of_list_ID indicates the number of bytes of the list ID. size_of_object_ID
Indicates the number of bytes of the object ID. size o
The f object position indicates the position (the number of bytes) in the list used for reference when performing control. numb
er_of_root_object_lists indicates the number of root object lists. root_object_list_id indicates an ID for identifying the root object list at the top of each independent hierarchy.

The subunit_dependent_length is the following subu
Indicates the number of bytes in the nit_dependent_information field. subunit_dependent_information is a field indicating information unique to the function. manufacturer_dep
endent_length is the following manufacturer_dependent_info
Indicates the number of bytes in the rmation field. manufactu
rer_dependent_information is a field indicating vendor (manufacturer) specification information. This field does not exist if the descriptor does not include manufacturer_dependent_information.

FIG. 13 shows a list ID allocation range shown in FIG. As shown in FIG.
00h to 0FFFh "and" 4000h to FFF "
“Fh” is reserved and reserved as an allocation range for future specifications. “1000h to 3FFFh” and “10000h to max list ID val”
“ue” is prepared to identify the dependent information of the function type.

Next, the AV /
The C command set will be described with reference to FIGS. FIG. 14 shows a stack model of the AV / C command set. As shown in FIG. 14, the physical layer 81, the link layer 82, the transaction layer 83, and the serial bus management 84
It conforms to EE1394. FCP (Function Contr
ol Protocol) 85 conforms to IEC61883. The AV / C command set 86 complies with the 1394TA specification.

FIG. 15 is a diagram for explaining commands and responses of the FCP 85 of FIG. FCP is IE
This is a protocol for controlling AV equipment on EE1394. As shown in FIG. 15, the controlling side is the controller, and the controlled side is the target. The transmission or response of the FCP command is performed between the nodes using an IEEE 1394 asynchronous transfer write transaction. The target that has received the data returns an acknowledgment to the controller for reception confirmation.

FIG. 16 is a diagram for explaining the relationship between the command and the response of the FCT shown in FIG. 15 in more detail. Node A and node B are connected via an IEEE 1394 bus. Node A is the controller and node B is the target. Each of the node A and the node B has a command register and a response register prepared for each 512 bytes. As shown in FIG. 16, the controller transmits a command by writing a command message to the command register 93 of the target. Conversely, the target transmits a response by writing a response message to the response register 92 of the controller. Control information is exchanged for the above two messages. The type of command set sent by FCP is described in CTS in the data field of FIG. 17 described later.

FIG. 17 shows the data structure of a packet transmitted by asynchronous transfer of an AV / C command. The AV / C command set is a command set for controlling AV equipment, and is CTS (I of the command set).
D) = “0000”. AV / C command frames and response frames are exchanged between nodes using the FCP. To avoid burdening the bus and AV equipment, the response to the command is 100
ms. As shown in FIG. 17, the data of the asynchronous packet is
It consists of bits (= 1 quadlet). The upper part in the figure shows the header part of the packet, and the lower part in the figure shows the data block. destination_ID indicates a destination.

CTS indicates the ID of the command set. In the AV / C command set, CTS = "0000"
It is. The type / response field indicates the functional classification of the command when the packet is a command, and indicates the processing result of the command when the packet is a response. Commands can be roughly divided into (1) a command for controlling functions from outside (CONTROL), (2) a command for inquiring the state from outside (STATUS),
(3) A command (GENERAL INQUIRY (o
pccode support) and SPECIFIC
INQUIRY (opcode and operand
s)), and (4) four types of commands (NOTIFY) for requesting external notification of state changes are defined.

The response is returned according to the type of the command. Responses to the CONTROL command include NOT INPLEMENTED (not implemented), ACCEPTED (accept), and REJECT.
ED (rejection) and (INTERIM (provisional). The response to the STATUS command includes N
OT INPLEMENTED, REJECTED, I
N TRANSITION (migrating) and STAB
There is LE (stable). GENERAL INQUIRY
Responses to the SPECIFIC INQUIRY command include IMPLEMENTED (implemented) and NOT IMPLEMENTED. In response to the NOTIFY command,
NOT IMPLEMENTED, REJECTED,
INTERIM and HANGED (changed).

The subunit type is provided to specify a function in the device.
recorder / player, tuner, etc. are assigned. In order to determine when there are a plurality of subunits of the same type, subunit
Addressing is performed with it id. opcode represents a command, and operand represents a parameter of the command. Additional operation
ands is a field added as needed.
The padding is also a field added as needed. dataCRC (Cyclic Redunda)
ncy Check) is used for error checking during data transmission.

FIG. 18 shows a specific example of the AV / C command. FIG. 18A shows ctype / response
Is shown. The upper part of the figure represents a command, and the lower part of the figure represents a response. "0000"
To CONTROL and “0001” to STATU
S, "0010" has SPECIFIC INQUIR
NOTIFY is assigned to Y and “0011”, and GENERAL INQUIRY is assigned to “0100”. “0101 to 0111” are reserved and reserved for future specifications. In addition, “1000” has NOT I
NPLEMENTED, "1001" is ACCEPT
ED, “1010” has REJECTED, “101”
"1" is IN TRANSITION, "1100" is IMPLEMENTED / STABLE, "110".
CHANGED for "1", INTER for "1111"
IM has been assigned. “1110” is reserved and reserved for future specifications.

FIG. 18B shows a specific example of subunit_type. "00000" contains Video
Monitor, "00011" has Disk rec
order / Player, "00100" is Tap
e recorder / Player, "00101"
Is Tuner, and “00111” is Video Ca
mera, "11100" has Vendor uniq
ue, “11110” has Subunit type
The extended to next byte is assigned. Note that a unit is assigned to “11111”, which is used when it is sent to the device itself, for example, power on / off.

FIG. 18C shows a specific example of the opcode. Opcode for each subunit_type
Table, and here, subunit ty
It shows an opcode when pe is Tape recorder / Player. Further, an operand is defined for each opcode. Here, "00"
h "is VENDOR-DEPENDENT," 50
h ”for SEARCHMODE,“ 51h ”for TIM
ECODE, ATN for "52h", O for "60h"
PEN MIC, "61h" has READ MIC, "
WRITE MIC for 62h ”, LO for“ C1h ”
AD MEDIUM, "C2h" has RECORD, "
PLAY is assigned to “C3h”, and WIND is assigned to “C4h”.

FIG. 19 shows a specific example of an AV / C command and response. For example, when a playback instruction is given to a playback device as a target (consumer), the controller sends a command as shown in FIG. 19A to the target. Since this command uses the AV / C command set, CTS = "0000". ct
The command for controlling the device from outside (CON)
TROL), ctype = "0000" (see FIG. 18A). subunit type
Since e is Tape recorder / Player, subunit type = "00100"
(See FIG. 18B). id indicates the case of ID0, and id = 000. opcode
Is "C3h" meaning reproduction (see FIG. 18C). Operand means FORWARD "7
When the target is reproduced, the target returns a response as shown in FIG. 19B to the controller. Here, since accepted indicating acceptance is included in response, response = "1"
001 "(see FIG. 18A).
Except for se, the rest is the same as FIG.

Next, software of HAVi architecture which is middleware provided between the above-described IEEE 1394 bus and an application will be described. HAVi architecture software is 3
Two application program interfaces (hereinafter referred to as API), namely, AVOS / API,
It can be considered that the API includes the mutual control API and the application API. AVOS / API is
It is a lower-level API and controls functions of a common operation system such as threads, communication, and storage. The mutual control API is a common device control model, provides a basic representation model, and has a function of extending the control model by a command unique to each manufacturer. The application API is the above-mentioned API, and includes, for example, an interactive television application.

The diagram 33a shown in FIG. 20 shows a HAVi including the local bus HAL layer 34 of the local bus 2.
3 is a data flow diagram of a software architecture. In this diagram 33a, the uppermost layer is the application program layer 26. The application program layer 26 is connected to the function control module layer 36 having the above-mentioned AV / C command. The application program layer 26 is provided inside a predetermined device, and is also connected to the device control module 27, the service registry 24, and the stream manager 39.

The device control module 27 is controlled by a device manager 30 connected to the event manager 23. The event manager 23 is connected to the communication media manager 29. The stream manager 39 is inserted between the communication media manager 29 and the application program layer 26. The stream manager 39 allows the application program layer 26 and the communication media manager 29 to send and receive data to and from each other. Communication media manager 29 is also connected to messaging manager 22.

The communication media manager 29 provides an interface to an IEEE 1394 interface 38 which is a local bus interface via a link driver unit 35. Link driver unit 35
Manages the function of updating the GUID list when a local bus reset occurs.

IEEE 1394 HAL interface 3
8 communicates with the serial bus management 84 of FIG. The transaction layer 83 executes a read transaction, a write transaction, a lock transaction, and a track pending transaction, and sets a busy / timeout register when communication is not completed due to communication line congestion or communication time out. Re-execute protocol using (retry protocol)
Re-executes communication. Data is transmitted by the link layer 82 and the physical layer 81.

As described above, the local bus HAL layer 34
Indicates a higher-order application, and the link driver unit 35 indicates a lower-order application.
About this diagram 33a, using FIG.
This will be described in more detail later.

A diagram 40 a shown in FIG. 21 shows a communication channel that can be used for communication with the communication media manager 29. The application program layer 26 accesses the communication media manager 29 to receive bus generation information, a GUID list, a speed map, a topology map, and the like.

The iLink transfer adaptation module (iLink Tr
anspotation Adaptation module; iLinkTAM) 22b
It connects to the communication media manager 29 and performs asynchronous requests and asynchronous responses. Digital interface controller (iLink connection adaptation module; iLinkC
AM) 39a connects to the communication media manager 29 and performs asynchronous requests, asynchronous responses, channel allocation, channel release, bandwidth allocation, bandwidth release, and the like. The stream manager 39 uses the GUID information to make a one-to-one (po
int to poin: PtoP). The device control module 27 communicates with the communication media manager 29 using the isochronous data.

A diagram 40b shown in FIG. 22 schematically illustrates a communication channel of communication performed by the communication media manager 29 with another object. The communication media manager 29 instructs the event manager 23 to perform a bus reset. Communication media manager 29
Manages status information on devices currently connected to the local bus 2, that is, information on which devices have been added and which devices have been removed after the GUID list has been created. The communication media manager 29 provides the iLinkTAM 22a with:
It transmits GUID information and bus reset information, and performs asynchronous reception and isochronous reception. The communication media manager 29 transmits the same information to the device control module 2 that functions as an isochronous data transmission / reception module.
7 is also supplied. Information about the device currently connected to the local bus 2 is also supplied to the digital interface controller 39a.

Next, a description will be given of control devices connected by an IEEE1394 bus to which the HAVi architecture described above is applied. FIG. 23 illustrates an internal hardware configuration of the first receiving device 3. The first receiving device 3 has a CPU (Central Processing Uniform).
t) 10, RO in which various programs and various information are stored
M (read only memory) 11, RAM (random access memory) 12 as work memory of CPU 10, IE
EE1394 interface circuit 13, tuner 1
4. An input / output interface circuit 15 and a modem 16 for connecting to the Internet
7 are connected to each other.

The input / output interface circuit 15 has an LCD
(Liquid Crystal Display) 18 and touch panel 1
9 is connected to the tuner unit 14, and a receiving antenna 20 for digital satellite broadcasting is connected to the tuner unit 14. The ROM 11 includes a configuration ROM. The configuration ROM includes HAVi including text data indicating a device name, a device control module (DCM) as control information, and the like.
Information and the like are stored. The control device acquires the DCM from the controlled device, and controls the controlled device based on the DCM. HAVi information and the like are stored in an appropriate location of the configuration ROM.

Here, the CPU 10 transmits the display data based on the program stored in the ROM 11 to the internal bus 17.
And LC through the input / output interface circuit 15 in sequence.
By transmitting the information to D18, necessary information is displayed on the LCD 18.

The CPU 10 also controls various commands input through the touch panel 19 and the digital AV devices 4-9.
(Refer to FIG. 1), based on a command given via the IEEE 1394 bus 2 as needed, the tuner 1
4 and the IEEE 1394 interface circuit 13.

When the digital AV devices 4 to 8 as controlled devices are connected to the IEEE 1394 bus 2, the CPU 10 acquires the DCM included in the configuration ROM of the digital AV device and stores it in the RAM.
12 based on identification information (ID) for identifying application software that uses the DCM and acquisition location information, which are also present in the DCM or other parts of the configuration ROM. Get and R
Store it in AM12. Here, the application software is not limited to one that uses one DCM for controlling a certain digital AV device, but also includes one that uses a plurality of DCMs for controlling a plurality of digital AV devices.

Acquisition of a DCM or the like from a configuration ROM of a digital AV device as a controlled device is performed using an IEEE 1394 read transaction. The location information of the application software includes, for example, an address of a memory in a digital AV device as the controlled device, a channel of digital satellite broadcasting, and a URL (Universal) of the Internet.
sal Resource Locator).

When the acquisition location information is a digital satellite broadcast channel, the tuner 14 controls the channel to be selected, and acquires application software from the digital broadcast signal of the channel. When the acquisition location information is the URL of the Internet, the user accesses the homepage of the URL with the modem 16 and downloads the application software from the homepage.

The flowchart of FIG.
9 shows an acquisition process of M and application software. This acquisition process is executed when the controlled device is connected to the IEEE 1394 bus 2 as described above.

First, in step ST1, DCM is obtained from the configuration ROM of the controlled device. Next, in step ST2, based on identification information (ID) for identifying application software (application software) in DCM or the like and acquisition location information, the DC
Obtain application software that uses M.

The first receiving device 3 transmits, for example, an instruction to receive a digital satellite broadcast of a predetermined channel to the touch panel 1.
9, the tuner section 14 selects the channel, and transfers the obtained video signal and audio signal to the internal bus 17 and the IEEE 1394 interface circuit 13.
And the corresponding digital AV equipment via the IEEE 1394 bus 2 sequentially.

In the above description, the CPU 10 of the first receiving device 3 as the control device acquires the DCM for controlling the digital AV device as the controlled device from the configuration ROM of the digital AV device. showed that. However, the first receiving device 3 has a DC for controlling a digital AV device as a controlled device.
M may be stored in the ROM 11 in advance. Alternatively, the configuration ROM of the digital AV device as the controlled device stores only the information on the location where the DCM is obtained, and the CPU 10 of the first receiving device 3 executes, for example, a digital The DCM may be obtained from satellite broadcasting or the Internet. Although the detailed description of the internal configuration of the second receiving device 5 is omitted, it is the same as the internal configuration of the first receiving device 3 described above.

Next, the controlled device will be described. Here, the digital VTR 6 will be described. FIG. 25 shows the internal configuration of the digital VTR 6. In the digital VTR 6, a CPU 45, a ROM 46 storing various programs and various information, a RAM 47 as a work memory of the CPU 45, an IEEE 1394 interface circuit 48, a recording / reproducing unit 49, and an input / output interface circuit 50 are each connected via an internal bus 51. Interconnected.

The input / output interface circuit 50 includes an LCD
(Liquid Crystal Display) 52 and touch panel 5
3 are connected. The ROM 46 includes a configuration ROM. The configuration ROM includes text data indicating a device name, and a device control module (DCM: Device) as control information.
HAVi information including a Control Module) is stored. Further, identification information (ID) for identifying application software that uses the DCM and acquisition location information are present in the DCM or other portions of the configuration ROM. This acquisition location information is, for example, a digital AV as the controlled device.
For example, the address of a memory in the device, the channel of digital satellite broadcasting, the URL of the Internet, and the like.

Here, the CPU 45 transfers the display data based on the program stored in the ROM 46 to the internal bus 51.
And the LC through the input / output interface circuit 50 sequentially.
By transmitting the information to the D 52, necessary information is displayed on the LCD 52. Further, the CPU 45 includes the touch panel 53
The recording / reproducing unit 49 is controlled as necessary based on various commands input through the IEEE 1394 bus and commands given from the first and second receiving devices 3 and 5 (see FIG. 1) via the IEEE 1394 bus 2. I do.

The digital VTR 6 receives a video or audio signal recording command from a predetermined digital AV device, for example.
A video signal and an audio signal supplied from the device via the IEEE 1394 bus 2 are taken into the recording / reproducing unit 49 via the IEEE 1394 interface circuit 48 and the internal bus 51 in order, and are recorded on a magnetic tape.

When a reproduction command is given, for example, the digital VTR 6 reproduces a video signal or an audio signal from a magnetic tape in the recording / reproducing section 49 and transmits the reproduced signal to the internal bus 51 and the IEEE 1394 interface circuit 48.
And the corresponding digital AV equipment via the IEEE 1394 bus 2 sequentially.

Next, the software in the first and second receiving devices 3 and 5 will be described.
The software configuration will be described in more detail. Receiving
The software in the devices 3 and 5 is H as shown in FIG.
An AVi software module 60 is provided.
This module 60 includes an application (Applicatio
n) 61, Event Manager 23,
Registry 24 for controlling controlled devices
Multiple DCM64 _-1~ 64_-N, These multiple D
CM64_-1~ 64_-NMultiple applications using
Application software (application software) 65_-1~ 6
5_-M, Message System 66,
Communication Media Manager (CMM: Comm
unication Media Manager) 67 and self-device
Each element of the control module (Self DCM) 68
It consists of a statement.

The application 61 includes various graphical user interfaces (GUIs).
Interface) and an application program for executing various events. When the application 61 takes in DCMs for controlling each of the controlled devices into the module 60 via the IEEE1394 bus 2 from the plurality of controlled devices, the application 61
The attribute information of the controlled device according to the CM is queried and read from the registry 24. In addition, application 41
Sends various commands to the above-described software elements such as the event manager 23 and the like, and executes, as a return value, the result of executing the processing content corresponding to the commands from the software elements to the DCM to be controlled. receive.

The registry 24 is a directory service of HAVi software, and can recognize all software elements on the home network. In the registry 24, attribute information corresponding to all the digital AV devices 3 to 9 on the home network is stored in a list format.

The event manager 23 manages events that occur in the home network (for example, when a new device is connected to the network, or when a certain device leaves the network, the network status changes, etc.). It is a software element. When a specific event occurs, the event manager 23 notifies the software element registered in advance of the event of the event.

The CMM 67 is an IEEE1394 bus 2
And an interface with each software module and application in the HAVi software module 60.
And a communication mechanism for transmitting and receiving signals between devices connected to the device.

The message system 66 is an application program interface (A) for communicating software modules of each device on the network.
PI) and plays a role in transmitting messages between software modules. For this reason, in a network employing HAVi software, a message transmitting side and a message receiving side can transmit a message without knowing each other's network location.

As described above, in the present embodiment, the first and second receiving devices 3 and 5 as control devices are used.
Are digital AV devices 4, 6 to 9 as controlled devices.
Is connected to the IEEE 1394 bus 2, D is read from the configuration ROM of the digital AV device.
In addition to the acquisition of the CM, application software using the DCM is acquired from the memory of the digital AV device or another network such as digital satellite broadcasting or the Internet. Therefore,
In the present embodiment, the first and second receiving devices 3 and 5 as control devices use digital A as a controlled device.
Application software using DCM for controlling the V devices 4, 6 to 9 can be automatically used.

Further, in the present embodiment, the first and second receiving devices 3 and 5 as the control devices are provided with the configuration RO of the digital AV device as the controlled device.
M that acquires application software based on identification information (ID) for identifying application software that uses the DCM and acquisition location information, which is present in the DCM acquired from M or another part of its configuration ROM. And D
Application software that uses the CM can be easily obtained.

Note that, although not described above, the first and second receiving devices 3 and 5 as control devices include DCMs for controlling digital AV devices 4 and 6 to 9 as controlled devices,
In the case of obtaining application software using the DCM from another network such as satellite broadcasting or the Internet, periodically check whether or not there is a change in the DCM or the application software. This may be notified to the user by display on the LCD 18 or the like, or the changed DCM or application software may be obtained and overwritten on the RAM 12. As a result, when the software is updated due to a bug fix or a new function addition, it can be dealt with immediately. The notification to the user may be performed by other notification means such as voice output.

Further, although not described above, the first and second receiving devices 3 and 5 as control devices store predetermined D
CM is stored, and application software that uses the DCM is stored.
AV as controlled equipment to be controlled by
When the device is not connected to the IEEE 1394 bus 2, the fact may be notified to the user by display on the LCD 18 or the like. As a result, the user can be prompted to connect the digital AV device to the IEEE 1394 bus 2.

[0084]

According to the present invention, application software that uses control information for controlling a controlled device is obtained from the controlled device or another network, and the application software can be automatically used. can do.

According to the present invention, control information for controlling a controlled device and application software utilizing the control information are obtained from another network such as digital satellite broadcasting or the Internet. When there is a change in control information or application software, this is to be notified, or the control information or application software after the change is obtained. When the software is updated due to a bug fix or addition of a new function, etc. Can be dealt with immediately.

Further, according to the present invention, when the controlled device corresponding to the available application software is not connected to the communication bus, the user is notified of the fact to the communication bus of the controlled device. Connection can be prompted.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an AV system as an embodiment.

FIG. 2 is a diagram showing a cycle structure of data transmission on an IEEE 1394 bus.

FIG. 3 is a diagram for explaining a structure of an address space of a CSR architecture.

FIG. 4 is a diagram illustrating offset addresses, names, and functions of main CSRs.

FIG. 5 is a diagram illustrating a general ROM format.

FIG. 6 is a bus info block, a root directory,
FIG. 3 is a diagram showing details of a unit directory.

FIG. 7 is a diagram illustrating a configuration of a PCR.

FIG. 8 is a diagram showing the configuration of oMPR, oPCR, iMPR, and iPCR.

FIG. 9 is a diagram illustrating a relationship among a plug, a plug control register, and an isochronous channel.

FIG. 10: Subunit Identifier D
FIG. 9 is a diagram for describing a data structure of an “esctor”.

FIG. 11: Subunit Identifier D
FIG. 9 is a diagram for describing a format of an “esscriptor”.

FIG. 12 is a diagram illustrating generation_ID.

FIG. 13 is a diagram for explaining a list ID allocation range.

FIG. 14 is a diagram illustrating a stack model of an AV / C command set.

FIG. 15 is a diagram for explaining the relationship between FCP commands and responses.

FIG. 16 is a diagram for explaining the relationship between FCP commands and responses in more detail;

FIG. 17 is a diagram illustrating a data structure of a packet transmitted in an asynchronous transfer mode of an AV / C command.

FIG. 18 is a diagram illustrating a specific example of an AV / C command.

FIG. 19 is a diagram illustrating a specific example of an AV / C command and a response.

FIG. 20 is a data flow diagram of the HAVi software architecture.

FIG. 21 is a diagram illustrating a communication channel that can be used for communication with a communication media manager.

FIG. 22 is a diagram illustrating a communication channel of communication performed by a communication media manager to another object.

FIG. 23 is a block diagram showing an internal configuration of a first receiving device as a control device.

FIG. 24 is a flowchart showing a process of acquiring a DCM and application software of a control device.

FIG. 25 is a block diagram showing an internal configuration of a digital VTR as a controlled device.

FIG. 26 is a schematic diagram for explaining a HAVi software module;

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... AV system, 2 ... IEEE1394 bus, 3 ... 1st receiving apparatus, 4 ... CD player,
5 ... second receiving device, 6 ... digital VTR,
7 ... MD deck, 8 ... DVD player, 9 ...
・ Digital TV, 10, 45 ... CPU, 11, 4
6 ROM, 12, 47 RAM, 13, 48
... IEEE 1394 interface circuit, 14 ...
· Tuner unit, 15, 50 · · · input / output interface circuit, 16 · · · modem, 17, 51 · · · internal bus
18, 52: LCD, 19, 53: Touch panel, 23: Event manager, 24: Registry, 49: Recording / reproducing unit, 60: HAVi software module, 61: Application , 6
4 _-1 to 64 _-n.. Device Control _Manager, 65 -1 _{to 65 -} m ... application software, 66 ... message system, 67 ... communication media manager, 68 ... self-device control module

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI theme coat ゛ (Reference) H04Q 9/00 321 G06F 9/06 640A F-term (Reference) 5B076 BB02 BB06 5B089 GA23 GB01 GB03 HA18 JA35 JB07 JB10 JB15 KA11 KA13 KB09 KD01 5C025 BA14 BA18 BA25 BA27 BA30 DA01 DA08 5K033 BA01 BA08 DA01 DA13 5K048 AA04 BA02 DA05 DC04 DC07 EB02 FC01 HA01 HA02

Claims (38)

[Claims] 1. A control device for controlling a controlled device via a communication bus, wherein the first storage means stores control information for controlling the controlled device; and A first information obtaining unit that obtains application software that uses the stored control information; and a second storage unit that stores the application software obtained by the first information obtaining unit. Characteristic control equipment. 2. The application software,
The control device according to claim 1, wherein a plurality of control information for controlling the plurality of controlled devices is used. 3. The control device according to claim 1, further comprising a second information acquisition unit that acquires the control information stored in the first storage unit. 4. The control device according to claim 3, wherein the second information obtaining means obtains the control information when the controlled device is connected to the communication bus. 5. The control device according to claim 3, wherein the second information obtaining means obtains the control information from the controlled device. 6. The control device according to claim 3, wherein the second information acquisition unit acquires the control information from another network. 7. The control device according to claim 6, further comprising a change detection unit that detects a change in the control information distributed on the another network. 8. The apparatus according to claim 7, wherein the second information acquisition means acquires the control information from the other network when the change detection means detects a change in the control information. The control device according to item 1. 9. The control device according to claim 7, further comprising a notifying means for notifying that the change of the control information is detected by the change detecting means. 10. The control device according to claim 1, wherein the first information acquisition unit acquires the application software by referring to identification information and acquisition location information of the application software. 11. The identification information and the acquisition location information,
2. The method according to claim 1, wherein the control information is included in the control information.
The control device according to 0. 12. The identification information and the acquisition location information,
The control device according to claim 10, wherein the control device holds the control device. 13. The control device according to claim 1, wherein the first information obtaining means obtains the application software when the controlled device is connected to the communication bus. 14. The control device according to claim 1, wherein the first information obtaining means obtains the application software from the controlled device. 15. The control device according to claim 1, wherein the first information acquisition unit acquires the application software from another network. 16. The control device according to claim 15, further comprising a change detection unit that detects a change in the application software distributed on the another network. 17. The information processing apparatus according to claim 16, wherein the first information acquiring means acquires the application software from the other network when the change detecting means detects a change in the application software. The control device according to item 1. 18. The control device according to claim 16, further comprising a notifying means for notifying when the change detection means detects a change in the application software. 19. A system further comprising: a notifying unit for notifying a controlled device to be controlled using application software stored in the second storage unit when the controlled device is not connected to the communication bus. The control device according to claim 1, wherein: 20. A control method of a control device for controlling a controlled device via a communication bus, wherein the application uses control information for controlling the controlled device stored in a first storage unit. A control method comprising: acquiring software; and storing the acquired application software in a second storage unit. 21. The application software according to claim 20, wherein the application software uses a plurality of pieces of control information for controlling the plurality of controlled devices.
The control method described in 1. 22. The control method according to claim 20, further comprising a step of acquiring said control information stored in said first storage means. 23. The control method according to claim 22, wherein the step of acquiring the control information is performed when the controlled device is connected to the communication bus. 24. The control method according to claim 22, wherein in the step of obtaining the control information, the control information is obtained from the controlled device. 25. The control method according to claim 22, wherein in the step of obtaining the control information, the control information is obtained from another network. 26. The control method according to claim 25, further comprising a step of detecting a change in the control information distributed on the another network. 27. The control method according to claim 26, wherein the step of acquiring the control information is performed when a change in the control information is detected. 28. The control method according to claim 26, further comprising a step of notifying a change in the control information when the change is detected. 29. The control method according to claim 20, wherein in the step of acquiring the application software, the application software is acquired with reference to identification information and acquisition location information of the application software. 30. The identification information and the acquisition location information,
3. The method according to claim 2, wherein the control information is included in the control information.
10. The control method according to 9. 31. The identification information and acquisition location information,
30. The control method according to claim 29, wherein the controlled device holds the control information. 32. The control method according to claim 20, wherein the step of acquiring the application software is performed when the controlled device is connected to the communication bus. 33. The control method according to claim 20, wherein in the step of obtaining the application software, the application software is obtained from the controlled device. 34. The control method according to claim 20, wherein in the step of obtaining the application software, the application software is obtained from another network. 35. The control method according to claim 34, further comprising a step of detecting a change in the application software distributed on the another network. 36. The control method according to claim 35, wherein the step of acquiring the application software is performed when a change in the application software is detected. 37. The control method according to claim 35, further comprising a step of, when a change in the application software is detected, notifying the user of the change. 38. When the controlled device to be controlled using the application software stored in the second storage means is not connected to the communication bus, the method further comprises a step of notifying the user of the fact. The control method according to claim 20, characterized in that: