JP5517463B2 - Thin client system, management server and thin client terminal - Google Patents

Description

  The present invention relates to a thin client system that manages connection between a thin client terminal and a thin client server.

  In recent years, the use of thin client systems has been spreading for the purpose of enhancing security and improving the efficiency of operation and management of PC (personal computer) terminals. The thin client system operates a user application to exchange display / input information with a thin client terminal, and a thin client terminal without a storage device such as a hard disk that exchanges display / input information with the thin client server. Consists of The thin client terminal previously installs connection information (such as the IP address of the thin client server) and connection software with the thin client server, and the user connects to the thin client server based on them. The connection authentication with the thin client server is performed using a user ID, a password, or a fingerprint authentication device.

  In the thin client system, the thin client terminal can be connected to a plurality of thin client servers. In the case of a thin client system in which multiple thin client servers are connected, the management server uses the management server to grasp the load status of each thin client server, and distributes the load by distributing the thin client servers to which the thin client terminals are connected. The technique to perform is disclosed in the following Patent Document 1.

JP 2006-209609 A

  However, in the above-described conventional technology, the thin client terminal needs to install setting information and connection software when connecting to the thin client server in advance. For this reason, there is a problem in that when it is necessary to change the setting, it is necessary to change the setting at each thin client terminal, which is troublesome. In addition, there is a problem that it takes time to install and upgrade the connected software. The connection authentication with the thin client server performed by the thin client terminal is only user information. Therefore, there is a problem that connection management with a thin client server corresponding to the thin client terminal to be connected cannot be performed.

  The present invention has been made in view of the above, and an object thereof is to obtain a thin client system capable of managing connection authentication and connection modules in an integrated manner and managing connection between a thin client terminal and a thin client server. To do.

  In order to solve the above-described problems and achieve the object, the present invention provides a thin client terminal, a thin client server, and a management server that manages the connection between the thin client terminal and the thin client server. In the client system, the management server receives user authentication information from the thin client terminal and connects to the thin client server type information available to the user and the thin client server based on the authentication information. Authentication management means for acquiring connection information that is information on the connection and transmitting the information to the thin client terminal, and connection module management for transmitting a connection module file requested from the thin client terminal to the thin client terminal Means, and the sinker The client terminal transmits user authentication information to the management server, and uses the server information acquisition means for receiving the type information and the connection information, and the type information received by the server information acquisition means. Based on the connection information received by the server selection means that selects the thin client server and the server information acquisition means, a request is made to the management server for a connection module necessary for connection with the thin client server selected by the server selection means. And connection module calling means for activating a connection module file acquired from the management server and connecting to the thin client server.

  According to the present invention, there is an effect that connection management between a thin client terminal and a thin client server can be performed.

FIG. 1 is a diagram showing a schematic diagram of a thin client system. FIG. 2 is a diagram illustrating a configuration example of a thin client system. FIG. 3 is a diagram illustrating a configuration example of terminal information. FIG. 4 is a diagram illustrating a configuration example of the management table of the authentication DB. FIG. 5 is a diagram illustrating a configuration example of the management table of the user authorization DB. FIG. 6 is a diagram illustrating a configuration example of the management table of the terminal authorization DB. FIG. 7 is a diagram illustrating a configuration example of the management table of the server information DB. FIG. 8 is a diagram illustrating a configuration example of a management table of the server state management DB. FIG. 9 is a diagram illustrating a configuration example of a management table of the connection module management DB. FIG. 10 is a diagram illustrating a configuration example of the management table of the usage history DB.

  Embodiments of a thin client system according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment.
FIG. 1 is a schematic diagram of a thin client system according to the present invention. The thin client terminal 2 and the thin client server 3 are connected via the network 4. The management server 1 is a server that manages the connection between each thin client terminal 2 and each thin client server 3 in this thin client system.

  FIG. 2 is a diagram showing a configuration example of a thin client system according to the present invention. The thin client system includes a management server 1, a thin client terminal (hereinafter referred to as a terminal) 2, and a thin client server (hereinafter referred to as a server) 3. For convenience of explanation, the number of connections of the terminals 2 is one, but a plurality of terminals 2 can be connected. In addition, since the portion related to the network 4 is the same as the conventional one, it is not shown and description thereof is omitted.

  The management server 1 manages connection between the terminal 2 and the server 3. Specifically, when connecting from the terminal 2 to the server 3, the management server 1 performs user authentication confirmation based on the authentication information and the terminal information notified from the terminal 2, and then the terminal used by the user 2 transmits information on the server 3 available from the terminal 2 to the terminal 2. Further, when a connection module request is received from the terminal 2, the module file of the requested connection module is downloaded to the terminal 2. When the terminal 2 and the server 3 are connected, the server 3 obtains the connection start time and end time. Further, the load state is periodically acquired from the server 3.

  The management server 1 includes an authentication management unit 10, an authentication database (DB) 11, a user authorization database (DB) 12, a terminal authorization database (DB) 13, a server information database (DB) 14, and a server state management unit. 15, a usage history database (DB) 16, a server state management database (DB) 17, a connection module management unit 18, and a connection module management database (DB) 19.

  The authentication management unit 10 receives the authentication information and the terminal information from the terminal 2, refers to the authentication DB 11, the user authorization DB 12, and the terminal authorization DB 13, and performs authorization (whether the corresponding user can use the thin client system from the corresponding terminal). Control. The authentication DB 11 holds information necessary for user authentication such as a user ID, password, and fingerprint information. The user authorization DB 12 holds a list of servers 3 that can be used by the user. The terminal authorization DB 13 holds a list of available servers 3 from the terminal information of the corresponding terminal 2. The server information DB 14 holds a list of server 3 connection information (IP address, server name, protocol, etc.). The server state management unit 15 manages the state of the server 3 (load size, presence / absence of user, etc.). In addition, a history of use of the server 3 by the user is managed. The usage history DB 16 holds the usage history of the time when the user started connection to the server 3 and the time when the connection was terminated. The server state management DB 17 holds the server state sent from the server 3. The connection module management unit 18 manages connection modules and provides connection modules in response to requests from the terminal 2. The connection module management DB 19 holds connection modules (module files) and performs version management according to the server 3.

  The terminal 2 connects to the server 3, performs work using an application provided in the server 3, and stores a work record in the server 3. When the user inputs authentication information when connecting to the server 3, the terminal 2 transmits the authentication information and terminal information to the management server 1. Information on the available server 3 is acquired from the management server 1, and a connection module required for connection with the selected server 3 is requested and acquired from the management server 1. Then, it connects with the server 3 using a connection module.

  The terminal 2 includes an authentication information input unit 20, terminal information 21, a server selection unit 22, a connection module call unit 23, and a connection module 24.

  The authentication information input unit 20 inputs authentication information (user ID and password, fingerprint information, etc.), and sends terminal information 21 and authentication information to the management server 1. Further, information on the available server 3 is acquired from the management server 1. The terminal information 21 is information for identifying a terminal indicating a terminal model, an ID for identifying the terminal, network information (IP address, etc.), and a connection method (LAN, modem, wireless communication, etc.). The server selection unit 22 provides a function of selecting the server 3 used by the user. The connection module calling unit 23 provides a function for calling a connection module necessary for connection to the selected server 3. When the connection module does not exist in its own device, it communicates with the connection module management unit 18 of the management server 1 to download and start the connection module (module file). The connection module 24 is an activated module file downloaded.

  The server 3 is connected to the terminal 2 and provides an application when the user works using the terminal 2, and stores a user's work record and the like. When the server 3 starts connection with the terminal 2, the server 3 notifies the management server 1 of the connection start time and the connection termination time. In addition, the management server 1 is periodically notified of the load state of its own device.

  The server 3 includes a thin client server interface (I / F) 30 and a status transmission agent 31.

  The thin client server I / F 30 is an interface with the terminal 2. The status transmission agent 31 notifies the management server 1 of the load status of its own device. Further, the user notifies the management server 1 of information (usage history) of the time when connection with the own device is started and the time when connection is ended.

  Subsequently, an operation until the terminal 2 connects to the server 3 will be described. When the user connects the terminal 2 to the server 3, the user inputs authentication information to the authentication information input unit 20 of the terminal 2. Authentication information includes user fingerprint information and the like, but here, a user ID and a password are used. The authentication information input unit 20 transmits the input authentication information and the terminal information 21 provided in advance to the management server 1. FIG. 3 is a diagram illustrating a configuration example of the terminal information 21. The terminal information 21 is information assigned to each terminal, and here, as an example, information on the model, terminal ID, IP address, and connection method is the terminal information 21.

  Upon receiving user authentication information (user ID and password) and terminal information 21 from the terminal 2, the authentication management unit 10 of the management server 1 first refers to the authentication DB 11, and the combination of the transmitted user ID and password is Check if it belongs to a registered user. FIG. 4 is a diagram illustrating a configuration example of a management table held in the authentication DB 11. A password corresponding to the user ID is registered.

  When it can be confirmed that the combination of the user ID and the password is that of the registered user, the authentication management unit 10 refers to the user authorization DB 12 and acquires information on the server 3 that can be used by the user. FIG. 5 is a diagram illustrating a configuration example of a management table held by the user authorization DB 12. The available server 3 types are registered for each user ID.

  Further, the authentication management unit 10 refers to the terminal authorization DB 13 and acquires information on the server 3 that can be used from the terminal 2 used by the user for each connection method with the server 3. FIG. 6 is a diagram illustrating a configuration example of a management table held by the terminal authorization DB 13. An available server 3 is registered for each terminal (terminal ID) connection method.

  Next, the authentication management unit 10 refers to the server information DB 14 and acquires the IP address, connection software, and version information of the connection software necessary for connecting to the server 3 for the server 3 that can be used by the user. FIG. 7 is a diagram illustrating a configuration example of a management table held in the server information DB 14. For each server 3, an IP address, connection software, and software version information necessary for connection are registered.

  Next, the authentication management unit 10 acquires information on the load state of the server 3. In the management server 1, when the server status management unit 15 receives the load status information of each server 3, the load information of the server 3 is transferred to the server status management DB 17, and the server status management DB 17 holds the load status of each server 3. To do. Therefore, the authentication management unit 10 acquires the load information of the server 3 that can be used by the user from the load information held by the server state management DB 17 via the server state management unit 15. FIG. 8 is a diagram illustrating a configuration example of a management table held by the server state management DB 17. The load state notified from each server 3 is registered. The load state may be specifically expressed as a numerical value based on information from the server 3, or the load state may be divided into a predetermined number and expressed as “high load” or “low load”. .

  The authentication management unit 10 uses the information acquired by the above processing (the type of the server 3 that can be used for each connection method, the information for connecting to the server 3, the load state of the server 3) as the authentication information input unit of the terminal 2. 20 is transmitted.

  The terminal 2 displays information from the management server 1 received by the authentication information input unit 20 on a display unit (not shown), refers to the load state of the server 3 as necessary, and selects the user from the available servers 3. Selects the server 3 to be used using the server selection unit 22.

  Next, the terminal 2 acquires a connection module necessary for communication with the selected server 3 from the management server 1. Specifically, the server 3 used by the connection module calling unit 23 of the terminal 2 based on the information for connecting to the server 3 received from the management server 1 to the connection module management unit 18 of the management server 1. Sends the type and version information of the connection module software necessary for the connection. The connection module management unit 18 extracts the module file of the requested version of the connection module from the module file held by the connection module management DB 19 and downloads the module file to the connection module call unit 23 of the terminal 2. FIG. 9 is a diagram illustrating a configuration example of a management table held by the connection module management DB 19. The corresponding module file name is registered for each version of the module file of the connection software (connection module).

  The terminal 2 executes the module file of the connection module acquired by the connection module calling unit 23 and starts the connection module 24 so that it can be connected to the thin client server I / F 30 of the server 3 and connected to the server 3. I do. Thereafter, operations performed between the server 3 and the terminal 2 after connection are the same as those of the conventional thin client system.

  The server 3 periodically notifies the server state management unit 15 of the management server 1 of the load state of the own device from the state transmission agent 31. The server state management unit 15 transfers the received server state to the server state management DB 17, and the server state management DB 17 holds the server state.

  As described above, when the user connects from the terminal 2 to the server 3, the management server 1 performs user authentication confirmation, and the server 3 that can be used by the user and the server that can be used from the terminal 2 that the user uses. 3 and connection information necessary for connection with the server 3 is transmitted to the terminal 2 each time the connection is made. In the terminal 2, the server 3 to be used is selected from the servers 3 that can be used by the user, and then a module necessary for connection with the server 3 is acquired.

  Even if the information required for connection with the server 3 is changed, the administrator of the thin client system only needs to change the contents of the database provided in the management server 1 and needs to change the setting at each terminal 2. No. In addition, since the module file necessary for connection with the server 3 is downloaded from the management server 1 and used every time it is connected, only the contents of the database provided in the management server 1 need be updated even when the module file is updated. The update work at each terminal 2 is not necessary. By only updating the contents of the management server 1, the connection between the server 3 and the terminal 2 can be performed in the latest state, and connection management in the thin client system is facilitated.

  Further, in the thin client system of the present embodiment, it is also possible to centrally manage user usage histories.

  For example, the status transmission agent 31 of the server 3 notifies the server status management unit 15 of the management server 1 of the usage history indicating the time when the user started the connection and the time when the connection was terminated, along with the load status information. The server state management unit 15 transfers the user usage history from the server 3 to the usage history DB 16. FIG. 10 is a diagram illustrating a configuration example of a management table held in the usage history DB 16. The usage history DB 16 holds a usage history of which user started connection to which server 3 when and when the connection was terminated.

  For example, the server status management unit 15 can obtain the usage time in the thin client system from the connection start time and the connection end time to each server 3 by searching the usage history DB 16 with the user ID. Conventionally, the usage time can be obtained only for each server 3, but the management server 1 can grasp the usage status of all the servers 3 connected to the system. As a result, the system can easily realize service billing according to the usage time.

  As described above, in the present embodiment, when the user connects from the terminal 2 to the server 3, the management server 1 confirms the user authentication information and the terminal information 21, and the server 3 that the user can use. The server 3 that can be used from the terminal 2 used by the user, and connection information necessary for connection to the server 3 are transmitted to the terminal 2 every time the connection is made. In the terminal 2, the server 3 to be used is selected from the servers 3 that can be used by the user, and thereafter, a connection module necessary for connection with the server 3 is acquired.

  Thereby, even when the information necessary for connection with the server 3 is changed, it is only necessary to change the contents of the database provided in the management server 1, and there is no need to change the setting at each terminal 2. In addition, since the module file necessary for connection with the server 3 is downloaded from the management server 1 and used every time it is connected, only the contents of the database provided in the management server 1 need be updated even when the module file is updated. The update work at each terminal 2 is not necessary. Therefore, it is possible to connect the server 3 and the terminal 2 in the latest state only by updating only the contents of the management server 1, and connection management in the thin client system becomes easy.

  Further, in the present embodiment, the management server 1 centrally manages the time when the user started the connection to the server 3 and the time when it ended. Thereby, in a thin client system, a user's utilization time can be grasped | ascertained easily and the usage fee etc. as the whole system can be put together easily.

  As described above, the thin client system according to the present invention is useful for a thin client system in which a plurality of thin client servers are connected, and is particularly suitable for managing connections between a thin client terminal and a thin client server.

1 management server 2 thin client terminal (terminal)
3 Thin client server (server)
4 Network 10 Authentication Management Unit 11 Authentication DB
12 User authorization DB
13 Terminal authorization DB
14 Server information DB
15 Server status management unit 16 Usage history DB
17 Server state management DB
18 Connection Module Management Unit 19 Connection Module Management DB
20 Authentication Information Input Unit 21 Terminal Information 22 Server Selection Unit 23 Connection Module Calling Unit 24 Connection Module 30 Thin Client Server I / F
31 Status sending agent

Claims (11)

A thin client system comprising a thin client terminal, a thin client server, and a management server that manages connection between the thin client terminal and the thin client server,
The management server
Receive user authentication information from the thin client terminal, and based on the authentication information, obtain type information of a thin client server that can be used by the user and connection information that is information for connecting to the thin client server. Authentication management means for transmitting the information to the thin client terminal;
A connection module management means for transmitting a connection module file, which is connection software requested from the thin client terminal, to the thin client terminal;
With
The thin client terminal
Server information acquisition means for transmitting user authentication information to the management server and receiving the type information and the connection information;
Server selection means for selecting a thin client server to be used, based on the type information received by the server information acquisition means;
Based on the connection information received by the server information acquisition means, a request is made to the management server for a connection module necessary for connection with the thin client server selected by the server selection means, and the connection module acquired from the management server A connection module calling means for starting a file and connecting to the thin client server;
A thin client system comprising: The server information acquisition means of the thin client terminal further transmits terminal information for identifying its own terminal to the management server,
The authentication management means of the management server further receives terminal information from the thin client terminal, acquires the type information and the connection information based on the authentication information and the terminal information, and obtains the information as the thin client Send to device,
The thin client system according to claim 1. The thin client server
Status transmission agent means for transmitting information on the load status of the own server to the management server;
With
The management server further includes:
Server status management means for managing the load status information received from the thin client server;
With
When the authentication management means of the management server transmits the type information and the connection information to the thin client terminal, it obtains information on the load state of the thin client server available to the user from the server state management means, Also send the load status information to the thin client terminal,
The server selection means of the thin client terminal further selects a thin client server to be used based on the load state information received from the management server.
The thin client system according to claim 1 or 2, wherein The thin client server further includes:
Usage history transmission means for transmitting a usage history indicating a time when a user starts connection to the server using the thin client terminal and a time when the connection is terminated to the management server,
With
The management server further includes:
Usage history database means for holding a user usage history received from the thin client server;
With
Extracting the user's usage history by searching the usage history database means based on the user's authentication information;
The thin client system according to any one of claims 1, 2, and 3. A management server in a thin client system comprising a thin client terminal, a thin client server, and a management server for managing the connection between the thin client terminal and the thin client server,
Receive user authentication information from the thin client terminal, and based on the authentication information, obtain type information of a thin client server that can be used by the user and connection information that is information for connecting to the thin client server. Authentication management means for transmitting the information to the thin client terminal;
A connection module management means for transmitting a connection module file, which is connection software requested from the thin client terminal, to the thin client terminal;
A management server comprising:   The authentication management means further receives terminal information for identifying the thin client terminal from the thin client terminal, acquires the type information and the connection information based on the authentication information and the terminal information, The management server according to claim 5, wherein the information is transmitted to the thin client terminal. further,
Server state management means for managing load state information of the thin client server;
With
When the authentication management means transmits the type information and the connection information to the thin client terminal, the authentication management means obtains information on the load state of the thin client server available to the user from the server state management means, and The management server according to claim 5, wherein the information is also transmitted to the thin client terminal. further,
A usage history database means for holding a usage history indicating a time when a user starts a connection to the thin client server using the thin client terminal and a time when the connection is terminated;
With
8. The management server according to claim 5, 6 or 7, wherein the usage history of the user is extracted by searching the usage history database means based on user authentication information. A thin client terminal in a thin client system comprising a thin client terminal, a thin client server, and a management server that manages connection between the thin client terminal and the thin client server,
Server information acquisition means for transmitting user authentication information to the management server and receiving from the management server type information of available thin client servers and connection information which is information for connecting to the thin client servers When,
Server selection means for selecting a thin client server to be used, based on the type information received by the server information acquisition means;
Based on the connection information received by the server information acquisition means, a request is made to the management server for connection modules that are connection software necessary for connection with the thin client server selected by the server selection means, and acquisition is performed from the management server. A connection module calling means for starting the connection module file and connecting to the thin client server;
A thin client terminal comprising:   The thin client terminal according to claim 9, wherein the server information acquisition unit further transmits terminal information for identifying the terminal itself to the management server. When the server information acquisition unit receives information on the load state of the thin client server available to the user from the management server,
11. The thin client terminal according to claim 9, wherein the server selection unit further selects a thin client server to be used based on the load state information received by the server information acquisition unit.

Images