JP2003008610A - Information processor and method, storage medium, and program for information processing - Google Patents

Abstract

PROBLEM TO BE SOLVED: To control devices connected to a 1394 network from a UPnP control point. SOLUTION: A UPnP control point 1 is connected to an IEEE 802 network 11, and 1394 devices 3 and 4 are connected to an IEEE 1394 network 12. The networks 11 and 12 are connected via a UPnP device 2 which functions as a bridge. The UPnP device 2 converts the packets sent from the UPnP control point 1 and forwards it to the 1394 device 3 via the network 12.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus and method, a recording medium, and an arrangement program.
Information processing apparatus and method, and recording medium enabling device connected to one of a first network based on 802 and a second network based on IEEE 1394 to control a device connected to the other , About the program.

[0002]

2. Description of the Related Art Recently, the IEEE (Institute of Electrical
and Electronics Engineers) Networks using 1394 high-speed serial buses (hereinafter simply referred to as IEEE 1394 networks) have become popular. By connecting an audio device and a video device to this IEEE 1394 network, each device can control another device using an AV / C command.

On the other hand, the IEEE 802 network is also widespread. This IEEE 802 is a network mainly for connecting personal computers to each other, and UPnP (Un
Each personal computer can control other personal computers based on the protocol of iversal Plag and Play).

[0004]

[Problems to be Solved by the Invention] However, this IE
The EE1394 network and the IEEE802 network are independent of each other, and are connected to the IEEE802 network (hereinafter referred to as UPnP devices).
Has a problem that it is not possible to control a device connected to the IEEE 1394 network (hereinafter referred to as a 1394 device).

The present invention has been made in view of such circumstances, and makes it possible for a UPnP device to control a 1394 device.

[0006]

An information processing apparatus according to the present invention includes a capturing means for capturing a first packet from a first network, and a first packet captured by the capturing means for a second network. Conversion means for converting into a second packet and second conversion means converted by the conversion means
And a second service means for performing service to an IEEE 1394 node, the converting means including a transmitting means for transmitting the packet to the second network, and the converting means for managing the information on the IEEE 1394 bus. It is characterized by including.

The converting means includes a first service means,
The second service means can be in one root device.

The converting means may have the first service means in the first root device and the second service means in the second root device which is different for each device.

The conversion means includes a first service means,
It is possible to have a different second service means for each device in one root device.

The converting means converts the first service means into one.
It is possible to have an embedded device that is included in one root device and that has a second service means that is different for each device, in one root device.

According to the information processing method of the present invention, a capturing step for capturing the first packet from the first network, and the first packet captured by the processing of the capturing step for converting the first packet into the second packet of the second network. And a transmission step of transmitting the second packet converted by the processing of the conversion step to the second network.
A first service step of managing the information of the bus of 4;
Second to execute service for IEEE 1394 node
And a service step of.

The recording medium program of the present invention stores the first packet from the first network in the capturing step, and the first packet captured by the processing of the capturing step in the second packet of the second network. A conversion step of converting the packet into a packet; and a transmission step of transmitting the second packet converted by the processing of the conversion step to a second network, the conversion step comprising:
It is characterized by including a first service step of managing information on the EE1394 bus and a second service step of executing a service to an IEEE1394 node.

The program of the present invention converts a first packet captured by the capturing step of capturing the first packet from the first network and the second packet of the second network into the second packet of the second network. And a transmitting step of transmitting the second packet converted by the processing of the converting step to the second network.
A first service step of managing the information of the bus of 4;
Second to execute service for IEEE 1394 node
Service steps of.

In the information processing apparatus and method, the recording medium, and the program of the present invention, the first service that manages the information of the IEEE 1394 bus and the second service that executes the service to the IEEE 1394 node are the first service. Is executed in the information processing device connected to the second network and the second network.

[0015]

1 shows the configuration of a network system to which the present invention is applied. In this configuration, the UPnP control point 1 is connected to the IEEE802 network 11. 1394 devices 3 and 4 are connected to the IEEE 1394 network 12. IE
The EE802 network 11 and the IEEE 1394 network 12 are connected to the UPnP device (1394 proxy) 2, respectively.

FIG. 2 shows a configuration example of the UPnP device 2. In FIG. 2, CPU (Central Processing Unit)
Reference numeral 21 denotes a program stored in a ROM (Read Only Memory) 22, or RAM (Random Acce
Various kinds of processing are executed according to the program loaded in the ss Memory) 23. The RAM 23 also appropriately stores data necessary for the CPU 21 to execute various processes.

The CPU 21, ROM 22 and RAM 23 are connected to each other via a bus 24. An input / output interface 25 is also connected to the bus 24.

The input / output interface 25 includes an input unit 26 including a keyboard and a mouse, a display including a CRT and an LCD, an output unit 27 including a speaker, and a storage unit 28 including a hard disk.
A communication unit 29 including a modem and a terminal adapter is connected. The communication unit 29 performs communication processing via the IEEE 802 network 11 or the IEEE 1394 network 12.

A drive 30 is connected to the input / output interface 25 as required, and a magnetic disk 41,
The optical disc 42, the magneto-optical disc 43, the semiconductor memory 44, or the like is appropriately mounted, and the computer program read from them is installed in the storage unit 28 as necessary.

UPnP devices (UPnP control point 1 and UPnP device 2 in the example of FIG. 1) are mainly used for addressing and discovery.
y), Description (Decription), Control (Control), Eventing (Eventing), and Presentation (Presentation).

For addressing, each UPnP device uses IEEE80
2 It is a function to acquire an address on the network 11, and DHCP (Dynamic Host Configuration Protocol)
l) or AutoIP is used.

The discovery is performed after the addressing, whereby the UPnP control point 1 can discover the target device to be controlled.
The protocol used here is SSDP (Simple Serivic
e Discovery Protocol). Each device is IEEE802
When connected to the network 11, a message for notifying a device or service included in itself is sent to the IEEE8
02 multicast on network 11 (especially
Send a packet without specifying the other party). The UPnP control point 1 receives this multicast message, and
Then, it is possible to know what kind of device is connected.

On the contrary, the UPnP control point 1 can also check the device currently connected to the IEEE802 network 11. At this time, the UPnP control point 1 multicasts the search command on the IEEE 802 network 11 using the device or service to be discovered as a keyword. Each device connected to the IEEE 802 network 11 unicasts a response to the search command if it meets the conditions specified in the multicast search command (by designating the other side, Send a packet). As a result, UPnP control point 1 becomes IE
A device connected to the EE802 network 11 can be detected.

Each device also broadcasts in advance when it is disconnected from the IEEE 802 network 11.

SS output by the device to be controlled discovered by UPnP control point 1 by discovery
The device description (Device Description) is included in the DP packet.
The URL (Uniform Resource Locator) of Description) is described. UPnP control point 1 is
By accessing the URL, more detailed device information of the device can be obtained from the device description. This device information includes icon information,
The model name, producer name, product name, etc. are included.

The device information describes the service information of the device, and the service description (Service Discription) describing detailed information of the service is also the URL described in the service information. You can follow from.

The UPnP control point 1 can know the method of accessing the target from these device information (Device Description) and service information (Service Description).

Further, the device description includes
The Presentation URL described later is also described.

Device Description and Service Descri
The ption is expressed in XML (Extensible Markup Language).

Control is broadly classified into two types: action and query. Action is S
The UPnP control point 1 can operate the target by invoking the action performed by the method specified in the action information of the ervice description.

On the other hand, Query is the st of Service Description
Used to retrieve the value of ateVariable. stateVa
The value of riable represents the state of the device.

In Control, SOAP (Simple Object Acces
s Protocol) is used. XML is used as the expression language.

Eventing is the stateVar
It is used to notify the UPnP control point 1 from the target when the value of iable is changed. UPnP control point 1 is Service De
By parsing the scription, the variable held by the target can be known from stateVariable. UPnP control point 1 is Subscrip against the target
By outputting the option, among the variables, send
For variables that have Events set to yes, you can get notifications from the target when the variables change. In Eventing, GENA (General Event Notification
Architecture) transport protocol is used. XML is used as the expression language.

The presentation is
It is used to provide the user with control means using a user interface (UI). Device Descrip
The Presentation Page described in HTML (Hyper Text Markup Language) can be obtained by accessing the Presentation URL described in Option. The function allows the target to prepare an application.

The UPnP device (1394 proxy) 2 is
It functions as a bridge between the IEEE 802 network 11 and the IEEE 1394 network 12, and internally has a device model shown in FIG. The device model of this example is composed of one root device 61, and this root device 61 is an IEEE 1394 proxy service 71.
IEEE 1394 node service
ice) 72.

The IEEE 1394 proxy service (hereinafter, simply referred to as a proxy service) 71 is an IEEE 1394 proxy service.
Bus reset occurrence of network 12, bus ID, number of nodes, bus manager, node unique ID (NUID) of isochronous resource manager, gap count (Gap Count), self ID packet (Self ID packet)
Manage such.

The IEEE 1394 node service (hereinafter, simply referred to as a node service) 72 is a Link-On packet, P
It exchanges Phy packets including hy Configuration packets, and asynchronous packets.

FIG. 4 shows the structure of this asynchronous packet.

Asynchronous communication is used for asynchronous data communication. In this Asynchronous communication,
It is guaranteed that the packet is reliably transmitted to the partner node, and the transmission delay time is not guaranteed. The sending node sends the header information and the actual data to the designated node, and the receiving node sends back an Acknowledge packet to notify the other party that the packet has been received. However, when a broadcast packet that does not specify the destination node is received, the Acknowledge packet is not returned.

At the beginning of the 1394 packet header, dest
ination_ID (Destination identifier) is placed. This represents the node_ID of the packet destination.

Tl (Transaction label) is a label for recognizing the matching of a pair of transactions of a request packet and a response packet. request packet t
l is also used as tl in the response packet.

Rt (Retry code) is busy Acknowledge
Represents information about the retry method when is received.

Tcode (Transaction code) represents the type code of the transaction packet. That is, read / wri
It shows whether it is te / lock or request / response.

In fair arbitration, pri (Priority) is set to all 0 (excluding cycle start).

The source_ID (Source indentifier) represents the node_ID of the packet transmission source.

Next to source_ID, packet-type-specifi
c information is placed, and if necessary, pac
Ket-type-specific data is placed. At the end of the 1394 packet header, the CRC for the above header information is had.
Inserted as er_CRC.

A data block is arranged following the 1394 packet header. Data blocks can be
It consists of a data block quadlet and data_CRC as a CRC for data information.

Next, referring to the flowchart of FIG.
The UPnP control point 1 connected to the IEEE802 network 11 is the IEEE1394 network 12
A process for controlling a device connected to the will be described.

In step S1, the UPnP control point 1 informs the proxy service 71 constituting the 1394 proxy device 2 of the IEEE 1394 network 1
To notify you when there is a change in 2,
Subscribe (SUBSCRIBE). In step S11, when the proxy service 71 receives this subscription, it executes the corresponding process.

For example, the 1394 device 3 is now in step S
If it is assumed that the 1394 device 3 is connected to the IEEE 1394 network 12 in 31, a bus reset occurs in the 1394 device 3 in step S32, and similarly, in step S21, the node service 72 of the root device 61,
Bus reset occurs. At this time, node service 7
2 notifies the proxy service 71 of the occurrence of the bus reset in step S22.

The proxy service 71 uses step S12.
In step S13, when the notification from the node service 72 is detected, based on the subscription from the UPnP control point 1 acquired in step S11, the 1394 device 3 connects to the UPnP control point 1 in step S13 and connects to the IEEE 1394 network 12. Notify that it was done.

In step S 2, the UPnP control point 1 receives the notification from the proxy service 71. As a result, UPnP control point 1 becomes IE
It is possible to know that the 1394 device 3 is connected to the EE1394 network 12.

Therefore, in step S3, the UPnP control point 1 uses as to read the information recorded at the predetermined address of the register of the 1394 device 3.
Invoke an action request packet based on SOAP corresponding to a ynchronous read request command.

FIG. 6 shows an example of the request message transferred from the UPnP control point 1 to the node service 72 at this time. The UPnP control point 1 is a 1394 Nodes Servic shown in FIG. 14 described later.
Generate this request message by referring to eDescription.

The number "5" included in the Transaction returns a response in response to this request. Therefore, the transaction label as a label for recognizing which request the response corresponds to. It represents.

The nuid included in Body represents the node unique ID (NUID) of the transmission partner of this message. In the case of the present example, it represents the NUID of the 1394 device 3. This NUID "080
“0460000000000000” is described in the notification obtained from the proxy service 71 in the process of step S2. This NUID is the node ID of the 1394 device 3 based on the correspondence table of the node service 72.
(In the case of the example in FIG. 7, it is converted into “ffc0” and stored in the destination_ID of the packet in FIG. 7.

AsyncRequest represents the type of command that the UPnP control point 1 requests the node service 72 to generate. That is, in this example, generation of an asynchronous read request command is requested.

[000] on the MSB side included in asyncRequest
001400000 "(hexadecimal number) is the read request for data shown in FIG. 7 generated by the node service 72.
Transaction label of Figure 7 in quadlet packet
tl, retry code rt, transaction code tcod
e, and priority Pri.

"Fffff0000404" on the LSB side is shown in FIG.
Corresponding to destination_offset of. That is, this value is
The UPnP control point 1 represents the address of the register of the 1394 device 3 to be read.

In the source_ID field of FIG. 7,
The node ID of the node service 72 (in the example of FIG. 7, “ff
c1 ”) is described.

Since all of these values are represented by text, it is possible to describe any type of IEEE 1394 packet.

Returning to FIG. 5, when the node service 72 receives the invoke of the Action shown in FIG. 6 in step S23, it responds to it in step S24 by aysnchronous read requ as shown in FIG.
est packet is generated and IEEE 1394 network 1
2 to the 1394 device 3 via. At this time, the node service 72 uses the request shown in FIG.
The correspondence relationship of the request packet shown in is stored in the correspondence table.

In step S33, the 1394 device 3 receives the asynchronous signal transmitted from the node device 72.
When a us read request packet is received, the processing corresponding to that request (in this case, reading the register)
To execute. In step S34, the 1394 device 3
Is the r as shown in FIG. 8 corresponding to the request packet.
An esponse packet is generated and transmitted to the node service 72.

As shown in FIG. 8, the value of the transaction code tcode is the value "6" representing the respond.

The values of destination_ID and source_ID are shown in FIG.
The value in the read request for data quadlet packet of is used as it is. quadlet data has dest
The data read from the address of ination_offset is arranged.

When the node service 72 receives the response packet transmitted from the 1394 device 3 in step S25, it returns Re as an action based on the SOAP protocol as shown in FIG. 9 in step S26.
Generate sponse and send to UPnP control point 1.

Transact shown in FIG. 9 based on the correspondence table.
The value “5” shown in ion is the Act that pairs with the Action in FIG.
Transaction in FIG. 6 to indicate that it is an ion
Is set to "5" (same value) corresponding to the value "5" of.

The Body of FIG. 9 has 1394 asychr.
“AsyncResponse” is described to indicate that it corresponds to the onous read response. And
There are "000001000000000000
Data of “00000133333934” is described. This data is the value described in the quadlet data of FIG. 8 and is the value read from the offset address of the 1394 device 3. In step S4, the UPnP control point 1 reads this value.

In order to execute the above processing, the root device 61 of the device model included in the 1394 proxy 2 shown in FIG.
The vice description has a vice description, and the proxy service 71 is a 1394 Proxy Service Descri shown in FIGS. 11 and 12.
The node service 72 having a ption is shown in FIG. 13 and FIG.
1394 Nodes Service Description shown in FIG.

DeviceType “urn: sony-cor” in FIG.
p: device: 1394ProxyDevice: 1 '' means the device type is Prox
y Device is displayed. FriendlyName "prox
“Y for IEEE1394” represents the friendly name of the root device 61.

UDN "nuid: upnp-1394proxy-root-08004600
“00000000” represents a unique number of the root device 61.

This Device Description has two servs.
ice is described. One is that serviceType is "urn: so
ny-corp: service: 1394ProxyService: 1 "and the other one has serviceType" urn: sony-corp: s
ervice: 1394NodeService: 1 ”. That is, the former is a service corresponding to the proxy service 71 of FIG. 3, and the latter is a node service 72 of FIG.
It is a service corresponding to.

SCPD URL of the former service "./scpd/proxyS
cpd.xml "is the Proxy Ser that the proxy service 71 has.
URL of vice description (specifically, Figure 11 and Figure 12
URL of Proxy Service Description shown in).

The SCPD URL of the latter service "./scpd-
nodeScpd.xml "is Nodes included in the node service 72.
The URL of Service Description (specifically, 1394 Nodes Service Description shown in FIGS. 13 and 14) is shown.

1394 Proxy Service of FIGS. 11 and 12.
The action in the Description represents various actions, and the action named “busRest” represents an action that causes a bus reset. Action with the name "getNodeNum"
Represents an action for acquiring the number of nodes on the 1394 bus. The action named “getIrmId” represents an action for acquiring the NUID of the IRM (Isochronous Resource Manager) on the 1394 bus.

The action named “getBmId” is 1394.
Represents the action to get the NUID of the bus manager on the bus. The action named “getGapCount” represents an action for acquiring the Gap Count on the 1394 bus.

The action of the name "getSelfIdPacket" is
It represents the action of acquiring the SelfID packet that has flowed on the 1394 bus.

The action named "getNodeNume" has "n
An argument whose direction is “outNum” and whose direction is “out” (an argument output from another device and transferred) is specified. Then, in this argument “nodeNum”, the related regulation is described in the serviceStateTable. That is, "nod
"eNum" describes that a notification is sent to a device that is subscribing. In addition, when the state variable changes, it is described that "the data type is an argument output as" i1 ".

In the action of "getIrmId", the argument of which the "direction" of the name "nuid" is "out" is defined. In the action of "getGapCount", the argument of the direction of "gapCount" whose direction is "out" is specified, and "getSelfI"
The action of the name "dPacket" defines the argument of the direction "out" of the name "selfIdPacket". These arguments are SUBCRIBE even if the state variables change.
It is described that the notification is not sent to the device that is operating. In addition, it is described that the data is output from each device as "bin.hex".

1394 Nodes Service of FIGS. 13 and 14
In the description, "asyncReqSend", "phyEPacketSen"
The action of "d" and "LinkOnPacketSend" is specified.

The action named “asyncReqSend” is asyn
Represents an action that sends a chronous packet.

For this action, di with the name "nuid" is
rection is an argument of "in" (output to other devices,
Arguments input to other devices) are specified. And the data type of this argument "nuid" is "bin.hex"
It is said that.

In the action of "asyncReqSend",
The argument whose direction of "asyncReqest" is "in" and the argument whose direction of "asyncResponse" is "out" are respectively defined.

Similarly, direct of the name "asyncRequest"
ion is an argument of "in" and dire with the name of "asyncResponse"
The data format of the argument whose ction is “out” is specified as “bin.hex”.

The action named “phyPacketSend” is Phy.
Represents the action of sending a packet. This command defines an argument whose direction is "in" with the name "phyPacket" and an argument whose direction is "out" with the name "phyPacketResp". These arguments are related variables "phyP
“Acket” and its data type is “ui4”.

The action with the name "LinkOnPacketSend" is
Represents an action that sends a LinkOn packet. This action has an argument whose direction of "phyId" is "in". The data type of this argument is “i1”.

FIG. 15, FIG. 16, and FIG.
4 Proxy Device Description, 1394 Proxy Service
Description, and 1394 Nodes Service Descrip
represents another example of tion.

In FIG. 15, the proxy service 71
ServiceType corresponding to `` urn: sony-corp: service: 1394P
service of "roxyService: 1" and serviceType corresponding to the node service 72 "urn: sony-corp: service: 1394NodeS
ervice: 1 ”service is specified. In the SCPD URL of the former service, the 1394 Proxy ServiceDes of FIG. 16 is used.
The URL of cription is described, and the latter SCPD URL is shown in Fig. 17.
URL of the 1394 Node Service Description is described.

In FIG. 16, "getNodeNu" is an action for obtaining the number of nodes on the IEEE 1394 network 12.
m ”and“ busRest ”, which is the action that causes a bus reset
Is described.

In FIG. 17, the action named “asynchTr” for performing Async Transaction is described. This action is called "destinationNuid", "requestPacke
It has three arguments, "t" and "responsePacket". The former two directions are "in" and the last argument d
The irection is "out".

In the above, as shown in FIG.
Although one root device 61 is made to hold the 1394 proxy service 71 and the node service 72, for example, as shown in FIG. 18, while making the root device 61-1 hold the proxy service 71, the IEEE1394 It is also possible to define a service for each individual node of each root device. In the example of FIG. 18, the root device (root dev
ice) 61-2 holds the node service 72-1 and the root device 61-3 holds the node service 72-2.
Is retained.

19 and 20 are the root device of FIG.
1394 Proxy Device included in 61-1 to 61-3
FIG. 21 shows an example of the Description, and FIG. 21 shows the 1394 Proxy Service Descr held by the proxy service 71 in FIG.
FIG. 22 shows an example of iption, and FIG. 22 shows a 1394 Node Service Des included in the node services 72-1 and 72-2 of FIG.
Here is an example of cription.

In FIG. 19 and FIG. 20, the root device
3 deviceTypes corresponding to 61-1 to 61-3
`` Urn: schemas-upnp-org: device: 1394ProxyDevice:
1 ”,“ urn: sony-corp: device: 1394NodeDevice: 1 ”, and“ urn: sony-corp: device: 1394NodeDevice: 1 ”are described.

The first deviceType SCPD URL is shown in FIG.
The URL of the 1394 Proxy Service Description of 1 is described, and the SCPD URLs of the latter two deviceTypes include 1 of FIG.
URL of 394node Service Description is described.

In FIG. 21, a variable "nodeNum" which is generated when a change in state occurs is defined.

In FIG. 22, an action named "asynchTr" for performing Async Transaction is described. This action uses "requestPacket" and "responsePacke"
It holds two arguments of "t". The former direction is "in" and the latter direction is "out".

FIG. 23 shows still another configuration example of the device model. In this example, one root device6
1, the proxy service 71 and the node service 72-
1, 72-2 are held. That is, in the example of FIG. 3, the node service is provided commonly to a plurality of nodes, whereas in this example, the node service is provided independently for each node.

FIG. 24 shows the root devic in the example of FIG.
25 shows the configuration of the 1394 Proxy Device Description included in the e61, FIG. 25 shows a configuration example of the 1394 Proxy Service Description held by the proxy service 71 of FIG. 23, and FIG. 26 shows the node service 72-1 of FIG.
72-2 has 1394 Node Service Description
A configuration example of is shown.

In FIG. 24, three serviceTypes "u
rn: sony-corp: service: 1394ProxyService: 1 '', `` urn: s
ony-corp: service: 1394NodeService: 1 '', `` urn: sony-c
"orp: service: 1394NodeService: 1" is described.

The first serviceType SCPD URL is shown in FIG.
URL of the 1394 Proxy Service Descripiton is described, and the URL of the 1394 Node Service Description of FIG. 26 is described in the SCPD URL corresponding to the latter two serviceTypes.

In FIG. 25, the variable "nodeNum" is defined.

In FIG. 26, the action of "asynchTr" for performing async Transaction is defined.

FIG. 27 shows still another configuration example of the device model. In this configuration example, root devic
The proxy service 71 is held in e61. In addition to the node services 72-1 and 72-2 provided for each node, embedded devices 81-1 and 81-1 held in the root device 61 are also provided.
81-2, respectively.

28 and 29 show root d in FIG. 27.
evice61 holds 1394 Proxy Device Descripti
FIG. 30 shows a configuration example of on, and FIG. 30 shows a 1394 Proxy Service Description held by the proxy service 71 in FIG.
FIG. 31 shows a configuration example of the node service 7 of FIG.
2-1 and 72-2 have 1394 Node Service Desc
A configuration example of ription is shown.

In FIG. 28 and FIG. 29, the proxy service 71, the node service 72-1 and the node service 7
2-2, the corresponding deviceType "urn: sony-cor"
p: device: 1394ProxyDevice: 1 '', `` urn: sony-corp: devi
ce: 1394NodeDevice: 1 ", as well as" urn: sony-corp: devic
e: 1394NodeDevice: 1 "is specified for each. The SUPD URL corresponding to the first serviceType is 13 in FIG.
The URL of the 94 Proxy Service Description is described, and the SCPD URL corresponding to the latter two deviceType is 1 in FIG.
394 Node Sevice Description URL is described.

In FIG. 30, the variable "nodeNum" is defined.

In FIG. 31, the action of "asynchTr" for performing async Transaction is described.

Next, FIGS. 3, 18, 23 and 27.
Compare the device models shown in.

In the example of FIG. 3, one root device
61, a proxy service 71 and a node device 72
Are defined one by one.

In the example of FIG. 18, the proxy service 71 is defined in one root device 61-1 and the node services 72-1 and 72-2 for the individual nodes on 1394 are root devices 61-2 and 61. −
It is defined every three.

In the example of FIG. 23, the proxy service 71 is provided in one root device 61, and a node service is provided corresponding to each node. These node services 72-1 and 72-2 are Like the proxy service 71, it is held in one root device 61.

In the example of FIG. 27, all the nodes on 1394 are embedded devices 81-1 of root device 61,
81-2.

FIG. 32 shows a comparison result of the characteristics of the device models of FIGS. 3, 18, 23, and 27. 32, type A, type B, type C, and type D are shown in FIG. 3, FIG. 18, and FIG.
3 or the device model of FIG. 27.

Comparing types A to D,
It can be seen that the SSDP packet volumes are very different.
That is, when there is one root device, the number of SSDP is three.
It becomes + 2d + k. Here, d means the number of embedded devices, and k means the number of service types. Therefore, 13
When the number of nodes on the 94 network 12 is N,
The amount of SSDP packets is 5 for type A, type B
Is 4 + 4N, type C is 4 + N, type D
At that time, it becomes 4 + 3N. In particular, in the case of type B (FIG. 18) and type D (FIG. 27), the number of packets that is several times the number of nodes will flow. Therefore, from the viewpoint of network traffic, the type A (FIG. 3) example in which the amount of SSDP packets is small is desirable.

The notification of the change of the bus configuration is made by GENA in the case of type A, and SSDP in the case of types B, C, D.
Done by.

The units of the presentation URL are such that type A and type C are bus units, and type B and type D are node units. Type B (FIG. 18) and type D (FIG. 27) that can have a URL for each node are easy to understand, but regarding type A (FIG. 3) and type C (FIG. 23), the proxy service 71 is By preparing something like a link page for a node, it is considered that the corresponding function can be realized.

In the case of type A, the NOTIFY notification unit is
It is a bus unit, and in the case of types B, C and D, it is a node unit.

In summary, the example of type A (FIG. 3) is considered to be optimum.

The series of processes described above can be executed by hardware, but can also be executed by software. When a series of processes is executed by software, a program that constitutes the software executes a variety of functions by installing a computer in which dedicated hardware is installed or various programs. It is installed from a network or a recording medium into a general-purpose personal computer or the like capable of performing the above.

This recording medium, as shown in FIG. 2, is a magnetic disk 4 on which a program is recorded, which is distributed in order to provide the program to the user separately from the apparatus main body.
1 (including floppy disk), optical disk 42 (CD-R
OM (Compact Disk-Read Only Memory), DVD (Digital Versa
tile disk)), magneto-optical disk 43 (MD (Mini
(Including -Disk)), or package media including semiconductor memory 44, etc.
A ROM 22 in which a program is recorded, which is provided to the user in a state of being pre-installed in the apparatus main body, and a storage unit 2
It is composed of a hard disk and the like included in 8.

In the present specification, the steps for writing the program recorded on the recording medium are not limited to the processing performed in time series according to the order described, but may not necessarily be performed in time series. It also includes processing executed in parallel or individually.

In this specification, the system means
It represents the entire apparatus composed of a plurality of devices.

[0123]

As described above, according to the information processing apparatus and method, recording medium, and program of the present invention, 1394
Since the first service that manages the information of the bus of and the second service that executes the service to the node are executed when converting the first packet into the second packet, it is possible to easily and surely. The device connected to the second network can be controlled by the device connected to the first network.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a network system to which the present invention is applied.

FIG. 2 is a block diagram showing a configuration of a UPnP device 2 of FIG.

FIG. 3 is a diagram showing a configuration of a device model included in the UPnP device 2 of FIG.

FIG. 4 is a diagram showing a structure of an asynchronous packet.

5 is a flowchart illustrating a process of the network system of FIG.

FIG. 6 is a diagram showing the structure of a message output in step S3 of FIG.

FIG. 7 is a diagram showing a configuration of a packet output in the process of step S24 of FIG.

8 is a diagram showing the structure of a packet output in the process of step S34 of FIG.

9 is a diagram showing an example of a message output in the process of step 26 of FIG.

FIG. 10 is a 1394 Proxy included in the root device of FIG.
It is a figure which shows the structure of Device Description.

FIG. 11 is a diagram showing a 1394 proxy service of FIG.
It is a figure which shows the structure of 94 Proxy Service Description.

FIG. 12 is a block diagram of the 1394 proxy service of FIG.
It is a figure which shows the structure of 94 Proxy Service Description.

FIG. 13 includes 13 of the 1394 nodes service of FIG.
It is a figure which shows the structure of 94 Nodes Service Description.

FIG. 14 is a view showing 13 of the 1394 nodes service of FIG.
It is a figure which shows the structure of 94 Nodes Service Description.

FIG. 15 is a 1394 Proxy included in the root device of FIG.
It is a figure which shows the other structure of Device Description.

FIG. 16 is a block diagram of the 1394 proxy service of FIG.
It is a figure which shows the structure of 94 Proxy Service Description.

FIG. 17 is a list of 13 included in the 1394 nodes service of FIG.
It is a figure which shows the structure of 94 Nodes Service Description.

FIG. 18 is a diagram showing another configuration of the device model.

FIG. 19 is a 1394 Prox included in the root device shown in FIG. 18;
It is a figure which shows the structure of y Device Description.

FIG. 20 is a 1394 Prox included in the root device shown in FIG. 18;
It is a figure which shows the structure of y Device Description.

FIG. 21 is a diagram of the 1394 proxy service of FIG.
It is a figure which shows the structure of 394 Proxy Service Description.

FIG. 22 is a diagram of 1 of the 1394 node service of FIG.
It is a figure which shows the structure of 394 Node Service Description.

FIG. 23 is a diagram showing another configuration of a device model.

FIG. 24 is a 1394 Prox included in the root device of FIG. 23.
It is a figure which shows the structure of y Device Description.

[FIG. 25] FIG. 25 shows the 1 which the 1394 proxy service of FIG.
It is a figure which shows the structure of 394 Proxy Service Description.

FIG. 26 is a table of 1394 node service of FIG.
It is a figure which shows the structure of 394 Node Service Description.

FIG. 27 is a diagram showing still another configuration of the device model.

28] A 1394 Prox included in the root device of FIG. 27.
It is a figure which shows the structure of y Device Description.

FIG. 29 is a 1394 Prox included in the root device shown in FIG. 27.
It is a figure which shows the structure of y Device Description.

[FIG. 30] FIG.
It is a figure which shows the structure of 394 Proxy Service Description.

FIG. 31: 1 which the 1394 node service of FIG. 27 has
It is a figure which shows the structure of 394 Nodes Service Description.

FIG. 32 is a diagram showing a comparison of device models.

[Explanation of symbols]

1 UPnP control point, 2 UPnP device,
3,4 1394 equipment, 11 IEEE802 network, 12 IEEE1394 network, 61 root
device, 71 1394 proxy service, 72
1394 nodes service

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Yukihiko Aoki             6-735 Kita-Shinagawa, Shinagawa-ku, Tokyo Soni             -Inside the corporation F term (reference) 5B089 GB01 HA06 HA18 JA35 KF05                 5K033 AA09 CB02 CC01 DA05 DB19                 5K034 AA20 DD03 FF12 HH61

Claims (8)

[Claims] 1. A first format based on IEEE802.
IEEE 13
In an information processing device that transmits and receives data to and from a second network that communicates with a second packet in a format based on 94, a capturing unit that captures the first packet from the first network, and the capturing unit Converting means for converting the first packet captured by the converting means into the second packet of the second network; and the second packet converted by the converting means,
Transmission means for transmitting to the second network, the conversion means includes a first service means for managing information on the IEEE 1394 bus, and a second service means for executing a service for the IEEE 1394 node. An information processing device comprising: 2. The information processing apparatus according to claim 1, wherein the conversion unit has the first service unit and the second service unit in one root device. 3. The conversion means has the first service means in a first root device and the second service means in a second root device which is different for each device. The information processing apparatus according to claim 1, which is characterized in that. 4. The information according to claim 1, wherein the conversion unit has the first service unit and the second service unit different for each device in one root device. Processing equipment. 5. The converting means includes the first service means in one root device, and an embedded device containing the second service means different for each device in the one root device. The information processing apparatus according to claim 1, wherein the information processing apparatus comprises: 6. A first format according to IEEE 802.
IEEE 13
In an information processing method of an information processing device for exchanging data with a second network communicating with a second packet of a format based on 94, a capturing step of capturing the first packet from the first network, A conversion step of converting the first packet acquired by the processing of the acquisition step into the second packet of the second network, and the second packet converted by the processing of the conversion step. And a transmitting step of transmitting to the second network, the converting step includes a first service step of managing information of the IEEE 1394 bus, and a second service step of executing a service to the IEEE 1394 node. An information processing method comprising: 7. A first format based on IEEE802.
IEEE 13
A program of an information processing device for exchanging data with a second network communicating with a second packet of a format based on 94, the capturing step of capturing the first packet from the first network, A conversion step of converting the first packet acquired by the processing of the acquisition step into the second packet of the second network, and the second packet converted by the processing of the conversion step. And a transmitting step of transmitting to the second network, the converting step includes a first service step of managing information of the IEEE 1394 bus, and a second service step of executing a service to the IEEE 1394 node. A computer-readable program characterized by including Recording medium on which arm is recorded. 8. A first format based on IEEE802.
IEEE 13
A program executed by a computer that controls an information processing device that transmits and receives data to and from a second network that communicates with a second packet in a format based on 94, the first network from the first network. A capturing step of capturing a packet; a conversion step of converting the first packet captured by the processing of the capturing step into the second packet of the second network; and a conversion of the processing of the converting step. A transmission step of transmitting the second packet to the second network, wherein the conversion step executes a first service step of managing information of the IEEE 1394 bus, and a service for the IEEE 1394 node. A second service step for performing the program.