CN112767113A - Account checking data processing method, device and system based on block chain - Google Patents
Account checking data processing method, device and system based on block chain Download PDFInfo
- Publication number
- CN112767113A CN112767113A CN202110216207.2A CN202110216207A CN112767113A CN 112767113 A CN112767113 A CN 112767113A CN 202110216207 A CN202110216207 A CN 202110216207A CN 112767113 A CN112767113 A CN 112767113A
- Authority
- CN
- China
- Prior art keywords
- data
- reconciliation
- hash
- account checking
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 15
- 238000000034 method Methods 0.000 claims abstract description 36
- 238000012545 processing Methods 0.000 claims description 71
- 238000004422 calculation algorithm Methods 0.000 claims description 43
- 230000011218 segmentation Effects 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 13
- 238000003860 storage Methods 0.000 claims description 11
- 230000006835 compression Effects 0.000 claims description 10
- 238000007906 compression Methods 0.000 claims description 10
- 238000004364 calculation method Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 26
- 230000006870 function Effects 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 5
- 239000000872 buffer Substances 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 239000003999 initiator Substances 0.000 description 3
- 102100022142 Achaete-scute homolog 1 Human genes 0.000 description 2
- 101000901099 Homo sapiens Achaete-scute homolog 1 Proteins 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
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/12—Accounting
- G06Q40/125—Finance or payroll
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a block chain-based reconciliation data processing method, device and system, and relates to the technical field of block chains, wherein the method comprises the following steps: 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 comprises: job batch number; obtaining the operation data of a service party according to the operation batch number, wherein the operation data of the service party comprises: multiple strokes of detail data; compressing each i of detail data in the server side operation data, and generating hash of the detail data, wherein i is greater than or equal to 1 and is less than or equal to n, and i and n are positive integers greater than or equal to 1; generating an operation hash chain table according to each compressed detailed data and the hash of each detailed data; and sending the account checking request message containing the chain table head hash to the client side, wherein the chain table head hash is the hash of the nth detailed data. By the method and the device, the safety and the accuracy of account checking can be improved.
Description
Technical Field
The invention relates to the technical field of block chains, in particular to a method, a device and a system for processing account checking data based on a block chain.
Background
Due to audit operation requirements, banks need to carry out financial detail check on public clients according to seasons or fixed periods, and lists with errors or questions are fed back regularly. At present, bank-enterprise reconciliation mainly adopts a manual offline reconciliation mode. The mechanism of mutually independent self-protection brings inconvenience to the financial management work to a certain extent: 1) the account checking process is long, and manual account checking is generally carried out after a paper statement is printed from the finance of a company to a counter; 2) the reconciliation accuracy is low, the financial details of a large company are numerous, and manual reconciliation is easy to be matched and missed; 3) the bank and enterprise privacy protection requirement is met, direct online communication is achieved, and the hidden trouble that the commercial secrets of the other party are leaked exists.
In contrast, the third-party financial platform provides an online reconciliation cooperation request, the bank provides corporate reconciliation details, the corporate reconciliation details are sent to an Enterprise ERP (Enterprise Resource Planning) platform, the platform outputs a result to be fed back to the bank system by comparing the accounting details, and the system and data connection are shown in fig. 1.
However, with the reconciliation mode proposed by the third-party financial platform, the following risks exist: for example, after the details of a certain company are obtained by a financial ERP system such as friends, if the details are disclosed to other companies, the bank risks to disclose the client's secret. Meanwhile, if the third-party platform acquires a large number of corporate clients, a large number of modeling products based on the real financial data of the clients can be created, and the asset value of bank data can be damaged to a certain extent.
Disclosure of Invention
In view of the above, the present invention provides a block chain-based reconciliation data processing method, apparatus and system to solve at least one of the above-mentioned problems.
According to a first aspect of the present invention, there is provided a block chain-based reconciliation data processing method, the method comprising:
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 comprises: job batch number;
obtaining the operation data of a service party according to the operation batch number, wherein the operation data of the service party comprises: multiple strokes of detail data;
compressing each i of detail data in the server side operation data, and generating hash of the detail data, wherein i is greater than or equal to 1 and is less than or equal to n, and i and n are positive integers greater than or equal to 1;
generating an operation hash chain table according to each compressed detailed data and the hash of each detailed data;
and sending the account checking request message containing the chain table head hash to the client side, wherein the chain table head hash is the hash of the nth detailed data.
According to a second aspect of the present invention, there is provided a block chain-based reconciliation data processing method, including:
receiving a reconciliation request message from a service party, wherein the reconciliation request message comprises: hash of the chain header;
obtaining a corresponding operation data block stored on a block chain according to the chain table head hash, wherein the operation data block comprises: hash of the job detail data and the previous job data block;
acquiring the affiliated operation detail data of the corresponding data block according to the hash of the previous operation data block so as to acquire all the operation detail data;
and performing reconciliation processing according to the acquired all job detail data and the locally stored client side job data.
According to a third aspect of the present invention, there is provided a block chain-based reconciliation data processing apparatus, the apparatus being located at a server side, the apparatus comprising:
the account checking result receiving unit is used for receiving an account checking operation result from the multi-party computing platform, wherein the account checking operation result is an account checking failure, and the account checking operation result comprises: job batch number;
a server job data obtaining unit, configured to obtain server job data according to the job batch number, where the server job data includes: multiple strokes of detail data;
the compression operation unit is used for compressing each i of detail data in the server side operation data and generating hash of the detail data, wherein i is greater than or equal to 1 and n is a positive integer greater than or equal to 1;
the hash chain table generating unit is used for generating an operation hash chain table according to each compressed detailed data and the hash of each detailed data;
and the account checking request message sending unit is used for sending the account checking request message containing the chain table head hash to the client side, wherein the chain table head hash is the hash of the nth detailed data.
According to a fourth aspect of the present invention, there is provided a block chain-based reconciliation data processing apparatus, the apparatus being located on a client side, the apparatus comprising:
a reconciliation request message receiving unit, configured to receive a reconciliation request message from a service party, where the reconciliation request message includes: hash of the chain header;
a data block obtaining unit, configured to obtain, according to the chain header hash, a corresponding job data block stored on a blockchain, where the job data block includes: hash of the job detail data and the previous job data block;
the operation detail data acquisition unit is used for acquiring the operation detail data of the corresponding data block according to the hash of the previous operation data block so as to acquire all the operation detail data;
and the account checking unit is used for performing account checking processing according to the acquired all job detail data and the locally stored client side job data.
According to a fifth aspect of the present invention, there is provided a block chain based reconciliation data processing system comprising: the block chain based reconciliation data processing device at the service side, the block chain based reconciliation data processing device at the client side and the multi-party computing platform comprise at least one computing node, wherein the computing node comprises:
a data receiving unit, configured to receive service-side reconciliation data from a service side and receive client-side reconciliation data from a client side, where the service-side reconciliation data and the client-side reconciliation data both include: the server side account checking data and the client side account checking data are encrypted by the same encryption algorithm;
a comparison unit for comparing whether the service side account checking data and the client side account checking data are consistent according to a preset comparison algorithm so as to execute account checking operation;
and the account checking result sending unit is used for sending the account checking operation result to the service party and the client party respectively.
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 on the memory and executable on the processor, the processor implementing the steps of the above method when executing the program.
According to a seventh aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above method.
According to the technical scheme, the server side operation data are obtained according to the operation batch number in the received reconciliation operation result, each detailed data in the server side operation data are compressed, the hash of the detailed data is generated, the operation hash chain table is generated according to the hash of each compressed detailed data and each detailed data, the reconciliation request message containing the chain table head hash is sent to the client side, so that the client side can obtain the server side operation data, and the reconciliation processing is performed with the locally stored operation data.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of a reconciliation system of the related art;
FIG. 2 is a block diagram of a block chain based reconciliation data processing system in accordance with an embodiment of the present invention;
FIG. 3 is a block diagram of a computing node 101 according to an embodiment of the invention;
fig. 4 is a block diagram of the structure of the server-side reconciliation data processing apparatus 20 according to an embodiment of the present invention;
fig. 5 is a block diagram of the structure of the client-side reconciliation data processing apparatus 30 according to an embodiment of the present invention;
FIG. 6 is an exemplary block diagram of a reconciliation data processing system in accordance with an embodiment of the present invention;
FIG. 7 is a flow diagram of transaction billing according to an embodiment of the invention;
FIG. 8 is a flow diagram of a Bank side and Enterprise side Continue reconciliation in accordance with an embodiment of the present invention;
FIG. 9 is a schematic diagram of a reconciliation transaction linked list according to an embodiment of the invention;
FIG. 10 is a schematic illustration of the processing of local detail data according to an embodiment of the invention;
FIG. 11 is a flow diagram of a reconciliation data processing method according to an embodiment of the invention;
FIG. 12 is another flow diagram of a reconciliation data processing method according to an embodiment of the present invention;
fig. 13 is a schematic block diagram of a system configuration of an electronic apparatus 600 according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In view of the problem that the existing reconciliation mode is low in both security and accuracy, the embodiment of the invention provides a reconciliation data processing scheme based on a block chain.
In the embodiment of the invention, the privacy computation technology, like algorithms such as state encryption and the like, can ensure the computation accuracy in a cryptograph-based state, and the bank and enterprise nodes respectively store own operation (namely transaction) data, so that the original operation data can be compared in a non-ex-warehouse state, and meanwhile, the block chain technology can ensure the technical characteristics of consistency, difficult tampering, traceability and the like of multiple nodes of the reconciliation result, and can ensure that when any party makes a doubt on the reconciliation result, the accountability is easy.
Embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Fig. 2 is a block diagram of a block chain-based reconciliation data processing system according to an embodiment of the present invention, as shown in fig. 2, the system comprising: the multi-party computing platform 10, the server side account checking data processing device 20 located at the server side and the client side account checking data processing device 30 located at the client side, the multi-party computing platform 10 respectively receives the encrypted account checking data of the server side account checking data processing device 20 and the encrypted account checking data of the client side account checking data processing device 30, the two encrypted account checking data are compared based on a preset comparison algorithm, when the two data are consistent, the account checking data can be judged to be consistent, the account checking is successful, otherwise, the account checking is failed, then the account checking result data are respectively sent to the server side account checking data processing device 20 and the client side account checking data processing device 30, and when the account checking is failed, the server side account checking data processing device 20 and the client side account checking data processing device 30 continue to execute account checking operation.
Through the system, plaintext data can not be exported, ciphertext data is compared and checked on the basis of a multi-party computing platform, a checking result is obtained, and the data can be used and can not be seen; when the account checking fails, the account checking can be continuously carried out based on the block chain, and the safety and the accuracy of the account checking operation are improved.
For a better understanding of the invention, each of the parts is described below.
(1) Multi-party computing platform 10
The multi-party computing platform 10 includes at least one computing node 101, as shown in fig. 3, the computing node 101 includes: a data receiving unit 1011, a comparing unit 1012, and a reconciliation result transmitting unit 1013, wherein:
a data receiving unit 1011, configured to receive service-side reconciliation data from a service side and receive client-side reconciliation data from a client side, where the service-side reconciliation data and the client-side reconciliation data both include: the server side account checking data and the client side account checking data are encrypted by the same encryption algorithm;
a comparison unit 1012, configured to compare whether the service-side reconciliation data and the client-side reconciliation data are consistent according to a predetermined comparison algorithm, so as to perform a reconciliation operation;
a reconciliation result sending unit 1013 configured to send a reconciliation operation result to the service party and the client party, respectively.
By receiving the encrypted data of the two parties and comparing the encrypted data of the two parties based on a preset comparison algorithm, when the original data are the same (namely, account checking data of a service party and the account checking data of a client party are the same), the encrypted data of the two parties are still the same based on the same encryption algorithm, the comparison result of the encrypted data of the two parties is the same, or the encrypted data of the two parties is subjected to subtraction operation, so that 0 can be obtained, otherwise, the result of the subtraction operation of the encrypted data of the two parties is not 0. Therefore, plaintext data can not be exported, ciphertext data is compared and checked based on a comparison algorithm to obtain a checking result, the data can be invisible, and the checking safety is improved.
In one embodiment, when the computing node is plural, the server tie-out data processing apparatus 20 may cut the server tie-out data into a plurality of server tie-out data segments of the same number as the computing node based on a predetermined cutting algorithm. For example, if there are 4 compute nodes, then the server tie-out data is divided into 4 server tie-out data segments.
In one embodiment, for reconciliation efficiency, the server-side reconciliation data may comprise: and the operation batch number, the summary amount of the operation data of the server and the detail data stroke number, namely, the account is checked only based on the summary amount and the detail stroke number.
Accordingly, the client-side reconciliation data also comprises: job batch number, summary amount of client job data and detailed data stroke number. The client-side reconciliation data processing apparatus 30 also segments the client-side reconciliation data into a plurality of client-side reconciliation data segments of the same number as the number of the calculation nodes based on the same segmentation algorithm.
Thereafter, the server-side reconciliation data processing apparatus 20 transmits the respective server-side reconciliation data segments to the respective nodes, and the client-side reconciliation data processing apparatus 30 transmits the respective client-side reconciliation data segments to the respective nodes.
The data receiving unit 1011 of each computing node receives the server-side reconciliation data segment and the client-side reconciliation data segment, and each comparing unit 1012 compares the received server-side reconciliation data segment and client-side reconciliation data segment according to a predetermined comparison algorithm to generate a comparison result.
Accordingly, the multi-party computing platform further comprises: and the comparison result summarizing unit is used for summarizing the comparison results of the calculation node comparison units and generating the reconciliation operation result. After that, the reconciliation result sending unit 1013 sends to the service side and the client side.
(2) Service side reconciliation data processing device 20
Fig. 4 is a block diagram showing the configuration of the server-side reconciliation data processing apparatus 20, and as shown in fig. 4, the apparatus 20 includes: a reconciliation result receiving unit 201, a server job data obtaining unit 202, a compression operation unit 203, a hash chain table generating unit 204 and a reconciliation request message sending unit 205, wherein:
a reconciliation result receiving unit 201, configured to receive a reconciliation operation result from the multi-party computing platform, where the reconciliation operation result includes: and the job batch number is used for executing the server job data acquisition unit 202, the compression operation unit 203, the hash chain table generation unit 204 and the reconciliation request message sending unit 205 when the result of the reconciliation operation is that the reconciliation fails.
A server job data obtaining unit 202, configured to obtain server job data according to the job batch number, where the server job data includes: and multiple strokes of detail data.
A compression operation unit 203, configured to compress i pieces of detail data in the server job data, and generate a hash of the i pieces of detail data, where 1 ≦ i ≦ n, and i and n are positive integers greater than or equal to 1.
And a hash chain table generating unit 204, configured to generate a job hash chain table according to each compressed detail data and the hash of each detail data.
Specifically, the hash chain table generating unit 204 includes: the data block generating module and the hash chain table generating module, wherein:
the data block generating module is used for generating an ith job data block according to the hash of each i-th detailed data and the i-1 st detailed data after compression;
and the hash linked list generating module is used for generating the operation hash linked list according to the generated operation data blocks.
And an account checking request message sending unit 205, configured to send an account checking request message including a list head hash to the client, where the list head hash is a hash of the nth detailed data.
The server job data is acquired by the server job data acquisition unit 202 based on the job batch number in the reconciliation operation result received by the reconciliation result receiving unit 201, the compression operation unit 203 compresses each detailed data in the server job data, and generates the hash of the piece of detail data, then the hash chain generating unit 204 generates a job hash chain according to the compressed each piece of detail data and the hash of each piece of detail data, then the reconciliation request message sending unit 205 sends the reconciliation request message containing the chain head hash to the client, so that the client side can conveniently obtain the operation data of the service side and carry out account checking processing with the locally stored operation data, and thus, the method and the device can realize subsequent reconciliation processing when the reconciliation operation fails based on the multi-party computing platform, and compared with the prior art, the method and the device can improve the security and the accuracy of the reconciliation.
In practical operation, the service-side reconciliation data processing apparatus 20 further comprises: first segmentation unit, first encryption unit and first encrypted data sending unit, wherein:
a first segmentation unit configured to segment, based on a predetermined segmentation algorithm, service-side reconciliation data into a plurality of service-side reconciliation data segments, the service-side reconciliation data comprising: the summary amount and the detailed data number of the service party operation data;
a first encryption unit, configured to encrypt the plurality of server reconciliation data segments based on a predetermined encryption algorithm, respectively;
and the first encrypted data sending unit is used for sending the plurality of encrypted service party account checking data segments to the multi-party computing platform.
Through the first dividing unit, the first encryption unit and the first encrypted data sending unit, account checking operation based on a multi-party computing platform can be achieved, plaintext data cannot be exported, ciphertext data is compared and checked based on a comparison algorithm, account checking results are obtained, and data can be used and cannot be seen.
(3) Client-side reconciliation data processing apparatus 30
Fig. 5 is a block diagram showing the configuration of the client-side reconciliation data processing apparatus 30, and as shown in fig. 5, the apparatus 30 includes: an account checking request message receiving unit 301, a data block acquiring unit 302, a job detail data acquiring unit 303 and an account checking unit 304, wherein:
a reconciliation request message receiving unit 301, configured to receive a reconciliation request message from a service party, where the reconciliation request message includes: hash of the chain header;
a data block obtaining unit 302, configured to obtain, according to the chain header hash, a corresponding job data block stored on a blockchain, where the job data block includes: hash of the job detail data and the previous job data block;
a job detail data obtaining unit 303, configured to obtain job detail data belonging to a corresponding data block according to the hash of the previous job data block, so as to obtain all job detail data;
and an account checking unit 304, configured to perform account checking processing according to the acquired all job detail data and locally stored client-side job data.
Through the reconciliation request message receiving unit 301, the data block acquiring unit 302, the job detail data acquiring unit 303 and the reconciliation unit 304, the subsequent reconciliation processing when the reconciliation operation based on the multi-party computing platform fails can be realized.
In practical operation, the client-side reconciliation data processing apparatus further comprises: and the account checking operation result receiving unit is used for receiving the account checking operation result from the multi-party computing platform. When the result of the reconciliation operation is a reconciliation failure, the above-described reconciliation request message receiving unit 301, data block acquisition unit 302, job detail data acquisition unit 303, and reconciliation unit 304 are executed.
In a specific implementation process, the client-side reconciliation data processing apparatus further includes: the second segmentation unit, second encryption unit and second encryption data sending unit, wherein:
a second segmentation unit, configured to segment the client-side reconciliation data into a plurality of client-side reconciliation data segments based on a predetermined segmentation algorithm, where the client-side reconciliation data includes: the summary amount and the detail data number of the client side job data;
a second encryption unit configured to encrypt the plurality of client reconciliation data segments, respectively, based on a predetermined encryption algorithm;
and the second encrypted data sending unit is used for sending the plurality of encrypted client account checking data segments to the multi-party computing platform.
Through the second segmentation unit, the second encryption unit and the second encrypted data sending unit, account checking operation based on a multi-party computing platform can be achieved, plaintext data is not exported, ciphertext data is compared and checked based on a comparison algorithm, an account checking result is obtained, data is not available and invisible, and account checking safety is improved.
It should be noted that, the segmentation algorithm, the encryption algorithm, and the comparison algorithm referred in the embodiments of the present invention may refer to the prior art, and the present invention is not limited thereto. In the embodiment of the invention, when account checking operation is carried out on the operation data of the same batch, the service party and the client party only need to use the same segmentation algorithm and the same segmentation mode to segment the account checking data, and use the same encryption algorithm to encrypt the segmented account checking data. If the local reconciliation data of the two parties are consistent, the comparison operation result of the multi-party computing platform can be ensured to be the consistency of the two-party reconciliation data. When the local account checking data of the two parties are inconsistent, the data are also inconsistent after the data are segmented and encrypted, and the comparison operation result on the multi-party computing platform is that the local account checking data of the two parties are inconsistent.
In practical operation, the units and the modules may be combined or may be singly arranged, and the present invention is not limited thereto.
For better understanding of the embodiment of the present invention, an example system is given below by taking a service side as a bank and a client side as an enterprise.
FIG. 6 is an exemplary block diagram of a reconciliation data processing system in accordance with an embodiment of the present invention, as shown in FIG. 6, comprising: a bank 11, an enterprise ERP 12, a bank MPC (Multi-Party Secure computing) node 13, an enterprise MPC node 14, and a blockchain network 15, where:
bank: in particular to a bank accounting system which comprises a local database service, wherein the local database stores the original data of the transaction. And the bank side computing node stores the encrypted details of the public account of the bank.
Enterprise ERP: refers to an enterprise ERP system and refers to a third party financial system. The enterprise can manage the financial details of the enterprise by accessing the enterprise ERP system. The system comprises an enterprise local database service, wherein the local database stores respective company financial details of enterprises, and in the reconciliation process, the enterprise ERP serves as a data source and provides original financial details of an enterprise side. And the enterprise side computing node stores the encrypted company financial details.
A bank MPC node: a trusted computing engine is deployed and supports various ciphertext computations such as four arithmetic operations, most value, comparison, mean value, statistics and the like. The bank MPC node saves the transaction details encrypted by the bank side. And in the account checking execution process, whether the transaction summary amount and the detailed ciphertext of the bank end and the enterprise end in the same transaction batch are consistent or not can be compared by calling the comparison operator.
An enterprise MPC node: a trusted computing engine is deployed and supports various ciphertext computations such as four arithmetic operations, most value, comparison, mean value, statistics and the like. The enterprise MPC node maintains transaction details encrypted at the enterprise side. And in the account checking execution process, whether the transaction summary amount and the detailed ciphertext of the bank end and the enterprise end in the same transaction batch are consistent or not can be compared by calling the comparison operator.
It is noted that the bank MPC nodes and enterprise MPC nodes in this example correspond to the multi-party computing platform 10 described above.
Block chain network: and the coalition chain is formed by the bank and the enterprise and is used for executing the reconciliation contract, broadcasting and scheduling the reconciliation task and storing and tracing the reconciliation result. The specific process is as follows:
firstly, an enterprise side is used as an account checking initiator, an account checking contract needs to be defined, and the contract content comprises:
1) trading batches
2) Transaction time
3) Reconciliation logic
4) Account checking result appointing receiver
And after the contract definition is finished, submitting the contract to the nodes of participators in the alliance chain for auditing, deploying the contract after the node auditing is passed, and starting the block chain network. And broadcasting the reconciliation task to each node through the block chain, and executing a calculation engine after the reconciliation task is received by the MPC (responsible for executing privacy calculation) node. Before, each party configures a local database address through a system, a calculation engine can read transaction data of each party after encryption and compare corresponding metadata, if the total value of the ciphertext data of each party after summary is consistent, the reconciliation result is correct, and the final reconciliation message comprises public key addresses of both reconciliation parties, a transaction batch number, a transaction hash, reconciliation time and a reconciliation result. And after the account checking is successful, returning the account checking message to the account checking parties, and performing hash storage on the account checking message to the block chain. If the summary reconciliation results are inconsistent, the enterprise side pulls the detail message through the transaction hash calling block chain reconciliation query interface in the reconciliation message, and compares the detail message one by one.
In actual practice, the transaction accounting flow at the bank side is shown in fig. 7:
after receiving the enterprise transaction message, the bank system generates a bookkeeping message, calls an encryption interface of the multi-party security reconciliation system to encrypt the message, and the server side analyzes a secret key in the enterprise public key certificate to serve as an encryption secret key. The encrypted transaction message is stored in a message queue together with information such as a transaction batch number (i.e., job batch number), an enterprise number, and the like. The uplink transaction is constructed through the block chain uplink service, after the bank end node receives the uplink transaction, a transaction HASH value of the batch transaction is generated, and the incidence relation among the message batch number, the enterprise account and the transaction HASH is stored in the block chain database.
Fig. 8 is a flowchart of continuing reconciliation on the bank side and the enterprise side after reconciliation failure of the bank MPC node 13 and the enterprise MPC node 14, and as shown in fig. 8, the flowchart includes:
in the continuous reconciliation process, a bank system firstly obtains a batch number of a transaction, reads a link transaction corresponding to the current transaction, constructs a link transaction after compressing the transaction, compresses each i detailed data of the current batch to generate a transaction HASH, constructs a reconciliation HASH linked list, links the HASH of the previous transaction besides the transaction detailed list and links the HASH of the previous transaction until the last transaction data of the batch, the reconciliation transaction linked list is as shown in fig. 9, stores a link header HASH (namely, HASH n) in an initiating enterprise reconciliation message, extracts a link header HASH value as an inquiry entry parameter after the enterprise receives the reconciliation message, calls a reconciliation inquiry interface to pull the batch of transaction detailed (the transaction detailed is stored on the link, and reads the transaction detailed on the link to the local through the reconciliation inquiry interface) and performs reconciliation one by one.
Fig. 9 illustrates the concatenation relationship between blockchain transactions. In the reconciliation process, reconciliation transaction data of a certain batch of enterprises are organized in a linked list form on a block chain, when the enterprises receive a reconciliation message, a data block (n represents the total number of the data blocks) represented by HASHn in a graph is found according to a header hash address of the linked list, and the structure of the data block is as follows:
{“transactions”:[
"transaction processing time, transaction type, message identification number, transaction initiator, payment mechanism, transaction receiver, amount, transaction status",
"transaction processing time, transaction type, message identification number, transaction initiator, payment mechanism, transaction receiver, amount, transaction status",
....
]
"preHash": block chain transaction hashing for storing last reconciliation transaction
}
The transactions field contains partial reconciliation details data for the batch. The pre-hash field points to the previous block of data with the same structure, in the figure to the hash-1 block of data.
By analogy, the HASH can be continuously resolved to trace back to the first data block HASH1 in the linked list. The contents of all transactions in the data blocks HASH1 through HASHN constitute all reconciliation data for the enterprise batch. Therefore, the enterprise can obtain all data required by account checking of a certain batch finally by serially calling the getlocktxbyhash (function applied to the blockchain) method provided by the blockchain SDK (software development kit) in sequence until the hash value in the return value TxByHashResp is null.
As shown in fig. 10, there are n pieces of detail data in the batch transaction of the banking system, which are denoted as tx1, tx 2. Before checking account, the sum and the total number of the batch of transactions are obtained through summarizing operation, then the sum and the total number of the batch of transactions are respectively divided into 4 data segments, and the 4 data segments are respectively encrypted and then sent to 4 MPC computing nodes. Similarly, for the enterprise accounting ERP system, the batch of transactions are summarized and booked, and the summarized message generally includes the information shown in the following table 1:
| message element | 《XML Tag》 | Remarks for note |
| BatchIdentification | <BatchId> | Trading batches |
| CountNumber | <CntNb> | Summarizing and recording the total number of strokes |
| CountAmount | <CntAmt> | The total amount of money is recorded in a summary manner |
| DebitCountNumber | <DbtCntNb> | Number of payment |
| DebitCountAmount | <DbtCntAmt> | Amount of payment |
| CreditorCountNumber | <CdtCntNb> | Number of collection strokes |
| CreditorCountAmount | <CdtCntAmt> | Amount of money collected |
TABLE 1
And respectively segmenting the summary amount A and the stroke number N, encrypting, and storing the encrypted sliced data to 4 MPC computing nodes. By executing a privacy calculation engine of the MPC node and calling a comparison operator (described in detail later), the equality of the summarized data of the two parties can be checked in a ciphertext state, and after the correctness of the check is checked, the final check result is sent to the two reconciliation parties along with the public key address, the transaction batch number, the transaction hash and the reconciliation time of the two reconciliation parties. If the check is wrong, the reconciliation flow in fig. 8 is executed, the transaction hash in the message is extracted, and the transaction hash is used as a getblockactbyhash method provided by the entry-reference calling block chain SDK to inquire and compare the detail messages one by one.
The comparison process of the comparator is described in detail below.
Assuming that account checking data of a bank party is a (including summary amount and number of strokes), firstly, a is divided into four data, a1+ a2+ a3+ a4 is guaranteed to be a, and the 4 divided data are processed into ciphertext and sent to 4 computing nodes.
The data after the encryption algorithm is as follows:
x1＝a1.t+r1.e
x2＝a2.t+r2.e
x3＝a3.t+r3.e
x4＝a4.t+r4.e
x1+x2+x3+x4＝(a1+a2+a3+a4)t+(r1+r2+r3+r4)e
wherein t and e are two public random numbers, a1, a2, a3 and a4 are secret numbers of the users, and r1, r2, r3 and r4 are blinding factors.
Similarly, for account checking data b (including the summary amount and the number of strokes) of the enterprise side, the account checking data is divided into 4 pieces, b1+ b2+ b3+ b4 is guaranteed, the piece data is processed into a ciphertext and sent to 4 computing nodes, the same encryption algorithm is used, and the data after the encryption algorithm is as follows:
y1＝b1.t+r1.e
...
each compute node executes xi-yi;
and finally, summarizing each calculation result: (x1-y1) + (x2-y2) + (x3-y3) + (x4-y 4);
after deformation, the following can be obtained: (x1+ x2+ x3+ x4) - (y1+ y2+ y3+ y4) ═ a.t + r.e) - (b.t + r.e.
If:
(x1+x2+x3+x4)－(y1+y2+y3+y4)＝x-y＝(a-b).t＝0
that is, when the ciphertext x is y, a must be b.
That is, the ciphertexts are equal, and it can be proved that the corresponding plaintexts are equal, otherwise, the corresponding plaintexts are not equal.
By the comparison operator, account checking operation can be performed without taking the full amount of plaintext data of the other party for enterprises and banking parties, and the data can be used and cannot be seen.
It should be noted that, the computing engines deployed by the 4 computing nodes are consistent, and the processing rules are the same.
In actual operation, the accounting data may be encrypted first and then split, the number of the split may be determined according to the number of nodes, and each node processes one segment data of the banking side and one segment data of the enterprise side.
The embodiment of the invention provides a multi-party safe block chain bank-enterprise reconciliation system, which solves the problems of low reconciliation frequency, large manual reconciliation workload, low accuracy, difficult reconciliation problem tracing and the like in the conventional bank-enterprise manual reconciliation mode by means of a block chain technology and a privacy calculation technology, and has the advantages that:
1. optimizing a client account checking flow and providing a simple safe block chain account checking scheme interface for a client;
2. private data are protected, account book data of all parties are stored locally, plaintext data cannot be exported, ciphertext data are calculated and checked on the basis of a multi-party safety computing platform, a checking result is obtained, and the data can be used and cannot be seen;
3. the method has the advantages of improving the account checking frequency and timeliness, ensuring the quasi-real-time account checking (within 1 hour), greatly shortening the account checking timeliness, improving the account checking frequency, reducing the problems of manual account checking error rate and the like.
Based on similar inventive concepts, the embodiment of the present invention further provides a block chain-based reconciliation data processing method, which is preferably applicable to the service-side reconciliation data processing apparatus 20 located on the service side.
Fig. 11 is a flowchart of the reconciliation data processing method, which, as shown in fig. 11, includes:
And 1104, generating a job hash chain table according to the compressed detailed data and the hash of the detailed data.
Specifically, generating an ith job data block according to the hash of each i-th detailed data and the (i-1) th detailed data after compression; and then generating the job hash chain table according to the generated plurality of job data blocks.
The method comprises the steps of obtaining service party operation data according to an operation batch number in a received account checking operation result, compressing each detailed data in the service party operation data, generating Hash of the detailed data, then generating an operation Hash chain table according to each compressed detailed data and Hash of each detailed data, and then sending an account checking request message containing chain table head Hash to a client side so as to facilitate the client side to obtain the service party operation data and perform account checking processing with locally stored operation data.
In practical operation, when the reconciliation flow based on the multi-party computing platform is executed, the following operations can be executed: based on a predetermined segmentation algorithm, segmenting the service party account checking data into a plurality of service party account checking data segments, wherein the service party account checking data comprises: the summary amount and the detailed data number of the service party operation data; subsequently, the reconciliation data segments of the plurality of service parties are respectively encrypted based on a preset encryption algorithm; and then sending the encrypted reconciliation data of the plurality of service parties to the multi-party computing platform in a segmented manner so as to facilitate the reconciliation flow of the multi-party computing platform.
The embodiment of the present invention further provides a block chain-based reconciliation data processing method, which can be preferably applied to the above client-side reconciliation data processing apparatus 30 located on the client side.
Fig. 12 is a flowchart of the reconciliation data processing method, which, as shown in fig. 12, includes:
and step 1204, performing reconciliation processing according to all the acquired job detail data and the locally stored client side job data.
Through the steps, the subsequent account checking processing can be realized when the account checking operation based on the multi-party computing platform fails.
Before step 1201 is executed, a reconciliation operation result from the multi-party computing platform is received, and when the reconciliation operation result is a reconciliation failure, the step 1201 and the step 1204 are executed.
In practical operation, when the reconciliation flow based on the multi-party computing platform is executed, the following operations can be executed: segmenting the client-side reconciliation data into a plurality of client-side reconciliation data segments based on a predetermined segmentation algorithm, the client-side reconciliation data comprising: the summary amount and the detail data number of the client side job data; encrypting the plurality of client reconciliation data segments respectively based on a predetermined encryption algorithm; and sending the encrypted reconciliation data of the plurality of clients to the multi-party computing platform in a segmented manner so as to facilitate the reconciliation flow of the multi-party computing platform.
For the specific flow of each step, reference may be made to the description in the above system embodiment, and details are not described here.
The present embodiment also provides an electronic device, which may be a desktop computer, a tablet computer, a mobile terminal, and the like, but 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 reconciliation data processing apparatus/system based on the block chain, which are incorporated herein and repeated details are not repeated.
Fig. 13 is a schematic block diagram of a system configuration of an electronic apparatus 600 according to an embodiment of the present invention. As shown in fig. 13, the electronic device 600 may include a central processor 100 and a memory 140; the memory 140 is coupled to the central processor 100. Notably, this diagram is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.
In one embodiment, the block chain based reconciliation data processing function may be integrated into the central processor 100. The central processor 100 may be configured to control as follows:
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 comprises: job batch number;
obtaining the operation data of a service party according to the operation batch number, wherein the operation data of the service party comprises: multiple strokes of detail data;
compressing each i of detail data in the server side operation data, and generating hash of the detail data, wherein i is greater than or equal to 1 and is less than or equal to n, and i and n are positive integers greater than or equal to 1;
generating an operation hash chain table according to each compressed detailed data and the hash of each detailed data;
and sending the account checking request message containing the chain table head hash to the client side, wherein the chain table head hash is the hash of the nth detailed data.
As can be seen from the above description, according to the electronic device provided in the embodiment of the present application, service party job data is obtained according to a job batch number in a received reconciliation operation result, each piece of detail data in the service party job data is compressed, a hash of the detail data is generated, then a job hash chain table is generated according to each compressed detail data and the hash of each piece of detail data, and then a reconciliation request packet including a chain table header hash is sent to a client, so that the client can obtain the service party job data and perform reconciliation processing with locally stored job data.
In another embodiment, the block chain based reconciliation data processing apparatus/system can be configured separately from the central processor 100, for example, the block chain based reconciliation data processing apparatus/system can be configured as a chip connected with the central processor 100, and the block chain based reconciliation data processing function can be realized by the control of the central processor.
As shown in fig. 13, the electronic device 600 may further include: communication module 110, input unit 120, audio processing unit 130, display 160, power supply 170. It is noted that the electronic device 600 does not necessarily include all of the components shown in FIG. 13; furthermore, the electronic device 600 may also comprise components not shown in fig. 13, which may be referred to in the prior art.
As shown in fig. 13, the central processor 100, sometimes referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device, the central processor 100 receiving input and controlling the operation of the various components of the electronic device 600.
The memory 140 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 100 may execute the program stored in the memory 140 to realize information storage or processing, etc.
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 an object to be displayed, such as an image or a character. The display may be, for example, an LCD display, but is not limited thereto.
The memory 140 may be a solid state memory such as Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 140 may also be some other type of device. Memory 140 includes buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application/function storage section 142, and the application/function storage section 142 is used to store application programs and function programs or a flow for executing the operation of the electronic device 600 by the central processing unit 100.
The memory 140 may also include a data store 143, the data store 143 for storing data, such as contacts, digital data, pictures, sounds, and/or any other data used by the electronic device. The driver storage portion 144 of the memory 140 may include various drivers of the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging application, address book application, etc.).
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 an input signal and receive an output signal, which may be the same as in the case of a conventional mobile communication terminal.
Based on different communication technologies, a plurality of communication modules 110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and receive audio input from the microphone 132 to implement general telecommunications functions. Audio processor 130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, an audio processor 130 is also coupled to the central processor 100, so that recording on the local can be enabled through a microphone 132, and so that sound stored on the local can be played through a speaker 131.
The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the above block chain-based reconciliation data processing method.
In summary, in order to solve the problems of security and accuracy of online account checking of the bank and enterprise, the embodiment of the present invention provides a multi-party secure block chain bank and enterprise account checking system by combining the characteristics of non-falsification of a block chain, data sharing and a data protection mechanism of multi-party secure computation, and the system mainly improves the convenience of bank and enterprise account checking from the following three aspects: 1. optimizing a client account checking flow and providing a simple safe block chain account checking scheme interface for a client; 2. private data are protected, account book data of all parties are stored locally, plaintext data cannot be exported, ciphertext data are calculated and checked on the basis of a multi-party safety computing platform, a checking result is obtained, and the data can be used and cannot be seen; 3. and the expandability is realized, the alliance of a multi-enterprise ERP system and a bank is established, and simple access and real-time account checking are realized.
The preferred embodiments of the present invention have been described above with reference to the accompanying drawings. The many features and advantages of the embodiments are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the embodiments which fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the embodiments of the invention to the exact construction and operation illustrated and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope thereof.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (16)
1. A reconciliation data processing method based on a block chain is characterized by comprising the following steps:
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 comprises: job batch number;
obtaining the operation data of a service party according to the operation batch number, wherein the operation data of the service party comprises: multiple strokes of detail data;
compressing each i of detail data in the server side operation data, and generating hash of the detail data, wherein i is greater than or equal to 1 and is less than or equal to n, and i and n are positive integers greater than or equal to 1;
generating an operation hash chain table according to each compressed detailed data and the hash of each detailed data;
and sending the account checking request message containing the chain table head hash to the client side, wherein the chain table head hash is the hash of the nth detailed data.
2. The method of claim 1, wherein generating the job hash chain table from the compressed each piece of detail data and the hash of each piece of detail data comprises:
generating an ith job data block according to the hash of each i-th detailed data and the i-1 th detailed data after compression;
and generating the job hash chain table according to the generated plurality of job data blocks.
3. The method of claim 1, wherein prior to receiving a reconciliation operation result from the multi-party computing platform, the method further comprises:
based on a predetermined segmentation algorithm, segmenting the service party account checking data into a plurality of service party account checking data segments, wherein the service party account checking data comprises: the summary amount and the detailed data number of the service party operation data;
encrypting the reconciliation data segments of the plurality of service parties respectively based on a predetermined encryption algorithm;
and sending the encrypted reconciliation data of the plurality of service parties to the multi-party computing platform in a segmented manner.
4. A reconciliation data processing method based on a block chain is characterized by comprising the following steps:
receiving a reconciliation request message from a service party, wherein the reconciliation request message comprises: hash of the chain header;
obtaining a corresponding operation data block stored on a block chain according to the chain table head hash, wherein the operation data block comprises: hash of the job detail data and the previous job data block;
acquiring the affiliated operation detail data of the corresponding data block according to the hash of the previous operation data block so as to acquire all the operation detail data;
and performing reconciliation processing according to the acquired all job detail data and the locally stored client side job data.
5. The method of claim 4, wherein prior to receiving a reconciliation request message from the service party, the method further comprises:
and receiving a reconciliation operation result from the multi-party computing platform, wherein the reconciliation operation result is a reconciliation failure.
6. The method of claim 5, wherein prior to receiving a reconciliation operation result from the multi-party computing platform, the method further comprises:
segmenting the client-side reconciliation data into a plurality of client-side reconciliation data segments based on a predetermined segmentation algorithm, the client-side reconciliation data comprising: the summary amount and the detail data number of the client side job data;
encrypting the plurality of client reconciliation data segments respectively based on a predetermined encryption algorithm;
and sending the encrypted plurality of client account checking data segments to the multi-party computing platform.
7. A block chain based reconciliation data processing apparatus, wherein the apparatus is located at a server side, the apparatus comprising:
the account checking result receiving unit is used for receiving an account checking operation result from the multi-party computing platform, wherein the account checking operation result is an account checking failure, and the account checking operation result comprises: job batch number;
a server job data obtaining unit, configured to obtain server job data according to the job batch number, where the server job data includes: multiple strokes of detail data;
the compression operation unit is used for compressing each i of detail data in the server side operation data and generating hash of the detail data, wherein i is greater than or equal to 1 and n is a positive integer greater than or equal to 1;
the hash chain table generating unit is used for generating an operation hash chain table according to each compressed detailed data and the hash of each detailed data;
and the account checking request message sending unit is used for sending the account checking request message containing the chain table head hash to the client side, wherein the chain table head hash is the hash of the nth detailed data.
8. The apparatus of claim 7, wherein the hash chain generation unit comprises:
the data block generating module is used for generating an ith job data block according to the hash of each i-th detailed data and the i-1 st detailed data after compression;
and the hash linked list generating module is used for generating the operation hash linked list according to the generated operation data blocks.
9. The apparatus of claim 7, further comprising:
a first segmentation unit configured to segment, based on a predetermined segmentation algorithm, service-side reconciliation data into a plurality of service-side reconciliation data segments, the service-side reconciliation data comprising: the summary amount and the detailed data number of the service party operation data;
a first encryption unit, configured to encrypt the plurality of server reconciliation data segments based on a predetermined encryption algorithm, respectively;
and the first encrypted data sending unit is used for sending the plurality of encrypted service party account checking data segments to the multi-party computing platform.
10. A block chain based reconciliation data processing apparatus, wherein the apparatus is located at a client side, the apparatus comprising:
a reconciliation request message receiving unit, configured to receive a reconciliation request message from a service party, where the reconciliation request message includes: hash of the chain header;
a data block obtaining unit, configured to obtain, according to the chain header hash, a corresponding job data block stored on a blockchain, where the job data block includes: hash of the job detail data and the previous job data block;
the operation detail data acquisition unit is used for acquiring the operation detail data of the corresponding data block according to the hash of the previous operation data block so as to acquire all the operation detail data;
and the account checking unit is used for performing account checking processing according to the acquired all job detail data and the locally stored client side job data.
11. The apparatus of claim 10, further comprising:
and the account checking operation result receiving unit is used for receiving an account checking operation result from the multi-party computing platform, and the account checking operation result is an account checking failure.
12. The apparatus of claim 10, further comprising:
a second segmentation unit, configured to segment the client-side reconciliation data into a plurality of client-side reconciliation data segments based on a predetermined segmentation algorithm, where the client-side reconciliation data includes: the summary amount and the detail data number of the client side job data;
a second encryption unit configured to encrypt the plurality of client reconciliation data segments, respectively, based on a predetermined encryption algorithm;
and the second encrypted data sending unit is used for sending the plurality of encrypted client account checking data segments to the multi-party computing platform.
13. A block chain based reconciliation data processing system, the system comprising: the blockchain based reconciliation data processing device at the server side according to any one of claims 7 to 9, the blockchain based reconciliation data processing device at the client side according to any one of claims 10 to 12 and the multi-party computing platform comprising at least one computing node comprising:
a data receiving unit, configured to receive service-side reconciliation data from a service side and receive client-side reconciliation data from a client side, where the service-side reconciliation data and the client-side reconciliation data both include: the server side account checking data and the client side account checking data are encrypted by the same encryption algorithm;
a comparison unit for comparing whether the service side account checking data and the client side account checking data are consistent according to a preset comparison algorithm so as to execute account checking operation;
and the account checking result sending unit is used for sending the account checking operation result to the service party and the client party respectively.
14. The system of claim 13, wherein when the computing node is a plurality of computing nodes,
the first dividing unit of the reconciliation data processing device on the service side is specifically configured to: based on the preset segmentation algorithm, segmenting the server side account checking data into a plurality of server side account checking data segments with the same number as that of the computing nodes;
the second segmentation unit of the reconciliation data processing device on the client side is specifically configured to: based on the preset segmentation algorithm, segmenting the client side account checking data into a plurality of client side account checking data segments with the same number as that of the computing nodes;
the data receiving unit is specifically configured to: receiving a server side account checking data segment and a client side account checking data segment;
the comparison unit is specifically configured to: comparing the received server side account checking data segment with the client side account checking data segment according to the preset comparison algorithm to generate a comparison result;
the multi-party computing platform further comprises:
and the comparison result summarizing unit is used for summarizing the comparison results of the calculation node comparison units and generating the reconciliation operation result.
15. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 6 are implemented when the processor executes the program.
16. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110216207.2A CN112767113A (en) | 2021-02-26 | 2021-02-26 | Account checking data processing method, device and system based on block chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110216207.2A CN112767113A (en) | 2021-02-26 | 2021-02-26 | Account checking data processing method, device and system based on block chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112767113A true CN112767113A (en) | 2021-05-07 |
Family
ID=75704169
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110216207.2A Pending CN112767113A (en) | 2021-02-26 | 2021-02-26 | Account checking data processing method, device and system based on block chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112767113A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326333A (en) * | 2021-06-30 | 2021-08-31 | 平安消费金融有限公司 | Data processing method, system, computer device and computer storage medium |
| CN113360935A (en) * | 2021-07-26 | 2021-09-07 | 永旗(北京)科技有限公司 | Account checking method and system based on block chain technology |
| CN115774885A (en) * | 2023-01-29 | 2023-03-10 | 成方金融科技有限公司 | Account checking method and device based on homomorphic encryption, electronic equipment and storage medium |
| WO2023109841A1 (en) * | 2021-12-15 | 2023-06-22 | 中国人民银行数字货币研究所 | Blockchain-based reconciliation method, apparatus, and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109767245A (en) * | 2019-01-08 | 2019-05-17 | 中国联合网络通信集团有限公司 | Consumption information checking method, equipment and storage medium |
| CN109859024A (en) * | 2019-01-23 | 2019-06-07 | 陕西优米数据技术有限公司 | A kind of tax system common recognition method based on alliance's chain |
| CN111861482A (en) * | 2020-09-22 | 2020-10-30 | 支付宝(杭州)信息技术有限公司 | Block chain account checking method and system |
-
2021
- 2021-02-26 CN CN202110216207.2A patent/CN112767113A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109767245A (en) * | 2019-01-08 | 2019-05-17 | 中国联合网络通信集团有限公司 | Consumption information checking method, equipment and storage medium |
| CN109859024A (en) * | 2019-01-23 | 2019-06-07 | 陕西优米数据技术有限公司 | A kind of tax system common recognition method based on alliance's chain |
| CN111861482A (en) * | 2020-09-22 | 2020-10-30 | 支付宝(杭州)信息技术有限公司 | Block chain account checking method and system |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326333A (en) * | 2021-06-30 | 2021-08-31 | 平安消费金融有限公司 | Data processing method, system, computer device and computer storage medium |
| CN113360935A (en) * | 2021-07-26 | 2021-09-07 | 永旗(北京)科技有限公司 | Account checking method and system based on block chain technology |
| WO2023109841A1 (en) * | 2021-12-15 | 2023-06-22 | 中国人民银行数字货币研究所 | Blockchain-based reconciliation method, apparatus, and system |
| CN115774885A (en) * | 2023-01-29 | 2023-03-10 | 成方金融科技有限公司 | Account checking method and device based on homomorphic encryption, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112767113A (en) | Account checking data processing method, device and system based on block chain | |
| CN109936457B (en) | Block chain multi-party witness method, device, equipment and computer readable storage medium | |
| CN110675145B (en) | Block chain-based data processing method, device, terminal and storage medium | |
| CN107317672A (en) | A kind of light weight terminating machine block catenary system | |
| CN111080295A (en) | Block chain-based electronic contract processing method and equipment | |
| CN111563820B (en) | Intelligent contract parallel execution method and device | |
| CN112163946A (en) | Accounting processing method and device based on distributed transaction system | |
| US11455295B2 (en) | Electronic document workflow | |
| CN104283975A (en) | File distribution method and device | |
| CN112600830B (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN107169364A (en) | A kind of data security method and related system | |
| CN112787812A (en) | Block chain-based calculation job processing method, device and system | |
| CN107070942A (en) | A kind of data security method and related system | |
| CN108052550B (en) | Annuity data receiving method and device, computer equipment and storage medium | |
| CN113722753A (en) | Privacy data processing method, device and system based on block chain | |
| CN112783853B (en) | Operation processing method, device and system based on block chain | |
| CN111711512B (en) | Message sending method and device | |
| US10970741B2 (en) | Method and system for integrating audience data with a social media site | |
| CN112860805A (en) | Block chain data interaction method and system | |
| US8005902B2 (en) | System and method for accelerated dynamic data message generation and transmission | |
| CN113191881A (en) | Financial business supervision data processing method, device and system based on block chain | |
| CN112949866A (en) | Poisson regression model training method and device, electronic equipment and storage medium | |
| CN115526629A (en) | Receipt transaction method and device based on block chain network and identity authentication device | |
| CN114238585A (en) | Query method and device based on 5G message, computer equipment and storage medium | |
| CN111198807B (en) | Data stream analysis method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |