JP2012221051A - Relay server and relay communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an operator with various login forms while securing sufficient security by allowing work only to limited operators in a relay communication system.SOLUTION: A relay communication system 1 is configured by including a center terminal 5, terminals of a connecting side, and terminals to be a connected side. IDs allowing login to the relay communication system 1 by an input by an operator include operator IDs (Op1 to Op4) unique to each operator, and a guest ID (Guest) different from the operator IDs. The center terminal 5 creates a connection job obtained by associating a terminal to be connected side (for example, a first terminal to be maintained 7A) with an operator ID or a guest ID representing a candidate (connection candidate) allowed to be connected to the terminal. When an operator logins from a terminal of a connecting side (for example, a first maintenance terminal 9A) with an operator ID or a guest ID, the operator is allowed to work on a connection job having the ID as a connection candidate.

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 technique called a virtual private network (VPN) is known. This VPN is used, for example, for applications in which terminals connected to LANs at a plurality of bases provided for each region communicate via the Internet. If the VPN is used, another remote LAN can be used as if it were a directly connected network. The VPN is used for, for example, a remote maintenance of a terminal provided at another base. A maintenance target terminal can receive remote maintenance or the like from a device connected to another LAN at a remote location.

  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

  By the way, in this type of system, it is common for a remote maintenance worker (operator) to be assigned an ID uniquely identifying himself / herself, and to log in to the system using that ID to perform work. . This method would be advantageous for properly managing login privileges and tracking who logged into the system and worked.

  On the other hand, in the above system, for example, in the case of an unusual situation, even if the same operator logs in, if another ID can be used instead of a normal time ID, it can be clearly distinguished from the normal work, etc. May be useful in terms. However, with the conventional configuration, it has been difficult to realize flexible handling of IDs as described above while ensuring security by allowing login to only a limited number of people.

  The present invention has been made in view of the above circumstances, and its purpose can be varied as needed while allowing only a limited number of operators according to the work to be performed and ensuring sufficient security. It is an object of the present invention to provide a relay server that can provide an operator with work in a simple login form.

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 the 1st viewpoint of this invention, the relay server with a management function of the following structures is provided. That is, this relay server with a management function includes an operator list storage unit, a login authentication unit, a connection job creation unit, a candidate job list transmission unit, and an execution determination unit. The operator list storage unit stores a list of operators that can log in to the relay communication system including the relay server and other relay servers. The login authentication unit determines whether or not the operator can log in based on at least the ID input by the operator and the contents of the operator list storage unit. The connection job creation unit creates a connection job in which a connection-side relay server is associated with an ID that is a connection candidate that can be permitted to be connected to the connection-side relay server. . In response to a request from the connection-side relay server, the candidate job list transmission unit is a list of the connection jobs in which the ID input by the logged-in operator via the connection-side relay server is set as a connection candidate. The candidate job list is transmitted to the relay server on the connection side. The execution determining unit, when the operator selects a connection job from the candidate job list, in response to an inquiry from the connection-side relay server, the connection-side relay server and the connected-side relay server, It is determined whether a connection session can be established by establishing a routing session. The ID that allows the operator to log in to the relay communication system includes an operator ID that is uniquely assigned to each operator and another setting ID that is set separately from the operator ID. . The connection job creation unit is configured to create a connection job in which the relay server on the connected side is associated with the different setting ID.

  As a result, when the operator logs in to the relay communication system from the relay server on the connection side using the operator ID or another setting ID, a list of connection jobs for which the ID is a connection candidate is displayed, and a connection job is selected from this list. Thus, it is possible to establish a routing session by connecting to the corresponding connected relay server and perform a predetermined operation. Therefore, the operator can smoothly perform from the login to the actual work without departing from the access authority permitted to the operator. In addition, it is possible to provide the operator with various log-in operations as necessary while permitting the operation only to a predetermined operator according to the target of the operation and ensuring sufficient security.

  The relay server with a management function preferably includes a special operator list storage unit that stores a list of operators that can log in to the relay communication system using the different setting ID among the operators.

  Thereby, since the operator who can use another setting ID can be managed by the special operator list storage unit, strong security can be realized.

  In the relay server with a management function, it is preferable that the operator list storage unit is configured to store the separate setting ID and an operator who can use the separate setting ID in association with each other.

  As a result, the access authority can be reliably managed by clearly associating the different setting ID with a specific operator.

  In the relay server with management function, when the operator set with the different setting ID logs in to the relay communication system using the operator ID, the operator is notified that the different setting ID is set. It is preferable that notification can be made.

  Thus, when another setting ID is set for a specific operator, the operation of notifying the operator of that fact can be omitted, so that smooth operation is possible.

  According to a second aspect of the present invention, a connection-side relay server having the following configuration is provided. That is, the connection-side relay server includes a management destination information storage unit, a selected job notification unit, a routing session establishment unit, and a routing control unit. The management destination information storage unit includes an ID that an operator is required to input to log in to a relay communication system including itself and other relay servers, and connection candidates that can be permitted to be connected. Stores identification information of a relay server with a management function, which is a storage destination of a connection job that associates a connected relay server with an ID set thereto. The selected job notification unit receives the candidate job list that is a list of the connection jobs in which the ID input by the logged-in operator is set as a connection candidate from the relay server with management function, after receiving the candidate job list The connection job selected from the candidate job list is notified to the relay server with management function. When the routing session establishment unit receives that the execution of the selected connection job is permitted, the routing session establishment unit establishes a routing session used for packet routing with the connected relay server indicated by the connection job. Establish. The routing control unit performs routing control based on the routing session. The ID that allows the operator to log in to the relay communication system includes an operator ID that is uniquely assigned to each operator and another setting ID that is set separately from the operator ID. .

  As a result, when the operator logs in to the relay communication system from the relay server on the connection side using the operator ID or another setting ID, a list of connection jobs for which the ID is a connection candidate is displayed, and a connection job is selected from this list. Thus, it is possible to establish a routing session by connecting to the corresponding connected relay server and perform a predetermined operation. Therefore, the operator can smoothly perform from the login to the actual work without departing from the access authority permitted to the operator. In addition, it is possible to provide the operator with various log-in operations as necessary while permitting the operation only to a predetermined operator according to the target of the operation and ensuring sufficient security.

  According to the 3rd viewpoint of this invention, the relay communication system of the following structures is provided. That is, the relay communication system includes a relay server with a management function, a connection-side relay server, and a connected-side relay server. The connection-side relay server and the connected-side relay server can communicate with the management-function relay server. The relay server with a management function includes an operator list storage unit, a login authentication unit, a connection job creation unit, a candidate job list transmission unit, and an execution determination unit. The operator list storage unit stores a list of operators who can log in to the relay communication system. The login authentication unit determines whether or not the operator can log in based on the ID input by the operator and the contents of the operator list storage unit. The connection job creation unit creates a connection job in which a connection-side relay server is associated with an ID that is a connection candidate that can be permitted to be connected to the connection-side relay server. . In response to a request from the connection-side relay server, the candidate job list transmission unit is a list of the connection jobs in which the ID input by the logged-in operator via the connection-side relay server is set as a connection candidate. The candidate job list is transmitted to the relay server on the connection side. The execution determining unit, when the operator selects a connection job from the candidate job list, in response to an inquiry from the connection-side relay server, the connection-side relay server and the connected-side relay server, It is determined whether a connection session can be established by establishing a routing session. The IDs that can be logged into the relay communication system by an operator input include an operator ID that is uniquely assigned to each operator and a different setting ID that is set separately from the operator ID. The connection job creation unit is configured to create a connection job in which the relay server on the connected side is associated with the different setting ID. The connection-side relay server includes a management destination information storage unit, a selected job notification unit, a routing session establishment unit, and a routing control unit. The management destination information storage unit stores identification information of the relay server with management function. The selected job notification unit receives the candidate job list that is a list of the connection jobs in which the ID input by the logged-in operator is set as a connection candidate from the relay server with management function, after receiving the candidate job list The connection job selected from the candidate job list is notified to the relay server with management function. When the routing session establishment unit receives that the execution of the selected connection job is permitted, the routing session establishment unit establishes a routing session used for packet routing with the connected relay server indicated by the connection job. Establish. The routing control unit performs routing control based on the routing session.

  As a result, when the operator logs in to the relay communication system from the relay server on the connection side using the operator ID or another setting ID, a list of connection jobs for which the ID is a connection candidate is displayed, and a connection job is selected from this list. Thus, it is possible to establish a routing session by connecting to the corresponding connected relay server and perform a predetermined operation. Therefore, the operator can smoothly perform from the login to the actual work without departing from the access authority permitted to the operator. In addition, it is possible to provide the operator with various log-in operations as necessary while permitting the operation only to a predetermined operator according to the target of the operation and ensuring sufficient security.

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 which shows the structure of a center terminal. The figure which shows the content of an operator list. The figure which shows the content of the maintenance terminal list. The figure which shows the content of a to-be-maintained terminal list. The figure which shows the content of a connection job list. The functional block diagram which shows the structure of a 1st maintenance terminal. The functional block diagram which shows the structure of a 2nd maintenance terminal. The sequence diagram which shows the flow of a process when a connection job is produced. The sequence diagram which shows the flow of the process performed at the time of login to the relay communication system by an operator. The sequence diagram which shows the flow of the process performed at the time of selection of the connection job by an operator. The sequence diagram which shows the flow of the process performed after completion | finish of a maintenance work. The figure which shows the content of a guest list. The figure which shows the operator list of the state in which guest ID was described. The figure which shows the connection job list in which the job list which uses guest ID as a connection candidate was described. The sequence diagram which shows a process when the connection job with respect to the said guest ID is created after registering a guest ID. The sequence diagram which shows a process in case an operator logs in to a relay communication system using guest ID. The sequence diagram which shows the process at the time of the operator who authenticated by guest ID selecting the connection job and performing maintenance work. The sequence diagram which shows the process performed after completion | finish of a maintenance work.

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

  As shown in FIG. 1, a relay communication system 1 is connected to a plurality of relay servers connected via a wide area network (WAN) 3 such as the Internet, and these relay servers via a LAN. And a client terminal. The relay server can communicate with other relay servers and client terminals connected to the other relay servers. The client terminal can communicate with other relay servers and client terminals connected to other relay servers via a relay server connected via a LAN.

  In the present embodiment, remote maintenance and management are performed using the relay communication system 1. In the relay communication system 1, the terminals functioning as the relay server are the center terminal 5, the first maintenance target terminal 7A, the second maintenance target terminal 7B, the first maintenance terminal 9A, and the second maintenance terminal 9B.

  The center terminal 5 is provided in the call center. A call center is a base where an operator who responds to an inquiry from the owner of a maintenance target device is enrolled. The center terminal 5 manages the access right of the maintenance terminal (or the operator who performs maintenance) to the maintenance target terminal. A center terminal operating terminal 11 as the client terminal is connected to the center terminal 5 via a LAN 13. The ID of the center terminal 5 is “Center@relaysystem.net”.

  The first maintenance target terminal 7A is provided at an installation destination of a device to be remotely maintained. A first maintenance target system 15A and a second maintenance target system 15B as the client terminals are connected to the first maintenance target terminal 7A via the LAN 17. The first maintenance target system 15A and the second maintenance target system 15B are a file server, a Web server, or the like that is a target of remote maintenance. The ID of the first maintenance target terminal 7A is “Target1@relaysystem.net”.

  The second maintenance target terminal 7B is provided at an installation destination of a device to be subjected to remote maintenance. A third maintenance target system 19A and a fourth maintenance target system 19B as the client terminals are connected to the second maintenance target terminal 7B via the LAN 21. The third maintenance target system 19A and the fourth maintenance target system 19B are a file server, a Web server, or the like that is a target of remote maintenance. The ID of the second maintenance target terminal 7B is “Target2@relaysystem.net”.

  The first maintenance terminal 9A is provided at a maintenance base where an operator who performs remote maintenance is present. A first maintenance operation terminal 23A and a second maintenance operation terminal 23B as the client terminals are connected to the first maintenance terminal 9A via the LAN 25. The ID of the first maintenance terminal 9A is “Maintenance2@relaysystem.net”.

  The second maintenance terminal 9B is provided at a maintenance base where an operator who performs remote maintenance is present. A third maintenance operation terminal 27A and a fourth maintenance operation terminal 27B as the client terminals are connected to the second maintenance terminal 9B via the LAN 29. The ID of the second maintenance terminal 9B is “Maintenance1@relaysystem.net”.

  In order for an operator at the maintenance base to perform maintenance work, it is necessary to log in to the relay communication system 1. The operator can log in to the relay communication system 1 by operating the maintenance operation terminal and inputting the ID and password. In the relay communication system 1 of this embodiment, the operator is not tied to a specific maintenance operation terminal, and can log in to the relay communication system 1 even when any maintenance operation terminal is used. After logging in to the relay communication system 1, the operator uses the maintenance operation terminal to perform remote maintenance of the maintenance target system within the range of access rights managed by the center terminal 5.

  Next, the configuration of the center terminal 5 will be described with reference to FIGS. FIG. 2 is a functional block diagram showing the configuration of the center terminal 5. FIGS. 3 to 6 are diagrams showing the contents stored in the database storage unit 33 of the center terminal 5.

  As shown in FIG. 2, the center terminal 5 includes an interface 35, a database storage unit 33, and a control unit 31.

  The interface 35 can communicate with a device connected to the LAN 13 using a private IP address. The interface 35 can perform communication via the WAN 3 using a global IP address.

  The database storage unit 33 includes an operator list storage unit 53, a guest list storage unit (special operator list storage unit) 54, a maintenance terminal list storage unit 55, a maintenance target terminal list storage unit 57, and a connection job list storage unit 59. And.

  The operator list storage unit 53 stores, for example, an operator list 53a shown in FIG. As shown in FIG. 3A, the operator list 53a includes “ID”, “password”, and “login relay server”. In the “ID” column, an ID of an operator who can log in to the relay communication system 1 is described. In the “password” column, a password necessary for logging in to the relay communication system 1 using the ID described in the same row is described. In the “login relay server” column, when the operator has logged in to the relay communication system 1 using the ID described in the same row, the operator ID and the relay server used by the operator ( ID of the center terminal or maintenance terminal) is described. If the operator has not logged in to the relay communication system 1, the “login relay server” is blank.

  In the example of FIG. 3A, operators Op1 to Op4 are registered in the operator list. For example, the first operator Op1 inputs a character string “Op1” as an ID and “abc” as a password. Thus, it can be seen that it is possible to log in to the relay communication system 1. From FIG. 3A, the second operator Op2 uses the center terminal 5 and the third operator Op3 logs in using the second maintenance terminal 9B, while the first operator Op1 and the fourth operator. It can be seen that Op4 has not logged into the relay communication system 1.

  The guest list storage unit 54 stores a list of special operators that can log in to the system using a guest ID described later. Details will be described later.

  The maintenance terminal list storage 55 stores a maintenance terminal list 55a shown in FIG. The maintenance terminal list 55a is composed of “name” and “terminal ID” describing the maintenance terminals constituting the relay communication system 1. In “Name”, a name given to the maintenance terminal is described. An appropriate name that is easy to understand, such as the installation location of the maintenance terminal (name of the maintenance base), can be given to this name. “Terminal ID” describes the ID of the maintenance terminal.

  The maintained terminal list storage unit 57 stores a maintained terminal list 57a shown in FIG. The to-be-maintained terminal list 57a includes “name” and “terminal ID” that describe the to-be-maintained terminals constituting the relay communication system 1. In “Name”, a name given to the maintenance target terminal is described. As this name, an appropriate name that is easy to understand, such as the installation location (company name) of the maintenance target terminal, can be given. “Terminal ID” describes the ID of the maintenance target terminal.

  The connection job list storage unit 59 stores information related to connection jobs. The connection job indicates a unit of maintenance work. The connection job is created by the center terminal 5 every time maintenance work is required for the maintenance target system, and is stored in the connection job list storage unit 59. The connection job list storage unit 59 stores a connection job list 59a including one or a plurality of connection jobs. The connection job list 59a is composed of “maintenance terminal ID”, “connection candidate ID”, and “job information” described for each connection job as shown in FIG. The “maintenance terminal ID” describes the ID of the maintenance target terminal connected to the same LAN as the maintenance target system requiring maintenance work. In “connection candidate ID”, an ID set as a candidate (connection candidate) that can be permitted to connect to the maintenance target terminal is described. In addition, in the “connection candidate ID”, IDs of one or a plurality of operators can be described, and a guest ID described later can also be described. “Job information” describes the state of the current connection job (for example, which operator is executing the connection job). The connection job is deleted from the connection job list 59a when the maintenance work is completed.

  From the example of FIG. 6A, it can be seen that the first connection job is created for the second maintenance target terminal 7B, and the IDs of the first operator Op1 and the third operator Op3 are set as connection candidates. . From the example of FIG. 6B, in addition to the first connection job, a second connection job is created for the first maintenance target terminal 7A, and the ID of the first operator Op1 is set as a connection candidate. I understand that. From the example of FIG. 6C, it can be seen that the first operator Op1 is executing the second connection job.

  The database storage unit 33 includes a log information storage unit (not shown), and stores information such as the time when the connection job was performed and the operator in charge.

  The control unit 31 includes a CPU, a RAM, a ROM, and the like, and can execute various processes by a program read from the ROM or the like. As illustrated in FIG. 2, the control unit 31 includes a login authentication unit 43, a connection job creation unit 45, an execution determination unit 47, a connection job list management unit 49, a candidate job list transmission unit 51, and permission information transmission. Part 52.

  The connection job creation unit 45 creates the connection job when receiving a notification from the maintenance target terminal that a failure has occurred in the maintenance target system. The connection job list management unit 49 manages the connection job list 59a stored in the connection job list storage unit 59. Specifically, the connection job created by the connection job creation unit 45 is registered in the connection job list 59a, the job information in the connection job list 59a is updated, or the connection job is deleted from the connection job list 59a.

  The login authentication unit 43 collates the operator list 53a with the ID and password received from the maintenance terminal or the like, and determines whether or not the operator can log in. Further, the login authentication unit 43 determines whether or not login is possible based on whether or not the ID of the maintenance terminal that transmitted the ID input by the operator is included in the maintenance terminal list 55a.

  In response to a request from an operator who performs maintenance, the candidate job list transmission unit 51 extracts a list of connection jobs (candidate job list) in which the operator is a connection candidate from the connection job list 59a, and selects a maintenance terminal. To the maintenance operation terminal. The operator selects a connection job desired to be executed from the candidate job list and notifies the center terminal 5 via the maintenance terminal. The execution determining unit 47 reads the job information of the connection job notified from the operator from the connection job list 59a, and based on this job information (for example, whether there is another operator who has already executed the connection job). To determine whether to permit execution of the connection job. The permission information transmission unit 52 notifies the operator of the determination result of the execution determination unit 47 (whether or not to permit the execution of the connection job) to the maintenance operation terminal via the maintenance terminal.

  Next, the configuration of the maintenance terminal will be described with reference to FIG. FIG. 7 is a functional block diagram showing the configuration of the first maintenance terminal 9A. Since the configuration of the first maintenance terminal 9A and the second maintenance terminal 9B is the same, the configuration of the first maintenance terminal 9A will be described as a representative. As shown in FIG. 7, the first maintenance terminal 9A includes an interface 65, a control unit 61, and a database storage unit 63.

  The interface 65 can communicate with a device connected to the LAN 25 using a private IP address. The interface 65 can perform communication via the WAN 3 using a global IP address.

  The control unit 61 includes a CPU, a RAM, a ROM, and the like, and can execute various processes by a program read from the ROM or the like. As shown in FIG. 7, the control unit 61 includes a routing session establishment unit 71, a routing control unit 73, a login information transmission unit 75, and a selected job notification unit 77.

  The routing session establishment unit 71 establishes a routing session between the first maintenance terminal 9A and the first maintenance target terminal 7A or the second maintenance target terminal 7B. The routing session is a media session used for routing communication packets transferred between a device connected to the LAN 25 and a device connected to a LAN (LAN 17 or LAN 21) where the maintenance target system is installed. . The routing control unit 73 uses this routing session to perform routing control of communication packets with devices connected to other LANs.

  The login information transmission unit 75 transmits the ID and password (hereinafter referred to as login information) input by the operator, received from the first maintenance target terminal 7A or the second maintenance target terminal 7B, to the center terminal 5. The selected job notification unit 77 transmits the connection job selected from the candidate job list by the operator to the center terminal 5.

  The database storage unit 63 includes a center terminal information storage unit 81. The center terminal information storage unit 81 stores the name and ID of the center terminal 5. The first maintenance terminal 9A can access the center terminal 5 by notifying the connection job selected from the candidate job list by referring to the stored contents of the center terminal information storage unit 81, for example.

  Next, the configuration of the maintenance target terminal will be described with reference to FIG. FIG. 8 is a functional block diagram showing a configuration of the first maintenance target terminal 7A. Since the configuration of the first serviced terminal 7A and the second serviced terminal 7B is the same, the configuration of the first serviced terminal 7A will be described as a representative. As shown in FIG. 8, the first maintenance target terminal 7A includes an interface 95, a control unit 91, and a database storage unit 93.

  The interface 95 can communicate with a device connected to the LAN 17 using a private IP address. Further, the interface 95 can perform communication via the WAN 3 by using a global IP address.

  The control unit 91 includes a CPU, a RAM, a ROM, and the like, and can execute various processes by a program read from the ROM or the like. As shown in FIG. 8, the control unit 91 includes a routing session establishment unit 101 and a routing control unit 103.

  The routing session establishing unit 101 establishes a routing session between the first maintenance target terminal 7A and the first maintenance terminal 9A or the second maintenance terminal 9B. The routing control unit 103 performs routing control of communication packets with devices connected to other LANs using this routing session.

  The database storage unit 93 includes a center terminal information storage unit 105. The center terminal information storage unit 105 stores the name and ID of the center terminal 5. The first maintenance target terminal 7A can access the center terminal 5 by referring to the stored contents of the center terminal information storage unit 105, for example, to notify that maintenance work is necessary.

  Next, the flow of processing when performing remote maintenance using the relay communication system 1 of the present embodiment will be described with reference to the sequence diagrams of FIGS. In the following, the second operator Op2 has logged in to the relay communication system 1 using the center terminal 5 as a login relay server, and the third operator Op3 has logged in to the relay communication system 1 using the second maintenance target terminal 7B as a login relay server. Consider a situation (the operator list 53a is in the state shown in FIG. 3A). Also, consider a situation where only the first connection job exists as a connection job (the connection job list 59a is in the state shown in FIG. 6A).

  First, processing performed in the relay communication system 1 when a connection job is created will be described. As described above, the connection job is created every time maintenance work is required on the maintenance target system. In the following, a case where maintenance work is required for the first maintenance target system 15A will be considered. For example, when a failure occurs in the first maintenance target system 15A, the fact is notified to the first maintenance target terminal 7A. When the first maintenance target terminal 7A receives a notification that a failure has occurred (sequence number 1 in FIG. 9), it notifies the center terminal 5 to that effect and requests the creation of a connection job (sequence number 2).

  The center terminal 5 transfers this notification and request to the center terminal operation terminal 11 and notifies the second operator Op2 of the call center (sequence number 3). The second operator Op2 selects an operator that is preferably in charge of maintenance based on the content of the fault and the name of the maintenance target terminal. Here, it is assumed that the first operator Op1 is selected. As a result, the center terminal 5 (connection job creation unit 45) creates a connection job (second connection job) (sequence number 4). The center terminal 5 (connection job list management unit 49) registers the created second connection job in the connection job list 59a (sequence number 5). That is, in the connection job list 59a, “maintenance terminal ID” describes the ID of the first maintenance target terminal 7A, and “connection candidate ID” describes the ID of the first operator Op1 (FIG. 6 ( see b)).

  The connection job is created as described above. If it is necessary to cause the first operator Op1 to perform maintenance work as soon as possible, the first operator Op1 may be notified immediately after creating the connection job. The notification that the connection job has been created can be performed in various ways. For example, when the instant message service is operated on the relay communication system 1 and the first operator Op1 has logged in to the relay communication system 1, The second operator Op2 can make the notification using the instant message service. If the first operator Op1 is not logged in to the relay communication system 1, it may be notified by appropriate means such as a telephone.

  Next, when the first operator Op1 operates the first maintenance operation terminal 23A to make a login request to the relay communication system 1 using the first maintenance terminal 9A as a login relay server, processing performed in the relay communication system 1 Will be explained. In this login request, the first operator Op1 is requested to input login information (ID and password). Then, the first operator Op1 operates the first maintenance operation terminal 23A, inputs the operator ID (Op1) and password (abc) assigned to him, and confirms the input contents, so that the login information is changed to the first one. 1 is sent to the maintenance terminal 9A. Thereby, the first maintenance terminal 9A receives the login request (sequence number 11 in FIG. 10) and transmits the received login information to the center terminal 5 (sequence number 12).

  The center terminal 5 (login authentication unit 43) that has received this login information determines whether or not login is possible. Specifically, the login authentication unit 43 determines whether or not the input ID and password are registered in the operator list 53a (sequence number 13), and the first maintenance terminal 9A that transmitted the login information serves as the maintenance terminal. It is determined whether or not it is registered in the list 55a (sequence number 14).

  As shown in FIG. 3, the ID and password input above are registered in the operator list 53a. Further, as shown in FIG. 4, the first maintenance terminal 9A is registered in the maintenance terminal list 55a. Therefore, the login authentication unit 43 of the center terminal 5 permits the login of the first operator Op1. Then, the center terminal 5 updates the contents of the operator list 53a (sequence number 15). Specifically, the ID of the first operator Op1 and the ID of the first maintenance terminal 9A are described in the “login relay server” corresponding to the first operator Op1 in the operator list 53a (from FIG. 3A). The operator list 53a is updated as shown in FIG. 3B). Then, the center terminal 5 notifies the first maintenance terminal 9A of successful login (sequence number 16). When the center terminal 5 fails to authenticate the terminal ID or the login information, the center terminal 5 notifies the maintenance terminal of the login failure.

  The first maintenance terminal 9A transfers the login success notification received from the center terminal 5 to the first maintenance operation terminal 23A and notifies the first operator Op1 of the login success (sequence number 17). The first maintenance terminal 9A requests the center terminal 5 for the candidate job list (a list of connection jobs for which the logged-in operator is a connection candidate) (sequence number 18).

  Upon receiving this notification, the center terminal 5 (candidate job list transmission unit 51) extracts a connection job in which the first operator Op1 is a connection candidate from the connection jobs stored in the connection job list 59a, and obtains a candidate job. A list is created (sequence number 19). As shown in FIG. 6B, since both the first connection job and the second connection job described in the connection job list 59a have the first operator Op1 as a connection candidate, One connection job and second connection job are described. Then, candidate job list transmission unit 51 transmits the created candidate job list to first maintenance terminal 9A (sequence number 20). When there is no connection job for which the first operator Op1 is a connection candidate, the center terminal 5 transmits a message to that effect to the first maintenance terminal 9A.

  The first maintenance terminal 9A transfers the candidate job list received from the center terminal 5 to the first maintenance operation terminal 23A and notifies the first operator Op1 (sequence number 21). Specifically, the first maintenance operation terminal 23A displays the candidate job list on its own display. Accordingly, the first operator Op1 can know a list of connection jobs that can be executed by the first operator Op1.

  The first operator Op1 can also log in to the relay communication system 1 from the first maintenance terminal 9A by operating the second maintenance operation terminal 23B. Furthermore, it is possible to log in to the relay communication system 1 from the second maintenance terminal 9B by operating the third maintenance operation terminal 27A or the fourth maintenance operation terminal 27B.

  Next, processing performed in the relay communication system 1 from selection of a connection job by the operator to maintenance work will be described. In the following, it is assumed that the first operator Op1 selects the second connection job from the candidate job list.

  When the first operator Op1 selects the second connection job and confirms the selection, information indicating the selected connection job is transmitted to the first maintenance terminal 9A. Thereby, the first maintenance terminal 9A accepts the selection of the connection job (sequence number 31 in FIG. 11), and notifies the center terminal 5 of the selection content of the first operator Op1 together with the ID of the first operator Op1 (sequence number). 32).

  Based on this notification, the center terminal 5 (execution determination unit 47) reads job information of the second connection job that is the corresponding connection job from the connection job list 59a (sequence number 33). Then, the execution determination unit 47 is executing the second connection job (for example, by another operator) based on the read job information in order to prevent a plurality of operators from executing the same connection job at the same time. It is determined whether execution preparation is in progress (sequence number 34). As shown in FIG. 6B, since the job information of the second connection job is blank, the connection job is neither being executed nor being prepared for execution. Accordingly, the execution determination unit 47 permits the first connection Op 1 to execute the second connection job. Thereafter, the connection job list management unit 49 describes “preparing for execution” in the job information of the second connection job in the connection job list 59a (sequence number 35). Thereby, the second operator Op2 of the call center can know that the connection work for the second connection job has started. Then, the center terminal 5 (permission information transmission unit 52) notifies the first maintenance terminal 9A that the execution of the corresponding connection job is permitted (sequence number 36). If the center terminal 5 does not permit execution of the connection job, the center terminal 5 notifies the maintenance terminal to that effect.

  The first maintenance terminal 9A transfers a notification that the execution of the connection job is permitted to the first maintenance operation terminal 23A and notifies the first operator Op1 (sequence number 37). Then, the first maintenance terminal 9A (routing session establishment unit 71) makes a routing session establishment request to the first maintenance target terminal 7A that is the maintenance destination of the corresponding connection job (sequence number 38). In response to this request, first maintenance target terminal 7A (routing session establishing unit 101) returns an OK response as access permission (sequence number 39). As a result, a media session is established between the first maintenance terminal 9A and the first maintenance target terminal 7A. After the media session is established, the first maintenance terminal 9A and the first maintenance target terminal 7A exchange the network addresses of the LAN 17 and the LAN 25 that are routing targets. This enables communication between the first maintenance operation terminal 23A and the first maintenance target system 15A or the second maintenance target system 15B via the routing session. Then, the first maintenance terminal 9A transmits to the first maintenance operation terminal 23A that the routing session has been established and notifies the first operator Op1 (sequence number 40). Furthermore, the first maintenance terminal 9A notifies the center terminal 5 that a routing session has been established (sequence number 41).

  Upon receiving this notification, the center terminal 5 (connection job list management unit 49) writes “Op1 in progress” in the job information of the second connection job in the connection job list 59a, as shown in FIG. 6C. (Sequence number 42). Thereby, the second operator Op2 of the call center can know that the maintenance work related to the second connection job has been started by the first operator Op1.

  The first maintenance terminal 9A performs maintenance work on the system (first maintenance target system 15A) requiring maintenance via the routing session established with the first maintenance target terminal 7A (sequence number 43). ). Specifically, the first operator Op1 can perform maintenance work such as grasping the status of the first maintenance target system 15A and updating software by operating the first maintenance operation terminal 23A.

  Next, processing performed in the relay communication system 1 when the maintenance work by the first operator Op1 is completed will be described.

  After the maintenance work is completed, the first operator Op1 notifies the completion of the maintenance work to the first maintenance target terminal 7A via the first maintenance terminal 9A (sequence number 51 in FIG. 12). In addition, the first operator Op1 notifies the center terminal 5 of the completion of the maintenance work via the first maintenance terminal 9A, and the log information indicating the date and time when the maintenance work was performed, the content, the person in charge, etc. Is transmitted (sequence number 52). In this log information, the ID of the first operator Op1 is recorded as the person in charge.

  Upon receiving this notification, the center terminal 5 (connection job list management unit 49) registers the completion of the maintenance work in the job information of the second connection job (sequence number 53), and sends the second connection job from the connection job list 59a. Delete (sequence number 54).

  Thereafter, the first maintenance terminal 9A requests the candidate job list to the center terminal 5 again, and a new maintenance operation by the first operator Op1 is performed through the same processing.

  The basic maintenance work has been described above. As described above, each operator registered in the operator list 53a uses an ID (operator ID, for example, “Op1”) and a password assigned to the operator. By inputting, it is possible to log in to the relay communication system 1 and perform remote maintenance (sequence number 11 in FIG. 10 and the like). On the other hand, in the relay communication system 1 of the present embodiment, the operator can log in using a special ID (separately set ID) called a guest ID that is set separately from the operator ID. .

  Hereinafter, this configuration will be described. As shown in FIG. 2, the database storage unit 33 of the center terminal 5 includes a guest list storage unit 54. In the guest list storage unit 54, for example, a guest list 54a shown in FIG. 13 is stored.

  In the guest list 54a, among the operators Op1 to Op4 registered in the operator list 53a, the ID of a special operator that is predetermined and that can be logged in using the guest ID is described in the column “ID”. Yes. From the example of FIG. 13, it can be seen that the third operator Op3 and the fourth operator Op4 can log in using the guest ID.

  In addition, in order to enable login using a guest ID, a record is added to the guest ID in the operator list 53a of the center terminal 5 as shown in the lowermost line of FIG. In the example of FIG. 14A, the character string “Guest” representing the guest ID is registered in the “ID” column of the operator list, and the operator ID assigned to the third operator Op3 is registered in the “password” column. ("Op3") and a password concatenated with "@" (that is, Op3 @ ghi) are described. This effectively means that only those who can input the operator ID and password of the third operator Op3 (that is, only the third operator Op3) can log in using the guest ID. In this way, in the operator list 53a, the guest ID and the specific operator (third operator Op3) are described in association with each other.

  FIG. 15A shows an example of a connection job list to which a connection job corresponding to the guest ID is added. From this example, it can be seen that, in addition to the first connection job similar to the above, a third connection job is created for the first maintenance target terminal 7A, and the guest ID is set as an operator of the connection candidate.

  Next, processing of the relay communication system 1 when the guest ID is used will be described with reference to FIGS. 16 to 19. Note that the sequence diagrams of FIGS. 16 to 19 substantially correspond to FIGS. 9 to 12 referred to in the previous description.

  Similarly to the above-described example, it is assumed that a failure has occurred in the first maintenance target system 15A, and that fact has been notified to the first maintenance target terminal 7A (sequence number 61 in FIG. 16). In response to this notification, the first maintenance target terminal 7A notifies the center terminal 5 to that effect and requests creation of a connection job (sequence number 62).

  The second operator Op2 operating the center terminal operation terminal 11 in the call center is notified that a connection job needs to be created (sequence number 63), and appropriately selects an operator that is preferably to perform maintenance. Although various situations are considered in this selection, in this example, the first operator Op1 is in charge of maintenance of the first maintenance target terminal 7A, although it is determined in advance that the rule is concerned. It is assumed that the operation is impossible for some reason such as the absence of the first operator Op1. Therefore, the second operator Op2 wishes to have someone perform remote maintenance with temporary support, and operates the center terminal operation terminal 11 to display a list of operators that can log in using the guest ID. To instruct.

  Upon receiving this instruction, the center terminal operation terminal 11 inquires of the center terminal 5 about an operator who can use the guest ID. In response to this inquiry, the center terminal 5 transmits the contents of the guest list 54a shown in FIG. 13 to the center terminal operation terminal 11, and the center terminal operation terminal 11 displays the result of the inquiry on the display. Thus, the second operator Op2 can know that the operators that can use the guest ID are the third operator Op3 and the fourth operator Op4.

  In this example, the second operator Op2 selects the third operator Op3 by operating the center terminal operation terminal 11 and wishing the third operator Op3 to perform the remote maintenance this time as a result of the examination. And In this selection, an instruction using a guest ID is also performed.

  As a result, the center terminal 5 registers the guest ID in the operator list 53a (sequence number 64). Specifically, as shown in FIG. 14A, the “ID” of the operator list 53a describes “Guest” representing the guest ID, and the “password” includes the ID and password of the third operator Op3. A character string concatenated with “@” is registered.

  Next, the second operator Op2 operates the center terminal operation terminal 11 to instruct the center terminal 5 to create a connection job. This instruction includes designation of the first maintenance target terminal 7A as the maintenance target terminal and the previously created guest ID as the connection candidate. In response to the instruction, the center terminal 5 (connection job creation unit 45) creates a connection job (sequence number 65) and registers it in the connection job list 59a (sequence number 66). Specifically, as shown by the third connection job in FIG. 15A, the ID of the first serviced terminal 7A is described in the “maintenance terminal ID” of the connection job list 59a and the “connection candidate ID”. Describes the guest ID.

  After creating the connection job as described above, the second operator Op2 contacts the third operator Op3 by telephone or the like, and informs that he / she wants to log in with the guest ID for support. In response to this, the third operator Op3 operates an appropriate maintenance operation terminal (for example, the third maintenance operation terminal 27A) and logs in with the guest ID.

  Similarly to the above, when logging in, input of login information (ID and password) is required. The login with the guest ID this time is different from the normal login, enter “Guest” as the ID, and enter the character string that concatenates the operator ID and password assigned to you with “@” as the password. By doing. In this example, the third operator Op3 logs in with the ID “Guest” and the password “Op3 @ ghi”. Thereby, a login request to the relay communication system 1 is performed using the second maintenance terminal 9B to which the third maintenance operation terminal 27A is connected as a login relay server.

  When receiving the login information from the third maintenance operation terminal 27A, the second maintenance terminal 9B accepts a login request (sequence number 71 in FIG. 17) and transmits the received login information to the center terminal 5 (sequence number 72).

  The center terminal 5 (login authentication unit 43) that has received this login information determines whether or not login is possible. Specifically, the login authentication unit 43 determines whether or not the input ID and password are registered in the operator list 53a (sequence number 73), and the second maintenance terminal 9B that transmitted the login information serves as the maintenance terminal. It is determined whether or not it is registered in the list 55a (sequence number 74).

  As shown in FIG. 14A, the guest ID and password input above are registered in the operator list 53a. Further, as shown in FIG. 4, the second maintenance terminal 9B is registered in the maintenance terminal list 55a. Accordingly, the login authentication unit 43 of the center terminal 5 permits login with the guest ID. However, in determining whether or not login is possible, the operator ID (Op3) is extracted from the password (Op3 @ ghi) input by the operator and then whether or not the operator ID is included in the guest list 54a. It may be included.

  When login with the guest ID is permitted, the center terminal 5 updates the contents of the operator list 53a (sequence number 75). Specifically, the guest ID and the ID of the second maintenance terminal 9B are described in the “login relay server” corresponding to the guest ID in the operator list 53a (from FIG. 14A to FIG. 14B). So that the operator list 53a is updated). Then, the center terminal 5 notifies the second maintenance terminal 9B of successful login (sequence number 76).

  The second maintenance terminal 9B transfers the login success notification received from the center terminal 5 to the third maintenance operation terminal 27A and notifies the operator of the login success (sequence number 77). Then, the second maintenance terminal 9B requests the center terminal 5 for the candidate job list (list of connection jobs whose guest IDs are connection candidates) (sequence number 78).

  Upon receiving this notification, the center terminal 5 (candidate job list transmission unit 51) extracts the connection job whose guest ID is the connection candidate from the connection jobs stored in the connection job list 59a, and displays the candidate job list. Create (sequence number 79). As shown in FIG. 15A, among the first connection job and the third connection job described in the connection job list 59a, the guest ID is a connection candidate because the guest ID is a connection candidate. The third connection job is described in the candidate job list.

  Although the third operator Op3 is actually logged in with the guest ID, only those whose guest ID is a connection candidate are extracted and described in the candidate job list. Accordingly, the first connection job is not included in the candidate job list because the guest ID is not a connection candidate although the third operator Op3 is a connection candidate. The created candidate job list is transmitted to the second maintenance terminal 9B by the candidate job list transmission unit 51 (sequence number 80).

  The second maintenance terminal 9B transfers the candidate job list received from the center terminal 5 to the third maintenance operation terminal 27A and notifies the third operator Op3 logged in with the guest ID (sequence number 81). Specifically, the third maintenance operation terminal 27A displays the candidate job list on the display provided in itself. As a result, the third operator Op3 can know a list of connection jobs that can be executed when the third operator Op3 uses the guest ID.

  As a result of examining the list of connection jobs displayed on the third maintenance operation terminal 27A, the third operator Op3 logged in with the guest ID knows that only the third connection job can be performed with the guest ID. . Therefore, the third operator Op3 selects the third connection job, and information indicating the connection job is transmitted to the second maintenance terminal 9B. The second maintenance terminal 9B receives the selection of the connection job (sequence number 91 in FIG. 18), and notifies the selection content of the third operator Op3 to the center terminal 5 together with the guest ID (sequence number 92).

  Based on this notification, the center terminal 5 (execution determination unit 47) reads job information of the third connection job that is the corresponding connection job from the connection job list 59a (sequence number 93). Then, the execution determination unit 47 is executing a third connection job (for example, by another operator) based on the read job information in order to prevent a plurality of operators from executing the same connection job at the same time. It is determined whether execution preparation is in progress (sequence number 94). As shown in FIG. 15A, since the job information of the third connection job is blank, the connection job is neither being executed nor being prepared for execution. Therefore, the execution determination unit 47 permits execution of the third connection job using the guest ID. Thereafter, the connection job list management unit 49 describes “preparing for execution” in the job information of the third connection job in the connection job list 59a (sequence number 95). Thereby, the second operator Op2 of the call center can know that the connection work for the third connection job has started. Then, the center terminal 5 (permission information transmission unit 52) notifies the second maintenance terminal 9B that execution of the corresponding connection job is permitted (sequence number 96).

  The second maintenance terminal 9B transfers a notification that the execution of the connection job is permitted to the third maintenance operation terminal 27A and notifies the third operator Op3 (sequence number 97). Then, the second maintenance terminal 9B (routing session establishment unit 71) issues a routing session establishment request to the first maintenance target terminal 7A, which is the maintenance destination of the corresponding connection job (sequence number 98). In response to this request, first maintained terminal 7A (routing session establishing unit 101) returns an OK response as access permission (sequence number 99). As a result, a media session is established between the second maintenance terminal 9B and the first maintenance target terminal 7A. This enables communication between the third maintenance operation terminal 27A and the first maintenance target system 15A or the second maintenance target system 15B via the routing session.

  The second maintenance terminal 9B transmits to the third maintenance operation terminal 27A that the routing session has been established and notifies the third operator Op3 (sequence number 100). Furthermore, the second maintenance terminal 9B notifies the center terminal 5 that a routing session has been established (sequence number 101).

  Upon receiving this notification, the center terminal 5 (connection job list management unit 49) writes “Guest in progress” in the job information of the third connection job in the connection job list 59a as shown in FIG. 15C. (Sequence number 102). Thereby, the second operator Op2 of the call center can know that the maintenance work related to the third connection job is started by the guest ID (third operator Op3). Thereafter, the second maintenance terminal 9B performs maintenance work on the first maintenance target system 15A that is the target of the connection job via the routing session (sequence number 103).

  After the maintenance work is completed, the third operator Op3 notifies the completion of the maintenance work to the first maintenance target terminal 7A via the second maintenance terminal 9B (sequence number 111 in FIG. 19). Further, the third operator Op3 notifies the center terminal 5 of the completion of the maintenance work via the second maintenance terminal 9B, and transmits the log information indicating the person in charge who performed the maintenance work, the date and time, contents, and the like. (Sequence number 112). Since the third operator Op3 logs in using the guest ID, the guest ID is described in the person in charge in the log information.

  Upon receiving this notification, the center terminal 5 (connection job list management unit 49) registers the completion of the maintenance work in the job information of the third connection job (sequence number 113), and sends the third connection job from the connection job list 59a. Delete (sequence number 114).

  In the above example, the second operator Op2 creates a guest ID used by the third operator Op3 and creates a connection job for the guest ID (sequence numbers 64 and 65). By simply creating a connection job for the ID (Op3) of the third operator Op3, it is possible to realize a situation where the remote maintenance work of the third operator Op3 is possible. However, for example, when a special situation occurs, such as when an outside operator works as described above, the operator performs login and remote maintenance using the guest ID, and works with the guest ID. By recording the fact in the log information, there is an advantage that it can be clearly distinguished from the normal work and is useful for later management.

  As described above, in the present embodiment, the center terminal 5 includes the operator list storage unit 53, the login authentication unit 43, the connection job creation unit 45, the candidate job list transmission unit 51, the execution determination unit 47, Is provided. The operator list storage unit 53 stores an operator list 53a that is a list of operators that can log in to the relay communication system 1 configured to include itself (center terminal 5) and other relay servers. The login authentication unit 43 determines whether or not the operator can log in based on at least the ID input by the operator and the contents of the operator list storage unit 53. The connection job creation unit 45 associates a maintenance target terminal (for example, the first maintenance target terminal 7A) with the ID that is a candidate for connection that can be permitted to be connected to the maintenance target terminal. Create a job. In response to a request from the maintenance terminal (for example, the second maintenance terminal 9B), the candidate job list transmission unit 51 is a connection job in which the ID input by the logged-in operator through the maintenance terminal is set as a connection candidate. A candidate job list that is a list of the above is transmitted to the maintenance terminal. When the operator selects a connection job from the candidate job list, the execution determination unit 47 responds to an inquiry from the maintenance terminal (second maintenance terminal 9B) and the maintenance terminal and the maintenance target terminal (for example, the first target terminal). A routing session is established with the maintenance terminal 7A) to determine whether or not the connection job can be executed. The IDs that can be logged into the relay communication system 1 by the operator input include operator IDs (Op1 to Op4) that are uniquely assigned to the operators, and guest IDs (Guest) that are set separately from the operator IDs. And are included. The connection job creation unit 45 is configured to create a connection job in which the maintenance target terminal and the guest ID are associated with each other as in the third connection job of FIG.

  Thereby, when the operator logs in to the relay communication system 1 from the maintenance terminal using the operator ID or guest ID, a list of connection jobs in which the ID is a connection candidate is displayed, and by selecting a connection job from this, A maintenance session can be performed by establishing a routing session by connecting to a corresponding maintenance target terminal. Therefore, the operator can smoothly perform from the login to the actual maintenance work without departing from the access authority permitted to the operator. In addition, it is possible to provide the operator with various log-in operations as necessary while permitting the maintenance operation only to a predetermined operator according to the object of the maintenance operation and ensuring sufficient security.

  In addition, the center terminal 5 of the present embodiment includes a guest list storage unit 54 that stores a list of operators (guest list 54a) that can log in to the relay communication system 1 using a guest ID.

  Thereby, since the operator who can use guest ID can be managed by the guest list storage part 54, strong security is realizable.

  In the center terminal 5 of the present embodiment, the operator list storage unit 53 is configured to store an operator list 53a as shown in FIG. 14 in which guest IDs and operators that can use guest IDs are associated with each other. Yes.

  Thereby, access authority can be managed reliably by linking a guest ID clearly to a specific operator.

  In this embodiment, the connection-side relay server (first maintenance terminal 9A and second maintenance terminal 9B) includes a center terminal information storage unit 81, a selected job notification unit 77, a routing session establishment unit 71, a routing And a control unit 73. The center terminal information storage unit 81 includes an ID requested by an operator to log in to the relay communication system 1 configured to include itself and other relay servers, and connection candidates that can be permitted to be connected. The identification information of the center terminal 5 which is the storage destination of the connection job in which the ID is set and the connected relay server (first maintenance target terminal 7A, etc.) is stored. The selected job notification unit 77 receives from the center terminal 5 a candidate job list that is a list of connection jobs in which the ID input by the logged-in operator through the user is set as a connection candidate, and then selects the candidate job list. The center terminal 5 is notified of the connection job selected from among them. When the routing session establishment unit 71 receives the notification that the execution of the selected connection job is permitted, the routing session establishment unit 71 establishes a routing session used for packet routing with the connected relay server indicated by the connection job. To do. The routing control unit 73 performs routing control based on the routing session. The IDs that can be logged into the relay communication system 1 by the operator input include operator IDs (Op1 to Op4) that are uniquely assigned to the operators, and guest IDs (Guest) that are set separately from the operator IDs. And are included.

  Thus, when the operator logs in to the relay communication system 1 from the connection-side relay server using the operator ID or guest ID, a list of connection jobs for which the ID is a connection candidate is displayed, and a connection job is selected from this list. Thus, it is possible to establish a routing session by connecting to the corresponding relay server on the connected side and perform maintenance work. Therefore, the operator can smoothly perform from the login to the actual maintenance work without departing from the access authority permitted to the operator. In addition, it is possible to provide the operator with various log-in operations as necessary while permitting the maintenance operation only to a predetermined operator according to the object of the maintenance operation and ensuring sufficient security.

  Next, a modified example for notifying the target operator that the guest ID has been set will be described.

  In other words, in the above embodiment, the second operator Op2 registers the guest ID for the third operator Op3 (sequence number 64 in FIG. 16), and creates a connection job for the guest ID (sequence numbers 65 and 66). ), The second operator Op2 notifies the third operator Op3 by telephone or the like so as to prompt the third operator Op3 to log in using the guest ID. However, after the guest ID is registered for the third operator Op3, the guest ID is set when the operator logs in to the relay communication system 1 with the operator ID of the third operator Op3 (“Op3”) instead of the guest ID. It is also possible to notify the third operator Op3 by displaying, for example, on the display of the third maintenance operation terminal 27A.

  The third operator Op3, who has noticed that the guest ID is set, determines whether to continue the login with the operator ID as it is or to switch to the login with the guest ID. When the third operator Op3 determines that the work should be performed with the guest ID, the logout operation is performed to cancel the login with the operator ID, and the login with the guest ID is performed again to request a candidate job list. As described above, the contact work from the second operator Op2 to the third operator Op3 can be omitted, and a smooth operation can be realized.

  As described above, in the center terminal 5 of the above-described modified example, the third operator Op3 (which is an operator for which a corresponding guest ID is set) uses the operator ID (“Op3”) to perform the relay communication system 1. , The third operator Op3 can be notified that the guest ID has been set.

  As a result, the operation of contacting the third operator Op3 to the effect that the guest ID has been set can be omitted, and smooth operation is possible.

  The preferred embodiment of the present invention has been described above, but the above configuration can be modified as follows, for example.

  In the above description, the operator ID is a character string such as “Op1” in order to facilitate understanding. However, the operator ID is not limited to this, and it goes without saying that an arbitrary character string can be set as the operator ID. The password for the operator ID is not limited to “abc” or the like and can be arbitrarily determined. For the guest ID, various character strings such as a character string other than “Guest”, for example, “Temp” can be set.

  In the above embodiment, by including the operator ID of the corresponding operator (that is, “Op3” which is the operator ID of the third operator Op3) in the password portion of the guest ID in the operator list 53a of FIG. The guest ID is associated with a specific operator. However, the association method is arbitrary. For example, a new “corresponding operator” column may be created in the operator list 53a, and the operator ID of the third operator Op3 may be described therein. The password for the guest ID may be determined in a format other than connecting the corresponding operator ID and the password with “@”.

  Further, in the operator list 53a of FIG. 14, it is not essential to associate the guest ID with the operator. For example, the guest ID and the password are determined in advance, and the guest ID and password are notified only to the operators Op3 and Op4 listed in the guest list 54a in FIG. Maintenance work by ID can be permitted.

  Registration of the guest ID indicated by the sequence number 64 in FIG. 16 may be performed in advance before the occurrence of the failure, instead of being performed each time in response to the notification of the occurrence of the failure.

  In the above embodiment, the operator registered in association with the guest ID in the operator list 53a in FIG. 14 is selected from the operators described in the guest list 54a in FIG. However, when no operator is registered in the guest list 54a in FIG. 13, all the operators (Op1 to Op4) registered in the operator list 53a can be registered in association with the guest IDs. good.

  The number of maintenance target terminals and maintenance terminals constituting the relay communication system 1 is not limited to the above embodiment, and may be one each, or may be three or more. In addition, the number of maintenance target systems connected to the maintenance target terminal and the number of maintenance operation terminals connected to the maintenance terminal are not limited to the above embodiment, and may be one each, or three or more. There may be.

  The first maintenance terminal 9A and the second maintenance terminal 9B may be a memory detachably attached to a personal computer and an application stored in the memory.

  The operator list 53a, maintenance terminal list 55a, maintenance target terminal list 57a, and connection job list 59a can be stored in an appropriate format (for example, XML format).

  Instead of the configuration of the above-described embodiment, an external server used for communication between each relay server may be installed on the Internet, and a communication may be performed by exhibiting a function as a SIP (Session Initiation Protocol) server. .

1 Relay communication system 5 Center terminal (relay server with management function)
7A First maintenance target terminal (relay server on the connected side)
7B Second maintenance target terminal (relay server on the connected side)
9A 1st maintenance terminal (relay server on the connection side)
9B Second maintenance terminal (relay server on the connection side)
11 Center terminal operation terminal 15A 1st maintenance target system 15B 2nd maintenance target system 19A 3rd maintenance target system 19B 4th maintenance target system 23A 1st maintenance operation terminal 23B 2nd maintenance operation terminal 27A 3rd maintenance operation Terminal 27B Fourth maintenance operation terminal 43 Login authentication unit 45 Connection job creation unit 47 Execution determination unit 51 Candidate job list transmission unit 53 Operator list storage unit 54 Guest list storage unit (special operator list storage unit)
77 Selected job notification section 81 Center terminal information storage section (management destination information storage section)
71 Routing session establishment unit 73 Routing control unit

Claims (6)

An operator list storage unit for storing a list of operators that can log in to a relay communication system including the relay server itself and other relay servers;
A login authentication unit that determines whether or not an operator can log in based on at least the ID input by the operator and the contents of the operator list storage unit;
A connection job creation unit that creates a connection job that associates a connected relay server with the ID that is a candidate for connection that can be permitted to be connected to the connected relay server;
In response to a request from the connection-side relay server, a candidate job list that is a list of the connection jobs in which the ID input by the logged-in operator through the connection-side relay server is set as a connection candidate is A candidate job list transmission unit to be transmitted to the relay server on the connection side;
When the operator selects a connection job from the candidate job list, a routing session is established between the connection-side relay server and the connected-side relay server in response to an inquiry from the connection-side relay server. An execution determination unit that determines whether to establish and execute the connection job;
With
The ID that allows the operator to log in to the relay communication system includes an operator ID that is uniquely assigned to each operator and another setting ID that is set separately from the operator ID. ,
The relay server with a management function, wherein the connection job creation unit is configured to be able to create a connection job in which the relay server on the connected side is associated with the different setting ID. A relay server with a management function according to claim 1,
A relay server with a management function, comprising: a special operator list storage unit that stores a list of operators that can log in to the relay communication system using the different setting ID among the operators. A relay server with a management function according to claim 1 or 2,
The relay list with management function, wherein the operator list storage unit is configured to be able to store the separate setting ID and an operator who can use the separate setting ID in association with each other. A relay server with a management function according to any one of claims 1 to 3,
When an operator set with the different setting ID logs in to the relay communication system using the operator ID, the operator is notified that the different setting ID is set. A relay server with management functions. The ID to which the operator is requested to log in to log in to the relay communication system including itself and other relay servers, and the connected side in which the ID is set as a connection candidate that can be permitted to connect A management destination information storage unit for storing identification information of a relay server with a management function that is a storage destination of a connection job in which
Select from the candidate job list after receiving from the relay server with management function a candidate job list that is a list of the connection jobs in which the ID entered by the logged-in operator is set as a connection candidate A selected job notification unit that notifies the relay server with management function of the connection job that has been made;
A routing session establishment unit that establishes a routing session used for packet routing with a relay server on the connected side indicated by the connection job when receiving the notification that the execution of the selected connection job is permitted; ,
A routing control unit that performs routing control based on the routing session;
With
The ID that allows the operator to log in to the relay communication system includes an operator ID that is uniquely assigned to each operator and another setting ID that is set separately from the operator ID. A relay server on the connection side characterized by the above. A relay server with management functions;
A relay server on the connection side capable of communicating with the relay server with management function;
A connected relay server capable of communicating with the management function relay server;
A relay communication system comprising:
The relay server with management function is:
An operator list storage unit for storing a list of operators that can log in to the relay communication system;
A login authentication unit that determines whether or not an operator can log in based on at least the ID input by the operator and the contents of the operator list storage unit;
A connection job creation unit that creates a connection job that associates a connected relay server with the ID that is a candidate for connection that can be permitted to be connected to the connected relay server;
In response to a request from the connection-side relay server, a candidate job list that is a list of the connection jobs in which the ID input by the logged-in operator through the connection-side relay server is set as a connection candidate is A candidate job list transmission unit to be transmitted to the relay server on the connection side;
When the operator selects a connection job from the candidate job list, a routing session is established between the connection-side relay server and the connected-side relay server in response to an inquiry from the connection-side relay server. An execution determination unit that determines whether to establish and execute the connection job;
With
The ID that allows the operator to log in to the relay communication system includes an operator ID that is uniquely assigned to each operator and another setting ID that is set separately from the operator ID. ,
The connection job creation unit is configured to be able to create a connection job in which the relay server on the connected side is associated with the different setting ID,
The connection side relay server is:
A management information storage unit that stores identification information of the relay server with the management function;
Select from the candidate job list after receiving from the relay server with management function a candidate job list that is a list of the connection jobs in which the ID entered by the logged-in operator is set as a connection candidate A selected job notification unit that notifies the relay server with management function of the connection job that has been made;
A routing session establishment unit that establishes a routing session used for packet routing with a relay server on the connected side indicated by the connection job when receiving the notification that the execution of the selected connection job is permitted; ,
A routing control unit that performs routing control based on the routing session;
A relay communication system comprising:

Images