Blockchain-based reconciliation data processing method, device, and system

Through the blockchain-based reconciliation data processing method, the hash link list and privacy computing technology are used to solve the problem of low security and accuracy in the bank-enterprise reconciliation model, and the reconciliation operations in the encrypted state are realized, improving the Security and accuracy of reconciliation.

CN112767113BActive Publication Date: 2024-12-06INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202110216207.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-02-26
Publication Date
2024-12-06
Estimated Expiration
2041-02-26

AI Technical Summary

Technical Problem

The existing bank-enterprise reconciliation model has problems with low security and accuracy, especially when online reconciliation, it is easy to leak client secrets and manual reconciliation is prone to errors.

Method used

Using blockchain-based reconciliation data processing method, the service provider's job data is obtained by receiving the job batch number in the reconciliation operation results, compressing and generating hash lists, realizing reconciliation operations in encrypted state, and using privacy computing technology Ensure the accuracy of calculations and ensure the consistency and immutability of reconciliation results through blockchain technology.

Benefits of technology

It improves the security and accuracy of reconciliation, ensures that plain text data is not out of the database, makes the data available and invisible, reduces manual reconciliation errors and improves the timeliness of reconciliation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112767113B_ABST
    Figure CN112767113B_ABST
Patent Text Reader

Abstract

The present invention discloses a method, device and system for processing reconciliation data based on blockchain, and relates to the field of blockchain technology, wherein the method comprises: receiving a reconciliation operation result from a multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure, and wherein the reconciliation operation result comprises: an operation batch number; obtaining service party operation data according to the operation batch number, wherein the service party operation data comprises: a plurality of detailed data; compressing each i detailed data in the service party operation data, and generating a hash of the detailed data, wherein 1≦i≦n, i and n are positive integers greater than or equal to 1; generating a job hash linked list according to each compressed detailed data and the hash of each detailed data; and sending a reconciliation request message containing a hash of a linked list header to a client, wherein the hash of the linked list header is a hash of the nth detailed data. Through the present invention, the security and accuracy of reconciliation can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a blockchain-based reconciliation data processing method, device, and system. Background Art

[0002] Due to audit operation requirements, banks need to check financial details with corporate customers on a quarterly or fixed basis, and regularly report errors or questions. At present, bank-enterprise reconciliation mainly adopts manual, offline reconciliation mode. This independent self-protection mechanism has brought inconvenience to financial management to a certain extent: 1) The reconciliation process is lengthy, and generally the company's finance department prints paper details at the counter and then conducts manual reconciliation; 2) The reconciliation accuracy is low. Large companies have many financial details, and manual reconciliation is prone to matching errors; 3) The privacy protection needs of banks and enterprises, if they are directly connected online, there is a risk of leaking the other party's business secrets.

[0003] In response to this, the third-party financial platform proposed an online reconciliation cooperation request. The bank provided the company's reconciliation details and sent them to the enterprise ERP (Enterprise Resource Planning) platform. The platform compared the account details and output the results to the bank system. For system and data connection, see Figure 1 shown.

[0004] However, the following risks exist when adopting the reconciliation model proposed by a third-party financial platform: if the financial ERP system such as UFIDA obtains the details of a company and leaks them to other companies, the bank may be at risk of leaking customer confidential information. At the same time, if the third-party platform obtains a large number of corporate customers' public details, it can create a large number of modeling products based on the real financial data of customers, which will damage the asset value of bank data to a certain extent. Summary of the invention

[0005] In view of this, the present invention provides a blockchain-based reconciliation data processing method, device, and system to solve at least one of the above-mentioned problems.

[0006] According to a first aspect of the present invention, a method for processing reconciliation data based on blockchain is provided, the method comprising:

[0007] Receiving a reconciliation operation result from the multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure, and the reconciliation operation result includes: an operation batch number;

[0008] Acquire the service side operation data according to the operation batch number, the service side operation data including: multiple detailed data;

[0009] Compress each i-th detail data in the service provider's job data and generate a hash of the detail data, where 1≦i≦n, and i and n are positive integers greater than or equal to 1;

[0010] Generate a job hash chain list based on each compressed detail data and the hash of each detail data;

[0011] A reconciliation request message containing a link list header hash is sent to the client, where the link list header hash is the hash of the nth detail data.

[0012] According to a second aspect of the present invention, a blockchain-based reconciliation data processing method is provided, the method comprising:

[0013] Receive a reconciliation request message from a service provider, wherein the reconciliation request message includes: a link list header hash;

[0014] Obtaining a corresponding job data block stored on the blockchain according to the chain list header hash, wherein the job data block includes: the job detail data and the hash of the previous job data block;

[0015] Obtaining the job detail data of the corresponding data block according to the hash of the previous job data block, thereby obtaining all the job detail data;

[0016] Reconciliation is performed based on all the acquired job detail data and the client's job data stored locally.

[0017] According to a third aspect of the present invention, a blockchain-based reconciliation data processing device is provided, the device is located on a service side, and the device includes:

[0018] A reconciliation result receiving unit, configured to receive a reconciliation operation result from the multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure, and the reconciliation operation result includes: an operation batch number;

[0019] A service side operation data acquisition unit, used to acquire service side operation data according to the operation batch number, the service side operation data including: a plurality of detailed data;

[0020] A compression operation unit, used to compress each i-th detailed data in the service party's job data and generate a hash of the detailed data, 1≦i≦n, i and n are positive integers greater than or equal to 1;

[0021] A hash chain table generating unit, used for generating a job hash chain table according to each piece of compressed detail data and the hash of each piece of detail data;

[0022] The reconciliation request message sending unit is used to send the reconciliation request message containing the link list header hash to the client, where the link list header hash is the hash of the nth detail data.

[0023] According to a fourth aspect of the present invention, a blockchain-based reconciliation data processing device is provided, the device is located on the client side, and the device includes:

[0024] A reconciliation request message receiving unit, configured to receive a reconciliation request message from a service provider, wherein the reconciliation request message includes: a link list header hash;

[0025] A data block acquisition unit, configured to acquire a corresponding job data block stored on the blockchain according to the chain list header hash, wherein the job data block includes: the job detail data and the hash of the previous job data block;

[0026] A job detail data acquisition unit, used to acquire the job detail data of the corresponding data block according to the hash of the previous job data block, so as to acquire all the job detail data;

[0027] The reconciliation unit is used to perform reconciliation processing based on all the acquired operation detail data and the client's operation data stored locally.

[0028] According to a fifth aspect of the present invention, a blockchain-based reconciliation data processing system is provided, the system comprising: the blockchain-based reconciliation data processing device located at the service side, the blockchain-based reconciliation data processing device located at the client side, and a multi-party computing platform, the multi-party computing platform comprising at least one computing node, the computing node comprising:

[0029] A data receiving unit, used to receive service-side reconciliation data from a service provider, and to receive client-side reconciliation data from a client, wherein the service-side reconciliation data and the client-side reconciliation data both contain: the same operation batch number, and the service-side reconciliation data and the client-side reconciliation data are both encrypted using the same encryption algorithm;

[0030] A comparison unit, configured to compare the service provider's account reconciliation data with the client's account reconciliation data according to a predetermined comparison algorithm to determine whether they are consistent, thereby performing an account reconciliation operation;

[0031] The reconciliation result sending unit is used to send the reconciliation operation results to the service provider and the client respectively.

[0032] According to a sixth aspect of the present invention, there is provided an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the program.

[0033] According to a seventh aspect of the present invention, there is provided a computer-readable storage medium having a computer program stored thereon, which implements the steps of the above method when executed by a processor.

[0034] It can be seen from the above technical solution that the service party's job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party's job data is compressed, and a hash of the detail data is generated, and then a job hash list is generated according to each compressed detail data and the hash of each detail data, and then a reconciliation request message containing the list header hash is sent to the client, so that the client can obtain the service party's job data and perform reconciliation processing with the locally stored job data. In this way, subsequent reconciliation processing can be achieved when the reconciliation operation based on the multi-party computing platform fails. Compared with the prior art, the embodiment of the present invention can improve the security and accuracy of reconciliation. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1 It is a schematic diagram of a reconciliation system of related technology;

[0037] Figure 2 is a structural block diagram of a blockchain-based account reconciliation data processing system according to an embodiment of the present invention;

[0038] Figure 3 is a structural block diagram of a computing node 101 according to an embodiment of the present invention;

[0039] Figure 4 is a structural block diagram of a service-side reconciliation data processing device 20 according to an embodiment of the present invention;

[0040] Figure 5 is a structural block diagram of a client-side account reconciliation data processing device 30 according to an embodiment of the present invention;

[0041] Figure 6 is an exemplary structural diagram of a reconciliation data processing system according to an embodiment of the present invention;

[0042] Figure 7 is a flow chart of transaction accounting according to an embodiment of the present invention;

[0043] Figure 8 is a flow chart of continued reconciliation between the bank side and the enterprise side according to an embodiment of the present invention;

[0044] Fig. 9 It is a schematic diagram of a reconciliation transaction chain according to an embodiment of the present invention;

[0045] Fig.10 is a schematic diagram of processing local detail data according to an embodiment of the present invention;

[0046] Fig.11 is a flowchart of a method for processing reconciliation data according to an embodiment of the present invention;

[0047] Fig.12 is another flow chart of the method for processing reconciliation data according to an embodiment of the present invention;

[0048] Fig.13 It is a schematic block diagram of the system structure of the electronic device 600 according to an embodiment of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] In view of the problems of low security and accuracy in the existing reconciliation model, an embodiment of the present invention provides a blockchain-based reconciliation data processing solution, which uses blockchain technology and privacy computing technology to realize reconciliation operations in an encrypted state, thereby overcoming the problems of low security and accuracy in the existing reconciliation model.

[0051] In an embodiment of the present invention, privacy computing technologies, such as algorithms such as homomorphic encryption, can ensure the accuracy of calculations based on ciphertext. Banks and enterprise nodes each save their own operation (i.e., transaction) data, so that the original operation data can be compared without leaving the warehouse. At the same time, blockchain technology can ensure that the reconciliation results are consistent across multiple nodes, difficult to tamper with, and easy to trace. This can ensure that when any party has doubts about the reconciliation results, it is easy to hold them accountable.

[0052] The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0053] Figure 2 is a structural block diagram of a blockchain-based account reconciliation data processing system according to an embodiment of the present invention. Figure 2As shown, the system includes: a multi-party computing platform 10, a service-side reconciliation data processing device 20 located on the service side, and a client-side reconciliation data processing device 30 located on the client side. The multi-party computing platform 10 receives the encrypted reconciliation data of the service-side reconciliation data processing device 20 and the encrypted reconciliation data of the client-side reconciliation data processing device 30 respectively, and compares the two encrypted reconciliation data based on a predetermined comparison algorithm. When the comparison result is that the two data are consistent, it can be determined that the reconciliation data are consistent and the reconciliation is successful. Otherwise, it is determined that the reconciliation has failed. After that, the reconciliation result data is sent to the service-side reconciliation data processing device 20 and the client-side reconciliation data processing device 30 respectively. When the reconciliation fails, the service-side reconciliation data processing device 20 and the client-side reconciliation data processing device 30 continue to perform the reconciliation operation.

[0054] Through this system, it is possible to prevent plaintext data from being shipped out of the warehouse, and to compare and reconcile ciphertext data based on a multi-party computing platform to obtain reconciliation results, thus achieving the availability of data but invisibility. When reconciliation fails, reconciliation can continue based on the blockchain, improving the security and accuracy of reconciliation operations.

[0055] In order to better understand the present invention, each part is described separately below.

[0056] (1) Multi-party computing platform 10

[0057] The multi-party computing platform 10 includes at least one computing node 101, such as Figure 3 As shown, the computing node 101 includes: a data receiving unit 1011, a comparison unit 1012 and a reconciliation result sending unit 1013, wherein:

[0058] The data receiving unit 1011 is used to receive service-side reconciliation data from the service provider and receive client-side reconciliation data from the client, wherein the service-side reconciliation data and the client-side reconciliation data both contain: the same operation batch number, and the service-side reconciliation data and the client-side reconciliation data are encrypted using the same encryption algorithm;

[0059] A comparison unit 1012, configured to compare the service provider's account reconciliation data with the client's account reconciliation data according to a predetermined comparison algorithm to determine whether they are consistent, thereby performing an account reconciliation operation;

[0060] The reconciliation result sending unit 1013 is used to send the reconciliation operation result to the service provider and the client respectively.

[0061] By receiving the encrypted data of the two parties and comparing the encrypted data of the two parties based on a predetermined comparison algorithm, when the original data is the same (i.e., the reconciliation data of the service party is the same as that of the customer party), the encrypted data of the two parties should still be the same after the same encryption algorithm, then the comparison result of the encrypted data of the two parties should be the same, or the encrypted data of the two parties perform a subtraction operation, and can get 0, otherwise, the result of the subtraction operation of the encrypted data of the two parties is non-0. In this way, it can be achieved that the plaintext data is not sent out of the warehouse, and the ciphertext data is compared and reconciled based on the comparison algorithm to obtain the reconciliation result, which realizes the availability of data but is invisible, and improves the security of reconciliation.

[0062] In one embodiment, when there are multiple computing nodes, the service party reconciliation data processing device 20 can divide the service party reconciliation data into multiple service party reconciliation data segments of the same number as the computing nodes based on a predetermined segmentation algorithm. For example, if there are 4 computing nodes, the service party reconciliation data is divided into 4 service party reconciliation data segments.

[0063] In one embodiment, for efficient reconciliation, the service party reconciliation data may include: job batch number, summary amount of service party job data and number of detailed data, that is, reconciliation is performed only based on summary amount and number of detailed data.

[0064] Accordingly, the client reconciliation data also includes: the operation batch number, the summary amount of the client operation data and the number of detailed data. The client reconciliation data processing device 30 also divides the client reconciliation data into multiple client reconciliation data segments with the same number of computing nodes based on the same segmentation algorithm.

[0065] Afterwards, the service-side reconciliation data processing device 20 sends each service-side reconciliation data segment to each node respectively, and the customer-side reconciliation data processing device 30 sends each customer-side reconciliation data segment to each node respectively.

[0066] The data receiving unit 1011 of each computing node receives the service-side reconciliation data segments and the client-side reconciliation data segments, and each comparison unit 1012 compares the received service-side reconciliation data segments and the client-side reconciliation data segments according to a predetermined comparison algorithm to generate a comparison result.

[0067] Accordingly, the multi-party computing platform further includes: a comparison result aggregation unit for aggregating the comparison results of the comparison units of each computing node to generate the above-mentioned reconciliation operation result. Afterwards, the reconciliation result sending unit 1013 sends it to the service provider and the client.

[0068] (2) Service-side reconciliation data processing device 20

[0069] Figure 4 is a structural block diagram of the service provider's account reconciliation data processing device 20, such as Figure 4As shown, the device 20 includes: a reconciliation result receiving unit 201, a service side operation data acquiring unit 202, a compression operation unit 203, a hash chain table generating unit 204 and a reconciliation request message sending unit 205, wherein:

[0070] The reconciliation result receiving unit 201 is used to receive the reconciliation operation result from the multi-party computing platform, and the reconciliation operation result includes: the job batch number. When the reconciliation operation result is a reconciliation failure, the service party job data acquisition unit 202, the compression operation unit 203, the hash list generation unit 204 and the reconciliation request message sending unit 205 are executed.

[0071] The service side operation data acquisition unit 202 is used to acquire the service side operation data according to the operation batch number, and the service side operation data includes: a plurality of detailed data.

[0072] The compression operation unit 203 is used to compress each i-th detailed data in the service party's job data and generate a hash of the detailed data, 1≦i≦n, i and n are positive integers greater than or equal to 1.

[0073] The hash chain table generating unit 204 is used to generate a job hash chain table according to each compressed detail data and the hash of each detail data.

[0074] Specifically, the hash chain table generation unit 204 includes: a data block generation module and a hash chain table generation module, wherein:

[0075] A data block generation module, used to generate the i-th operation data block according to the hash of each i-th compressed detail data and the i-1-th detail data;

[0076] The hash chain table generating module is used to generate the job hash chain table according to the generated multiple job data blocks.

[0077] The account reconciliation request message sending unit 205 is used to send the account reconciliation request message including the link list header hash to the client, where the link list header hash is the hash of the nth detail data.

[0078] The service-side job data acquisition unit 202 acquires the service-side job data according to the job batch number in the reconciliation operation result received by the reconciliation result receiving unit 201. The compression operation unit 203 compresses each detail data in the service-side job data and generates a hash of the detail data. Then, the hash chain list generation unit 204 generates a job hash chain list according to each compressed detail data and the hash of each detail data. Then, the reconciliation request message sending unit 205 sends the reconciliation request message containing the chain list header hash to the client, so that the client can obtain the service-side job data and perform reconciliation processing with the locally stored job data. In this way, subsequent reconciliation processing can be implemented when the reconciliation operation fails based on the multi-party computing platform. Compared with the prior art, the embodiment of the present invention can improve the security and accuracy of reconciliation.

[0079] In actual operation, the service party reconciliation data processing device 20 further includes: a first segmentation unit, a first encryption unit and a first encrypted data sending unit, wherein:

[0080] A first segmentation unit is used to segment the service party reconciliation data into a plurality of service party reconciliation data segments based on a predetermined segmentation algorithm, wherein the service party reconciliation data includes: a summary amount and a number of detailed data items of the service party operation data;

[0081] A first encryption unit, configured to encrypt the plurality of service party reconciliation data segments respectively based on a predetermined encryption algorithm;

[0082] The first encrypted data sending unit is used to send the encrypted multiple service party reconciliation data in segments to the multi-party computing platform.

[0083] Through the first splitting unit, the first encryption unit and the first encrypted data sending unit, reconciliation operations based on the multi-party computing platform can be implemented, so that plaintext data will not be shipped out, and ciphertext data will be compared and reconciled based on a comparison algorithm to obtain reconciliation results, thereby achieving data availability but invisibility.

[0084] (3) Customer-side account reconciliation data processing device 30

[0085] Figure 5 is a structural block diagram of the client-side reconciliation data processing device 30, such as Figure 5 As shown, the device 30 includes: a reconciliation request message receiving unit 301, a data block acquisition unit 302, a job detail data acquisition unit 303 and a reconciliation unit 304, wherein:

[0086] The reconciliation request message receiving unit 301 is used to receive a reconciliation request message from a service provider, wherein the reconciliation request message includes: a link list header hash;

[0087] A data block acquisition unit 302 is used to acquire a corresponding job data block stored on the blockchain according to the chain list header hash, wherein the job data block includes: the job detail data and the hash of the previous job data block;

[0088] The job detail data acquisition unit 303 is used to acquire the job detail data of the corresponding data block according to the hash of the previous job data block, so as to acquire all the job detail data;

[0089] The reconciliation unit 304 is used to perform reconciliation processing based on all the acquired operation detail data and the locally stored client operation data.

[0090] Through the reconciliation request message receiving unit 301, the data block obtaining unit 302, the operation detail data obtaining unit 303 and the reconciliation unit 304, subsequent reconciliation processing when the reconciliation operation fails based on the multi-party computing platform can be implemented.

[0091] In actual operation, the client-side reconciliation data processing device further includes: a reconciliation operation result receiving unit, which is used to receive the reconciliation operation result from the multi-party computing platform. When the reconciliation operation result is a reconciliation failure, the reconciliation request message receiving unit 301, the data block acquisition unit 302, the operation detail data acquisition unit 303 and the reconciliation unit 304 are executed.

[0092] In a specific implementation process, the above-mentioned client reconciliation data processing device further includes: a second segmentation unit, a second encryption unit, and a second encrypted data sending unit, wherein:

[0093] A second segmentation unit is used to segment the client reconciliation data into a plurality of client reconciliation data segments based on a predetermined segmentation algorithm, wherein the client reconciliation data includes: a summary amount and a number of detailed data items of the client operation data;

[0094] A second encryption unit, configured to encrypt the plurality of client reconciliation data segments respectively based on a predetermined encryption algorithm;

[0095] The second encrypted data sending unit is used to send the encrypted multiple client reconciliation data in segments to the multi-party computing platform.

[0096] Through the second splitting unit, the second encryption unit and the second encrypted data sending unit, reconciliation operations based on the multi-party computing platform can be implemented, so that plaintext data does not leave the warehouse, and ciphertext data is compared and reconciled based on a comparison algorithm to obtain reconciliation results, thereby achieving data availability but invisibility and improving the security of reconciliation.

[0097] It should be noted that the segmentation algorithm, encryption algorithm, and comparison algorithm involved in the embodiments of the present invention can refer to the prior art, and the present invention does not limit this. In the embodiments of the present invention, when performing reconciliation operations on the same batch of job data, the service party and the client party only need to use the same segmentation algorithm and the same segmentation method to segment the reconciliation data, and use the same encryption algorithm to encrypt the segmented reconciliation data. If the local reconciliation data of the two parties are consistent, it can be guaranteed that the comparison operation result on the multi-party computing platform is consistent with the reconciliation data of the two parties. When the local reconciliation data of the two parties are inconsistent, the data is inconsistent after data segmentation and encryption, and the comparison operation result on the multi-party computing platform should also be inconsistent with the reconciliation data of the two parties.

[0098] In actual operation, the above-mentioned units and modules may be provided in combination or individually, and the present invention is not limited thereto.

[0099] In order to better understand the embodiments of the present invention, an exemplary system is given below, taking a bank as the service provider and an enterprise as the client.

[0100] Figure 6 is an example structural diagram of a reconciliation data processing system according to an embodiment of the present invention. Figure 6 As shown, the system includes: a bank 11, an enterprise ERP 12, a bank MPC (Secure Multi-Party Computation) node 13, an enterprise MPC node 14 and a blockchain network 15, wherein:

[0101] Bank: Specifically refers to the bank's accounting system, including local database services, which store the original transaction data. The bank's computing nodes store encrypted bank public account details.

[0102] Enterprise ERP: refers to the enterprise ERP system, which refers to the third-party financial system. Enterprises can manage their own financial details by accessing the enterprise ERP system. The system includes the enterprise local database service, which stores the company's financial details. During the reconciliation process, the enterprise ERP acts as a data source and provides the original financial details on the enterprise side. The computing nodes on the enterprise side store the encrypted company financial details.

[0103] Bank MPC node: A trusted computing engine is deployed to support various ciphertext calculations such as arithmetic, maximum value, comparison, average, statistics, etc. The bank MPC node saves the encrypted transaction details on the bank side. In the reconciliation process, by calling the comparison operator, it is possible to compare whether the transaction summary amount and detailed ciphertext of the bank side and the enterprise side in the same transaction batch are consistent.

[0104] Enterprise MPC node: A trusted computing engine is deployed to support various ciphertext calculations such as arithmetic, maximum value, comparison, mean, statistics, etc. The enterprise MPC node saves the encrypted transaction details on the enterprise side. And during the reconciliation process, by calling the comparison operator, it is possible to compare whether the transaction summary amount and detailed ciphertext of the bank side and the enterprise side under the same transaction batch are consistent.

[0105] It should be noted that the bank MPC node and the enterprise MPC node in this example correspond to the multi-party computing platform 10 mentioned above.

[0106] Blockchain network: a consortium chain composed of banks and enterprises, used for the execution of reconciliation contracts, the broadcast and scheduling of reconciliation tasks, and the storage and traceability of reconciliation results. The specific process is as follows:

[0107] First, as the initiator of reconciliation, the enterprise needs to define a reconciliation contract, which includes:

[0108] 1) Transaction batches

[0109] 2) Trading hours

[0110] 3) Reconciliation logic

[0111] 4) Designate the recipient of the reconciliation results

[0112] After the contract definition is completed, submit the contract to the participating nodes in the alliance chain for review. After the node review is passed, the contract is deployed and the blockchain network is started. The reconciliation task is broadcast to each node through the blockchain. After the MPC (responsible for executing privacy calculations) node receives the reconciliation task, it executes the calculation engine. Previously, all parties have configured the local database address through the system. The calculation engine will read the encrypted transaction data of all parties and compare the corresponding metadata. If the total value of the detailed ciphertext data of all parties is consistent after aggregation, the reconciliation result is correct. The final reconciliation message contains the public key address, transaction batch number, transaction hash, reconciliation time, and reconciliation result of both parties. After the reconciliation is successful, the reconciliation message is returned to both parties and its hash is stored in the blockchain. If the summary reconciliation results are inconsistent, the enterprise party calls the blockchain reconciliation query interface through the transaction hash in the reconciliation message to pull the detailed message for item-by-item comparison.

[0113] In actual operation, the transaction accounting process on the bank side is as follows: Figure 7 As shown:

[0114] After receiving the enterprise transaction message, the bank system generates an accounting message and calls the encryption interface of the multi-party security reconciliation system to encrypt the message. The server parses the key in the enterprise public key certificate as the encryption key. The encrypted transaction message is stored in the message queue together with the transaction batch number (i.e., the operation batch number), enterprise number and other information. The blockchain on-chain service constructs the on-chain transaction. After receiving the on-chain transaction, the bank node generates the transaction hash value of this batch of transactions. The relationship between the message batch number, enterprise account and transaction HASH is stored in the blockchain database.

[0115] Figure 8 This is a flow chart based on the bank side and the enterprise side continuing to reconcile after the bank MPC node 13 and the enterprise MPC node 14 fail to reconcile, such as Figure 8 As shown, the process includes:

[0116] In the reconciliation process, the bank system first obtains the batch number of the transaction, reads the on-chain transaction corresponding to the current transaction, compresses the transaction and constructs the on-chain transaction, compresses each i-th transaction detail data of the current batch, generates a transaction HASH, and constructs a reconciliation HASH linked list. Each transaction contains a transaction detail list and is linked to the HASH of the previous transaction, all the way to the last transaction data of the batch. The reconciliation transaction linked list is as follows: Fig. 9 As shown, the list header HASH (i.e., HASHn) is stored in the reconciliation message of the initiating enterprise. After receiving the reconciliation message, the enterprise extracts the list header HASH value as the query input parameter, calls the reconciliation query interface to pull the transaction details of the batch (the transaction details are stored on the chain, and the transaction details on the chain are read locally through the reconciliation query interface), and reconciles one by one.

[0117] Fig. 9 This illustrates the serial relationship between blockchain transactions. During the reconciliation process, a batch of reconciliation transaction data of an enterprise is organized in the form of a linked list on the blockchain. When the enterprise receives the reconciliation message, it finds the data block represented by HASHn in the figure (n represents the total number of data blocks) according to the header hash address of the linked list. The structure of the data block is:

[0118] {“transactions”:[

[0119] "Transaction processing time, transaction type, message identification number, transaction initiator, payment institution, transaction recipient, amount, transaction status",

[0120] "Transaction processing time, transaction type, message identification number, transaction initiator, payment institution, transaction recipient, amount, transaction status", .... ]

[0123] “preHash”: stores the blockchain transaction hash of the previous reconciliation transaction

[0124] }

[0125] The transactions field above contains part of the reconciliation details of this batch. The preHash field points to the previous data block with the same structure, and in the figure it points to the HASHn-1 data block.

[0126] Similarly, by continuously parsing preHash, we can trace back to the first data block HASH1 in the linked list. The contents of all transactions in data blocks HASH1 to HASHn constitute all the reconciliation data of the enterprise in this batch. Therefore, the enterprise can serially call the getblockTxByHash (function applied to blockchain) method provided by the blockchain SDK (software development kit) in sequence until the preHash value in the return value TxByHashResp is empty, and finally obtain all the data required for reconciliation of a batch.

[0127] like Fig.10 As shown in the figure, there are n detailed data in a batch of transactions in the banking system, recorded as tx1, tx2, ... txn. Before reconciliation, a summary operation is required to obtain the summary amount and number of transactions in the batch, and then the summary amount and total number of transactions in the batch are divided into 4 data segments respectively. After encrypting these 4 data segments, they are sent to 4 MPC computing nodes. Similarly, for the enterprise accounting ERP system, it also summarizes and accounts for the batch of transactions. The summary message usually contains the information shown in Table 1 below:

[0128] Message elements 《XML Tag》 Remark BatchIdentification <batchid> < / batchid> Transaction batches CountNumber <cntnb> < / cntnb> Total number of records CountAmount <cntamt> < / cntamt> Summarize the total amount of records DebitCountNumber <dbtcntnb> < / dbtcntnb> Number of payments DebitCountAmount <dbtcntamt> < / dbtcntamt> Payment Amount CreditorCountNumber <cdtcntnb> < / cdtcntnb> Number of payments received CreditorCountAmount <cdtcntamt> < / cdtcntamt> Amount of payment

[0129] Table 1

[0130] The aggregate amount A and the number of transactions N are split and encrypted respectively, and the encrypted shard data is stored in 4 MPC computing nodes. By executing the privacy computing engine of the MPC node and calling the comparison operator (described in detail later), the aggregate data of both parties can be checked for equality in the ciphertext state. After the verification is correct, the final verification result is sent to the two parties of the account together with the public key address, transaction batch number, transaction hash, and reconciliation time of the two parties of the account. If the verification is incorrect, execute Figure 8 In the reconciliation process, extract the transaction hash in the message and use it as an input parameter to call the getblockTxByHash method provided by the blockchain SDK to query the detailed message and compare them one by one.

[0131] The comparison process of the comparison operator is described in detail below.

[0132] Assuming that the bank's reconciliation data is a (including the summary amount and the number of transactions), first split a into four data to ensure that a1+a2+a3+a4=a. The four split data are processed into ciphertext and sent to the four computing nodes.

[0133] The data after encryption algorithm is:

[0134] x1=a1.t+r1.e

[0135] x2=a2.t+r2.e

[0136] x3=a3.t+r3.e

[0137] x4=a4.t+r4.e

[0138] x1+x2+x3+x4=(a1+a2+a3+a4)t+(r1+r2+r3+r4)e

[0139] Among them, t and e are two public random numbers, a1, a2, a3, a4 are their own secret numbers, and r1, r2, r3, r4 are blinding factors.

[0140] Similarly, for the enterprise's reconciliation data b (including the summary amount and number of transactions), the reconciliation data is divided into 4 pieces to ensure that b1+b2+b3+b4=b. The sharded data is processed into ciphertext and sent to the 4 computing nodes. The same encryption algorithm as above is used. The data after encryption algorithm is:

[0141] y1=b1.t+r1.e ...

[0143] Each computing node executes xi-yi;

[0144] Finally, each calculation result is summarized: (x1-y1)+(x2-y2)+(x3-y3)+(x4-y4);

[0145] After deformation, we can get: (x1+x2+x3+x4)-(y1+y2+y3+y4)=(a.t+re)-(b.t+re).

[0146] if:

[0147] (x1+x2+x3+x4)-(y1+y2+y3+y4)=xy=(ab).t=0

[0148] That is, when the ciphertext x=y, then a=b.

[0149] That is, if the ciphertexts are equal, it can be proved that the corresponding plaintexts are equal, otherwise the corresponding plaintexts are not equal.

[0150] Through the above-mentioned comparison operator, both the enterprise and the bank can perform reconciliation operations without obtaining the other party's full plaintext data, thus achieving the availability but invisible nature of data.

[0151] It should be noted that the computing engines deployed on the four computing nodes are consistent and their processing rules are the same.

[0152] In actual operation, the reconciliation data can also be encrypted first and then split. The number of splits can be determined according to the number of nodes. Each node processes one segment of data from the bank and one segment of data from the enterprise.

[0153] The embodiment of the present invention proposes a multi-party secure blockchain bank-enterprise reconciliation system, which solves the problems of low reconciliation frequency, large manual reconciliation workload, low accuracy, and difficulty in accountability for reconciliation problems in the existing manual reconciliation mode between banks and enterprises by using blockchain technology and privacy computing technology. The advantages of this example are mainly:

[0154] 1. Optimize the customer reconciliation process and provide customers with a simple and secure blockchain reconciliation solution interface;

[0155] 2. Protect privacy data. The ledger data of each party is stored locally. Plain text data is not stored. Cipher text data is calculated and reconciled based on a multi-party secure computing platform to obtain the reconciliation results, making the data available but invisible.

[0156] 3. It improves the frequency and timeliness of reconciliation, and can ensure quasi-real-time reconciliation (can be achieved within 1 hour), greatly shortens the timeliness of reconciliation, increases the frequency of reconciliation, and reduces problems such as the error rate of manual reconciliation.

[0157] Based on similar inventive concepts, an embodiment of the present invention also provides a blockchain-based reconciliation data processing method, which can preferably be applied to the above-mentioned service party reconciliation data processing device 20 located at the service party.

[0158] Fig.11 is a flow chart of the reconciliation data processing method, such as Fig.11 As shown, the method includes:

[0159] Step 1101, receiving a reconciliation operation result from a multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure, and the reconciliation operation result includes: an operation batch number.

[0160] Step 1102, obtaining service-side operation data according to the operation batch number, wherein the service-side operation data includes: multiple detailed data.

[0161] Step 1103, compress each i-th detailed data in the service party's job data, and generate a hash of the detailed data, where 1≦i≦n, i and n are positive integers greater than or equal to 1.

[0162] Step 1104, generating a job hash linked list according to each compressed detail data and the hash of each detail data.

[0163] Specifically, the i-th job data block is generated according to the hash of each i-th compressed detail data and the i-1-th detail data; and then the job hash linked list is generated according to the generated multiple job data blocks.

[0164] Step 1105: Send a reconciliation request message including a link list header hash to the client, where the link list header hash is a hash of the nth detail data.

[0165] The service party's job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party's job data is compressed, and a hash of the detail data is generated, and then a job hash list is generated according to each compressed detail data and the hash of each detail data, and then a reconciliation request message containing the hash of the list header is sent to the client, so that the client can obtain the service party's job data and reconcile it with the locally stored job data. In this way, subsequent reconciliation processing can be implemented when the reconciliation operation fails based on the multi-party computing platform. Compared with the prior art, the embodiments of the present invention can improve the security and accuracy of reconciliation.

[0166] In actual operation, when executing the reconciliation process based on the multi-party computing platform, the following operations can be performed: based on a predetermined segmentation algorithm, the service party reconciliation data is divided into multiple service party reconciliation data segments, and the service party reconciliation data includes: the summary amount of the service party operation data and the number of detailed data items; then, based on a predetermined encryption algorithm, the multiple service party reconciliation data segments are encrypted respectively; and then the encrypted multiple service party reconciliation data segments are sent to the multi-party computing platform to facilitate the multi-party computing platform to perform the reconciliation process.

[0167] The embodiment of the present invention also provides a blockchain-based reconciliation data processing method, which can preferably be applied to the above-mentioned customer-side reconciliation data processing device 30 located on the customer side.

[0168] Fig.12 is a flow chart of the reconciliation data processing method, such as Fig.12 As shown, the method includes:

[0169] Step 1201, receiving a reconciliation request message from a service provider, wherein the reconciliation request message includes: a link list header hash;

[0170] Step 1202, obtaining a corresponding job data block stored on the blockchain according to the chain header hash, wherein the job data block includes: the job detail data and the hash of the previous job data block;

[0171] Step 1203, obtaining the job detail data of the corresponding data block according to the hash of the previous job data block, thereby obtaining all the job detail data;

[0172] Step 1204, reconciliation processing is performed based on all the acquired operation detail data and the client's operation data stored locally.

[0173] Through the above steps, subsequent reconciliation processing can be implemented when the reconciliation operation based on the multi-party computing platform fails.

[0174] Before executing step 1201, a reconciliation operation result is received from the multi-party computing platform. When the reconciliation operation result is a reconciliation failure, the above steps 1201-1204 are executed.

[0175] In actual operation, when executing the reconciliation process based on the multi-party computing platform, the following operations can be performed: based on a predetermined segmentation algorithm, the customer reconciliation data is divided into multiple customer reconciliation data segments, and the customer reconciliation data includes: the summary amount and the number of detailed data of the customer operation data; based on a predetermined encryption algorithm, the multiple customer reconciliation data segments are respectively encrypted; and the encrypted multiple customer reconciliation data segments are sent to the multi-party computing platform to facilitate the multi-party computing platform to perform the reconciliation process.

[0176] The specific process of each of the above steps can be found in the description of the above system embodiment, which will not be repeated here.

[0177] This embodiment also provides an electronic device, which may be a desktop computer, a tablet computer, a mobile terminal, etc., but this embodiment is not limited thereto. In this embodiment, the electronic device may be implemented with reference to the above method embodiment and the embodiment of the blockchain-based reconciliation data processing device / system, the contents of which are incorporated herein, and the repeated parts are not repeated.

[0178] Fig.13 FIG. 6 is a schematic block diagram of a system structure of an electronic device 600 according to an embodiment of the present invention. Fig.13 As shown, the electronic device 600 may include a central processor 100 and a memory 140; the memory 140 is coupled to the central processor 100. It should be noted that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0179] In one embodiment, the blockchain-based reconciliation data processing function may be integrated into the central processor 100. The central processor 100 may be configured to perform the following control:

[0180] Receiving a reconciliation operation result from the multi-party computing platform, the reconciliation operation result is a reconciliation failure, and the reconciliation operation result includes: an operation batch number;

[0181] Acquire the service side operation data according to the operation batch number, the service side operation data including: multiple detailed data;

[0182] Compress each i-th detail data in the service provider's job data and generate a hash of the detail data, where 1≦i≦n, and i and n are positive integers greater than or equal to 1;

[0183] Generate a job hash chain list based on each compressed detail data and the hash of each detail data;

[0184] A reconciliation request message containing a link list header hash is sent to the client, where the link list header hash is the hash of the nth detail data.

[0185] From the above description, it can be seen that the electronic device provided in the embodiment of the present application obtains the service party's job data according to the job batch number in the received reconciliation operation result, compresses each detail data in the service party's job data, and generates a hash of the detail data, and then generates a job hash list based on each compressed detail data and the hash of each detail data, and then sends a reconciliation request message containing the list header hash to the client, so that the client can obtain the service party's job data and perform reconciliation processing with the locally stored job data. In this way, subsequent reconciliation processing based on the multi-party computing platform can be implemented when the reconciliation operation fails. Compared with the prior art, the embodiment of the present invention can improve the security and accuracy of reconciliation.

[0186] In another embodiment, the blockchain-based reconciliation data processing device / system can be configured separately from the central processor 100. For example, the blockchain-based reconciliation data processing device / system can be configured as a chip connected to the central processor 100, and the blockchain-based reconciliation data processing function can be implemented through the control of the central processor.

[0187] like Fig.13 As shown, the electronic device 600 may further include: a communication module 110, an input unit 120, an audio processing unit 130, a display 160, and a power supply 170. It is worth noting that the electronic device 600 does not necessarily have to include Fig.13 In addition, the electronic device 600 may also include Fig.13 For components not shown, reference may be made to the prior art.

[0188] like Fig.13 As shown, the central processor 100 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor devices and / or logic devices. The central processor 100 receives inputs and controls the operations of various components of the electronic device 600.

[0189] The memory 140 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory or other suitable devices. The above-mentioned information related to the failure may be stored, and a program for executing the relevant information may also be stored. The CPU 100 may execute the program stored in the memory 140 to implement information storage or processing.

[0190] The input unit 120 provides input to the CPU 100. The input unit 120 is, for example, a key or a touch input device. The power supply 170 is used to provide power to the electronic device 600. The display 160 is used to display display objects such as images and text. The display may be, for example, an LCD display, but is not limited thereto.

[0191] The memory 140 may be a solid-state memory, such as a read-only memory (ROM), a random access memory (RAM), a SIM card, etc. It may also be a memory that saves information even when the power is off, can be selectively erased, and is provided with more data, examples of which are sometimes referred to as EPROMs, etc. The memory 140 may also be some other type of device. The memory 140 includes a buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application / function storage unit 142, which is used to store application programs and function programs or processes for executing the operation of the electronic device 600 through the central processor 100.

[0192] The memory 140 may also include a data storage unit 143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 144 of the memory 140 may include various drivers for communication functions of the electronic device and / or for executing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0193] The communication module 110 is a transmitter / receiver 110 that transmits and receives signals via an antenna 111. The communication module (transmitter / receiver) 110 is coupled to the central processor 100 to provide input signals and receive output signals, which may be the same as the case of a conventional mobile communication terminal.

[0194] Based on different communication technologies, multiple communication modules 110 may be provided in the same electronic device, such as a cellular network module, a Bluetooth module and / or a wireless LAN module. The communication module (transmitter / receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide an audio output via the speaker 131 and receive an audio input from the microphone 132, thereby realizing a common telecommunication function. The audio processor 130 may include any suitable buffer, decoder, amplifier, etc. In addition, the audio processor 130 is also coupled to the central processor 100, so that the sound can be recorded on the local machine through the microphone 132, and the sound stored on the local machine can be played through the speaker 131.

[0195] An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned blockchain-based reconciliation data processing method are implemented.

[0196] To sum up, in order to solve the security and accuracy problems of online reconciliation between banks and enterprises, the embodiments of the present invention combine the characteristics of blockchain that cannot be tampered with and data sharing and the data protection mechanism of multi-party secure computing, and propose a multi-party secure blockchain bank-enterprise reconciliation system. The system mainly improves the convenience of bank-enterprise reconciliation from the following three aspects: 1. Optimize the customer reconciliation process and provide customers with a simple and secure blockchain reconciliation solution interface; 2. Protect privacy data, the ledger data of each party is stored locally, the plaintext data is not stored, and the ciphertext data is calculated and reconciled based on the multi-party secure computing platform to obtain the reconciliation results, so as to achieve data availability but invisibility; 3. Scalability, build an alliance between multi-enterprise ERP systems and banks to achieve simple access and real-time reconciliation.

[0197] The preferred embodiments of the present invention are described above with reference to the accompanying drawings. Many features and advantages of these embodiments are clear from this detailed description, and therefore the claims are intended to cover all such features and advantages of these embodiments that fall within their true spirit and scope. In addition, since many modifications and changes are easily conceivable to those skilled in the art, it is not intended to limit the embodiments of the present invention to the precise structure and operation illustrated and described, but all suitable modifications and equivalents falling within its scope may be covered.

[0198] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0199] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0200] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0201] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0202] The present invention uses specific embodiments to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for processing account reconciliation data based on blockchain, characterized in that: The method comprises: Receiving a reconciliation operation result from the multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure, and the reconciliation operation result includes: an operation batch number; Acquire the service side operation data according to the operation batch number, the service side operation data including: multiple detailed data; Compress each i-th detail data in the service provider's job data and generate a hash of the detail data, where 1≦i≦n, and i and n are positive integers greater than or equal to 1; Generate a job hash chain list based on each compressed detail data and the hash of each detail data; Sending a reconciliation request message containing a link header hash to the client, where the link header hash is a hash of the nth detail data; Specifically, the service party job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party job data is compressed, and a hash of the detail data is generated, and then a job hash linked list is generated according to each compressed detail data and the hash of each detail data.

2. The method according to claim 1, characterized in that The hash chain table of the job generated according to each compressed detail data and the hash of each detail data includes: Generate the i-th job data block according to the hash of each i-th compressed detail data and the i-1-th detail data; The job hash chain list is generated according to the generated multiple job data blocks.

3. The method according to claim 1, characterized in that Before receiving the reconciliation operation result from the multi-party computing platform, the method further includes: Based on a predetermined segmentation algorithm, the service party reconciliation data is segmented into a plurality of service party reconciliation data segments, wherein the service party reconciliation data includes: a summary amount of the service party operation data and a number of detailed data items; Encrypting the multiple service party reconciliation data segments respectively based on a predetermined encryption algorithm; The encrypted reconciliation data of multiple service parties are sent in segments to the multi-party computing platform.

4. A method for processing account reconciliation data based on blockchain, characterized in that: The method comprises: Receive a reconciliation request message from a service provider, wherein the reconciliation request message includes: a link list header hash; Obtaining a corresponding job data block stored on the blockchain according to the chain list header hash, wherein the job data block includes: the job detail data and the hash of the previous job data block; Obtaining the job detail data of the corresponding data block according to the hash of the previous job data block, thereby obtaining all the job detail data; Perform reconciliation based on all acquired operation detail data and locally stored client operation data; Specifically, the service party job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party job data is compressed, and a hash of the detail data is generated, and then a job hash linked list is generated according to each compressed detail data and the hash of each detail data.

5. The method according to claim 4, characterized in that Before receiving the reconciliation request message from the service provider, the method further includes: A reconciliation operation result is received from the multi-party computing platform, where the reconciliation operation result is a reconciliation failure.

6. The method according to claim 5, characterized in that Before receiving the reconciliation operation result from the multi-party computing platform, the method further includes: Dividing the client reconciliation data into a plurality of client reconciliation data segments based on a predetermined segmentation algorithm, wherein the client reconciliation data includes: a summary amount and a number of detailed data items of the client operation data; Encrypting the plurality of client reconciliation data segments respectively based on a predetermined encryption algorithm; The encrypted multiple client reconciliation data are sent in segments to the multi-party computing platform.

7. A blockchain-based account reconciliation data processing device, characterized in that: The device is located at the service side, and the device includes: A reconciliation result receiving unit, configured to receive a reconciliation operation result from the multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure, and the reconciliation operation result includes: an operation batch number; A service side operation data acquisition unit, used to acquire service side operation data according to the operation batch number, the service side operation data including: a plurality of detailed data; A compression operation unit, used to compress each i-th detailed data in the service party's job data and generate a hash of the detailed data, 1≦i≦n, i and n are positive integers greater than or equal to 1; A hash chain table generating unit, used for generating a job hash chain table according to each piece of compressed detail data and the hash of each piece of detail data; A reconciliation request message sending unit, used to send a reconciliation request message including a link list header hash to the client, wherein the link list header hash is a hash of the nth detail data; Specifically, the service party job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party job data is compressed, and a hash of the detail data is generated, and then a job hash linked list is generated according to each compressed detail data and the hash of each detail data.

8. The device according to claim 7, characterized in that The hash chain table generation unit comprises: A data block generation module, used to generate the i-th operation data block according to the hash of each i-th compressed detail data and the i-1-th detail data; The hash chain table generating module is used to generate the job hash chain table according to the generated multiple job data blocks.

9. The device according to claim 7, characterized in that The device also includes: A first segmentation unit is used to segment the service party reconciliation data into a plurality of service party reconciliation data segments based on a predetermined segmentation algorithm, wherein the service party reconciliation data includes: a summary amount and a number of detailed data items of the service party operation data; A first encryption unit, configured to encrypt the plurality of service party reconciliation data segments respectively based on a predetermined encryption algorithm; The first encrypted data sending unit is used to send the encrypted multiple service party reconciliation data in segments to the multi-party computing platform.

10. A blockchain-based reconciliation data processing device, characterized in that: The device is located at the client side, and the device includes: A reconciliation request message receiving unit, configured to receive a reconciliation request message from a service provider, wherein the reconciliation request message includes: a link list header hash; A data block acquisition unit, configured to acquire a corresponding job data block stored on the blockchain according to the chain list header hash, wherein the job data block includes: the job detail data and the hash of the previous job data block; A job detail data acquisition unit, used to acquire the job detail data of the corresponding data block according to the hash of the previous job data block, so as to acquire all the job detail data; A reconciliation unit is used to perform reconciliation processing based on all acquired operation detail data and locally stored client operation data; Specifically, the service party job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party job data is compressed, and a hash of the detail data is generated, and then a job hash linked list is generated according to each compressed detail data and the hash of each detail data.

11. The device according to claim 10, characterized in that The device also includes: The reconciliation operation result receiving unit is used to receive the reconciliation operation result from the multi-party computing platform, where the reconciliation operation result is reconciliation failure.

12. The device according to claim 10, characterized in that The device also includes: A second segmentation unit is used to segment the client reconciliation data into a plurality of client reconciliation data segments based on a predetermined segmentation algorithm, wherein the client reconciliation data includes: a summary amount and a number of detailed data items of the client operation data; A second encryption unit, configured to encrypt the plurality of client reconciliation data segments respectively based on a predetermined encryption algorithm; The second encrypted data sending unit is used to send the encrypted multiple client reconciliation data in segments to the multi-party computing platform.

13. A blockchain-based reconciliation data processing system, characterized in that: The system comprises: a blockchain-based account reconciliation data processing device located at a service side as claimed in claim 9, a blockchain-based account reconciliation data processing device located at a client side as claimed in claim 12, and a multi-party computing platform, wherein the multi-party computing platform comprises at least one computing node, wherein the computing node comprises: A data receiving unit, used to receive service-side reconciliation data from a service provider, and to receive client-side reconciliation data from a client, wherein the service-side reconciliation data and the client-side reconciliation data both contain: the same operation batch number, and the service-side reconciliation data and the client-side reconciliation data are both encrypted using the same encryption algorithm; A comparison unit, configured to compare the service provider's account reconciliation data with the client's account reconciliation data according to a predetermined comparison algorithm to determine whether they are consistent, thereby performing an account reconciliation operation; A reconciliation result sending unit, used to send the reconciliation operation result to the service provider and the client respectively; Specifically, the service party job data is obtained according to the job batch number in the received reconciliation operation result, each detail data in the service party job data is compressed, and a hash of the detail data is generated, and then a job hash linked list is generated according to each compressed detail data and the hash of each detail data.

14. The system according to claim 13, characterized in that When there are multiple computing nodes, The first segmentation unit of the reconciliation data processing device located at the service side is specifically used to: segment the service side reconciliation data into a plurality of service side reconciliation data segments having the same number as the computing nodes based on the predetermined segmentation algorithm; The second segmentation unit of the client-side reconciliation data processing device is specifically used to: segment the client-side reconciliation data into a plurality of client-side reconciliation data segments having the same number as the computing nodes based on the predetermined segmentation algorithm; The data receiving unit is specifically used to: receive the service party reconciliation data segments and the customer party reconciliation data segments; The comparison unit is specifically used to: compare the received service-side reconciliation data segments and the client-side reconciliation data segments according to the predetermined comparison algorithm to generate a comparison result; The multi-party computing platform also includes: The comparison result aggregation unit is used to aggregate the comparison results of the comparison units of each computing node to generate the reconciliation operation result.

15. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method according to any one of claims 1 to 6 are implemented.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Citation Information

Patent Citations

  • Consumption information checking method and device and storage medium

    CN109767245A

  • Blockchain reconciliation method and system

    CN111861482A