Managing a database management system using a blockchain database

Patent metadata

Field	Value
Publication number	US-10135609-B2
Application number	US-201715851879-A
Country	US
Kind code	B2
Filing date	Dec 22, 2017
Priority date	Feb 9, 2017
Publication date	Nov 20, 2018
Grant date	Nov 20, 2018

Abstract

Disclosed aspects relate to managing a database management system (DBMS). A central database to include a set of central data may be structured with respect to the DBMS. A blockchain database which is linked with the central database may be constructed with respect to the DBMS. A set of blockchain data may be established in the blockchain database corresponding to the set of central data of the central database. An access request may be received with respect to the DBMS. In response to receiving the access request, both the central database and the blockchain database may be maintained.

First claim

What is claimed is:

1. A computer-implemented method for managing a database management system (DBMS), the method comprising:
structuring, with respect to the DBMS, a central database to include a set of central data;
constructing, with respect to the DBMS, a blockchain database which is linked with the central database;
establishing, in the blockchain database corresponding to the set of central data of the central database, a set of blockchain data;
receiving, with respect to the DBMS, an access request; and
maintaining, in response to receiving the access request, both the central database and the blockchain database;
mapping a first central entry of the central database to a first blockchain entry of the blockchain database to establish the set of blockchain data;
receiving, in association with the access request, a valid user authorization to carry-out the access request with respect to the blockchain database
detecting an inconsistency of the central database and the blockchain database and storing the inconsistency in a permanent log, wherein the inconsistency is indicative of an unauthorized access and modification of the central database;
comparing, to detect the inconsistency, the set of central data of the central database with the set of blockchain data of the blockchain database, wherein the set of blockchain data is a partial copy of the set of central data;
determining a mismatch of a first central entry of the central database and a first blockchain entry of the blockchain database, wherein the mismatch is based on a magnitude of discrepancy with respect to a threshold similarity factor;
recording, in a blockchain permanent log, the mismatch of the first central entry of the central database and the first blockchain entry of the blockchain database;
providing, in response to detecting the inconsistency, an alert of the inconsistency;
compiling, to manage the blockchain database, a set of blockchain database copies for a set of consumer-users;
generating, in an application program, a set of code to interact with the blockchain database;
configuring the central database for accessibility by a set of administrator users;
configuring the central database for inaccessibility by a set of non-administrator users;
configuring the blockchain database for inaccessibility by the set of administrator users;
configuring the blockchain database for accessibility via a smart contract;
deriving the set of blockchain data from the set of central data, wherein the set of blockchain data is a subset of the set of central data, wherein the subset is based on a series of discrete connected blocks associated with a hash;
resolving, in association with the access request, a smart contract feature to carry-out the access request with respect to the blockchain database;
resolving, in association with the access request, a public key cryptography feature to carry-out the access request with respect to the blockchain database;
resolving, in association with the access request, a private key cryptography feature to carry-out the access request with respect to the blockchain database;
introducing, separate from both the central database and the blockchain database, a detection engine to detect the inconsistency, wherein the central database and the blockchain database are physically separate, wherein the detection engine monitors the central database and the blockchain database;
probing, by the detection engine in response to achieving a monitoring criteria, the central database and the blockchain database, wherein the monitoring criteria consists: a benchmark parameter, a condition, a stipulation, and a threshold;
executing, in a dynamic fashion to streamline management of the DBMS, each of: the structuring, the constructing, the establishing, the receiving, and the maintaining, wherein the dynamic fashion is performed on-the-fly simultaneously in response to the access request;
executing, in an automated fashion without user intervention, each of: the structuring, the constructing, the establishing, the receiving, and the maintaining, wherein the automated fashion is performed by an DBMS management module with automated computing machinery.

Assignees

• IBM

Inventors

• Bibera Wyndell Love
• Faeldon James Arnold A
• Pantola Alexis V

Classifications

• G06F17/30371

  Physics · mapped topic

• G06F17/30289

  Physics · mapped topic

• H04L9/30

  Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy · CPC title

• H04L63/083

  using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title

• H04L9/0643

  Hash functions, e.g. MD5, SHA, HMAC or f9 MAC · CPC title