JP5483064B2 - Management relay server and relay communication system - Google Patents

Description

  The present invention mainly relates to a relay server that enables communication between terminals connected to different LANs (Local Area Networks).

  Conventionally, a communication system called a virtual private network (VPN) is known. This VPN is used for, for example, applications in which client terminals connected to a plurality of LANs communicate with each other via the Internet to remotely maintain a certain client terminal. If the VPN is used, a client terminal to be maintained can receive remote maintenance or the like from a device connected to another remote LAN.

  Patent Document 1 discloses a management system via this type of network. This management system is constructed so as to straddle building owners, equipment maintenance companies, and electrical equipment manufacturers. The building owner installs electrical equipment and an operation control management device for controlling the electrical equipment in the building owned by the building owner. This operation control management device is configured to be accessible via a network such as the Internet. The equipment maintenance company is entrusted with the management of the electrical equipment by the building owner, and has obtained permission from the electrical equipment manufacturer to access the operation control management device. Therefore, the equipment maintenance company can manage the electrical equipment from a remote location via a network such as the Internet.

JP 2003-223521 A

  When performing remote maintenance as described above via a server connected to the local network of the site where maintenance is performed, by selecting an incorrect device as a maintenance target and applying an incorrect application, etc. There may be cases where proper maintenance is not performed. Such a situation needs to be detected quickly because it takes a long time to recover and the time period during which maintenance work is possible is limited. In addition, even when appropriate maintenance work has been performed, if heavy maintenance work is performed on the same target at the same time, the load on the customer's server may increase, leading to a decrease in communication efficiency. .

  The present invention has been made in view of the above circumstances, and an object thereof is to provide a management relay server that appropriately manages information exchanged between relay servers that are management targets.

Means and effects for solving the problems

  The problems to be solved by the present invention are as described above. Next, means for solving the problems and the effects thereof will be described.

According to a first aspect of the present invention, a management relay server having the following configuration is provided. That is, the management relay server includes a connection management information storage unit, a communication content information storage unit, and a control unit. The connection management information storage unit stores a connection status between relay servers. The communication content information storage unit is an outline of information exchanged during communication between the relay servers and information exchanged during communication between the relay servers, and processing performed by communication between the relay servers And communication summary information including the contents of . The control unit selects the target relay server based on the connection status stored in the connection management information storage unit, and information exchanged from the relay server during communication between the relay servers or the communication Information is selected and received and stored in the communication content information storage unit.

  Thereby, since the management relay server stores the communication content information between the relay servers, the communication content information can be centrally managed in the management relay server. In addition, since it is possible to analyze the operation status of the relay server and the like based on the communication content stored in the communication content information storage unit, even when an abnormality occurs and inappropriate communication is performed, The cause can be easily investigated.

  The management relay server preferably has the following configuration. That is, the control unit requests, as the communication content information, necessary information among the information regarding the communication content to at least one of the relay servers communicating with each other. And the said control part receives the said communication content information, and memorize | stores it in the said communication content information storage part.

  Thereby, the management relay server can acquire the communication content information at a timing convenient for the own device. In addition, the information required for management varies depending on how the relay server is managed. By selecting and requesting the required information from the information related to communication contents, it is possible to flexibly handle various management contents. Management.

  The management relay server preferably receives the communication content information during communication between the relay servers.

  As a result, the management relay server can determine whether or not appropriate communication is being performed between the relay servers during the communication. Therefore, even when inappropriate communication is performed, it can be detected during the communication.

  In the management relay server, the communication content information can be received after the communication between the relay servers is completed.

  Thereby, the management relay server can receive the communication content information without imposing a load on the relay server in communication.

  In the management relay server, the control unit is configured to establish a communication path with at least one of the relay servers and simultaneously receive communication content information during communication between the relay servers. You can also.

  As a result, it is possible for the management relay server side to quickly know that an abnormality such as unnecessary transmission / reception of information between relay servers has occurred. On the relay server side, it is sufficient that transmission of the communication content information is performed simultaneously to the management relay server every time the relay servers communicate with each other. Therefore, the relay server can quickly discard unnecessary communication content information among the communication content information exchanged between the relay servers.

According to the 2nd viewpoint of this invention, the relay communication system of the following structures is provided. That is, this relay communication system includes a management relay server and a plurality of relay servers. The relay servers can communicate with each other. The management relay server includes a connection management information storage unit, a communication content information storage unit, and a control unit. The connection management information storage unit stores a connection status between the relay servers. The communication content information storage unit is an outline of information exchanged during communication between the relay servers and information exchanged during communication between the relay servers, and processing performed by communication between the relay servers And communication summary information including the contents of . The control unit selects the target relay server based on the connection status stored in the connection management information storage unit, and information exchanged from the relay server during communication between the relay servers or the communication Is received and stored in the communication content information storage unit .

  As a result, it is possible to realize a relay communication system capable of performing detailed management including not only the connection status between relay servers but also communication contents.

BRIEF DESCRIPTION OF THE DRAWINGS Explanatory drawing which shows the whole structure of the relay communication system which concerns on one Embodiment of this invention. The functional block diagram of an external server. The functional block diagram of a call center server. The figure which shows the content of client terminal information. The figure which shows the content of relay server information. The figure which shows the content of relay group information. A table showing the contents of the access permission information database. A table showing the contents of the communication management information database. Explanatory drawing explaining a routing process. The figure which shows the content of LAN search result information. The figure which shows the content of route search result information. The figure which shows the content of routing group information. The sequence diagram which shows the communication processing of the first half part of a maintenance work. The sequence diagram which shows the communication process of the second half part of a maintenance work. The sequence diagram which shows the communication processing of a modification.

  Next, an embodiment of the invention will be described. FIG. 1 is an explanatory diagram showing the overall configuration of a relay communication system according to an embodiment of the present invention.

  The relay communication system of this embodiment is a remote maintenance system constructed for the purpose of remote maintenance of an apparatus or a machine, a call center, an installation destination (customer factory) of the apparatus or machine, a serviceman dispatch destination, Are connected via the Internet.

  The call center is a service base for performing maintenance of the device or machine introduced into the customer factory, and is installed at the manufacturer of the device or machine, for example. A service person dispatch destination is a place where a service person is dispatched, and is set up separately from the call center as a base for providing a remote maintenance service. The relay communication system according to the present embodiment is constructed assuming a situation in which a serviceman waiting at a serviceman dispatch destination remotely maintains a device or machine at a customer factory via the Internet.

  As shown in FIG. 1, the relay communication system includes a plurality of LANs 91 to 93 connected to the WAN. A WAN (Wide Area Network) is a network that connects different LANs to each other. In the present embodiment, the Internet is used as the WAN. A LAN (Local Area Network) is a network constructed in a limited place. There are a plurality of LANs, and they are constructed at locations physically separated from each other.

  A LAN (call center LAN) 91 is constructed in a call center, a LAN (dispatch destination LAN) 92 is constructed in a serviceman dispatch destination, and a LAN (customer LAN) 93 is constructed in a customer factory. These three LANs 91, 92, 93 are connected to the Internet, which is a global network.

  In addition, the relay servers 1 are installed in the LANs 91 to 93, respectively. In the following description, in order to distinguish the relay server 1 arranged in each LAN, the relay server 1 arranged in the LAN 91 may be referred to as a call center server (relay server 1) R1. Further, the relay server 1 arranged in the LAN 92 may be called a dispatch server (relay server 2) R2, and the relay server 1 arranged in the LAN 93 may be called a customer server (relay server 3) R3. .

  A client terminal 5 for performing various settings for performing relay communication is connected to the call center server R1 via a LAN 91. A client terminal 5 that is directly operated when a serviceman performs remote maintenance is connected to the dispatch destination server R2 via a LAN 92.

  At the customer factory, a client terminal 5 that is a target for a serviceman to perform remote maintenance is arranged. The client terminal 5 itself at the customer factory may be an apparatus or machine manufactured by the manufacturer, or the client terminal 5 at the customer factory may be merely a control terminal for controlling the apparatus or machine. In any case, the service person provides the remote maintenance service by accessing the client terminal 5 of the customer factory. The client terminal 5 arranged in the customer factory is connected to the customer server R3 via the LAN 93.

  The client terminal 5 connected to each of the LANs 91 to 93 is a terminal that can be directly operated by the user, for example, a personal computer (PC) used for daily work by the user. Accordingly, there are usually a large number of client terminals 5 in the LAN. Each client terminal 5 is assigned a private IP address that is uniquely managed in the same LAN.

  In addition to the call center server R1, the dispatch destination server R2, and the customer server R3 shown in FIG. 1, a LAN is constructed in a physically separated place, and the relay server 1 is arranged in the LAN. Yes. A plurality of these relay servers 1 are connected to the external server 2 via the Internet.

  More specifically, although the LAN 92 is installed in the service person dispatch destination shown in FIG. 1, there are some dispatch destinations not shown. A LAN is also established at each dispatch destination (not shown), and a relay server 1 as a dispatch destination server is connected to the LAN (similar to the LAN 92 in FIG. 1). In addition, although the LAN 93 is installed at the customer factory shown in FIG. 1, there is a customer factory (customer where a machine or apparatus to be maintained is installed) other than this. A LAN is also installed at each customer factory (not shown), and a relay server 1 as a customer server is connected to the LAN (as in the case of the LAN 93 in FIG. 1).

  And in this embodiment, the relay server 1 as a some dispatch destination server is set for every customer server (relay server 1). In the following description, “relay server 1 as a dispatch destination server” may be simply referred to as “dispatch destination server”, and “relay server 1 as a customer server” may be simply referred to as “customer server”.

  Next, the configuration of the external server 2 will be described. The external server 2 is a device used for communication between the relay servers 1 arranged in each LAN, and is installed on the Internet. The external server 2 of the present embodiment has a function as a SIP (Session Initiation Protocol) server. Specifically, the external server 2 has a function as a SIP proxy server that relays SIP methods and responses, and a function as a SIP registrar server that registers an account of the relay server 1.

  As shown in FIG. 2, the external server 2 includes a WAN interface 201, a control unit 202, and a relay server account information database 203 as main components.

  The WAN interface 201 is an interface that communicates with each device such as the relay server 1 connected to the Internet using a global IP address.

  The relay server account information database 203 is a database that manages the account of the relay server 1 constituting the relay communication system in association with the global IP address. In the relay server account information database 203 of this embodiment, the accounts of the call center server R1, the dispatch destination server R2, and the customer server R3 and the global IP address are registered for each relay server 1 in association with each other.

  The control unit 202 is a processing unit that controls various communications performed via the WAN interface 201, and controls communication processing according to a protocol such as TCP / IP, UDP, or SIP. For example, the control unit 202 receives information related to the account of the relay server 1 from each relay server 1 and registers the information in the relay server account information database 203. Also, processing such as relaying communication data such as various SIP methods or responses transmitted from the relay server 1 to other relay servers 1 is performed.

  Next, the configuration of the relay server 1 arranged in the LANs 91 to 93 will be described. Each relay server 1 arranged in the LANs 91 to 93 is communicably connected to the client terminal 5 arranged in each LAN and is also connected to the Internet. Each relay server 1 (that is, call center server R1, dispatch destination server R2, and customer server R3) is assigned both a private IP address and a global IP address. As a result, the relay servers 1 can perform relay communication with each other via the external server 2. The relay server 1 has a function as a SIP registrar server, and communication between each relay server 1 and each client terminal 5 is performed using SIP. The communication between each relay server 1 and each client terminal 5 is not limited to the one using SIP, and it is also possible to perform communication according to an appropriate protocol such as TCP / IP or UDP. is there.

  With reference to FIG. 3, the relay server 1 will be described by taking the call center server R1 disposed in the LAN 91 as an example. FIG. 3 is a functional block diagram of the call center server R1.

  As shown in FIG. 3, the call center server R1 includes a LAN interface 501, a WAN interface 502, a control unit 503, a client terminal information database 511, an access permission information database 513, a communication management information database 515, and communication contents. An information database 516 is provided as a main component.

  The LAN interface 501 is an interface that uses a private IP address to communicate with the client terminal 5 connected to the same LAN as its own device.

  The WAN interface 502 is an interface that communicates with each device such as the external server 2 connected to the Internet using a global IP address.

  The control unit 503 is a processing unit that controls various communications performed via the LAN interface 501 and the WAN interface 502, and controls various communication processes according to protocols such as TCP / IP, UDP, and SIP.

  The client terminal information database 511 is a database that manages account information of the client terminal 5 that is locally connected to the call center server R1 via the LAN 91 in association with a private IP address.

  An example of the contents of the client terminal information stored in the client terminal information database 511 is shown in FIG. As shown in FIG. 4, in the client terminal information, for each client terminal 5 connected to the LAN 91, a node tag including attribute information related to the client terminal 5 is described. The attribute information related to the client terminal 5 includes the private IP address (“addr”), identification information (“id”), name (“name”), port information (“port”), and the like of the client terminal 5. Although the description of the client terminals 5 other than the client 11 and the client 12 is omitted in the stored content example illustrated in FIG. 4, in practice, other client terminals 5 (for example, connected to the relay server 1 via the LAN 91 (for example, The attribute information regarding client 13) is also described.

  The relay server information database 512 is a database that manages information on the relay servers 1 that perform relay communication and the client terminals 5 that are connected to the respective relay servers 1.

  An example of storage contents of relay server information stored in the relay server information database 512 is shown in FIG. The relay server information shown in FIG. 5 is a combination of information created in each of the relay servers 1 (call center server R1, dispatch destination server R2, customer server R3, etc.) that perform relay communication. The relay server information is created by the call center server R1 by combining the relay server information created by the call center server R1 itself with each relay server information received from the other relay server 1 that performs relay communication.

  In the relay server information shown in FIG. 5, a site tag described for each relay server 1 and a node tag of a child element having the site tag as a parent element are described. The site tag includes attribute information related to the relay server 1. The attribute information includes identification information (“id”) of the relay server 1, name (“name”) of the relay server 1, and activation information (“stat”). ") Etc. The node tag that is a child element of the site tag includes attribute information related to the client terminal 5 that logs on to the relay server 1. The attribute information related to the client terminal 5 includes the identification information (“id”) of the client terminal 5 and the name (“name”) of the client terminal 5. Although the description of the relay server 1 other than the relay server 1 and the relay server 2 is omitted in the storage content example of FIG. 5, the attribute related to the other relay server 1 (for example, the relay server 3) connected through the external server 2 is actually used. Information is also described. Further, in FIG. 5, as in FIG. 4, a part of the description regarding the client terminal 5 is omitted.

  The relay group information database 521 is a database that manages relay group information for performing relay communication.

  An example of the contents of relay group information stored in the relay group information database 521 is shown in FIG. As shown in FIG. 6, in the relay group information, a group tag and a site tag of a child element having the group tag as a parent element are described. The group tag includes attribute information related to the relay group. Examples of the attribute information include relay group identification information (“id”) and a relay group name (“name”). The site tag includes attribute information related to the relay server 1 included in the relay group, and the attribute information includes identification information (“id”) of the relay server 1 and the like. Further, additional relay groups can be created. In this case, unique identification information different from other relay groups is given to the new relay group. As a result, settings such as data exchange only within the relay group are possible.

  The routing group information database 522 is a database that manages routing group information used for performing routing processing using the relay communication system. Details of the routing group information and routing processing using the routing group information will be described later.

  The example of stored contents of client terminal information shown in FIG. 4, the example of stored contents of relay server information shown in FIG. 5, and the example of stored contents of relay group information shown in FIG. 6 are merely examples, and appropriate attribute information Of course, element information can be added or deleted.

  The access permission information database 513 is a database that manages, for each customer server, identification information, various settings, and the like of a relay server that is permitted to communicate except for the call center server R1. The customer server here means the relay server 1 including the customer server R3 illustrated in FIG. This access permission information database 513 is configured so that, for example, when a serviceman dispatch destination is in charge of remote maintenance of which customer factory, it is determined in advance so that only the responsible serviceman dispatch destination can perform remote maintenance. This is for restricting access to the customer server.

  The access permission information database 513 will be specifically described with reference to FIG. FIG. 7 is a table showing the contents of the access permission information database 513.

  As described above, the call center server R1 of the present embodiment is connected not only to the dispatch destination server R2 and the customer server R3 but also to a large number of relay servers 1. In FIG. 7, among the relay servers 1, customer servers are represented as relay servers 3, 31, 32, 33, and 34, and dispatch destination servers are represented as relay servers 2, 21, 22, and 23.

  In the table of FIG. 7, customer servers are described in the target column. On the other hand, the destination column describes the dispatch destination server. In this table, a dispatch destination server permitted to communicate with a certain customer server is described in a form associated with the customer server. For example, relay server 3 permits communication from relay servers 2, 21, and 23.

  For example, when there is a connection request from the dispatch destination server R2, the control unit 503 creates an access permission list based on information registered in the access permission information database 513, and transmits the access permission list to the dispatch destination server R2. . This access permission list is a list indicating the relay server 1 that is permitted to communicate from the dispatch destination server R2 and the communication conditions.

  Note that the control unit 503 may transmit information registered in the access permission information database 513 to the dispatch destination server R2 without creating an access permission list. The dispatch destination server R2 can grasp customer servers with which it can communicate by performing appropriate processing on this information.

  The communication management information database (connection management information storage unit) 515 is a database that manages connection times and connection statuses between customer servers and dispatch destination servers.

  The communication management information database 515 will be specifically described with reference to FIG. FIG. 8 is a table showing the contents of the communication management information database 515. In the table of FIG. 8, each row indicates a media session established between the relay servers 1. In the active column, the relay server 1 on the side that requested access is described, and in the passive column, the relay server 1 on the side that requested access is described. Further, the start time of the media session is described in the start-time column, and the end time of the media session is described in the end-time column. When the media session is ongoing, “connecting” is recorded in the end-time column.

  The communication content information database (communication content information storage unit) 516 is a database that stores information exchanged between the dispatch destination server and the customer server during communication and related information.

  The dispatch destination server R2 and the customer server R3 include a LAN interface, a WAN interface, and a control unit. The configuration of the dispatch destination server R2 and the customer server R3 substantially corresponds to the configuration in which the access permission information database 513 and the communication management information database 515 are omitted from the configuration of the call center server R1 shown in FIG. Description is omitted.

  Next, packet routing control in the relay communication system of this embodiment will be described. In the present embodiment, the client terminals 5 belonging to the remote LAN can communicate with each other without being aware of the WAN, so that packet routing processing can be performed in the application layer. . Hereinafter, a description will be given with reference to FIG. In the following description, in order to distinguish each client terminal 5, there is a case where an alphabet is added to the end of the code and displayed as a client terminal 5a, a client terminal 5b,.

  In the following description, a case will be described in which a packet is routed between the dispatch destination LAN 92 and the customer LAN 93 on the assumption that the serviceman remotely maintains the client terminal 5 at the customer factory. In the following description regarding routing, it is assumed that a media session has already been established between the dispatch destination server R2 and the customer server R3. Processing for establishing a media session between the dispatch destination server R2 and the customer server R3 will be described later.

  In the relay communication system of this embodiment, private IP addresses are assigned to the LANs 91 to 93 connected to each other via the WAN. Each private address is managed so as to be uniquely determined in the relay communication system. As an example, as shown in FIG. 5, it is assumed that the address of the destination LAN 92 is “172.16.1.0/24” and the address of the customer LAN 93 is “172.30.2.0/24”. I will explain.

  In the relay communication system according to the present embodiment, in order to realize packet routing in the application layer, at least one relay server 1 or client terminal 5 that can function as a routing device is prepared in the LAN to be routed. Yes. For example, in the case of this embodiment, it is assumed that the dispatch destination server R2 can function as a routing device in the dispatch destination LAN 92 and the client terminal 5d can function as a routing device in the customer LAN 93, respectively.

  In the relay communication system of this embodiment, when routing a packet, first, a search for a routable LAN is performed. Specifically, a routable LAN search command (hereinafter simply referred to as a LAN search command) is transmitted from any client terminal 5 to the relay server 1. In the following description, it is assumed that the client terminal 5b has transmitted a routable LAN search command to the dispatch destination server R2.

  Here, the “routable LAN” is a LAN including the relay server 1 or the client terminal 5 as a routing device. In FIG. 9, the dispatch destination LAN 92 and the customer LAN 93 are described as one, but actually, a plurality of LANs can be connected to each relay server 1, and each LAN is not necessarily routed. It is not always possible. Therefore, it is necessary to search for a routable LAN in this way.

  The dispatch destination server R2 that has received the LAN search command transfers the LAN search command to the other relay servers 1 (call center server R1, customer server R3) constituting the relay group by referring to the relay group information. . Each relay server 1 (call center server R1, dispatch destination server R2, customer server R3) that has received the LAN search command communicates with each client terminal 5 registered in the client terminal information database 511, and connects itself. It is checked whether or not there is a client terminal 5 that can function as a routing device in the connected LAN. When the client terminal 5 having a function as a routing device is found, the LAN including the client terminal 5 is a routable LAN. Even when the relay server 1 itself can function as a routing device, the LAN including the relay server 1 is a routable LAN. In such a case, the relay server 1 generates LAN search response information that associates the fact that the LAN is a routable LAN and the private IP address of the LAN.

  Subsequently, the call center server R1 and the customer server R3 transmit the generated LAN search response information to the dispatch destination server R2. The dispatch destination server R2 generates combined LAN search response information obtained by combining the LAN search response information generated by itself and the LAN search response information received from each relay server 1. The dispatch destination server R2 transfers the combined LAN search response information to the client terminal 5b. The client terminal 5b generates and stores LAN search result information based on the combined LAN search response information.

  An example of LAN search result information stored in the client terminal 5b is shown in FIG. In the LAN search result information, a child element network tag having a routing_network tag as a parent element is described. Each network tag describes private IP address information (“addr”) of a routable LAN. In this way, the private IP address of the LAN that can be routed in the relay communication system can be specified in the client terminal that is the transmission source of the LAN search command. For example, in this embodiment, as shown in FIG. 10, the destination LAN 92 (addr = “172.16.1.0/24”) and the customer LAN 93 (addr = “172.30.2.0/24”) Is identified as a routable LAN.

  Next, in the client terminal 5b that identifies the routable LAN, a routing route search (specifically, a routing point) is performed. The client terminal 5b specifies a routing target LAN from among routable LANs, and transmits a routing route search command (hereinafter simply referred to as a route search command) to the dispatch destination server R2. Hereinafter, a case where the dispatch destination LAN 92 and the customer LAN 93 are designated as the routing target LAN will be described.

  The dispatch destination server R2 that has received the route search command refers to the relay group information and transfers the route search command to the other relay servers 1 (call center server R1 and customer server R3) that constitute the relay group. .

  Each relay server 1 (call center server R1, dispatch destination server R2, customer server R3) that has received the route search command communicates with each client terminal 5 registered in the client terminal information database 511, so that It is checked whether or not there is a client terminal 5 that can function as a routing device for a LAN designated as a routing target LAN in the connected LANs.

  For example, in the case of this embodiment, the client terminal 5d can function as a routing device for a LAN (customer LAN 93) designated as a routing target LAN. In this way, the client terminal 5d that can function as a routing device for the routing target LAN can function as a routing point for routing packets between designated LANs (between the dispatch destination LAN 92 and the customer LAN 93). When a client terminal 5d that can function as a routing point is found, the customer server R3 generates route search response information that associates the private IP address of the customer LAN 93 with the identification information of the client terminal 5d.

  On the other hand, when the relay server 1 itself can function as a LAN routing device designated as a routing target LAN, the relay server 1 can function as a routing point. For example, in the present embodiment, the dispatch destination server R2 can function as a routing device for a LAN designated as a routing target LAN (dispatch destination LAN 92). In such a case, the dispatch destination server R2 generates route search response information in which the private IP address of the dispatch destination LAN 92 is associated with its own identification information.

  Subsequently, the customer server R3 transmits the generated route search response information to the dispatch destination server R2. The dispatch destination server R2 generates combined route search response information obtained by combining the route search response information received from the customer server R3 and the route search response information generated by itself. The dispatch destination server R2 transfers the combined route search response information to the client terminal 5b. The client terminal 5b generates and stores route search result information based on the combined route search response information.

  An example of route search result information stored in the client terminal 5b is shown in FIG. In the route search result information, a network tag of a child element having a routing_network tag as a parent element is described. In each network tag, private IP address information (“addr”) of a routable LAN and identification information (“router”) of a device that can function as a routing point are described in association with each other. In this way, a search for a routing path between LANs designated as routing target LANs (that is, specification of a routing point) can be realized.

  Next, a routing session is established. The routing session is a media session used for packet routing control in the relay communication system of the present embodiment.

  In order to establish a routing session, the client terminal 5b transmits information specifying a routing point used in the routing session to the dispatch destination server R2. In the dispatch destination server R2, routing group information is generated based on the route search result information. The routing group information is routing setting information for executing routing control using the relay communication system, and is stored in the routing group information database 522.

  An example of the routing group information stored in the routing group information database 522 is shown in FIG. In the routing group information, the network tag describes the local IP address of the routing target LAN and the identification information of the device to be used with the routing point in association with each other. In the session tag of the child element whose parent element is the routing_session tag, the start point (“start”) and the end point (“end”) of the routing session are described.

  Subsequently, the dispatch destination server R2 transfers the routing group information to the client terminal 5d that is the next routing point. Thereby, the information regarding the routing path | route between routing object LAN is shared in each routing point.

  After each routing point receives the routing group information, a routing session including a plurality of media sessions is established between the routing points. Specifically, a media session is established between the customer server R3 and the client terminal 5d. As described above, a media session has already been established between the dispatch destination server R2 and the customer server R3. The two media sessions constitute a routing session that connects the routing points (the dispatch destination server R2 and the client terminal 5d).

  Next, a case where a packet is transmitted from the terminal 5a in the dispatch destination LAN 92 to the client terminal 5f in the customer LAN 93 via a routing session will be described. In this case, the client terminal 5a creates a packet designating the private IP address (1722.30.2) of the client terminal 5f. Subsequently, the client terminal 5a transfers the packet to the dispatch destination server R2 that is a routing point of the LAN (the dispatch destination LAN 92) to which the client terminal 5a itself belongs.

  When receiving a packet to be routed, the dispatch destination server R2 as a routing point specifies a LAN to which the packet is to be delivered based on the destination private IP address (172.23.2.3). In this explanation, the destination LAN of the packet is the customer LAN 93 (the private IP address is 172.30.2.0/24). Next, the dispatch destination server R2 determines whether or not a valid routing session is established with the customer LAN 93 by referring to the routing group information. For example, in the example currently being described, it can be seen that a routing session has already been established with the customer LAN 93 by referring to the routing group information. Therefore, the packet may be transmitted using the routing session. It will be. If a routing session is not established here, an error occurs because transmission of a packet through the routing session is impossible.

  After identifying the routing session used for packet transmission, the dispatch destination server R2 as a routing point sends out the packet received from the client terminal 5a via the routing session. Thereby, the packet is received by the client terminal 5d which is the next routing point.

  The client terminal 5d, which is the next routing point, transfers the packet to the private IP address (1722.30.2) designated as the destination. Thereby, the packet is delivered to the client terminal 5f. Similarly, in the reverse communication (when a packet is transmitted from the client terminal 5f to the client terminal 5a), the packet can be routed through the routing session.

  The routing-related processing described above, that is, processing such as search for a routable LAN, search for a routing route, and the like are performed in the application layer. As described above, in the present embodiment, the routing target data is flowed in the routing session of the application layer. Therefore, the routing described above is different from normal IP routing.

  By performing routing in the application layer in this manner, remote LANs can communicate with each other using private IP addresses without being aware of WAN, and routing routes and the like can be determined according to the configuration of the relay communication system. Can be constructed flexibly. It should be noted that, in the case of performing single transmission / reception of information without establishing a routing session, it is needless to say that packets may be transmitted / received by a normal method without performing the above routing.

  In the present embodiment, the service person dispatched to the service person can perform remote maintenance of the client terminal 5 at the customer factory via the routing session described above. By the way, the routing session established as described above includes a media session between the relay servers 1. For example, in the above example, the routing session for transmitting and receiving packets between the client terminal 5a and the client terminal 5f includes a media session established between the dispatch destination server R2 and the customer server R3. ing. Therefore, it can be said that the service person performs remote maintenance via a media session established between the dispatch destination server R2 and the customer server R3. In the following description, even if the service person performs remote maintenance, the description of the entire routing session is omitted, and the part of the media session established between the dispatch destination server R2 and the customer server R3. There may only be explained.

  As described above, when the media session is established between the dispatch destination server R2 and the customer server R3, the remote maintenance work such as confirmation of operation status and software update is performed on the client terminal 5 of the customer server R3. It can be performed. In addition, when a problem occurs in the client terminal 5, a recovery operation such as applying a recovery application can be performed.

  Next, communication processing according to this embodiment will be described with reference to FIG. FIG. 13 is a sequence diagram illustrating communication processing in the first half of the maintenance work.

  When performing remote maintenance such as remote maintenance, the service person operates the client terminal 5 and transmits an access permission list request (GET method) with the call center server R1 as a transmission destination via the dispatch destination server R2 (sequence). Number 1).

  As described above, in this embodiment, a request or the like may be transmitted from the client terminal 5 via each relay server 1, but in the following description, a specific description of processing for operating the client terminal 5 is omitted. There are things to do.

  In this access permission list request, the account of the call center server R1 as the transmission destination is specified. The external server 2 acquires the global IP address of the call center server R1 by referring to the relay server account information database 203, and relays the request from the dispatch destination server R2 to the call center server R1.

  As described above, communication between each relay server 1 of the present embodiment is performed via the external server 2, and the same applies to the following. Therefore, in the following description, a specific description of communication processing via the external server 2 may be omitted.

  The call center server R1 that has received the access permission list request creates an access permission list indicating the relay servers that the dispatch destination server R2 can access based on the access permission information database 513. Then, the call center server R1 transmits this access permission list to the dispatch destination server R2.

  Then, the service person selects a customer server with which the service person should communicate based on the access permission list. In the present embodiment, it is assumed that the customer server R3 is selected as the connection destination customer server.

  However, as described above, the customer server R3 normally does not accept communications from other than the call center server R1. In order to start this communication, it is necessary to notify the access source (dispatch destination server R2) from the call center server R1 to the customer server R3. Therefore, the service person transmits an access destination notification (Access method) to the call center server R1 via the dispatch destination server R2 (sequence number 2).

  The selection of the customer server and the notification of the access destination may be automatically performed by the dispatch destination server R2 or the client terminal 5 by a preset method.

  Upon receiving this notification, the call center server R1 stores in the communication management information database 515 that the dispatch destination server R2 wishes to communicate with the customer server R3. Then, the call center server R1 transmits an access permission request (ACCESS_PERMIT method) for the destination server R2 to the customer server R3 (sequence number 2.2).

  The customer server R3 that has received this access permission request performs processing for accepting communication from the dispatch destination server R2, and returns an OK response to the call center server R1. After receiving the OK response from the customer server R3, the call center server R1 returns an OK response to the access permission request to the dispatch destination server R2.

  Upon receiving this OK response, the dispatch destination server R2 transmits a connection request (INVITE method) to the customer server R3 (sequence number 3). The dispatch destination server R2 that has received the OK response to this transmits a final response (ACK method) to INVITE to the customer server R3 (sequence number 4). Then, the customer server R3 transmits a MediaSession command to the dispatch destination server R2. By this command, a communication path (routing session) is established between the dispatch destination server R2 and the customer server R3 (sequence number 5).

  When the communication path is established, the dispatch destination server R2 notifies the call center server R1 of the establishment of the routing session (NOTIFY_ESTABLISHMENT method, sequence number 5.1). Then, the call center server R1 stores in the communication management information database 515 that the dispatch destination server R2 is performing relay communication with the customer server R3, and sends an OK response to the notification of routing session establishment to the dispatch destination server R2. In return.

  Then, the service person performs maintenance work on the customer server R3 (or the client terminal 5 connected to the customer server R3) via the dispatch destination server R2. In such maintenance work, not only information used for maintenance etc. is transmitted from the dispatch destination server R2 to the customer server R3, but also from the customer server R3 to the dispatch destination server R2 from the service person. Information is sent in response to the request. For example, it is conceivable that the service person requests the operating status from the customer server R3 and the like, and the customer server R3 transmits the operating status report.

  By the way, the call center server R1 of the present embodiment receives information exchanged between the dispatch destination server and the customer server and information indicating an outline of this information as communication content information and stores them in the communication content information database 516. doing. There are various types of information indicating this outline, for example, information indicating an outline of maintenance contents of information exchanged via a communication path, information indicating a data size, and the like. In the following description, “information indicating an outline of actually exchanged information” may be referred to as “communication outline information”.

  Further, the call center server R1 selects the relay server 1 that is the target of requesting the communication content information, based on the communication management information stored in the communication management information database 515. From the communication management information, as described above, it is possible to know which dispatch destination server is connected to which customer server.

  The call center server R1 can arbitrarily select which relay server 1 receives the communication content information and the communication outline information. However, this selection is preferably performed so that the load is not concentrated on some relay servers 1. Below, the dispatch destination server R2 and the customer server R3 that are currently connected are selected as the relay servers 1 for which communication content information is requested. In particular, the communication summary information is received from the dispatch destination server R2 and actually exchanged. The information will be described in the case where each information is selected to be received from the customer server R3.

  Hereinafter, a communication process after the call center server R1 receives the communication content information will be specifically described with reference to FIG. FIG. 14 is a sequence diagram showing communication processing in the latter half of the maintenance work.

  First, the call center server R1 specifies communication outline information (session info) and transmits a request (GET method) to the dispatch destination server R2 (sequence number 6). In this request, the type of communication summary information is also specified, and the dispatch destination server R2 that has received the request transmits the communication summary information corresponding to this type to the call center server R1. In FIG. 14, the request for the communication outline information is shown only once, but in actuality, the request is made as many times as necessary.

  For example, the outline of the maintenance content is designated as the type of the communication outline information, and information such as which service person applied the maintenance work to the client terminal 5e at the customer factory is obtained. Suppose. By storing this information in the communication content information database 516, it is possible to improve the efficiency of the maintenance work such as having the same person perform the same maintenance work. Further, by comparing this information with a list of applications applicable to the client terminal 5e, it can be determined whether or not an appropriate application is applied.

  The above analysis is configured to be automatically performed by the call center server R1 in the present embodiment, but may be configured to be determined by an operator at the call center.

  When the above analysis is performed and it is necessary to acquire more detailed information, for example, when an abnormality is suspected, a process for establishing a communication path between the call center server R1 and the customer server R3 is performed. Is performed (sequence numbers 7 to 9). Since this process is the same as the process for establishing a communication path between the dispatch destination server R2 and the customer server R3, the description thereof is omitted.

  When a communication path is established between the call center server R1 and the customer server R3, the customer server R3 receives the information received from the dispatch destination server R2 (receiveData) and the information transmitted to the dispatch destination server R2 (sendData). Are transmitted simultaneously to the call center server R1 (sequence numbers 10 and 11). Specifically, the customer server R3, when receiving information from the dispatch destination server R2, simultaneously transmits a copy thereof to the call center server R1. When the customer server R3 transmits information to the dispatch destination server R2, the customer server R3 simultaneously transmits a copy of the information to the call center server R1.

  Then, based on the obtained information, the call center worker determines, for example, whether or not an abnormality has actually occurred, and backs up data used for maintenance work. Here, if it is determined that it is not necessary to receive further communication detailed information, a communication disconnection request (BYE method) is transmitted to the customer server R3, whereby the established communication path is disconnected. (Sequence number 12). The communication is thus completed.

  Then, after the maintenance work is completed, the service person transmits a communication disconnection request (BYE method) to the customer server R3 via the dispatch destination server R2, thereby disconnecting the established communication path. (Sequence number 13). Then, the dispatch destination server R2 notifies the call center server R1 of the end of the routing session (NOTIFY_TERMINATION method, sequence number 13.1). Receiving this, the call center server R1 stores in the communication management information database 515 that the communication path between the dispatch destination server R2 and the customer server R3 has been disconnected.

  As described above, the call center server R1 of this embodiment includes the communication management information database 515, the communication content information database 516, and the control unit 503. The communication management information database 515 stores the connection status between the relay servers 1. The communication content information database 516 stores communication content information that is information related to communication content exchanged during communication between the relay servers 1. The control unit 503 selects the dispatch destination server R2 and the customer server R3 based on the connection status stored in the communication management information database 515, receives the communication content information, and stores it in the communication content information database 516.

  Thereby, since the call center server R1 stores the communication content information between the relay servers 1, the call center server R1 can centrally manage the communication content information. Therefore, based on the content of the communication content information database 516, an appropriate service person can be selected according to the state of the customer factory. Furthermore, the communication content information database 516 can be used from the service person and the customer factory through the respective relay servers 1. Further, based on the communication content stored in the communication content information database 516, the operating status of the customer server R3 and its client terminal 5 can be analyzed. Therefore, even when an abnormality occurs and when inappropriate communication is performed, the cause can be easily investigated.

  Further, in the call center server R1 of the present embodiment, the control unit 503 requests, as communication content information, necessary information from among the information regarding the communication content to at least one of the relay servers 1 that communicate with each other. Then, the control unit 503 receives the communication content information and stores it in the communication content information database 516.

  Thereby, the call center server R1 can acquire the communication content information at a timing convenient for itself. Further, information necessary for managing the relay server 1 differs depending on how the relay server 1 is managed, but various information can be obtained by selecting and requesting necessary information from information regarding communication contents. Management can be performed flexibly corresponding to management contents.

  Further, the call center server R1 of the present embodiment receives the communication content information while the dispatch destination server R2 and the customer server R3 are communicating.

  As a result, the call center server R1 can determine whether or not appropriate communication is performed between the dispatch destination server R2 and the customer server R3 during the communication. Therefore, even when inappropriate communication is performed, it can be detected during the communication.

  Further, in the call center server R1 of the present embodiment, the control unit 503 establishes a communication path with the customer server R3 during communication between the dispatch destination server R2 and the customer server R3, and simultaneously transmits communication content information. To receive.

  Thereby, it is possible to quickly know on the call center server R1 side that an abnormality such as transmission / reception of unnecessary information between relay servers has occurred. The customer server R3 only needs to transmit the communication content information to the call center server R1 at the same time each time it communicates with the dispatch destination server R2. Accordingly, the customer server R3 can quickly discard unnecessary communication content information among the communication content information exchanged with the dispatch destination server R2.

  Next, a modification of the above embodiment will be described. FIG. 15 is a sequence diagram illustrating a communication process according to a modification. In FIG. 15, sequence numbers 11 to 16.1 are the same as those in FIGS. 13 and 14 and will not be described.

  In the above embodiment, the communication content information is received while the communication path is established between the dispatch destination server R2 and the customer server R3. In this modification, this communication path is The communication content information is received after being disconnected.

  Specifically, when notified from the dispatch destination server R2 that the communication path has been disconnected, the call center server R1 returns an OK response to this notification. Then, the dispatch destination server R2 of the present modification transmits the information received from the customer server R3 (receiveData) and the information transmitted to the customer server R3 (sendData) to the call center server R1 (sequence number 17.1). , 17.2).

  Then, after the reception of the communication content information is completed, the call center server R1 returns an OK response indicating that the reception is completed to the dispatch destination server R2.

  At the time of transmission of the communication content information in the present modification, the communication path between the dispatch destination server R2 and the customer server R3 is disconnected, and therefore no more between the dispatch destination server R2 and the customer server R3. There is no exchange of information. Therefore, the information transmitted / received with the sequence numbers 17.1 and 17.2 includes all the information transmitted / received while the communication path is established between the dispatch destination server R2 and the customer server R3.

  Therefore, the communication content information transmitted in the present modification has a large data size, and continuing to store this information is a burden on the destination server R2. Therefore, in this modification, it is not the structure corresponding to transmission of the request | requirement from call center server R1, but is the structure which transmits communication content information from dispatch destination server R2.

  In addition, it can replace with dispatch destination server R2 and can receive communication content information from customer server R3. Which relay server 1 is used for reception is selected in advance by the call center server R1, and a notification to that effect is given to the selected relay server 1.

  As described above, the call center server R1 according to the present modification receives the communication content information after the communication between the dispatch destination server R2 and the customer server R3 is completed.

  Accordingly, the call center server R1 can receive the communication content information without imposing a load on the dispatch destination server R2 and the customer server R3 that are in communication.

  Although the embodiment and the modification of the present invention have been described above, the above configuration can be further modified as follows.

  The client terminal information, relay server information, relay group information, routing group information, etc. have been described as XML format data when described with reference to the drawings. However, the format for storing the information is not limited to this. Each information can be stored in an appropriate format.

  In the above embodiment, the communication outline information is requested at sequence number 6 in FIG. 14, but information that is actually exchanged may be requested instead of the outline as the target of this request. In this case, since receiving in real time may not be appropriate from the viewpoint of the amount of communication or the like, a specific time zone may be specified, and the information request may be made only during that time zone.

  In the embodiment and the modification, the call center server R1 receives the information exchanged between the dispatch destination server R2 and the customer server R3 and the related information, but the information exchanged between the other relay servers 1 However, it can be received similarly.

  In the above modification, in the sequence numbers 17.1 and 17.2 in FIG. 15, the call center server R1 receives all the information exchanged between the customer server R3 and the dispatch destination server R2. However, information may be appropriately selected and received according to the data size, information content, and the like.

R1 call center server (management relay server)
R2 Dispatch server R3 Customer server 503 Control unit 515 Communication management information database (connection management information storage unit)
516 Communication content information database (communication content information storage unit)

Claims (6)

A connection management information storage unit for storing the connection status between relay servers;
Information exchanged during communication between the relay servers, communication outline information including an outline of information exchanged during communication between the relay servers, including processing performed by communication between the relay servers; , Communication content information storage unit for storing,
The target relay server is selected based on the connection status stored in the connection management information storage unit, and the information exchanged during the communication between the relay servers or the communication summary information is selected from the relay server. A control unit that receives and stores in the communication content information storage unit,
A management relay server comprising:
The management relay server according to claim 1,
The control unit requests, as at least one of the relay servers communicating with each other, necessary information as information on the communication content as the communication content information, receives the communication content information, and transmits the communication information. A management relay server characterized in that it is stored in a content information storage unit. The management relay server according to claim 1 or 2,
The management relay server, wherein the communication content information is received during communication between the relay servers. The management relay server according to claim 1 or 2,
The management relay server receiving the communication content information after communication between the relay servers is completed. The management relay server according to claim 1,
The control unit establishes a communication path with at least one of the relay servers during communication between the relay servers, and simultaneously receives communication content information. Management relay server,
A plurality of relay servers capable of communicating with each other;
With
The management relay server is
A connection management information storage unit for storing a connection status between the relay servers;
Information exchanged during communication between the relay servers, communication outline information including an outline of information exchanged during communication between the relay servers, including processing performed by communication between the relay servers; , Communication content information storage unit for storing,
The target relay server is selected based on the connection status stored in the connection management information storage unit, and the information exchanged during the communication between the relay servers or the communication summary information is selected from the relay server. A control unit that receives and stores in the communication content information storage unit ,
A relay communication system comprising:

Images