WO2020207090A1 - 基于区块链的数据处理系统、方法、计算设备及存储介质 - Google Patents
基于区块链的数据处理系统、方法、计算设备及存储介质 Download PDFInfo
- Publication number
- WO2020207090A1 WO2020207090A1 PCT/CN2020/071866 CN2020071866W WO2020207090A1 WO 2020207090 A1 WO2020207090 A1 WO 2020207090A1 CN 2020071866 W CN2020071866 W CN 2020071866W WO 2020207090 A1 WO2020207090 A1 WO 2020207090A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- business
- counted
- data
- blockchain
- node
- Prior art date
Links
Images
Classifications
-
- 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
-
- 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/08—Insurance
Definitions
- This specification relates to the field of blockchain technology, in particular to a data processing system, method, computing device and storage medium based on blockchain.
- the inter-institutional data processing method is that a third-party service platform packages the transaction data generated within a preset time period and sends it to the insurance company.
- the insurance company verifies the transaction data, and then performs commission settlement after the verification is passed.
- the commission settlement method used in the prior art has a high development cost.
- the third-party service platform needs to export transaction data from the core business system and send it to the insurance company for data verification by file transfer or other methods. The entire process takes a long time. , The timeliness is poor, and in the future, if a party's institution disputes transaction data, there is no arbitration mechanism that both parties can recognize.
- the embodiments of this specification provide a blockchain-based data processing system, method, computing device, and storage medium to solve the technical defects in the prior art.
- a blockchain-based data processing system including:
- the business end blockchain node is configured to create a matching transaction data structure for the target business and integrate the to-be-processed business data according to the transaction data structure to generate shared business data, where the information contained in the shared business data satisfies the
- the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, and the shared business data is updated and the accounting operation is performed according to the execution result.
- the server-side blockchain node is configured to receive the service processing request to be counted, and calculate the sum of the amount to be counted in the updated shared service data.
- the business-end blockchain node includes: a business-end blockchain business sub-node and a business-end blockchain accounting sub-node;
- the business-end blockchain business sub-node is configured to create a matching transaction data structure for the target business and integrate the to-be-processed business data according to the transaction data structure to generate shared business data, and bill the sub-node to the business-end blockchain Sending a billing request, where the billing request carries the shared service data;
- the business-end blockchain accounting sub-node is configured to receive the accounting request, and automatically execute the calculation of the amount to be counted when the smart contract automatic execution conditions in the business-end blockchain accounting sub-node are met The task of generating the corresponding execution result, updating the shared business data and executing the accounting operation according to the execution result of the smart contract.
- the business-end blockchain accounting sub-node is also configured to collect updated shared service data according to preset conditions and send to the server a service processing request to be counted, and the service processing request to be counted carries The updated shared service data.
- the business-end blockchain business sub-node is further configured to create a transaction data structure based on an unused transaction output model (UTXO), and the transaction data structure includes a transaction ID, a transaction input and output unit, and The transaction input unit is attached with a signature unlocking script that uses the account balance, and the transaction output unit is attached with a lock script of the output balance, which is used to limit that only the designated account can use the corresponding UTXO unit.
- UTXO unused transaction output model
- the business end blockchain accounting sub-node is further configured to calculate the amount to be counted according to the business amount in the shared business data and the proportion of the amount to be counted in the business amount, and according to The shared service data and the account mapping table in the smart contract determine an output account, and the output unit of the shared service data is updated based on the amount to be counted and the output account.
- the business-end blockchain accounting sub-node is also configured to monitor whether the state machines, things and/or trigger conditions in the smart contract meet preset execution conditions, if the state in the smart contract If any one of the machine, thing and/or trigger condition meets the preset execution condition, the smart contract will reach the automatic execution condition.
- the business-end blockchain business sub-node is also configured to obtain the calculation method of the amount to be counted, determine the mapping relationship between the transaction information and the accounting account, and according to the mapping between the transaction information and the accounting account The relationship generates a corresponding account mapping table, creates the smart contract according to the calculation method of the amount to be counted and the account mapping table, and writes the smart contract into the blockchain network.
- the business end blockchain accounting sub-node is also configured to obtain the calculation method of the amount to be counted, determine the mapping relationship between the transaction information and the accounting account, and according to the transaction information and the accounting account The mapping relationship generates a corresponding account mapping table, creates the smart contract according to the calculation method of the amount to be counted and the account mapping table, and writes the smart contract into the blockchain network.
- the business-end blockchain node is also configured to transfer the updated shared service data signed with the private key to the blockchain network, and to transfer the updated shared service data to the blockchain network The validity of the business data is verified. After the validity verification of the updated shared business data is successful, the updated shared business data is integrated into a hash block ID, and the hash block ID is combined Spread to the entire network.
- the business-end blockchain accounting sub-node is further configured to collect shared business data according to preset conditions, and integrate the shared business data to generate business data to be counted, and perform statistics on the business data to be counted. Process to generate a corresponding hash value, and send a service processing request to be counted to the server blockchain node, where the service processing request to be counted carries the service data to be counted and the corresponding hash value.
- the server-side blockchain node is further configured to obtain the business data to be counted and the corresponding hash value carried in the business processing request to be counted, and to perform statistics on the data to be counted based on the hash value.
- the validity of the business data is verified. If the verification is passed, the total sum of the amount to be counted in the business data to be counted is calculated, and the output unit in the business data to be counted is updated based on the calculation result. As a result, the business processing to be counted on the blockchain node at the business end is completed.
- the server blockchain node is further configured to write the updated business data to be counted into the blockchain.
- a blockchain-based data processing method is provided, which is applied to a business-end blockchain node, including:
- the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, and the execution result is calculated according to the execution result.
- the shared service data is updated and accounting operations are performed;
- creating a matching transaction data structure for the target business includes:
- automatically executing the task of calculating the amount to be counted, generating a corresponding execution result, and updating the shared service data according to the execution result includes:
- the output unit of the shared service data is updated based on the amount to be counted and the output account.
- the smart contract reaches the automatic execution condition.
- writing the smart contract into the blockchain network includes:
- the updated shared service data signed with the private key into the blockchain network, and verify the validity of the updated shared service data passed into the blockchain network.
- the updated shared service After the validity of the data is successfully verified, the updated shared service data is integrated into a hash block ID, and the hash block ID is spread to the entire network.
- collecting updated shared service data according to preset conditions and sending a service processing request to be counted to the server blockchain node includes:
- a service processing request to be counted is sent to the server blockchain node, where the service processing request to be counted carries the service data to be counted and the corresponding hash value.
- a blockchain-based data processing method which is applied to a server-side blockchain node, and includes:
- the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, and the execution result is calculated
- the shared service data is updated and accounting operations are performed;
- the updated shared service data after calculating the total amount to be counted in the updated shared service data, it further includes:
- a computing device including a memory, a processor, and computer instructions stored in the memory and executable on the processor.
- the processor implements the Steps of blockchain-based data processing method.
- a computer-readable storage medium which stores computer instructions that, when executed by a processor, implement the steps of the blockchain-based data processing method.
- a matching transaction data structure is created for the target business through the business end blockchain node, and the to-be-processed business data is integrated according to the transaction data structure to generate shared business data.
- the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, the shared business data is updated according to the execution result, and the accounting operation is performed, and the update is collected according to the preset conditions
- send a service processing request to be counted to the server blockchain node and the server blockchain node receives the service processing request to be counted, and calculates the sum of the amount to be counted in the updated shared service data
- a distributed ledger jointly maintained by both parties is established between the business end and the server, and the transaction data generated by each transaction on the business end is calculated in real time on the ledger, which greatly improves the efficiency of data settlement.
- Blockchain can also guarantee the immutability and accuracy of transaction data.
- Figure 1 is a schematic diagram of a blockchain-based data processing system provided by an embodiment of the present application.
- Figure 2 is a structural block diagram of a computing device provided by an embodiment of the present application.
- FIG. 3 is a flowchart of a blockchain-based data processing method provided by an embodiment of the present application.
- Figure 4 is a flowchart of a blockchain-based data processing method provided by an embodiment of the application.
- FIG. 5 is a schematic diagram of interaction in the application scenario of the insurance business alliance chain according to the blockchain-based data processing method provided by the embodiment of the present application.
- first, second, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
- the first may also be referred to as the second, and similarly, the second may also be referred to as the first.
- word “if” as used herein can be interpreted as "when” or “when” or "in response to determination”.
- Unspent Transaction Output The basic unit of Bitcoin transaction, referred to as UTXO for short. UTXO cannot be divided, locked by the owner, or recorded in the blockchain and recognized as a currency unit by the entire network A certain amount of Bitcoin currency.
- Figure 1 shows a schematic diagram of a blockchain-based data processing system according to an embodiment of this specification, including:
- the business side blockchain node 102 and the server side blockchain node 104 on the blockchain 100 are identical to each other.
- the business-end blockchain node 102 is configured to create a matching transaction data structure for the target business and integrate the to-be-processed business data according to the transaction data structure to generate shared business data.
- the information contained in the shared business data satisfies all requirements.
- the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, and the shared business data is updated according to the execution result and the accounting operation is performed Collecting updated shared service data according to preset conditions and sending a service processing request to be counted to the server blockchain node, where the service processing request to be counted carries the updated shared service data.
- the server-side blockchain node 104 is configured to receive the service processing request to be counted, and calculate the total sum of the to-be counted amount in the updated shared service data.
- the business-end blockchain node includes: a business-end blockchain business sub-node and a business-end blockchain accounting sub-node;
- the business-end blockchain business sub-node is configured to create a matching transaction data structure for the target business and integrate the to-be-processed business data according to the transaction data structure to generate shared business data, and bill the sub-node to the business-end blockchain Sending a billing request, where the billing request carries the shared service data;
- the business-end blockchain accounting sub-node is configured to receive the accounting request, and automatically execute the calculation of the amount to be counted when the smart contract automatic execution conditions in the business-end blockchain accounting sub-node are met The task of generating the corresponding execution result, updating the shared business data and executing the accounting operation according to the execution result of the smart contract.
- the business-end blockchain accounting sub-node is also configured to collect updated shared service data according to preset conditions and send a service processing request to be counted to the server.
- the processing request carries the updated shared service data.
- the business-end blockchain business sub-node is further configured to create a transaction data structure based on an unused transaction output model (UTXO), and the transaction data structure includes a transaction ID, transaction input, and An output unit, the transaction input unit is attached with a signature unlocking script that uses the account balance, and the transaction output unit is attached with a lock script for the output balance to limit that only the designated account can use the corresponding UTXO unit.
- UTXO unused transaction output model
- the first method is called the "Unused Transaction Output (UTXO)” model
- the second method is the “Account/Balance” model.
- Bitcoin uses the “Unused Transaction Output” “Model, while Ethereum uses the “account/balance” model.
- a transaction data structure is created based on the "unused transaction output” model.
- each transaction will cost the amount of the previous transaction balance, and this amount is called “unused transaction Output”.
- a new "unused transaction output” will be generated after each transaction, and all "unused transaction outputs" will be stored in each fully synchronized node.
- the business-end blockchain accounting sub-node is further configured to calculate the pending transaction based on the business amount in the shared business data and the proportion of the amount to be counted in the business amount. Calculate the amount, determine an output account according to the shared service data and the account mapping table in the smart contract, and update the output unit of the shared service data based on the amount to be counted and the output account.
- the business-end blockchain accounting child node is also configured to monitor whether the state machine, things and/or trigger conditions in the smart contract meet the preset execution conditions, if the If any one of the state machine, things, and/or trigger conditions in the smart contract meets the preset execution condition, the smart contract reaches the automatic execution condition.
- the business-end blockchain business sub-node is also configured to obtain the calculation method of the amount to be counted, determine the mapping relationship between the transaction information and the accounting account, and based on the transaction information and accounting The mapping relationship between the accounts generates a corresponding account mapping table, the smart contract is created according to the calculation method of the amount to be counted and the account mapping table, and the smart contract is written into the blockchain network.
- the business-end blockchain accounting sub-node is also configured to obtain the calculation method of the amount to be counted, determine the mapping relationship between transaction information and accounting accounts, and based on the transaction information and The mapping relationship between the accounting accounts generates a corresponding account mapping table, the smart contract is created according to the calculation method of the amount to be counted and the account mapping table, and the smart contract is written into the blockchain network.
- both the business-end blockchain business sub-node and the business-end blockchain accounting sub-node can be used to generate smart contracts.
- the business-end blockchain node is also configured to transmit the updated shared business data signed with the private key to the blockchain network, and to transfer all the data in the blockchain network.
- the updated shared service data is validated, and when the updated shared service data is successfully validated, the updated shared service data is integrated into a hash block ID, and the The hash block ID spread to the entire network.
- the business-end blockchain accounting sub-node is further configured to collect shared business data according to preset conditions, and integrate the shared business data to generate business data to be counted.
- the business data to be counted is processed to generate a corresponding hash value, and a business processing request to be counted is sent to the server blockchain node, and the business processing request to be counted carries the business data to be counted and the corresponding hash value.
- the server blockchain node is further configured to obtain the business data to be counted and the corresponding hash value carried in the business processing request to be counted, based on the hash value Verify the validity of the business data to be counted, and if the verification is passed, calculate the total sum of the business data to be counted, and update the output unit in the business data to be counted according to the calculation result, And based on the calculation result, complete the business processing to be counted on the business end blockchain node.
- the server blockchain node is further configured to write the updated business data to be counted into the blockchain.
- the server-side blockchain node is also configured to transfer the updated business data to be counted signed with a private key into the blockchain network.
- Validity verification of the updated business data to be counted in is performed, and when the validity verification of the updated business data to be counted is successful, the updated business data to be counted is integrated into a hash block ID, and spread the hash block ID to the entire network.
- a distributed ledger jointly maintained by both parties is established between the business end and the server, and the transaction data generated by each transaction on the business end is calculated in real time on the ledger, which greatly improves the efficiency of data settlement.
- the use of blockchain can also ensure the immutability and accuracy of transaction data.
- Fig. 2 shows a structural block diagram of a computing device 200 according to an embodiment of the present specification.
- the components of the computing device 200 include but are not limited to a memory 210 and a processor 220.
- the processor 220 and the memory 210 are connected through a bus 230, and the database 250 is used to store data.
- the computing device 200 also includes an access device 240 that enables the computing device 200 to communicate via one or more networks 260.
- networks include public switched telephone network (PSTN), local area network (LAN), wide area network (WAN), personal area network (PAN), or a combination of communication networks such as the Internet.
- the access device 240 may include one or more of any type of wired or wireless network interface (for example, a network interface card (NIC)), such as IEEE802.11 wireless local area network (WLAN) wireless interface, global interconnection for microwave access ( Wi-MAX) interface, Ethernet interface, universal serial bus (USB) interface, cellular network interface, Bluetooth interface, near field communication (NFC) interface, etc.
- NIC network interface card
- the aforementioned components of the computing device 200 and other components not shown in FIG. 2 may also be connected to each other, for example, via a bus. It should be understood that the structural block diagram of the computing device shown in FIG. 2 is only for the purpose of example, and is not a limitation on the scope of this specification. Those skilled in the art can add or replace other components as needed.
- the computing device 200 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (for example, tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (for example, smart phones). ), wearable computing devices (for example, smart watches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs.
- the computing device 200 may also be a mobile or stationary server.
- the processor 220 may execute the steps in the blockchain-based data processing method shown in FIG. 3.
- FIG. 3 shows a flowchart of a blockchain-based data processing method according to an embodiment of the present specification, including steps 302 to 306.
- Step 302 Create a matching transaction data structure for the target business and integrate the to-be-processed business data according to the transaction data structure to generate shared business data.
- creating a matching transaction data structure for a target business includes:
- Table 1 includes transaction ID, input unit and output unit. Each transaction will generate a transaction ID.
- the input unit includes the source transaction ID, account, transaction type and amount.
- the source transaction ID is the source of the amount. In the insurance industry, the source transaction ID can be the policy number .
- the account is the income account of the amount.
- the transaction information includes user information and policy information.
- the output unit includes the account and amount. Taking the calculation of the policy commission as an example, the account of the output unit is the account that receives the commission, and the amount is the commission amount.
- the insurance industry is still taken as an example.
- User A purchases a health insurance product of insurance company C on Internet sales platform B.
- the transaction ID is A001
- the policy number is C00100001
- the premium is 3,000 yuan
- the insurance amount For 450,000
- the sales commission ratio of Internet sales platform B is 3% of the premium.
- Table 2 shows the shared business data generated by integrating the aforementioned business data generated by the transaction according to the transaction data structure.
- Step 304 When the information contained in the shared service data meets the automatic execution conditions of the smart contract of the business end blockchain node, the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, and the corresponding execution result is generated according to the The execution result updates the shared service data and performs accounting operations.
- the business data to be processed is integrated according to the transaction data structure to generate shared business data
- the business amount in the shared business data and the proportion of the amount to be counted in the business amount is calculated, and the output account is determined based on the shared business data and the account mapping table in the smart contract, and based on the amount to be counted.
- the statistical amount and the output account update the output unit of the shared service data.
- the insurance industry is still taken as an example.
- the amount to be counted is the commission generated by each transaction, and the business amount is the insured amount of each transaction.
- the business amount is the insured amount of each transaction.
- the insured amount is 3000, and the commission accounted for 3% of the insured amount, then the commission for this transaction can be calculated as 90.
- the output account can be determined as: B-health insurance-online sales-pending settlement.
- a new transaction data structure is generated.
- the business-end blockchain node will package and spread the N transaction data structures to other blockchain nodes, so that other blockchain nodes can treat the transaction data A consensus on the structure.
- the business-end blockchain node transmits the updated shared service data signed with the private key to the blockchain network, and verifies the validity of the updated shared service data transmitted to the blockchain network .
- the updated shared service data is integrated into a hash block ID, and the hash block ID is spread to the entire network.
- Step 306 Collect updated shared service data according to preset conditions and send a service processing request to be counted to the server blockchain node, where the service processing request to be counted carries the updated shared service data.
- collecting updated shared service data according to preset conditions and sending a service processing request to be counted to the server blockchain node can be implemented by the following steps:
- a service processing request to be counted is sent to the server blockchain node, where the service processing request to be counted carries the service data to be counted and the corresponding hash value.
- the preset condition is to generate three new transactions
- the Internet platform B generates three new transactions
- the three transaction data are integrated to generate business data to be counted.
- the business-end blockchain child node processes the business data to be counted to generate a corresponding hash value, and sends a business processing request to be counted to the server-end blockchain node.
- the business processing request to be counted Carry the business data to be counted and the corresponding hash value.
- the server blockchain node receives the service processing request to be counted, and verifies the validity of the bandpass and service data based on the hash value. In the case of passing the verification, calculate the total amount to be counted in the business data to be counted, and update the output unit in the business data to be counted according to the calculation result.
- the updated result is shown in Table 5 and is based on The calculation result completes the business processing to be counted on the business end blockchain node.
- the insurance company C transfers the corresponding virtual currency to the corresponding account according to the account and amount of the output unit in Table 5, performs accounting operations, and writes the updated business data to be counted into the blockchain.
- the preset condition is to generate 3 new transactions.
- the preset condition can be determined according to actual needs, and is not limited here.
- the business-end blockchain node before the business-end blockchain node creates a matching transaction data structure for the target business, it first generates a smart contract.
- the smart contract includes the calculation method of the amount to be counted and the account mapping table, and the smart contract is generated.
- the amount to be counted is the commission
- the specific way to write the smart contract into the blockchain network is: transfer the updated shared service data signed with the private key into the blockchain network, The validity of the updated shared service data in.
- the updated shared service data is integrated into a hash block ID, and the hash block ID is spread to the entire network.
- the transaction data structure is created based on the UXTO model, and each transaction data is integrated according to the transaction data structure, which provides convenience for the insurance company to calculate the total commission, and the unlocking script of the model in the input and output unit can also
- the business-end blockchain node will write the transaction data into the blockchain after calculating the amount to be counted for each transaction data, and the server-end blockchain node will treat the pending statistics in the business data. After the calculation of the total amount of statistics is completed, the business data to be counted is written into the blockchain to ensure that the data cannot be tampered with.
- FIG. 4 shows a flowchart of a blockchain-based data processing method according to an embodiment of this specification, including steps 402 to 406.
- Step 402 Receive a service processing request, where the service processing request carries shared service data.
- the business end blockchain node creates a transaction data structure based on the unused transaction output model (UTXO) for the target business, and the transaction data structure includes transaction ID, transaction input and output units.
- the service data to be processed is integrated according to the transaction data structure to generate shared service data, and a service processing request is sent to the server blockchain node, and the service processing request carries the shared service data.
- the server-side blockchain node before receiving the business processing request, the server-side blockchain node generates a smart contract according to which the smart contract includes the calculation method of the amount to be counted and the account mapping table.
- the smart contract generation process can be performed by the following steps achieve:
- the updated shared service data signed with a private key is transferred to the blockchain network, and the validity of the updated shared service data transferred to the blockchain network is verified.
- the updated shared service data is integrated into a hash block ID, and the hash block ID is spread to the entire network.
- Step 404 When the information contained in the shared service data meets the automatic execution conditions of the smart contract of the server blockchain node, the task of calculating the amount to be counted is automatically executed, the corresponding execution result is generated, and the corresponding execution result is generated according to the The execution result updates the shared service data and performs accounting operations.
- the server blockchain node monitors whether the state machine, things and/or trigger conditions in the smart contract of the server blockchain node meet the preset execution conditions. If any one of the state machine, things, and/or trigger conditions in the smart contract meets the preset execution conditions, the smart contract meets the automatic execution conditions and automatically executes the task of calculating the amount to be counted.
- the business amount in the shared business data and the proportion of the amount to be counted in the business amount is calculated, and the output account is determined based on the shared business data and the account mapping table in the smart contract, and based on the amount to be counted.
- the statistical amount and the output account update the output unit of the shared service data and keep accounts.
- a new transaction data structure is generated.
- the server-side blockchain node will package and spread the N transaction data structures to other blockchain nodes, so that other blockchain nodes can treat the transaction data A consensus on the structure.
- the server blockchain node transfers the updated shared service data signed with the private key into the blockchain network, and verifies the validity of the updated shared service data transferred to the blockchain network .
- the updated shared service data is integrated into a hash block ID, and the hash block ID is spread to the entire network.
- Step 406 Collect updated shared service data according to preset conditions and calculate the total amount to be counted in the updated shared service data.
- the server blockchain node collects updated shared business data according to preset conditions, integrates the updated shared business data to generate business data to be counted, and calculates the business data to be counted The sum of the amounts to be counted. Update the output unit in the business data to be counted according to the calculation result, complete the business processing to be counted on the blockchain node of the business end based on the calculation result, and combine the updated business data to be counted Write to the blockchain.
- the method for writing the updated business data to be counted into the blockchain is: the updated business data to be counted signed with a private key is transferred to the blockchain network, and the data is transferred to the blockchain network.
- Validity verification of the updated business data to be counted in is performed, and when the validity verification of the updated business data to be counted is successful, the updated business data to be counted is integrated into a hash block ID, and spread the hash block ID to the entire network.
- each newly generated transaction data is transmitted to the blockchain node in real time
- the commission calculation ensures real-time performance and spreads the calculation results to other blockchain nodes to realize the immutability of data.
- FIG. 5 shows a schematic diagram of interaction in an application scenario of an insurance business alliance chain according to a blockchain-based data processing method provided according to an embodiment of the present specification, including steps 502 to 516.
- Step 502 The Internet sales platform receives the user's insurance application request.
- the Internet platform after receiving the user's insurance request, the Internet platform sells the corresponding insurance to the user and records related transaction data.
- Step 504 The Internet sales platform generates shared business data.
- the Internet sales platform before receiving the user’s insurance request, creates a transaction data structure based on the unused transaction output model (UTXO) for the target business.
- the transaction data structure includes transaction ID, transaction input, and Output unit. After a new transaction occurs, the transaction data is integrated according to the transaction data structure to generate shared business data.
- Step 506 The Internet sales platform sends an accounting request to the accounting node.
- Step 508 The accounting node updates the shared service data.
- the billing request carries shared service data to monitor whether the state machine, things and/or trigger conditions in the smart contract of the billing node meet the preset execution conditions. If any one of the state machine, things, and/or trigger conditions in the smart contract meets the preset execution conditions, the smart contract meets the automatic execution conditions, and the task of calculating commissions is automatically executed according to the shared business Calculate the commission based on the insured amount in the data and the percentage of the commission in the insured amount, determine the billing account based on the shared business data and the account mapping table in the smart contract, and based on the commission and billing account pair
- the output unit of the shared service data is updated. When the number of new transaction data structures reaches the preset threshold N, the accounting node packs and spreads the N transaction data structures to other blockchain nodes, so that other blockchain nodes reach a consensus on the transaction data structure .
- the accounting node may be any node on the insurance business alliance chain, where the insurance business alliance chain is constructed based on multiple nodes of an insurance company and an Internet sales platform.
- Step 510 The accounting node sends a request for processing the business to be counted to the insurance company.
- the service processing request to be counted is the total commission settlement request.
- the accounting node integrates the data of the three pending transactions into the business data to be counted, and sends it to the insurance company Processing request of pending settlement business.
- Step 512 The insurance company calculates the total amount to be counted.
- Step 514 The insurance company sends an accounting request to the accounting node.
- Step 516 The insurance company transfers the commission to the Internet sales platform.
- the insurance company calculates the sum of 3 commissions in the business data to be counted, updates the output unit in the business data to be counted according to the calculation result, and sends the calculation result to the accounting node for recording According to the calculation results, the corresponding amount of virtual currency is transferred to the Internet platform.
- a distributed ledger jointly maintained by both parties is established between the Internet sales platform and the insurance company, and the transaction data generated by each transaction of the Internet sales platform is calculated in real time on the accounting node, which greatly increases the commission
- the efficiency of settlement, the use of blockchain can also ensure the immutability and accuracy of transaction data.
- An embodiment of the present specification also provides a computing device, including a memory, a processor, and computer instructions stored on the memory and capable of running on the processor.
- the processor implements the block-based The steps of the chain of data processing methods.
- An embodiment of the present application also provides a computer-readable storage medium that stores computer instructions that, when executed by a processor, implement the steps of the blockchain-based data processing method described above.
- the computer instructions include computer program codes, and the computer program codes may be in the form of source code, object code, executable files, or some intermediate forms.
- the computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signal, telecommunications signal, and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately added or deleted in accordance with the requirements of the legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to the legislation and patent practice, the computer-readable medium Does not include electrical carrier signals and telecommunication signals.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
一种基于区块链的数据处理系统、方法、计算设备及存储介质,其中所述基于区块链的数据处理系统包括:区块链(100)上的业务端区块链节点(102)和服务端区块链节点(104);业务端区块链节点(102)为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,自动执行计算待统计金额的任务,生成对应的执行结果,根据所述执行结果对所述共享业务数据进行更新并执行记账操作,根据预设条件采集更新后的共享业务数据并向服务端区块链节点(104)发送待统计业务处理请求;服务端区块链节点(104)接收所述待统计业务处理请求,计算所述更新后的共享业务数据中的待统计金额总和。
Description
本说明书涉及区块链技术领域,特别涉及一种基于区块链的数据处理系统、方法、计算设备及存储介质。
随着经济的发展,保险已经成为生活中重要的组成部分,如今保险的销售方式越来越多样化,例如,许多保险公司会委托第三方服务机构代销保险,这样保险公司与第三方服务机构间就需要进行保险佣金结算,而现有技术中,保险公司与第三方服务平台之间在结算佣金之前,双发需对交易数据达成一致,即保险公司与第三方服务平台间需要对一定周期内的交易数据进行核对,以便发现同一笔交易在不同机构是否存在数据差异。
现有技术中,机构间的数据处理方法为第三方服务平台将预设时间段内产生的交易数据打包发送至保险公司,保险公司对交易数据进行验证,在验证通过后,再进行佣金结算,但是现有技术中所采用的佣金结算方法开发成本较高,第三方服务平台需将交易数据从核心业务系统导出,以文件传输或其他方式发送至保险公司进行数据核对,整个过程耗时较长,时效性较差,并且未来如果某一方机构对交易数据发生争议,缺少一个双方都能认可的仲裁机制。
发明内容
有鉴于此,本说明书实施例提供了一种基于区块链的数据处理系统、方法、计算设备及存储介质,以解决现有技术中存在的技术缺陷。
根据本说明书实施例的第一方面,提供了一种基于区块链的数据处理系统,包括:
区块链上的业务端区块链节点和服务端区块链节点;
业务端区块链节点,被配置为为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,在所述共享业务数据包含的信息满足所述业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据所述执行结果对所述共享业务数据进行更新 并执行记账操作,根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据;
服务端区块链节点,被配置为接收所述待统计业务处理请求,计算所述更新后的共享业务数据中的待统计金额总和。
可选地,业务端区块链节点包括:业务端区块链业务子节点和业务端区块链记账子节点;
业务端区块链业务子节点,被配置为为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,向业务端区块链记账子节点发送记账请求,所述记账请求中携带有所述共享业务数据;
业务端区块链记账子节点,被配置为接收所述记账请求,在满足所述业务端区块链记账子节点中的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据智能合约执行结果对所述共享业务数据进行更新并执行记账操作。
可选地,业务端区块链记账子节点,还被配置为根据预设条件采集更新后的共享业务数据并向服务端发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
可选地,业务端区块链业务子节点,进一步被配置为创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元,所述交易输入单元中附带有使用账户余额的签名解锁脚本,所述交易输出单元中附带有输出余额的锁定脚本,用于限定只有指定账户可使用与之对应的UTXO单元。
可选地,业务端区块链记账子节点,进一步被配置为根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,并根据所述共享业务数据以及智能合约中的账户映射表确定输出账户,基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新。
可选地,业务端区块链记账子节点,还被配置为监控所述智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件,若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件。
可选地,业务端区块链业务子节点,还被配置为获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生 成对应的账户映射表,根据待统计金额的计算方式以及所述账户映射表创建所述智能合约,并将所述智能合约写入区块链网络。
可选地,业务端区块链记账子节点,还被配置为获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表,根据待统计金额的计算方式以及所述账户映射表创建所述智能合约,并将所述智能合约写入区块链网络。
可选地,业务端区块链节点,还被配置为将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证,当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
可选地,业务端区块链记账子节点,进一步被配置为根据预设条件采集共享业务数据,并将所述共享业务数据进行整合生成待统计业务数据,对所述待统计业务数据进行处理生成对应的哈希值,向所述服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述待统计业务数据以及对应的哈希值。
可选地,服务端区块链节点,进一步被配置为获取所述待统计业务处理请求中携带的所述待统计业务数据以及对应的哈希值,基于所述哈希值对所述待统计业务数据进行有效性验证,在验证通过的情况下,计算所述待统计业务数据中的待统计金额总和,根据计算结果对所述待统计业务数据中的输出单元进行更新,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理。
可选地,服务端区块链节点,还被配置为将所述更新后的待统计业务数据写入区块链中。
根据本说明书实施例的另一方面,提供了一种基于区块链的数据处理方法,应用于业务端区块链节点,包括:
为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据;
在所述共享业务数据包含的信息满足所述业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新并执行记账操作;
根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务 处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
可选地,为目标业务创建匹配的交易数据结构包括:
创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元。
可选地,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新包括:
根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,并根据所述共享业务数据以及智能合约中的账户映射表确定输出账户;
基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新。
可选地,为目标业务创建匹配的交易数据结构之前,还包括:
获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表;
根据待统计金额的计算方式以及所述账户映射表创建所述智能合约;
将所述智能合约写入区块链网络。
可选地,自动执行计算待统计金额的任务之前,还包括:
监控所述业务端区块链节点的智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件;
若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件。
可选地,将所述智能合约写入区块链网络包括:
将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证,当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
可选地,根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求包括:
根据预设条件采集共享业务数据;
将所述共享业务数据进行整合生成待统计业务数据,对所述待统计业务数据进行处理生成对应的哈希值;
向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述待统计业务数据以及对应的哈希值。
根据本说明书实施例的另一方面,提供了一种基于区块链的数据处理方法,应用于服务端区块链节点,包括:
接收业务处理请求,所述业务处理请求中携带有共享业务数据;
在所述共享业务数据包含的信息满足所述服务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新并执行记账操作;
根据预设条件采集更新后的共享业务数据并计算所述更新后的共享业务数据中的待统计金额总和。
可选地,计算所述更新后的共享业务数据中的待统计金额总和之后,还包括:
根据计算结果对所述待统计业务数据中的输出单元进行更新,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理;
将所述更新后的待统计业务数据写入区块链中。
根据本说明书实施例的另一方面,提供了一种计算设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令,所述处理器执行所述指令时实现所述基于区块链的数据处理方法的步骤。
根据本说明书实施例的另一方面,提供了一种计算机可读存储介质,其存储有计算机指令,该指令被处理器执行时实现所述基于区块链的数据处理方法的步骤。
本说明书实施例中,通过业务端区块链节点为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,在满足业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据所述执行结果对所述共享业务数据进行更新并执行记账操作,根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求,服务端区块链节点接收所述待统计业务处理请求,计算所述更新后的共享业务数据中的待统计金额总和,本说明书实施例中,在业务端和服务端之间建立双方共同维护的分 布式账本,并对业务端每笔交易产生的交易数据在账本上进行实时计算,大幅提高了数据结算的效率,利用区块链同时能够保证交易数据的不可篡改性和准确性。
图1是本申请实施例提供的基于区块链的数据处理系统的示意图;
图2是本申请实施例提供的计算设备的结构框图;
图3是本申请实施例提供的基于区块链的数据处理方法的流程图;
图4是本申请实施例提供的基于区块链的数据处理方法的流程图;
图5是本申请实施例提供的基于区块链的数据处理方法在保险业务联盟链的应用场景中的交互示意图。
在下面的描述中阐述了很多具体细节以便于充分理解本申请。但是本申请能够以很多不同于在此描述的其它方式来实施,本领域技术人员可以在不违背本申请内涵的情况下做类似推广,因此本申请不受下面公开的具体实施的限制。
在本说明书一个或多个实施例中使用的术语是仅仅出于描述特定实施例的目的,而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。还应当理解,本说明书一个或多个实施例中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解,尽管在本说明书一个或多个实施例中可能采用术语第一、第二等来描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如,在不脱离本说明书一个或多个实施例范围的情况下,第一也可以被称为第二,类似地,第二也可以被称为第一。取决于语境,如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
首先,对本发明一个或多个实施例涉及的名词术语进行解释。
未使用交易输出模型(Unspent Transaction Output):比特币交易的基本单位,简称为UTXO,UTXO是不能再分割、被所有者锁住或记录于区块链中的并被整个网络识 别成货币单位的一定量的比特币货币。
在本申请中,提供了一种基于区块链的数据处理系统、方法、计算设备及存储介质,在下面的实施例中逐一进行详细说明。
图1示出了本说明书一实施例的基于区块链的数据处理系统的示意图,包括:
区块链100上的业务端区块链节点102和服务端区块链节点104。
业务端区块链节点102,被配置为为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,在所述共享业务数据包含的信息满足所述业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据所述执行结果对所述共享业务数据进行更新并执行记账操作,根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
服务端区块链节点104,被配置为接收所述待统计业务处理请求,计算所述更新后的共享业务数据中的待统计金额总和。
本说明书一实施例中,所述业务端区块链节点包括:业务端区块链业务子节点和业务端区块链记账子节点;
业务端区块链业务子节点,被配置为为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,向业务端区块链记账子节点发送记账请求,所述记账请求中携带有所述共享业务数据;
业务端区块链记账子节点,被配置为接收所述记账请求,在满足所述业务端区块链记账子节点中的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据智能合约执行结果对所述共享业务数据进行更新并执行记账操作。
本说明书一实施例中,所述业务端区块链记账子节点,还被配置为根据预设条件采集更新后的共享业务数据并向服务端发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
本说明书一实施例中,所述业务端区块链业务子节点,进一步被配置为创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元,所述交易输入单元中附带有使用账户余额的签名解锁脚本,所述交 易输出单元中附带有输出余额的锁定脚本,用于限定只有指定账户可使用与之对应的UTXO单元。
区块链网络中使用两种不同的记录模式,第一种方法称为“未使用交易输出(UTXO)”模型,第二种方法是“账户/余额”模型,比特币使用“未使用交易输出”模型,而以太坊使用“账户/余额”模型。本说明书一实施例中,基于所述“未使用交易输出”模型创建交易数据结构,其中,在比特币中,每笔交易都会花费之前交易所结余的金额,这个金额就称作“未使用交易输出”。每次交易之后都会产生新的“未使用交易输出”,所有的“未使用交易输出”都会保存在每个完全同步的节点中。
本说明书一实施例中,所述业务端区块链记账子节点,进一步被配置为根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,并根据所述共享业务数据以及智能合约中的账户映射表确定输出账户,基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新。
本说明书一实施例中,所述业务端区块链记账子节点,还被配置为监控所述智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件,若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件。
本说明书一实施例中,所述业务端区块链业务子节点,还被配置为获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表,根据待统计金额的计算方式以及所述账户映射表创建所述智能合约,并将所述智能合约写入区块链网络。
本说明书一实施例中,所述业务端区块链记账子节点,还被配置为获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表,根据待统计金额的计算方式以及所述账户映射表创建所述智能合约,并将所述智能合约写入区块链网络。
本说明书一实施例中,业务端区块链业务子节点和业务端区块链记账子节点均可用于生成智能合约。
本说明书一实施例中,所述业务端区块链节点,还被配置为将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证,当所述更新后的共享业务数据的有效性验证成功后,将所述更新后 的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
本说明书一实施例中,所述业务端区块链记账子节点,进一步被配置为根据预设条件采集共享业务数据,并将所述共享业务数据进行整合生成待统计业务数据,对所述待统计业务数据进行处理生成对应的哈希值,向所述服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述待统计业务数据以及对应的哈希值。
本说明书一实施例中,所述服务端区块链节点,进一步被配置为获取所述待统计业务处理请求中携带的所述待统计业务数据以及对应的哈希值,基于所述哈希值对所述待统计业务数据进行有效性验证,在验证通过的情况下,计算所述待统计业务数据中的待统计金额总和,根据计算结果对所述待统计业务数据中的输出单元进行更新,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理。
本说明书一实施例中,所述服务端区块链节点,还被配置为将所述更新后的待统计业务数据写入区块链中。
本书明书一实施例中,所述服务端区块链节点,还被配置为将用私钥签名的更新后的待统计业务数据传入区块链网络中,对传入区块链网络中的所述更新后的待统计业务数据进行有效性验证,当所述更新后的待统计业务数据的有效性验证成功后,将所述更新后的待统计业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
本说明书一实施例中,在业务端和服务端之间建立双方共同维护的分布式账本,并对业务端每笔交易产生的交易数据在账本上进行实时计算,大幅提高了数据结算的效率,利用区块链同时能够保证交易数据的不可篡改性和准确性。
图2示出了根据本说明书一实施例的计算设备200的结构框图。该计算设备200的部件包括但不限于存储器210和处理器220。处理器220与存储器210通过总线230相连接,数据库250用于保存数据。
计算设备200还包括接入设备240,接入设备240使得计算设备200能够经由一个或多个网络260通信。这些网络的示例包括公用交换电话网(PSTN)、局域网(LAN)、广域网(WAN)、个域网(PAN)或诸如因特网的通信网络的组合。接入设备240可以包括有线或无线的任何类型的网络接口(例如,网络接口卡(NIC))中的一个或多个,诸如IEEE802.11无线局域网(WLAN)无线接口、全球微波互联接入(Wi-MAX)接口、以太网接口、通用串行总线(USB)接口、蜂窝网络接口、蓝牙接口、近场通信(NFC)接口,等等。
在本说明书的一个实施例中,计算设备200的上述部件以及图2中未示出的其他部件也可以彼此相连接,例如通过总线。应当理解,图2所示的计算设备结构框图仅仅是出于示例的目的,而不是对本说明书范围的限制。本领域技术人员可以根据需要,增添或替换其他部件。
计算设备200可以是任何类型的静止或移动计算设备,包括移动计算机或移动计算设备(例如,平板计算机、个人数字助理、膝上型计算机、笔记本计算机、上网本等)、移动电话(例如,智能手机)、可佩戴的计算设备(例如,智能手表、智能眼镜等)或其他类型的移动设备,或者诸如台式计算机或PC的静止计算设备。计算设备200还可以是移动式或静止式的服务器。
其中,处理器220可以执行图3所示基于区块链的数据处理方法中的步骤。图3示出了根据本说明书一实施例的基于区块链的数据处理方法的流程图,包括步骤302至步骤306。
步骤302:为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据。
本说明书一实施例中,为目标业务创建匹配的交易数据结构包括:
创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元。
以保险行业为例,创建的交易数据结构如表1所示。
表1
表1包括交易ID、输入单元和输出单元。每发生一笔交易,均会产生一个交易ID,输入单元包括来源交易ID、账户、交易类型以及金额,其中,来源交易ID即为金额的 来源,在保险行业中,来源交易ID可以是保单号。账户即为金额的收入账户,交易信息包括用户信息和保单信息,输出单元包括账户和金额,以计算保单佣金为例,输出单元的账户即为收佣金的账户,金额即为佣金金额。
本说明书一实施例中,仍以保险行业为例,用户A在互联网销售平台B购买了一份保险公司C的健康险产品,交易ID为A001,保单号为C00100001,保费为3000元,保额为450000,互联网销售平台B的销售佣金比例为保费的3%。
将该笔交易产生的上述业务数据按照所述交易数据结构进行整合生成的共享业务数据如表2所示。
表2
步骤304:在所述共享业务数据包含的信息满足所述业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新并执行记账操作。
本说明书一实施例中,将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据之后,监控业务端区块链节点的智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件。若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件,自动执行计算待统计金额的任务,根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,根据所述共享业务数据以及智能合约中的账户映射表确定输出账户,并基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新。
本说明书一实施例中,仍以保险行业为例,待统计金额即为每笔交易产生的佣金,业务额即为每笔交易的保额,以步骤302中的表2为例,共享业务数据中的保额为3000, 佣金在保额中的占比为3%,则计算可得该笔交易产生的佣金为90。根据智能合约中的账户映射表可确定输出账户为:B-健康险-网销-待结算。
根据佣金金额和输出账户对表2进行更新得到的结果如表3所示。
表3
本说明书一实施例中,每发生一笔交易,均产生一个新的交易数据结构。在新的交易数据结构的数量达到预设阈值N时,业务端区块链节点将所述N个交易数据结构打包扩散至其他区块链节点,以使其他区块链节点对所述交易数据结构达成共识。
具体地,业务端区块链节点将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证。当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
步骤306:根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
本说明书一实施例中,根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求可由以下步骤实现:
根据预设条件采集共享业务数据;
将所述共享业务数据进行整合生成待统计业务数据,对所述待统计业务数据进行处理生成对应的哈希值;
向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述待统计业务数据以及对应的哈希值。
本说明书一实施例中,假设预设条件为生成3笔新的交易,互联网平台B产生三笔新的交易,则将这3笔交易数据整合生成待统计业务数据。
仍以保险行业为例,3笔交易数据整合生成的待统计业务数据如表4所示。
表4
本说明书一实施例中,业务端区块链子节点将待统计业务数据进行处理生成对应的哈希值,并向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有待统计业务数据及对应的哈希值。服务端区块链节点接收所述待统计业务处理请求,基于所述哈希值对所述带通及业务数据进行有效性验证。在验证通过的情况下,计算所述待统计业务数据中的待统计金额总和,根据计算结果对所述待统计业务数据中的输出单元进行更新,更新后的结果如表5所示,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理。
表5
保险公司C根据表5中输出单元的账户及金额向对应的账户转入相应的虚拟货币,并执行记账操作,将所述更新后的待统计业务数据写入区块链中。
本说明书一实施例中,预设条件为生成3笔新的交易,实际应用中,所述预设条件可根据实际需要来确定,在此不做限制。
本说明书一实施例中,业务端区块链节点为目标业务创建匹配的交易数据结构之前,先生成智能合约,所述智能合约中包括待统计金额的计算方式以及账户映射表,生成智能合约的过程具体可由以下步骤实现:
获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表;
根据待统计金额的计算方式以及所述账户映射表创建所述智能合约;
将所述智能合约写入区块链网络。
本说明书一实施例中,以保险行业为例,待统计金额即为佣金,待统计金额的计算方式即佣金在保额中的占比。确定交易信息和记账账户间的映射关系即根据交易信息确定该笔交易信息对应的记账账户,假设某笔交易的部分信息为:用户A在互联网销售平台B购买了一份保险公司C的健康险产品,则可确定该笔交易对应的记账账户为互联网销售平台B-健康险-网销-待结算佣金。
本说明书一实施例中,将所述智能合约写入区块链网络的具体方式为:将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证。当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
本说明书一实施例中,基于UXTO模型创建交易数据结构,并将每笔交易数据按照交易数据结构整合,为保险公司对佣金总额计算提供了方便,而且该模型在输入输出单元的解锁脚本还可以为用户提供更多的隐私性,业务端区块链节点对每一笔交易数据的待统计金额计算完成后将交易数据写入区块链,服务端区块链节点对待统计业务数据中的待统计金额总和计算完成后将待统计业务数据写入区块链,保证了数据的不可篡改性。
图4示出了本说明书一实施例的基于区块链的数据处理方法的流程图,包括步骤402至步骤406。
步骤402:接收业务处理请求,所述业务处理请求中携带有共享业务数据。
本说明书一实施例中,由业务端区块链节点为目标业务创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元。将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,向服务端区块链节点发送业务处理请求,所述业务处理请求中携带有所述共享业务数据。
本说明书一实施例中,在接收业务处理请求之前,服务端区块链节点根据生成智能合约,所述智能合约中包括待统计金额的计算方式以及账户映射表,智能合约的生成过程可由以下步骤实现:
获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表;
根据待统计金额的计算方式以及所述账户映射表创建所述智能合约;
将所述智能合约写入区块链网络。
本说明书一实施例中,将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证。当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
步骤404:在所述共享业务数据包含的信息满足所述服务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新并执行记账操作。
本说明书一实施例中,服务端区块链节点接收业务处理请求之后,监控服务端区块链节点的智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件。若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件,自动执行计算待统计金额的任务,根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,根据所述共享业务数据以及智能合约中的账户映射表确定输出账户,并基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新并记账。
本说明书一实施例中,每发生一笔交易,均产生一个新的交易数据结构。在新的交易数据结构的数量达到预设阈值N时,服务端区块链节点将所述N个交易数据结构打包扩散至其他区块链节点,以使其他区块链节点对所述交易数据结构达成共识。
具体地,服务端区块链节点将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证。当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
步骤406:根据预设条件采集更新后的共享业务数据并计算所述更新后的共享业务数据中的待统计金额总和。
本说明书一实施例中,服务端区块链节点根据预设条件采集更新后的共享业务数据,将所述更新后的共享业务数据进行整合生成待统计业务数据,计算所述待统计业务数据中的待统计金额总和。根据计算结果对所述待统计业务数据中的输出单元进行更新,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理,并将所述更新后的待统计业务数据写入区块链中。
具体地,将所述更新后的待统计业务数据写入区块链的方法为:将用私钥签名的更新后的待统计业务数据传入区块链网络中,对传入区块链网络中的所述更新后的待统计业务数据进行有效性验证,当所述更新后的待统计业务数据的有效性验证成功后,将所述更新后的待统计业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
本说明书一实施例中,通过将每笔新产生的交易数据实时传送到区块链节点
进行佣金计算,保证了实时性,并且将计算结果扩散到其他区块链节点,实现了数据的不可篡改。
图5示出了根据本说明书一实施例提供的基于区块链的数据处理方法在保险业务联盟链的应用场景中的交互示意图,包括步骤502至步骤516。
步骤502:互联网销售平台接收用户的投保请求。
本说明书一实施例中,互联网平台接收用户的投保请求后,向用户售出对应的保险并记录相关的交易数据。
步骤504:互联网销售平台生成共享业务数据。
本说明书一实施例中,互联网销售平台在接收用户的投保请求之前,为目标业务创建创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元。有新的交易发生后,将交易数据按照所述交易数据结构进行整合生成共享业务数据。
步骤506:互联网销售平台向记账节点发送记账请求。
步骤508:记账节点更新共享业务数据。
本说明书一实施例中,记账请求中携带有共享业务数据,监控记账节点的智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件。若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件,自动执行计算佣金的任务,根据所述共享业务数据中的保额以及佣金在所述保额中的占比计算所述佣金,根据所述共享业务数据以及智能合约中的账户映射表确定记账账户,并基于所述佣金及记账账户对所述共享业务数据的输出单元进行更新。在新的交易数据结构的数量达到预设阈值N时,记账节点将所述N个交易数据结构打包扩散至其他区块链节点,以使其他区块链节点对所述交易数据结构达成共识。
本说明书一实施例中,记账节点可以是保险业务联盟链上的任意一个节点,其中,所述保险业务联盟链是基于保险公司和互联网销售平台的多个节点构建而成。
步骤510:记账节点向保险公司发送待统计业务处理请求。
本说明书一实例中,待统计业务处理请求即佣金总额结算请求,以预设条件为3笔交易为例,记账节点将三笔待结算交易数据整合为待统计业务数据,并向保险公司发送待结算业务处理请求。
步骤512:保险公司计算待统计金额总和。
步骤514:保险公司向记账节点发送记账请求。
步骤516:保险公司向互联网销售平台转入佣金。
本说明书一实施例中,保险公司计算待统计业务数据中的3笔佣金的总和,根据计算结果对所述待统计业务数据中的输出单元进行更新,并将计算结果发送至记账节点进行记账,根据计算结果向互联网平台转入相应数量的虚拟货币。
本说明书一实施例中,在互联网销售平台和保险公司之间建立双方共同维护的分布式账本,并对互联网销售平台每笔交易产生的交易数据在记账节点上进行实时计算,大幅提高了佣金结算的效率,利用区块链同时能够保证交易数据的不可篡改性和准确性。
本说明书一实施例中还提供一种计算设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令,所述处理器执行所述指令时实现所述的基于区块链的数据处理方法的步骤。
本申请一实施例还提供一种计算机可读存储介质,其存储有计算机指令,该指令被处理器执行时实现如前所述基于区块链的数据处理方法的步骤。
上述为本实施例的一种计算机可读存储介质的示意性方案。需要说明的是,该存储介质的技术方案与上述的基于区块链的数据处理方法的技术方案属于同一构思,存储介质的技术方案未详细描述的细节内容,均可以参见上述基于区块链的数据处理方法的技术方案的描述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下,在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外,在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中,多任务处理和并行处理也是 可以的或者可能是有利的。
所述计算机指令包括计算机程序代码,所述计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括:能够携带所述计算机程序代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是,所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减,例如在某些司法管辖区,根据立法和专利实践,计算机可读介质不包括电载波信号和电信信号。
需要说明的是,对于前述的各方法实施例,为了简便描述,故将其都表述为一系列的动作组合,但是本领域技术人员应该知悉,本申请并不受所描述的动作顺序的限制,因为依据本申请,某些步骤可以采用其它顺序或者同时进行。其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定都是本申请所必须的。
在上述实施例中,对各个实施例的描述都各有侧重,某个实施例中没有详述的部分,可以参见其它实施例的相关描述。
以上公开的本申请优选实施例只是用于帮助阐述本申请。可选实施例并没有详尽叙述所有的细节,也不限制该发明仅为所述的具体实施方式。显然,根据本说明书的内容,可作很多的修改和变化。本说明书选取并具体描述这些实施例,是为了更好地解释本申请的原理和实际应用,从而使所属技术领域技术人员能很好地理解和利用本申请。本申请仅受权利要求书及其全部范围和等效物的限制。
Claims (23)
- 一种基于区块链的数据处理系统,其特征在于,包括:区块链上的业务端区块链节点和服务端区块链节点;业务端区块链节点,被配置为为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,在所述共享业务数据包含的信息满足所述业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据所述执行结果对所述共享业务数据进行更新并执行记账操作,根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据;服务端区块链节点,被配置为接收所述待统计业务处理请求,计算所述更新后的共享业务数据中的待统计金额总和。
- 如权利要求1所述的系统,其特征在于,所述业务端区块链节点包括:业务端区块链业务子节点和业务端区块链记账子节点;业务端区块链业务子节点,被配置为为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据,向业务端区块链记账子节点发送记账请求,所述记账请求中携带有所述共享业务数据;业务端区块链记账子节点,被配置为接收所述记账请求,在满足所述业务端区块链记账子节点中的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,根据智能合约执行结果对所述共享业务数据进行更新并执行记账操作。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链记账子节点,还被配置为根据预设条件采集更新后的共享业务数据并向服务端发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链业务子节点,进一步被配置为创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元,所述交易输入单元中附带有使用账户余额的签名解锁脚本,所述交易输出单元中附带有输出余额的锁定脚本,用于限定只有指定账户可使用与之对应的UTXO单元。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链记账子节点,进一步被配置为根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,并根据所述共享业务数据以及智能合约中的账户映射表确定输出 账户,基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链记账子节点,还被配置为监控所述智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件,若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链业务子节点,还被配置为获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表,根据待统计金额的计算方式以及所述账户映射表创建所述智能合约,并将所述智能合约写入区块链网络。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链记账子节点,还被配置为获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表,根据待统计金额的计算方式以及所述账户映射表创建所述智能合约,并将所述智能合约写入区块链网络。
- 如权利要求1所述的系统,其特征在于,所述业务端区块链节点,还被配置为将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证,当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
- 如权利要求2所述的系统,其特征在于,所述业务端区块链记账子节点,进一步被配置为根据预设条件采集共享业务数据,并将所述共享业务数据进行整合生成待统计业务数据,对所述待统计业务数据进行处理生成对应的哈希值,向所述服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述待统计业务数据以及对应的哈希值。
- 如权利要求1所述的系统,其特征在于,所述服务端区块链节点,进一步被配置为获取所述待统计业务处理请求中携带的所述待统计业务数据以及对应的哈希值,基于所述哈希值对所述待统计业务数据进行有效性验证,在验证通过的情况下,计算所述待统计业务数据中的待统计金额总和,根据计算结果对所述待统计业务数据中的输出单元进行更新,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理。
- 如权利要求1所述的系统,其特征在于,所述服务端区块链节点,还被配置为将所述更新后的待统计业务数据写入区块链中。
- 一种基于区块链的数据处理方法,其特征在于,应用于业务端区块链节点,包括:为目标业务创建匹配的交易数据结构并将待处理业务数据按照所述交易数据结构进行整合生成共享业务数据;在所述共享业务数据包含的信息满足所述业务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新并执行记账操作;根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述更新后的共享业务数据。
- 如权利要求13所述的方法,其特征在于,所述为目标业务创建匹配的交易数据结构包括:创建基于未使用交易输出模型(UTXO)的交易数据结构,所述交易数据结构中包括交易ID、交易输入和输出单元。
- 如权利要求13所述的方法,其特征在于,所述自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新包括:根据所述共享业务数据中的业务额以及待统计金额在所述业务额中的占比计算所述待统计金额,并根据所述共享业务数据以及智能合约中的账户映射表确定输出账户;基于所述待统计金额及输出账户对所述共享业务数据的输出单元进行更新。
- 如权利要求13所述的方法,其特征在于,所述为目标业务创建匹配的交易数据结构之前,还包括:获取待统计金额的计算方式,确定交易信息和记账账户间的映射关系,并根据所述交易信息和记账账户间的映射关系生成对应的账户映射表;根据待统计金额的计算方式以及所述账户映射表创建所述智能合约;将所述智能合约写入区块链网络。
- 如权利要求13所述的方法,其特征在于,所述自动执行计算待统计金额的任务之前,还包括:监控所述业务端区块链节点的智能合约中的状态机、事物和/或触发条件是否满足预设的执行条件;若所述智能合约中的状态机、事物和/或触发条件中的任意一项满足预设的执行条件,则所述智能合约达到自动执行条件。
- 如权利要求16所述的方法,其特征在于,所述将所述智能合约写入区块链网络包括:将用私钥签名的更新后的共享业务数据传入区块链网络中,对传入区块链网络中的所述更新后的共享业务数据进行有效性验证,当所述更新后的共享业务数据的有效性验证成功后,将所述更新后的共享业务数据集成为一个哈希区块ID,并将所述哈希区块ID扩散到全网。
- 如权利要求13所述的方法,其特征在于,所述根据预设条件采集更新后的共享业务数据并向服务端区块链节点发送待统计业务处理请求包括:根据预设条件采集共享业务数据;将所述共享业务数据进行整合生成待统计业务数据,对所述待统计业务数据进行处理生成对应的哈希值;向服务端区块链节点发送待统计业务处理请求,所述待统计业务处理请求中携带有所述待统计业务数据以及对应的哈希值。
- 一种基于区块链的数据处理方法,其特征在于,应用于服务端区块链节点,包括:接收业务处理请求,所述业务处理请求中携带有共享业务数据;在所述共享业务数据包含的信息满足所述服务端区块链节点的智能合约自动执行条件的情况下,自动执行计算待统计金额的任务,生成对应的执行结果,并根据所述执行结果对所述共享业务数据进行更新并执行记账操作;根据预设条件采集更新后的共享业务数据并计算所述更新后的共享业务数据中的待统计金额总和。
- 如权利要求20所述的方法,其特征在于,所述计算所述更新后的共享业务数据中的待统计金额总和之后,还包括:根据计算结果对所述待统计业务数据中的输出单元进行更新,并基于所述计算结果完成对所述业务端区块链节点的待统计业务处理;将所述更新后的待统计业务数据写入区块链中。
- 一种计算设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机指令,其特征在于,所述处理器执行所述指令时实现权利要求13-21任意一项所述方法的步骤。
- 一种计算机可读存储介质,其存储有计算机指令,其特征在于,该指令被处理 器执行时实现权利要求13-21任意一项所述方法的步骤。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/875,552 US11315115B2 (en) | 2019-04-12 | 2020-05-15 | Blockchain-based data processing system, method, computing device and storage medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910296014.5 | 2019-04-12 | ||
CN201910296014.5A CN110175913B (zh) | 2019-04-12 | 2019-04-12 | 基于区块链的数据处理系统、方法、计算设备及存储介质 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/875,552 Continuation US11315115B2 (en) | 2019-04-12 | 2020-05-15 | Blockchain-based data processing system, method, computing device and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020207090A1 true WO2020207090A1 (zh) | 2020-10-15 |
Family
ID=67689993
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/071866 WO2020207090A1 (zh) | 2019-04-12 | 2020-01-14 | 基于区块链的数据处理系统、方法、计算设备及存储介质 |
Country Status (3)
Country | Link |
---|---|
CN (2) | CN113222752B (zh) |
TW (1) | TW202038173A (zh) |
WO (1) | WO2020207090A1 (zh) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112491792A (zh) * | 2020-10-20 | 2021-03-12 | 深圳智乾区块链科技有限公司 | 数据安全传输方法、装置、设备及可读存储介质 |
CN112532395A (zh) * | 2020-11-26 | 2021-03-19 | 中国船舶工业系统工程研究院 | 一种基于区块链的数据授信系统、方法和介质 |
CN112565219A (zh) * | 2020-11-26 | 2021-03-26 | 中国船舶工业系统工程研究院 | 基于区块链的海上智能系统通信方法、系统及存储介质 |
CN112883411A (zh) * | 2020-12-29 | 2021-06-01 | 杭州趣链科技有限公司 | 基于区块链的数据处理方法、系统、电子设备及存储介质 |
CN112965981A (zh) * | 2021-03-15 | 2021-06-15 | 中国平安财产保险股份有限公司 | 数据核对方法、装置、计算机设备和存储介质 |
CN112988386A (zh) * | 2021-03-19 | 2021-06-18 | 北京京东振世信息技术有限公司 | 信息生成方法、装置、服务器及存储介质 |
CN113127689A (zh) * | 2021-04-30 | 2021-07-16 | 平安普惠企业管理有限公司 | 一种数据处理方法、装置、设备及存储介质 |
CN113177092A (zh) * | 2021-05-21 | 2021-07-27 | 中船黄埔文冲船舶有限公司 | 一种船舶制造检验数据的共享方法、联盟链及系统 |
CN113191780A (zh) * | 2021-05-31 | 2021-07-30 | 中国银行股份有限公司 | 基于区块链的高风险业务交易执行方法及装置 |
CN113344563A (zh) * | 2021-05-26 | 2021-09-03 | 摩拜(北京)信息技术有限公司 | 一种账户管理方法、物品服务器、区块链集群及系统 |
CN113592614A (zh) * | 2021-08-02 | 2021-11-02 | 四川瑞虹云信息技术有限责任公司 | 一种基于区块链技术的互联网代理记账智能平台 |
CN113722285A (zh) * | 2021-11-03 | 2021-11-30 | 江苏荣泽信息科技股份有限公司 | 一种基于多链的跨链分布式文件存证系统 |
CN116402610A (zh) * | 2023-04-12 | 2023-07-07 | 湖南经研电力设计有限公司 | 基于区块链技术的共享储能并发交易数据处理方法及系统 |
CN117728961A (zh) * | 2024-02-07 | 2024-03-19 | 成都信息工程大学 | 一种区块链中可信时间服务预言机的方法和系统 |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11315115B2 (en) | 2019-04-12 | 2022-04-26 | Advanced New Technologies Co., Ltd. | Blockchain-based data processing system, method, computing device and storage medium |
CN113222752B (zh) * | 2019-04-12 | 2024-09-10 | 创新先进技术有限公司 | 基于区块链的数据处理系统、方法、计算设备及存储介质 |
CN110689344B (zh) * | 2019-08-30 | 2021-04-09 | 创新先进技术有限公司 | 在区块链中并发执行交易的方法和装置 |
CN112685496B (zh) * | 2019-10-18 | 2024-04-23 | 阿里巴巴集团控股有限公司 | 分布式系统及其数据处理方法 |
CN111242630A (zh) * | 2019-12-19 | 2020-06-05 | 广州宏算信息科技有限公司 | 一种基于区块链的结算方法、装置及存储介质 |
CN111415161B (zh) * | 2020-04-27 | 2024-03-19 | 财付通支付科技有限公司 | 基于区块链的数据验证方法、装置及计算机可读存储介质 |
CN111737301A (zh) * | 2020-06-23 | 2020-10-02 | 北京同邦卓益科技有限公司 | 业务处理方法、装置、设备及计算机可读存储介质 |
CN111861429A (zh) * | 2020-06-30 | 2020-10-30 | 上海佩俪信息科技有限公司 | 区块链交易矿工费委托方法及链下中继器 |
CN111783144A (zh) * | 2020-08-20 | 2020-10-16 | 支付宝(杭州)信息技术有限公司 | 基于区块链的数据处理方法以及装置 |
CN112487010B (zh) * | 2020-12-14 | 2024-02-23 | 深圳前海微众银行股份有限公司 | 一种区块链用户数据表更新方法、设备及存储介质 |
CN113268503B (zh) * | 2021-04-02 | 2024-03-08 | 北京比格大数据有限公司 | 信息聚合方法、存储介质、计算机设备 |
CN113269639A (zh) * | 2021-05-06 | 2021-08-17 | 众连智能科技有限公司 | 一种基于区块链智能合约的业务处理方法、装置、设备及介质 |
CN113469823B (zh) * | 2021-06-30 | 2024-04-30 | 浙江数秦科技有限公司 | 一种基于区块链的农业保险平台 |
CN114221967B (zh) * | 2021-12-14 | 2023-06-02 | 建信金融科技有限责任公司 | 基于区块链网络的资源共享平台、资源共享方法 |
CN114826667B (zh) * | 2022-03-22 | 2024-05-28 | 浪潮卓数大数据产业发展有限公司 | 一种基于区块链的数据共享方法、装置、设备及介质 |
CN115422184A (zh) * | 2022-08-22 | 2022-12-02 | 中国人民银行数字货币研究所 | 一种数据获取方法、装置、设备及存储介质 |
CN116303805B (zh) * | 2023-05-22 | 2023-07-25 | 北京恒歌科技有限公司 | 一种基于区块链的地理空间基础数据共享方法及系统 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109102281A (zh) * | 2018-07-31 | 2018-12-28 | 北京比特大陆科技有限公司 | 一种实现数字货币交易记录整合的方法和装置 |
CN109272403A (zh) * | 2018-07-31 | 2019-01-25 | 北京比特大陆科技有限公司 | 一种支持数字货币交易的方法和装置 |
CN109493203A (zh) * | 2018-09-30 | 2019-03-19 | 咪咕文化科技有限公司 | 一种数据核算方法、装置及存储介质 |
CN109544354A (zh) * | 2018-10-19 | 2019-03-29 | 中国平安人寿保险股份有限公司 | 基于区块链的再保结算方法、电子装置及可读存储介质 |
CN110175913A (zh) * | 2019-04-12 | 2019-08-27 | 阿里巴巴集团控股有限公司 | 基于区块链的数据处理系统、方法、计算设备及存储介质 |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170140408A1 (en) * | 2015-11-16 | 2017-05-18 | Bank Of America Corporation | Transparent self-managing rewards program using blockchain and smart contracts |
US10475030B2 (en) * | 2016-02-22 | 2019-11-12 | Bank Of America Corporation | System for implementing a distributed ledger across multiple network nodes |
CN105976231A (zh) * | 2016-06-24 | 2016-09-28 | 深圳前海微众银行股份有限公司 | 基于区块链智能合约的资产管理方法及节点 |
US20180089760A1 (en) * | 2016-09-26 | 2018-03-29 | Shapeshift Ag | System and method of providing a multi-asset rebalancing mechanism |
US10587628B2 (en) * | 2016-09-29 | 2020-03-10 | Microsoft Technology Licensing, Llc | Verifiable outsourced ledgers |
CN107341702B (zh) * | 2017-03-08 | 2020-06-23 | 创新先进技术有限公司 | 一种业务处理的方法及装置 |
CN107993047B (zh) * | 2017-11-22 | 2021-02-19 | 焦文华 | 一种基于区块链的保单销售佣金权益管理方法 |
KR101936756B1 (ko) * | 2018-03-05 | 2019-01-11 | 주식회사 미탭스플러스 | 블록체인을 이용한 공유경제 관리 장치 |
CN108615148B (zh) * | 2018-03-26 | 2019-03-15 | 北交金科金融信息服务有限公司 | 一种基于区块链技术的担保资产前置交易方法及系统 |
CN108446969A (zh) * | 2018-03-29 | 2018-08-24 | 张文昌 | 一种基于区块链的统一的公共交通记账与交易系统 |
CN108776929A (zh) * | 2018-04-02 | 2018-11-09 | 成都云创智融科技有限公司 | 基于区块链数据库的账单处理方法、系统和可读存储介质 |
CN108846659B (zh) * | 2018-06-13 | 2021-09-14 | 深圳前海微众银行股份有限公司 | 基于区块链的转账方法、装置及存储介质 |
CN109035018A (zh) * | 2018-07-11 | 2018-12-18 | 中链科技有限公司 | 一种区块链中智能合约的数据记录统计方法及装置 |
CN109064334B (zh) * | 2018-08-27 | 2021-12-24 | 深圳前海益链网络科技有限公司 | 一种智能合约记账方法、计算机装置及可读存储介质 |
CN110471953B (zh) * | 2018-12-07 | 2023-05-26 | 深圳市智税链科技有限公司 | 在区块链网络中确定记账节点的方法、代理节点和介质 |
-
2019
- 2019-04-12 CN CN202110291638.5A patent/CN113222752B/zh active Active
- 2019-04-12 CN CN201910296014.5A patent/CN110175913B/zh active Active
- 2019-12-31 TW TW108148528A patent/TW202038173A/zh unknown
-
2020
- 2020-01-14 WO PCT/CN2020/071866 patent/WO2020207090A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109102281A (zh) * | 2018-07-31 | 2018-12-28 | 北京比特大陆科技有限公司 | 一种实现数字货币交易记录整合的方法和装置 |
CN109272403A (zh) * | 2018-07-31 | 2019-01-25 | 北京比特大陆科技有限公司 | 一种支持数字货币交易的方法和装置 |
CN109493203A (zh) * | 2018-09-30 | 2019-03-19 | 咪咕文化科技有限公司 | 一种数据核算方法、装置及存储介质 |
CN109544354A (zh) * | 2018-10-19 | 2019-03-29 | 中国平安人寿保险股份有限公司 | 基于区块链的再保结算方法、电子装置及可读存储介质 |
CN110175913A (zh) * | 2019-04-12 | 2019-08-27 | 阿里巴巴集团控股有限公司 | 基于区块链的数据处理系统、方法、计算设备及存储介质 |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112491792B (zh) * | 2020-10-20 | 2022-08-02 | 深圳智乾区块链科技有限公司 | 数据安全传输方法、装置、设备及可读存储介质 |
CN112491792A (zh) * | 2020-10-20 | 2021-03-12 | 深圳智乾区块链科技有限公司 | 数据安全传输方法、装置、设备及可读存储介质 |
CN112532395A (zh) * | 2020-11-26 | 2021-03-19 | 中国船舶工业系统工程研究院 | 一种基于区块链的数据授信系统、方法和介质 |
CN112565219A (zh) * | 2020-11-26 | 2021-03-26 | 中国船舶工业系统工程研究院 | 基于区块链的海上智能系统通信方法、系统及存储介质 |
CN112532395B (zh) * | 2020-11-26 | 2024-02-27 | 中国船舶工业系统工程研究院 | 一种基于区块链的数据授信系统、方法和介质 |
CN112565219B (zh) * | 2020-11-26 | 2023-03-21 | 中国船舶工业系统工程研究院 | 基于区块链的海上智能系统通信方法、系统及存储介质 |
CN112883411A (zh) * | 2020-12-29 | 2021-06-01 | 杭州趣链科技有限公司 | 基于区块链的数据处理方法、系统、电子设备及存储介质 |
CN112965981A (zh) * | 2021-03-15 | 2021-06-15 | 中国平安财产保险股份有限公司 | 数据核对方法、装置、计算机设备和存储介质 |
CN112965981B (zh) * | 2021-03-15 | 2023-06-20 | 中国平安财产保险股份有限公司 | 数据核对方法、装置、计算机设备和存储介质 |
CN112988386A (zh) * | 2021-03-19 | 2021-06-18 | 北京京东振世信息技术有限公司 | 信息生成方法、装置、服务器及存储介质 |
CN112988386B (zh) * | 2021-03-19 | 2024-05-17 | 北京京东振世信息技术有限公司 | 信息生成方法、装置、服务器及存储介质 |
CN113127689A (zh) * | 2021-04-30 | 2021-07-16 | 平安普惠企业管理有限公司 | 一种数据处理方法、装置、设备及存储介质 |
CN113127689B (zh) * | 2021-04-30 | 2024-05-14 | 峥峰润洁科技(山西)股份有限公司 | 一种数据处理方法、装置、设备及存储介质 |
CN113177092B (zh) * | 2021-05-21 | 2023-07-25 | 中船黄埔文冲船舶有限公司 | 一种船舶制造检验数据的共享方法、联盟链及系统 |
CN113177092A (zh) * | 2021-05-21 | 2021-07-27 | 中船黄埔文冲船舶有限公司 | 一种船舶制造检验数据的共享方法、联盟链及系统 |
CN113344563A (zh) * | 2021-05-26 | 2021-09-03 | 摩拜(北京)信息技术有限公司 | 一种账户管理方法、物品服务器、区块链集群及系统 |
CN113344563B (zh) * | 2021-05-26 | 2024-04-16 | 摩拜(北京)信息技术有限公司 | 一种账户管理方法、物品服务器、区块链集群及系统 |
CN113191780A (zh) * | 2021-05-31 | 2021-07-30 | 中国银行股份有限公司 | 基于区块链的高风险业务交易执行方法及装置 |
CN113592614A (zh) * | 2021-08-02 | 2021-11-02 | 四川瑞虹云信息技术有限责任公司 | 一种基于区块链技术的互联网代理记账智能平台 |
CN113722285B (zh) * | 2021-11-03 | 2022-02-11 | 江苏荣泽信息科技股份有限公司 | 一种基于多链的跨链分布式文件存证系统 |
CN113722285A (zh) * | 2021-11-03 | 2021-11-30 | 江苏荣泽信息科技股份有限公司 | 一种基于多链的跨链分布式文件存证系统 |
CN116402610A (zh) * | 2023-04-12 | 2023-07-07 | 湖南经研电力设计有限公司 | 基于区块链技术的共享储能并发交易数据处理方法及系统 |
CN117728961A (zh) * | 2024-02-07 | 2024-03-19 | 成都信息工程大学 | 一种区块链中可信时间服务预言机的方法和系统 |
CN117728961B (zh) * | 2024-02-07 | 2024-05-28 | 成都信息工程大学 | 一种区块链中可信时间服务预言机的方法和系统 |
Also Published As
Publication number | Publication date |
---|---|
CN110175913B (zh) | 2021-03-02 |
CN113222752A (zh) | 2021-08-06 |
TW202038173A (zh) | 2020-10-16 |
CN110175913A (zh) | 2019-08-27 |
CN113222752B (zh) | 2024-09-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020207090A1 (zh) | 基于区块链的数据处理系统、方法、计算设备及存储介质 | |
WO2020192272A1 (zh) | 基于区块链的转账方法、系统、计算设备及存储介质 | |
WO2020211491A1 (zh) | 基于区块链的项目审核系统、方法、计算设备及存储介质 | |
US11695578B2 (en) | Systems and methods for storing and sharing transactional data using distributed computer systems | |
US20220020001A1 (en) | Decisional Architectures in Blockchain Environments | |
TWI706665B (zh) | 基於區塊鏈的資料核對系統、方法、計算設備及儲存媒體 | |
CN112020705B (zh) | 区块链随机计时器事务同步 | |
US11315115B2 (en) | Blockchain-based data processing system, method, computing device and storage medium | |
US20190353685A1 (en) | Method or system for management of a device for energy consumption by applying blockchain protocol | |
JP6813477B2 (ja) | 信頼度が低い、または信頼度が皆無の当事者間での価値転送を円滑化する装置、システム、または方法 | |
US20190287107A1 (en) | Resource equity for blockchain | |
US11620165B2 (en) | System for automated resource transfer processing using a distributed server network | |
JP6457391B2 (ja) | データストリームを分配するための方法及びシステム | |
CN111309745B (zh) | 虚拟资源处理方法、装置、电子设备及存储介质 | |
WO2020220746A1 (zh) | 一种基于区块链的结算方法、装置以及电子设备 | |
WO2020134606A1 (zh) | 基于区块链的发票冲红方法及装置和电子设备 | |
WO2020220740A1 (zh) | 基于区块链的发票创建方法和装置、电子设备 | |
US20190295046A1 (en) | Settlement facilitation hub | |
US20200169125A1 (en) | Wireless energy transfer | |
CN110659993A (zh) | 一种基于区块链网络的资源管理方法及装置 | |
US20230246835A1 (en) | System for generation of substitutable configurations of secure electronic distributed register tokens | |
CN113177772B (zh) | 一种业务数据处理方法、装置和系统 | |
TW202013276A (zh) | 交易處理方法、裝置、電子設備及電腦可讀取儲存媒體 | |
Chen et al. | Efficient and Non-Repudiable Data Trading Scheme Based on State Channels and Stackelberg Game | |
CN117745412A (zh) | 资源信息处理方法、装置、计算机设备和存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20787076 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20787076 Country of ref document: EP Kind code of ref document: A1 |