JP2013084190A - Connection control system and connection control method - Google Patents

Connection control system and connection control method Download PDF

Info

Publication number
JP2013084190A
JP2013084190A JP2011224807A JP2011224807A JP2013084190A JP 2013084190 A JP2013084190 A JP 2013084190A JP 2011224807 A JP2011224807 A JP 2011224807A JP 2011224807 A JP2011224807 A JP 2011224807A JP 2013084190 A JP2013084190 A JP 2013084190A
Authority
JP
Japan
Prior art keywords
connection
terminal
virtual terminal
virtual
peripheral device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2011224807A
Other languages
Japanese (ja)
Other versions
JP5705699B2 (en
Inventor
Hiroyuki Kurita
弘之 栗田
Original Assignee
Nippon Telegr & Teleph Corp <Ntt>
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nippon Telegr & Teleph Corp <Ntt>, 日本電信電話株式会社 filed Critical Nippon Telegr & Teleph Corp <Ntt>
Priority to JP2011224807A priority Critical patent/JP5705699B2/en
Publication of JP2013084190A publication Critical patent/JP2013084190A/en
Application granted granted Critical
Publication of JP5705699B2 publication Critical patent/JP5705699B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Abstract

PROBLEM TO BE SOLVED: To support peripheral equipment which is being used under a virtual environment from a remote place without performing the setting change of a thin client or new function addition to the thin client.SOLUTION: When receiving the connection permission state confirmation request of a business person PC91 who is permitted to connect to a virtual terminal 61 from the virtual terminal 61, a connection management server 70 derives a determination result indicating that the business person PC91 is put in a connection permission state, and transmits the determination result to the virtual terminal 61 under conditions that the IP address of the business person PC91 included in the connection permission state confirmation request and an IP address stored in a virtual terminal connection state management table are made coincident. When receiving the determination result indicating that the business person PC91 is put in the connection permission state from the connection management server 70, the virtual terminal 61 establishes a virtual terminal connection session with the business person PC91.

Description

  The present invention relates to a connection control system and a connection control method.

  In recent years, for the purpose of reducing terminal management costs and unifying service usage environments, a virtual terminal for each user has been constructed on a server installed in a data center, and Web services and various applications are used on the virtual terminal. Thin client systems are attracting attention again. In this thin client system, a GUI (Graphical User Interface) of a virtual terminal (client OS) operating on a server is operated over a network using a thin client terminal at hand.

  For example, when a peripheral device such as a printer, a digital camera, or an external hard disk is physically connected to a thin client terminal through an interface such as a USB (Universal Serial Bus), the thin client terminal and the server are connected to the thin client terminal. It is recognized on the virtual terminal as if it is directly connected to the virtual terminal via a communication session established with the virtual terminal operating above. Therefore, when a peripheral device is used in a virtual environment such as a thin client system, it may be possible to remotely receive support from the operator or other users regarding the operation method or malfunction of the peripheral device. It is done.

  In this connection, a conventional technique (for example, “USB over IP”) that encapsulates the USB protocol with an IP packet for the purpose of making a remote personal computer recognize a USB device connected to the personal computer via a network. There is a conventional technique for superimposing and converting any computer interface such as USB and analog RGB on an optical network (see Patent Document 1).

Japanese Patent No. 3778031

  By the way, when receiving remote support for peripheral device operation methods and malfunctions, the user receiving the support temporarily logs in to his / her virtual terminal to the support provider and other users. It may be possible to grant permission and receive support on the virtual terminal. However, in a virtual environment such as the above-described thin client system, it is generally difficult for a business operator or the like to change the setting of a virtual terminal that operates on a server, and software used for analysis is virtual terminal. Also difficult to install. As described above, there is a limit to the support provided on the virtual terminal, and it is desirable to directly recognize the peripheral device of the user receiving the support with the personal computer of the support provider.

  In addition, when the peripheral device of the user receiving the support is directly recognized by the personal computer of the business operator performing the support, the user receiving the support changes the setting of the thin client terminal by itself, and the peripheral device It is necessary to change the virtual connection destination from the virtual terminal on the server to the personal computer used by the business operator. For this purpose, the thin client terminal is connected to the peripheral independently of the connection destination of the virtual terminal connection. There is a problem that a function for enabling setting of the connection destination of the device is required, and the cost for expanding the function of the thin client terminal increases.

  Further, the above-described conventional technology assumes that a thin client terminal to which a peripheral device is physically connected and a virtual terminal on a server that recognizes the peripheral device are directly connected. For this reason, for example, for remote support, temporarily changing the connection destination of a thin client terminal to which a peripheral device is physically connected to a virtual terminal on the support side arranged on the server, etc. It is not taken into consideration, and it does not solve the problems such as that there is a limit to the support performed on the virtual terminal and the cost for realizing the support performed on the virtual terminal increases.

  The present invention has been made in view of the above, and remotely supports peripheral devices used in a virtual environment without changing settings of the thin client or adding new functions to the thin client. An object of the present invention is to provide a connection control system and a connection control method that enable the connection.

  In order to solve the above-described problems and achieve the object, the present invention executes a thin client terminal to which a peripheral device is connected, a virtual terminal connected to the thin client terminal, and remote support for the peripheral device. A connection control system having an operator terminal operated by the operator, wherein the connection control system is permitted to connect to the virtual terminal to which the thin client terminal is connected via a virtual terminal connection session. A virtual terminal connection state management table for storing identification information unique to the provider terminal, and a confirmation request when receiving a confirmation request from the virtual terminal for a provider terminal permitted to connect to the virtual terminal. That the identification information unique to the provider terminal included in the information matches the identification information stored in the virtual terminal connection state management table. As a matter, a connection management server having a confirmation response unit that derives a determination result indicating that the provider terminal is in a connection-permitted state and transmits the derived determination result to the virtual terminal as a response to the confirmation request. In addition, when the virtual terminal receives, as a response to the confirmation request, the determination result that the provider terminal that is the transmission source of the connection request is in a connection-permitted state from the connection management server, It has the session establishment part which establishes the said virtual terminal connection session between the said provider terminals.

  The present invention also includes a thin client terminal to which a peripheral device is connected, a virtual terminal connected to the thin client terminal, and a business operator terminal operated by a business operator that performs remote support for the peripheral device. A connection control method executed by a connection control system, wherein the thin client terminal transmits a connection request for the peripheral device to a connection management server, and the connection management server is connected to the thin client terminal. When the peripheral device connection request is received, identification information unique to the virtual terminal connected to the thin client terminal is stored in a peripheral device connection state management table that stores information on a virtual connection destination of the peripheral device. After recording as the virtual connection destination, the peripheral device between the thin client terminal and the virtual terminal A peripheral device connection session establishment step of establishing a connection session and transmitting a response to the connection request to the thin client terminal, and the virtual terminal responding to an operation input from the thin client terminal to the virtual terminal A connection permission request transmission step of transmitting a connection permission request for requesting connection permission of the provider terminal to the connection management server; and when the connection management server receives the connection permission request from the virtual terminal, Included in the connection permission request in a virtual terminal connection state management table that stores identification information specific to the provider terminal that is permitted to connect to the virtual terminal to which a client terminal is connected via a virtual terminal connection session Response to the connection permission request after newly recording identification information unique to the carrier terminal A connection-permitted terminal recording step for transmitting to the virtual terminal, and a connection request for a confirmation of a provider terminal permitted to connect to the virtual terminal when the virtual terminal receives a connection request from the provider terminal A confirmation request transmission step to be transmitted to the management server; when the connection management server receives the confirmation request; identification information unique to the operator terminal included in the confirmation request; and the virtual terminal connection state management table A determination result that the operator terminal is in a connection-permitted state is derived on condition that the identification information stored in the virtual machine matches the identification information, and the derived determination result is used as a response to the confirmation request. A confirmation response step to be transmitted to the terminal; and as a response to the confirmation request from the virtual terminal, the operator terminal that is the transmission source of the connection request A session establishment step of establishing the virtual terminal connection session with the provider terminal when the determination result indicating that the communication terminal is in the state is received from the connection management server.

  According to the present invention, it is possible to realize remote support for peripheral devices used in a virtual environment without changing settings of the thin client or adding new functions to the thin client.

FIG. 1 is a functional block diagram illustrating the configuration of the connection control system according to the first embodiment. FIG. 2 is a diagram illustrating an example of a functional configuration of the USB device. FIG. 3 is a diagram illustrating an example of a functional configuration of the thin client. FIG. 4 is a diagram illustrating an example of a functional configuration of the virtual terminal. FIG. 5 is a diagram illustrating an example of a functional configuration of the connection management server. FIG. 6 is a diagram illustrating a configuration example of the virtual terminal connection state management table. FIG. 7 is a diagram illustrating a configuration example of the peripheral device connection state management table. FIG. 8 is a diagram illustrating an example of a functional configuration of the operator PC. FIG. 9 is a diagram illustrating a flow of processing by the connection control system according to the first embodiment. FIG. 10 is a diagram illustrating a flow of processing by the connection control system according to the first embodiment. FIG. 11 is a diagram illustrating a flow of processing by the connection control system according to the first embodiment. FIG. 12 is a diagram illustrating an example of a computer that executes a program for realizing the same function as the processing described in the embodiment.

  Embodiments of a connection control system and a connection control method according to the present application will be described below with reference to the drawings. Each example described below is merely an embodiment, and does not limit the embodiments of the connection control system and the connection control method according to the present application. In addition, the embodiments described later can be appropriately combined within a range that does not cause a contradiction in the processing contents.

[Outline and Features of Connection Control System and Connection Control Method (Example 1)]
An overview and features of the connection control system according to the first embodiment will be described. The connection control system according to the first embodiment includes a thin client terminal to which a peripheral device is connected, a virtual terminal connected to the thin client terminal, and a business operator operated by a business operator that performs remote support for the peripheral device. Terminal. The connection control system stores a virtual terminal connection state that stores identification information unique to the provider terminal that is permitted to connect to the virtual terminal to which the thin client terminal is connected via a virtual terminal connection session. A management table, identification information unique to the operator terminal included in the confirmation request when receiving a confirmation request of the operator terminal permitted to connect to the virtual terminal from the virtual terminal, and the virtual terminal On the condition that the identification information stored in the connection state management table matches, a determination result indicating that the operator terminal is in a connection permission state is derived, and the derived determination result is applied to the confirmation request. A connection management server having a confirmation response unit to be transmitted to the virtual terminal as a response. A session that establishes the virtual terminal connection session with the provider terminal when the determination result that the provider terminal that is the connection request source is in a connection-permitted state is received from the connection management server. It is characterized in that it has an establishment part.

  Specifically, when the connection management server receives a connection permission state confirmation request for a carrier terminal permitted to connect to the virtual terminal from the virtual terminal, the connection management server sends the connection management server to the carrier terminal included in the connection permission state confirmation request. The unique identification information (for example, IP address) matches the identification information (for example, IP address) that is stored in the virtual terminal connection state management table and is unique to the operator terminal that is permitted to connect to the virtual terminal. On the condition that this is done, a determination result indicating that the operator terminal is in the connection permitted state is derived and transmitted to the virtual terminal. When the virtual terminal receives a determination result indicating that the provider terminal is in the connection-permitted state from the connection management server, the virtual terminal establishes a virtual terminal connection session with the provider terminal. As a result, the business entity terminal can check the status of the peripheral device recognized on the virtual terminal via the virtual terminal connection session established with the virtual terminal.

  For this reason, in the connection control system according to the first embodiment, it is possible to remotely connect the peripheral device used in the virtual environment without changing the setting of the thin client or adding a new function to the thin client. Support can be realized.

[Configuration of Connection Control System (Example 1)]
FIG. 1 is a functional block diagram illustrating the configuration of the connection control system according to the first embodiment. As illustrated in FIG. 1, the connection control system according to the first embodiment includes a user environment 101, a virtual terminal provider environment 401, a provider A environment 801, and a provider B environment 802. The connection control system according to the first embodiment communicates each device accommodated in the user environment 101 and each device accommodated in the virtual terminal operator environment 401 with each other via the core network 200. Connect as possible. Similarly, the connection control system according to the first embodiment is accommodated in each device accommodated in the virtual terminal operator environment 401 and each device accommodated in the operator A environment 801 or the operator B environment 802. Are connected so that they can communicate with each other.

  As shown in FIG. 1, the user environment 101 accommodates USB devices 11 and 12, a thin client 20, and a router 30.

  The USB device 11 and the USB device 12 (hereinafter referred to as a USB device as appropriate) are physically connected to the thin client 20 via a USB (Universal Serial Bus) interface such as a printer, a digital camera, or an external hard disk. It is a general purpose peripheral device.

  FIG. 2 shows an example of the functional configuration of the USB device. FIG. 2 is a diagram illustrating an example of a functional configuration of the USB device. As shown in FIG. 2, the USB device has a thin client connection unit. The thin client connection unit connects the USB device and the thin client 20 through a USB (Universal Serial Bus) interface.

  The thin client 20 is a client terminal that uses a virtual terminal environment provided by a virtual terminal operator.

  FIG. 3 shows an example of the functional configuration of the thin client. FIG. 3 is a diagram illustrating an example of a functional configuration of the thin client. As shown in FIG. 3, the thin client 20 includes a virtual terminal connection unit and a peripheral device connection session establishment unit. The virtual terminal connection unit establishes a virtual terminal connection session between the thin client 20 and the virtual terminals 61 and 62 arranged in the virtual terminal accommodation server 50 operated by the virtual terminal provider. The peripheral device connection session establishing unit uses a technology (eg, “USB over IP”) that encapsulates the USB protocol with an IP packet to connect the peripheral device to the connection management server 70 operated by the virtual terminal operator. Establish a session.

  The router 30 relays various information exchanged between each device accommodated in the user environment 101 and each device accommodated in the virtual terminal operator environment 401 via the core network 200.

  As shown in FIG. 1, the virtual terminal provider environment 401 accommodates a virtual terminal accommodation server 50, a connection management server 70, and a router 40.

  The virtual terminal accommodation server 50 is a general-purpose server that accommodates virtual terminals to be used by clients such as the thin client 20, and for example, a virtual terminal 61 and a virtual terminal 62 are arranged for each client.

  The virtual terminal 61 and the virtual terminal 62 (hereinafter referred to as a virtual terminal as appropriate) are virtual software that can be remotely operated from a client such as the thin client 20. FIG. 4 shows an example of the functional configuration of the virtual terminal. FIG. 4 is a diagram illustrating an example of a functional configuration of the virtual terminal. As illustrated in FIG. 4, the virtual terminal includes a connection permission state confirmation unit, a connection permission terminal change unit, and a peripheral device connection destination change request unit.

  When receiving a request for virtual terminal connection, the connection permission state confirmation unit confirms the connection permission state of the request source terminal (thin client or business operator PC) with the connection management server 70. The connection-permitted terminal changing unit requests the connection management server 70 to add a terminal that permits connection to the virtual terminal and to delete a terminal that does not permit connection to the virtual terminal. The peripheral device connection destination change request unit requests the connection management server 70 to change the connection destination terminal of the peripheral device.

  The connection management server 70 manages the connection destination of the virtual terminal. FIG. 5 shows an example of the functional configuration of the connection management server. FIG. 5 is a diagram illustrating an example of a functional configuration of the connection management server. As illustrated in FIG. 5, the connection management server 70 includes a peripheral device connection transfer unit, a virtual terminal connection state management unit, and a peripheral device connection state management unit.

  The peripheral device connection transfer unit performs a peripheral device connection session such as “USB over IP” to the virtual terminal or the connection destination terminal of the peripheral device according to the information (connection state) held in the peripheral device connection state management table. Establish.

  The virtual terminal connection state management unit has a virtual terminal connection state management table that holds the virtual terminal connection state of the thin client 20 and the connection permission state of the external terminal to the virtual terminal, and based on the virtual terminal connection state management table, Responds to the connection permission status confirmation from the virtual terminal. FIG. 6 shows a configuration example of the virtual terminal connection state management table. FIG. 6 is a diagram illustrating a configuration example of the virtual terminal connection state management table. As illustrated in FIG. 6, the virtual terminal connection state management table stores a user ID, a session ID, a connection destination virtual terminal IP address, and information on a connection-permitted external terminal in association with each other.

  The peripheral device connection state management unit uses the peripheral device connection state management table to obtain information on the virtual connection destination terminal (virtual terminal) of the peripheral device physically connected to the connection source thin client of the virtual terminal connection session. to manage. FIG. 7 shows a configuration example of the peripheral device connection state management table. FIG. 7 is a diagram illustrating a configuration example of the peripheral device connection state management table. As illustrated in FIG. 7, the peripheral device connection state management table stores a user ID, a session ID, a device ID, and connection destination information in association with each other.

  The router 40 receives various information exchanged between each device accommodated in the user environment 101 and each device accommodated in the virtual terminal operator environment 401 via the core network 200, and the virtual terminal business. Various information exchanged between each device accommodated in the operator environment 401 and each device accommodated in the operator A environment 801 and the operator B environment 802 is relayed.

  The operator A environment 801 accommodates the router 81 and the operator PC 91. The router 81 relays various information exchanged between each device accommodated in the virtual terminal operator environment 401 and each device accommodated in the operator A environment 801. The business operator PC 91 is a PC (Personal Computer) used by a business operator who provides remote support to peripheral devices physically connected to the thin client 20.

  The operator B environment 802 accommodates the router 82 and the operator PC 92. The router 82 relays various information exchanged between each device accommodated in the virtual terminal operator environment 401 and each device accommodated in the operator B environment 802. The business operator PC 92 is a PC (Personal Computer) used by a business operator who provides remote support to peripheral devices physically connected to the thin client 20.

  FIG. 8 shows an example of the functional configuration of the operator PC 91 and the operator PC 92 (hereinafter, appropriately referred to as the operator PC). FIG. 8 is a diagram illustrating an example of a functional configuration of the operator PC. As shown in FIG. 8, the business operator PC includes a virtual terminal connection unit and a peripheral device storage unit. The virtual terminal connection unit establishes a virtual terminal connection session with the virtual terminal. The peripheral device accommodating unit establishes a peripheral device connection session by “USB over IP” or the like with respect to the connection management server 70, and accommodates and recognizes the peripheral device physically connected to the thin client 20.

[Processing by Connection Control System (Example 1)]
A flow of processing by the connection control system according to the first embodiment will be described with reference to FIGS. 9 to 11. 9 to 11 are diagrams illustrating a process flow of the connection control system according to the first embodiment.

(Virtual terminal connection processing)
First, a virtual terminal connection process between the thin client 20 and the virtual terminal 61, which is started after the USB device 11 and the USB device 12 are physically connected to the thin client 20, will be described with reference to FIG.

  As shown in FIG. 9, the thin client 20 transmits a virtual terminal allocation request to the connection management server 70 (S101). The virtual terminal allocation request includes a virtual terminal service user ID (for example, “User A”) and a password for user authentication.

  When receiving the virtual terminal allocation request from the thin client 20, the connection management server 70 transmits a virtual terminal allocation response to the thin client 20 (S102). More specifically, after performing user authentication using the user ID and password included in the virtual terminal allocation request, the connection management server 70 determines a virtual terminal to be allocated to this user ID and sends a virtual terminal allocation response to the thin client 20. Send to. The virtual terminal assignment response includes an IP address of the assigned virtual terminal (for example, virtual terminal 61) and a ticket for connection authentication.

  When the thin client 20 receives the virtual terminal allocation response from the connection management server 70, the thin client 20 connects to the virtual terminal 61 based on the IP address (for example, “11.11.11.11”) included in the virtual terminal allocation response. A request is transmitted (S103). The thin client 20 inserts a ticket for connection authentication included in the virtual terminal assignment response received from the connection management server 70 into the virtual terminal connection request.

  When the virtual terminal 61 receives the virtual terminal connection request from the thin client 20, the virtual terminal 61 verifies the validity of the ticket included in the virtual terminal connection request. A terminal connection session is established (S104). The virtual terminal connection session established in step S104 is maintained until it is subsequently disconnected, and the display output of the virtual terminal 61 is transmitted to the thin client 20 and displayed on the display of the thin client 20.

  When the virtual terminal 61 completes the establishment of the virtual terminal connection session with the thin client 20, the virtual terminal 61 transmits a virtual terminal connection completion notification to the connection management server 70 (S105).

  Upon receiving the virtual terminal connection completion notification from the virtual terminal 61, the connection management server 70 adds a new record to the virtual terminal connection management table, and transmits a virtual terminal connection completion response to the thin client 20 after the addition is completed (S106). . Specifically, for the virtual terminal connection session established between the thin client 20 and the virtual terminal 61, the connection management server 70 identifies a session ID (for example, “1234” for uniquely identifying the session). )). Then, the connection management server 70 associates the user ID: “User A”, the session ID: “1234”, and the connection destination virtual terminal IP address: “11.11.11.11” with each other in a virtual terminal connection state table (FIG. 6)) as a new record. Since the new record is being registered, no information is registered in the connection permitted external terminal field of the virtual terminal connection state table, and the state becomes empty. Then, after completing the addition of the new record to the virtual terminal connection state table, the connection management server 70 transmits a virtual terminal connection completion response to the thin client 20. The connection management server 70 inserts a session ID into this virtual terminal connection completion response.

  When the thin client 20 receives the virtual terminal connection completion response from the connection management server 70, in order to use the USB device 11 and the USB device 12 that are USB-connected to the thin client 20 on the virtual terminal 61, a USB device connection request Is transmitted to the connection management server 70 (S107). The thin client 20 inserts the user ID, the session ID, and the device IDs of the USB device 11 and the USB device 12 into the USB device connection request in the USB device connection request. As the device ID, information that can be uniquely specified by the thin client 20 in the virtual terminal connection session with the virtual terminal 61 is assigned to each USB device.

  Upon receiving the USB device connection request from the thin client 20, the connection management server 70 adds a new record for each device ID inserted in the USB device connection request to the USB device connection state management table. A device connection response is transmitted to the thin client 20 (S108). More specifically, in the connection management server 70, the connection destination of the USB device 11 and the USB device 12 is a virtual connection destination of the user (“User A”) of the thin client 20 that is the transmission source of the USB device connection request. Each virtual terminal 61 that is a terminal is set. Then, the connection management server 70 associates the user ID: “User A”, the session ID: “1234”, the device ID: “USB_11”, and the connection destination: “virtual terminal 61” with the peripheral device connection. Register as a new record in the status table (see FIG. 7). Then, the connection management server 70 transmits a USB device connection response to the thin client 20 after completing the addition of the new record to the peripheral device connection state table.

  When the thin client 20 receives the USB device connection response from the connection management server 70, the thin client 20 establishes a “USB over IP” connection session with the connection management server 70 (S109).

  After establishing the “USB over IP” connection session with the thin client 20, the connection management server 70 establishes the “USB over IP” connection session with the virtual terminal 61 according to the peripheral device connection state management table. Establish (S110). As a result, the USB device 11 and the USB device 12 physically connected to the thin client 20 are recognized on the virtual terminal 61. In addition, the “USB over IP” connection session established between the thin client 20 and the connection management server 70 in step S109 and step S110 is continued until disconnected.

  After the “USB over IP” connection session is established between the connection management server 70 and the virtual terminal 61, the USB device 11 and the USB device 12 are established between the thin client 20 and the connection management server 70. A USB device connected to the virtual terminal 61 on the virtual terminal 61 via the “USB over IP” connection session and the “USB over IP” connection session established between the connection management server 70 and the virtual terminal 61. Recognized as

(Support processing by the operator)
Next, with reference to FIG. 10, a case will be described in which a business operator remotely supports peripheral devices physically connected to the thin client 20. In the following, for example, when a problem occurs in the USB device 11 connected to the thin client 20, the support person in charge of the business operator A uses the business operator PC 91 to use the virtual terminal 61 to which the thin client 20 is connected. A case will be described as an example in which a failure of the USB device 11 recognized on the virtual terminal 61 is diagnosed and analyzed by connecting to the virtual terminal 61. The upper part of FIG. 10 shows a process of connecting the operator PC to the virtual terminal to which the thin client is connected, and the lower part of FIG. 10 is a process of switching the connection destination of the USB device connected to the thin client to the operator PC 91. Indicates.

(Process of connecting the operator's PC to the virtual terminal)
The connection process of the operator PC to the virtual terminal shown in the upper part of FIG. 10 will be described. As shown in the upper part of FIG. 10, in order to permit connection from the operator A to the virtual terminal 61, the thin client 20 transmits a connection permission terminal change request from the virtual terminal 61 to the connection management server 70 ( S201). For example, a user (“User A”) of the thin client 20 operates the virtual terminal 61 through a virtual terminal connection session with the virtual terminal 61 to connect to the connection management server 70 from the virtual terminal 61. The permitted terminal change request is transmitted. In this connection permitted terminal change request, a user ID (for example, “User A”), a session ID (for example, “1234”), and a business that permits connection to the virtual terminal 61 It is assumed that the IP address of the user PC 91 is inserted. Although the operator name can be inserted into the connection permission terminal change request instead of the IP address, in this case, the connection management server 70 holds the IP assigned to the operator name and the operator PC that is held in advance. It is assumed that an IP address corresponding to the business name is acquired by referring to a table in which addresses are associated.

  When the connection management server 70 receives a connection permission terminal change request (request for connection permission of the operator PC 91 to the virtual terminal 61) from the virtual terminal 61, the virtual terminal connection state management table (FIG. 6) for the column of the connection permission external terminal. Record) is updated, and after the update is completed, a connection permission terminal change response is transmitted to the virtual terminal 61 (S202). More specifically, the connection management server 70 searches the virtual terminal connection state management table using the user ID and session ID included in the connection permission terminal change request as keys, and enters the connection permission external terminal field of the hit record. Then, the IP address of the operator PC 91 included in the connection permission terminal change request is additionally registered. Then, the connection management server 70 transmits a connection permission terminal change response to the virtual terminal 61.

  In response to a request from the support person in charge of the business operator A, the business operator PC 91 transmits a virtual terminal connection request to the virtual terminal 61 (S203). Note that the support person in charge of operator A sends the IP address of the virtual terminal 61 that is the destination of the virtual terminal connection request or the host name that can be resolved by DNS (Domain Name System) to the thin client 20 that wants to support it. It is assumed that the user (“User A”) has confirmed in advance by telephone or the like.

  When receiving the virtual terminal connection request from the operator PC 91, the virtual terminal 61 transmits a connection permission state confirmation request to the connection management server 70 (S204). The virtual terminal 61 inserts the IP address of the operator PC 91 that is the transmission source of the virtual terminal connection request in the connection permission state confirmation request. Even if the virtual terminal 61 receives a virtual terminal connection request from the operator PC 91 before receiving the connection permission terminal change response from the connection management server 70, the virtual terminal 61 sends a connection permission state confirmation request to the connection management server 70. The connection permission terminal change request / response process with the connection management server 70 is executed. At this time, when NG is returned from the connection management server 70 as a connection permission state confirmation response, the virtual terminal 61 establishes a virtual terminal connection session with the operator PC 91 as described below. Absent. On the other hand, the operator PC 91 retries the virtual terminal connection request until the connection permitted terminal change request / response processing between the virtual terminal 61 and the connection management server 70 is completed and a session is established.

  When receiving the connection permission state confirmation request from the virtual terminal 61, the connection management server 70 confirms the connection permission state based on the virtual terminal connection state management table, and transmits a connection permission state confirmation response to the virtual terminal 61 ( S205). Specifically, the connection management server 70 searches the virtual terminal connection state management table using the IP address of the operator PC 91 included in the connection permission state confirmation request as a key, and in the example shown in FIG. Since the IP address registered in the column of the connection permission external terminal corresponding to the URL matches the IP address of the operator PC 91 included in the connection permission state confirmation request, the connection permission state is “OK” (connection permission A connection permission state confirmation response is transmitted to the virtual terminal 61. Temporarily, the virtual terminal connection state management table is searched using the IP address of the operator PC included in the connection permission state confirmation request as a key, and the IP address registered in the column of the connection permission external terminal corresponding to the virtual terminal 61; If the IP address of the operator PC 91 included in the connection permission state confirmation request does not match, the connection management server 70 indicates that the connection permission state is “NG” (not a connection permission state). “NG” is transmitted to the virtual terminal 61 as a confirmation response.

  Upon receiving the connection permission status response (“OK”) from the connection management server 70, the virtual terminal 61 establishes a virtual terminal connection session with the business operator PC 91 (S206). The virtual terminal connection session established in step S206 is maintained until it is disconnected thereafter, and the display output of the virtual terminal 61 is transmitted to the business operator PC 91 and displayed on the business operator PC 91 display. Similarly, as shown in FIG. 10, the virtual terminal connection session established between the virtual terminal 61 and the thin client 20 is also maintained.

  The support person in charge of the business operator A confirms the status of the malfunction of the USB device 11 recognized by the virtual terminal through the virtual terminal connection session established between the virtual terminal 61 and the business operator PC 91 in step S206. If it is possible to solve the problem on the spot, and analysis using dedicated software is necessary to perform a more detailed analysis, the USB device 11 is directly recognized by the business operator PC 91. 11 is switched to the business operator PC 91.

(USB device connection destination switching process)
Hereinafter, the switching process of the connection destination of the USB device shown in the lower part of FIG. 10 will be described. As shown in the lower part of FIG. 10, the thin client 20 transmits a USB device connection destination change request from the virtual terminal 61 to the connection management server 70 (S301). For example, a user of the thin client 20 (“User A”) operates the virtual terminal 61 via a virtual terminal connection session with the virtual terminal 61, so that the virtual terminal 61 connects the USB to the connection management server 70. A device connection destination change request is transmitted. In this USB device connection destination change request, the user ID (for example, “User A”), the session ID (for example, “1234”), and the USB device whose connection destination is to be changed are included. It is assumed that the device ID (in the case shown in FIG. 10, the device ID of the USB device 11) and the IP address of the business operator PC 91 desired as the connection change destination are inserted. Note that, instead of the IP address, the connection change destination operator name can be inserted into the USB device connection destination change request. In this case, the connection management server 70 holds the operator name and the operator PC in advance. The IP address corresponding to the business name is acquired by referring to the table in which the IP address assigned to the is associated. The session ID (the session ID of the virtual terminal connection session between the thin client 20 and the virtual terminal 61) is inserted by the virtual terminal 61, for example.

  When the connection management server 70 receives the USB device connection destination change request from the virtual terminal 61, the connection management server 70 updates the record of the peripheral device connection state management table (see FIG. 7) for the connection destination column. Establish a “USB over IP” connection session (S302). Specifically, the connection management server 70 includes a user ID (for example, “User A”), a session ID (for example, “1234”) included in the USB device connection destination change request, and a device ID for the USB device (for example, “1234”). By searching the peripheral device connection state management table using ““ USB — 11 ”” as a key, and changing the connection destination field of the hit record to the IP address of the operator PC 91 included in the USB device connection destination change request Then, the “USB over IP” connection session is established with the operator PC 91. The operator PC 91 establishes the “USB over IP” connection session established with the connection management server 70 in step S302, and FIG. Established between the thin client 20 and the connection management server 70 in steps S109 and S110 shown A body via a "USB-over-IP" connection session, it is possible to recognize the USB device 11 which is physically connected to the thin client 20 directly.

  Then, the connection management server 70 transmits a USB device connection destination change response to the virtual terminal 61 (S303). In accordance with an instruction from the support person in charge of the business operator A, the business operator PC 91 executes analysis and recovery processing of the USB device 11 using dedicated software (S304).

  For example, after the recovery processing of the USB device 11 is completed, the thin client 20 transmits a USB device connection destination change request from the virtual terminal 61 to the connection management server 70 (S305). Note that, for example, a user (“User A”) of the thin client 20 that has received a report on the completion of the recovery processing of the USB device 11 by telephone or the like uses the virtual terminal connection session with the virtual terminal 61 to connect the virtual terminal 61. By operating, a USB device connection destination change request is transmitted from the virtual terminal 61 to the connection management server 70. In this USB device connection destination change request, the user ID (for example, “User A”), the session ID (for example, “1234”), and the device ID of the USB device whose connection destination is to be changed (in the case shown in FIG. 10). , Device ID of the USB device 11), and the IP address of the virtual terminal 61 desired as a connection change destination is inserted.

  When the connection management server 70 receives the USB device connection destination change request from the virtual terminal 61, the user ID (for example, “User A”), the session ID (for example, “1234”) included in the USB device connection destination change request, The peripheral device connection state management table is searched using the device ID of the USB device (for example, ““ USB — 11 ”” as a key), and the connection destination column of the hit record is displayed in the virtual terminal 61 included in the USB device connection destination change request. By changing the IP address to the virtual terminal 61, a “USB over IP” connection session is established with the virtual terminal 61 (S306), and the connection management server 70 transmits a USB device connection destination change response to the virtual terminal 61. (S307).

(Virtual terminal connection disconnection process)
Next, the virtual terminal connection disconnection process will be described with reference to FIG. As illustrated in FIG. 11, when the virtual terminal 61 detects disconnection of the virtual terminal connection session with the thin client 20, the virtual terminal 61 transmits a virtual terminal connection disconnection notification to the connection management server 70 (S401). It is assumed that the user ID and the session ID are inserted in the virtual terminal connection disconnection notification.

  When the connection management server 70 receives the virtual terminal connection disconnection notification from the virtual terminal 61, the connection management server 70 uses the user ID and session ID included in the virtual terminal connection disconnection notification as a key and the virtual terminal connection state management table (see FIG. 6). Search is made and the hit record is deleted (S402). Similarly, the connection management server 70 searches the peripheral device connection state management table (see FIG. 7) using the user ID and session ID included in the virtual terminal connection disconnection notification as keys, and deletes the hit record. To do. As a result, the “USB over IP” connection session with the thin client 20 and the “USB over IP” connection session with the virtual terminal 61 associated with the session ID included in the virtual terminal connection disconnection notification are both disconnected. The

[Effects of Example 1]
As described above, in the connection control system according to the first embodiment, for example, the connection management server 70 has received a connection permission state confirmation request for a provider PC that is permitted to connect from the virtual terminal 61 to the virtual terminal 61. In such a case, on the condition that the IP address of the business operator PC 91 included in the connection permission status confirmation request matches the IP address stored in the virtual terminal connection status management table (see FIG. 6), A determination result indicating that the connection is permitted is derived, and the derived determination result is transmitted to the virtual terminal 61 as a response to the connection permission state confirmation request. When the virtual terminal 61 receives a determination result indicating that the operator PC 91 is in the connection permission state from the connection management server 70 as a response to the connection permission state confirmation request, the virtual terminal 61 establishes a virtual terminal connection session with the operator PC 91. Establish. That is, according to the first embodiment, the operator PC 91 can check the status of the USB device 11 recognized on the virtual terminal 61 through the virtual terminal connection session established with the virtual terminal 61. , It is possible to remotely support peripheral devices used in a virtual environment without changing the settings of the thin client or adding new functions to the thin client, and the situation can be solved by checking the status on the virtual terminal 61. If the USB device is faulty, it can be solved on the spot by remote support.

  In the first embodiment, when the connection management server 70 receives a USB device connection request from the thin client 20, the connection management server 70 uses the IP address of the virtual terminal 61 connected to the thin client 20 through the virtual terminal connection session. After newly recording in the peripheral device connection state management table as a virtual connection destination of the USB device 11 physically connected to the client 20, the “USB” is connected with the thin client 20 and with the virtual terminal 61. An “over IP” connection session (peripheral device connection session) is established. For this reason, according to the first embodiment, peripheral devices such as USB devices physically connected to the thin client can be connected without changing the setting of the thin client or adding a new function to the thin client. The virtual terminal connected to the thin client can be recognized through the virtual terminal connection session.

  In the first embodiment, the connection management server 70 changes the connection destination of the USB device when receiving a change request from the virtual terminal 61 to change the connection destination of the USB device from the virtual terminal 61 to the business operator PC 91. Peripheral device connection records that correspond to the session ID that identifies the user ID that identifies the user of the thin client 20 that connects to the virtual terminal 61 and the virtual terminal connection session that are established with the virtual terminal, included in the request From the status management table (see FIG. 7), the virtual connection destination in the search hit record is searched from the IP address of the virtual terminal 61 to the IP address of the operator PC 91 included in the change request for the connection destination of the USB device. Change to and update. Then, the connection management server 70 establishes a peripheral device connection session with the business operator PC 91 after updating the virtual connection destination recorded in the peripheral device connection state management table. For this reason, according to the first embodiment, the business operator PC 91 can directly recognize peripheral devices such as a USB device physically connected to the thin client on the business operator PC 91. For more detailed analysis, it is possible to perform analysis using dedicated software.

  Further, in the first embodiment, the connection management server 70 changes the connection destination of the USB device from the virtual terminal 61 to the business operator PC 91, for example, by changing the connection destination of the USB device to, for example, the business. Since the user PC 91 returns to the virtual terminal 61, the original connection state can be easily restored.

  In the first embodiment, the connection management server 70 adds a new record for each device ID to the USB device connection state management table in response to the USB device connection request from the thin client 20, and permits connection from the virtual terminal 61. A case has been described in which the IP address of the operator PC 91 is additionally registered in the virtual terminal connection state management table as information on a connection-permitted external terminal in response to a terminal change request. It should be noted that the peripheral device such as a USB device is connected to the thin client 20 and the peripheral device connection session is established, and the IP address of the business operator PC permitted to connect to the virtual terminal 61 is preliminarily connected externally. An embodiment in which the terminal information is statically registered in the virtual terminal connection state management table is also conceivable. In this case, when the connection management server 70 receives from the virtual terminal 61 the connection permission state confirmation request for the business operator PC that is permitted to connect, the IP address of the business operator PC 91 included in this request and the virtual terminal On the condition that the IP address stored in the connection state management table matches, it is directly determined that the business operator PC 91 is in the connection permission state, and the determination result is returned to the virtual terminal 61. Upon receiving this response, the virtual terminal 61 can proceed with the process of establishing a virtual terminal connection session with the business operator PC 91.

  Example 2 will be described below as another embodiment of the connection control system and connection control method according to the present invention.

(1) Device Configuration, etc. The configuration of the connection control system according to the first embodiment, for example, each component of the connection control system shown in FIG. 1 is functionally conceptual and is not necessarily physically configured as illustrated. I don't need it.

  For example, the virtual terminal accommodation server 50 and the connection management server 70 installed in the virtual terminal provider environment 401 in the connection control system shown in FIG. 1 may be functionally or physically integrated. Further, the peripheral device connection transfer unit and the peripheral device connection state management unit included in the connection management server 70 illustrated in FIG. 5 may be functionally or physically integrated. As described above, the specific form of distribution or integration of each component of the connection control system is not limited to that shown in FIGS. 1 and 5 or the like. Depending on the above, it can be configured to be functionally or physically distributed and integrated in arbitrary units.

(2) Connection Control Method The following connection control method is realized by the connection control system according to the first embodiment.

  That is, a thin client terminal to which a peripheral device is connected, a virtual terminal connected to the thin client terminal, a connection management server that manages connection to the virtual terminal, and a business that executes remote support for the peripheral device A connection control method executed by a connection control system having an operator terminal operated by a user, wherein the thin client terminal transmits a connection request for the peripheral device to the connection management server (for example, When the connection management server receives a connection request for the peripheral device from the thin client terminal, identification information unique to the virtual terminal connected to the thin client terminal is obtained. The virtual connection is stored in the peripheral device connection state management table that stores information on the virtual connection destination of the peripheral device. After recording as a destination, a peripheral device connection session establishing step of establishing a peripheral device connection session with the thin client terminal and with the virtual terminal and transmitting a response to the connection request to the thin client terminal ( For example, see step S108 to step S110 in FIG. 9), and the virtual terminal issues a connection permission request for requesting connection permission of the provider terminal to the virtual terminal in response to an operation input from the thin client terminal. A connection permission request transmission step (refer to step S201 in FIG. 10) to be transmitted to the connection management server, and when the connection management server receives the connection permission request from the virtual terminal, the thin client terminal connects to the virtual terminal Connection to the virtual terminal connected through a session is permitted In the virtual terminal connection state management table storing identification information unique to the article trader terminal, after newly identifying identification information unique to the provider terminal included in the connection permission request, a response to the connection permission request A connection permitted terminal recording step to be transmitted to the virtual terminal (see step S202 in FIG. 10), and a provider permitted to connect to the virtual terminal when the virtual terminal receives a connection request from the provider terminal A confirmation request transmission step (see step S203 in FIG. 10) for transmitting a terminal confirmation request to the connection management server; and when the connection management server receives the confirmation request, the operator included in the confirmation request On the condition that the identification information unique to the terminal matches the identification information stored in the virtual terminal connection state management table, the business A confirmation response step of deriving a determination result that the user terminal is in a connection-permitted state and transmitting the derived determination result to the virtual terminal as a response to the confirmation request (see step S204 to step S205 in FIG. 10) When the virtual terminal receives, as a response to the confirmation request, a determination result indicating that the provider terminal that is the transmission source of the connection request is in a connection-permitted state from the connection management server, the provider A connection control method including a session establishing step (see step S206 in FIG. 10) for establishing the virtual terminal connection session with a terminal is realized.

(3) Program for causing the connection control system to execute a predetermined procedure The various processes described in the above-described embodiments (for example, FIGS. 9 to 11) are related to the first embodiment such as a personal computer and a workstation. A program for causing a computer implemented as the connection management server 70 included in the connection control system to execute procedures (processes) for realizing the same processing functions as the various types of processing described in the above embodiment is installed. Can also be realized. Therefore, in the following, an example of a computer that realizes the same functions as the various types of processing (for example, FIGS. 9 to 11 and the like) described in the above embodiment will be described with reference to FIG. FIG. 12 is a diagram illustrating an example of a computer that executes a program for realizing the same function as the processing described in the above-described embodiment.

  As illustrated in FIG. 12, the computer 300 implemented as the connection management server 70 includes, for example, a memory 301 and a CPU (Central Processing Unit) 302. Further, the computer 300 includes a hard disk drive interface 303 and an optical disk drive interface 304 as shown in FIG. Further, the computer 300 includes a serial port interface 305, a video adapter 306, and a network interface 307, as shown in FIG. The computer 300 connects these units 301 to 307 via a bus 308.

  As shown in FIG. 12, the memory 301 includes a ROM (Read Only Memory) and a RAM (Random Access Memory). The ROM stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 303 is connected to the hard disk drive 309 as shown in FIG. The optical disc drive interface 304 is connected to the optical disc drive 310 as shown in FIG. For example, a removable storage medium such as an optical disk is inserted into the optical disk drive 310. The serial port interface 305 is connected to a mouse 400 and a keyboard 500, for example, as shown in FIG. As shown in FIG. 12, the video adapter 306 is connected to a display 600, for example.

  Here, as shown in FIG. 12, the hard disk drive 309 stores, for example, an OS (Operating System), application programs, program modules, and program data.

  That is, a program having the same function as the connection management server 70 described above is stored in, for example, the hard disk drive 309 as a program module in which a command executed by the computer 300 is described. That is, a program module describing a procedure for causing the computer 300 as the connection management server 70 to implement the same processing functions as the various types of processing described in the above-described embodiment (for example, FIGS. 9 to 11) Stored in the hard disk drive 309. This program module corresponds to, for example, a procedure (process) executed by the peripheral device connection transfer unit, the virtual terminal connection state management unit, the peripheral device connection state management unit, and the like of the connection management server 70 shown in FIG.

  In addition, it is used by a program module in which a procedure for causing the computer 300 as the connection management server 70 to implement the same processing functions as the various processes (for example, FIG. 9 to FIG. 11) described in the above-described embodiments is described. The stored data is stored as program data, for example, in the hard disk drive 309. For example, this program data corresponds to various data recorded in, for example, the virtual terminal connection state management table (see FIG. 6) or the peripheral device connection state management table (see FIG. 7).

  Then, the CPU 302 reads out the program modules and program data stored in the hard disk drive 309 to the RAM as necessary, and realizes various processes (for example, FIGS. 9 to 11) described in the above-described embodiments. Follow the steps.

  It should be noted that a program module or program in which procedures for causing the computer 300 as the connection management server 70 to implement the same processing functions as the various types of processing described in the above-described embodiments (for example, FIG. 9 to FIG. 11) are described. The data is not limited to being stored in the hard disk drive 309, and may be stored in, for example, the optical disk drive 310 that is a removable storage medium. In this case, the CPU 302 reads out program modules and program data having functions similar to those of the connection management server 70 via the optical disc drive 310.

  Alternatively, a program module or program in which procedures for causing the computer 300 as the connection management server 70 to implement the same processing functions as the various types of processing (for example, FIG. 9 to FIG. 11) described in the above embodiment are described. The data may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). In this case, the CPU 302 reads program modules and program data having the same functions as those of the connection management server 70 from other computers via the network interface 307.

  Instead of the CPU 302 operating by a program to perform various processes, for example, the process can be performed using an electronic circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). Further, a flash memory or the like can be used as the memory 301.

DESCRIPTION OF SYMBOLS 11 USB apparatus 12 USB apparatus 20 Thin client 30 Router 40 Router 50 Virtual terminal accommodation server 61 Virtual terminal 62 Virtual terminal 70 Connection management server 81 Router 82 Router 91 Provider PC
92 Business PC
200 core network 300 computer 301 memory 302 CPU
303 Hard Disk Drive Interface 304 Optical Disk Drive Interface 305 Serial Port Interface 306 Video Adapter 307 Network Interface 308 Bus 309 Hard Disk Drive 310 Optical Disk Drive 400 Mouse 500 Keyboard 600 Display

Claims (5)

  1. A connection control system comprising: a thin client terminal to which a peripheral device is connected; a virtual terminal connected to the thin client terminal; and a business operator terminal operated by a business operator that performs remote support for the peripheral device. ,
    The connection control system includes:
    A virtual terminal connection state management table storing identification information unique to the provider terminal that is permitted to connect to the virtual terminal to which the thin client terminal is connected via a virtual terminal connection session;
    When receiving a confirmation request for an operator terminal permitted to connect to the virtual terminal from the virtual terminal, identification information unique to the operator terminal included in the confirmation request, and the virtual terminal connection state management table A determination result that the operator terminal is in a connection-permitted state is derived on condition that the identification information stored in the virtual machine matches the identification information, and the derived determination result is used as a response to the confirmation request. A connection management server having a confirmation response unit to be transmitted to the terminal;
    The virtual terminal is
    As a response to the confirmation request, when a determination result indicating that the provider terminal that is the transmission source of the connection request is in a connection-permitted state is received from the connection management server, A connection control system comprising a session establishment unit for establishing a virtual terminal connection session.
  2. The connection management server
    Peripheral device connection state management table for storing identification information unique to the virtual terminal as information on the virtual connection destination of the peripheral device connected to the thin client terminal;
    When receiving a connection request for the peripheral device from the thin client terminal, identification information unique to the virtual terminal connected to the thin client terminal is obtained, and virtual connection of the peripheral device connected to the thin client terminal is performed. Peripheral device connection status recording unit newly recording in the peripheral device connection status management table as a destination,
    After recording identification information unique to the virtual terminal in the peripheral device connection state management table as a virtual connection destination of the peripheral device, connect the peripheral device to the thin client terminal and to the virtual terminal. After each session is established, a peripheral device connection session establishment unit that transmits a response to the connection request to the thin client terminal;
    When a connection permission request for requesting connection permission of the provider terminal to the virtual terminal is received from the virtual terminal, identification information unique to the provider terminal included in the connection permission request is transmitted to the virtual terminal. A connection-permitted terminal recording unit that newly records in the virtual terminal connection state management table as identification information unique to the operator terminal that is permitted to connect, and then transmits a response to the connection permission request to the virtual terminal. Have
    The client terminal is
    A connection request transmitter for transmitting a connection request for the peripheral device to the connection management server;
    The virtual terminal is
    A connection permission request transmitter for transmitting the connection permission request to the connection management server in response to an operation input from the client terminal;
    And a confirmation request transmitter for transmitting the confirmation request to the connection management server when a connection request is received from the provider terminal after receiving a response to the connection permission request from the connection management server. The connection control system according to claim 1, wherein:
  3. When the peripheral device connection state recording unit receives a change request from the virtual terminal to change the connection destination of the peripheral device from the virtual terminal to the provider terminal, the peripheral device connection state change request A record corresponding to a user ID for identifying a user of the thin client terminal connected to the virtual terminal and a session ID for identifying a virtual terminal connection session established between the virtual terminal and the peripheral Search from the device connection status management table, and identify the virtual connection destination in the record hit by the search, from the identification information unique to the virtual terminal, specific to the provider terminal included in the change request for the connection destination of the peripheral device Change to the identification information of
    The peripheral device connection session establishing unit is connected to the operator terminal after the virtual connection destination recorded in the peripheral device connection state management table is updated by the peripheral device connection state recording unit. Establishing a device connection session, sending a response to the change request to change the connection destination of the peripheral device from the virtual terminal to the operator terminal, to the virtual terminal,
    The connection permission request transmission unit transmits, to the connection management server, a change request for changing the connection destination of the peripheral device from the virtual terminal to the provider terminal in response to an operation input from the client terminal. The connection control system according to claim 2.
  4. The peripheral device connection state recording unit changes the connection destination of the peripheral device from the virtual terminal to the provider terminal, and further changes the connection destination of the peripheral device from the provider terminal to the virtual terminal. When the change request is received from the virtual terminal, the record corresponding to the user ID and the session ID included in the change request for the connection destination of the peripheral device is searched from the peripheral device connection state management table, The virtual connection destination in the search hit record is changed from the identification information unique to the provider terminal to the identification information unique to the virtual terminal included in the change request for the connection destination of the peripheral device. ,
    The peripheral device connection session establishing unit updates the virtual device with the virtual terminal after the peripheral device connection state recording unit updates the virtual connection destination recorded in the peripheral device connection state management table. Establish a connection session, send a response to the change request to change the connection destination of the peripheral device from the operator terminal to the virtual terminal to the virtual terminal,
    The connection permission request transmission unit transmits a change request for changing the connection destination of the peripheral device from the provider terminal to the virtual terminal in response to an operation input from the client terminal to the connection management server. The connection control system according to claim 3.
  5. Executed in a connection control system having a thin client terminal to which a peripheral device is connected, a virtual terminal connected to the thin client terminal, and an operator terminal operated by an operator that performs remote support for the peripheral device A connection control method,
    A connection request transmission step in which the thin client terminal transmits a connection request for the peripheral device to a connection management server;
    When the connection management server receives a connection request for the peripheral device from the thin client terminal, identification information unique to the virtual terminal connected to the thin client terminal is obtained as a virtual connection destination of the peripheral device. After recording as a virtual connection destination in the peripheral device connection state management table storing information, establish a peripheral device connection session with the thin client terminal and with the virtual terminal, respectively, for the connection request A peripheral device connection session establishment step of transmitting a response to the thin client terminal;
    A connection permission request transmission step of transmitting a connection permission request for requesting connection permission of the provider terminal to the virtual terminal to the connection management server in response to an operation input from the thin client terminal;
    The provider terminal that is permitted to connect to the virtual terminal to which the thin client terminal is connected via a virtual terminal connection session when the connection management server receives the connection permission request from the virtual terminal. In the virtual terminal connection state management table that stores the unique identification information, the identification information unique to the provider terminal included in the connection permission request is newly recorded, and then a response to the connection permission request is sent to the virtual terminal. A connection permitted terminal recording step to be transmitted;
    When the virtual terminal receives a connection request from the provider terminal, a confirmation request transmission step of transmitting a confirmation request of the provider terminal permitted to connect to the virtual terminal to the connection management server;
    When the connection management server receives the confirmation request, the identification information unique to the provider terminal included in the confirmation request matches the identification information stored in the virtual terminal connection state management table. A determination response step of deriving a determination result that the operator terminal is in a connection-permitted state on the condition that the determination is made, and transmitting the derived determination result to the virtual terminal as a response to the confirmation request;
    When the virtual terminal receives, as a response to the confirmation request, a determination result that the provider terminal that is the transmission source of the connection request is in a connection-permitted state from the connection management server, the provider terminal And a session establishing step of establishing the virtual terminal connection session with the connection control method.
JP2011224807A 2011-10-12 2011-10-12 Connection control system and connection control method Active JP5705699B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2011224807A JP5705699B2 (en) 2011-10-12 2011-10-12 Connection control system and connection control method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2011224807A JP5705699B2 (en) 2011-10-12 2011-10-12 Connection control system and connection control method

Publications (2)

Publication Number Publication Date
JP2013084190A true JP2013084190A (en) 2013-05-09
JP5705699B2 JP5705699B2 (en) 2015-04-22

Family

ID=48529304

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2011224807A Active JP5705699B2 (en) 2011-10-12 2011-10-12 Connection control system and connection control method

Country Status (1)

Country Link
JP (1) JP5705699B2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016009370A (en) * 2014-06-25 2016-01-18 株式会社東芝 Information processing device and operation control method
JP2016133959A (en) * 2015-01-19 2016-07-25 千和 大倉 Network connection device, network connection method, and network connection system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007310508A (en) * 2006-05-16 2007-11-29 Nippon Telegraph & Telephone East Corp Thin client system and program for thin client terminal
JP2011150499A (en) * 2010-01-21 2011-08-04 Dainippon Printing Co Ltd Thin client system, thin client terminal, and thin client program
JP2011198157A (en) * 2010-03-19 2011-10-06 Fujitsu Ltd Virtual computer system, device and method for controlling virtual computer

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007310508A (en) * 2006-05-16 2007-11-29 Nippon Telegraph & Telephone East Corp Thin client system and program for thin client terminal
JP2011150499A (en) * 2010-01-21 2011-08-04 Dainippon Printing Co Ltd Thin client system, thin client terminal, and thin client program
JP2011198157A (en) * 2010-03-19 2011-10-06 Fujitsu Ltd Virtual computer system, device and method for controlling virtual computer

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016009370A (en) * 2014-06-25 2016-01-18 株式会社東芝 Information processing device and operation control method
JP2016133959A (en) * 2015-01-19 2016-07-25 千和 大倉 Network connection device, network connection method, and network connection system

Also Published As

Publication number Publication date
JP5705699B2 (en) 2015-04-22

Similar Documents

Publication Publication Date Title
KR100847596B1 (en) Communication network system, gateway, data communication method and program providing medium
KR100817651B1 (en) Device management system
US8627417B2 (en) Login administration method and server
US7840688B2 (en) Information processing device, server client system, method, and computer program
US8767737B2 (en) Data center network system and packet forwarding method thereof
JP2005536801A (en) Remote storage and joint use of peer-to-peer data
US8347378B2 (en) Authentication for computer system management
AU2008248385B2 (en) Managing network components using USB keys
JP2014516487A (en) Method and system for distributing information on one or more electrical devices
US8266300B2 (en) System and method for plug and play between host and client
JP2009217656A (en) Software update system in information apparatus
WO2013183814A1 (en) Improved security function-based cloud service system and method for supporting same
TWI545446B (en) A method and system for use with a public cloud network
US9301122B2 (en) Apparatus and method for establishing a personal network for providing a CPNS service
US7735129B2 (en) Firewall device
US8813243B2 (en) Reducing a size of a security-related data object stored on a token
US20100174791A1 (en) Short distance wireless communication system and method for accessing instant messenger
KR101209014B1 (en) Data processing device, method, and server to determine types of electric appliances
JP2007156587A (en) Method of controlling power supply, and system realizing the same
US9363285B2 (en) Communication system, network for qualification screening/setting, communication device, and network connection method
US20070288623A1 (en) Device management system
CN102763095B (en) Portable storage interface
US9596501B2 (en) Remote control processing method, device and system
CN102947797B (en) The online service using directory feature extending transversely accesses and controls
US8271632B2 (en) Remote access providing computer system and method for managing same

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20140207

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20141215

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20141224

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20150203

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20150224

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20150225

R150 Certificate of patent or registration of utility model

Ref document number: 5705699

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150