JP2015201758A - Repeater, communication system, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce a cost of creating/managing information on a managed transfer destination, while making it possible to acquire a resource in a different home network.SOLUTION: A repeater includes: analysis means for performing analysis to determine whether or not data received from a second communication device includes first resource information for identifying a position of a resource provided by a data provision device; acquisition means for acquiring host information on the data provision device from the first resource information, when a result of the analysis shows that the first resource information for identifying the position of the resource provided by the data provision device is included; creation means for creating second resource information obtained by converting the host information on the data provision device to host information on the repeater; and first transfer means for transferring data obtained by replacing the first resource information included in the data received from the second communication device with the second resource information, to a first communication device.

Description

  The present invention relates to a relay apparatus, a communication system, an information processing method, and a program that enable creation of information about a transfer destination to be managed and a management cost and acquisition of resources in different home networks.

In recent years, with the spread of networks, not only personal computers but also mobile phones and electronic devices can be connected to the network. As a result, the environment where electronic devices are used in cooperation with each other is not only for office use, but also home appliances and other electrical appliances that have been used alone until now are connected to the network, so that they can also be used for home use. It has become. For this reason, there has been a particular demand for easy connection and easy setting of various devices connected to the network.
One of the network technologies that can meet such demands is called Universal Plug and Play (UPnP: Universal Plug and Play). UPnP is a protocol that operates within a single home network, but there is a technology that enables such a protocol that operates within a closed network to operate in a higher-level network such as between remote sites over the Internet. To do.

The system described in Patent Document 1 arranges a reverse proxy device between two networks that cannot communicate directly, and the reverse proxy device relays data between the two networks, thereby exchanging data between the networks. Is possible. More specifically, a conversion table of information used when accessing the destination web server designated by the transmission source user and information used when the reverse proxy device accesses the destination web server is used. When the transmission source user explicitly designates the destination web server, the reverse proxy device refers to the conversion table and transfers it to the destination web server.
In the system described in Patent Document 2, a UPnP device proxy is arranged in each of different home networks, and connection between UPnP devices connected in each home network is enabled.

JP 2010-55200 A JP-A-2005-311773

In order to transfer data to a destination by referring to the conversion table as in the system described in Patent Document 1, it is necessary to create a conversion table. However, as the number of bases to be connected increases, there are problems that the cost for creating and managing the conversion table increases and the data size of the conversion table increases.
On the other hand, in the system described in Patent Document 2, each UPnP device can be connected, but there is a problem that access specifying a resource managed by the UPnP device is not possible.
An object of the present invention is to reduce the cost of creating and managing information related to a transfer destination to be managed, and enabling acquisition of resources in different home networks.

  Therefore, the present invention is a relay device that relays a first network including a first communication device and a second network including a second communication device and a data providing device, wherein the second network includes the second network. Provided by the data providing apparatus as a result of the analysis, and analysis means for analyzing whether or not the data received from the communication apparatus includes first resource information for identifying the location of the resource provided by the data providing apparatus If the first resource information for identifying the location of the resource to be included is included, the acquisition means for acquiring the host information of the data providing device from the first resource information, and the host information of the data providing device are relayed Creation means for creating second resource information converted into host information of the device; and the first resource information included in the data received from the second communication device as the second resource information. The data rewritten in the resource information; and a first transfer means for transferring to the first communication device.

  ADVANTAGE OF THE INVENTION According to this invention, while creating the information regarding the transfer destination to manage and management cost can be reduced, the resource acquisition in a different home network can be enabled.

It is a figure which shows an example of a system structure without communication. It is a figure which shows an example of a function structure of a relay server, a SIP server, and a data management apparatus. It is a sequence diagram which shows the flow of the message of the whole communication system. It is a figure which shows an example about the outline of a message. It is a figure which shows an example about the outline of a message. It is a figure which shows an example about the outline of a message. It is a flowchart which shows an example of the information processing of a relay server. It is a sequence diagram which shows the flow of the message at the time of request transmission. It is a flowchart which shows an example of the information processing of a relay server. It is a sequence diagram which shows the flow of a message when deleting session information. It is a sequence diagram which shows the flow of a message when changing session information.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
<Embodiment 1>
FIG. 1 is a diagram illustrating an example of a system configuration of a communication system.
The relay server 100 is connected to the HGWA 410 and the HGWB 510 via a WAN (Wide Area Network) 600. For the connection with the HGWA 410 and the HGWB 510, a session established by the SIP server 200 described later with each of the HGWA 410 and the HGWB 510 is used. The relay server 100 is a server that relays data between the Client A 420 and the Server A 520 via the HGWA 410 and the HGWB 510 using these sessions. The relay server 100 can access a data management apparatus 300 that manages data shared with the SIP server 200, and has a function of referring to, storing, changing, and deleting data from the data management apparatus 300.

The SIP server 200 has a function of connecting to the HGWA 410 and the HGWB 510 via the network and establishing a session using the HGWA 410 and the HGWB 510 and the SIP (Session Initiation Protocol). Further, the SIP server 200 can access a data management apparatus 300 that manages data shared with the relay server 100, and has a function of referring to, storing, changing, and deleting data with respect to the data management apparatus 300. In the communication system of the present embodiment, description is made using SIP as a protocol, but the protocol is not limited to this. For example, the communication system may use XMPP, H323, HTTP, and WebSocket.
The data management device 300 is accessed from the relay server 100 and the SIP server 200, and has a function of managing data used by the relay server 100 and the SIP server 200. The data management apparatus 300 responds to data reference, addition, change, and deletion from the relay server 100 and the SIP server 200.
In this embodiment, the relay server 100, the SIP server 200, and the data management device 300 are arranged as independent nodes, but the present invention is not limited to this. The relay server 100, the SIP server 200, and the data management apparatus 300 may be arranged as an integrated apparatus, and do not depend on the place or the arrangement apparatus.

HomeA is an area in which a LAN 400 (Local Area Network) is constructed, and ClientA 420 and HGWA 410 described later are connected thereto.
The HGWA 410 is a device that relays data between the Client A 420 and the Server A 520 via the relay server 100. The HGWA 410 has a function of establishing a session with the SIP server 200 using the SIP protocol.
The Client A 420 conforms to the Control Point defined by UPnP Device Architecture and has a function of controlling UPnP Media Server. The client A 420 is a device that acquires a content list and content for a server A 520 and a server B 530 described later. Server A 520 and Server B 530 are examples of data providing apparatuses.
Home B is an area where a LAN 500 (Local Area Network) is constructed, and Server A 520, Server B 530, and HGWB 510 described later are connected thereto.
The HGWB 510 is a device that relays data between each of the server A 520 and the server B 530 and the relay server 100. The HGWB 510 has a function of establishing a session with the SIP server 200 using the SIP protocol.
The Server A 520 and the Server B 530 have UPnP Media Server functions, and are devices that provide a list of content managed in response to a request from the Client A 420 and provide content. In this embodiment, an apparatus having a Media Server function is described. However, the Server A 520 and the Server B 530 may be other devices or services other than UPnP, or devices or services other than UPnP.

FIG. 2 is a diagram illustrating an example of functional configurations of the relay server 100, the SIP server 200, and the data management apparatus 300.
The data transfer unit 101 has a function of transmitting / receiving data to / from the HGWA 410 and HGWB 510. The data transfer unit 101 transmits and receives data based on information negotiated when the SIP server 200 establishes a session with each of the HGWA 410 and the HGWB 510.
The data analysis unit 102 analyzes whether or not the data is received from the HGWB 510 by the data transfer unit 101, and acquires host information from the URL. The host information is an IP address and port number, or a domain name and port number. Although the port number may be omitted, in that case, the default port number defined by the protocol is used from the scheme included in the URL.
The data conversion unit 103 converts the host information included in the URL acquired by the data analysis unit 102 into host information accessible by the Client A 420.
The data access unit 104 has an access function to the data management apparatus 300 and performs data reference, registration, update, and deletion.
The data rewriting unit 105 rewrites the URL included in the data received from the HGWB 510 to the URL converted by the data conversion unit 103. In the present embodiment, the data rewriting unit 105 converts the URL. However, the data rewriting unit 105 is not limited to the URL, and may change an identifier that specifies the location of another resource.
The message type determination unit 106 determines whether the data received from the HGWA 410 is a request message that conforms to a standard document. When the message type determination unit 106 determines that the request message conforms to the standard document, the message type determination unit 106 determines whether or not the URL to be converted is included in the response message from the standard document of the response message to the request message. For example, when the SOAP protocol is used, a response message for the Action is defined in the standard document, and the message type determination unit 106 can determine from the Action name whether or not a URL is included in the response message.

  The session control unit 201 establishes a session with each of the HGWA 410 and the HGWB 510, and performs negotiation for the data transmission / reception between the relay server 100 and each of the HGWA 410 and the HGWB 510. In addition, the session control unit 201 receives status notifications of the Server A 520 and the Server B 530 connected to the LAN 500 from the HGWB 510. The status notification includes the server device type, service type, and whether each service is accessible. For the status notification, SIP MESSAGE, INFO request, SUBSCRIBE / NOTIFY, and PUBLISH are used. Protocols other than SIP may be used. The session control unit 201 has a function of accessing the data management apparatus 300, and performs data reference, registration, update, and deletion.

The data management device 300 has a function of managing data and a function of controlling data access from the relay server 100 and the SIP server 200.
The device information management unit 301 stores and manages the HGW information of the HGWA 410 and the HGWB 510 and the UPnP device information of the Server A 520 and the Server B 530. The HGW information and UPnP device information are made up of an identifier for identifying the HGW and Server and information included in the status notification. The device information management unit 301 may manage other information as well as the above information.
The session information management unit 302 stores and manages session information established by the SIP server 200. The session information includes a session identifier, HGW information of the HGW belonging to the session, Server UPnP device information connected under the HGW, and the like. The session information management unit 302 may manage other information as well as the above information.

  The functional configuration of the relay server 100, the SIP server 200, and the data management device 300 may be implemented in each device as a hardware configuration, or may be implemented in each device as a software configuration. When some or all of each configuration is implemented as a software configuration, each device includes at least a CPU and a memory as a hardware configuration. Then, the CPU of each device executes processing based on the program stored in the memory of each device, thereby realizing the software configuration of each device. Further, in the case of such a configuration, a process according to a sequence diagram and a process according to a flowchart to be described later are realized by the CPU of each device executing a process based on a program stored in the memory of each device. When the device information management unit 301 and the session information management unit 302 are implemented in the data management apparatus 300 as software configurations, the management system manages device information and session information stored in the memory of the data management apparatus 300 or the like. Implemented.

FIG. 3 is a sequence diagram showing a message flow of the entire communication system. For simplification of description, the description of the SIP server 200 is omitted in FIG. Each of the HGWA 410 and the HGWB 510 is registered in the SIP server 200. The processing of this embodiment will be described below using this sequence diagram.
In S101 and S103, each of the HGWA 410 and the HGWB 510 notifies the SIP server 200 of the HGW information and the Server information. The HGW information includes at least the identifiers (SIP-URI) of the HGWA 410 and the HGWB 510 and information of UPnP devices (Server A 520 and Server B 530) connected to each Home network. The UPnP device information includes at least a Location-URL, a device type, and a service type. In addition, information included in the device description or the service description may be included.
In S102, HGWB 510 monitors Server A 520 and Server B 530 in LAN 500 to which it is connected.
When Server A 520 and Server B 530 are newly connected to LAN 500 or disconnected from LAN 500, HGWB 510 notifies UPnP device status information to relay server 100 in S103.
In S104, the relay server 100 registers the data received in S101 and S103 in the device information management unit 301 of the data management apparatus 300. Data registered in the device information management unit 301 will be described using Table 1.

ＨＧＷ情報の識別子Ｌｉｓｔ１−１は、ＨＧＷを識別する識別子でＳＩＰＵＲＬである。
ＵＰｎＰデバイス情報のＬｏｃａｔｉｏｎＵＲＬＬｉｓｔ１−２は、ＳｅｒｖｅｒＡ５２０及びＳｅｒｖｅｒＢ５３０が送信したＳＳＤＰのＡｄｖｅｒｔｉｓｅメッセージのＬｏｃａｔｉｏｎヘッダの内容である。
ＵＰｎＰデバイス情報のＤｅｖｉｃｅ情報Ｌｉｓｔ１−３は、ＳｅｒｖｅｒＡ５２０及びＳｅｒｖｅｒＢ５３０のＤｅｖｉｃｅＴｙｐｅである。
ＵＰｎＰデバイス情報のＳｅｒｖｉｃｅ情報Ｌｉｓｔ１−４は、ＳｅｒｖｅｒＡ５２０及びＳｅｒｖｅｒＢ５３０のＳｅｒｖｉｃｅＴｙｐｅである。
登録する内容は上記情報に限定するものではなく、ＳｅｒｖｅｒＡ５２０及びＳｅｒｖｅｒＢ５３０を識別する識別子であるＵＵＩＤやＤｅｖｉｃｅＤｅｓｃｒｉｐｔｉｏｎに含まれる情報、例えばＦｒｉｅｎｄｌｙＮａｍｅ等を含んでもよい。

The identifier List1-1 of the HGW information is an SIP URL that identifies the HGW.
The LocationURLList1-2 of the UPnP device information is the contents of the Location header of the SSDP Advertise message transmitted by Server A520 and ServerB530.
Device information List1-3 of the UPnP device information is DeviceType of Server A520 and ServerB530.
Service information List1-4 of the UPnP device information is a ServiceType of Server A520 and ServerB530.
The contents to be registered are not limited to the above information, and may include UUID that is an identifier for identifying Server A 520 and Server B 530, information included in Device Description, for example, FriendlyName, and the like.

Returning to the description of FIG. 3, in S105, the SIP server 200 establishes a session with each of the HGWA 410 and the HGWB 510. The SIP server 200 negotiates connection information for performing data communication between the HGWA 410 and the relay server 100 and between the HGWB 510 and the relay server 100 when a session is established. The connection information between the HGWA 410 and the relay server 100 includes at least the IP addresses or domain names and port numbers of the HGWA 410 and the relay server 100. The HGWA 410 starts up an HTTP server on the LAN 400 side and notifies the relay server 100 of the IP address and port number. Thereafter, the HGWA 410 transfers the data received by the HTTP server to the relay server 100 using the connection information negotiated when the session is established.
In S106, relay server 100 registers the connection information as session information in session information management unit 302 of data management device 300. The contents to be registered will be described using Table 2.

ＨＧＷ情報の識別子Ｌｉｓｔ２−１は、デバイス情報管理部３０１で保存されているＨＧＷ情報の識別子Ｌｉｓｔ１−１と同じである。
ＨＧＷ情報の接続情報Ｌｉｓｔ２−２は、中継サーバ１００がセッション確立（Ｓ１０５）の際に取得したＨＧＷＡ４１０及びＨＧＷＢ５１０へ接続するための情報である。
ＨＧＷ情報のＨＴＴＰサーバ情報Ｌｉｓｔ２−３は、中継サーバ１００がセッション確立（Ｓ１０５）の際に取得したＨＧＷＡ４１０のＨＴＴＰサーバのＩＰアドレス及びポート番号である。
Ｓｅｒｖｅｒ情報のＬｏｃａｔｉｏｎＵＲＬＬｉｓｔ２−５及び２−６は、デバイス情報管理部３０１に保存されているＬｏｃａｔｉｏｎＵＲＬＬｉｓｔ１−２である。ＬｏｃａｔｉｏｎＵＲＬＬｉｓｔ１−２の内容がＩＰアドレス及びポート番号（Ｌｉｓｔ２−５）と、以降のパス情報（Ｌｉｓｔ２−６）とに分割されて保存されている。
Ｓｅｒｖｅｒ情報のｐｒｅｆｉｘＬｉｓｔ２−４は、ＬｏｃａｔｉｏｎＵＲＬＬｉｓｔ２−５を識別するプリフィックスである。ｐｒｅｆｉｘは中継装置のホスト情報の一例である。ＬｏｃａｔｉｏｎＵＲＬはデータ提供装置のホスト情報の一例である。Ｓｅｒｖｅｒ情報は関連情報の一例である。

The identifier List2-1 of the HGW information is the same as the identifier List1-1 of the HGW information stored in the device information management unit 301.
The connection information List2-2 of the HGW information is information for connecting to the HGWA 410 and the HGWB 510 acquired when the relay server 100 establishes a session (S105).
The HTTP server information List2-3 of the HGW information is the IP address and port number of the HTTP server of the HGWA 410 acquired when the relay server 100 establishes a session (S105).
Server URL LocationURLList2-5 and 2-6 are LocationURLList1-2 stored in the device information management unit 301. The contents of LocationURLList1-2 are divided into an IP address and a port number (List2-5) and subsequent path information (List2-6) and stored.
Server information prefixList2-4 is a prefix for identifying LocationURLList2-5. prefix is an example of host information of a relay device. LocationURL is an example of host information of the data providing apparatus. Server information is an example of related information.

Returning to the description of FIG. 3, in S <b> 107, the SIP server 200 notifies the HGWA 410 of a list of Server information connected to the HGWB 510 stored in the session information management unit 302.
In S108, the HGWA 410 uses the acquired information of the Server A 520 to advertise the service that the Server A 520 has using the SSDP protocol. The HGWA 410 links the Location-URL with the HTTP server on the LAN 400 side of the HGWA 410, the port number, the prefix (List2-4), and the path information (List2-6), and advertises the device / service that the Server A520 has. This allows the client A 420 to discover the server A 520. FIG. 4 shows an example of the outline of the message. The Location header is composed of the following contents.
・ HTTP server address of HGWA410 (192.168.0.1:1000)
・ Prefix (/ pre1)
-Path string (/desc.xml)

After S109, the Client A 420 acquires the device description and the service description, acquires the content list, and acquires the content for the Server A 520 via the HTTP server of the HGWA 410.
FIG. 5 shows an example of an outline of a message when the client A 420 acquires content. The HTTP request line 801 includes the following contents. Other configurations are omitted.
・ Method: POST (GET for description)
URI: Prefix (/ pre1) and path character string (ControlURL / soap described in the device description)
HTTP version: HTTP / 1.1

In S110, HGWA 410 transmits the message from Client A 420 to relay server 100 based on the connection information negotiated when the session was established in S105. The HGWA 410 may change the Host header, the Usr-Agent header, and the like of the HTTP request received from the Client A 420.
In S111, relay server 100 analyzes the request line of the received message and extracts a prefix (802 in FIG. 5). Further, the relay server 100 identifies an entry that matches the extracted prefix from List2-4 of the session information management unit 302, and acquires the LocationURL of the identified entry from List2-5. Furthermore, the relay server 100 also acquires the identifier of the HGW from the List 2-1. The relay server 100 creates a message using the acquired LocationURL. The relay server 100 transmits the created message using the connection information of the connection information List2-2 of the HGWB 510 acquired when the session is established in S105. An example of the outline of the message to be transferred is shown in FIG. The request line 901 is composed of the following contents, and other contents are omitted.
・ Method: POST (same as received method)
URI: Host information (192.168.1.1:5000) corresponding to the prefix (/ pre1), path character string (same as the received path character string)
HTTP version: HTTP / 1.1
The relay server 100 may update the Host header, User-Agent header, and the like of the data received from the HGWA 410.

In S112, HGWB 510 behaves as HTTP Proxy and transfers the received data to Server A 520.
In S113, Server A 520 returns a response including a list of contents managed by the self.
In S114, HGWB 510 behaves as HTTP Proxy and transfers the received data to relay server 100.
In S115, the relay server 100 analyzes the received data and performs data processing according to the analysis result.

FIG. 7 is a flowchart illustrating an example of information processing related to data analysis and data processing.
The relay server 100 receives data from the HGWB 510 (S1001).
The relay server 100 analyzes the received data and confirms whether or not a content list is included in the data (S1002).
If the content list is not included as a result of the analysis in S1002, the relay server 100 ends the process illustrated in FIG. When the content list is included, the relay server 100 confirms whether or not the URL is included in the content list (S1003). The URL is an example of first resource information that identifies the location of the resource.
If the URL is not included in S1003, the relay server 100 ends the process shown in FIG. When the URL is included, the relay server 100 separates the URL into a host part and a path part after the host part, and acquires the host part (S1004).
The relay server 100 confirms whether the host part (IP address and port number) of the URL has already been saved in the session information management unit 302 (S1005).

If not already saved, the relay server 100 newly creates a prefix for identifying the host part (S1006).
The relay server 100 associates the prefix created in S1006 with the host part and stores it in the session information management unit 302 (S1007).
The relay server 100 acquires a prefix corresponding to the host portion acquired in S1004 from the session information management unit 302 (S1008).
The relay server 100 acquires HTTP server information of the HGWA 410 that transfers data received from the HGWB 510 from the session information management unit 302. The relay server 100 converts the host part of the URL included in the content list into HTTP server information of the HGWA 410 stored in the session information management unit 302. Subsequently, the relay server 100 concatenates the prefixes, and then concatenates path character strings after the host part of the original URL to create a URL (S1009).

Returning to the description of FIG. 3, in S <b> 116, the relay server 100 transfers the data after the data processing to the HGWA 410.
In S117, HGWA 410 transfers the received data to Client A 420.
In the above example, the URL conversion process has been described for a series of relay processes for acquiring a content list. However, the relay process is not limited to URL conversion. As an example, in the case of acquiring a device description, the relay server 100 may rewrite the contents of the device description received from the HGWB 510. More specifically, the relay server 100 may add the HGWB 510 identifier or HomeB nickname to the FriendlyName of Server A520. By adding, the user operating the client A 420 can recognize that the server A 520 is connected to the LAN 500 instead of the LAN 400.
In S118, Client A 420 performs resource acquisition for the URL included in the content list received in S117.
Thereafter, from S119 to S125, the same processing as S110 to S117 is performed.
Through the series of processes described above, the relay server 100 analyzes the data transferred from the HGWB 510 to the HGWA 410, and dynamically changes the transfer destination entry stored in the session information management unit 302 for each host that owns the resource. be able to.

FIG. 8 is a sequence diagram showing a message flow when a request is transmitted.
In S201, Client A 420 transmits a request message to Server A 520.
In S202, HGWA 410 transfers the received request message to relay server 100.
In S203 to S209, the relay server 100 or the like returns a response of Server A520 to the request message of Client A420 received from HGWA 410 to HGWA 410.

The processing related to the relay server 100 in S203 to S209 will be described with reference to FIG.
The relay server 100 receives the request message from the HGWA 410 (S1101). The request message is an example of request data.
The relay server 100 checks whether or not the request message received in S1101 is defined in the standard document (S1102). An example of a message defined in a standard document is a SOAP request.
If it is determined in S1102 that the request is specified by the standard document, the relay server 100 checks whether or not a URL is included in the response to the request (S1103). In the case of SOAP, when the SOAPACTION header is included in the HTTP header, the relay server 100 knows that it is an HTTP request defined by SOAP. The relay server 100 can identify a fixed response sentence from the action name. Then, the relay server 100 can confirm whether the URL is included from the standard document.
The relay server 100 transfers the request message received in S1101 to the HGWB 510 (S1104 or S1106).
The relay server 100 receives a response to the request transferred in S1104 or S1106 from the HGWB 510 (S1105 or S1107).
If it is determined in S1103 that the response message includes a URL, the relay server 100 performs the analysis described with reference to FIG. 7 on the received response data (S1108).
The relay server 100 transfers the response message to the HGWA 410 (S1109).

Returning to the description of FIG. 8, in S209 and S210, the relay server 100 or the like transfers the response of the Server A 520 to the Client A 420.
Through the series of processes described above, the relay server 100 does not need to analyze all data. In addition, since it is known in advance what data of the response should be converted when the request is received, the relay server 100 can secure the conversion resource before receiving the response. In addition, when the conversion process is performed in a device different from the relay server 100, it is possible to know to which device data should be transferred before receiving a response. As a result, the processing related to the transfer processing of the relay server 100 can be reduced. Further, when data that cannot be converted is received, or when securing of conversion resources fails, the relay server 100 can return an error response without transferring the data to the HGWB 510. In addition, when data that cannot be converted is received, or when securing of conversion resources fails, the relay server 100 can request a conversion process from a server having another conversion function.

FIG. 10 is a sequence diagram showing a message flow when deleting session information.
In S301, HGWB 510 detects that Server A 520 has left the network. For example, the HGWB 510 detects the disconnection when an SSDP ByeBye request notified from the UPnP device when the network is stipulated by UPnP or when the connection valid time has elapsed.
In S302, HGWB 510 notifies relay server 100 that the separation has been detected. The contents of the leaving information to be notified include the host information of the Location URL of the Server information or an identifier such as UUID.
In S <b> 303, the relay server 100 deletes the corresponding data entry from the information included in the withdrawal information from the device information management unit 301 and the session information management unit 302. The relay server 100 may transition to the inactive state without deleting the entry.
In S304, relay server 100 and HGWB 510 delete the session established in S105 of FIG. More specifically, the relay server 100 and the HGWB 510 delete the negotiated connection information.
In S305, the relay server 100 deletes all information regarding the HGWB 510 from the device information management unit 301 and the session information management unit 302. The relay server 100 may transition to the inactive state without deleting the information.
Through the series of processes described above, the lifetime of data managed by the data management apparatus can be managed.

FIG. 11 is a sequence diagram showing a message flow when session information is changed.
In S401, HGWB 510 detects that the IP address of Server A 520 has been changed.
In S402, HGWB 510 notifies relay server 100 that a change has been detected. The contents of the changed information to be notified include the contents of the changed information and the host information of the location URL of the server information, or an identifier such as a UUID.
In S403, the relay server 100 updates the entry of the corresponding data from the information included in the change information to the device information management unit 301 and the session information management unit 302.
In the present embodiment, the description has been given of two sites, HomeA and HomeB, but the same applies to three or more sites.

<Other embodiments>
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  As described above, according to each of the above-described embodiments, it is possible to reduce information creation and management costs related to a transfer destination to be managed, and to acquire resources in different home networks.

100 relay server, 200 SIP server, 300 data management device

Claims (14)

A relay device that relays a first network including a first communication device and a second network including a second communication device and a data providing device;
Analyzing means for analyzing whether or not the data received from the second communication device includes first resource information for specifying a location of a resource provided by the data providing device;
As a result of the analysis, when first resource information for specifying a location of a resource provided by the data providing device is included, an acquisition unit that obtains host information of the data providing device from the first resource information; ,
Creating means for creating second resource information obtained by converting host information of the data providing device into host information of the relay device;
First transfer means for transferring data obtained by rewriting the first resource information included in the data received from the second communication device to the second resource information to the first communication device;
A relay device. Storage means for associating host information of the relay device and host information of the data providing device in association with each other,
When request data including the second resource information is received from the first communication device, the second resource information is acquired from the request data, and the related information including the second resource information is specified. Second transfer means for transferring the request data to the host information device included in the identified related information;
The relay device according to claim 1, further comprising: Based on the request data, further comprising determining means for determining whether or not the first resource information is included in data received from the second communication device in response to the request data;
The first transfer means is the case where the determination means determines that the first resource information is not included in the data received from the second communication device according to the request data, and the data The relay apparatus according to claim 2, wherein when the data is received from the second communication apparatus, the processing by the analysis unit is omitted and the data is transferred to the first communication apparatus.   The determination means includes the first resource information in data received from the second communication device according to the request data, depending on whether the request data is data defined in a standard document. The relay device according to claim 3, which determines whether or not.   The determination means depends on whether or not the request data is data defined in a standard document and whether or not the request data requests data including the first resource information as a response. The relay apparatus according to claim 3, wherein it is determined whether or not the first resource information is included in data received from the second communication apparatus according to the request data.   The relay apparatus according to claim 2, further comprising a deletion unit that deletes the related information when a session between the first communication apparatus and the second communication apparatus is deleted. Analyzing means for analyzing whether or not the data received from the second communication device of the second network includes the first resource information specifying the location of the resource provided by the data providing device of the second network When,
As a result of the analysis, when first resource information for specifying a location of a resource provided by the data providing device is included, an acquisition unit that obtains host information of the data providing device from the first resource information; ,
Creating means for creating second resource information obtained by converting host information of the data providing device into host information of a relay device;
First transfer means for transferring data obtained by rewriting the first resource information included in the data received from the second communication device to the second resource information to the first communication device of the first network; ,
A communication system. Storage means for associating host information of the relay device and host information of the data providing device in association with each other,
When request data including the second resource information is received from the first communication device, the second resource information is acquired from the request data, and the related information including the second resource information is specified. Second transfer means for transferring the request data to the host information device included in the identified related information;
The communication system according to claim 7, further comprising: An information processing method executed by a relay device that relays a first network including a first communication device and a second network including a second communication device and a data providing device,
An analysis step of analyzing whether or not the data received from the second communication device includes first resource information that specifies a location of a resource provided by the data providing device;
An acquisition step of acquiring host information of the data providing device from the first resource information when the first resource information specifying the location of the resource provided by the data providing device is included as a result of the analysis; ,
A creation step of creating second resource information obtained by converting host information of the data providing device into host information of the relay device;
A first transfer step of transferring data obtained by rewriting the first resource information included in data received from the second communication device to the second resource information to the first communication device;
An information processing method including: A storage step of associating and storing the host information of the relay device and the host information of the data providing device as related information;
When request data including the second resource information is received from the first communication device, the second resource information is acquired from the request data, and the related information including the second resource information is specified. A second transfer step of transferring the request data to the host information device included in the identified related information;
The information processing method according to claim 9, further comprising: An information processing method executed by a communication system,
An analysis step of analyzing whether or not the data received from the second communication device of the second network includes the first resource information for specifying the position of the resource provided by the data providing device of the second network When,
An acquisition step of acquiring host information of the data providing device from the first resource information when the first resource information specifying the location of the resource provided by the data providing device is included as a result of the analysis; ,
A creation step of creating second resource information obtained by converting host information of the data providing device into host information of a relay device;
A first transfer step of transferring data obtained by rewriting the first resource information included in the data received from the second communication device to the second resource information to the first communication device of the first network; ,
An information processing method including: A storage step of associating and storing the host information of the relay device and the host information of the data providing device as related information;
When request data including the second resource information is received from the first communication device, the second resource information is acquired from the request data, and the related information including the second resource information is specified. A second transfer step of transferring the request data to the host information device included in the identified related information;
The information processing method according to claim 11, further comprising: A computer that relays a first network including a first communication device and a second network including a second communication device and a data providing device;
An analysis step for analyzing whether or not the data received from the second communication device includes first resource information for specifying a location of a resource provided by the data providing device;
An acquisition step of acquiring host information of the data providing apparatus from the first resource information when the first resource information specifying the position of the resource provided by the data providing apparatus is included as a result of the analysis; ,
Creating a second resource information obtained by converting host information of the data providing device into host information of the computer;
A first transfer step of transferring data obtained by rewriting the first resource information included in data received from the second communication device to the second resource information to the first communication device;
A program for running A storage step of associating and storing the host information of the computer and the host information of the data providing device as related information
When request data including the second resource information is received from the first communication device, the second resource information is acquired from the request data, and the related information including the second resource information is specified. A second transfer step of transferring the request data to the host information device included in the specified related information;
14. The program according to claim 13, for further executing

Images