JP2009181458A - Thin client system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To continue an operation even when communication with a server is temporarily disconnected, and to prevent a waiting time from occurring during communication. <P>SOLUTION: A portable terminal 10 as a client terminal and a server 50 communicate through a communication network 40. The server 50 is provided with a storage device 70 storing secure data 702 to be secured at least. The portable terminal 10 includes: a temporary storage device 30 for temporarily storing data; a cache memory 302 installed in the temporary storage device 30; and an information processor 20 including a reading/writing means 202 for reading/writing data for the cache memory 302 and reading/writing data for the server 50 for starting a secure application 201 for handing the secure data 301, reading secure data 702 stored in a storage device 70 of the server 50 through the communication network 40 by the reading/writing means 202, and temporarily storing the secure data in the cache memory 302. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a thin client system in which a client terminal and a server communicate via a communication network, a communication method for the thin client system, and a thin client terminal.

  In recent years, with the widespread use of mobile terminals (client terminals), there is an increasing demand for executing applications on mobile terminals. On the other hand, there are many cases where secure data is stored in a portable terminal and lost and information is leaked, and the demand for thin client systems is increasing.

  Here, secure data refers to data that has a high risk of leakage such as corporate secret information and personal information and requires security considerations. A thin client system is a type of client server system that executes an application program on a server and performs the operation from a portable terminal.

  For example, Patent Document 1 (Japanese Patent Application Laid-Open No. 2005-228227) and Patent Document 2 (Japanese Patent Application Laid-Open No. 2007-346687) propose a thin client terminal, but both applications are executed on the server side. Since the user's operation and the drawing portion on the screen are communicated with the portable terminal via the network, the operation becomes impossible when communication with the server is disconnected.

  In order to enable the operation of the terminal when communication with the server is disconnected, it is necessary to create a mechanism for storing operation contents as in Patent Document 2.

JP 2005-228227 A JP 2007-34687 A

  Therefore, the present invention has been made in view of the above-described problems of the prior art, and its purpose is to enable the operation to be continued even when communication with the server is temporarily interrupted, and to perform operation by communication. It is to make it difficult to generate the waiting time.

In order to achieve the above object, the present invention provides a thin client system in which a client terminal and a server communicate with each other via a communication network,
The server
It has a storage device that stores secure data that needs at least security considerations,
The client terminal
A temporary storage device for temporarily storing data;
A cache memory provided in the temporary storage device;
Including read / write means for reading / writing data to / from the cache memory and reading / writing data to / from the server, operating a secure application for handling the secure data, and storing the server by the read / write means And an information processing device that reads secure data stored in the device via a communication network and temporarily stores the data in a cache memory.

Further, in the present invention, a communication method of a thin client system in which a client terminal and a server communicate via a communication network,
The server storage device stores at least secure data that requires security considerations,
The client terminal operates a secure application for handling the secure data, reads the secure data stored in the storage device of the server via the communication network, and temporarily stores it in the cache memory.

Further, in the present invention, a thin client terminal that communicates via a communication network with a server having a storage device that stores secure data that requires at least security considerations,
A temporary storage device for temporarily storing data;
A cache memory provided in the temporary storage device;
Including read / write means for reading / writing data to / from the cache memory and reading / writing data to / from the server, operating a secure application for handling the secure data, and storing the server by the read / write means And an information processing device that reads secure data stored in the device via a communication network and temporarily stores the data in a cache memory.

  According to the present invention, the operation can be continued even when communication with the server is temporarily disconnected. Further, it is possible to make it difficult for the waiting time for the operation by communication to occur, and to provide the user with an operation feeling without being aware of communication.

  Next, embodiments of the present invention will be described in detail with reference to the drawings.

(First embodiment)
FIG. 1 is an overall configuration diagram of a thin client system according to a first embodiment of the present invention.

  The thin client system according to the first embodiment includes a mobile terminal 10 as a client terminal, a communication network 40, and a server 50.

  The mobile terminal 10 includes an information processing device 20 and a temporary storage device 30. The temporary storage device 30 stores secure data 301 and has a cache memory 302.

  In the information processing apparatus 20, software such as an operating system and an application operates. Further, the information processing apparatus 20 includes a secure application (hereinafter referred to as a secure application 201), a data reading / writing unit 202, and a communication unit 203.

  On the other hand, the server 50 includes an information processing device 60 and a storage device 70. The information processing apparatus 60 includes a communication unit 601 and a data reading / writing unit 602. The storage device 70 has a file for storing the secure data 701 and a file for storing the secure application 702. The communication network 40 is a wired or wireless communication network.

  Here, the secure data 301 and 702 refer to data that has a high risk of leakage such as corporate secret information and personal information and requires security considerations. Secure applications 201 and 701 are applications for handling secure data 301 and 702. The application main body is stored in the storage device 70 in the server 50. When the application main body is activated by a user operation from a menu screen (not shown) of the mobile terminal 10, it is read and activated via the communication network 40.

  After being activated, the secure application 201 performs authentication for confirming whether the user is an authorized user. The authentication method uses any authentication means possessed by the portable terminal 10, but it is desirable to use biometric authentication such as fingerprint authentication and face authentication, which is easy for the user to operate and has high authentication accuracy. Furthermore, in order to avoid being misused when lost or stolen, the secure application 201 is automatically terminated when there is no operation for a certain period of time.

  The data reading / writing unit 202 performs data reading / writing processing on the cache memory 302 and data reading / writing processing on the server 50. As described above, the data reading / writing unit 202 provides an interface when the secure application 201 reads information on the server 50.

  Data once read is automatically stored in the cache memory 302 by the data reading / writing means 202. When there is a next read request, data is read from the cache memory 302. When there is a data write request, the data is once written on the cache memory 302, and the process is immediately returned to the application, and the reflection (data transfer) to the server 50 is performed asynchronously. In this way, it is possible to improve the data access performance and continue the operation when temporarily disconnecting communication. However, the cache memory 302 is automatically cleared when the disconnected state continues for a certain period of time in order to avoid being misused when lost or stolen.

  The communication unit 203 communicates with the communication unit 601 on the server 50 via the communication network 40. Encryption is performed before data is sent to the communication network 40 to ensure confidentiality of communication contents. Decode when receiving data.

  The temporary storage device 30 is a volatile storage device, and all data is erased when the power is turned off. The temporary storage device 30 includes a cache memory 302 that stores secure data 301 handled by the secure application 201 and stores the data once read by the data reading / writing unit 202 for reuse.

  The role of the server 50 is to store the secure application 701 and secure data 702 used by the mobile terminal 10, and send them using the read communication means 601 via the data read / write means 602 according to a request from the mobile terminal 10. In addition, the data transmitted from the portable terminal 10 in response to the write request is stored in the storage device 70.

  The communication unit 601 transfers the data received from the mobile terminal 10 to the data reading / writing unit 602. In addition, the data received from the data reading / writing unit 602 is transmitted to the mobile terminal 10. Decryption is performed when data is received, and encryption is performed before data is sent to the communication network 40 to ensure confidentiality of communication contents.

  The data reading / writing unit 602 receives a data reading request from the secure application 201 of the mobile terminal 10, reads the requested data from the storage device 70, and transmits it to the secure application 201 of the mobile terminal 10. Further, it receives a data storage request from the secure application 201 of the mobile terminal 10 and stores the received data in the storage device 70. The storage device 70 stores secure data 702 and a secure application 701 used by the mobile terminal 10.

  Next, the operation of the first embodiment of the present invention will be described in detail with reference to FIG. 1 and FIG. Here, FIG. 2 is a flowchart showing an operation focusing on data processing from the start of the secure application to the operation by the user and the end of the secure application.

  First, when the user selects activation of the secure applications 201 and 701 from the menu screen, the data reading / writing unit 202 is instructed to read the main body files of the secure applications 201 and 701 (step 201).

  Next, the data reading / writing unit 202 determines whether or not the main body files of the secure applications 201 and 701 exist in the cache memory 302 (step 202).

  As a result of the determination, if it exists in the cache memory 302 (cache hit), the process proceeds to step 204 as it is. On the other hand, as a result of the determination, if the cache memory 302 does not exist, the file of the main body of the secure application 701 is read from the server 50 via the communication network 40 and stored in the cache memory 302 (step 203).

  In step 204, the secure application 201 is read from the cache memory 302, and in step 205, the secure application 201 is activated.

  After the secure application 201 is activated, the process branches according to a user operation (step 206).

  First, when the user performs a data reading operation, the secure application 201 instructs the data reading / writing unit 202 to read data, and it is determined whether the data to be read exists in the cache memory 302 ( Step 207).

  As a result of the determination, if it exists in the cache memory 302 (cache hit), the process proceeds to step 209 as it is. On the other hand, as a result of the determination, if it does not exist in the cache memory 302, the target data is read from the server 50 and stored in the cache memory 302 (step 208). In step 209, the data is read from the cache memory 302 and passed to the secure application 201.

  If the user performs a data write operation in step 206, the secure application 201 instructs the data read / write means to write 202 data, and determines whether the write target data exists in the cache memory 302. (Step 210).

  As a result of the determination, if it exists in the cache memory 302 (cache hit), the process proceeds to step 212 as it is. On the other hand, as a result of the determination, if the cache memory 302 does not exist, the target data is read from the server 50 and stored in the cache memory 302.

  In step 212, the data is written to the cache memory 302, and the secure application 201 is notified of the completion of writing. Data written to the cache memory 302 is reflected (transferred) to the server 50 asynchronously.

  If an application termination operation is performed in step 206, all data written in the cache memory 302 is reflected on the server 50 and the application is terminated (step 213). In this way, the changed data in the cache memory 302 is reflected on the server 50.

  With the above operation, when the target data to be read / written exists in the cache memory 302, communication does not occur during the user's operation. Therefore, the operation can be continued even when the communication is temporarily disconnected. .

  When the target data does not exist in the cache memory 302 or when the data is reflected asynchronously after writing to the server 50, if the communication is disconnected, it is necessary to connect to the server 50. In this case, since the connection to the server 50 is automatically performed, the user can operate without being aware of the temporary disconnection of communication.

  The first embodiment has the following effects.

  First, by always passing through the cache memory 302 in the data read / write processing to the server 50, it is possible to provide the user with an operational feeling that is not conscious of communication.

  Secondly, the secure data 702 is managed on the server 50 side, held only in the temporary storage device 30 on the portable terminal 10 side, and devised timing for erasure, so that the secure data 301 is lost when the portable terminal 10 is lost or stolen. Leakage can be prevented.

  Thirdly, by concealing the process of reading the secure data 702 from the server 50 below the file system, the application development method may be the same as the existing one, and there is a development advantage that the existing application can be easily diverted.

  Fourth, when an application version upgrade occurs, it is not necessary to make settings for each portable terminal 10, and only the application main body stored in the server 50 needs to be updated.

(Second embodiment)
Next, a second embodiment of the present invention will be described. FIG. 3 is an overall configuration diagram of a thin client system according to the second embodiment of the present invention.

  In the first embodiment shown in FIG. 1, both the secure application 701 and the secure data 702 are stored in the storage device 70 of the server 50. On the other hand, in the second embodiment, only the secure data 702 is stored in the storage device 70 of the server 50, and the secure application 201 is stored in the mobile terminal 10. Since the other configuration is the same as that of the first embodiment, the description thereof is omitted. According to the second embodiment, the waiting time when starting up the secure application 201 is reduced as compared with the first embodiment.

(Third embodiment)
Next, a third embodiment of the present invention will be described. FIG. 4 is an overall configuration diagram of a thin client system according to the third embodiment of the present invention.

  In the third embodiment, unlike the first embodiment, not only the secure application 701 and the secure data 702 but also all software 703 including the operating system of the mobile terminal 10 is stored in the storage device 70 of the server 50. . Then, the entire software 703 of the mobile terminal 10 is read from the server 50 via the communication network 40 when the mobile terminal 10 is activated. Since the other configuration is the same as that of the first embodiment, the description thereof is omitted.

  According to the third embodiment, since no area for storing software is required on the mobile terminal 10 side, the manufacturing cost of the mobile terminal 10 is reduced. Further, all software including the operating system can be updated without setting on the mobile terminal 10 side.

  As described above, in the embodiment of the present invention, the secure data 301 and 702 are not stored permanently on the mobile terminal 10 side but managed by the server 50 and downloaded to the mobile terminal 10 as necessary, thereby leaking information. A high level of security is achieved.

  The data once read from the server 50 is stored in the cache memory 302 in the temporary storage device 30 on the portable terminal 10 side and reused at the next read time, and once written to the cache memory 302 when the data is updated. The reflection to the server 50 is performed asynchronously. Thereby, the waiting time of the operation by communication hardly occurs, and the user can operate the mobile terminal 10 without being aware of the communication.

  Further, since the application is executed on the mobile terminal 10 side, even if the connection with the server 50 is temporarily disconnected, the user can continue the operation without being aware of it.

  Although the invention made by the present inventor has been specifically described based on the embodiments, it is needless to say that the present invention is not limited to the above embodiments and can be variously modified without departing from the gist thereof. Yes.

  For example, portable terminals as thin client terminals described in the above embodiments widely include mobile phones, smartphones, PDAs, notebook computers, desktop computers, and the like.

1 is an overall configuration diagram of a thin client system according to a first embodiment of the present invention. It is a flowchart which shows operation | movement of the 1st Example of this invention. It is a whole block diagram of the thin client system which concerns on 2nd Example of this invention. It is a whole block diagram of the thin client system which concerns on the 3rd Example of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Mobile terminal 20 Information processing apparatus 30 Temporary storage apparatus 40 Communication network 50 Server 60 Information processing apparatus 70 Storage apparatus 201 Secure application 202 Data reading / writing means 203 Communication means 301 Secure data 302 Cache memory 601 Communication means 602 Data reading / writing means 701 Secure application 702 Secure data 703 All software

Claims (24)

A thin client system in which a client terminal and a server communicate via a communication network,
The server
It has a storage device that stores secure data that needs at least security considerations,
The client terminal
A temporary storage device for temporarily storing data;
A cache memory provided in the temporary storage device;
Including read / write means for reading / writing data to / from the cache memory and reading / writing data to / from the server, operating a secure application for handling the secure data, and storing the server by the read / write means A thin client system comprising: an information processing device that reads secure data stored in the device via a communication network and temporarily stores the data in a cache memory.   The thin client system according to claim 1, wherein the read / write unit reads the secure data from the cache memory when there is a read request.   The read / write means temporarily writes the secure data in the cache memory when a write request is made, and asynchronously transfers the changed secure data to the server. The thin client system according to claim 1.   4. The thin client system according to claim 1, wherein the information processing apparatus deletes secure data stored in the cache memory at a predetermined timing. 5.   The thin client system according to claim 4, wherein the predetermined timing is a timing at which a disconnected state between the client terminal and the server continues for a predetermined time. The temporary storage device is volatile;
The thin client system according to claim 4, wherein the predetermined timing is a timing when the power of the client terminal is turned off. The storage device of the server stores the secure data and the secure application,
The reading / writing means of the client terminal reads the secure application and secure data stored in the storage device of the server via a communication network, and temporarily stores the read secure application and secure data in the cache memory The thin client system according to claim 1, wherein:   The storage device of the server further stores software executed by the client terminal, and the software is read into the client terminal via the communication network when the client terminal is activated. The thin client system according to any one of 1 to 7. A communication method of a thin client system in which a client terminal and a server communicate via a communication network,
The server storage device stores at least secure data that requires security considerations,
The client terminal operates a secure application for handling the secure data, reads the secure data stored in the storage device of the server via the communication network, and temporarily stores it in the cache memory Thin client system communication method. When there is a request to read the secure data, it is determined whether the secure data exists in the cache memory,
If not present in the cache memory, the secure data is read from the server and stored in the cache memory;
The communication method of the thin client system according to claim 9, wherein the secure data is read from the cache memory when it exists in the cache memory. If there is a write request for the secure data, determine whether the secure data exists in the cache memory,
If not present in the cache memory, the secure data is read from the server and stored in the cache memory;
If present in the cache memory, the secure data is written to the cache memory;
The thin client system communication method according to claim 9, wherein the changed secure data in the cache memory is asynchronously transferred to the server.   12. The thin client system communication method according to claim 9, wherein the secure data stored in the cache memory is erased at a predetermined timing.   13. The thin client system communication method according to claim 12, wherein the predetermined timing is a timing at which a disconnection state between the client terminal and the server continues for a predetermined time.   13. The communication method of a thin client system according to claim 12, wherein the predetermined timing is a timing when the power of the client terminal is turned off. The storage device of the server stores the secure data and the secure application,
The client terminal reads a secure application and secure data stored in a storage device of the server via a communication network, and temporarily stores the read secure application and secure data in the cache memory. The communication method of the thin client system according to claim 9. Determining whether the secure application exists in the cache memory;
If present in the cache memory, read the secure application from the cache memory;
The communication method of the thin client system according to claim 15, wherein, when the cache application does not exist, the secure application is read from the server. A thin client terminal that communicates via a communication network with a server having a storage device that stores secure data that requires at least security considerations,
A temporary storage device for temporarily storing data;
A cache memory provided in the temporary storage device;
Including read / write means for reading / writing data to / from the cache memory and reading / writing data to / from the server, operating a secure application for handling the secure data, and storing the server by the read / write means A thin client terminal comprising: an information processing device that reads secure data stored in the device via a communication network and temporarily stores the data in a cache memory.   18. The thin client terminal according to claim 17, wherein the reading / writing unit reads the secure data from the cache memory when there is a reading request.   The read / write means temporarily writes the secure data in the cache memory when a write request is made, and asynchronously transfers the changed secure data to the server. The thin client terminal according to claim 17.   The thin client terminal according to any one of claims 17 to 19, wherein the information processing apparatus deletes secure data stored in the cache memory at a predetermined timing.   21. The thin client terminal according to claim 20, wherein the predetermined timing is a timing at which a disconnected state between the client terminal and the server continues for a predetermined time. The temporary storage device is volatile;
21. The thin client terminal according to claim 20, wherein the predetermined timing is a timing when the power of the client terminal is turned off. The storage device of the server stores the secure data and the secure application,
The reading / writing means of the client terminal reads the secure application and secure data stored in the storage device of the server via a communication network, and temporarily stores the read secure application and secure data in the cache memory The thin client terminal according to any one of claims 17 to 22, characterized by:   The storage device of the server further stores software executed by the client terminal, and the software is read into the client terminal via the communication network when the client terminal is activated. The thin client terminal according to any one of 17 to 23.

Images