CN115062094A - Fabric-based relational database content synchronization method - Google Patents
Fabric-based relational database content synchronization method Download PDFInfo
- Publication number
- CN115062094A CN115062094A CN202111650572.0A CN202111650572A CN115062094A CN 115062094 A CN115062094 A CN 115062094A CN 202111650572 A CN202111650572 A CN 202111650572A CN 115062094 A CN115062094 A CN 115062094A
- Authority
- CN
- China
- Prior art keywords
- database
- synchronization
- fabric
- relational database
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 239000004744 fabric Substances 0.000 title claims abstract description 40
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000001360 synchronised effect Effects 0.000 claims abstract description 14
- 230000008569 process Effects 0.000 claims abstract description 7
- 238000012795 verification Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 4
- 230000002457 bidirectional effect Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 10
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention relates to a Fabric-based relational database content synchronization method, which is characterized in that each Peer node is provided with a relational database for storing more complex data, operation records are stored in a block chain account book, and corresponding logics are added to each part of the Fabric so as to achieve the purpose of synchronizing the contents of the relational databases. The process comprises the following steps: when the node is started, a series of initialization operations are carried out, particularly the re-enabling of the key and the re-pulling of the content of the relational database. And then, the synchronous information is broadcasted through Gossip, the height of the account book is compared after the nodes receive the synchronous information, and the database of each node with the highest height of the account book is taken as the standard, so that the database table is synchronized based on Gossip service. The invention can not only expand the storage capacity of the block chain, but also enhance the safety and the tamper resistance of the data.
Description
Technical Field
The invention relates to the technical field of block chains, in particular to a method for synchronizing contents of a relational database based on Fabric.
Background
The fabric of the hyper ledger (hyper-Ledger) is an open-source enterprise-level licensing distributed ledger technology platform, and compared with other popular distributed ledgers or blockchain platforms, the fabric has a highly modular and configurable architecture and better performance in terms of transaction processing and transaction confirmation delay. The fabric as a distributed account book has the advantages of high security, tamper resistance, traceability and the like compared with the traditional relational database, but has the defects that the relational database does not have, such as difficult expansion of storage, difficult organization of data with complex structure and low performance. Similarly, for a traditional relational database, there are data security problems, database downtime, data loss, centralized vulnerability, and the like.
Thus, combining the two can take advantage of both. In this combination, since the relational database does not have Byzantine Fault Tolerance (BFT) capability, it is a key problem to be solved to design a reasonable synchronization process for the relational database based on the block chain ledger.
Disclosure of Invention
In view of the above-mentioned drawbacks and deficiencies of the prior art, the present invention provides a method for synchronizing data contents of a relational database based on fabric. The method adds an additional relational database for each Peer node (Peer) to store different parts of data into a Fabric block chain account book and the relational database respectively, and simultaneously combines a symmetric encryption method and properly modifies a data storage flow to be stored into the Fabric and the relational database, so that the method can ensure the safety and the integrity of the stored data and can also consider the efficiency of storing and inquiring the data.
The technical scheme of the invention is as follows: a data content synchronization method based on a fabric relational database comprises the following steps: firstly, allocating a relational database for each Peer node to store data to be linked, and then adding corresponding logic to each part of the fabric to achieve the aim of synchronizing the contents of the relational database; the process comprises the following steps: when the node is started, a series of initialization operations are carried out, particularly the re-starting of the key and the re-pulling of the content of the relational database are carried out; and then, broadcasting the synchronization information through Gossip, comparing the height of the account book after the nodes receive the synchronization information, and taking the database of each node with the highest height of the account book as a reference, thereby synchronizing the database table based on Gossip service, and modifying the storage logic and adding the synchronization logic to the fabric through modification of each step.
Further, the method comprises the following specific steps:
step 1: the security of external data needs to be guaranteed by adding an additional database, and data in the relational database needs to be read at the same time, so that encryption is performed in an AES (advanced encryption standard) bidirectional encryption mode;
step1.1, adding a key management class Crypter for Fabric, comprising the following steps: RandomKeyGen () for generating a fixed length random key; EncryptTable () used to encrypt the database table name; EncryptSQL () used for encrypting each field of specific SQL stored in the relational database; DecryptTable () for decrypting the database table name; DecryptResult () for decrypting the database operation result set;
step1.2, key storage is very important for symmetric encryption, and because nodes in a federation chain cannot be restarted frequently in normal operation, a random KeyGen () method is used to create a key when the nodes are started, and the key is stored in a program, wherein the random key is different for each Peer node, and is not stored externally (configuration files, block ledgers and the like) so as to ensure the security of the key.
Step 2: adding an additional relational database requires managing the database, so that a database management table added for database synchronization is added for management;
step2.1, add an additional relational database management class DBmanager for the Peer part of Fabric, comprising the method: RunSQLFile (), executing SQL files and operating SQL sentences in batches; exenuteSQL (), executing SQL statements; QuerySQL (), executing query SQL statements; IsTableExist () to check whether the data table exists; CalTableChecksum () used for calculating the check sum of the database table and carrying out comparison check with other nodes; insertSyncTable/ReadSyncState/UpdateSyncState/DeleteSyncState for operating the synchronization table;
step2.2, adding a database synchronization state table SyncStateTable in the relational database for managing the synchronization condition of each table of the database; the design of the table is shown in table 1.
Step2.3, when the Peer node is started, checking the connection of the database, checking the state of a synchronization table, inquiring whether the database exists or not, and if not, establishing the database; setting a database; checking a synchronization table SyncStateTable, and if the synchronization table SyncStateTable does not exist, establishing the synchronization table; checking the checksum of each table, and confirming whether to synchronize with other nodes through network service; whenever the database table is operated, the checksum is recalculated and stored in the synchronization state table.
Step 3: in order to ensure the data synchronization of the additional relational database, a new message type and processing logic need to be added through gossypervice; the defined new message is compiled through the fabric-proto-go project and then is put in the DataMassege of the gosspService to serve as a new message content type;
step3.1, adding a new checking synchronization verification message type DBDataSyncMessage for the proto message of Fabric;
step3.2, after receiving the synchronous check information, generating a return information type SyncRespMessage;
step3.3, when synchronization is needed (such as a node A), randomly sending a broadcast message DBDataSyncMessage to a plurality of nodes nearby through gosspService, and checking the synchronization state of the corresponding table; after receiving the message, other nodes (such as node B) compare the message with the check sum of the database table of the node B and return a response message SyncRespMessage of the node B, wherein the message containing the highest block of the node B is used for height check;
step3.4, the node A receives a plurality of related return messages, and after summary verification, the node with the highest block height is selected to request the corresponding data table SQL file; other nodes read a data table different from the node A, decrypt the data table through DecrytResult (), and send the data table to the node A through TLS encrypted communication; after receiving the new data tables sent by other nodes, the node A encrypts the data again through the own key, then executes RunSQLFile () to update the data into the database, and finally updates the state of SyncStateTable.
Step 4: the operation of the relational database is carried out through a client API of the fabric, when the client initiates the operation of the database, the consensus of the operation records is firstly carried out, a block chain account book is stored, and then the related operation of the relational database is carried out; when the operation record is generated and the database is operated, recalculating the checksum of each data table and storing the checksum into a SyncStateTable;
step 5: adding a management class Syncer for periodically checking synchronization in the fabric, and performing synchronization check by calling the Step of Step3 every time 100 blocks are built so as to remove the relation type database difference in the running process.
The invention has the beneficial effects that:
the invention provides a relational database for each Peer node for storing data to be linked. In a federation chain, a node is typically kept online for a long period of time, and if the node is not online, the node is restarted and a series of initialization operations are performed, particularly re-enabling of keys and re-pulling of the contents of the relational database. And then, the synchronous information is broadcasted through Gossip, the height of the account book is compared after the nodes receive the synchronous information, and the database of each node with the highest height of the account book is used as the standard, so that the database table is synchronized based on Gossip service. The invention carries out the transformation of storage logic and the addition of synchronous logic on the fabric. According to the method provided by the invention, under the condition of expanding the storage mode of the fabric, a set of method for synchronizing the relational database is designed, so that the capacity expansion of the block chain storage can be ensured, and the safety and the tamper resistance of the data can be enhanced.
Drawings
FIG. 1 is a synchronization flow diagram of the present invention.
Detailed Description
Embodiment 1, as shown in fig. 1, a method for synchronizing content of a Fabric-based relational database is to configure a relational database, such as MySQL, for each Peer node to store data for uplink transmission. And then the modification of the fabric-protocols, fabric-protocols-go and fabric open source items is carried out. Through modification of all steps, the method carries out modification of storage logic and addition of synchronous logic on the fabric.
The method comprises the following specific steps:
step 1: the security of external data needs to be guaranteed by adding an additional database, and data in the relational database needs to be read at the same time, so that encryption is performed in an AES (advanced encryption standard) bidirectional encryption mode;
step1.1, adding a key management class Crypter for Fabric, and mainly comprising the following steps: RandomKeyGen () for generating a fixed length random key; EncryptTable () used to encrypt the database table name; EncryptSQL () used for encrypting each field of specific SQL stored in the relational database; DecryptTable () for decrypting the database table name; DecryptResult () for decrypting the database operation result set;
step1.2, key storage is very important for symmetric encryption, and because nodes in a federation chain cannot be restarted frequently during normal operation, a random KeyGen () method is used to create a key when the nodes are started, and the key is stored in a program, wherein the random key is different for each Peer node and is not stored to the outside (configuration files, block accounts and the like) so as to ensure the security of the key.
Step 2: adding an additional relational database requires managing the database, so that a database management table added for database synchronization is added for management;
step2.1, add an additional relational database management class DBmanager for the Peer part of Fabric, comprising the method: RunSQLFile (), SQL files are executed, and SQL sentences are operated in batch; ExecuteSQL (), execute SQL statement; QuerySQL (), executing query SQL statements; IsTableExist () to check whether the data table exists; CalTableCheckSum () used for calculating the check sum of the database table and carrying out comparison check with other nodes; insertSyncTable/ReadSyncState/UpdateSyncState/DeleteSyncState for operating the synchronization table;
step2.2, adding a database synchronization state table SyncStateTable in the MySQL database, and managing the synchronization condition of each table of the database; the design of the table is shown in table 1.
Table 1 shows the structure of SyncTableState
| Name of field | Type (B) | Description of the invention |
| Owner | String | Table creator storing client identity and node identity information |
| TableName | String | Table name |
| TableNameInDB | String | Encrypted database table names |
| Checksum | Int | Check sum of corresponding table |
| LedgerHash | String | Highest hash of account book |
| LedgerSeq | String | Height of account book |
| PreviousCommit | String | The last transaction hash of the table |
| Deleted | Bool | Whether the table is valid, deleted |
Step2.3, when the Peer node is started, checking the connection of the database, checking the state of a synchronization table, inquiring whether the database exists or not, and if not, establishing the database; setting a database; checking a synchronization table SyncStateTable, and if the synchronization table SyncStateTable does not exist, establishing the synchronization table; checking the checksum of each table, and confirming whether to synchronize with other nodes through network service; whenever the database table is operated, the checksum is recalculated and stored in the synchronization state table.
Step 3: in order to ensure the data synchronization of the additional relational database, a new message type and processing logic need to be added through gossypervice; the defined new message is compiled through a fabric-proto-go project and then is put in DataMassege of gosspService to serve as a new message content type;
step3.1, adding a new checking synchronization verification message type DBDataSyncmessage for the proto message of Fabric; it is defined as follows:
step3.2, after the node receives the synchronous verification information by modifying the fabric-protocols project, generating a return information type SyncRespMessage; it is defined as follows:
step3.3, when synchronization is needed (such as a node A), randomly sending a broadcast message DBDataSyncMessage to a plurality of nodes nearby through gosspService, and checking the synchronization state of the corresponding table; after receiving the message, other nodes (such as node B) compare the message with the check sum of the database table of the node B and return a response message SyncRespMessage of the node B, wherein the message containing the highest block of the node B is used for height check;
step3.4, the node A receives a plurality of related return messages, and after summary verification, the node with the highest block height is selected to request the corresponding data table SQL file; the node B reads a data table different from the node A, decrypts the data table through DecrytResult (), and sends the data table to the node A through TLS encrypted communication; after receiving the new data table sent by the node B, the node A encrypts the data again through the own key, executes RunSQLFile () to update the data into the database, and finally updates the state of the SyncStateTable.
Step 4: the operation of the relational database is carried out through a client API of the fabric, when the client initiates the operation of the database, the consensus of the operation records is firstly carried out, a block chain account book is stored, and then the related operation of the relational database is carried out; when the operation record is generated and the database is operated, recalculating the checksum of each data table and storing the checksum into a SyncStateTable;
step 5: adding a management class Syncer for periodically checking synchronization in the fabric, and performing synchronization check by calling the Step of Step3 every time 100 blocks are built so as to remove the relation type database difference in the running process.
While the present invention has been described in detail with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, and various changes can be made without departing from the spirit of the present invention within the knowledge of those skilled in the art.
Claims (5)
1. A method for synchronizing contents of a relational database based on Fabric is characterized in that: firstly, allocating a relational database for each Peer node for storing data to be linked, and then adding corresponding logic to each part of the fabric to achieve the aim of synchronizing the contents of the relational database; the process comprises the following steps: when the node is started, a series of initialization operations are carried out, particularly the re-starting of the key and the re-pulling of the content of the relational database are carried out; and then, the synchronous information is broadcasted through Gossip, the height of the account book is compared after the nodes receive the synchronous information, and the database of each node with the highest height of the account book is taken as the standard, so that the database table is synchronized based on Gossip service.
2. The Fabric-based relational database content synchronization method of claim 1, wherein: the method comprises the following specific steps:
step 1: the safety of external data needs to be ensured by adding an additional database, and data in the relational database needs to be read at the same time, so that encryption is performed by adopting an AES (advanced encryption Standard) bidirectional encryption mode;
step 2: adding an additional relational database requires managing the database, so that a database management table added for database synchronization is added for management;
step 3: in order to ensure the data synchronization of the additional relational database, a new message type and processing logic need to be added through gossypervice; the defined new message is compiled through the fabric-proto-go project and then is put in the DataMassege of the gosspService to serve as a new message content type;
step 4: the operation of the relational database is carried out through a client API of the fabric, when the client initiates the operation of the database, the consensus of operation records is firstly carried out, a block chain account book is stored, and then the related operation of the relational database is carried out; when the operation record is generated and the database is operated, recalculating the checksum of each data table and storing the checksum into a SyncStateTable;
step 5: adding a management class Syncer for periodically checking synchronization in the fabric, and performing synchronization check by calling the Step of Step3 every time 100 blocks are built so as to remove the relation type database difference in the running process.
3. The Fabric-based relational database content synchronization method of claim 1, wherein: the Step1 specifically comprises the following steps:
step1.1, adding a key management class Crypter for Fabric, comprising the following steps: RandomKeyGen () for generating a fixed length random key; EncryptTable () used to encrypt the database table name; EncryptSQL () used for encrypting each field of specific SQL stored in the relational database; DecryptTable () for decrypting the database table name; DecryptResult () for decrypting the database operation result set;
step1.2, key storage is very important for symmetric encryption, and because nodes in a federation chain are not frequently restarted in normal operation, a random KeyGen () method is used to create a key when the nodes are started, and the key is stored in a program, wherein the random key is different for each Peer node and is not stored to the outside so as to ensure the security of the key.
4. The Fabric-based relational database content synchronization method of claim 1, wherein: the Step2 specifically comprises the following steps:
step2.1, add an additional relational database management class DBmanager for the Peer part of Fabric, comprising the method: RunSQLFile (), executing SQL files and operating SQL sentences in batches; exenuteSQL (), executing SQL statements; QuerySQL (), executing query SQL statements; IsTableExist () to check whether the data table exists; CalTableChecksum () used for calculating the check sum of the database table and carrying out comparison check with other nodes; insertSyncTable/ReadSyncState/UpdateSyncState/DeleteSyncState for operating the synchronization table;
step2.2, adding a database synchronization state table SyncStateTable in the relational database for managing the synchronization condition of each table of the database;
step2.3, when the Peer node is started, checking the connection of the database, checking the state of a synchronization table, inquiring whether the database exists or not, and if not, establishing the database; setting a database; checking a synchronization table SyncStateTable, and if the synchronization table SyncStateTable does not exist, establishing the synchronization table; checking the checksum of each table, and confirming whether to synchronize with other nodes through network service; whenever the database table is operated, the checksum is recalculated and stored in the synchronization state table.
5. The Fabric-based relational database content synchronization method of claim 1, wherein: the Step3 specifically comprises the following steps:
step3.1, adding a new checking synchronization verification message type DBDataSyncmessage for the proto message of Fabric;
step3.2, after receiving the synchronous check information, generating a return information type SyncRespMessage;
step3.3, when the synchronization is needed, the node A randomly sends a broadcast message DBDataSyncMessage to a plurality of nodes nearby through gosspService, and checks the synchronization state of the corresponding table; after receiving the message, other nodes compare the message with the check sum of the database table of the other nodes and return a response message SyncRespMessage of the other nodes, wherein the information containing the highest block of the other nodes is used for height check;
step3.4, the node A receives a plurality of related return messages, and after summary verification, the node with the highest block height is selected to request the corresponding data table SQL file; other nodes read a data table different from the node A, decrypt the data table through DecrytResult (), and send the data table to the node A through TLS encrypted communication; after receiving the new data tables sent by other nodes, the node A encrypts the data again through the own key, then executes RunSQLFile () to update the data into the database, and finally updates the state of SyncStateTable.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111650572.0A CN115062094B (en) | 2021-12-30 | 2021-12-30 | Relational database content synchronization method based on Fabric |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111650572.0A CN115062094B (en) | 2021-12-30 | 2021-12-30 | Relational database content synchronization method based on Fabric |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115062094A true CN115062094A (en) | 2022-09-16 |
| CN115062094B CN115062094B (en) | 2024-03-29 |
Family
ID=83196964
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111650572.0A Active CN115062094B (en) | 2021-12-30 | 2021-12-30 | Relational database content synchronization method based on Fabric |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115062094B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170206034A1 (en) * | 2006-05-17 | 2017-07-20 | Richard Fetik | Secure Application Acceleration System, Methods and Apparatus |
| CN108830709A (en) * | 2018-04-17 | 2018-11-16 | 中车工业研究院有限公司 | A kind of crowdsourcing transaction system based on block chain |
| CN110266817A (en) * | 2019-07-15 | 2019-09-20 | 武汉天喻信息产业股份有限公司 | Across channel data sharing model, sharing method and device based on block chain |
| CN110597926A (en) * | 2019-10-10 | 2019-12-20 | 山东爱城市网信息技术有限公司 | Method and system for establishing block chain side chain based on horizontal extension database |
| CN111949726A (en) * | 2020-06-07 | 2020-11-17 | 中信银行股份有限公司 | Relational database synchronization method and system based on block chain |
| CN112737779A (en) * | 2020-12-30 | 2021-04-30 | 深圳市宝能投资集团有限公司 | Service method and device for cipher machine, cipher machine and storage medium |
| CN113157723A (en) * | 2021-04-06 | 2021-07-23 | 福州大学 | SQL access method for Hyperridge Fabric |
| CN113515772A (en) * | 2021-04-20 | 2021-10-19 | 昆明理工大学 | Method for querying log information uplink by database based on RPCA (resilient packet access) consensus mechanism |
-
2021
- 2021-12-30 CN CN202111650572.0A patent/CN115062094B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170206034A1 (en) * | 2006-05-17 | 2017-07-20 | Richard Fetik | Secure Application Acceleration System, Methods and Apparatus |
| CN108830709A (en) * | 2018-04-17 | 2018-11-16 | 中车工业研究院有限公司 | A kind of crowdsourcing transaction system based on block chain |
| CN110266817A (en) * | 2019-07-15 | 2019-09-20 | 武汉天喻信息产业股份有限公司 | Across channel data sharing model, sharing method and device based on block chain |
| CN110597926A (en) * | 2019-10-10 | 2019-12-20 | 山东爱城市网信息技术有限公司 | Method and system for establishing block chain side chain based on horizontal extension database |
| CN111949726A (en) * | 2020-06-07 | 2020-11-17 | 中信银行股份有限公司 | Relational database synchronization method and system based on block chain |
| CN112737779A (en) * | 2020-12-30 | 2021-04-30 | 深圳市宝能投资集团有限公司 | Service method and device for cipher machine, cipher machine and storage medium |
| CN113157723A (en) * | 2021-04-06 | 2021-07-23 | 福州大学 | SQL access method for Hyperridge Fabric |
| CN113515772A (en) * | 2021-04-20 | 2021-10-19 | 昆明理工大学 | Method for querying log information uplink by database based on RPCA (resilient packet access) consensus mechanism |
Non-Patent Citations (2)
| Title |
|---|
| Y MANEVICH等: "Endorsement in Hyperledger Fabric via service discovery", IBM JOURNAL OF RESEARCH AND DEVELOPMENT, vol. 63, no. 2, 20 February 2019 (2019-02-20), pages 1 - 9 * |
| 余涛;牛保宁;樊星;: "FabricSQL:区块链数据的关系查询", 计算机工程与设计, vol. 41, no. 10, 16 October 2020 (2020-10-16), pages 2988 - 2995 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115062094B (en) | 2024-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107888562B (en) | Data verification and transceiving method, node and system for parallel link access to interconnection chain | |
| CN109766673B (en) | Alliance type audio and video copyright block chain system and audio and video copyright chaining method | |
| CN107943833B (en) | Centerless distributed file storage and retrieval method based on block chain | |
| CN103595730B (en) | A kind of ciphertext cloud storage method and system | |
| TW202101939A (en) | Method and device for switching processing of main node in block chain system | |
| CN112910840A (en) | Medical data storage and sharing method and system based on alliance blockchain | |
| WO2019184210A1 (en) | Multi-warehouse data management method based on block chain and related device | |
| CN110990408A (en) | Block chain-based business information cooperation method, business system and alliance chain | |
| US20230316273A1 (en) | Data processing method and apparatus, computer device, and storage medium | |
| TW202101261A (en) | Improved anti-replay device based on memory space interchange | |
| CN112615847B (en) | Data sharing and privacy protection method based on block chain | |
| CN110601830A (en) | Key management method, device, equipment and storage medium based on block chain | |
| CN112486736A (en) | Block chain based data backup system and backup method | |
| CN113259453B (en) | Cross-chain interaction method and device | |
| CN106255103A (en) | A kind of method of data synchronization and equipment | |
| EP4357950A1 (en) | Device management method, system and apparatus | |
| CN113259456A (en) | Cross-chain interaction method and device | |
| CN115695449A (en) | Block chain digital collection source file cross-platform synchronization and transfer method | |
| CN110620776B (en) | Data transfer information transmission method and device | |
| CN110673966A (en) | Data interaction method based on block chain up-link down cooperation | |
| CN111177265A (en) | Block chain domain division method | |
| CN110543606A (en) | Method and system for storing genealogy data based on alliance chain | |
| CN115062094B (en) | Relational database content synchronization method based on Fabric | |
| CN111865983A (en) | Block chain-based data security tracing method | |
| CN112818061A (en) | Unstructured data storage method and block chain system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |