CN110471928B - Data circulation system - Google Patents
Data circulation system Download PDFInfo
- Publication number
- CN110471928B CN110471928B CN201910610245.9A CN201910610245A CN110471928B CN 110471928 B CN110471928 B CN 110471928B CN 201910610245 A CN201910610245 A CN 201910610245A CN 110471928 B CN110471928 B CN 110471928B
- Authority
- CN
- China
- Prior art keywords
- node
- data
- nodes
- record
- supplier
- 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.)
- Active
Links
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/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- 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/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Computational Linguistics (AREA)
- Economics (AREA)
- Computing Systems (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A data flow system comprising: the data nodes comprise a plurality of demander nodes and a plurality of supplier nodes, wherein the demander nodes are used for collecting the query records received by the demander nodes and writing the collected query records into the block chain ledger, and the supplier nodes are used for collecting the data records sent by the supplier nodes and writing the collected data records into the block chain ledger; and the core node is used for acquiring the query record and the data record from the block chain account book and settling the transaction according to the query record and the data record. The technical scheme of the invention can realize the consistency of the transaction records in the data circulation process.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a data circulation system.
Background
In the field of data circulation, a data demander queries label data of a data supplier through data identification (information for uniquely determining data, such as mobile equipment codes, personal identification and the like, agreed by the data supplier and the data demander).
However, in the circulation process, each party may tamper the log or repudiate the number of the sent and received logs to cause distrust of the two parties, so that the accounts of the transaction parties are inconsistent and the reconciliation is difficult.
Disclosure of Invention
The invention solves the technical problem of how to realize the consistency of transaction records in the data circulation process.
To solve the above technical problem, an embodiment of the present invention provides a data circulation system, including: the data nodes comprise a plurality of demander nodes and a plurality of supplier nodes, wherein the demander nodes are used for collecting the query records received by the demander nodes and writing the collected query records into the block chain ledger, and the supplier nodes are used for collecting the data records sent by the supplier nodes and writing the collected data records into the block chain ledger; and the core node is used for acquiring the query record and the data record from the block chain account book and settling the transaction according to the query record and the data record.
Optionally, the acquirer node writes the collected query records into the block chain ledger according to a preset period, and the supplier node writes the collected data records into the block chain ledger according to the preset period.
Optionally, the data node includes a monitoring module, and the monitoring module is configured to submit the collected query record or data record to the endorsement node when the time length for collecting the query record or data record reaches a preset time length.
Optionally, each data node has a corresponding white list, and the white list includes endorsement nodes selected by the data node.
Optionally, when the data node writes the collected query record or data record into the block chain ledger, one or more endorsement nodes are selected from the white list to perform endorsement.
Optionally, the one or more endorsement nodes analyze and confirm the query record or the data record, and sign the confirmed query record or data record.
Optionally, the data node selects an endorsement node in one of the following manners: the data node randomly selects one or more endorsement nodes from the white list; the data node determines a supplier node for sending the query record and a supplier node for receiving the query record, or determines a supplier node for sending the data record and a supplier node for receiving the data record, and selects an overlapped endorsement node in a white list corresponding to the determined supplier node and the supplier node; and the data node selects one or more endorsement nodes with the most endorsement times from the white list.
Optionally, the blockchain ledger is synchronously stored in the endorsement node and the core node.
Optionally, for an acquirer node and a supplier node where a transaction occurs, the hash value of the transaction log data is written into the blockchain book, and the transaction log data is synchronously stored in each node in a node set corresponding to the acquirer node and the supplier node where the transaction occurs, where the node set includes the acquirer node and the supplier node where the transaction occurs and a preset data node.
Optionally, the core node determines a transaction amount according to the query record sent by the acquirer node and the data record sent by the supplier node, deducts the transaction amount from the account amount of the acquirer node, and adds the transaction amount to the account amount of the supplier node.
Optionally, when the query record and the data record are inconsistent, the core node marks an exception to the query record and the data record.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
in the technical scheme of the invention, the data circulation system comprises data nodes, a plurality of acquirer nodes and a plurality of supplier nodes, wherein the acquirer nodes are used for collecting inquiry records received by the acquirer nodes and writing the collected inquiry records into a block chain account book; and the core node is used for acquiring the query record and the data record from the block chain account book and settling the transaction according to the query record and the data record. According to the technical scheme, a plurality of block chain nodes, namely data nodes and core nodes are arranged, so that transaction records of a supplier node and an demander node, namely query records, data records and the like can be written into a block chain account book; the block chain account book can be synchronized by each node, each node participating in data circulation can maintain a unified account book, the consistency of transaction records in the data circulation process is realized through an intelligent contract and a consensus mechanism of the block chain, the transaction records are prevented from being falsified, the problem caused by 'checking account before checking account' is solved by changing the problem into 'checking account before checking account', the automation, the digitization, the transparency and the notarization of transaction settlement of core nodes are ensured, and the efficiency, the reliability and the credibility of the transaction settlement are improved. In addition, because the blockchain network is a distributed accounting, the computing, storage and network bandwidth resources are shared among all nodes, and the performance problem caused by centralization is greatly reduced.
Furthermore, each data node is provided with a corresponding white list, and the white list comprises endorsement nodes selected by the data nodes. In the technical scheme of the invention, each data node can maintain a corresponding white list and can select the endorsement node from the maintained white list, so that the reliability of the selection of the endorsement node can be ensured, and the reliability of data writing into a block chain account book is ensured.
Further, for the demand side node and the supplier side node where the transaction occurs, the hash value of the transaction log data is written into the block chain account book, and the transaction log data is synchronously stored in each node in the node set corresponding to the demand side node and the supplier side node where the transaction occurs. According to the technical scheme, the transaction log data are stored in each node in the set, and the hash value of the transaction log data is written into the block chain account book, so that the safety and the privacy of the data can be guaranteed on the basis of guaranteeing the consistency of data records.
Drawings
FIG. 1 is a schematic structural diagram of a data flow system according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a specific application scenario according to an embodiment of the present invention.
Detailed Description
As described in the background art, in the circulation process, since each party may tamper with the log or repudiate the number of the transmitted and received logs to cause distrust of both parties, the accounts of each party in the transaction are inconsistent and the reconciliation is difficult.
According to the technical scheme, a plurality of block chain nodes, namely data nodes and core nodes are arranged, so that transaction records, namely query records, data records and the like of a supplier node and an acquirer node can be written into a block chain account book; the block chain account book can be synchronized by each node, so that each node participating in data circulation can maintain a unified account book, the problem caused by 'account checking before account checking' is solved by changing the intelligent contract and the consensus mechanism of the block chain into 'account checking before account checking', the automation, the digitization, the transparence and the notarization of transaction settlement of the core node are ensured, and the efficiency, the reliability and the credibility of the transaction settlement are improved. In addition, because the blockchain network is distributed accounting, the computing, storage and network bandwidth resources are shared among all the nodes, and the performance problem caused by centralization is greatly reduced.
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.
Fig. 1 is a schematic structural diagram of a data circulation system according to an embodiment of the present invention.
The data circulation system is a blockchain network that may be deployed and maintained by a data trading platform. In this embodiment, the blockchain network may adopt a distributed network structure of a Fabric architecture.
Referring to fig. 1, the data circulation system includes a plurality of data nodes 101, at least one core node 102, and a block chain ledger 103.
The data node 101 may include a plurality of acquirer nodes 1011 and a plurality of supplier nodes 1012. The acquirer node 1011 is configured to collect the query records sent by the acquirer node 1011 and write the collected query records into the blockchain ledger 103, and the supplier node 1012 is configured to collect the data records sent by the supplier node 1012 and write the collected data records into the blockchain ledger 103.
The core node 102 is configured to obtain the query record and the data record from the blockchain ledger 103, and perform transaction settlement according to the query record and the data record.
In particular implementations, the core node 102 may be deployed at a data trafficking platform.
In an implementation, the acquirer node 1011 sends a data request identifier (Identity, ID) to the data provider (i.e., the supplier node 1012) when requesting data. The acquirer node 1011 may record in real time the number of data identifiers received from the data supplier after it requests data from the data supplier, i.e., the query record.
After receiving the data request identifier sent by the acquirer node 1011, the supplier node 1012 searches the local database for the matched data, and returns the matched data. Donor node 1012 may record the number of data identifications it sends out, i.e., data records, in real time.
Further, after receiving the data sent by the supplier node 1012, the acquirer node 1011 may also record the amount of the data it receives, and write the record into the blockchain ledger 103 as a query record.
Further, the core node 102 may settle the transaction between the acquirer node 1011 and the supplier node 1012 based on the amount of data (i.e., data records) sent by the supplier node 1012 and the amount of data received by the acquirer node 1011 (i.e., query records).
In this embodiment, the block chain network formed by the data node 101 and the core node 102 may be a federation chain.
In the embodiment of the invention, by setting a plurality of block chain nodes, namely data nodes and core nodes, transaction records, namely query records, data records and the like of a supplier node and an demander node can be written into a block chain account book; the block chain account book can be synchronized by each node, so that each node participating in data circulation can maintain a unified account book, the problem caused by 'account checking before account checking' is solved by changing the intelligent contract and the consensus mechanism of the block chain into 'account checking before account checking', the automation, the digitization, the transparence and the notarization of transaction settlement of the core node are ensured, and the efficiency, the reliability and the credibility of the transaction settlement are improved. In addition, because the blockchain network is distributed accounting, the computing, storage and network bandwidth resources are shared among all the nodes, and the performance problem caused by centralization is greatly reduced.
In a non-limiting embodiment, the acquirer node 1011 writes the collected query records into the blockchain ledger 103 according to a preset period, and the supplier node 1012 writes the collected data records into the blockchain ledger 103 according to the preset period.
In this embodiment, the query records and/or data records collected in real time are grouped and aggregated according to "node-delivery order-delivery task" to form a total record number, and since the transaction number is large and the frequency is high, in order to reduce the system concurrency pressure, the query records of each acquirer node 1011 and the data records of each supplier node 1012 are aggregated and calculated with a preset period, for example, "per hour" as the frequency.
In particular, for a single record collected in real time for which statistics are complete, a "completed" flag may be set to avoid duplicate calculations. Further, the query records or data records after statistics are completed can be recorded in a local database.
Further, the hourly record collection of each acquirer node 1011 and supplier node 1012 can be monitored, and if a preset period is reached, a proposal is submitted to a designated endorsement node for transaction confirmation to write into the blockchain ledger 103.
In one non-limiting embodiment, each data node 101 has a corresponding white list that includes endorsement nodes for selection by the data node 101.
In a specific implementation, the acquirer node 1011 and the supplier node 1012 submit data to an endorsement node in a federation chain organization for signature authentication before the data is written into a block chain ledger. The endorsement node simulates and calculates a transaction book according to a distribution mode aiming at data (namely query records and data records) proposed by the acquirer node 1011 and the supplier node 1012, and signs the data which runs without errors.
In this embodiment, each data node 101 may maintain a corresponding white list. The white list members can only be selected from nodes in the blockchain network, i.e., the white list members are selected from the data nodes 101 in the data traffic system, i.e., from the acquirer node 1011 and the supplier node 1012.
Further, when the data node 101 writes the collected query record or data record into the block chain ledger 103, one or more endorsement nodes are selected from the white list for endorsement.
Further, the one or more endorsement nodes analyze and confirm the query record or the data record, and sign the confirmed query record or data record.
In specific implementation, after a receiver or a provider submits a transaction to a designated endorsement node, the endorsement node operates an algorithm according to counting and charging rules, analyzes the submitted transaction, confirms ledger information, and signs the confirmed ledger.
It should be noted that, as to the specific process of signature confirmation of the endorsement node on the query record or the data record, reference may be made to the prior art, and the embodiment of the present invention is not limited thereto.
In the embodiment of the invention, each data node 101 can maintain a corresponding white list and can select the endorsement node from the maintained white list, so that the reliability of the selection of the endorsement node can be ensured, and the reliability of data writing into a block chain account book is ensured.
In a specific implementation, the data node 101 may select an endorsement node by using one of the following methods: the data node 101 may randomly select one or more endorsement nodes from the whitelist;
the data node 101 may determine an acquirer node 1011 sending an inquiry record and a supplier node 1012 receiving the inquiry record, or determine a supplier node 1012 sending a data record and an acquirer node 1011 receiving the data record, and select an overlapped endorsement node in a white list corresponding to the determined supplier node 1012 and the supplier node 1011;
and the data node 101 selects one or more endorsement nodes with the most endorsement times from the white list.
Further, data that the acquirer node 1011 or the supplier node 1012 has completed validation may be sorted in time order waiting to be written into the blockchain ledger 103.
In one non-limiting embodiment, the blockchain ledger 103 is stored in an endorsement node in synchronization with the core node 102.
In this embodiment, the endorsement node and the core node 102 can synchronize the blockchain ledger 103, and may also store data in the blockchain ledger 103 locally. Further, core node 102 may obtain data of each data node 101 in blockchain ledger 103 from its synchronized blockchain ledger 103 for settlement of transactions.
In one non-limiting embodiment, for an acquirer node 1011 and a supplier node 1012 where a transaction occurs, a hash value of transaction log data is written to the blockchain ledger 103, and the transaction log data is stored at each node in a node set corresponding to the acquirer node 1011 and the supplier node 1012 where the transaction occurs.
In this embodiment, a private data set may be established between the requiring node 1011 and the providing node 1012 where the transaction occurs, and the transaction log data may be stored in both data transaction parties and other nodes with authority authentication, that is, the transaction log data may only be accessed by each node in the node set, that is, both transaction parties or other nodes with access authority.
It will be appreciated that when no private data set is established between the acquirer node 1011 and the supplier node 1012 where the transaction occurs, the transaction log data may be stored at all nodes in the blockchain network.
For example. For data nodes A, B and C, if there is a transaction between data node a and data node B, data node C cannot obtain private data information in the channels of data node a and data node B, thereby ensuring the isolation and privacy of information. Meanwhile, hash values of transaction log data of the data node A and the data node B are recorded in the block chain ledger, and therefore it is ensured that ledger information can be obtained again from a neutral endorsement node if the data node A and the data node B lose information abnormally.
In the embodiment of the invention, the transaction log data is stored in each node in the node set corresponding to the acquirer node and the supplier node where the transaction occurs, and the hash value of the transaction log data is written into the block chain account book, so that the safety and the privacy of the data can be ensured on the basis of ensuring the consistency of data records.
In one non-limiting embodiment, the core node 102 determines the transaction amount according to the query record sent by the acquirer node 1011 and the data record sent by the supplier node 1012, deducts the transaction amount from the account credit of the acquirer node 1011, and adds the transaction amount to the account credit of the supplier node 1012.
In this embodiment, since the block chain ledger 103 records transaction records (i.e., query records and data records) of each data node, and the core node 102 can synchronize the block chain ledger 103, the core node 102 can determine the total amount of data of the transaction between the acquirer node 1011 and the supplier node 1012 from the transaction records recorded by the block chain ledger 103. In addition, the core node can also obtain the unit price of the transaction data, and thus, the core node 102 can determine the transaction amount according to the total data amount of the transaction and the unit price of the transaction data. The core node 102 may update the account credit of the acquirer node 1011 and the account credit of the party node 1012 based on the transaction amount.
To this end, core node 102 completes the settlement of the transaction between the acquirer node 1011 and the supplier node 1012.
In one non-limiting embodiment, the core node marks the query record and the data record with an exception when the query record and the data record are inconsistent.
Further, in the transaction settlement process, if the data amounts recorded by the acquirer node 1011 and the supplier node 1012 in the blockchain ledger 103 are not consistent, for example, 3000 pieces of received data are recorded in the blockchain ledger 103 by the acquirer node 1011, and 5000 pieces of sent data are recorded in the blockchain ledger 103 by the supplier node 1012, in this case, the core node 102 may mark the corresponding record as "clearing exception", and for such an abnormal ledger, the platform operator coordinates the adjustment processing of both transaction parties.
In a specific application scenario, referring to fig. 2, the data circulation system 20 may include a supplier node 201, a demander node 202, a supplier node 203, a demander node 204, an endorsement node 205, and a sorting node 206. The core node and blockchain ledger are not labeled in the figure.
The identifier 2 indicates a transaction data flow between the supplier node 201 and the demander node 202, that is, data transaction occurs between the supplier node 201 and the demander node 202, the demander node 202 sends an inquiry request through the data flow 2, the supplier node 201 sends transaction data through the data flow 2, and the demander node 202 receives the transaction data through the data flow 2.
Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (9)
1. A data circulation system, comprising:
the data nodes comprise a plurality of demander nodes and a plurality of supplier nodes, wherein the demander nodes are used for collecting the query records received by the demander nodes and writing the collected query records into the block chain ledger, and the supplier nodes are used for collecting the data records sent by the supplier nodes and writing the collected data records into the block chain ledger;
at least one core node, configured to obtain the query record and the data record from the blockchain ledger, and perform transaction settlement according to the query record and the data record; each data node is provided with a corresponding white list, and the white list comprises endorsement nodes selected by the data nodes; the data node selects an endorsement node by adopting one of the following modes: the data node randomly selects one or more endorsement nodes from the white list; the data node determines a requiring party node for sending the query record and a providing party node for receiving the query record, or determines a providing party node for sending the data record and a requiring party node for receiving the data record, and selects the overlapping endorsement nodes in the white list corresponding to the determined providing party node and the requiring party node; and the data node selects one or more endorsement nodes with the most endorsement times from the white list.
2. The data circulation system of claim 1, wherein the acquirer node writes the collected inquiry records into the blockchain ledger according to a preset period, and the supplier node writes the collected data records into the blockchain ledger according to the preset period.
3. The data circulation system of claim 1, wherein the data node comprises a monitoring module, and the monitoring module is configured to submit the collected query records or data records to the endorsement node when the time length for collecting the query records or data records reaches a preset time length.
4. The data circulation system of claim 1, wherein the data node selects one or more endorsement nodes from the white list for endorsement when writing the collected query records or data records into a blockchain ledger.
5. The data circulation system of claim 1, wherein the one or more endorsement nodes analyze and validate the query record or the data record and sign the validated query record or data record.
6. A data flow system according to claim 1, wherein the blockchain ledger is stored in an endorsement node and the core node simultaneously.
7. The data circulation system according to claim 1, wherein for an acquirer node and a supplier node where a transaction occurs, the hash value of transaction log data is written into the blockchain book, and the transaction log data is synchronously stored in each node in a node set corresponding to the acquirer node and the supplier node where the transaction occurs, the node set including the acquirer node and the supplier node where the transaction occurs and a preset data node.
8. The data currency system according to claim 1, wherein the core node determines a transaction amount according to the query record sent by the acquirer node and the data record sent by the supplier node, deducts the transaction amount from the account amount of the acquirer node, and adds the transaction amount to the account amount of the supplier node.
9. The data flow system according to claim 1, wherein the core node marks the query record and the data record with an exception when the query record and the data record are inconsistent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910610245.9A CN110471928B (en) | 2019-07-08 | 2019-07-08 | Data circulation system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910610245.9A CN110471928B (en) | 2019-07-08 | 2019-07-08 | Data circulation system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110471928A CN110471928A (en) | 2019-11-19 |
| CN110471928B true CN110471928B (en) | 2022-06-21 |
Family
ID=68507115
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910610245.9A Active CN110471928B (en) | 2019-07-08 | 2019-07-08 | Data circulation system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110471928B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107786642A (en) * | 2017-09-30 | 2018-03-09 | 上海数据交易中心有限公司 | Block chain building method and device, storage medium, server for data circulation |
| CN108763389A (en) * | 2018-05-18 | 2018-11-06 | 上海数据交易中心有限公司 | The integration method and device of data, storage medium, terminal |
| CN108830733A (en) * | 2018-06-21 | 2018-11-16 | 中国银行股份有限公司 | A kind of information processing method, block scm cluster and system |
| AU2019200933B1 (en) * | 2017-10-27 | 2019-05-23 | Digital Asset (Switzerland) GmbH | Computer system and method for distributed privacy-preserving shared execution of one or more processes |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106651346A (en) * | 2016-11-28 | 2017-05-10 | 上海凯岸信息科技有限公司 | Block chain-based credit investigation data sharing and trading system |
| WO2018120121A1 (en) * | 2016-12-30 | 2018-07-05 | 深圳前海达闼云端智能科技有限公司 | Block chain permission control method, device, and node apparatus |
| CN107807951B (en) * | 2017-09-18 | 2020-10-13 | 联动优势科技有限公司 | Block chain generation method, data verification method, node and system |
| US11556521B2 (en) * | 2017-09-29 | 2023-01-17 | Oracle International Corporation | System and method for providing an interface for a blockchain cloud service |
-
2019
- 2019-07-08 CN CN201910610245.9A patent/CN110471928B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107786642A (en) * | 2017-09-30 | 2018-03-09 | 上海数据交易中心有限公司 | Block chain building method and device, storage medium, server for data circulation |
| AU2019200933B1 (en) * | 2017-10-27 | 2019-05-23 | Digital Asset (Switzerland) GmbH | Computer system and method for distributed privacy-preserving shared execution of one or more processes |
| CN108763389A (en) * | 2018-05-18 | 2018-11-06 | 上海数据交易中心有限公司 | The integration method and device of data, storage medium, terminal |
| CN108830733A (en) * | 2018-06-21 | 2018-11-16 | 中国银行股份有限公司 | A kind of information processing method, block scm cluster and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110471928A (en) | 2019-11-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109791591B (en) | Method and system for identity and credential protection and verification via blockchain | |
| US11930113B2 (en) | Blockchain hybrid consensus-based system for maintaining domain name information | |
| Luu et al. | {SmartPool}: Practical decentralized pooled mining | |
| CN107392608B (en) | Block chain system-based digital asset transaction method and block chain system | |
| CN109859024B (en) | Tax system consensus method based on alliance chain | |
| US20170344435A1 (en) | Method and system for desynchronization recovery for permissioned blockchains using bloom filters | |
| CN110827028B (en) | Block chain-based data acquisition transaction system and method | |
| CN110399373A (en) | A kind of block chain account book storage system, storage querying method and delet method | |
| US20210049715A1 (en) | Blockchain-based data procesing method, apparatus, and electronic device | |
| CN109002725A (en) | Data processing system based on block chain | |
| CN109859043B (en) | Transaction clearing method and transaction clearing system | |
| CN110135860A (en) | A kind of safe traceability system of crop seeds based on block chain technology | |
| CN111931220B (en) | Consensus processing method, device, medium and electronic equipment for block chain network | |
| CN103067363A (en) | Index conversion method for public data integrity checking | |
| CN113011883A (en) | Data processing method, device, equipment and storage medium | |
| CN110019194A (en) | Verification of data method, apparatus, computer equipment and storage medium | |
| CN114840527A (en) | Data processing method, device and computer readable storage medium | |
| CN114006920A (en) | Geological disaster emergency command system based on alliance chain | |
| CN114693241A (en) | Block chain-based electronic resume system and implementation method thereof | |
| CN110471928B (en) | Data circulation system | |
| CN113205345A (en) | Agricultural product certificate tracing system based on Ether house block chain technology and tracing method thereof | |
| CN113643032B (en) | Information processing method, device and data management system based on block chain | |
| CN110417917A (en) | Method, system, computer equipment and medium for bill circulation | |
| CN111444416A (en) | Method, system and device for popularizing financial business | |
| CN110991573A (en) | Product management method, system, client node and storage medium |
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 |