Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20070233844 A1
Publication typeApplication
Application numberUS 11/723,466
Publication dateOct 4, 2007
Filing dateMar 20, 2007
Priority dateMar 29, 2006
Also published asUS8499083, US20120102205
Publication number11723466, 723466, US 2007/0233844 A1, US 2007/233844 A1, US 20070233844 A1, US 20070233844A1, US 2007233844 A1, US 2007233844A1, US-A1-20070233844, US-A1-2007233844, US2007/0233844A1, US2007/233844A1, US20070233844 A1, US20070233844A1, US2007233844 A1, US2007233844A1
InventorsYoshifumi Tanimoto
Original AssigneeMurata Kikai Kabushiki Kaisha
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Relay device and communication system
US 20070233844 A1
Abstract
A relay device requests a status notification of another relay device to a server device. When the relay device is notified that the other relay device is under a logged-out status, the relay device stands by. When the relay device is notified that the other relay device has logged in, the relay device transmits a connection request to the server device. The server device relays the connection request to the other relay device. A response is transmitted from the other relay device to the server device, and further relayed to the relay device. Accordingly, a TCP connection is established between the relay device and the other relay device. A communication device connected to a different network can transmit and receive data to and from the relay device via the other relay device.
Images(16)
Previous page
Next page
Claims(15)
1. A communication system in which data is relayed between terminals, the communication system comprising:
a first relay device which carries out communication with a first communication device;
a server device; and
a second relay device which carries out communication with a second communication device,
wherein the first relay device includes:
a holding unit which inquires a status of the second relay device to the server device, and when the second relay device is capable of accepting a connection, carries out a connection request to the second relay device and dynamically establishes a relay connection with the second relay device and holds the established relay connection, and
a relay unit which relays data received from the first communication device to the second relay device so that the second relay device further relays the data to the second communication device.
2. The communication system according to claim 1, wherein the first communication device and the second communication device are provided in different private networks, and a connection request for establishing a transmission control protocol connection cannot be carried out from an external network to the first communication device and the second communication device.
3. A relay device which can carry out communication with a first communication device and a server device, the relay device comprising:
a relay unit which relays data received from the first communication device to another relay device; and
a holding unit which inquires a status of the other relay device to the server device, and when the other relay device is capable of accepting a connection, carries out a connection request to the other relay device, dynamically establishes a relay connection with the other relay device and holds the established relay connection,
wherein the other relay device can carry out communication with a second communication device, and the relay unit relays the data received from the first communication device to the other relay device so that the data is further relayed to the second communication device.
4. The relay device according to claim 3, wherein the holding unit establishes and holds relay connections with a plurality of other relay devices, and the relay unit uses a plurality of the relay connections to relay the data to the plurality of the other relay devices.
5. The relay device according to claim 4, wherein the holding unit separately disconnects the relay connections held with the plurality of the other relay devices.
6. A communication system in which data is relayed between terminals, the communication system comprising:
a first relay device which can carry out communication with a first communication device;
a server device; and
a second relay device which can carry out communication with a second communication device,
wherein the first relay device includes:
an accepting unit which accepts a relay instruction of data designating the second relay device from the first communication device, and
a holding unit which inquires a status of the second relay device to the server device, and when the second relay device is capable of accepting a connection, carries out a connection request to the second relay device, dynamically establishes a relay connection with the second relay device, and holds the established relay connection,
wherein the first relay device relays the data received from the first communication device to the second relay device so that the second relay device further relays the data to the second communication device.
7. The communication system according to claim 6, wherein the first communication device and the second communication device are provided indifferent private networks, and a connection request for establishing a transmission control protocol connection cannot be carried out from an external network to the first communication device and the second communication device.
8. A relay device which can carry out communication with a first communication device, the relay device comprising:
an accepting unit which accepts a relay transmission instruction designating another relay device from the first communication device; and
a holding unit which inquires a status of the other relay device to the server device, and when the other relay device is capable of accepting a connection, carries out a connection request to the other relay device, dynamically establishes a relay connection with the other relay device and holds the established relay connection,
wherein the other relay device can carry out communication with a second communication device, and the relay device relays data received from the first communication device to the other relay device so that the data is further relayed to the second communication device.
9. The relay device according to claim 8, wherein when the other relay device is incapable of accepting a connection, the holding unit notifies a connection impossible state to the first communication device, and when the holding unit receives a notification from the server device that the other relay device can accept a connection, the holding unit notifies a connection possible-state to the first communication device.
10. The relay device according to claim 8, wherein only data having the first communication device as a transmitter or a transmission destination is relayed over the relay connection held by the holding unit.
11. The relay device according to claim 9, wherein only data having the first communication device as a transmitter or a transmission destination is relayed over the relay connection held by the holding unit.
12. A communication system in which data is relayed between terminals, the communication system comprising:
a first relay device which can carry out communication with a first communication device;
a server device; and
a second relay device which can carry out communication with a second communication device,
wherein the first relay device includes:
an accepting unit which accepts a relay transmission instruction of data designating the second relay device from the first communication device, and
a holding unit, when a relay connection is yet to be established with the second relay device, the holding unit inquires a status of the second relay device to the server device, and when the second relay device is capable of accepting a connection, the holding unit dynamically establishes a relay connection with the second relay device and holds the established relay connection, and when the relay connection is already established with the second relay device, the holding unit sets so that the first communication device shares the already established relay connection,
wherein the first relay device relays data received from the first communication device to the second relay device, and the second relay device further relays the data to the second communication device.
13. The communication system according to claim 12, wherein the first communication device and the second communication device are provided in different private networks, and a connection request for a transmission control protocol connection cannot be carried out from an external network to the first communication device and the second communication device.
14. A relay device, which can carry out communication with a first communication device, the relay device comprising:
an accepting unit which accepts a relay transmission instruction designating another relay device from the first communication device; and
a holding unit, when a relay connection is yet to be established with the other relay device, the holding unit inquires a status of the other relay device to a server device, and when the other relay device is capable of accepting a connection, the holding unit dynamically establishes a relay connection with the other relay device and holds the established relay connection, and when the relay connection is already established with the other relay device, the holding unit sets so that the first communication device shares the already established relay connection,
wherein the other relay device can carry out communication with the second communication device, and the relay device relays data received from the first communication device to the other relay device so that the data is further relayed to the second communication device.
15. The relay device according to claim 14, wherein when receiving a notification from the first communication device to terminate a relay transmission being carried out to the other relay device, in case another communication device is carrying out a relay transmission to the other relay device, the holding unit holds the relay connection with the other relay device, and in case none of other communication devices is carrying out a relay transmission to the other relay device, the holding unit disconnects the relay connection established with the other relay device.
Description
    BACKGROUND OF THE INVENTION
  • [0001]
    1. Field of the Invention
  • [0002]
    The present invention relates to technology for relaying data transmitted and received between communication devices.
  • [0003]
    2. Description of the Related Art
  • [0004]
    By using technology such as a Virtual Private Network (VPN) and tunneling, data transmitted from a terminal located inside a private network can be relayed to a terminal located in another private network via the Internet. For example, by establishing a connection between a Local Area Network (LAN) of a headquarter office and a LAN of a branch office via the VPN, data can be relayed between terminals connected to different LANs via the Internet.
  • [0005]
    According to known technology, data is relayed between local systems connected via the Internet. According to this technology, each terminal located within a local system accesses a relay server on the Internet to establish a Transmission Control Protocol (TCP) connection, and uses the established TCP connection to transmit and receive data between the local systems.
  • [0006]
    By using the technology of the VPN and the tunneling, data can be transmitted and received between different LANs connected via the Internet. However, such technology provides a system which is constructed by a fixed setting. That is, a relay device provided on the Internet between the LANs carries out a fixed connection setting between the LANs. Therefore, there is no problem when a VPN connection is preferably established constantly between a headquarter office and a branch office of a company, for example. However, the above-described technology cannot support a case in which a connection is to be established dynamically between different private networks.
  • [0007]
    The technology such as the VPN is basically technology for establishing a connection between networks, for example, between a LAN and a LAN, and is not technology for establishing a connection between individual terminals. Therefore, the technology such as the VPN is technology for enabling communication to be carried out between networks in which the VPN is developed as an infrastructure, and is not technology for supporting a case in which an individual personally demands a communication with a specific network.
  • [0008]
    Meanwhile, when constructing a system in which a connection is established between networks in response to a request from individual terminals, performance of a relay device may decrease due to a fact that resources may become insufficient when a plurality of connections are generated according to the request from terminals.
  • SUMMARY OF THE INVENTION
  • [0009]
    In order to overcome the problems described above, preferred embodiments of the present invention provide a system in which relaying of data between networks connected via the Internet can be set dynamically.
  • [0010]
    Preferred embodiments of the present invention also provide a system in which relaying of data between networks connected via the Internet can be set dynamically according to a request of each terminal.
  • [0011]
    According to an aspect of the present invention, a relay device can carry out communication with a first communication device, and includes a relay unit and a holding unit. The relay unit relays data received from the first communication device to another relay device. The holding unit inquires a status of the other relay device to a server device. When the other relay device is capable of accepting a connection, the holding unit carries out a connection request to the other relay device, dynamically establishes a relay connection with the other relay device, and holds the established relay connection. The other relay device can carry out communication with a second communication device. The relay device relays the data received from the first communication device to the other relay device to further relay the data to the second communication device.
  • [0012]
    The holding unit also establishes relay connections with a plurality of relay devices, and the relay unit uses the plurality of the relay connections to relay the data to the plurality of the relay devices.
  • [0013]
    The holding unit can separately disconnect the relay connections held with the plurality of the relay devices.
  • [0014]
    According to another aspect of the present invention, a communication system for relaying data between terminals includes a first relay device that can carry out communication with a first communication device, a server device, and a second relay device that can carry out communication with a second communication device. The first relay device includes a holding unit. When the holding unit inquires a status of the second relay device to the server device and the second relay device is capable of accepting a connection, the holding unit carries out a connection request to the second relay device, dynamically establishes a relay connection with the second relay device, and holds the established relay connection. The first relay device relays data received from the first communication device to the second relay device, and the second relay device further relays the data to the second communication device.
  • [0015]
    The first communication device and the second communication device are respectively provided in different private networks. Accordingly, a connection request for a TCP connection cannot be carried out to the first communication device and the second communication device from an external network.
  • [0016]
    According to another aspect of the present invention, a relay device can carry out communication with a first communication device. The relay device includes an accepting unit and a holding unit. The accepting unit accepts a relay transmission instruction designating another relay device from the first communication device. The holding unit inquires a status of the other relay device to the server device. When the other relay device is capable of accepting a connection, the holding unit carries out a connection request to the other relay device, dynamically establishes a relay connection with the other relay device, and holds the established relay connection. The other relay device can carry out communication with a second communication device. The relay device relays data received from the first communication device to the other relay device, and the other relay device further relays the data to the second communication device.
  • [0017]
    When the other relay device is incapable of accepting a connection, the holding unit notifies such a connection impossible state to the first communication device. When the holding unit receives a notification from the server device that the other relay device has become capable of accepting a connection, the holding unit notifies a connection possible state to the first communication device.
  • [0018]
    Only data, which has the first communication device as a transmitter or a transmission destination, is relayed over the relay connection held by the holding unit.
  • [0019]
    According to another aspect of the present invention, a communication system for relaying data between terminals includes a first relay device that can carry out communication with a first communication device, a server device, and a second relay device that can carry out communication with a second communication device. The first relay device includes an accepting unit and a holding unit. The accepting unit accepts a relay instruction of data designating the second relay device from the first communication device. The holding unit inquires a status of the second relay device to the server device. When the second relay device is capable of accepting a connection, the holding unit carries out a connection request to the second relay device, dynamically establishes a relay connection with the second relay device, and holds the established relay connection. The first relay device relays data received from the first communication device to the second relay device so that the second relay device can further relay the data to the second communication device.
  • [0020]
    The first communication device and the second communication device are respectively provided in different private networks. A connection request for a TCP connection cannot be carried out to the first communication device and the second communication device from an external network.
  • [0021]
    According to another aspect of the present invention a relay device can carry out communication with a first communication device. The relay device includes an accepting unit and a holding unit. The accepting unit accepts a relay transmission instruction designating another relay device from the first communication device. When a relay connection has not been established yet with the other relay device, the holding unit inquires a status of the other relay device to the server device. When the other relay device is capable of accepting a connection, the holding unit dynamically establishes a relay connection with the other relay device, and holds the established relay connection. When a relay connection is already established with the other relay device, the holding unit sets such relay connection to be shared with the first communication device. The other relay device can carry out communication with the second communication device. The relay device relays data received from the first communication device to the other relay device, and the other relay device further relays the data to the second communication device.
  • [0022]
    When receiving a notification from the first communication device to terminate the relay transmission to the other relay device, if the other communication device is carrying out a relay transmission to the other relay device, the relay connection established between the relay device and the other relay device is maintained. When none of the communication devices is carrying out a relay transmission to the other relay device, the holding unit disconnects the relay connection held with the other relay device.
  • [0023]
    According to another aspect of the present invention, a communication system for relaying data between terminals includes a first relay device that can carry out communication with a first communication device, a server device, and a second relay device that can carry out communication with the second communication device. The first relay device includes an accepting unit and a holding unit. The accepting unit accepts a relay transmission instruction of data designating the second relay device from the first communication device. When a relay connection is yet to be established with the second relay device, the holding unit inquires a status of the second relay device to the server device. When the second relay device is capable of accepting a connection, the holding unit dynamically establishes a relay connection with the second relay device and holds the established relay connection. When a relay connection is already established with the second relay device, the holding unit sets such relay connection to be shared with the first communication device. The first relay device relays data received from the first communication device to the second relay device, and the second relay device further relays the data to the second communication device.
  • [0024]
    The first communication device and the second communication device are respectively provided in different private networks. A connection request for a TCP connection cannot be carried out to the first communication device and the second communication device from an external network.
  • [0025]
    The relay device of the present invention inquires a status of another relay device to the server device. When the other relay device is capable of accepting a connection, the relay device carries out a connection request, and establishes and holds a relay connection with the other relay device. Therefore, a communication device, which can carry out communication with the relay device, can carry out communication via the private network with a communication device, which can carry out communication with the other relay device.
  • [0026]
    The relay device of the present invention can establish a relay connection with a plurality of relay devices, and hold the established relay connections. Therefore, when communication devices to which communication is to be carried out belong to different networks, a plurality of connections can be generated independently.
  • [0027]
    The relay device of the present invention can independently disconnect each of the relay connections being held with a plurality of the relay devices. Therefore, the relay device of the present invention can maintain only the connections that are necessary for communication, and resources can be utilized efficiently.
  • [0028]
    The relay device of the present invention accepts a relay transmission instruction designating the other relay device from the first communication device, and inquires a status of the other relay device to the server device. When the other relay device is capable of accepting a connection, the relay device dynamically establishes a relay connection with the other relay device and holds the established relay connection. Therefore, by carrying out a request designating a relay destination to the relay device of the present invention, a communication device, which can carry out communication with the relay device of the present invention, can carry out communication with a communication device, which can carry out communication with the other relay device. Since a connection is established between the relay devices according to a request from the communication device, a network of a communication destination can be selected and a connection can be established more dynamically.
  • [0029]
    When receiving a notification from the server device that the other relay device has become capable of accepting a connection, the relay device notifies a connection possible state to the first communication device. Accordingly, at a point of time when a preparation is completed at the relay destination, a relay transmission can be started immediately.
  • [0030]
    Only the data having the first communication device as a transmitter or a transmission destination is relayed over the relay connection held by the holding unit. Therefore, a terminal, which has carried out a connection request to the relay device, can exclusively use the established connection.
  • [0031]
    The relay device of the present invention accepts a relay transmission instruction designating another relay device from the first communication device. When a relay connection is already established between the relay device of the present invention and the other relay device, the relay device of the present invention sets the first communication device to share the already established relay connection. Therefore, by carrying out a request designating a relay destination to the relay device of the present invention, a communication device, which can carry out communication with the relay device of the present invention, can carry out communication with a communication device, which can carry out communication with the other relay device. When a relay connection is already established between the relay device of the present invention and the designated relay device, the already established relay connection is shared. Therefore, processing load for establishing a connection can be reduced, and resources can be saved.
  • [0032]
    When receiving a notification from the first communication device to terminate the relay transmission to the other relay device, if the other communication device is carrying out a relay transmission to the other relay device, the relay connection established with the other relay device is maintained. Accordingly, an end of communication of one communication device does not influence a communication of another communication device. A communication device sharing the relay connection can use the relay connection until the communication of the communication device itself is completed.
  • [0033]
    Other features, elements, processes, steps, characteristics and advantages of the present invention will become more apparent from the following detailed description of preferred embodiments of the present invention with reference to the attached drawings.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0034]
    FIG. 1 illustrates a configuration of a communication system according to a first preferred embodiment of the present invention.
  • [0035]
    FIG. 2 illustrates a registration example of a relay device database.
  • [0036]
    FIG. 3 is a flowchart illustrating a processing carried out in the communication system according to the first preferred embodiment of the present invention.
  • [0037]
    FIG. 4 is a flowchart illustrating a processing carried out in the communication system focusing on a relay device.
  • [0038]
    FIG. 5 is a flowchart illustrating a processing carried out in the communication system focusing on a relay device.
  • [0039]
    FIG. 6 illustrates an imaginary state in which a plurality of relay connections are established.
  • [0040]
    FIG. 7 illustrates a configuration of a communication system according to a second preferred embodiment of the present invention.
  • [0041]
    FIG. 8 illustrates a registration example of a relay connection database.
  • [0042]
    FIG. 9 is a flowchart illustrating a processing carried out in the communication system according to the second preferred embodiment of the present invention.
  • [0043]
    FIG. 10 is a flowchart illustrating a processing carried out in the communication system focusing on a relay device.
  • [0044]
    FIG. 11 is a flowchart illustrating a processing carried out in the communication system focusing on a relay device.
  • [0045]
    FIG. 12 illustrates a registration example of a relay connection database.
  • [0046]
    FIG. 13 is a flowchart illustrating a processing carried out in a communication system according to a third preferred embodiment of the present invention.
  • [0047]
    FIG. 14 is a flowchart illustrating a processing carried out in the communication system focusing on a relay device.
  • [0048]
    FIG. 15 is a flowchart illustrating a processing carried out in the communication system focusing on a relay device.
  • DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS First Preferred Embodiment
  • [0049]
    Preferred embodiments of the present invention will be described with reference to the accompanying drawings. FIG. 1 illustrates a configuration of a communication system according to a first preferred embodiment. In the communication system of the first preferred embodiment, two Local Area Networks (LANs) 10 and 20 are connected via a Wide Area Network (WAN) 30. For example, the LANs 10 and 20 are an in-house LAN of a company, and the WAN 30 is a public network such as the Internet. That is, two different private LANs 10 and 20 are connected via a public network such as the Internet.
  • [0050]
    As illustrated in FIG. 1, two communication devices 11 and 12 and a relay device 15 are connected in the LAN 10. The LAN 10 is connected to the WAN 30 via a gateway (GW) 16. Two communication devices 21 and 22 and a relay device 25 are connected in the LAN 20. The LAN 20 is connected to the WAN 30 via a gateway 26.
  • [0051]
    The communication devices 11 and 12 are terminals such as personal computers, and include a network function. Specifically, each of the communication devices 11 and 12 includes a Transmission Control Protocol/Internet Protocol (TCP/IP), and uses the TCP/IP to carry out communication with the relay device 15 and other computers or the like connected to the LAN 10. In the same manner, each of the communication devices 21 and 22 includes a TCP/IP, and uses the TCP/IP to carry out communication with the relay device 25 and other computers or the like connected to the LAN 20. The relay devices 15 and 25 and the gateways 16 and 26 can also carry out communication by the TCP/IP.
  • [0052]
    A server device 35 is connected to the WAN 30. As described above, the WAN 30 is a public network such as the Internet. Therefore, a terminal connected to the LAN 10, the LAN 20, or the WAN 30 can establish a TCP connection by designating a global IP address of the server device 35.
  • [0053]
    A private IP address is assigned to the communication devices 11 and 12 and the relay device 15 connected to the LAN 10 and the communication devices 21 and 22 and the relay device 25 connected to the LAN 20. The gateways 16 and 26 function as a firewall, and a connection cannot be established directly from an external network by designating a terminal located inside of the network. Therefore, a terminal or the like connected to the WAN 30 has restrictions when carrying out a TCP connection request to the relay device 15 or 25. In the first preferred embodiment, since the server device 35 functions as a Session Initiation Protocol (SIP) server (a proxy server and a registered server of the SIP) as to be described hereinafter, the gateways 16 and 26 are set such that communication designating a specific port corresponding to the relay servers 15 and 25 can be carried out to the gateways 16 and 26, respectively.
  • [0054]
    FIG. 2 illustrates a registration example of a relay device database 351 managed by the server device 35. In the example illustrated in FIG. 2, three relay devices A, B, and C are registered. The relay devices A, B, and C are device names that are assigned to the relay device 15 or the relay device 25, for example. Flags of a Uniform Resource Locator (URL), an IP address, and a login status are set for each of the relay devices A, B, and C.
  • [0055]
    An IP address of each of the relay devices registered in the relay device database 351 is not an IP address in a private network, but is a global IP address converted by a gateway by a function such as a Network Address Translation (NAT) or an IP masquerade. For example, the relay device 15 is assigned with a private address in the LAN 10. When the relay device 15 accesses the server device 35, the IP address assigned to the relay device 15 is converted into a global IP address by the gateway 16.
  • [0056]
    Each of the relay devices A through C establishes a connection with the server device 35, and logs into the server device 35. A “status” field of the relay device database 351 stores information indicating whether each of the relay devices A through C is currently under a logged-in status or a logged-out status with respect to the server device 35. When each of the relay devices is under a logged-in status, the server device 35 determines that a TCP connection is prepared to be established between the logged-in relay devices. In other words, a status in which the relay device is logged in the server device 35 indicates a status in which the relay device is capable of accepting a TCP connection request transmitted from another terminal.
  • [0057]
    With reference to FIG. 3 through FIG. 5, a description will be made of a flow of a communication processing in the above-described communication system. FIG. 3 illustrates a flow of the processing of the entire communication system including the relay devices 15 and 25 and the server device 35. Further, in the following description, a Session Initiation Protocol (SIP) is used for communication between the relay device 15 and the server device 35, and between the relay device 25 and the server device 35. However, other protocols may also be used.
  • [0058]
    Each of the relay devices 15 and 25 transmits a “REGISTER request message” of the SIP to the server device 35 at initialization or periodically to notify position information (for example, an IP address, and/or a port number) of the relay device to the server device 35. The server device 35 manages the relay device database 351 illustrated in FIG. 2 according to the notified position information. The server device 35 can carry out communication with each of the relay devices over the gateway according to the position information. In FIG. 3, under an initial state, the relay device 15 and the relay device 25 are logged in the server device 35. First, the relay device 25 notifies logout status information to the server device 35 (step S101), and the server device 35 responds to the notification (step S102). The server device 35 executes a logout processing of the relay device 25, and updates the “status” field of the relay device 25 in the relay device database 351 to “logout”.
  • [0059]
    Under this state, when the relay device 15 carries out a notification request of the status information to the server device 35 (step S103), the server device 35 carries out a response (step S104), and notifies that the relay device 25 is logged-out (step S105). The relay device 15 responds to this notification (step S106).
  • [0060]
    Next, the relay device 25 notifies login status information to the server device 35 (step S107), and the server device 35 responds to the notification (step S108). The server device 35 executes the login processing of the relay device 25, and updates the “status” field of the relay device database 351 to “login”. Furthermore, the server device 35 notifies the relay device 15 that the relay device 25 has logged in (step S109). The relay device 15 responds to this notification (step S110).
  • [0061]
    When the relay device 15 receives a notification that the relay device 25 has logged in, the relay device 15 transmits a connection request for the relay device 25 to the server device 35 (step S111). As illustrated in FIG. 3, this connection request is an “INVITE request message” of the SIP, and includes TCP connection information in a body portion following a blank line. In the illustrated example, the connection request includes an IP address (200.1.1.1) and a TCP port number (6109) or the like of the relay device 15 (transmitter). The server device 35 relays the connection request to the relay device 25 (step S112). The relay device 25, which has received the connection request, transmits a response to the server device 35 to permit a connection (step S113). As illustrated in FIG. 3, this response is “200 OK response message” of the SIP, and includes TCP connection information in a body portion following a blank line. In the illustrated example, the response includes an IP address (200.2.2.2) and a TCP port number (7109) or the like of the relay device 25 (transmitter). The server device 35 relays the response to the relay device 15 (step S114). As described above, the relay device 15 and the relay device 25 use the INVITE request and the OK response of the SIP to exchange TCP connection information, and carry out a negotiation for establishing a TCP connection. When the relay device 15 receives the response, the relay device 15 transmits a TCP connection request to the relay device 25 (step S115). Accordingly, a TCP connection is established between the relay device 15 and the relay device 25.
  • [0062]
    The above-described processing is executed by a network administrator of the LAN 10 or the LAN 20, for example. That is, in order to prepare such that a connection with another LAN can be carried out dynamically, a relay device in a network is logged into the server device 35 by the network administrator as illustrated at step S107. Accordingly, a preparation is completed for receiving a TCP connection request from another relay device. When the network administrator wishes to carry out a connection with another LAN, the network administrator accesses the server device 35, and acquires status of a destination relay device. When the network administrator learns that the destination relay device is under a logged-in status, the network administrator transmits a connection request to the server device 35.
  • [0063]
    That is, in the present preferred embodiment, the relay device 15 transmits an INVITE request of the SIP via the server device 35 to establish a TCP connection (media session) for relaying. In other words, since a relay channel as a media session is generated by a call control protocol, a relay communication channel can be established dynamically.
  • [0064]
    When a TCP connection is established between the relay device 15 and the relay device 25 as described above, the relay device 15 and the relay device 25 hold the established TCP connection. When the relay device 15 receives data from the communication device 11, 12 or the like to be transmitted to the communication device 21, 22 or the like, the relay device 15 relays the received data to the relay device 25 (step S116). The relay device 25 further relays the relayed data to the communication device 21, 22 or the like. Data transmitted from the communication device 21, 22 or the like is also relayed to the communication device 11, 12, or the like via the relay device 25 and the relay device 15 (step S117).
  • [0065]
    Further, in order to carry out communication between the LAN 10 and the LAN 20 via the WAN 30, each of the relay devices 15 and 25 manages a list of device names of communication devices connected to each of the LANs 10 and 20, respectively. When a TCP connection is established between the relay device 15 and the relay device 25, the relay device 15 and the relay device 25 exchange the list. When carrying out communication between a communication device connected to the LAN 10 and a communication device connected to the LAN 20, a device name of a relay device of a LAN of a transmission destination and a device name of a communication device of the transmission destination are designated. That is, since a unique device name (registered in the relay device database 351) is assigned to a relay device using such a communication system, by designating both the device name of the relay device and the device name of the communication device, the communication device of the transmission destination can be identified uniquely. For example, a name such as “communication device name@relay device name” may be used. Each relay device knows an association between a communication device name and an IP address for a communication device connected to the LAN to which the relay device itself is also connected. Therefore, the relay device can relay data to a communication device designated by “communication device name@relay device name”.
  • [0066]
    When transmission and reception of data between the communication devices end and the connection established between the relay device 15 and the relay device 25 becomes unnecessary, the network administrator disconnects the connection. First, the relay device 15 transmits a disconnection request for the relay device 25 to the server device 35 (step S118). The server device 35 relays the disconnection request to the relay device 25 (step S119). A response from the relay device 25 is transmitted to the server device 35 (step S120), and relayed to the relay device 15 (step S121).
  • [0067]
    FIG. 4 is a flowchart focusing on a processing carried out by the relay device 15 in the processing described with reference to FIG. 3. First, the relay device 15 transmits a starting request for starting a relay connection to the server device 35 (step S201). The relay-device 25 is designated as the relay destination in the starting request. When a fact that the relay device 25 of the relay destination is logged out becomes apparent from the response from the server device 35 (step S202: NO), the relay device 15 stands by until receiving a login notification (step S203). When receiving a login notification (step S203: YES), the process proceeds onto step S204.
  • [0068]
    When a determination is made at step S202 that the relay device 25 of the relay destination is logged in, the relay device 15 generates TCP connection information (step S204), and transmits a connection request (step S205). Then, the relay device 15 stands by for a response from the relay device 25 (step S206). When receiving a response (step S206: YES), the relay device 15 analyzes the TCP connection information included in the received response (step S207). That is, the relay device 15 acquires port number information or the like included in the response transmitted from the relay device 25. Then, the relay device 15 carries out a TCP connection with the relay device 25 (step S208).
  • [0069]
    Under a state in which a TCP connection is established and held, when the communication device 11 or the like transmits relay data (step S209: YES), the relay device 15 relays the data to the communication device 21 or the like (step S210). When the relay device 15 receives relay data to be relayed to the communication device 11 or the like (step S211: YES), the relay device 15 relays the data to the communication device 11 or the like of the relay destination (step S212). When the relay device 15 receives a disconnection request from the relay device 25 (step S213: YES), the relay device 15 transmits a response (step S214) and disconnects the TCP connection (step S215).
  • [0070]
    When a disconnection request is carried out by a network administrator of the LAN 10 (step S216: YES), the relay device 15 transmits a disconnection request to the relay device 25 (step S217). When the relay device 15 receives a response (step S218: YES), the relay device 15 disconnects the TCP connection (step S219).
  • [0071]
    FIG. 5 is a flowchart focusing on a processing carried out by the relay device 25 in the processing described with reference to FIG. 3. First, a network administrator of the LAN 20 determines whether or not to prepare for establishing a connection with another LAN. When preparing for establishing a connection with another LAN, an operation is performed for validating a relay function of the relay device 25. When the relay function is validated (step S301: YES), the relay device 25 transmits a login command to the server device 35 (step S302). Then, the relay device 25 receives a response from the server device 35 (step S303), and a processing for validating the relay function is completed.
  • [0072]
    As described above, when the relay device 25 of the relay destination is under a logged-in status, that is, when the relay device 25 is capable of accepting a connection, the relay device 15 dynamically establishes a TCP connection with the relay device 25. Accordingly, data can be transmitted and received via the WAN 30 such as the Internet. For example, in case of a headquarter office and a branch office of a company where traffic constantly generates stably, LANs may be connected fixedly by using the conventionally used VPN. Meanwhile, when carrying out data communication by establishing connections with different networks via the WAN 30 under any timing, the communication system of the present preferred embodiment can be used.
  • [0073]
    According to the communication system of the present preferred embodiment, when a connection environment (an IP address and/or a port number) of the relay device of the other party is changed, the relay device carries out a negotiation first (steps S111 through S114). Therefore, a connection for relaying data can be established reliably.
  • [0074]
    The relay devices 15 and 25 of the present preferred embodiment can establish a TCP connection with a plurality of relay devices. For example, as illustrated in FIG. 6, the relay device 15 can establish a separate TCP connection with each of three relay devices 25, 45 and 55. A method for establishing a TCP connection with the relay devices 45 and 55 is the same as the processing carried out with respect to the relay device 25. Each of the relay devices 15 and 25 or the like establishes a TCP connection with a plurality of relay devices, and relays data to the plurality of the relay devices. In an example illustrated in FIG. 6, the relay device 15 relays data transmitted from a certain communication device to the relay device 45, and relays data transmitted from another communication device to the relay device 55.
  • [0075]
    A method for disconnecting the TCP connection established with each of the relay devices 45 and 55 is also the same as the processing carried out with respect to the relay device 25. That is, a TCP connection can be established independently with each of the plurality of the relay devices 25, 45, and 55, and the TCP connection can be disconnected independently.
  • [0076]
    Conventionally, in the VPN or the like, when a plurality of LANs are connected, the plurality of the LANs are connected as one VPN. Meanwhile, according to the communication system of the present preferred embodiment, a connection is established independently with just a relay device to which a communication is to be carried out, and a connection established with a relay device to which a communication is no longer necessary to be carried out can be disconnected independently. Therefore, efficient communication system can be constituted without consuming unnecessary resources.
  • Second Preferred Embodiment
  • [0077]
    Next, a second preferred embodiment of the present invention will be described. In the first preferred embodiment, a connection is established dynamically between relay devices according to an instruction from a network administrator. In the second preferred embodiment, a connection is established between relay devices according to a designation from a communication device. Specifically, in the first preferred embodiment, by predicting a status of communication to be generated between the communication devices, a network administrator carries out an operation for establishing or disconnecting a connection between the relay devices. Meanwhile, in the second preferred embodiment, a control is carried out to establish or disconnect a connection between the relay devices more dynamically according to a communication processing that generates from a communication device. In the following description, a description that is the same as the first preferred embodiment will be omitted.
  • [0078]
    FIG. 7 illustrates an example of a configuration of a communication system according to the second preferred embodiment of the present invention. In FIG. 7, a LAN 40 is added to the system configuration illustrated in FIG. 1. The basic system configuration illustrated in FIG. 7 is the same as the first preferred embodiment. A communication device 41 and a relay device 45 are connected to the LAN 40, and the LAN 40 is connected to a WAN 30 via a gateway 46.
  • [0079]
    The relay devices 15, 25, and 45 include relay connection databases 151, 251, and 451, respectively. FIG. 8 illustrates an example of registration of the relay connection database 151 stored in the relay device 15.
  • [0080]
    The relay connection database 151 is a database for managing a TCP connection currently established by the relay device 15. A “client” field stores a setting of a device name of a communication device that has requested a connection to be established with a relay device (hereinafter referred to as a “requesting communication device”). For example, “ClientX” and “ClientY” in FIG. 8 are a device name assigned to the communication device 11, 21 or the like. “Relay destination URL” and “IP address” fields store a setting of a URL and an IP address of a relay device of a relay destination, respectively. “Connection number” field stores a setting of a port number of a generated TCP connection. “Generated time” field stores a setting of time when a TCP connection has been established.
  • [0081]
    In the present preferred embodiment, according to a designation from the requesting communication device, a TCP connection is established with a relay device of a communication destination. However, a device that can use such a TCP connection for carrying out communication is only the requesting communication device. That is, as illustrated in FIG. 8, one-to-one relation is established for a communication device and a TCP connection.
  • [0082]
    The contents of the relay connection databases 251 and 451 are the same as the relay connection databases 151 illustrated in FIG. 8. The relay connection databases 251 and 451 include registration of a status of a TCP connection currently established by the relay devices 25 and 45, respectively.
  • [0083]
    Next, with reference to FIG. 9 through FIG. 11, a description will be made of a flow of a communication processing carried out in the above-described communication system. FIG. 9 illustrates a flow of the processing of the entire communication system including the communication devices 11 and 12, the relay devices 15 and 25, and the server device 35. Further, in the following description, a description will be made of an example in which the SIP is used for the communication between the relay devices 15 and the server device 35 and between the server device 35 and the relay device 25. However, other protocols may also be used.
  • [0084]
    In the same manner as in the first preferred embodiment, each of the relay devices 15 and 25 transmits a “REGISTER request message” of the SIP to the server device 35 at initialization or periodically to notify position information (for example, an IP address and/or a port number) of the relay device to the server device 35. In FIG. 9, under an initial state, the relay device 15 and the relay device 25 are logged in the server device 35. First, the relay device 25 notifies logout status information to the server device 35 (step S401), and the server device 35 responds to the notified logout status information (step S402). The server device 35 executes a logout processing of the relay device 25, and updates the “status” field of the relay device 25 in the relay device database 351 to “logout”.
  • [0085]
    Under this state, the communication device 11 transmits a relay transmission request of data and a status confirmation request, which designate the relay device 25, to the relay device 15 (step S403). When the relay device 15 carries out a notification request of the status information to the server device 35 (step S404), the server device 35 carries out a response (step S405) and notifies the relay device 15 that the relay device 25 is logged out (step S406). The relay device 15 responds to the notification (step S407). Furthermore, the relay device 15 notifies the communication device 11 that the relay device 25 is a logged out (step S408). Accordingly, the communication device 11 stands by until the relay device 25 logs in.
  • [0086]
    Next, the relay device 25 notifies login status information to the server device 35 (step S409), and the server device 35 responds to the notified login status information (step S410). The server device 35 executes a login processing of the relay device 25, and updates the “status” field of the relay device database 351 to “login”. The server device 35 also notifies the relay device 15 that the relay device 25 has logged in (step S411). The relay device 15 responds to the notification (step S412). Furthermore, the relay device 15 notifies the communication device 11 that the relay device 25 has logged in (step S413).
  • [0087]
    When the communication device 11, which has been on standby, receives the notification carried out at step S413, the communication device 11 carries out a relay transmission request again designating the relay device 25 (step S414). Further, in the second preferred embodiment, the communication device 11 is provided to standby until receiving a notification that the relay device 25 has logged in. However, as another preferred embodiment, without standing by for such a notification, the communication device 11 may periodically transmit a relay transmission request to the relay device 15.
  • [0088]
    When the relay device 15 receives the relay transmission request from the communication device 11, the relay device 15 transmits a connection request for the relay device 25 to the server device 35 (step S415). As described in the first preferred embodiment, the connection request is an “INVITE request message” of the SIP, and includes TCP connection information. The server device 35 relays the connection request to the relay device 25 (step S416). When receiving the connection request, the relay device 25 transmits a response to the server device 25 to permit a connection (step S417). As described in the first preferred embodiment, the response is “200 OK response message” of the SIP, and includes TCP connection information. The server device 35 relays the response to the relay device 15 (step S418). The relay device 15 and the relay device 25 exchange the TCP connection information as described above. When receiving the response, the relay device 15 transmits a TCP connection request to the relay device 25 (step S419). Accordingly, a TCP connection is established between the relay device 15 and the relay device 25.
  • [0089]
    The above-described processing is carried out dynamically, for example, when a communication processing from the communication device 11 to the communication device 21 generates. That is, the relay devices are not connected fixedly, but a connection is carried out when traffic generates. However, in order to prepare for a connection request from a relay device of another end, a network administrator is required to be prepared by logging a relay device within a network into the server device 35 as illustrated at step S409.
  • [0090]
    In the present preferred embodiment, the relay device 15 receives an instruction from the communication device 11, and the relay device 15 transmits an INVITE request of the SIP via the server device 35 to establish a relay TCP connection (media session). That is, at a point of time when a connection request from a communication device generates, since a relay channel as a media session is generated by a call control protocol, a relay communication channel can be established dynamically.
  • [0091]
    When a TCP connection is established between the relay device 15 and the relay device 25 as described above, the relay device 15 and the relay device 25 hold the established TCP connection. When the communication device 11 transmits data addressed to the communication device 21, 22 or the like (step S421), the relay device 15 relays the data to the relay device 25 (step S422). The relay device 25 further relays the relayed data to the communication device 21, 22 or the like. The data transmitted from the communication device 21, 22 or the like is relayed to the relay device 15 via the relay device 25 in the same manner (step S423) and relayed further to the communication device 11 via the relay device 15 (step S424).
  • [0092]
    When a relay transmission using the relay device 25 is completed, the communication device 11 transmits a disconnection instruction to the relay device 15 (step S425). The relay device 15 transmits a disconnection request for the relay device 25 to the server device 35 (step S426). The server device 35 relays the received disconnection request to the relay device 25 (step S427). A response from the relay device 25 is transmitted to the server device 35 (step S428) and relayed to the relay device 15 (step S429). Accordingly, the TCP connection between the relay device 15 and the relay device 25 is disconnected, and the relay device 15 notifies the communication device 11 that the TCP connection has been disconnected (step S430).
  • [0093]
    Under such a state, when another communication device 12 carries out a relay transmission request designating the relay device 25 again (step S431), a connection request is transmitted from the relay device 15 to the server device 35 (step S432). At this point of time, when the relay device 25 is under a logged-out status, the server device 35 notifies the logged-out status (step S433), and the communication device 12 is notified that the relay device 25 is under a logged-out status. In the same manner as the processing carried out by the communication device 11, when the relay device 25 logs in, the communication device 12 carries out a relay transmission request to the relay device 25 again. Accordingly, a TCP connection is established between the relay device 15 and the relay device 25.
  • [0094]
    FIG. 10 is a flowchart focusing on a processing carried out by the relay device 15 in the processing described with reference to FIG. 9. First, the relay device 15 confirms whether or not a relay instruction from the communication device 11, 12 or the like is generated (step S501). When a relay instruction is generated (step S501: YES), the relay device 15 confirms whether or not a status monitoring instruction is generated (step S502). When the status monitoring instruction is generated, the relay device 15 checks whether or not the relay device of the relay destination is logged in (step S503). When the relay device 15 confirms that the relay device of the relay destination is logged out (step S503: NO), the relay device 15 stands by until receiving a login notification (step S504).
  • [0095]
    When receiving a notification from the server device 35 indicating that the relay device of the relay destination has logged in (stepS504: YES), the relay device 15 notifies the requesting communication device that the relay destination has logged in (step S505). Then, the relay device 15 stands by until receiving a relay instruction from the communication device 11, 12 or the like again (step S506). When the relay device 15 receives a relay instruction, the process proceeds onto step S508. When a determination is made at step S503 that the relay device of the relay destination is logged in, the process proceeds immediately onto step S508. When a status monitoring instruction is not included in the request from the communication device (step S502: NO), if the relay destination is logged in (step S507: YES), the process proceeds onto step S508. If the relay destination is not logged in, the process returns to step S502 and the processing is repeated. That is, when a status monitoring instruction has been received from a requesting communication device, the relay device 15 monitors the relay device of the relay destination until the relay device of the relay destination logs in. When receiving a notification that the relay device of the relay destination has logged in, the relay device 15 notifies such information also to the requesting communication device.
  • [0096]
    Next, the relay device 15 generates TCP connection information (step S508) and transmits a connection request (step S509). The relay device 15 stands by until receiving a response from the relay device 25 (step S510). When not receiving a response (step S510: NO), the relay device 15 carries out an error notification to the requesting communication device (step S511). The process returns to step S501 and the processing is repeated. When receiving a response (step S510: YES), the relay device 15 analyzes the TCP connection information included in the received response (step S512). That is, the relay device 15 acquires port number information or the like included in the response transmitted from the relay device 25. Then, the relay device 15 carries out a TCP connection to the relay device 25 (step S513). The relay device 15 notifies the requesting communication device that a connection has been established with the relay destination (step S514). Then, the relay device 15 registers information of the newly established TCP connection in the relay connection database 151 (step S515).
  • [0097]
    Under a state in which the TCP connection is established and held, in the flowchart of FIG. 11, when relay data is transmitted from the communication device 11 or the like (step S516: YES), the relay device 15 relays the data to the communication device 21 or the like (step S517). When receiving relay data to be relayed to the communication device 11 or the like (step S518: YES), the relay device 15 relays the data to the communication device 11 or the like of the relay destination (step S519). When receiving a disconnection request from the relay device 25 (step S520: YES), the relay device 15 transmits a response (step S521) and disconnects the TCP connection (step S522). When a disconnection request is carried out by the requesting communication device (step S523: YES), the relay device 15 transmits a disconnection request to the relay device 25 of the relay destination (step S524). When receiving a response (step S525: YES), the relay device 15 disconnects the TCP connection (step S526). Then, the relay device 15 notifies the requesting communication device that a connection with the relay destination has been disconnected (step S527), and the information of the TCP connection registered in the relay connection database 151 is deleted (step S528).
  • [0098]
    As described above, according to the second preferred embodiment, when a relay instruction from a communication device generates, a TCP connection is established dynamically with the relay device of the relay destination, and communication can be carried out between private networks. Unlike the conventional VPN or the like that is fixedly set, when a request of communication generates, a connection necessary for such communication is established. Therefore, resources can be utilized efficiently.
  • [0099]
    According to the second preferred embodiment, when a communication connection is established according to a request from a certain communication device, only such a requesting communication device is permitted to use the established communication connection. For example, when a request of communication generates from the communication device 11 to the communication device 21, a TCP connection is established between the relay device 15 and the relay device 25 according to the request. The established TCP connection is used only for the communication between the communication device 11 and the communication device 21. In other words, the relay device 15 and the relay device 25 use the TCP connection just for relaying the data transmitted and received between the communication device 11 and the communication device 21. Therefore, a connection established according to a request from a certain communication device is used exclusively by such a communication device.
  • [0100]
    In the example illustrated in FIG. 7, under a state in which a connection is established between the relay device 15 and the relay device 25 according to a request from the communication device 11, suppose that a connection is established further between the relay device 15 and the relay device 45 according to a request from the communication device 12. In this case, a description has been made with reference to FIG. 6 that an individual data relay connection is established. Therefore, the communication device 11 and the communication device 12 use different TCP connections for relaying data. Meanwhile, under a state in which the communication device 11 is carrying out a relay transmission designating the relay device 25, when the communication device 12 also carries out a relay instruction designating the same relay device 25, since the already established TCP connection is used exclusively by the communication device 11, a separate communication connection is established.
  • Third Preferred Embodiment
  • [0101]
    Next, a description will be made of a third preferred embodiment of the present invention. Also in the third preferred embodiment, in the same manner as in the second preferred embodiment, a connection is carried out between relay devices according to a request from a communication device. However, in the third preferred embodiment, when a connection has already been established between the relay devices, another communication device shares the already established connection. This feature differs from the second preferred embodiment. In the following, a description will be made primarily of aspects that are different from the second preferred embodiment.
  • [0102]
    FIG. 12 illustrates an example of registration of the relay connection database 151 stored in the relay device 15. As illustrated in FIG. 12, a plurality of clients (communication devices) are associated with one TCP connection. In the example illustrated in FIG. 12, a relay transmission request has generated from two communication devices (ClientX and ClientY), and both of the communication devices designate the same relay device (Relayserver1@sample.net). Therefore, the two communication devices are sharing a TCP connection with a connection number 49583.
  • [0103]
    The contents of the relay connection databases 251 and 451 stored in the relay devices 25 and 45, respectively, are the same as the relay connection database 151 illustrated in FIG. 12. The relay connection databases 251 and 451 store a status of a TCP connection currently established by the relay devices 25 and 45, respectively.
  • [0104]
    Next, with reference to FIG. 13 through FIG. 15, a description will be made of a flow of a communication processing carried out in the above-described communication system. FIG. 13 illustrates a flow of a processing of the entire communication system including the communication devices 11 and 12, the relay devices 15 and 25, and the server device 35. Further, in the following description, a description will be made of an example in which the SIP is used for the communication between the relay device 15 and the server device 35, and between the server device 35 and the relay device 25. However, other protocols may also be used.
  • [0105]
    The processing from step S701 to step S724 in FIG. 13 corresponds to the processing from step S401 to step S424 in FIG. 9. Since the processing is the same, a description will be omitted. That is, the communication device 11 generates a relay transmission request designating the relay device 25, and a TCP connection is established between the relay device 15 and the relay device 25. Then, data is transmitted and received between the communication device 11 and the communication device 21 or the like.
  • [0106]
    Under such a state, a different communication device 12 carries out a relay transmission request designating the relay device 25 again (step S725). Since the TCP connection is currently being established between the relay device 15 and the relay device 25, the relay device 15 notifies the communication device 12 that a relay transmission of the data can be carried out (step S726). Accordingly, when data is transmitted from the communication device 12 (step S727), the relay device 15 uses the already established TCP connection to relay the data transmitted from the communication device 12 to the relay device 25 (step S728). The relay device 25 also uses the already established TCP connection for relaying the data, which has been transmitted from the communication device 21 or the like to the communication device 12, to the relay device 15 (step S729). The relay device 15 further transmits the received data to the communication device 12 (step S730).
  • [0107]
    As described above, in the third preferred embodiment, a TCP connection is already established between the relay devices, and when the already established TCP connection can be used for a newly generated relay transmission request, a new TCP connection is not established. A plurality of communication terminals share the same TCP connection. Accordingly, load required for establishing a TCP connection can be reduced, and communication between different networks can be carried out under higher speed. In addition, resources of the relay device can be saved. For example, when carrying out communication via the Internet between a plurality of communication terminals connected to the LAN 10 and a plurality of communication terminals connected to the LAN 20, an increase in the processing speed and saving of the resources are possible and efficient. The above-described third preferred embodiment is also efficient when data volume to be relayed from one communication device is small.
  • [0108]
    Under a state in which the communication device 11 and the communication device 12 are sharing the TCP connection and carrying out data communication as described above, the communication device 11 transmits a disconnection instruction to the relay device 15 (step S731). Since the communication device 12 is using the same TCP connection, the relay device 15 does not carry out a processing in particular with respect to the disconnection instruction of step S731, and just carries out a response (step S732).
  • [0109]
    Then, when the relay transmission using the relay device 25 ends, the communication device 12 transmits a disconnection instruction to the relay device 15 (step S733). Since the relay device 15 has already received the disconnection instruction from the communication device 11, the relay device 15 can determine that the shared TCP connection has become unnecessary. Therefore, the relay device 15 transmits a disconnection request for the relay device 25 to the server device 35 (step S734). The server device 35 relays the disconnection request to the relay device 25 (step S735). The relay device 25 transmits a response to the server device 35 (step S736). Then, the server device 35 relays the response to the relay device 15 (step S737). Accordingly, the TCP connection between the relay device 15 and the relay device 25 is disconnected, and the relay device 15 notifies the communication device 11 that the TCP connection has been disconnected (step S738).
  • [0110]
    FIG. 14 is a flowchart focusing on a processing carried out by the relay device 15 in the processing described with reference to FIG. 13. First, the relay device 15 confirms whether or not a relay instruction from the communication device 11 or 12 or the like has generated (step S801). When a relay instruction has generated (step S801: YES), the relay device 15 confirms whether or not a TCP connection is already established with a relay device of a relay destination (step S802). That is, the relay device 15 confirms whether or not the same relay device has already been designated by another communication device and a communication is being carried out with such a relay device.
  • [0111]
    When a connection is already established with the already instructed relay destination (step S802: YES), the relay device 15 notifies that data can be relayed to a requesting communication device (step S815). Then, the relay device 15 updates the information of the relay connection database 151 (step S816). That is, since information regarding the TCP connection is already registered in the relay connection database 151, the relay device 15 just adds a client (communication device). In the example illustrated in FIG. 12, for example, when ClientX and a TCP connection with a connection number 49583 are associated and stored, the relay device 15 carries out a processing for adding ClientY to the “client” field of such record.
  • [0112]
    When a connection is yet to be established with the designated relay destination at step S802, the relay device 15 executes the processing from step S803 to step S814. This processing corresponds to the processing from step S502 to step S513 in FIG. 10. Since the processing is the same, a description will be omitted.
  • [0113]
    Next, a description will be made with reference to FIG. 15. Under a state in which a TCP connection is established and held, when relay data is transmitted from the communication device 11 or the like (step S817: YES), the data is relayed to the communication device 21 or the like (step S818). When receiving relay data to be relayed to the communication device 11 or the like (step S819: YES), the relay device 15 relays the data to the communication device 11 or the like of the relay destination (step S820). When receiving a disconnection request from the relay device 25 of the relay destination (step S821: YES), the relay device 15 transmits a response (step S822) and disconnects the TCP connection (step S823). As described above, when the TCP connection is disconnected from the relay device 25 of the relay destination, the relay device 15 notifies the communication device to which relay transmission is being carried out that the connection with the relay destination has been disconnected to (step S824). When the disconnected TCP connection had been shared among a plurality of communication devices, the disconnection is notified to all of the communication devices (steps S824 and S825).
  • [0114]
    When a disconnection request is carried out by the requesting communication device (step S826: YES), the relay device 15 checks whether or not the TCP connection instructed to be disconnected is being shared with another communication device (step S827). When such a TCP connection is being shared with another communication device (step S827: YES), without disconnecting the TCP connection, a formal disconnection notification is carried out to the communication device that has carried out the disconnection instruction (step S828). Then, the relay device 15 updates the information stored in the relay connection database 151 (stepS829). That is, the relay device 15 deletes information of the client (communication device) that has requested the disconnection instruction from the information of the shared TCP connection. The relay device 15 manages a currently established TCP connection and communication devices sharing the TCP connection at all times as described above.
  • [0115]
    When the TCP connection instructed to be disconnected is not shared with another communication device (step S827: NO), the relay device 15 transmits a disconnection request to the relay device 25 (step S830). When receiving a response (step S831: YES), the TCP connection is disconnected (step S832). Then, the relay device 15 notifies the requesting communication device that the connection with the relay destination has been disconnected (step S833) and deletes the information of the TCP connection registered in the relay connection database 151 (step S834).
  • [0116]
    As described above, according to the third preferred embodiment, when a relay instruction from a communication device generates, a TCP connection is dynamically established with a relay device of a relay destination, and communication can be carried out between private networks. Furthermore, when a relay instruction generates, if a TCP connection is already established with the relay destination, the already established TCP connection is shared. Accordingly, speed of the processing is increased, and resources can be utilized efficiently.
  • [0117]
    While the present invention has been described with respect to preferred embodiments thereof, it will be apparent to those skilled in the art that the disclosed invention may be modified in numerous ways and may assume many embodiments other than those specifically set out and described above. Accordingly, the appended claims are intended to cover all modifications of the present invention that fall within the true spirit and scope of the present invention.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US5224205 *May 21, 1990Jun 29, 1993International Business Machines Corp.Method of combining architecturally dissimilar computing networks into a single logical network
US5535375 *Oct 11, 1994Jul 9, 1996International Business Machines CorporationFile manager for files shared by heterogeneous clients
US5848134 *Jan 27, 1997Dec 8, 1998Sony CorporationMethod and apparatus for real-time information processing in a multi-media system
US5884312 *Feb 28, 1997Mar 16, 1999Electronic Data Systems CorporationSystem and method for securely accessing information from disparate data sources through a network
US6061796 *Aug 26, 1997May 9, 2000V-One CorporationMulti-access virtual private network
US6111883 *Jun 27, 1997Aug 29, 2000Hitachi, Ltd.Repeater and network system utilizing the same
US6145084 *Oct 8, 1998Nov 7, 2000Net I TrustAdaptive communication system enabling dissimilar devices to exchange information over a network
US6178427 *May 7, 1998Jan 23, 2001Platinum Technology Ip, Inc.Method of mirroring log datasets using both log file data and live log data including gaps between the two data logs
US6215877 *Sep 23, 1998Apr 10, 2001Fujitsu LimitedKey management server, chat system terminal unit, chat system and recording medium
US6222536 *Dec 30, 1997Apr 24, 2001Korea TelecomMethod and apparatus for providing a number of subscribers with on-line banking service employing a plurality of bank systems
US6226692 *Dec 13, 1996May 1, 2001Object Dynamics CorporationMethod and system for constructing software components and systems as assemblies of independent parts
US6237023 *Jun 11, 1997May 22, 2001Canon Kabushiki KaishaSystem for controlling the authority of a terminal capable of simultaneously operating a plurality of client softwares which transmit service requests
US6324574 *Nov 7, 1997Nov 27, 2001International Business Machines CorporationRelay server for unsigned applets
US6336141 *Sep 10, 1999Jan 1, 2002Hitachi, Ltd.Method of collectively managing dispersive log, network system and relay computer for use in the same
US6538773 *Mar 26, 1999Mar 25, 2003International Business Machines CorporationMethod and apparatus for rendering grayscales at a facsimile presentation device using a calibrated transform
US6546488 *Sep 21, 1998Apr 8, 2003Hughes Electronics CorporationBroadcast delivery of information to a personal computer for local storage and access
US6564261 *May 9, 2000May 13, 2003Telefonaktiebolaget Lm Ericsson (Publ)Distributed system to intelligently establish sessions between anonymous users over various networks
US6594246 *Jul 9, 1999Jul 15, 2003Malibu Networks, Inc.IP-flow identification in a wireless point to multi-point transmission system
US6636513 *Sep 5, 1996Oct 21, 2003Fujitsu LimitedSwitching system
US6650631 *Mar 11, 1997Nov 18, 2003Verizon Services Corp.Public IP transport network
US6754212 *Jul 26, 2000Jun 22, 2004Hitachi, Ltd.Repeater and network system utililzing the same
US6757365 *Oct 16, 2000Jun 29, 2004Tellme Networks, Inc.Instant messaging via telephone interfaces
US6765686 *Nov 12, 1998Jul 20, 2004Canon Kabushiki KaishaImage processing apparatus, method of controlling same, and image processing system
US6766373 *May 31, 2000Jul 20, 2004International Business Machines CorporationDynamic, seamless switching of a network session from one connection route to another
US6889256 *Jun 9, 2000May 3, 2005Microsoft CorporationSystem and method for converting and reconverting between file system requests and access requests of a remote transfer protocol
US6898641 *Nov 28, 2000May 24, 2005Fujitsu LimitedNetwork routing system and routing apparatus
US6938042 *Oct 8, 2002Aug 30, 2005Laplink Software Inc.Peer-to-peer file sharing
US6950879 *Jan 24, 2001Sep 27, 2005Interland, Inc.Using virtual network address information during communications
US6988199 *Jun 21, 2001Jan 17, 2006Message SecureSecure and reliable document delivery
US7000248 *Nov 1, 2001Feb 14, 2006Nec CorporationVirtual network and virtual network connection system
US7110393 *Feb 28, 2001Sep 19, 20063Com CorporationSystem and method for providing user mobility handling in a network telephony system
US7120927 *Jun 9, 1999Oct 10, 2006Siemens Communications, Inc.System and method for e-mail alias registration
US7139811 *Jul 31, 2002Nov 21, 2006Actona Technologies Ltd.Double-proxy remote data access system
US7152111 *Aug 15, 2002Dec 19, 2006Digi International Inc.Method and apparatus for a client connection manager
US7174378 *May 29, 2001Feb 6, 2007Nitgen Technologies, Inc.Co-location service system equipped with global load balancing (GLB) function among dispersed IDCS
US7181542 *Mar 22, 2001Feb 20, 2007Corente, Inc.Method and system for managing and configuring virtual private networks
US7191195 *Nov 27, 2002Mar 13, 2007Oki Electric Industry Co., Ltd.Distributed file sharing system and a file access control method of efficiently searching for access rights
US7200642 *Apr 29, 2001Apr 3, 2007Geodigm CorporationMethod and apparatus for electronic delivery of electronic model images
US7206088 *Jan 10, 2002Apr 17, 2007Murata Kikai Kabushiki KaishaRelay server, communication system and facsimile system
US7257638 *Dec 20, 2001Aug 14, 2007Microsoft CorporationDistributing network applications
US7299275 *Jun 3, 2003Nov 20, 2007Matsushita Electric Industrial Co., Ltd.Content delivery system for dynamically and optimally relocates contents to archive server, edge servers and terminal storage devices based on users' viewing tendency
US7412489 *Aug 13, 2004Aug 12, 2008Ameriprise Financial, Inc.Method and system for electronic archival and retrieval of electronic communications
US7574523 *Jan 22, 2002Aug 11, 2009Sun Microsystems, Inc.Relay peers for extending peer availability in a peer-to-peer networking environment
US7624175 *Nov 3, 2003Nov 24, 2009Sprint Communications Company L.P.Update messaging system
US7660809 *Jan 31, 2005Feb 9, 2010Microsoft CorporationUsing a file server as a central shared database
US7701954 *May 12, 2004Apr 20, 2010Broadcom CorporationGateway with voice
US7774495 *Feb 13, 2003Aug 10, 2010Oracle America, Inc,Infrastructure for accessing a peer-to-peer network environment
US7813299 *Jan 3, 2005Oct 12, 2010Hitachi, Ltd.Session control system for hierarchical relaying processes
US7860978 *Jan 22, 2004Dec 28, 2010Toshiba America Research, Inc.Establishing a secure tunnel to access router
US20010044819 *Nov 7, 1997Nov 22, 2001International Business Machines CorporationRelay server for unsigned applets
US20010047414 *May 29, 2001Nov 29, 2001Yoon Ki J.Dedicated private network service method having backup and loads-balancing functions
US20020023143 *Apr 3, 2001Feb 21, 2002Stephenson Mark M.System and method for projecting content beyond firewalls
US20020029276 *Apr 11, 2001Mar 7, 2002Samuel BendinelliMethods and systems for an extranet
US20020032616 *Jul 9, 2001Mar 14, 2002Kazunori SuzukiRelay server, relaying method and payment system
US20020056003 *Apr 11, 2001May 9, 2002Dinkar GoswamiSystem and method for real-time multi-directional file-based data streaming editor
US20020073182 *Dec 8, 2000Jun 13, 2002Zakurdaev Maxim V.Method and apparatus for a smart DHCP relay
US20020095506 *Jan 10, 2002Jul 18, 2002Murata Kikai Kabushiki KaishaRelay server, communication system and facsimile system
US20020118398 *Jan 10, 2002Aug 29, 2002Murata Kikai Kabushiki KaishaRelay server, communication system and facsimile system
US20020143855 *Jan 22, 2002Oct 3, 2002Traversat Bernard A.Relay peers for extending peer availability in a peer-to-peer networking environment
US20020143922 *Apr 1, 2002Oct 3, 2002Murata Kikai Kabushiki KaishaRelay server and relay system
US20020143956 *Apr 2, 2002Oct 3, 2002Murata Kikai Kabushiki KaishaRelay server
US20020143957 *Apr 2, 2002Oct 3, 2002Murata Kikai Kabushiki KaishaRelay server, network device, communication system, and communication method
US20020143960 *Dec 4, 2000Oct 3, 2002Erez GorenVirtual network generation system and method
US20020146002 *Jul 24, 2001Oct 10, 2002Takayuki SatoNetwork administration apparatus, network administrating program, network administrating method and computer network system
US20020152299 *Jan 22, 2002Oct 17, 2002Traversat Bernard A.Reliable peer-to-peer connections
US20020156875 *Dec 18, 2001Oct 24, 2002Kuldipsingh PablaPeer group name server
US20030021232 *Jul 27, 2001Jan 30, 2003Jerome DuplaixScalable router
US20030055741 *Aug 20, 2002Mar 20, 2003Kabushiki Kaisha ToshibaServer for exchanging design information, method for exchanging design information, program for exchanging design information, buying method of special design product and selling method of special design product
US20030097456 *Jun 14, 2002May 22, 2003Huh Mi YoungMethod for synchronizing registration information within intra-domain
US20040068524 *Oct 8, 2002Apr 8, 2004Aboulhosn Amir L.Peer-to-peer file sharing
US20040073610 *Sep 22, 2003Apr 15, 2004Katsuhiko TeradaContents reproducing system
US20040083385 *Oct 25, 2002Apr 29, 2004Suhail AhmedDynamic network security apparatus and methods for network processors
US20040162871 *Feb 13, 2003Aug 19, 2004Pabla Kuldipsingh A.Infrastructure for accessing a peer-to-peer network environment
US20040172395 *Feb 28, 2003Sep 2, 2004Microsoft CorporationMethod to delay locking of server files on edit
US20040243703 *Aug 12, 2003Dec 2, 2004Nbt Technology, Inc.Cooperative proxy auto-discovery and connection interception
US20040255048 *Jul 31, 2002Dec 16, 2004Etai Lev RanVirtual file-sharing network
US20040267939 *Jan 23, 2004Dec 30, 2004Hitachi, Ltd.Session control apparatus, software applied to session control apparatus, communication control method, and network system
US20050144289 *Jan 29, 2004Jun 30, 2005Hitachi, Ltd.Connection control system, connection control equipment and connection management equipment
US20050216523 *Aug 2, 2004Sep 29, 2005Akihiko SakaguchiFile management method in a distributed storage system
US20050256909 *Dec 15, 2004Nov 17, 2005Aboulhosn Amir LPeer-to-peer file sharing
US20050281251 *Jan 3, 2005Dec 22, 2005Hitachi, Ltd.Session control system for hierarchical relaying processes
US20050287998 *Jun 28, 2005Dec 29, 2005Nec CorporationConference assisting system and method
US20060020695 *Sep 15, 2005Jan 26, 2006Microsoft CorporationScaling and delivering distributed applications
US20060083171 *Jul 6, 2005Apr 20, 2006Aruze CorporationMedia communication apparatus and media communication program product
US20060101064 *Nov 8, 2005May 11, 2006Sharpcast, Inc.Method and apparatus for a file sharing and synchronization system
US20060117076 *Nov 29, 2004Jun 1, 2006Spencer William AMethod for replication tracing
US20060149771 *Dec 1, 2005Jul 6, 2006Hitachi, Ltd.Information processing system and communication retry method
US20060187902 *Feb 24, 2005Aug 24, 2006Oliver BirchMethod and apparatus for session initiation protocol application design, development, execution and integration
US20060206616 *Mar 14, 2006Sep 14, 2006Gridiron Software, Inc.Decentralized secure network login
US20060256771 *May 12, 2005Nov 16, 2006Yahoo! Inc.Proxy server for relaying VOIP messages
US20060259553 *Feb 3, 2003Nov 16, 2006Jun KawakitaSynchronization program
US20060282540 *May 12, 2006Dec 14, 2006Murata Kikai Kabushiki KaishaFile server device, communication management server device, and network system including the file server device and the communication management server device
US20070019545 *Dec 30, 2005Jan 25, 2007Mci, Inc.Method and system for securing real-time media streams in support of interdomain traversal
US20070022477 *Sep 14, 2006Jan 25, 2007Science Applications International CorporationThird party vpn certification
US20070081530 *Sep 11, 2003Apr 12, 2007Yuji NomuraPacket relay apparatus
US20070106795 *Nov 8, 2005May 10, 2007Gilfix Michael AAutomatic orchestration of dynamic multiple party, multiple media communications
US20070192434 *Jun 12, 2006Aug 16, 2007Fujitsu LimitedNetwork system, terminal, and gateway
US20080098088 *Jan 11, 2006Apr 24, 2008Hirokazu TamanoCommunication System, Terminal Device And Communication Device
US20090177573 *Mar 16, 2009Jul 9, 2009Beadle Alastair J DSystem and method for managing relationships between brokers and traders
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US8005893Apr 30, 2008Aug 23, 2011Murata Machinery, Ltd.Relay server and relay communication system
US8005961Nov 23, 2007Aug 23, 2011Murata Machinery, Ltd.Relay server, relay communication system, and communication device
US8010598Dec 10, 2007Aug 30, 2011Murata Machinery, Ltd.Relay server and client terminal
US8010647Dec 10, 2007Aug 30, 2011Murata Machinery, Ltd.Relay server and relay communication system arranged to share resources between networks
US8010675Dec 16, 2008Aug 30, 2011Murata Machinery, Ltd.Relay server and relay communication system
US8069246Dec 22, 2008Nov 29, 2011Murata Machinery, Ltd.Relay server and relay communication system including a relay group information registration unit, a shared resource information registration unit, and a control unit
US8296391Aug 31, 2009Oct 23, 2012Murata Machinery, Ltd.Relay server, relay communication system, and communication apparatus
US8307100Apr 23, 2008Nov 6, 2012Murata Machinery, Ltd.Relay server and relay communication system
US8316134Sep 27, 2007Nov 20, 2012Murata Machinery, Ltd.File server device arranged in a local area network and being communicable with an external server arranged in a wide area network
US8321575Dec 16, 2008Nov 27, 2012Murata Machinery, Ltd.Relay server and relay communication system
US8356116Aug 31, 2009Jan 15, 2013Murata Machinery, Ltd.Relay server and relay communication system
US8391276 *Oct 3, 2008Mar 5, 2013At&T Intellectual Property I, LpMethods and apparatus to form secure cross-virtual private network communications sessions
US8443088Oct 11, 2007May 14, 2013Murata Machinery, Ltd.File transfer server
US8472454Sep 12, 2007Jun 25, 2013Murata Machinery, Ltd.Relay-server arranged to carry out communications between communication terminals on different LANS
US8606941Apr 16, 2008Dec 10, 2013Murata Machinery, Ltd.Relay server and relay communication system
US8798082May 13, 2010Aug 5, 2014Murata Machinery, Ltd.Relay communication system and first relay server
US8879543 *Mar 4, 2013Nov 4, 2014At&T Intellectual Property I, L.P.Methods and apparatus to form secure cross-virtual private network communication sessions
US8949419Nov 14, 2008Feb 3, 2015Murata Machinery, Ltd.Synchronizing sharing servers
US9137313 *Dec 6, 2011Sep 15, 2015Samsung Sds Co., Ltd.Data transmission system and method using relay server
US9246879 *Oct 16, 2014Jan 26, 2016At&T Intellectual Property, I., L.P.Methods and apparatus to form secure cross-virtual private network communication sessions
US9307068Feb 10, 2010Apr 5, 2016Canon Kabushiki KaishaInformation processing apparatus and communication processing method thereof
US20080063001 *Sep 12, 2007Mar 13, 2008Murata Machinery, Ltd.Relay-server
US20080089349 *Sep 27, 2007Apr 17, 2008Murata Machinery, LtdFile server device
US20080091768 *Oct 11, 2007Apr 17, 2008Murata Machinery, LtdFile transfer server
US20080137672 *Dec 10, 2007Jun 12, 2008Murata Machinery, Ltd.Relay server and relay communication system
US20080147825 *Dec 10, 2007Jun 19, 2008Murata Machinery, Ltd.Relay server and client terminal
US20080275945 *Apr 16, 2008Nov 6, 2008Murata Machinery, Ltd.Relay server and relay communication system
US20080275953 *Apr 30, 2008Nov 6, 2008Murata Machinery, Ltd.Relay server and relay communication system
US20080281981 *Apr 23, 2008Nov 13, 2008Murata Machinery, Ltd.Relay server and relay communication system
US20080288591 *Nov 23, 2007Nov 20, 2008Murata Machinery, Ltd.Relay server, relay communication system, and communication device
US20090164636 *Nov 14, 2008Jun 25, 2009Murata Machinery, Ltd.Relay server and relay communication system
US20090164637 *Dec 16, 2008Jun 25, 2009Murata Machinery, Ltd.Relay server and relay communication system
US20090172075 *Dec 22, 2008Jul 2, 2009Murata Machinery, Ltd.Relay server and relay communication system
US20090172166 *Dec 16, 2008Jul 2, 2009Murata Machinery, Ltd.Relay server and relay communication system
US20100085957 *Oct 3, 2008Apr 8, 2010Elias Mark AMethods and Apparatus to Form Secure Cross-Virtual Private Network Communications Sessions
US20100235497 *Feb 10, 2010Sep 16, 2010Canon Kabushiki KaishaInformation processing apparatus and communication processing method thereof
US20110161525 *Aug 31, 2009Jun 30, 2011Murata Machinery, Ltd.Relay server and relay communication system
US20110179167 *Aug 31, 2009Jul 21, 2011Murata Machinery, Ltd.Relay server, relay communication system, and communication apparatus
US20120166593 *Dec 6, 2011Jun 28, 2012Samsung Sds Co., Ltd.Data transmission system and method using relay server
US20130136130 *Nov 14, 2012May 30, 2013Murata Machinery, Ltd.Relay server and relay communication system
US20130177013 *Mar 4, 2013Jul 11, 2013At&T Intellectual Property I, LpMethods and apparatus to form secure cross-virtual private network communication sessions
US20150040207 *Oct 16, 2014Feb 5, 2015At&T Intellectual Property, I, L.P.Methods and apparatus to form secure cross-virtual private network communication sessions
US20150312363 *Apr 25, 2014Oct 29, 2015Pravala Networks Inc.Using proxy devices as dynamic data relays
Classifications
U.S. Classification709/223
International ClassificationG06F15/173
Cooperative ClassificationH04L67/28, H04L67/1095, H04L67/2842
European ClassificationH04L29/08N27, H04L29/08N9R, H04L29/08N27S
Legal Events
DateCodeEventDescription
Mar 20, 2007ASAssignment
Owner name: MURATA KIKAI KABUSHIKI KAISHA, JAPAN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TANIMOTO, YOSHIFUMI;REEL/FRAME:019132/0967
Effective date: 20070307