TWI468947B - Data managing system of thin client - Google Patents

Description

Client management system

The present invention relates to a client management system, and more particularly to a client management system that enables a client to process data while disconnected from the server.

In order to reduce costs, improve security, and facilitate management, multiple computers are generally managed in the form of a client. Traditional client computers do not have an application. They only send input such as mouse and keyboard to the server for processing, and the server returns the processing result to the client for display.

However, since the traditional client performs data processing through the network and the server, when the network fails or other reasons, the client cannot disconnect the server due to disconnection from the server. The above information is processed.

In view of the above, it is necessary to provide a client management system that enables the client to process the data and secure the data if the client is disconnected from the server.

A client management system includes a server and a client connected to the server, the client includes a storage device and a security management module, and the storage device can be used to store the server from the server to the client. The data can be processed by the client in the case of disconnecting the communication connection with the server, and the security management module securely manages the exported data.

Preferably, the server includes a user management module, and the user management module can allow the client to derive the data from the server.

Preferably, the user management module can be configured to set a time when the exported data is exported, and the security management module deletes the exported data in the client when the time when the exported data is exported exceeds the set export time.

Preferably, the server includes a marking module, and the marking module can mark the data exported by the client in the server.

Preferably, the security management module of the client includes a tag sub-module, and the tag sub-module can mark the data that is exported from the server to the client.

Preferably, the security management module of the client further includes a data control sub-module, wherein the security management module of the client determines whether the time when the data is exported exceeds the set time by the data control sub-module .

Preferably, the security management module of the client deletes the exported data by using the data control submodule.

Preferably, the security management module of the client includes an I/O control sub-module, and the security management module can limit the exported data by the I/O control sub-module by the client I/ The O interface is copied to other external storage devices.

Preferably, the server includes a password setting module, and the password setting module can be used to set a user name, a user password, and a user password for the user to access the server.

Preferably, the server includes an ID management module, and the ID management module can be used to assign an ID to a client connected to the server.

Compared with the prior art, the client management system of the present invention guides the data of the server The storage device is sent out to the client, so that the client can still process the data when the client and the server are disconnected, and the security management module ensures the security of the exported data.

100‧‧‧Client Management System

10‧‧‧ server

11‧‧‧Storage Access Management Module

13‧‧‧User Management Module

15‧‧‧ password setting module

17‧‧‧ID Management Module

19‧‧‧Marking module

30‧‧‧Client

301‧‧‧Storage device

303‧‧‧Security Management Module

31‧‧‧Marking submodules

33‧‧‧Data Control Sub-module

35‧‧‧I/O Control Submodule

50‧‧‧Network

1 is a hardware composition diagram of a preferred embodiment of the client management system of the present invention.

2 is a flow chart showing the use of one of the client management systems of the present invention.

Referring to FIG. 1, a preferred embodiment of the client management system 100 of the present invention includes a server 10 and a client 30 communicably connected to the server 10 via a network 50.

The server 10 includes a storage access management module 11, a user management module 13, a password setting module 15, an ID (IDENTIFICATION) management module 17, and a marking module 19.

The storage access management module 11 can be configured to allow or prohibit the client 30 from accessing data stored in the server 10, such as data stored in a partition of the hard disk drive, or stored in a hard disk drive. The data in a folder in a partition.

The user management module 13 can be used to set the access type of the client 30, including CHECK OUT and CHECK IN, and can be used to set the time (PERIOD) of the CHECK OUT data by the client 30. In the CHECK OUT state, the server 10 allows the client to CHECK OUT the data on the server 10 to the client 30, and the client 30 can therefore add, modify, delete, etc. the CHECK OUT data. During the set CHECK OUT time, the data that is CHECK OUT to the client 30 can be CHECK IN to the server 10 after being processed or not processed, and exceeds the set CHECK. After the OUT time, the The data of CHECK OUT to the client 30 can no longer be CHECK IN to the server 10; but in the CHECK IN state, the user does not allow CHECK OUT to the data in the server 10, but is created at the client 30. The data processed by the editor, etc. can be CHECK IN to the server 10. The password setting module 15 can be used to set a user name, a user password, and a user password for the user to access the server 10. The ID management module 17 can be used to assign an ID to the client 30 connected to the server 10, the ID including an IP (INTERNET PROTOCOL) address and the like. The tagging module 19 can be used to tag the data of the client 30 CHECK OUT in the server 10, register the information of the client 30, and process the history of the CHECK OUT data. The information of the client 30 includes the ID of the client 30, the user name, the time when the data is CHECK OUT, and the like. The processing history includes processing such as adding, deleting, and modifying data, and the time of performing the above processing.

The client 30 includes a storage device 301 and a security management module 303, which can be used to store data exported from the server 10 to the client 30. The security management module 303 includes a tag sub-module 31, a data control sub-module 33, and an I/O control sub-module 35. The tag sub-module 31 can be used to tag the data from the client 30 from the CHECK OUT in the server 10. The data control sub-module 33 can be used to determine whether the time when the data is CHECK OUT exceeds the set CHECK OUT time, and the client 30 can be used when the data is exceeded by the set time by the CHECK OUT time. The data marked by the tag sub-module 31 is deleted. The I/O control sub-module 35 can be used to restrict the marked data in the client 30 from being copied to other external storage devices by the I/O interface of the client, thereby ensuring that the CHECK OUT is queried to the client 30. The security of the information.

Please refer to FIG. 1 and FIG. 2 together. In use, the client 30 provides the service through the network 50. End 10 issues an access request. After receiving the access request from the client 30, the server 10 assigns an ID to the client 30. The storage access management module 11 sets the data that allows/disallows access by the client 30. The password setting module 15 sets the user name and access password of the client 30 when the client 30 needs to access the server 10 for a password. The user management module 13 sets the access type of the client 30. The client 30 connects to the server 10 according to the assigned ID, and logs in to the server 10 by using the user name and the access password, so that the data of the server 10 can be accessed under the set access type.

When the access type set by the user management module 13 is CHECK OUT, the user can store the accessible data CHECK OUT set by the storage access management module 11 to the client 30 and store it in the storage device 301. At this time, the tag module 19 of the server 10 and the tag sub-module 31 of the client 30 respectively mark the data, and the user management module 13 sets the CHECK OUT time. The data that is CHECK OUT to the client 30 can be processed on the client 30 even if the client 30 is disconnected from the server 10 at this time. The data control sub-module 33 of the client 30 determines whether the data is CHECK OUT time exceeds the set CHECK OUT time; if the CHECK OUT time is not exceeded, the user can process the CHECK OUT The data CHECK IN is sent to the server 10; if there is a CHECK OUT time exceeding the setting, the data of the CHECK OUT can no longer be CHECK IN to the server 10, and the data control sub-module 33 of the client 30 The data that is CHECK OUT to the client 30 will be deleted. When the access type set by the user management module 13 is CHECK IN, the user can create, edit, and the like at the client 30, and CHECK IN the data to the server 10.

In addition, when the data is CHECK OUT to the client 30, the I/O control submodule 35 will control the I/O interface of the client 30 so that the data that is CHECK OUT to the client 30 cannot be copied to other storage devices through the I/O interface.

In summary, this creation has indeed met the requirements of the invention patent, and has filed a patent application in accordance with the law. However, the above description is only a preferred embodiment of the present invention, and equivalent modifications or variations made by those skilled in the art of the present invention should be included in the following claims.

100‧‧‧Client Management System

10‧‧‧ server

11‧‧‧Storage Access Management Module

13‧‧‧User Management Module

15‧‧‧ password setting module

17‧‧‧ID Management Module

19‧‧‧Marking module

30‧‧‧Client

301‧‧‧Storage device

303‧‧‧Security Management Module

31‧‧‧Marking submodules

33‧‧‧Data Control Sub-module

35‧‧‧I/O Control Submodule

50‧‧‧Network

Claims (8)

A client management system includes a server and a client connected to the server, the client includes a storage device and a security management module, and the storage device can be used to store the server from the server to the client. Data, the client can process the exported data in a disconnected connection with the server, and the security management module securely manages the exported data, and the server includes a user management module, the user The management module may allow the client to export the data from the server, and the user management module may be configured to set a time when the exported data is exported, and the security management module exceeds the setting when the exported data is exported. Delete the exported data in the client at the time. The client management system of claim 1, wherein the server includes a marking module, and the marking module can mark the data exported by the client in the server. The client management system of claim 1, wherein the client security management module includes a tag submodule, and the tag submodule can be exported from the server to the client. The data is marked. The client management system of claim 3, wherein the security management module of the client further includes a data control sub-module, wherein the security management module of the client controls the sub-module by using the data Determine if the time the data was exported exceeds the set time. The client management system of claim 4, wherein the security management module of the client deletes the exported data by using the data control submodule. The client management system of claim 1, wherein the security management module of the client includes an I/O control sub-module, and the security management module can control the sub-module by using the I/O To limit the export data to the other external storage device by the I/O interface of the client. The client management system of claim 1, wherein the server includes a password. The setting module can be used to set the user name, user password and user password of the user accessing the server. The client management system of claim 1, wherein the server includes an ID management module, and the ID management module is configured to assign an ID to a client connected to the server.