Information processing apparatus and method for receiving/transmitting data between an IEEE802-based format and an IEEE1394-based format

[0001] 1. Field of the Invention

[0002] The present invention relates to information processor and method, recording medium and program, and particularly to information processor and method, recording medium and program with which equipment connected to one of a first network based on IEEE802 and a second network based on IEEE1394 can identify another equipment connected to the other network.

[0003] 2. Description of the Related Art

[0004] Recently, a network using IEEE (Institute of Electrical and Electronics Engineers) 1394 high-speed serial bus (hereinafter merely referred to as “IEEE1394 network”) has become popular. By connecting audio equipment or video equipment to the IEEE1394 network, each equipment can control the other equipment by using AV/C commands.

[0005] Further, an IEEE802 network has become popular. The IEEE802 network is a network that is mainly used to mutually connect personal computers to each other, and each personal computer can control other personal computers on the basis of UPnP (Universal Plug and Play) protocol.

[0006] However, the IEEE1394 network and the IEEE802 network are independent on each other, and thus there is a problem that an equipment connected to the IEEE1394 network (hereinafter referred to as “1394 equipment”) cannot identify another equipment connected to the IEEE802 network (hereinafter referred to as “UPnP device”).

[0007] The present invention has been implemented in view of the foregoing situation, and has an object to enable the 1394 equipment to identify an UPnP device.

[0008] In order to achieve the above object, according to a first aspect of the present invention, there is provided an information processor characterized by comprising: plural input means for inputting a first packet from a first network; converting means for converting the first packet input from any input means of the plural input means to a second packet of a second network; plural output means for outputting the second packet converted in the converting means to the second network from any output means of the plural output means; and storage means for storing the association relationship between each of the plural input means and each of the plural output means, the respective input and output means concerned inputting/outputting the corresponding packet.

[0009] According to a second aspect of the present invention, there is provided an information processing method characterized by comprising the steps of: managing plural input plugs for inputting a first packet from a first network; managing plural output plugs for outputting a second packet to a second network; converting the first packet input from any input plug of the plural input plugs to the second packet of the second network; outputting the second packet thus converted from any output plug of the plural output plugs to the second network; and storing the association relationship between each of the plural input plugs and each of the plural output plugs, the respective input and output plugs concerned inputting/outputting the corresponding packet.

[0010] According to a third aspect of the present invention, there is provided a program of a recording medium for an information processor for performing data communications between a first network in which communications are performed by using a first packet of an IEEE802-based format and a second network in which communications are performed by using a second packet of an IEEE1394-based format, characterized in that the recording medium stores therein a program for executing the steps of: managing plural input plugs for inputting the first packet from the first network; managing plural output plugs for outputting the second packet to the second network; converting the first packet input from any input plug of the plural input plugs to the second packet of the second network; outputting the second packet thus converted from any output plug of the plural output plugs to the second network; and storing the association relationship between each of the plural input plugs and each of the plural output plugs, the respective input and output plugs concerned inputting/outputting the corresponding packet.

[0011] According to a fourth aspect of the present invention, there is provided a program for a computer for controlling an information processor for performing data communications between a first network in which communications are performed by using a first packet of an IEEE802-based format and a second network in which communications are performed by using a second packet of an IEEE1394-based format, characterized in that the program makes the computer execute the steps of: managing plural input plugs for inputting the first packet from the first network; managing plural output plugs for outputting the second packet to the second network; converting the first packet input from any input plug of the plural input plugs to the second packet of the second network; outputting the second packet thus converted from any output plug of the plural output plugs to the second network; and storing the association relationship between each of the plural input plugs and each of the plural output plugs, the respective input and output plugs concerned inputting/outputting the corresponding packet.

[0012] In the information processor and method, the storage medium and the program according to the present invention, the association relationship between the plural input means or input plugs and the plural output means or output plugs is stored.

[0036] Preferred embodiments according to the present invention will be described with reference to the accompanying drawings.

[0037] FIG. 1 shows the construction of a network system to which the present invention is applied.

[0038] In the construction shown in FIG. 1, an UPnP control point 1 is connected to an IEEE802 network 11. 1394 equipments 3, 4 are connected to an IEEE1394 network 12. The IEEE802 network 11 and the IEEE1394 network 12 are respectively connected to the UPnP device (1394 proxy) 2.

[0039] FIG. 2 shows an example of the construction of the UPnP device 2.

[0040] In FIG. 2, CPU (Central Processing Unit) 21 executes various kinds of processing according to a program stored in ROM (Read Only Memory) 22 or a program loaded from a storage portion 28 into RAM (Random Access Memory) 23. In RAM 23 are also stored data required when CPU 21 executes various kinds of processing, if necessary.

[0041] CPU 21, ROM 22 and RAM 23 are mutually connected to one another through a bus 24. An input/output interface 25 is also connected to the bus 24.

[0042] To the input/output interface 25 are connected an input portion 26 comprising a keyboard, a mouse or the like, a display such as CRT or LCD, an output portion 27 such as a speaker, a storage portion 28 comprising a hard disc or the like, and a communication portion 29 such as a modem, or a terminal adapter. The communication portion 29 carries out the communication processing through the IEEE802 network 11 or the IEEE1394 network 12.

[0043] Further, a drive 30 is connected to the input/output interface 25 as occasion demands, a magnetic disc 41, an optical disc 42, a magneto-optical disc 43, a semiconductor memory 44 or the like is mounted if necessary, and a computer program read out therefrom is installed into the storage portion 28 as occasion demands.

[0044] The UPnP device (in the case of FIG. 1, the UPnP control point 1 and the UPnP device 2) mainly has the following six functions: Addressing, Discovery, Description, Control, Eventing and Presentation.

[0045] Addressing is a function with which each UPnP device achieves an address on the IEEE 802 network 11, and DHCP (Dynamic Host Configuration Protocol) or AutoIP is used.

[0046] Discovery is carried out after Addressing, and it enables the UPnP control point 1 to find out target equipment which the UPnP control point 1 wishes to control. A protocol used here is SSDP (Simple Service Discovery Protocol). When each equipment is connected to the IEEE802 network 11, it multicasts a message indicating devices installed therein and services onto the IEEE802 network 11 (particularly, packets are transmitted without specifying any communication partner). The UPnP control point 1 receives the message thus multicasted to know which equipment is connected to the IEEE802 network 11 (i.e., identify the equipment connected to the IEEE802 network 11.

[0047] Conversely, an equipment connected to the IEEE802 network 11 at present can be investigated from the side of the UPnP control point 1. At this time, the UPnP control point 1 multicasts a search command onto the IEEE802 network 11 by using a device or service to be discovered as a keyword. When the condition prescribed in the search command thus multicasted is met, each equipment connected to the IEEE802 network 11 unicasts a response to the search command concerned (i.e., specifies the communication partner side and transmits packets thereto), whereby the UPnP control point 1 can detect the equipment connected to the IEEE802 network 11.

[0048] Further, when each equipment gets out of the IEEE802 network 11, this is broadcasted in advance.

[0049] URL (Uniform Resource Locator) of a device description is described in an SSDP packet output from control target equipment discovered on the basis of Discovery by the UPnP control point 1. The UPnP control point 1 accesses the URL to achieve more detailed device information on the equipment from the device description. The device information contains icon information, model name, producer name, article name, etc.

[0050] In the device information is described information on a service to be provided by the device concerned. The service description in which the detailed information of the service is described can be searched on the basis of URL described in the service information.

[0051] The UPnP control point 1 can know a method of accessing the target on the basis of the device information (Device Description) and the service information (Service Description).

[0052] Further, Presentation URL described later is also described in the device description.

[0053] The Device Description and the Service Description are represented by XML (Extensible Markup Language).

[0054] Control is mainly classified into Action and Query. Action is performed by a method prescribed in the action information of the Service Description, and the UPnP control point 1 can operate the target by invoking Action.

[0055] Query is used to pick up the value of stateVariable of the Service Description. The value of stateVariable represents the state of the equipment.

[0056] A transport protocol called as SOAP (Simple Object Access Protocol) is used in Control. XML is used as the expression language thereof.

[0057] When the value of stateVariable is changed, Eventing is used to notify the fact of the change from the target to the UPnP control point 1. The UPnP control point 1 can know variables held by the target from stateVariable by analyzing the Service Description. With respect to variables for which sendEvents is set to yes, when these variables are changed, the UPnP control point 1 can receive a notification on the change from the target by outputting Subscription to the target in advance. A transport protocol called as GENA (General Event Notification Architecture) is used for Eventing. XML is used as the expression language thereof.

[0058] Presentation is used to supply a user with control means using a user interface (UI). Presentation Page described with HTML (Hyper Text Markup Language) can be achieved by accessing Presentation URL described in Device Description. By using this function, an application can be prepared at the target.

[0059] The UPnP device (1394 proxy) 2 functions as a bridge between the IEEE802 network 11 and the IEEE1394 network 12, and it has a device model shown in FIG. 3. The device model is constructed by one root device 61, and the root device 61 has an IEEE1394 proxy service 71 and an IEEE1394 nodes service 72.

[0060] The IEEE1394 proxy service (hereinafter merely referred to proxy service) 71 manages occurrence of bus reset of the IEEE1394 network 12, bus ID, the number of nodes, bus manager, node unique ID of isochronous resource manager (NUID), Gap Count, Self ID packet, etc.

[0061] The IEEE1394 nodes service (hereinafter merely referred to “node service”) 72 receives/transmits Link-On packets, phy packets containing Phy Configuration packets, etc., asynchronous packets and isochronous packets.

[0062] FIG. 4 shows the construction of the asynchronous packet.

[0063] Asynchronous communication is used when data communications are carried out asynchronously. In the asynchronous communications, it is guaranteed that packets are surely transmitted to a communication partner node, and no delay time of the transmission is guaranteed. The transmission node transmits header information and actual data to a node which is an indicated partner, and a reception node returns an Acknowledge packet to thereby notify reception of the packet to the communication partner. However, when a broadcast packet indicating no communication-partner node is received, the reception node returns no Acknowledge packet.

[0064] Destination_ID (Destination identifier) is disposed at the head of the 1394 packet header. This represents node_ID of the packet transmission destination.

[0065] “tl” (Transaction label) is a label for recognizing the coincidence between a pair of transactions of a request packet and a response packet. tl of the request packet is also used as tl of the response packet.

[0066] “rt” (Retry code) represents information on a retry method when busy Acknowledge is received.

[0067] “tcode” (Transaction code) represents a type code of a transaction packet. That is, it represents one of read/write/lock or request/response.

“pri” (Priority) is set to a110 (excluding cycle start at fair arbitration.

[0068] “source_ID” (Source identifier) represents the node_ID of a packet transmission origin.

[0069] “packet-type-specific information” is disposed subsequently to source_ID, and if necessary, “packet-type-specific data” are further disposed. CRC corresponding to the above header information is inserted as header_CRC at the last of the 1394 packet header.

[0070] A data block is disposed subsequently to the 1394 packet header. The data block comprises a required number of data block quadlets, and data_CRC as CRC for data information.

[0071] FIG. 5 represents the structure of the Isochronous packet. Data_length prescribes the byte value of a data field subsequent to the header. If this value is equal to zero, it represents that there is no data field.

[0072] “tag” (isochronous data format tag) represents the format of the Isochronous packet.

[0073] “channel” represents a channel number used to identify the Isochronous packet. “tcode” (transaction code) represents a code indicating the type of the packet. Isochronous packet is set to Ah.

[0074] “sy” (synchronization code) is used to communicate synchronous information such as pictures and sounds between a transmission node and a reception node.

[0075] “data field” (data block payload) represents Isochronous data.

[0076] FIG. 6 shows the construction of an AV/C device model that the proxy service 71 has. The AV/C device model 50 has an isochronous input plug 51 and a general bus input plug 52 as input plugs, and also it has an isochronous output plug 53 and a general bus output plug 54 as output plugs. Plugs having numbers of 00h to 1Eh can be provided as the isochronous input plug 51, and plugs having numbers of 40h to 5Eh can be provided as the general bus input plug 52. Further, plugs having numbers of 00h to 1Eh can be provided as the isochronous output plug 53, and plugs having numbers of 40h to 5Eh can be provided as the general bus output plug 54.

[0077] An isochronous packet is input to the isochronous input plug 51. Packets other than the isochronous packet (for example, packets in the IEEE802 network 11) are input to the general bus input plug 52.

[0078] The isochronous output plug 53 outputs an isochronous packet, the general bus output plug 54 outputs other packets (for example, packets of the IEEE802 network 11).

[0079] The AV/C device model 50 basically outputs from the isochronous output plug 53 the data input from the isochronous input plug 51, and also outputs from the general bus output plug 54 the data input from the general bus input plug 52. However, if necessary, it can switch the input and the output to each other to output from the isochronous input plug 54 the data input from the isochronous input plug 51 and also output from the isochronous output plug 53 the data input from the general input plug 52.

[0080] Next, the processing carried out when the UPnP control point 1 connected to the IEEE802 network 11 controls equipment connected to the IEEE1394 network 12 will be described with reference to the flowchart of FIG. 7.

[0081] In step S1, the UPnP control point 1 subscribes the proxy service 71 constituting the 1394 proxy device 2 so that when some variation is made in the IEEE1394 network 12, the proxy service 71 notifies this variation to the UPnP control point 1. Instep S11, when receiving this Subscribe, the proxy service 71 executes the processing corresponding to the subscribe.

[0082] For example, if 1394 equipment 3 is connected to the IEEE1394 network 12 in step S41, in step S42 bus reset occurs in the 1394 equipment 3, and likewise, in step S21 bus reset occurs in the node service 72 of the root device 61. At this time, the node service 72 notifies the occurrence of the bus reset to the proxy service 71 in step S22.

[0083] When detecting a notification from the node service 72 instep S12, on the basis of the Subscribe from the UPnP control point 1 taken in step S11, the proxy service 71 notifies to the UPnP control point 1 that the 1394 equipment 3 is connected to the IEEE1394 network 12 in step S13.

[0084] In step S2, the UPnP control point 1 receives a notification from the proxy service 71, whereby the UPnP control point 1 can know that the 1394 equipment 3 is connected to the IEEE1394 network 12.

[0085] Therefore, in step S3, the UPnP control point 1 invokes the request packet of Action based on SOAP corresponding to asynchronous read request command to read out information recorded at a predetermined address of the register of the 1394 equipment 3, for example.

[0086] FIG. 8 shows an example of a request message transmitted from the UPnP control point 1 to the node service 72. The UPnP control point 1 refers to 1394 Nodes Service Description shown in FIGS. 20 to 23 described later to create a request message.

[0087] Since a response is returned in connection with a request, the numeral “5” contained in Transaction represents a transaction level as a label to recognize which request the response corresponds to.

[0088] “nuid” contained in Body represents the node unique ID (NUID) of the communication partner of this message. In the case of this example, it represents NUID of the 1394 equipment 3. NUID “0800460000000000” is described in the notification achieved from the proxy service 71 through the processing of step S2. This NUID is converted to the node ID of the 1394 equipment 3 (in the case of FIG. 9, “ffc0”) on the basis of the corresponding table that the node service 72 has, and stored in destination_ID of the packet of FIG. 9.

[0089] “command” represents the type of a command with which the UPnP control point 1 requests “occurrence” to the node service 72. That is, in this example, occurrence of asynchronous read request command is requested.

[0090] “000001400000” (hexadecimal number) at MSB side which is contained in “command” represents a transaction label tl, a retry code rt, a transaction code tcode and a priority Pri of FIG. 9 in read request for data quadlet packet shown in FIG. 9 which is generated by the node service 72.

[0091] “fffff0000404” at LSB side corresponds to destination_offset in FIG. 9. That is, this value represents the address of the register of the 1394 equipment 3 which the UPnP control point 1 wishes to read.

[0092] The node ID of the node service 72 (in the case of the example of FIG. 9, “ffc1”) is described in the source_ID field of FIG. 9.

[0093] All these values are represented in the text style, and thus they can be described in any kind of packet of the IEEE1394.

[0094] Returning to FIG. 7, when receiving Invoke of Action shown in FIG. 8 in step S23, the node service 72 creates a packet of asynchronous read request shown in FIG. 9 in connection with Invoke of Action in step S24, and transmits it through the IEEE1394 network 12 to the 1394 equipment 3. At this time, the node service 72 stores the corresponding table representing the association relationship between the request shown in FIG. 8 and the request packet shown in FIG. 9.

[0095] When receiving the asynchronous read request packet transmitted from the node device 72 in step S43, the 1394 equipment 3 executes the processing corresponding to the request (in this case, read-out of the register). In step S44, the 1394 equipment 3 creates a response packet as shown in FIG. 10 which corresponds to the request packet, and transmits it to the node service 72.

[0096] As shown in FIG. 10, the value of the transaction code tcode is set to the value “6” representing “response”.

[0097] The values in the read request for data quadlet packet of FIG. 9 are directly used as the values of destination_ID and source_ID. The data read out from the address of destination_offset are disposed in quadlet data.

[0098] When receiving the response packet transmitted from the 1394 equipment 3 in step S25, the node service 72 creates Response as Action based on the SOAP protocol as shown in FIG. 11 in step S26, and transmits it to the UPnP control point 1.

[0099] On the basis of the corresponding table, the value “5” indicated in Transaction shown in FIG. 11 is set to “5” (the same value) in connection with the value “5” of Transaction in FIG. 8 in order to indicate that it is Action paired with Action of FIG. 8.

[0100] In Body of FIG. 11 is described “Response” so that it corresponds to the asynchronous read response of 1394. Further, data of “00000160000000000000000031333934” is described there. This data is the value described in the quadlet data of FIG. 10, and it is read out from the offset address of the 1394 equipment 3. In step S4, the UPnP control point 1 reads out this value.

[0101] In this example, in step S5 the UPnP control point 1 subsequently invokes the request packet of Action based on SOAP in which a command to control a predetermined operation of the 1394 equipment 3 (in this case, the turn on the power of the 1394 equipment 3) is described.

[0102] The UPnP control point 1 refers to the 1394 Nodes Service Description shown in FIGS. 20 to 23 described later that the node service 7 has, and creates this message (command).

[0103] When receiving Invoke of Action in step S27, the node service 72 creates the AV/C command (AV/C power control command) in connection with the Invoke of Action in step S28, and transmits it through the IEEE1394 network 12 to the 1394 equipment 3.

[0104] The AV/C node service 72 creates and holds the corresponding table between NUID and Node ID, and renews them every time bus reset occurs. NUID is converted to the node ID on the basis of the corresponding table, and transmitted to the IEEE1394 network 12.

[0105] When receiving the AV/C power control command transmitted from the node device 72 in step S45, the 1394 equipment 3 turns on the power of the device in connection with the content of the command. Thereafter, instep S46 the 1394 equipment 3 creates the corresponding AV/C response (AV/C POWER response) and transmits it to the node service 72.

[0106] When receiving the AV/C POWER response transmitted from the 1394 equipment 3 in step S29, the node service 72 creates Response as Action based on the SOAP protocol in step S30, and transmits it to the UPnP control point 1.

[0107] The node service 72 creates and holds a table for holding the association relationship of Transaction (corresponding table). That is, when the AV/C POWER control command is received in step S27 and when the AV/C POWER control command is output in step S28, it is stored in the table that both are associated with each other. Accordingly, when the AV/C POWER response is transmitted from the 1394 equipment 3, the node service 72 can recognize that it is the response corresponding to the AV/C POWER control command by referring to this table.

[0108] When receiving the AV/C POWER response in step S29, the node service 72 creates Response of Action based on SOAP in step S30, and transmits it to the UPnP control 1.

[0109] The UPnP control point 1 receives this response in step S6, whereby the UPnP control point 1 can know that the 1394 equipment 3 turns on the power of the device.

[0110] According to the prescription of AV/C, it is prescribed that when AV/C equipment cannot immediately execute the processing corresponding to a request received, it returns INTERIM as a response. Thereafter, when the processing corresponding to the request is completed, the AV/C equipment returns the final response to the transmitter of the request at that time point.

[0111] However, there is no prescription on the time from the reception of the request until the return of the final response. Therefore, the node service 72 manages the time until it receives the AV/C response from the 1394 equipment 3 in the processing of the step S29 after the AV/C command is output to the 1394 equipment 3 in the processing of the step S28. When a response is received within a predetermined time set in advance (for example, 30 seconds), the AV/C node service 72 immediately transmits the response corresponding to the response received to the UPnP control point 1 if the response is not INTERIM (in the case of the final response).

[0112] On the other hand, if the response received is INTERIM, the AV/C node service 72 is on standby until 30 seconds elapse from the transmission of the AV/C command. When a response other than INTERIM (final response) is received before 30 seconds elapse, the response corresponding to the final response is output. If no final response is received within 30 seconds, the AV/C node service 72 outputs INTERIM as the response, whereby the UPnP control point 1 can know whether the processing requested at least within 30 seconds can be completed or not.

[0113] In the example of FIG. 7, the UPnP control point 1 invokes “get Stream” of Action based on SOAP in step S7.

[0114] FIG. 12 shows an example of a message to be created and output in this case.

[0115] “5” represents a transaction label, and “getStream xmlns” represents an action name. “protocol” indicates a protocol used to transmit a stream on IP. “uri” indicates a file on IP which flows in the style of “isochronous”.

[0116] When receiving Invoke of get Stream from the UPnP control point 1 in step S14, the proxy service 71 executes the processing of achieving a stream flowing through the IEEE802 network 11 in connection with the Invoke thus received in step S15. At this time, the proxy service 71 is assumed to input the stream to the general bus input plug 52 of the AV/C device model 50. When this stream flows into the IEEE1394 network 12, the proxy service 71 carries out the conversion processing of the format of the packet, and also connects the general bus input plug 52 to the isochronous output plug 53.

[0117] Further, it requests the node service 72 to transmit the packet to the IEEE1394 network 12. The node service 72 executes the processing based on this request in step S31.

[0118] As described above, the connection relationship between the input plug and the output plug is stored (reflected) in a built-in memory.

[0119] That is, through this processing, the association relation indicating which plug of the plural input plugs is connected to which plug of the plural output plugs is stored. Accordingly, by referring to this memory (table), the 1394 equipment 3 can known the UPnP device connected to the IEEE802 network 11.

[0120] FIG. 13 shows an example of the table stored in the node service 72. In this case, the node service 72 has totally four plugs (1 to 4). Of these plugs, the plug 1 is used as the general bus input plug 52 of the number (ID) 40, and the plug 4 is used as the general bus input plug 52 of the number (ID) 41. Data of MEPG format are input to the former plug, and data of Audio format are input to the latter plug.

[0121] In step S16, the proxy service 71 creates Response of get Stream as Action corresponding to Action received in step S14, and outputs it to the UPnP control point 1. The UPnP control point 1 receives it in step S8.

[0122] FIG. 14 shows an example of a message in this case. “5” of the transaction label corresponds to the transaction label of FIG. 12.

[0123] In the case of FIG. 7, the 1394 equipment 3 further outputs AV/C Input Plug Signal Format Status Command to the node service 72 in step S47. This command requests a notification of the equipment connected to the input plug in the AV/C device model 50.

[0124] FIG. 15 shows the format of the command. In Opcode is described a value 19h representing that this command is INPUT PLUG SIGNAL FORMAT.

[0125] One number for specifying the input plug is described in the plug field.

[0126] When receiving the command from the 1394 equipment 3 in step S32, the node service 72 executes the processing corresponding to this command in step S33. That is, the equipment connected to the input plug indicated is read out, and it is output as AV/C Input Plug Signal Format Status Response to the 1394 equipment 3. In step S48, the 1394 equipment 3 receives this Response and reads the content thereof, so that it can know the UPnP device connected to the IEEE802 network 11.

[0127] FIG. 16 shows the format of Response in this case. The format is set to the same format as INPUT PLUG SIGNAL FORMAT control command format.

[0128] In the case of Audio, “010000” is described in an fmt field, and in the case of MEPG 2 of video, “100000” is described in the fmt field.

[0129] The value described in the plug field of the command format of FIG. 15 is directly described in the plug field.

[0130] The time for which the plug is connected is described in an fdf field.

[0131] In order to execute the above processing, the root device 61 of the device model owned by the 1394 proxy 2 shown in FIG. 3 has 1394 Proxy Device Description shown in FIG. 17, the proxy service 71 has 1394 Proxy Service Description shown in FIGS. 18 and 19, and the node service 72 has 1394 Nodes Service Description shown in FIGS. 20 to 23.

[0132] In these Descriptions are described parameters required to execute the functions of the equipment concerned and other conditions. When another equipment requests the equipment concerned to execute the function thereof, by referring the Description thereof, the equipment adds the condition described therein and transmits it to the equipment concerned.

[0133] In FIG. 17, deviceType “urn:sonycorp:device:1394ProxyDevice:1” represents that the device type is Proxy Device. FriendlyName “proxy for IEEE1394” represents the friendly name of the root device 61.

[0134] UDN“nuid:upnp-1394proxy-root-0800460000000000” represents the inherent number of the root device 61.

[0135] Two services are described in this Device Description. One is a service the serviceType of which is “urn:sonycorp:service:1394ProxyService:1” and the other is a service the serviceType of which is “urn:sonycorp:service:1394NodeService:1”. That is, the former is the service corresponding to the proxy service 71 of FIG. 3, and the latter is the service corresponding to the node service 72 of FIG. 3.

[0136] SCPDURL “./scpd/proxyScpd.xml” of the former service represents URL of Proxy Service Description owned by the proxy service 71 (specifically, URL of Proxy Service Description shown in FIGS. 18 and 19).

[0137] SCPDURL “./scpd-nodeScopd.xml” of the latter service represents URL of Nodes Service Description owned by the node service 72 (specifically, 1394 Nodes Service Description shown in FIGS. 20 to 23).

[0138] Action in 1394 Proxy Service Description of FIGS. 18 and 19 represents various kinds of actions, and the action having the name “busRest” represents an action for inducing bus reset. The action having the name “getNodeNum” represents an action to achieve the number of nodes on the 1394 bus. The action having the name “getIrmId” represents an action to achieve NUID of IRM (Isochronous Resource Manager) on the 1394 bus.

[0139] The action having the name “getBmId” represents an action to achieve NUID of the bus manager on the 1394 bus. The action having the name “getGapCount” represents an action to achieve Gap Count on the 1394 bus.

[0140] The action having the name “getselfIdPacket” represents an action to achieve SelfID packet flowing on the 1394 bus.

[0141] An argument in which the direction having the name “nodeNum” is “out” (the argument output and transmitted from another equipment) is prescribed in the action having the name “getNodeNum”. In the argument “nodeNum”, the relating prescription is described in serviceStateTable. That is, it is described in “nodeNum” that when an event is generated in subscribed equipment or a status variable is varied, it is an argument that is output while it has the data form of “il”.

[0142] An argument in which “direction” having the name “nuid” is “out” is prescribed in the action of “getIrmId”. An argument in which “direction” having the name “getcount” is “out” is prescribed in the action of “getGapCount”, and an argument in which “direction” having the name “selfIdPacket” is “out” is prescribed in the action having the name “getSelfIdPacket”. These arguments transmit no notification to even the subscribed equipment even when the status variable is varied, and it is described that they are output from each equipment while the form of the data is “bin.hex”.

[0143] In 1394 Nodes Service Description shown in FIGS. 20 to 23 are prescribed the actions of “asyncReqSend”, “avcCommandSend”, “phyPacketSend” and “LinkOnPacketSend”.

[0144] The action having the name “asyncReqSend” represents an action to transmit an asynchronous packet. On the basis of this action, the action shown in FIGS. 8 and 11 is created.

[0145] In this action is prescribed an argument in which “direction” having the name “nuid” is “in” (an argument output to and input into another equipment). The data type of this argument “nuid” is set to “bin.hex”.

[0146] In the action of “asyncReqSend” are further prescribed an argument in which direction of “asyncRequest” is “in” and an argument in which direction of “asynchResponse” is “out”.

[0147] Likewise, an argument in which direction having the name “asyncRequest” is “in” and an argument in which direction having the name “asyncResponse” is “out” are prescribed as having the date form of “bin.hex”.

[0148] The action having the name “avcCommandSend” represents an action to transmit the AV/C command, thereby creating the action based on the processing of the steps S5 and S30 of FIG. 7.

[0149] The action having the name “phyPacketSend” represents an action to transmit a phy packet. In this command, an argument in which direction having the name “phypacket” is “in” and an argument in which direction having the name “phyPacketResp” is “out” are prescribed, these arguments have the relating variables “phypacket” and the data type is “ui4”.

[0150] The action having the name “LinkOnPacketSend” represents an action to transmit LinkOn packet. This action has an argument in which direction of “phyid” is “in”. The data type of this argument is “il”.

[0151] The series of processing described above can be executed by hardware, however, they may be executed by software. When the series of processing is executed by software, the program constituting the software is installed into a computer incorporated in a dedicated-purpose hardware or installed from a network or recording medium into a general personal computer which can execute various kinds of functions by installing various programs or the like.

[0152] As shown in FIG. 2, the recording medium is constructed not only by a package medium such as a magnetic disc 41 (containing a floppy disk), optical disc 42 (containing CD-ROM (Compact Disk-Read Only Memory), DVD (Digital Versatile Disk)), magneto-optical disc 43 (containing MD (Mini-Disk)) or semiconductor memory 44, which is distributed to users to supply programs separately from the main body of an apparatus and in which the programs are recorded, but also by ROM 22 which is supplied to users while it is installed in the main body of an apparatus in advance and in which the programs are recorded, a hard disc contained in the storage portion 28 or the like.

[0153] In this specification, the step of describing the program to be recorded in the recording medium may contain not only the processing that is time-sequentially carried along the order described, but also the processing that is executed in parallel or individually even without being processed time-sequentially.

[0154] Further, in this specification, the system represents the overall apparatus constructed by plural devices.

[0155] As described above, according to the information processing apparatus and method of the present invention, the recording medium and the program, the association relationship between the input means or input plug and the output means or output plug is stored, so that equipment connected to a second network can know equipment connected to a first network.