JP2013161259A - Thin client system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a thin client system with high security which can reduce development labor and a cost, and easily deal with input of a character code in a desired use language, even when a use language of a terminal is different from a use language of an application in an application server.SOLUTION: In a thin client system 10, terminals 12a-12e are connected to an application server 20 through a virtual server unit 30. The system comprises a session management device 24 having the virtual server unit 30. The virtual server unit 30 comprises a plurality of virtual servers 32a-32c in which a thin client OS is activated. The session management device 24 comprises: a database 38 which stores first authentication information, individual connection data, a user information table 40, an application language table 42 and a conversion table 44; and a control unit 26.

Description

  The present invention relates to a thin client system in which a terminal connects to an application server via a virtual server unit.

  In recent years, with changes in work styles, thin clients have been used outside the company to realize a work environment similar to that in the company. In order to prevent leakage of in-house information and the like, a thin client using an authentication key for identifying a user is used (Patent Documents 1 and 2).

  In a server-based thin client, processing such as application execution is performed in a thin client server by remote operation from a terminal that is a thin client, and a processing result by the thin client server is displayed on the terminal (Patent Document 3). .

  Regarding input from a terminal, Patent Document 4 describes a system in which a scan code output from a keyboard is output as a character code of a desired language based on a key table for each language.

JP 2010-92240 A JP 2010-211406 A JP 2010-231430 A JP 2004-220158 A

  In the server-based thin client, it is necessary to develop an application for connecting to the server for each OS provided in the terminal or to modify the OS, and there is a problem that it takes labor and cost for development. .

  The system of Patent Document 4 is a system that enables multilingual input from a single keyboard. However, if the language used by the terminal that is the thin client is different from the language used by the application in the thin client server, the character code input to the application in the thin client server is appropriately performed even using the system of Patent Document 4. There was a problem that was not done.

  The present invention has been made in consideration of the above-mentioned problems, reduces development effort and cost, has high security, and the language used by the terminal is different from the language used by the application of the application server. Even so, an object of the present invention is to provide a thin client system that can easily cope with input of a character code in a desired language.

  The thin client system according to the present invention is a thin client system in which a terminal is connected to an application server via a virtual server unit, and includes a session management device having the virtual server unit, and the virtual server unit includes a thin client An OS includes a plurality of virtual servers, and the session management device includes first authentication information for the terminal to connect to the virtual server, and encrypted individual connection data for connection to the application server, A user information table having first usage language data of the terminal, an application language table having second usage language data for each application of the application server, and a scan code input from the terminal is used for the second usage. Change to character code corresponding to language data A database in which a conversion table is stored, and a control unit, wherein the control unit acquires second authentication information for connecting to the virtual server from the terminal, and is stored in the database The first authentication information is collated, and if they match, the terminal is allowed to connect to the virtual server, the control unit obtains a decryption password for decrypting the individual connection data from the terminal, and the database When the individual connection data stored in the terminal can be decrypted by the decryption password, the application server can be remotely operated by the terminal, and the control unit is selected from the first language used data and the terminal. When the second language data of the application is collated and does not match, the terminal is determined based on the conversion table. The scan code output from the end is converted into the character code of the second use language data and output to the application server.

  In the thin client system, the session management apparatus includes an allocation management unit that manages allocation of the virtual servers to the terminal in a round robin manner, and the session management apparatus reads the individual connection data by the terminal. A flag is set when the terminal is issued, and reading of the individual connection data from another terminal is prohibited while the terminal is connected to the virtual server.

  In the thin client system, when the terminal is a smartphone having a routing function, the terminal includes a memory that stores an application that is executed by a controller and receives an instruction from the session management device. Executes the application, receives a terminal authentication key acquisition command, which is authentication information for identifying the subscriber of the terminal, from the session management device, and transmits the terminal authentication key to the session management device, Acquired by the session management device.

  According to the thin client system of the present invention, by realizing the thin client function with a virtual server, development labor and cost are reduced, security is high, and the language of the terminal and the application server application are used. Even if the language is different, it is possible to provide a thin client system that can easily cope with input of a character code in a desired language. Furthermore, the connection of the terminal to the virtual server is verified based on the authentication information stored in the database, and when the individual connection data stored in the database can be decrypted by the decryption password, By enabling the operation, the security of the thin client system can be increased.

  The session management device sets a flag when the individual connection data is read by the terminal, and prohibits reading of the individual connection data from other terminals while the terminal is connected to the virtual server. As a result, it is possible to prevent spoofing access by an unauthorized acquirer of authentication information. Furthermore, by allocating terminals to virtual servers in a round robin manner, virtual servers can be operated efficiently.

  Furthermore, when the terminal is a smartphone having a routing function, the terminal has a memory that stores an application that is executed by the controller and receives an instruction from the session management device, and the controller executes the application The terminal management key is received from the session management apparatus, and the terminal authentication key is transmitted to the session management apparatus, and the session management apparatus acquires the terminal authentication key. Thereby, it is possible to connect to the virtual server unit using the terminal authentication key of the terminal that cannot use the AT command in communication with the session management apparatus, and to remotely control the application server.

It is explanatory drawing of the thin client system which concerns on embodiment of this invention. It is explanatory drawing of an allocation management table. 3A and 3B are explanatory diagrams of the user information table. It is explanatory drawing of an application language table. It is explanatory drawing of a conversion table. It is explanatory drawing of the process sequence of the thin client system which concerns on embodiment of this invention. FIG. 7A is an explanatory diagram of an application selection screen in English, and FIG. 7B is an explanatory diagram of an application selection screen in Japanese. It is explanatory drawing about the terminal which is a smart phone. It is explanatory drawing of the process sequence in case a terminal is a smart phone.

  Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is an explanatory diagram of a thin client system 10 according to an embodiment of the present invention, FIG. 2 is an explanatory diagram of an allocation management table 36, and FIGS. 3A and 3B are explanatory diagrams of a user information table 40. 4 is an explanatory diagram of the application language table 42, and FIG. 5 is an explanatory diagram of the conversion table 44.

<Description of Configuration of Thin Client System 10>
The thin client system 10 includes terminals 12a to 12e, a public line 14, a VPN (Virtual Private Network) 16, a firewall 18, an application server 20, and a session management device 24.

  The terminals 12a to 12e (referred to collectively as “terminal 12” as appropriate) are terminals having a communication function, and the terminal 12e is a smartphone having a routing function equipped with a general-purpose OS. The public line 14 is a public line constituted by the Internet or the like. The firewall 18 is a firewall that prevents unauthorized access to the application server 20. The application server 20 is a server that performs processing such as application execution, file input / output, and data storage. The application server 20 is provided with a firewall 18 between the public line 14 and installed in a DMZ (demilitarized zone) 22.

  The session management device 24 includes a control unit 26, a communication unit 28, a virtual server unit 30, an allocation management unit 34, and a database 38. The application server 20 and the communication unit 28 are connected by a VPN (Virtual Private Network) 16 via a firewall 18.

  The control unit 26 is a control unit that performs overall control of the session management device 24. The communication unit 28 performs communication processing with the terminal 12 and communication processing with the application server 20.

  The virtual server unit 30 includes virtual servers 32a to 32c that are activated by the thin client OS. Each of the virtual servers 32a to 32c has an IP address and can be connected to the application server 20 alone. Further, in order from the highest priority of assignment to the terminal 12, virtual server 32a> virtual server 32b> virtual server 32c.

  The allocation management unit 34 includes an allocation management table 36 and manages connection of the terminal 12 to the virtual server unit 30 based on the allocation management table 36. The allocation management table 36 stores virtual server names and virtual server allocation states. The allocation management unit 34 permits connection to the virtual server unit 30 in a round robin manner.

  The database 38 includes a user information table 40, an application language table 42, and a conversion table 44 in which information relating to whether or not the terminal 12 can be connected to the virtual server unit 30 and whether or not to connect to the application server 20 is stored. It is a prepared database.

  In the user information table 40, the user ID, the user password, the first use language data, the individual connection data, the decryption password, and the read state to the individual connection data are recorded. The user ID and the user password are authentication information (first authentication information) for connecting to the virtual server unit 30. The first used language data is data representing the type of language used in the terminal 12. The individual connection data is encrypted data such as a connection password for connecting to the application server 20. The decryption password is a password for decrypting the encryption of the individual connection data.

  As shown in FIGS. 3A and 3B, for example, for the terminal 12a, as a user ID, a user password, first use language data, individual connection data, and a decryption password, Ia, Pa, EN , Sa, Da are stored in the user information table 40. Similarly, user IDs and the like are stored in the user information table 40 for the terminals 12b to 12d. EN of the first use language data represents English, and JP represents Japanese. In addition, about the terminal 12e, there are a case where a user password is not set as described later, and a case where the same user password as the user ID is set.

  In the application language table 42, second usage language data is recorded for each application of the application server 20. The second used language data is data representing the type of language used in each of the applications A to C included in the application server 20. As shown in FIG. 4, the language used by the application A is Japanese, which is represented as JP. The language used for the application B is English, which is expressed as EN. The language used by the application C is Japanese and is expressed as JP.

  In the conversion table 44, a scan code output from the terminal 12, a character code in English corresponding to the scan code, and a character code in Japanese are recorded. In the conversion table 44, in order to facilitate understanding, each character code is represented by a character notation corresponding to a character code in English and a character notation corresponding to a character code in Japanese.

  The scan code column of the conversion table 44 represents a scan code generated by pressing the keyboard of the terminal 12 and a scan code generated when the finger is released after pressing the keyboard of the terminal 12. . For example, “16” on the left side of the slash (/) of the scan code “16 / F0 16” means a scan code generated when the keyboard of the terminal 12 is pressed. “F0 16” on the right side of the slash (/) is a scan code generated when a finger is released after pressing the keyboard of the terminal 12.

  In the English column of the conversion table 44, a scan code generated when the keyboard of the terminal 12 is pressed without pressing the Shift key, and a scan generated when the keyboard of the terminal 12 is pressed together with the Shift key. The character code in English corresponding to the code is shown. For example, the scan code “16” is converted into a character code corresponding to “1” when the keyboard is pressed without pressing the Shift key. The scan code “16” is converted into a character code corresponding to “!” When the keyboard of the terminal 12 is pressed together with the Shift key. Similarly to the English column, the Japanese column of the conversion table 44 represents a character code corresponding to the scan code corresponding to whether or not the Shift key is pressed.

  In the conversion table 44, most of the English character code and the Japanese character code for the same scan code match, but the English character code and the Japanese character code are different in some scan codes. . For example, scan codes `` 0E / F0 0E '', `` 4E / F0 4E '', `` 55 / F0 55 '', `` 6A / F0 6A '', `` 54 / F0 54 '', `` 5B / F0 5B '', `` 4C / F0 For 4C, 52 / F0 52, 5D / F0 5D, and 51 / F0 51, the English character code is different from the Japanese character code.

<Description of Operation of Thin Client System 10>
Next, the operation of the thin client system 10 will be described with reference to FIGS. 6, 7A, and 7B. 6 is an explanatory diagram of a processing procedure of the thin client system 10 according to the embodiment of the present invention, FIG. 7A is an explanatory diagram of an application selection screen in English, and FIG. 7B is an application selection screen in Japanese. It is explanatory drawing. Hereinafter, a case where the terminal 12a connects to the application server 20 will be described. The terminals 12b to 12d can be connected to the application server 20 in the same processing procedure.

  The user connects to the session management device 24 via the public line 14 by the terminal 12a (step S1). The control unit 26 of the session management device 24 uses the user ID and the authentication information (second authentication information) for connecting the terminal 12a to the virtual server unit 30 via the public line 14 from the communication unit 28. Send a request to enter the user password. The terminal 12a displays that the input is requested on the display screen. A user of the terminal 12 a inputs a user ID and a user password, and the input user ID and user password are transmitted to the session management device 24. The control unit 26 acquires a user ID and a user password as authentication information (step S2).

  The allocation management unit 34 confirms the allocation status of the virtual server unit 30 based on the allocation management table 36, and allocates one of the virtual servers 32a to 32c to the terminal 12a (step S3). The virtual servers 32a to 32c are assigned by a round robin method. That is, after confirming the allocation status of the virtual servers 32a to 32c, the allocation management unit 34 allocates virtual servers that are not allocated to the terminals 12a in the order of connection requests according to the priority of allocation. The terminal 12a is assigned to the virtual server 32a, and the assignment management table 36 stores information indicating that the terminal 12a has been assigned to the virtual server 32a (FIG. 2).

  In the present embodiment, the virtual server unit 30 includes only three virtual servers. For example, when three terminals 12 a to 12 c are connected to the virtual server unit 30, the terminal 12 d that is the fourth connection request cannot be connected to the virtual server unit 30. In such a case, after the connection of any terminal of the virtual server unit 30 is completed, the terminal 12d can connect to the terminated virtual server.

  The control unit 26 collates the user ID and user password transmitted from the terminal 12a with the user ID and user password of the terminal 12a stored in the user information table 40 of the database 38 (step S40). S4). If the user ID and the user password transmitted from the terminal 12a are Ia and Pa, respectively, the control unit 26 determines that the verification is matched (YES in step S4), and the individual connection data Sa of the terminal 12a is read. In the database 38, the user information table 40 is flagged as having read individual connection data (FIG. 3B). In FIG. 3B, the flag is written as “read”. If the user ID and the user password do not match, it is requested to input the user ID and the user password again (NO in step S4).

  Further, the control unit 26 sets a flag when the individual connection data is read out, thereby prohibiting the other terminal 12 from reading the same individual connection data while the terminal 12a is connected to the virtual server 32a. . This process can prevent spoofing access. That is, it is assumed that an unauthorized acquirer other than a regular user of the terminal 12a has illegally acquired the user ID and user password of the terminal 12a. When the unauthorized acquirer inputs and connects the user ID and user password of the terminal 12a, the processing procedure from step S1 to S3 can be advanced. However, even if the unauthorized acquirer has advanced the processing procedure from step S1 to S3, the legitimate user of the terminal 12a has already set a flag for reading the individual connection data. Prohibits reading of individual connection data by the acquirer. These processes prevent spoofing access by an unauthorized acquirer.

  Since the individual connection data Sa is encrypted, the control unit 26 transmits to the terminal 12a a request for input of a decryption password for decrypting the individual connection data Sa. The terminal 12a displays that the input is requested on the display screen. The user of the terminal 12 a inputs the decryption password and transmits it to the session management device 24. The control unit 26 collates the decryption password transmitted from the terminal 12a with the decryption password of the terminal 12a stored in the user information table 40 of the database 38 (step S5).

  If the decryption password transmitted from the terminal 12a is Da, the control unit 26 determines that the verification is matched (YES in step S5), the individual connection data Sa is decrypted, and the application is transmitted via the virtual server 32a. Use of the server 20 is permitted. By permission to use the application server 20, the terminal 12a can remotely operate the application server 20 (step S6). If the decryption passwords do not match, it is requested to input the decryption password again (NO in step S5).

  Further, when the terminal 12a stops the connection to the virtual server unit 30, the allocation of the virtual server 32a is canceled, and the flag indicating reading of the individual connection data is returned to the state before reading.

  The control unit 26 acquires EN (English) which is the first used language data of the terminal 12a from the user information table 40. The control unit 26 generates an application selection screen 46A for the application of the application server 20 that matches the first use language data (FIG. 7A), and the application selection screen 46A is displayed on the terminal 12a (step S7).

  The user of the terminal 12a selects an application to be used from the application selection screen 46A (step S8). When the user of the terminal 12a selects the application A, the terminal 12a transmits information indicating that the application A has been selected from the application selection screen 46A to the control unit 26.

  The control unit 26 collates the first usage language data of the terminal 12a with the second usage language data of the application language table 42 corresponding to the information indicating that the application A transmitted from the terminal 12a has been selected (step S9). ).

  While the first use language data of the terminal 12a is EN, the second use language data of the application language table 42 corresponding to the information indicating that the application A has been selected does not match because it is JP (step S9 NO). . If the first use language data does not match the second use language data, the control unit 26 reads the conversion table 44 (step S10). The control unit 26 converts the scan code output from the terminal 12 a from English to Japanese character code based on the conversion table 44 and transmits it to the application server 20. The application A of the application server 20 performs processing based on the character code transmitted to the application server 20 (step S11).

  On the other hand, if the first usage language data of the terminal 12a matches the second usage language data of the application language table 42 corresponding to the information indicating that the application A transmitted from the terminal 12a is selected, the control unit 26 does not read the conversion table 44 (step S9 YES). For example, it is assumed that the user of the terminal 12a selects the application B from the application selection screen 46A as an application. The first usage language data of the terminal 12a is EN, whereas the second usage language data of the application language table 42 corresponding to the information of the application B is EN and matches. In this case, the control unit 26 does not read the conversion table 44, and the scan code output from the terminal 12a is transmitted to the application server 20 as it is and processed in the application B of the application server 20 (step S11).

  Next, a case where the user uses the terminal 12b will be described. In the case of the terminal 12b, the process from step S1 to S6 is the same as that of the terminal 12a. Step S7 and subsequent steps are as follows. The control unit 26 acquires JP which is the first language data of the terminal 12b from the user information table 40. The control unit 26 generates an application selection screen 46B for the application of the application server 20 that matches the first use language data (FIG. 7B), and the application selection screen 46B is displayed on the terminal 12b (step S7).

  The user of the terminal 12b selects the application B as an application to be used from the controller 48B (Step S8). The terminal 12b transmits information indicating that the application B selected from the application selection screen 46B has been selected to the control unit 26 (step S8).

  The control unit 26 collates the first usage language data of the terminal 12b with the second usage language data of the application language table 42 corresponding to the information indicating that the application B transmitted from the terminal 12b has been selected (step S9). ).

  While the first use language data of the terminal 12b is JP, the second use language data of the application language table 42 corresponding to the information indicating that the application B has been selected is EN and therefore does not match (NO in step S9). . Since the first use language data does not match the second use language data, the control unit 26 reads the conversion table 44 (step S10). The control unit 26 converts the scan code input from the terminal 12 b from Japanese into English character code according to the conversion table 44 and transmits it to the application server 20. Application B of application server 20 performs processing based on the character code transmitted to application server 20 (step S11).

  It is assumed that the user of the terminal 12b has selected the application A from the application selection screen 46B as an application. The first usage language data of the terminal 12b is JP, whereas the second usage language data of the application language table 42 corresponding to the information indicating that the application A is selected is JP and matches. In this case, the control unit 26 does not read the conversion table 44, and the scan code output from the terminal 12b is transmitted to the application server 20 as it is and processed in the application A of the application server 20 (step S11).

  Next, a case where the terminal 12e connects to the application server 20 will be described. When a smartphone is used as the terminal, the authentication key stored in the portable terminal cannot be acquired from the external device. This is because a smartphone cannot perform control using an AT command from an external device such as a thin client.

  FIG. 8 is an explanatory diagram of the terminal 12e that is a smartphone, and FIG. 9 is an explanatory diagram of a processing procedure when the terminal is a smartphone.

  The terminal 12 e includes a controller 48, a USIM (Universal Subscriber Identity Module) 50, and a memory 54.

  The controller 48 is a control unit that performs overall control of the terminal 12e. The USIM 50 is a memory module in which a terminal authentication key 52, which is unique subscriber information for identifying a subscriber of the terminal 12e such as a telephone number, is stored. The memory 54 stores an application 52 that is executed by the controller 48 and receives a command from the session management device 24 by the smartphone 42. The application 52 is, for example, a java application written in the java language.

  First, in the terminal 12e, the application 56 in the memory 54 is executed by the controller 48 (step S21). By executing the application 56, it becomes possible for the terminal 12e to accept a command from the session management device 24, and a state in which activation of the daemon is permitted is formed.

  The user connects to the session management device 24 via the public line 14 by the terminal 12e (step S22).

  The control unit 26 transmits an instruction requesting the terminal authentication key 52 of the terminal 12e to the terminal 12e. Since the application 56 is executed on the terminal 12e, the controller 48 can accept a command from the control unit 26. The controller 48 receives the command and starts a daemon for acquiring the terminal authentication key 52. The controller 48 executes the started daemon, acquires the terminal authentication key 52 from the USIM 50, and transmits it to the session management device 24. The control unit 26 receives the terminal authentication key 52, and the acquisition is completed (step S23).

  Hereafter, Step S24 is basically the same as Step S3 described above, and Steps S25 to S32 are processed in the same manner as Steps S4 to S11, respectively.

  However, in step S25, part of the processing procedure is different from step S4. The terminal authentication key 52 of the terminal 12e is treated as a user ID in the user information table 40. Here, since the terminal authentication key 52 is unique, the user password of the terminal 12e is not set in the user information table 40. Accordingly, in step S4, if the user ID stored in the user information table 40 matches the authentication key 46, the authentication information is determined to match.

  When the terminal 12 is a smartphone, the terminal authentication key 52 is unique, and therefore the user ID and the user password may be set to be the same in the user information table 40. In such a case, the terminal authentication key 52 is handled as a user ID and a user password, and collation processing is performed.

  As described above, the thin client system 10 is the thin client system 10 in which the terminal 12 is connected to the application server 20 via the virtual server unit 30, and includes the session management apparatus 24 having the virtual server unit 30. The virtual server unit 30 includes a plurality of virtual servers 32a to 32c that are activated by the thin client OS. The session management device 24 uses the first authentication information for the terminal 12 to connect to the virtual servers 32 a to 32 c, the encrypted individual connection data for connecting to the application server 20, and the first use language data of the terminal 12. The user information table 40, the application language table 42 having the second used language data for each application of the application server 20, and the scan code input from the terminal 12 is converted into a character code corresponding to the second used language data. The database 38 in which the conversion table 44 to be stored is stored, and the control unit 26. The control unit 26 acquires the second authentication information for connecting to the virtual servers 32 a to 32 c from the terminal 12, collates with the first authentication information stored in the database 38, and if they match, the virtual server of the terminal 12 Connection to 32a-32c is permitted. In addition, when the control unit 26 obtains a decryption password for decrypting the individual connection data from the terminal 12 and the individual connection data stored in the database 38 can be decrypted by the decryption password, the application server 20 by the terminal 12 Remote control of the system is possible. Further, the control unit 26 collates the first used language data with the second used language data of the application 56 selected from the terminal 12, and when the data does not match, the control unit 26 outputs the data from the terminal 12 based on the conversion table 44. The scan code is converted into the character code of the second usage language data and output to the application server 20.

  According to the thin client system 10, by realizing the thin client function with the virtual servers 32a to 32c, development labor and cost are reduced, security is high, and the language of the terminal and the application server application Even if the language used is different, it is possible to provide a thin client system that can easily cope with input of a character code in a desired language. When the connection of the terminal 12 to the virtual servers 32a to 32c is verified based on the authentication information stored in the database 38, and the individual connection data stored in the database 38 can be decrypted by the decryption password, By enabling remote control of the application server 20 by the terminal 12, the security of the thin client system can be increased.

  The virtual server unit 30 also has a role as a relay server that relays between the terminal 12 and the application server 20. Furthermore, each of the virtual servers 32a to 32c is a virtual server that is started by the thin client OS and functions as a thin client.

  The session management device 24 also has an allocation management unit 34 that manages allocation of the virtual servers 32a to 32c to the terminal 12 in a round robin manner, and sets a flag when the individual connection data is read by the terminal 12. During the connection of the terminal 12 to the virtual servers 32a to 32c, reading of individual connection data from other terminals 12 is prohibited. As a result, it is possible to prevent spoofing access by an unauthorized acquirer of authentication information. Further, by assigning the terminal 12 to the virtual servers 32a to 32c by the round robin method, the virtual servers 32a to 32c can be efficiently operated.

  Further, when the terminal 12 is a smartphone having a routing function, the terminal 12 includes a memory 54 that stores an application that is executed by the controller 48 and receives an instruction from the session management device 24. An application that accepts a command from the session management device 24 is executed, a command for obtaining a terminal 12 authentication key, which is authentication information for identifying a subscriber of the terminal 12, is received from the session management device 24, and the terminal 12 authentication key is assigned to the session management device. 24 and is acquired by the session management device 24. As a result, it is possible to connect to the virtual server unit 30 using the terminal authentication key 52 of the terminal 12e that cannot use the AT command in communication with the session management device 24, and to remotely control the application server 20. be able to.

  It should be noted that the present invention is not limited to the above-described embodiment, and various configurations can be adopted without departing from the gist of the present invention.

  For example, in the thin client system 10, the terminal 12 includes five terminals 12 a to 12 e and the virtual server unit 30 includes three virtual servers 32 a to 32 c. However, if the number of terminals 12 is equal to or greater than the number of virtual servers, It is not limited to this.

  The application server 20 includes three types of applications, but the types are not limited.

  The conversion table 44 is a conversion table for converting between English and Japanese, but is not limited to an English and Japanese conversion table. A conversion table for converting between other languages, such as a conversion table between Japanese and Chinese, may be used.

10 ... Thin client systems 12a to 12e ... Terminal 14 ... Public line 16 ... VPN
18 ... Firewall 20 ... Application server 22 ... DMZ
24 ... Session management device 26 ... Control unit 28 ... Communication unit 30 ... Virtual server units 32a to 32c ... Virtual server 34 ... Assignment management unit 36 ... Assignment management table 38 ... Database 40 ... User information table 42 ... Application language table 44 ... Conversion table 46 ... Application selection screen 48 ... Controller 50 ... USIM
52 ... Terminal authentication key 54 ... Memory 56 ... Application

Claims (3)

A thin client system in which a terminal connects to an application server via a virtual server unit,
A session management device having the virtual server unit;
The virtual server unit includes a plurality of virtual servers that are started by a thin client OS,
The session management device includes:
A user information table having first authentication information for the terminal to connect to the virtual server, encrypted individual connection data for connection to the application server, and first usage language data of the terminal; A database in which an application language table having second usage language data for each application in the application server and a conversion table for converting a scan code input from the terminal into a character code corresponding to the second usage language data are stored. When,
A control unit;
With
The control unit acquires second authentication information for connecting to the virtual server from the terminal, collates with the first authentication information stored in the database, and if the two match, the virtual server of the terminal Allow connection to
When the control unit obtains a decryption password for decrypting the individual connection data from the terminal, and the individual connection data stored in the database can be decrypted by the decryption password, the application by the terminal Enables remote operation of the server,
The control unit collates the first usage language data with the second usage language data of the application selected from the terminal, and when the data does not match, is output from the terminal based on the conversion table A thin client system, wherein a scan code is converted into the character code of the second usage language data and output to the application server. The thin client system according to claim 1,
The session management device has an allocation management unit that manages allocation of the virtual servers to the terminal in a round robin manner,
The session management device sets a flag when the individual connection data is read by the terminal, and prohibits reading of the individual connection data from other terminals while the terminal is connected to the virtual server. Thin client system characterized by The thin client system according to claim 1 or 2,
When the terminal is a smartphone having a routing function,
The terminal includes a memory in which an application that is executed by a controller and receives an instruction from the session management device is stored;
The controller executes the application, receives a terminal authentication key acquisition command, which is authentication information for identifying a subscriber of the terminal, from the session management apparatus, and transmits the terminal authentication key to the session management apparatus And the session management device obtains the thin client system.

Images