JP2004129028A - Communication equipment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that a 1394 device on a 1394 bus held between networks with different protocols can not be operated from the current 1394 device that is not adaptable to a 1394 bridge because the bridge is surely needed, when a network other than a 1394 bus exists between 1394 buses, or the like. <P>SOLUTION: Communication equipment is provided with a means for acquiring an element on a second 1394 bus through a third interface means and emulating a node on the second 1394 bus as a node on a first 1394 bus. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
According to the present invention, in a system in which a first 1394 bus and a second 1394 bus are connected by a third network, a communication device that exists on the second 1394 bus and communicates with a node of the third network is used. 1 which is on the 1394 bus and communicates with a node of the third network.
[0002]
[Prior art]
In recent years, 1394 has been in the spotlight as a network for connecting AV devices, and various 1394-compatible products such as BS digital tuners, DVHS decks, and DV cameras have already been released.
[0003]
Attempts have also been made to implement a 1394 bus on a broadband radio, and there are radio communication protocols such as Wireless 1394 and 1394 over 802.11, and a 1394 bus can be constructed over the radio by using the technology shown here. A method for realizing connection between a wired 1394 bus and a wireless 1394 bus as a network through a bridge is discussed.
[0004]
In order to communicate with a wireless terminal from a wired 1394 bus as disclosed in Patent Document 1, the wireless terminal is emulated as a subunit of one communication device on the wired 1394 bus, and the subunit is emulated. A method of controlling the wireless terminal in conjunction with the control of the wireless terminal has also been considered.
[0005]
[Patent Document 1]
JP 2000-156683 A
[0006]
[Problems to be solved by the invention]
However, in the case where a network other than the 1394 bus exists between the 1394 buses, a 1394 bridge is required, so that a current 1394 device that does not support bridges must be connected to a 1394 bus with a different protocol network. The above 1394 device cannot be operated.
[0007]
In addition, if a method as disclosed in Patent Document 1 is used, there is a possibility that one 1394 device can be operated. However, existing devices control the nodes by transmitting AV / C commands to the nodes or subunits assuming the internal configuration of the devices such as BS digital tuners and DVHS decks. It is usually impossible to operate. In the above-mentioned method, in order to emulate the function of the device which originally existed in the configuration of the unit and the subunit into one subunit, the unit or the subunit is inevitably replaced with one different from the conventional AV / C command. It must be transmitted and cannot be controlled in the same way as existing equipment.
[0008]
In addition, since communication devices connected to a network such as wireless are emulated as subunits of communication devices on the 1394 bus, communication can be performed only with devices that can be connected to the network.
[0009]
[Means for Solving the Problems]
In order to solve the above problems, the present invention has taken the following measures.
[0010]
In other words, the communication device according to the present invention is connected to the first 1394 bus in a system in which the first IEEE 1394 (hereinafter abbreviated as 1394) bus and the second 1394 bus are connected by the third network. 1394 interface means, third interface means connected to a third network, means for recognizing each node on the first 1394 bus as a component on the first 1394 bus, and A third interface connected to a third network, a 1394 interface connected to a second 1394 bus, and each node on the second 1394 bus connected to a second 1394 bus. Means for recognizing components on the 1394 bus, and components recognized by the recognizing means. Acquiring the components on the second 1394 bus through the third interface means from the communication device having the means for disclosing through the third interface means, and connecting the nodes on the second 1394 bus to the first 1394 bus. A means to emulate as a node is provided.
[0011]
Further, the communication device has a function of emulating a plurality of nodes on the second 1394 bus obtained through the third interface means as a plurality of nodes on the first 1394 bus.
[0012]
In the communication device, the component on the second 1394 bus acquired through the third interface means includes device information of each node (GUID of each device, register address and value, subunit configuration, etc.). did.
[0013]
In the communication device, when an asynchronous packet (hereinafter abbreviated as an Async packet) is transmitted from an arbitrary node on the first 1394 bus to a node emulated by the communication device, the second 1394 bus A function of transmitting an equivalent Async packet to the above node is provided.
[0014]
Further, in the communication device, when an Async packet is transmitted from an arbitrary node on the first 1394 bus to an emulated node, a response is created and returned in the emulated node. .
[0015]
Further, the communication device has its own function as a node in addition to the emulation node on the second 1394 bus.
[0016]
The above-described means is to provide a communication device with a plurality of 1394 PHYs and emulate a 1394 device on a remote 1394 bus as a node for each 1394 PHY, thereby transmitting an Async packet to the emulated node (AV / AV). (Including the transmission and reception of the C command), an equivalent Async packet can be transmitted to the 1394 device on the remote 1394 bus corresponding to the emulated node. By doing so, the existing 1394 device transmits the Async packet to the node emulated by the communication device on the same 1394 bus, thereby transmitting the Async packet to the 1394 device on the remote 1394 bus. This makes it possible to operate 1394 devices on a remote 1394 bus in the same manner as the conventional operation method.
[0017]
Here, the 1394 PHY refers to an existing PHY chip having basic functions of the 1394 PHY layer, such as repeat, cable state recognition, bus initialization, and arbitration.
[0018]
Further, by copying register information such as a ConfigurationROM (hereinafter abbreviated as ConfigROM) of the 1394 device to a node in a communication device emulating the 1394 device on a remote 1394 bus, the Async packet transmission can be performed. An Async packet (READ_RESPONSE, etc.) for a response to a part (READ_REQUEST, etc. of ConfigROM) can be created and returned by an emulated node in a communication device that has received the Async packet, thereby shortening the transmission path. Also becomes possible.
[0019]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0020]
(1st Embodiment)
A first embodiment of the present invention will be described.
[0021]
FIG. 1 shows an example of a communication system in which a wireless network (107) is connected between a first 1394 bus (105) and a second 1394 bus (106).
[0022]
As illustrated in FIG. 1, the 1394 device 1 (100) is connected to the first 1394 bus (105), and the communication device A (101) is connected to the first 1394 bus (105) and the wireless network (107). ), The 1394 device 2 (103) and the 1394 device 3 (104) are connected to the second 1394 bus (106), and the communication device B (102) is connected to the second 1394 bus (106). It is assumed that the wireless device A (101) and the wireless device B (102) are connected by the wireless network (107).
[0023]
In the 1394 bus, a configuration process is started when the number of connected devices increases or decreases, or when a bus reset occurs. The bus initialization, tree identification, and self-recognition are performed, and a node ID of each device is assigned. These processes are normally performed by the PHY chip, and one node ID is assigned to one PHY chip.
[0024]
In addition to the node ID, a 1394 device is assigned a 64-bit GUID uniquely determined in the world. Usually, one GUID is stored in the ConfigROM that always exists in one node.
[0025]
In the example of FIG. 1, there is one ConfigROM for each of the 1394 device 1 (100), the 1394 device 2 (103), and the 1394 device 3 (104), and the GUID is contained therein. The 1394 device 1 (100) is assigned a node ID on the first 1394 bus (105), and the 1394 device 2 (103) and the 1394 device 3 (104) have node IDs on the second 1394 bus (106). Assigned.
[0026]
The 1394 device 1 (100) has a GUID of 0x11111111 and a node ID on the first 1394 bus (105) of 0 (hereinafter, a device having a node ID of 0 is abbreviated as a node 0, and a device having a node ID of 1 or 2). Similarly, the 1394 device 2 (103) has a GUID of 0x222222222 and the node 1 and the 1394 device 3 (104) on the second 1394 bus (106) have a GUID of 0x33333333. It is assumed that it is assigned to node 2 on the 1394 bus (106).
[0027]
The communication device A (101) has two nodes, ie, a node 1 and a node 2, for emulating the 1394 device on the second 1394 bus (106). Similarly, it is assumed that one node 1 for emulating the 1394 device on the first 1394 bus (105) is also assigned to the communication device B. In the 1394 bus, the node ID is variable, and there is a possibility that the node ID changes due to a bus reset, an increase or decrease in the number of devices, and the like. Here, an example at the time when each of the above 1394 devices is assigned to the node ID is described. Is shown.
[0028]
When the node IDs are different, the node IDs may be replaced and considered.
[0029]
The wireless network (107) between the wireless device A (100) and the wireless device B (102) transmits data according to a protocol such as IEEE802.11a.
[0030]
Next, an outline of the internal configuration of the communication device A (101) and the communication device B (102) is illustrated in FIG. This indicates that the communication device A (101) has two emulation nodes and the communication device B (102) has one emulation node, and a management table is assigned to each emulation node. This emulated node operates as a repeater.
[0031]
FIG. 3 illustrates a block diagram of the communication device A (300).
[0032]
Hereinafter, the function of each block in FIG. 3 will be described.
[0033]
The wireless I / F processing unit (302) has a basic function of a PHY level such as negotiation in wireless transmission, and has a function of transmitting and receiving a packet according to a wireless transmission protocol.
[0034]
The device information transmission / reception unit (303) receives a request for provision of device configuration information on the 1394 bus from a wireless device on the wireless network, acquires data corresponding to the request from the internal device information storage unit (309), and performs wireless communication. It has a function of transmitting to the I / F (301), a function of acquiring device configuration information on the 1394 bus connected to the wireless device on the wireless network, and requesting registration to the external device information storage unit (308). It also has a function of receiving notification of a change in device configuration on a 1394 bus connected to wireless devices on a wireless network.
[0035]
The protocol conversion unit (304) receives a wireless packet including a packet equivalent to an Async packet whose destination and destination are indicated by the GUID from the wireless I / F processing unit (302), and transmits the destination indicated by the GUID. With reference to the management tables of the internal device information storage unit (309) and the external device information storage unit (308), the source and destination are converted into the destination and source by the node ID, and are converted into Async packets that can be transmitted on the 1394 bus. It has a function, receives an Async packet indicating the transmission destination and transmission source indicated by the node ID from the 1394 I / F processing unit (302), and stores the internal device information storage unit (309) and the external device information storage unit (308). ), A function of referring to the management table and converting the data into a transmission destination and a transmission source based on the GUID to convert the packet into a wireless packet including the packet.
[0036]
The 1394 I / F processing unit (305) has a function of receiving an Async packet from the protocol conversion unit (304) and transmitting the Async packet to one of (306, 307) according to the source of the Async packet. 306, 307), by referring to the management table of the external device information unit (308), returning a response if the information is possible, and transmitting a response to the protocol conversion unit (304) if the response is not possible. Further, a function is provided for controlling the 1394 PHY (306, 307) so as to operate as a repeater when an emulation flag in a management table described later is invalid.
[0037]
The 1394 PHY (306, 307) has all the functions of the existing PHY chip, and has the functions of repeat, cable status recognition, bus initialization, and arbitration. One 1394 PHY has one node. It works to ensure. The 1394 PHY is desirably provided with at least the maximum number of 1394 devices that can be connected to the communication device B (102) on the second 1394 bus (106). In this embodiment, two 1394 PHYs are provided.
[0038]
The external device information storage unit (308) has a function of storing the device configuration on the second 1394 bus (106) and device information such as ConfigROM of the 1394 device on the second 1394 bus (106) in each management table. Prepare. The external device information storage unit (308) desirably includes at least the maximum number of 1394 devices that can be connected to the communication device B (102) on the second 1394 bus (106). In the present embodiment, two are provided. It shall be.
[0039]
The internal device information storage unit (309) has a function of accumulating device information such as ConfigROM of the 1394 device on the first 1394 bus (105) in the device configuration on the first 1394 bus (105) and each management table. Prepare. The management table of the internal information storage unit (309) desirably includes at least the maximum number of 1394 devices that can be connected to the communication device A (101) on the first 1394 bus (105). It shall be prepared.
[0040]
FIG. 4 shows an example of information stored in the management tables of the external device information storage unit (308) and the internal device information storage unit (309).
[0041]
As shown in FIG. 4, the management table contains an emulation flag indicating whether or not the 1394 device is emulated, that is, a node ID, a GUID of the emulated device, and a register of the register as necessary. It has an area for registering addresses and values. In the present embodiment, it is assumed that there is an area for registering a register of ConfigROM (register address is 0xFFFFF000400-) in register address and value.
[0042]
However, as the node ID, the node ID secured by the 1394 PHY (306, 307) of the communication device is stored in the management table of the external device information storage unit (308), and the node ID is stored in the management table of the internal device information storage unit (309). The node ID of the 1394 device connected to the device A (300) via the 1394 bus is registered.
The contents to be registered in the management table described above can be registered if the data is in the 1394 register space.
[0043]
FIG. 5 illustrates a block diagram of the communication device B.
[0044]
The wireless I / F processing unit (502), the device information transmitting / receiving unit (503), the protocol conversion unit (504), the 1394 I / F processing unit (505), the 1394 PHY (506), the external device information storage unit ( 507), the internal device information storage unit (508) has the same function as the function shown in FIG.
[0045]
Next, a flow for recognizing devices on the first 1394 bus (105) and the second 1394 bus (106) will be described with reference to FIGS.
[0046]
First, an operation of recognizing a device on the 1394 bus and recognizing the device in the communication device A when a bus reset occurs in the first 1394 bus (105) in FIG.
[0047]
When a bus reset occurs on the first 1394 bus (105), a bus initialization operation is performed between 1394 PHYs of each 1394 device, and a node ID is assigned to each 1394 device. When the node ID is determined, the communication device A (101) sequentially reads the ConfigROM from the device of the node 0 on the first 1394 bus (105) except for its own device. In this embodiment, the node 1 and the node 2 The device reads the ConfigROM of the 1394 device 1 (100) of the node 0 except for being included in the own device. Since the read ConfigROM usually contains a GUID, the GUID is extracted in advance, and the node ID, the GUID, and the ConfigROM of the device of the node 0 are stored in the management table of the internal device information storage unit (309) in FIG. Register and enable the emulate flag.
[0048]
When the creation of the management table of all the devices, in this embodiment, the node 0 is completed, the communication device B (102) is notified of the change in the device configuration of the first 1394 bus (105) if the device configuration has changed. Send a device configuration change notification.
[0049]
Next, when the communication device B (102) recognizes the device on the second 1394 bus (106) and recognizes the device, similarly, when a bus reset occurs on the second 1394 bus (106), A bus initialization operation is performed between the 1394 PHYs of each device, and a node ID of each device is assigned.
[0050]
When the node ID is determined, the communication device A (102) sequentially reads the ConfigROM from the devices of the node 0 on the second 1394 bus (106) except for the device itself. In this embodiment, since the node 0 is not included in its own device, the Config ROM of the 1394 device 2 (103) and the 1394 device 3 (104) of the nodes 1 and 2 are read. Since the read ConfigROM always contains the GUID, the GUID is extracted in advance and stored in the management table of the internal device information storage unit (508). Write the node ID, GUID, and ConfigROM, and enable the emulation flag. When the management table of the devices of the nodes 1 and 2 on the second 1394 bus (106) indicating all the devices, in this embodiment, the 1394 device 2 and the 1394 device 3, is created, the communication device A (101) gives the second device. If the device configuration of the 1394 bus (106) has changed, a device configuration change notification for notifying the device configuration change is transmitted.
[0051]
Upon receiving the device configuration change notification from the communication device B (102), the communication device A (101) requests device configuration information from the communication device B (102), and stores the internal device storage unit (508) of the communication device B (102). ), The acquired information is registered in the management table of the external device information storage unit (308) of the communication device A (101), and the emulation flag is made valid. In the present embodiment, the management table of the external device information storage unit (308) of the node 1 on the first 1394 bus (105) assigned to the communication device A (101) stores the GUID of the 1394 device 2 (103) and the CofigROM. To enable the emulation flag.
[0052]
The GUID and ConfigROM of the 1394 device 3 (104) are registered in the management table of the external device information storage unit (308) of the node 2 on the first 1394 bus (105) allocated to the communication device A (101), and emulated. Enable the flag.
[0053]
Similarly, upon receiving the device configuration change notification from the communication device A (101), the communication device B (102) requests device configuration information from the communication device A (101) and stores the internal device storage of the communication device A (101). The information of the management table of the communication unit B (102) is obtained, and the obtained information is written in the management table of the external device information storage unit (308) of the communication device B (102), thereby enabling the emulation flag. In the present embodiment, the GUID and ConfigROM of the 1394 device 1 (100) are stored in the management table of the external device information storage unit (507) of the node 0 on the second 1394 bus (106) allocated to the communication device B (102). And enable the emulation flag.
[0054]
Here, in the device information registration method, instead of the sequence example of FIG. 6, the communication device A (101) sets the device on the second 1394 bus (106) to the external device information as in the sequence example of FIG. In the process of registering the device information in the management table of the storage unit (308), the communication device B (102) stores the device information of the 1394 device on the second 1394 bus (106) in the internal device information storage unit (508). After the registration in the table, the communication device B (102) registers the device information registered in the management table of the internal device information storage unit (508) in the external device information storage unit (308) of the communication device A (101). The request may be received and registered in the management table of the external device information storage unit (308) of the communication device A (101).
[0055]
By registering the 1394 devices connected to the 1394 bus as described above, it is possible to recognize all the 1394 devices connected to the communication device A (101) and the communication device B (102) via the 1394 bus. As if there were 1394 devices on the second 1394 bus (106) on the 1394 bus (105), and devices on the first 1394 bus (105) on the second 1394 bus (106). The 1394 device on the first 1394 bus (105) is emulated to the node of the communication device A (101) so that it appears as if it is, and the 1394 device on the second 1394 bus (106) is emulated. A mechanism for emulating the node of the communication device B (102) can be constructed.
[0056]
Next, after the 1394 device is emulated as a communication device node as described above, the first 1394 device (105) and the second 1394 device will be described in order to describe the operation at the communication device node that emulates the 1394 device. FIG. 8 shows an embodiment in which the device (106) transmits an Async packet.
[0057]
Here, the structure of the Async packet to be transmitted is shown in FIG.
[0058]
The meaning of each area in FIG. 8 will be described. destination_ID indicates the node ID of the packet transmission destination. tl indicates a label for recognizing a match between a pair of transactions of a request packet and a response packet. rt indicates information about the retry line method at the time of receiving the busy Acknowledge. tcode indicates a transaction packet type code. pri indicates the priority. source_ID indicates the node ID of the packet transmission source.
[0059]
destination_offset indicates the destination address 48 bits in the register space of the packet destination node. data_dength indicates the byte length of the data payload. extended_tcode indicates an extension type code of the transaction packet. header_CRC indicates a CRC for header information. data indicates a data payload. data_CRC indicates the CRC of the data payload.
[0060]
FIG. 9 shows an example of a sequence for transmitting the above-mentioned Async packet after emulating the 1394 device to the node of the communication device as in the above-described embodiment based on FIGS. The sequence from when the Async packet is transmitted from the 1394 device 1 (100) on the first 1394 bus (105) to the 1394 device 2 (103) on the second 1394 bus (106) is shown.
[0061]
Since the 1394 device 2 (103) is emulated by the node 1 of the communication device A (101) on the first 1394 bus (105) according to the sequence example at the time of transmitting the Async packet in FIG. 9, the 1394 device 1 (100) is emulated. ) Attempts to transmit an Async packet to the node 1, the node 0 being the transmission source of the Async packet, the node 1 being the transmission destination, and a packet having appropriate data set in other areas. The communication device A (101) to which the node 1 belongs receives the Async packet, obtains a GUID by referring to the management table corresponding to the node 0 in the internal device information storage unit (309), and sets the source node ID to the GUID. Convert to The GUID is acquired by referring to the management table corresponding to the node 1 in the external device information storage unit (308), and the node ID of the transmission destination is converted into the GUID. In this embodiment, the transmission source node 0 is converted to the GUID of the 1394 device 1, 0x11111111, and the transmission destination node 1 is converted to the 1394 device 2, the GUID of 0x22222222.
[0062]
FIG. 10 shows an example of an Async packet in which the transmission source and the transmission destination have been converted into GUIDs. This is obtained by adding Destination_GUID and Source_GUID to the head of the received Async packet. Destination_GUID indicates the GUID of the destination 1394 device. Source_GUID indicates the GUID of the transmission source 1394 device. In other words, the Destination_GUID is set to the GUID of the 1394 device 2, 0x222222222, and the Source_GUID is set to the GUID of the 1394 device 1, 0x11111111.
[0063]
Next, the Async packet converted to the GUID is included in the protocol of a wireless packet for wireless transmission to the communication device B (102) and transmitted to the communication device B (102). The communication device B (102) extracts the Async packet from the received wireless packet, refers to the GUID of the transmission source from the management table of the external device information (507) of the communication device B (102), and places it on the second 1394 bus. It converts the emulated 1394 device 1 (100) into a node ID assigned to it and sets it as source_ID. At the same time, the GUID of the transmission destination is referred to from the management table of the internal device information storage unit (509) of the communication device B, and is converted into the node ID assigned to the 1394 device 2 (103) on the second 1394 bus (106). And set it to source_ID. In the present embodiment, in the Async packet of FIG. 7, the destination 1 is set to the node 1 in which the 1394 device 1 (100) is emulated, and the source_ID is set to the node 0 of the 1394 device 2 (103).
[0064]
According to the above-described sequence, the 1394 device 1 (100) transmits an Async packet to the node 1 that emulates the 1394 device 2 (103) to the communication device A (101) on the first 1394 bus (105). The 1394 device 2 (103) receives an Async packet from a node that emulates the 1394 device 1 (100) in the communication device B (102) on the second 1394 bus (106). Async packets can be transmitted without being aware that wireless communication is included between the 1394 bus (105) and the second 1394 bus (106).
[0065]
Next, based on FIGS. 1 to 8, an example of a sequence in FIG. 11 in which the Config ROM of the 1394 device 2 emulated by the node 1 of the communication device A (101) is read from the 1394 device 1 (100) in FIG. 11. Is shown.
[0066]
In this case, in the Async packet shown in FIG. 8, the destination_ID is set to node 1, the source_ID is set to node 0, the tcode is set to READ_REQUEST, which is a read request, and the destination address is set to the register address where the ConfigROM is located (normally 0xFFFFFF000400-). If necessary, set the byte length of the ConfigROM to be read to data_length.
[0067]
Transmission of the READ_REQUEST Async packet set as described above reads out the data in the ConfigROM of the transmission destination.
[0068]
As in the sequence example shown in FIG. 11, when the Async packet of the READ_REQUEST is transmitted from the 1394 device 1 (100) that is the node 0 to the node 1 that emulates the 1394 device 2 (103) of the communication device A (101), the communication is started. The device A (101) receives the Async packet, refers to the management table of the external device information storage unit (308) corresponding to the node 1 that emulates the 1394 device 2 (103), and stores the destination_offset in the management table. When it is confirmed that the register address set in step (1) is registered, an Async packet of READ_RESPONSE is created with reference to the value of the register address and transmitted to the node 1. That is, the communication device A (101) can directly respond to the read request of the ConfigROM of the node 1 of the communication device A (101) emulating the 1394 device 2 (103).
[0069]
By the above-described processing, the Async packet is read from the 1394 device 1 (100) on the first 1394 bus (105) to read the ConfigROM of the 1394 device 2 (103) on the second 1394 bus (106). In response to an Async packet requesting a response without transmitting to the 1394 device 2 (103) of the second 1394 bus (106), the response can be returned, and the communication time can be reduced.
[0070]
In the present embodiment, since a method using the performance of the existing PHY chip is adopted, in which a plurality of 1394 PHYs are provided and only a few 1394 PHY nodes are secured on the 1394 bus, the number of 1394 PHYs is reduced. Although the following equation holds: the number of nodes to be secured, the means for securing a plurality of nodes does not specify increasing the number of 1394 PHYs. For example, even in one 1394 PHY, it is possible to secure a plurality of nodes with one 1394 PHY by transmitting and receiving a plurality of types of self ID packets in a pseudo manner. good.
[0071]
Further, in this embodiment, up to one device having the above-mentioned network configuration, that is, the communication device A (101) is connected to the communication device A (101) by the 1394 bus, and the communication device B (102) is connected to the communication device B (102) by the 1394 bus. This is an example in which up to two devices are assumed, so the number of 1394 PHYs and the number of management tables are limited, but the number of nodes to be secured and the number of management tables need not be limited. However, the number of nodes to be reserved and the number of management tables need to be larger than the number of 1394 devices to be emulated.
[0072]
It is desirable that the number of nodes secured by the communication device is larger than the number of 1394 devices on the remote 1394 bus. However, emulation is performed from among the device elements on the remote 1394 bus acquired through the wireless network. By selecting 1394 devices (which can transmit Async packets), it is also possible to reduce the number of nodes secured by communication devices compared to the number of 1394 devices on a remote 1394 bus.
[0073]
Further, the information arranged in the management table is not limited to the information described in the present embodiment, and data other than the ConfigROM can be arranged, and registers other than the ConfigROM can be directly sent from the emulated node. It is also possible to respond.
[0074]
(Second embodiment)
Next, a second embodiment will be described.
[0075]
Unless otherwise specified, the same system as in the first embodiment has the same function.
[0076]
FIG. 12 shows an example of a communication system in which a wireless network (107) is connected between a first 1394 bus (105) and a second 1394 bus (106).
[0077]
As illustrated in FIG. 12, the 1394 device 1 (1200) is connected to the first 1394 bus (1205), and the communication device A (1201) is connected to the first 1394 bus (1205) and the wireless network (1207). ), The 1394 device 2 (1203) and the 1394 device 3 (1204) are connected to the second 1394 bus (1206), and the communication device B (1202) is connected to the second 1394 bus (1206). And the wireless device A (1201) and the wireless device B (1202) are connected by the wireless network (1207).
[0078]
In the example of FIG. 12, one ConfigROM exists for each of the 1394 device 1 (1200), the 1394 device 2 (1203), and the 1394 device 3 (1204), and the GUID is contained therein.
[0079]
The 1394 device 1 (1200) is assigned a node ID on the first 1394 bus (1205), and the 1394 device 2 (1203) and the 1394 device 3 (1204) have node IDs on the second 1394 bus (1206). Assigned. The 1394 device 1 (1200) has a GUID of 0x11111111 and a node ID of 0 on the first 1394 bus (1205) (hereinafter, a device with a node ID of 0 is abbreviated as a node 0, and a device with a node ID of 1 or 2 is also used). Similarly, the node 1 and the node 2 are omitted), the 1394 device 2 (1203) has the GUID of 0x222222222, and the node 1 and the 1394 device 3 (1204) on the second 1394 bus (1206) have the GUID of 0x33333333. It is assumed that it is allocated to node 2 on the 1394 bus (1206). The communication device A (1201) has two nodes, Node 1 and Node 2, for emulating the 1394 device on the second 1394 bus (1206), and the function of the communication device A (1201) itself. It is assumed that the controlling node 3 has been allocated, and the node 3 controlling the function of the communication device A (1201) itself has a GUID of 0xAAAAAAAA. Similarly, for the communication device B, a node 1 for emulating the 1394 device on the first 1394 bus (1205) is allocated and obtained.
[0080]
In the 1394 bus, the node ID is variable, and there is a possibility that the node ID changes due to a bus reset, an increase or decrease in the number of devices, and the like. Here, an example at the time when each of the above 1394 devices is assigned to the node ID is described. Is shown. When the node IDs are different, the node IDs may be replaced and considered.
[0081]
The wireless network (1207) between the wireless device A (1200) and the wireless device B (1202) transmits data according to a protocol such as IEEE802.11a.
[0082]
Next, FIG. 13 illustrates an outline of an internal configuration of the communication device A (1201) and the communication device B (1202). This indicates that the communication device A (1201) has two emulation nodes, and the communication device B (1202) has one emulation node, and a management table is allocated to each emulation node. This emulated node operates as a repeater. In addition, it indicates that the communication device A (1201) has one node for indicating its own node and one management table is also allocated.
[0083]
Next, FIG. 14 shows a block diagram of a communication device A (1201) having itself as a node.
[0084]
This block diagram has the same functions as the block diagram of the communication device A (300) of FIG. 3 described in the first embodiment, and a 1394 PHY (1408) for securing a node of the communication device A (1400) itself. ), A management table (1410-b) in the internal device information storage unit (1410) for registering information of the communication device A (1400) itself, a 1394 register (1412) of the communication device's own node, and a communication device. A (1400) has a device control unit (1411) for controlling its own function, and a function is added to the 1394 I / F (1405).
[0085]
The 1394 PHY (1408) has the function of the conventional PHY chip as shown in the first embodiment, and is used to secure the node of the communication device A (1400) itself on the 1394 bus.
[0086]
The management table (1410-b) is used to add the communication device A (1400) itself to a component on the first 1394 bus (1205).
[0087]
The 1394 register (1411) stores the 1394 register of the node representing the communication device A (1400) itself. A 1394 register value such as a Config ROM is stored in the 1394 register, and reading, writing, and the like are performed according to an Async packet from the 1394 I / F processing unit (1405).
[0088]
The device control (1412) receives an Async packet from an arbitrary 1394 device on the first 1394 bus (1205) for a node representing the communication device A (1400) and operates the 1394 register. And control corresponding to the operation. For example, in the case of an AV / C command, an Async packet requesting to write command data in a register address area called an AVC_COMMAND register of the 1394 register is received, and the device of the node is controlled according to the data. An Async packet to be written into an area called an AVC_RESPONSE register of the node that has transmitted the AV / C command is transmitted to the node that has transmitted the AV / C command.
[0089]
At this time, the device control unit (1412) reads the contents of the AVC_COMMAND register of the 1394 register, performs predetermined control, and transmits an Async packet that writes the response to the AVC_RESPONE register of the 1394 register that transmitted the AV / C command. 1394 I / F.
[0090]
In addition to the function of the first embodiment, when the destination node of the received Async packet is the node of the communication device A (1400) itself, the 1394 I / F stores the content of the Async packet in the 1394 register. Request read and write processing. In addition, in response to a request for transmission of an Async packet from the device control unit, an Async packet is transmitted on the 1394 bus.
[0091]
Having the node of the communication device itself as described above is convenient when operating the communication device itself. For example, an AV / C command reads information in a management table of an internal device information storage unit and an external device information storage unit of a communication device, selects information to be registered in the management table, and a device to be registered in the management table. Or you can choose. Also, operations that depend on the capability of the wireless I / F, such as switching on / off the power of the wireless device, enabling / disabling the wireless I / F function, and communication devices connected via a wireless network And various operations and statuses can be obtained.
[0092]
In this embodiment, an example is shown in which only the communication device A has its own node, but both the communication device A and the communication device B may have their own nodes.
[0093]
【The invention's effect】
By installing the communication device, a plurality of 1394 devices on different 1394 buses connected to a network of another protocol can be changed from existing 1394 devices that do not support bridge with another protocol on the 1394 bus. Devices on the same 1394 bus can be operated in a conventional manner.
[Brief description of the drawings]
FIG. 1 is an example of a communication system.
FIG. 2 is a schematic example of a communication device A and a communication device B;
FIG. 3 is a block diagram of a communication device A.
FIG. 4 is an example of a management table.
FIG. 5 is a block diagram of a communication device B.
FIG. 6 is a first example of a sequence of device recognition and management table registration.
FIG. 7 is a second example of the sequence of device recognition and management table registration.
FIG. 8 shows an Async packet.
FIG. 9 is a sequence example at the time of transmitting an Async packet.
FIG. 10 is an example of an Async packet to which a GUID is added.
FIG. 11 is a sequence example of a READ process of the ConfigROM.
FIG. 12 is an example of a communication system including a communication device having itself as a node.
FIG. 13 is a schematic example of a communication device A and a communication device B each having their own node.
FIG. 14 is a block diagram of a communication device A having itself as a node.
[Explanation of symbols]
100: 1394 equipment 1
101: Communication equipment A
102: Communication equipment B
103: 1394 equipment 2
104: 1394 equipment 3
105: first 1394 bus
106: second 1394 bus
107: Wireless network
300: Wireless device A
301: Wireless I / F
302: Wireless I / F processing unit
303: Device information transmission / reception unit
304: Protocol conversion unit
305: 1394 I / F processing unit
306: 1394PHY
307: 1394PHY
308: External device information storage unit
309: Internal device information storage unit
310: IEEE 1394 bus
500: Wireless device B
501: Wireless I / F
502: Wireless I / F processing unit
503: Device information transmission / reception unit
504: Protocol conversion unit
505: 1394 I / F processing unit
506: 1394PHY
507: External device information storage unit
508: Internal device information storage unit
509: IEEE 1394 bus
1200: 1394 equipment 1
1201: Communication device A
1202: Communication equipment B
1203: 1394 equipment 2
1204: 1394 equipment 3
1205: First 1394 bus
1206: Second 1394 bus
1207: Wireless network
1400: Wireless device A
1401: Wireless I / F
1402: wireless I / F processing unit
1403: Device information transmission / reception unit
1404: Protocol conversion unit
1405: 1394 I / F processing unit
1406, 1407, 1408: 1394PHY
1409: External device information storage unit
1409-a, 1409-b: management table
1410: Internal device information storage unit
1410-a, 1210-b: management table
1411: 1394 register
1412: Device control unit
1413: IEEE 1394 bus

Claims (6)

In a communication device in which a first IEEE 1394 (hereinafter abbreviated as 1394) bus and a second 1394 bus are connected by a third network,
1394 interface means connected to the first 1394 bus;
Third interface means connected to a third network;
Means for recognizing each node on the first 1394 bus as a component on the first 1394 bus, means for disclosing the component through a third interface,
Third interface means connected to the third network and 1394 interface means connected to the second 1394 bus;
Means for recognizing each node on the second 1394 bus as a component on the second 1394 bus;
Acquiring a component on the second 1394 bus through the third interface unit from a communication device having a unit that discloses the component unit recognized by the recognizing unit through a third interface unit; A communication device comprising means for emulating a node on a bus as a node on a first 1394 bus. The communication device according to claim 1,
A communication device having a function of emulating a plurality of nodes on a second 1394 bus obtained through the third interface means as a plurality of nodes on a first 1394 bus. The communication device according to claim 1,
A communication device characterized in that components on the second 1394 bus obtained through the third interface means include device information of each node (GUID, register address and value of each device, subunit configuration, etc.). The communication device according to claim 1,
When an Asynchronous packet (hereinafter abbreviated as Async packet) is transmitted from an arbitrary node on the first 1394 bus to a node emulated by a communication device, the node transmits the Async packet to the node on the second 1394 bus. A communication device having a function of transmitting an equivalent Async packet. The communication device according to claim 1,
A communication device wherein, when an Async packet is transmitted from an arbitrary node on the first 1394 bus to an emulated node, a response is created and returned in the emulated node. The communication device according to claim 1,
A communication device having its own function as a node in addition to the emulated node on the second 1394 bus.

Images