DATABASE OPERATION METHOD AND DEVICE

• US 20170262640A1
• Filed: 11/18/2014
• Published: 09/14/2017
• Est. Priority Date: 09/09/2014
• Status: Abandoned Application

• Current Assignee: ZTE Corporation
• Original Assignee: ZTE Corporation
• Inventors: FAN, Wuxun, ZHAO, Guotao
• Application Number:
  US15/509,369
• Publication Number:
  US 20170262640A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: G06F 21/60 Protecting data
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04W 12/041 Key generation or derivation
• CPC Class Codes: H04W 12/08 Access security

Abstract

Disclosed are a database operation method and device. The method includes: receiving a read/write request to an open source database of a first terminal; generating a first key for accessing the open source database under triggering of the read/write request; comparing and determining whether the first key is consistent with a second key, wherein the second key is a key generated by the first terminal based on a feature code of the first terminal when creating the open source database; and determining whether to allow a read/write operation to the open source database according to a comparison result, wherein the read/write operation to the open source database is permitted when the comparison result indicates that the first and second keys are consistent; and the read/write operation to the open source database is prohibited when the comparison result indicates that the first and second keys are inconsistent.

Claims

1. A method for operating a database, comprising:

receiving a read/write request to an open source database of a first terminal;

generating a first key for accessing the open source database under triggering of the read/write request;

comparing and determining whether the first key is consistent with a second key, wherein the second key is a key generated by the first terminal based on a feature code of the first terminal when creating the open source database; and

determining whether to allow a read/write operation to the open source database according to a comparison result, wherein the read/write operation to the open source database is permitted when the comparison result indicates that the first and second keys are consistent; and

the read/write operation to the open source database is prohibited when the comparison result indicates that the first and second keys are inconsistent.

2. The method of claim 1, wherein the generating the first key for accessing the open source database comprises:

when the read/write request is a read/write request sent by the first terminal, generating the first key based on the feature code of the first terminal.

3. The method of claim 2, wherein when the read/write request is the read/write request sent by the first terminal, the comparison result indicates that the first and second keys are consistent.

4. The method of claim 1, wherein the generating the first key for accessing the open source database comprises:

when the read/write request is a read/write request sent by a second terminal, generating the first key based on a feature code of the second terminal.

5. The method of claim 4, wherein when the read/write request is the read/write request sent by the second terminal, the comparison result indicates that the first and second keys are inconsistent.

6. The method of claim 1, wherein the determining whether to allow the read/write operation to the open source database based on the comparison result comprises:

determining whether to allow the read/write operation to the open source database itself and/or whether to allow the read/write operation to contents in the open source database based on the comparison result.

7. The method of claim 1, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

15. The method of claim 2, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

16. The method of claim 3, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

17. The method of claim 4, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

18. The method of claim 5, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

19. The method of claim 6, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

8. A device for operating a database, comprising:

a processor; and

a memory for storing instructions executable by the processor;

wherein the processor is arranged to;

receive a read/write request to an open source database of a first terminal;

generate a first key for accessing the open source database under triggering of the read/write request;

compare and determine whether the first key is consistent with a second key, wherein the second key is a key generated by the first terminal based on a feature code of the first terminal when creating the open source database; and

determine whether to allow a read/write operation to the open source database according to a comparison result, wherein the read/write operation to the open source database is permitted when the comparison result indicates that the first and second keys are consistent; and

the read/write operation to the open source database is prohibited when the comparison result indicates that the first and second keys are inconsistent.

9. The device of claim 8, wherein the processor is further arranged to, when the read/write request is a read/write request sent by the first terminal, generate the first key based on the feature code of the first terminal.

10. The device of claim 9, wherein the processor is further arranged to, when the read/write request is the read/write request sent by the first terminal, indicate that the first and second keys are consistent.

11. The device of claim 8, wherein the processor is further arranged to, when the read/write request is a read/write request sent by a second terminal, generate the first key based on a feature code of the second terminal.

12. The device of claim 11, wherein the processor is further arranged to, when the read/write request is the read/write request sent by the second terminal, indicate that the first and second keys are inconsistent.

13. The device of claim 8, wherein the processor is further arranged to determine whether to allow the read/write operation to the open source database itself and/or whether to allow the read/write operation to contents in the open source database based on the comparison result.

14. The device of claim 8, wherein the feature code comprises at least one of:

a terminal identification, a Bluetooth communication address, and a Wireless Fidelity WiFi address.

20. A computer storage medium, wherein the computer storage medium is stored with a computer-executable instruction, and the computer-executable instruction is arranged to:

receive a read/write request to an open source database of a first terminal;

generate a first key for accessing the open source database under triggering of the read/write request;

compare and determine whether the first key is consistent with a second key, wherein the second key is a key generated by the first terminal based on a feature code of the first terminal when creating the open source database; and

determine whether to allow a read/write operation to the open source database according to a comparison result, wherein the read/write operation to the open source database is permitted when the comparison result indicates that the first and second keys are consistent; and

the read/write operation to the open source database is prohibited when the comparison result indicates that the first and second keys are inconsistent.