A database access method and system

Abstract

The present invention is applicable to the field of data access technology, and provides a database access method and system, the method comprising the following steps: receiving data access information sent by a user terminal; determining the classification of data to be accessed; when the data to be accessed is primary data, allowing the data to be accessed to be accessed by the user terminal; when the data to be accessed is secondary data, when the user account is in a logged-in state on the user terminal, allowing the data to be accessed to be accessed by the user terminal; when the data to be accessed is tertiary data, reading the device ID information of the user terminal logged in by the user account, verifying the device ID information of the user terminal through the device ID information bound to the user account, and allowing the data to be accessed to be accessed by the user terminal when the verification is passed. In the present invention, only when the logged-in device is consistent with the device bound to the user account, the tertiary data can be read, ensuring that confidential information will not be leaked.

Description

Technical Field

[0001] The present invention relates to the technical field of data access, and in particular to a database access method and system. Background Art

[0002] At present, databases have become the main attack targets of hackers. Databases store a large amount of valuable and confidential information. Therefore, ensuring the security of databases has become an increasingly important task. Under the CS architecture, the client and the database are generally connected by communication. The common method is that the user enters his or her own username and password to log in to the user account. After verification, the data in the database can be read and accessed. However, since the client is placed on the client's local machine, especially now most CS architectures are developed based on interpreted languages ​​such as C# or JAVA, which are easy to be decompiled. Once important information such as the account and password connected to the database is cracked, it will cause major security problems and cause significant losses. Therefore, it is necessary to provide a database access method and system to solve the above problems. Summary of the invention

[0003] In view of the deficiencies in the prior art, the object of the present invention is to provide a database access method and system to solve the problems existing in the above-mentioned background technology.

[0004] The present invention is implemented in this way: a database access method, the method comprising the following steps:

[0005] Receiving data access information sent by a user terminal;

[0006] Determine the classification of the data to be accessed through the data access information;

[0007] When the data to be accessed is primary data, directly allowing the data to be accessed to be accessed by the user terminal;

[0008] When the data to be accessed is secondary data, checking the login status of the user terminal, and when the user account is in the login status on the user terminal, allowing the data to be accessed to be accessed by the user terminal;

[0009] When the data to be accessed is level 3 data, the device ID information of the user terminal logged in by the user account is read, and the device ID information of the user terminal is verified through the device ID information bound to the user account. If and only if the verification is successful, the data to be accessed is allowed to be accessed by the user terminal, and there are at least two device ID information bound to one user account.

[0010] As a further solution of the present invention: the method further includes binding the device ID information, specifically:

[0011] Send a device ID information binding request through a user terminal;

[0012] Check whether the corresponding user account has device ID information bound;

[0013] When the corresponding user account has no device ID information bound to it, read the device ID information of the user terminal, and obtain the device ID information of the device when the user account is registered, and send a device ID information binding instruction to the user terminal if and only if the two device ID information are consistent;

[0014] When the corresponding user account has bound device ID information, the device ID information of the user terminal is read, and the device ID information of the user terminal is verified by the bound device ID information. If and only if the verification is successful, a device ID information binding instruction is sent to the user terminal;

[0015] The device ID information binding feedback information sent by the user terminal is received, wherein the device ID information binding feedback information includes the device ID information that needs to be bound.

[0016] As a further solution of the present invention: the method further includes unbinding the device ID information, specifically:

[0017] When one of the device ID information needs to be unbound, a device ID information unbinding request is sent through the user terminal;

[0018] Read the device ID information of the user terminal logged in by the user account, verify the device ID information of the user terminal through the bound device ID information, and send a device ID information unbinding instruction to the user terminal if and only if the verification passes;

[0019] The device ID information unbinding feedback information sent by the user terminal is received, wherein the device ID information unbinding feedback information includes the device ID information that needs to be unbinded.

[0020] As a further solution of the present invention: the step of sending a device ID information unbinding instruction to the user terminal specifically includes:

[0021] Verify the number of device ID information bound to the user account;

[0022] When the number of bound device ID information is two, a device ID information unbinding instruction is sent to the user terminal, wherein the device ID information unbinding instruction includes the device information to be re-bound;

[0023] When the number of bound device ID information is greater than two, a device ID information unbinding instruction is sent to the user terminal, wherein the device ID information unbinding instruction does not include device information to be re-bound.

[0024] As a further solution of the present invention: the method further includes enabling the user account to automatically log out, specifically:

[0025] When the device ID information is unbound successfully, verifying the device ID information of the user terminal;

[0026] When the device ID information of the user terminal is unbound device ID information, the user account is automatically logged out.

[0027] Another object of the present invention is to provide a database access system, the system comprising:

[0028] A data access receiving module, used for receiving data access information sent by a user terminal;

[0029] An access data classification module, used to determine the classification of the data to be accessed through the data access information;

[0030] a first access permission module, which directly allows the data to be accessed to be accessed by the user terminal when the data to be accessed is primary data;

[0031] a second access permission module, which checks the login status of the user terminal when the data to be accessed is secondary data, and allows the data to be accessed to be accessed by the user terminal when the user account is in the login status on the user terminal; and

[0032] The third access permission module, when the data to be accessed is level 3 data, reads the device ID information of the user terminal logged in by the user account, verifies the device ID information of the user terminal through the device ID information bound to the user account, and allows the data to be accessed to be accessed by the user terminal only when the verification is passed, and the number of device ID information bound to one user account is at least two.

[0033] As a further solution of the present invention: the system further includes a device ID information binding module, and the device ID information binding module includes:

[0034] A binding request unit, sending a device ID information binding request through a user terminal;

[0035] A binding verification unit, used to verify whether the corresponding user account has been bound to the device ID information;

[0036] a binding instruction sending unit, which reads the device ID information of the user terminal and obtains the device ID information of the device when the user account is registered, when the corresponding user account has no bound device ID information, and sends a device ID information binding instruction to the user terminal if and only if the two device ID information are consistent; reads the device ID information of the user terminal when the corresponding user account has bound device ID information, verifies the device ID information of the user terminal through the bound device ID information, and sends a device ID information binding instruction to the user terminal if and only if the verification is successful; and

[0037] The binding feedback information receiving unit is used to receive device ID information binding feedback information sent by a user terminal, wherein the device ID information binding feedback information includes device ID information that needs to be bound.

[0038] As a further solution of the present invention: the system further includes a device ID information unbinding module, and the device ID information unbinding module includes:

[0039] An unbinding request unit, when one of the device ID information needs to be unbound, sends a device ID information unbinding request through a user terminal;

[0040] an unbinding verification unit, configured to read the device ID information of the user terminal logged in by the user account, verify the device ID information of the user terminal through the bound device ID information, and send a device ID information unbinding instruction to the user terminal if and only if the verification is successful; and

[0041] The unbinding feedback information receiving unit is used to receive device ID information unbinding feedback information sent by a user terminal, wherein the device ID information unbinding feedback information includes device ID information that needs to be unbound.

[0042] As a further solution of the present invention: the unbinding verification unit includes:

[0043] A quantity verification subunit, used to verify the quantity of device ID information bound to the user account;

[0044] The unbinding instruction sending subunit sends a device ID information unbinding instruction to the user terminal when the number of bound device ID information is two, and the device ID information unbinding instruction includes the device information to be re-bound; when the number of bound device ID information is greater than two, the device ID information unbinding instruction is sent to the user terminal, and the device ID information unbinding instruction does not include the device information to be re-bound.

[0045] Compared with the prior art, the beneficial effect of the present invention is that when a user accesses the database through a user terminal, the present invention automatically reads the device ID information of the user terminal logged in by the user account, and verifies the device ID information of the user terminal through the device ID information bound to the user account. If and only if the verification is passed, the data to be accessed is allowed to be accessed by the user terminal. Only when the logged-in device is consistent with the device bound to the user account, the third-level data can be read, so that even if the user account and password are cracked, confidential information will not be leaked. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 The flowchart of a database access method is shown in FIG.

[0047] Figure 2 The present invention is a flowchart for binding device ID information in a database access method.

[0048] Figure 3 The present invention is a flowchart for unbinding device ID information in a database access method.

[0049] Figure 4 The present invention is a flow chart of sending a device ID information unbinding instruction to a user terminal in a database access method.

[0050] Figure 5 The present invention is a flowchart for automatically logging out a user account in a database access method.

[0051] Figure 6 A schematic diagram of the structure of a database access system.

[0052] Figure 7 The schematic diagram is a structural diagram of a device ID information binding module in a database access system.

[0053] Figure 8 This is a structural diagram of a device ID information unbinding module in a database access system.

[0054] Fig. 9 The present invention is a structural diagram of an unbinding verification unit in a database access system. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0056] The specific implementation of the present invention is described in detail below in conjunction with specific embodiments.

[0057] like Figure 1 As shown, an embodiment of the present invention provides a database access method, the method comprising the following steps:

[0058] S100, receiving data access information sent by a user terminal;

[0059] S200, determining the category of the data to be accessed through the data access information;

[0060] S300, when the data to be accessed is primary data, directly allowing the data to be accessed to be accessed by the user terminal;

[0061] S400, when the data to be accessed is secondary data, checking the login status of the user terminal, and when the user account is in the login status on the user terminal, allowing the data to be accessed to be accessed by the user terminal;

[0062] S500, when the data to be accessed is level 3 data, the device ID information of the user terminal logged in by the user account is read, and the device ID information of the user terminal is verified through the device ID information bound to the user account. If and only if the verification is successful, the data to be accessed is allowed to be accessed by the user terminal, and the number of device ID information bound to one user account is at least two.

[0063] It should be noted that databases have become the main target of hackers, and databases store a large amount of valuable and confidential information. Therefore, ensuring the security of databases has become an increasingly important task. Under the CS architecture, the client and the database are generally connected by communication. The common method is that the user enters his or her own username and password to log in to the user account. After verification, the data in the database can be read and accessed. However, since the client is placed on the client's local machine, especially now most CS architectures are developed based on interpreted languages ​​such as C# or JAVA, which are easy to be decompiled. Once important information such as the account and password for connecting to the database is cracked, it will cause major security problems and cause significant losses. Therefore, the embodiments of the present invention are intended to solve the above problems.

[0064] In the embodiment of the present invention, in order to ensure that confidential information will not be leaked even if the user account and password are cracked, when accessing the database through the user terminal, it is necessary to read the device ID information of the user terminal logged in by the user account, and verify the device ID information of the user terminal through the device ID information bound to the user account. If and only if the verification is successful, the data to be accessed is allowed to be accessed by the user terminal. It can be seen that only when the logged-in device is consistent with the device bound to the user account, the third-level data can be read. In this way, even if the user account and password are cracked, the confidential information will not be leaked. It is easy to understand that this method has certain disadvantages. For example, when the bound device is lost, the third-level data may never be accessible. Therefore, the device ID information bound to one user account is at least two. In addition, this solution still has the disadvantage of remote login. When When the logged-in device is not a bound device, access to data will be hindered. Therefore, it is necessary to classify the data in the database in advance, for example, into primary data, secondary data and tertiary data. Primary data refers to public data, secondary data refers to internal public data, and tertiary data refers to confidential data and privacy data. The data classification work is performed by relevant staff, or the user classifies the data when uploading the data. When the data to be accessed is primary data, the data to be accessed is directly allowed to be accessed by the user terminal without logging in to the user account, which is convenient and fast; when the data to be accessed is secondary data, the login status of the user terminal is checked. When the user account is in the logged-in status on the user terminal, the data to be accessed is allowed to be accessed by the user terminal. When accessing secondary data, it is necessary to log in to the user account. It should be noted that secondary data refers to internal public data. Even if the user account and password are cracked, it will not cause serious losses.

[0065] like Figure 2 As shown, as a preferred embodiment of the present invention, the method further includes binding the device ID information, specifically:

[0066] S601, sending a device ID information binding request through a user terminal;

[0067] S602, checking whether the corresponding user account has device ID information bound;

[0068] S603, when the corresponding user account is not bound to device ID information, reading the device ID information of the user terminal, and obtaining the device ID information of the device when the user account is registered, and sending a device ID information binding instruction to the user terminal if and only if the two device ID information are consistent;

[0069] S604, when the corresponding user account has bound device ID information, read the device ID information of the user terminal, verify the device ID information of the user terminal through the bound device ID information, and send a device ID information binding instruction to the user terminal if and only if the verification passes;

[0070] S605: Receive device ID information binding feedback information sent by the user terminal, where the device ID information binding feedback information includes device ID information that needs to be bound.

[0071] In the embodiment of the present invention, in order to be able to read and access the third-level data, the device must be bound, and a device ID information binding request needs to be sent through the user terminal. The embodiment of the present invention will check whether the corresponding user account has device ID information bound. When the corresponding user account has no device ID information bound, the device ID information of the user terminal is read, and the device ID information of the device when the user account is registered is obtained. If and only if the two device ID information are consistent, a device ID information binding instruction is sent to the user terminal. It should be noted that when the user account is registered, the embodiment of the present invention will automatically read and store the device ID information of the device at the time of registration. When the device is bound for the first time, the logged-in device ID information The information must be the device ID information of the registered device, that is, the logged-in device must be the device at the time of registration, so as to avoid the user account being arbitrarily bound to the device after being stolen, resulting in the leakage of the tertiary data. In addition, for the convenience of use, the device binding work can be completed at the same time as registration; in addition, when the corresponding user account has bound device ID information, the device ID information of the user terminal is read, and the device ID information of the user terminal is verified through the bound device ID information. If and only if the device ID information of the user terminal belongs to the bound device ID information, a device ID information binding instruction is sent to the user terminal; finally, the device ID information binding feedback information sent by the user terminal is received to complete the device binding work.

[0072] like Figure 3 As shown, as a preferred embodiment of the present invention, the method further includes unbinding the device ID information, specifically:

[0073] S701, when one of the device ID information needs to be unbound, a device ID information unbinding request is sent through the user terminal;

[0074] S702, reading the device ID information of the user terminal logged in by the user account, verifying the device ID information of the user terminal through the bound device ID information, and sending a device ID information unbinding instruction to the user terminal if and only if the verification passes;

[0075] S703: Receive device ID information unbinding feedback information sent by the user terminal, where the device ID information unbinding feedback information includes device ID information that needs to be unbinded.

[0076] In an embodiment of the present invention, when a bound device is lost or no longer in use, unbinding is required. A device ID information unbinding request is sent through the user terminal. The embodiment of the present invention automatically reads the device ID information of the user terminal logged in by the user account, and verifies the device ID information of the user terminal through the bound device ID information. Only when the logged in device belongs to the bound device, a device ID information unbinding instruction is sent to the user terminal, and then the device ID information unbinding feedback information sent by the user terminal is received to complete the unbinding work.

[0077] like Figure 4 As shown, as a preferred embodiment of the present invention, the step of sending a device ID information unbinding instruction to the user terminal specifically includes:

[0078] S7021, checking the number of device ID information bound to the user account;

[0079] S7022, when the number of bound device ID information is two, sending a device ID information unbinding instruction to the user terminal, wherein the device ID information unbinding instruction includes the device information to be re-bound;

[0080] S7023: When the number of bound device ID information is greater than two, a device ID information unbinding instruction is sent to the user terminal, wherein the device ID information unbinding instruction does not include device information to be re-bound.

[0081] In the embodiment of the present invention, it should be noted that, when unbinding, it is necessary to check the number of device ID information bound to the user account. When the number of bound device ID information is two, when a device ID information unbinding instruction is sent to the user terminal, the device ID information unbinding instruction includes the device information to be re-bound. That is to say, when unbinding, the user must upload the device information to be re-bound and perform the device binding work at the same time to ensure that the number of device ID information bound to one user account is at least two.

[0082] like Figure 5 As shown, as a preferred embodiment of the present invention, the method further includes enabling the user account to automatically log out, specifically:

[0083] S801, after the device ID information is unbound successfully, verify the device ID information of the user terminal;

[0084] S802: When the device ID information of the user terminal is unbound device ID information, the user account is automatically logged out.

[0085] In the embodiment of the present invention, it can be understood that after the device ID information is successfully unbound, the device logged in to the unbound device cannot access the third-level data. In order to avoid that the logged-in device has already been verified, when the device ID information of the logged-in user terminal is the unbound device ID information, the user account is automatically logged out, so that the logged-in device will be re-verified when accessing the third-level data.

[0086] like Figure 6 As shown, an embodiment of the present invention further provides a database access system, the system comprising:

[0087] The data access receiving module 100 is used to receive data access information sent by a user terminal;

[0088] An access data classification module 200, used to determine the classification of the data to be accessed through the data access information;

[0089] A first access permission module 300, which directly allows the data to be accessed to be accessed by the user terminal when the data to be accessed is primary data;

[0090] A second access permission module 400, when the data to be accessed is secondary data, checks the login status of the user terminal, and when the user account is in the login status on the user terminal, allows the data to be accessed to be accessed by the user terminal; and

[0091] The third access permission module 500, when the data to be accessed is level 3 data, reads the device ID information of the user terminal logged in by the user account, verifies the device ID information of the user terminal through the device ID information bound to the user account, and allows the data to be accessed to be accessed by the user terminal only when the verification is passed, and the number of device ID information bound to one user account is at least two.

[0092] In the embodiment of the present invention, in order to ensure that confidential information will not be leaked even if the user account and password are cracked, when accessing the database through the user terminal, it is necessary to read the device ID information of the user terminal logged in by the user account, and verify the device ID information of the user terminal through the device ID information bound to the user account. If and only if the verification is successful, the data to be accessed is allowed to be accessed by the user terminal. It can be seen that only when the logged-in device is consistent with the device bound to the user account, the third-level data can be read. In this way, even if the user account and password are cracked, the confidential information will not be leaked. It is easy to understand that this method has certain disadvantages. For example, when the bound device is lost, the third-level data may never be accessible. Therefore, the device ID information bound to one user account is at least two. In addition, this solution still has the disadvantage of remote login. When When the logged-in device is not a bound device, access to data will be hindered. Therefore, it is necessary to classify the data in the database in advance, for example, into primary data, secondary data and tertiary data. Primary data refers to public data, secondary data refers to internal public data, and tertiary data refers to confidential data and privacy data. The data classification work is performed by relevant staff, or the user classifies the data when uploading the data. When the data to be accessed is primary data, the data to be accessed is directly allowed to be accessed by the user terminal without logging in to the user account, which is convenient and fast; when the data to be accessed is secondary data, the login status of the user terminal is checked. When the user account is in the logged-in status on the user terminal, the data to be accessed is allowed to be accessed by the user terminal. When accessing secondary data, it is necessary to log in to the user account. It should be noted that secondary data refers to internal public data. Even if the user account and password are cracked, it will not cause serious losses.

[0093] like Figure 7 As shown, as a preferred embodiment of the present invention, the system further includes a device ID information binding module 600, and the device ID information binding module 600 includes:

[0094] A binding request unit 601 sends a device ID information binding request through a user terminal;

[0095] A binding verification unit 602 is used to verify whether the corresponding user account has been bound to the device ID information;

[0096] The binding instruction sending unit 603 reads the device ID information of the user terminal when the corresponding user account has no bound device ID information, and obtains the device ID information of the device when the user account is registered, and sends a device ID information binding instruction to the user terminal only when the two device ID information are consistent; reads the device ID information of the user terminal when the corresponding user account has bound device ID information, verifies the device ID information of the user terminal through the bound device ID information, and sends a device ID information binding instruction to the user terminal only when the verification is successful; and

[0097] The binding feedback information receiving unit 604 is configured to receive device ID information binding feedback information sent by a user terminal, wherein the device ID information binding feedback information includes device ID information that needs to be bound.

[0098] In the embodiment of the present invention, in order to be able to read and access the third-level data, the device must be bound, and a device ID information binding request needs to be sent through the user terminal. The embodiment of the present invention will check whether the corresponding user account has device ID information bound. When the corresponding user account has no device ID information bound, the device ID information of the user terminal is read, and the device ID information of the device when the user account is registered is obtained. If and only if the two device ID information are consistent, a device ID information binding instruction is sent to the user terminal. It should be noted that when the user account is registered, the embodiment of the present invention will automatically read and store the device ID information of the device at the time of registration. When the device is bound for the first time, the logged-in device ID information The information must be the device ID information of the registered device, that is, the logged-in device must be the device at the time of registration, so as to avoid the user account being arbitrarily bound to the device after being stolen, resulting in the leakage of the tertiary data. In addition, for the convenience of use, the device binding work can be completed at the same time as registration; in addition, when the corresponding user account has bound device ID information, the device ID information of the user terminal is read, and the device ID information of the user terminal is verified through the bound device ID information. If and only if the device ID information of the user terminal belongs to the bound device ID information, a device ID information binding instruction is sent to the user terminal; finally, the device ID information binding feedback information sent by the user terminal is received to complete the device binding work.

[0099] like Figure 8 As shown, as a preferred embodiment of the present invention, the system further includes a device ID information unbinding module 700, and the device ID information unbinding module 700 includes:

[0100] The unbinding request unit 701 sends a device ID information unbinding request through a user terminal when one of the device ID information needs to be unbinded;

[0101] The unbinding verification unit 702 is used to read the device ID information of the user terminal logged in by the user account, verify the device ID information of the user terminal through the bound device ID information, and send a device ID information unbinding instruction to the user terminal if and only if the verification is successful; and

[0102] The unbinding feedback information receiving unit 703 is configured to receive device ID information unbinding feedback information sent by a user terminal, wherein the device ID information unbinding feedback information includes device ID information that needs to be unbound.

[0103] In an embodiment of the present invention, when a bound device is lost or no longer in use, unbinding is required. A device ID information unbinding request is sent through the user terminal. The embodiment of the present invention automatically reads the device ID information of the user terminal logged in by the user account, and verifies the device ID information of the user terminal through the bound device ID information. Only when the logged in device belongs to the bound device, a device ID information unbinding instruction is sent to the user terminal, and then the device ID information unbinding feedback information sent by the user terminal is received to complete the unbinding work.

[0104] like Fig. 9 As shown, as a preferred embodiment of the present invention, the unbinding verification unit 702 includes:

[0105] The quantity verification subunit 7021 is used to verify the quantity of device ID information bound to the user account;

[0106] The unbinding instruction sending subunit 7022 sends a device ID information unbinding instruction to the user terminal when the number of bound device ID information is two, and the device ID information unbinding instruction includes the device information to be re-bound; when the number of bound device ID information is greater than two, the device ID information unbinding instruction is sent to the user terminal, and the device ID information unbinding instruction does not include the device information to be re-bound.

[0107] In the embodiment of the present invention, it should be noted that, when unbinding, it is necessary to check the number of device ID information bound to the user account. When the number of bound device ID information is two, when a device ID information unbinding instruction is sent to the user terminal, the device ID information unbinding instruction includes the device information to be re-bound. That is to say, when unbinding, the user must upload the device information to be re-bound and perform the device binding work at the same time to ensure that the number of device ID information bound to one user account is at least two.

[0108] The above only describes in detail the preferred embodiments of the present invention, which is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

[0109] It should be understood that, although each step in the flow chart of each embodiment of the present invention is shown in sequence according to the indication of the arrow, these steps are not necessarily performed in sequence according to the order indicated by the arrow. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be performed in other orders. Moreover, at least a portion of the steps in each embodiment may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0110] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0111] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the disclosure in the specification and examples. This application is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

Claims

1. A database access method, characterized in that: The method comprises the following steps: Receiving data access information sent by a user terminal; Determine the classification of the data to be accessed through the data access information; When the data to be accessed is primary data, directly allowing the data to be accessed to be accessed by the user terminal; When the data to be accessed is secondary data, checking the login status of the user terminal, and when the user account is in the login status on the user terminal, allowing the data to be accessed to be accessed by the user terminal; When the data to be accessed is level 3 data, the device ID information of the user terminal logged in by the user account is read, and the device ID information of the user terminal is verified by the device ID information bound to the user account. If and only if the verification is successful, the data to be accessed is allowed to be accessed by the user terminal, and the number of device ID information bound to one user account is at least two; The method further includes binding the device ID information, specifically: Send a device ID information binding request through the user terminal; Check whether the corresponding user account has device ID information bound; When the corresponding user account has no device ID information bound to it, read the device ID information of the user terminal, and obtain the device ID information of the device when the user account is registered, and send a device ID information binding instruction to the user terminal if and only if the two device ID information are consistent; When the corresponding user account has bound device ID information, the device ID information of the user terminal is read, and the device ID information of the user terminal is verified through the bound device ID information. If and only if the device ID information of the user terminal belongs to the bound device ID information, a device ID information binding instruction is sent to the user terminal; The device ID information binding feedback information sent by the user terminal is received, wherein the device ID information binding feedback information includes the device ID information that needs to be bound.

2. A database access method according to claim 1, characterized in that: The method further includes unbinding the device ID information, specifically: When one of the device ID information needs to be unbound, a device ID information unbinding request is sent through the user terminal; Read the device ID information of the user terminal logged in by the user account, verify the device ID information of the user terminal through the bound device ID information, and send a device ID information unbinding instruction to the user terminal if and only if the verification passes; The device ID information unbinding feedback information sent by the user terminal is received, wherein the device ID information unbinding feedback information includes the device ID information that needs to be unbinded.

3. A database access method according to claim 2, characterized in that: The step of sending a device ID information unbinding instruction to the user terminal specifically includes: Verify the number of device ID information bound to the user account; When the number of bound device ID information is two, a device ID information unbinding instruction is sent to the user terminal, wherein the device ID information unbinding instruction includes the device information to be re-bound; When the number of bound device ID information is greater than two, a device ID information unbinding instruction is sent to the user terminal, wherein the device ID information unbinding instruction does not include device information to be re-bound.

4. A database access method according to claim 3, characterized in that: The method further includes causing the user account to automatically log out, specifically: When the device ID information is unbound successfully, verifying the device ID information of the user terminal; When the device ID information of the user terminal is unbound device ID information, the user account is automatically logged out.

5. A database access system, characterized in that: The system comprises: A data access receiving module, used for receiving data access information sent by a user terminal; An access data classification module, used to determine the classification of the data to be accessed through the data access information; a first access permission module, which directly allows the data to be accessed to be accessed by the user terminal when the data to be accessed is primary data; a second access permission module, which checks the login status of the user terminal when the data to be accessed is secondary data, and allows the data to be accessed to be accessed by the user terminal when the user account is in the login status on the user terminal; and A third access permission module, when the data to be accessed is level 3 data, reads the device ID information of the user terminal logged in by the user account, verifies the device ID information of the user terminal through the device ID information bound to the user account, and allows the data to be accessed by the user terminal only if and only if the verification is successful, and the device ID information bound to one user account is at least two; The system further includes a device ID information binding module, and the device ID information binding module includes: A binding request unit, sending a device ID information binding request through a user terminal; A binding verification unit, used to verify whether the corresponding user account has been bound to the device ID information; a binding instruction sending unit, which reads the device ID information of the user terminal and obtains the device ID information of the device when the user account is registered, when the corresponding user account has no bound device ID information, and sends a device ID information binding instruction to the user terminal if and only if the two device ID information are consistent; reads the device ID information of the user terminal when the corresponding user account has bound device ID information, verifies the device ID information of the user terminal through the bound device ID information, and sends a device ID information binding instruction to the user terminal if and only if the device ID information of the user terminal belongs to the bound device ID information; and The binding feedback information receiving unit is used to receive device ID information binding feedback information sent by a user terminal, wherein the device ID information binding feedback information includes device ID information that needs to be bound.

6. A database access system according to claim 5, characterized in that: The system further includes a device ID information unbinding module, and the device ID information unbinding module includes: An unbinding request unit, when one of the device ID information needs to be unbound, sends a device ID information unbinding request through a user terminal; an unbinding verification unit, configured to read the device ID information of the user terminal logged in by the user account, verify the device ID information of the user terminal through the bound device ID information, and send a device ID information unbinding instruction to the user terminal if and only if the verification is successful; and The unbinding feedback information receiving unit is used to receive device ID information unbinding feedback information sent by a user terminal, wherein the device ID information unbinding feedback information includes device ID information that needs to be unbound.

7. A database access system according to claim 6, characterized in that: The unbinding verification unit includes: A quantity verification subunit, used to verify the quantity of device ID information bound to the user account; The unbinding instruction sending subunit sends a device ID information unbinding instruction to the user terminal when the number of bound device ID information is two, and the device ID information unbinding instruction includes the device information to be re-bound; when the number of bound device ID information is greater than two, the device ID information unbinding instruction is sent to the user terminal, and the device ID information unbinding instruction does not include the device information to be re-bound.

Images