Data processing method and device based on blockchain

Abstract

The embodiment of the present application discloses a data processing method and device based on blockchain, which includes: the verification node obtains the data verification request sent by the target user, and if it is determined that the data verification request is a legitimate request, a ticket acquisition request including authorization information is sent to the ticket service node, so that when the ticket service node determines that the authorized party identifier is the same as the verification node identifier included in the ticket acquisition request, it obtains the node public key of the ticket service node, and the ticket storage block identifier corresponding to the ticket identifier is returned to the verification node. According to the received ticket storage block identifier, the corresponding ticket storage block is obtained from the blockchain. If the ticket storage block is successfully decrypted based on the node public key, the to-be-verified bill corresponding to the bill identifier is obtained from the decrypted ticket storage block, and data verification is performed based on the to-be-verified bill. The use of the embodiment of the present application can improve reimbursement efficiency and bill authenticity.

Description

Technical Field

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

[0002] At present, there are two main ways to reimburse bills, one is offline reimbursement and the other is online reimbursement. In the offline reimbursement method, users are usually required to obtain printed paper bills from the consumer after consumption, or obtain electronic bills and print them out by themselves, and then take them to the reimbursement agency for reimbursement. Among them, the offline reimbursement method requires more manpower and resources, so the online reimbursement method is more popular among users. In this method, users can submit the invoices to be reimbursed to the reimbursement agency online for bill reimbursement, which does not require printing paper bills, saves more paper resources, and is more environmentally friendly.

[0003] However, in the prior art, whether it is an online or offline reimbursement method, there may be a situation where the receipts provided by the user are not authentic, so a lot of manpower and time are required to verify the received receipts, which reduces the efficiency of receipt reimbursement. Summary of the invention

[0004] The embodiments of the present application provide a blockchain-based data processing method and device, which can improve reimbursement efficiency and bill authenticity and has high applicability.

[0005] In a first aspect, an embodiment of the present application provides a data processing method based on blockchain, the method comprising:

[0006] The verification node obtains a data verification request sent by a target user, the data verification request carries the first signature information of the target user on the data verification request, the data verification request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the ticket identifier;

[0007] If the data cancellation request is determined to be a legitimate request based on the first signature information, a ticket acquisition request including the authorization information is sent to the ticket service node, so that when the ticket service node determines that the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request, the node public key of the ticket service node and the ticket storage block identifier corresponding to the ticket identifier are obtained and returned to the cancellation node;

[0008] The above-mentioned cancellation node obtains the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the above-mentioned bill storage block is decrypted successfully based on the above-mentioned node public key, the bill to be cancelled corresponding to the above-mentioned bill identifier is obtained from the decrypted bill storage block, and data cancellation is performed based on the above-mentioned bill to be cancelled.

[0009] In a second aspect, an embodiment of the present application provides a data processing device based on blockchain, the device comprising:

[0010] A verification request acquisition module is used to acquire a data verification request sent by a target user, wherein the data verification request carries the first signature information of the target user on the data verification request, and the data verification request includes the authorization information of the target user, and the authorization information includes an authorized party identifier and a bill identifier;

[0011] A cancellation request processing module, configured to send a ticket acquisition request including the authorization information to a ticket service node if the data cancellation request is determined to be a legitimate request based on the first signature information, so that when the ticket service node determines that the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request, the node public key of the ticket service node and the ticket storage block identifier corresponding to the ticket identifier are returned to the cancellation node;

[0012] The data cancellation module is used to obtain the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is decrypted successfully based on the node public key, the bill to be cancelled corresponding to the bill identifier is obtained from the decrypted bill storage block, and data cancellation is performed based on the bill to be cancelled.

[0013] In conjunction with the second aspect, in a possible implementation, the cancellation request processing module includes an identity authentication unit and a ticket acquisition unit, and the identity authentication unit includes:

[0014] The public key acquisition subunit is used to obtain the target user public key corresponding to the above target user from the public key storage block;

[0015] A signature decryption subunit, used to decrypt the first signature information based on the target user public key to obtain a first hash value;

[0016] The user identity determination unit is used to perform a hash operation on the data verification request to obtain a second hash value, and if the first hash value is the same as the second hash value, determine that the data verification request is a legal request.

[0017] In conjunction with the second aspect, in a possible implementation manner, the identity verification unit is further configured to:

[0018] If the data verification request is determined to be a legitimate request based on the first signature information, and the blockchain does not include the data verification record corresponding to the ticket identifier, a ticket acquisition request including the authorization information is sent to the ticket service node.

[0019] In conjunction with the second aspect, in a possible implementation manner, the data cancellation request further includes the data receiving account of the target user; the data cancellation module includes a data decryption unit and a data cancellation execution unit, and the data cancellation execution unit is specifically used to:

[0020] Obtain the amount of data to be written off included in the above-mentioned bills to be written off;

[0021] The above-mentioned amount of data to be written off is transferred from the data storage account to the above-mentioned data receiving account.

[0022] In conjunction with the second aspect, in a possible implementation manner, the authorization information further includes an authorization time range; and the apparatus further includes:

[0023] The ticket service node obtains the first time of receiving the ticket acquisition request, and if it is determined that the first time is within the authorization time range, determines whether the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request.

[0024] In conjunction with the second aspect, in a possible implementation, the apparatus further includes a verification record uploading module, and the verification record uploading module includes:

[0025] A verification record generating unit, configured to receive the verification confirmation information sent by the target user, and generate a data verification record according to the verification confirmation information;

[0026] A write-off record consensus unit, used to send the data write-off record and the write-off confirmation information to the consensus nodes in the blockchain system, so that each consensus node determines the verification result of the data write-off record according to the write-off confirmation information;

[0027] A verification record processing unit is used to receive the verification results sent by each consensus node in the above-mentioned blockchain system, determine the consensus result of the above-mentioned data verification record according to each verification result, and when it is determined that a consensus is reached on the above-mentioned data verification record, add a data verification record storage block including the above-mentioned data verification record to the above-mentioned blockchain.

[0028] In conjunction with the second aspect, in a possible implementation, the verification record processing unit includes a consensus result determination subunit and a verification record storage subunit, and the consensus result determination subunit is specifically used to:

[0029] If the proportion of verification passes in the verification results returned by the above-mentioned consensus nodes is not less than the preset passing proportion, it is determined that the above-mentioned consensus nodes have reached a consensus on the above-mentioned data verification record.

[0030] In a third aspect, an embodiment of the present application provides a terminal device, the terminal device includes a processor and a memory, the processor and the memory are connected to each other. The memory is used to store a computer program that supports the terminal device to execute the method provided by the first aspect and / or any possible implementation of the first aspect, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method provided by the first aspect and / or any possible implementation of the first aspect.

[0031] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program includes program instructions, which, when executed by a processor, enable the processor to execute the method provided by the above-mentioned first aspect and / or any possible implementation method of the first aspect.

[0032] In an embodiment of the present application, the verification node obtains a data verification request sent by a target user, wherein the data verification request carries the first signature information of the target user for the data verification request, and the data verification request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the bill identifier. If the data verification request is determined to be a legitimate request based on the first signature information, a bill acquisition request including the authorization information is sent to the bill service node, so that when the bill service node determines that the authorized party identifier is the same as the verification node identifier included in the bill acquisition request, it obtains the node public key of the bill service node, and the bill storage block identifier corresponding to the bill identifier is returned to the verification node. The verification node obtains the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is successfully decrypted based on the node public key, the bill to be verified corresponding to the bill identifier is obtained from the decrypted bill storage block, and data verification is performed according to the bill to be verified. By adopting the embodiment of the present application, the reimbursement efficiency and bill authenticity can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0034] Figure 1 It is a structural diagram of a blockchain system provided by an embodiment of the present application;

[0035] Figure 2 This is a flowchart of a blockchain-based data processing method provided by an embodiment of the present application;

[0036] Figure 2aIt is a schematic diagram of the process of verifying the first signature information provided by an embodiment of the present application;

[0037] Figure 2b It is a schematic diagram of the structure of the blockchain and blocks provided in the embodiment of the present application;

[0038] Figure 3 This is another flowchart of the blockchain-based data processing method provided in an embodiment of the present application;

[0039] Figure 4 This is a schematic diagram of a block chain-based data processing device provided in an embodiment of the present application;

[0040] Figure 5 is another structural schematic diagram of a blockchain-based data processing device provided in an embodiment of the present application;

[0041] Figure 6 It is a schematic diagram of the structure of the terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0043] See also Figure 1 , Figure 1 This is a schematic diagram of the structure of a blockchain system provided by an embodiment of the present application. Figure 1 As shown in FIG, a blockchain system refers to a system for sharing data between blockchain nodes. The blockchain system may include various types of blockchain nodes, such as Figure 1The verification node 1, verification node 2, verification node 3, ticket service node 1, ticket service node 2, etc. are shown. For the convenience of description, the verification node and the ticket service node, etc. can be referred to as nodes, wherein each node has a connection relationship with other nodes. It is understandable that any node in the blockchain system can be any form of computing device, such as a server, a terminal, etc., which is not limited here. It should be understood that the terminal includes but is not limited to mobile phones, tablet computers, laptops, PDAs, mobile Internet devices (mobile internet devices, MIDs), etc., which are not limited here. Each node can receive input information when performing normal work, and maintain the shared data in the blockchain system based on the received input information. Among them, the consensus process is controlled by a pre-selected node (i.e., a consensus node). In order to ensure the information intercommunication within the blockchain system, there can be an information connection between each node in the blockchain system, and the nodes can transmit information through the above information connection. For example, when any blockchain node in the blockchain system receives input information, other blockchain nodes in the blockchain system obtain the input information according to the consensus algorithm, and store the input information as data in the shared data, so that the data stored on all blockchain nodes in the blockchain system are consistent. It should be understood that the entire blockchain system is maintained by various nodes. The consensus node can be a node pre-determined from multiple nodes included in the blockchain system based on the consensus mechanism of the blockchain system. For example, the consensus node can be Figure 1 The cancellation nodes 1, 2 and 3 are shown.

[0044] Among them, for each blockchain node in the blockchain system, there is a blockchain node identifier corresponding to it, and each blockchain node in the blockchain system can store the blockchain node identifiers of other blockchain nodes in the blockchain system, so that the generated blocks can be broadcast to other blockchain nodes in the blockchain system according to the blockchain node identifiers of other blockchain nodes. Each blockchain node can maintain a blockchain node identifier list as shown in the following table, and the blockchain node name and blockchain node identifier are stored in the blockchain node identifier list accordingly. Among them, the blockchain node identifier can be an IP (Internet Protocol, a protocol for interconnecting networks) address and any other information that can be used to identify the blockchain node. Table 1 only takes the IP address as an example for explanation.

[0045] Blockchain node name Blockchain node identification Blockchain Node 1 117.114.151.174 Blockchain Node 2 117.116.189.145 … … Blockchain Node N 119.123.789.258

[0046] Table 1

[0047] The data processing method based on blockchain provided in the embodiment of the present application can be widely applied to blockchain systems. In the method in the embodiment of the present application, the verification node can obtain the first signature information of the target user for the data verification request carried by the data verification request by obtaining the data verification request sent by the target user. Among them, the data verification request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the bill identifier. If the data verification request is determined to be a legal request based on the first signature information, a bill acquisition request including the authorization information is sent to the bill service node, so that when the bill service node determines that the authorized party identifier is the same as the verification node identifier included in the bill acquisition request, the node public key of the bill service node is obtained, and the bill storage block identifier corresponding to the bill identifier is returned to the verification node. Then the verification node can obtain the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is successfully decrypted based on the node public key, the bill to be cancelled corresponding to the bill identifier is obtained from the decrypted bill storage block, and data verification is performed according to the bill to be cancelled. By adopting the embodiment of the present application, the reimbursement efficiency and bill authenticity can be improved.

[0048] The following will be combined Figures 2 to 6 The methods and related devices provided by the embodiments of the present application are described in detail respectively. The methods provided by the embodiments of the present application may include receiving a data cancellation request and a first signature information, determining the legitimacy of the data cancellation request based on the first signature information, sending a ticket acquisition request to a ticket service node, receiving a node public key and a ticket storage block identifier returned by the ticket service node, acquiring the corresponding ticket storage block according to the ticket storage block identifier, and decrypting the obtained ticket storage block according to the node public key, and acquiring the to-be-cancelled ticket corresponding to the ticket identifier from the decrypted ticket storage block, and other data processing stages. Among them, the implementation methods of the above-mentioned various data processing stages can be found in the following. Figure 2 and Figure 3 The implementation shown.

[0049] See also Figure 2 , Figure 2 A flowchart of a blockchain-based data processing method provided in an embodiment of the present application. The method provided in an embodiment of the present application may include the following steps S201 to S203:

[0050] S201. Obtain a data verification request sent by a target user.

[0051] In some feasible implementations, the verification node can obtain the first signature information of the target user on the data verification request carried by the data verification request, as well as the target user identifier corresponding to the target user included in the information verification request, the target user's authorization information, the target user's data receiving account, and other contents. Among them, the verification node can be the node corresponding to the institution / unit responsible for data verification. For example, the verification node can be the node corresponding to the communication company, or the verification node can be the node corresponding to the insurance company, or the verification node can also be the node corresponding to the social security bureau, etc., without limitation here. The data verification request can be a request for applying for data verification sent by the user based on the user terminal. For example, the data verification request can be a communication expense reimbursement request, an insurance claim request, or a medical insurance reimbursement request, etc., without limitation here. Among them, the target user identity identifier corresponding to the target user can be the target user's resident ID number, etc., without limitation here. It should be understood that the authorization information of the above-mentioned target user can be information for authorizing other nodes to obtain the target user's to-be-reimbursed bills from the blockchain. The authorization information may include the authorizing party identifier, the authorized party identifier, the bill identifier corresponding to the bill to be reimbursed that is allowed to be obtained, etc., which are not limited here. It should be understood that an authorizing party identifier can be used to uniquely mark an authorizing party, an authorized party identifier can be used to uniquely mark an authorized party, and a bill identifier can be used to uniquely mark a bill. Here, the authorizing party is the target user, so the authorizing party identifier can be the resident ID number corresponding to the target user, etc.

[0052] S202: If the data cancellation request is determined to be a legitimate request based on the first signature information, a ticket acquisition request including authorization information is sent to a ticket service node.

[0053] In some feasible implementations, the verification node can verify the legitimacy of the received data verification request based on the first signature information. It is not difficult to understand that the first signature information carried by the above-mentioned data verification request is the signature information generated after the target user encrypts the content of the data verification request. For example, the target user encrypts the content included in the data verification request based on the target user private key to generate the first signature information, and then the data verification request and the first signature information are spliced ​​and sent to the verification node. Among them, when the verification node obtains the data verification request carrying the first signature information, the target user public key corresponding to the target user can be obtained from the public key storage block of the blockchain based on the target user identity corresponding to the target user, and then the first signature information is decrypted based on the target user public key to obtain the first hash value. Further, the verification node performs a hash operation on the content in the data verification request based on the hash algorithm to obtain a second hash value. It should be understood that by comparing the first hash value with the second hash value, it can be determined whether the user identity of the target user who sent the data verification request is a legal identity. That is to say, by verifying the legitimacy of the identity of the user who sent the data verification request, the legitimacy of the data verification request sent can be determined, that is, whether someone has sent the data verification request by impersonating the target user. Here, if the first hash value is the same as the second hash value, it can be determined that the data verification request is a legal request. On the contrary, if the first hash value is different from the second hash value, it can be determined that the data verification request is an illegal request, that is, someone has sent the data verification request by impersonating the target user, and therefore the data verification request can be rejected. It is not difficult to understand that the hash algorithm is a one-way cryptographic system, that is, it is an irreversible mapping from plaintext to ciphertext, there is only an encryption process, no decryption process, and at the same time, the hash algorithm can change the input data of any length to obtain an output of a fixed length, and if there is a change in any character in the input data, it will inevitably lead to a different hash value in the final output. Among them, the hash algorithms used in the embodiments of the present application include MD series hash algorithms, SHA hash algorithms, and SM3 hash algorithms, etc., which are not limited here. The MD series hash algorithms include MD2, MD4, and MD5, etc., and the SHA hash algorithms include SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, etc. For the convenience of description, the hash algorithms mentioned in the embodiments of the present application are all described by taking the SHA-256 algorithm as an example.

[0054] For example, see Figure 2a , Figure 2a Schematic diagram of the process of verifying the first signature information provided by the embodiment of the present application. Figure 2aAs shown, when the target user initiates a data cancellation request based on the user terminal, in order to ensure the validity and security of the content included in the data cancellation request, the target user performs a hash operation on the content to be transmitted (such as the target user identification and authorization information included in the data cancellation request) based on the hash algorithm, and the corresponding hash value can be obtained. Then, the target user encrypts the generated hash value through the target user private key to obtain the first signature information. Then, the target user splices the data cancellation request with the first signature information, and then sends the spliced ​​data to the cancellation node in the blockchain system. When the cancellation node receives the data sent by the target user, it will first parse the received data to obtain the separated data cancellation request and the first signature information. Then, by obtaining the target user public key corresponding to the target user from the public key storage block of the blockchain, the first signature information can be decrypted based on the target user public key to obtain the decrypted first hash value, and the content included in the separated data cancellation request can be hashed based on the hash algorithm to obtain the second hash value. Finally, the cancellation node can obtain the verification result of the data cancellation request by comparing and analyzing the first hash value and the second hash value.

[0055] In some feasible implementations, if the above-mentioned data cancellation request is a legitimate request, the cancellation node may send a ticket acquisition request including the above-mentioned authorization information to the ticket service node, so that when the ticket service node determines that the authorized party identifier in the authorization information included in the ticket acquisition request is the same as the cancellation node identifier included in the ticket acquisition request, the ticket service node can obtain the node public key corresponding to the ticket service node, and the ticket storage block identifier is returned to the above-mentioned cancellation node. Specifically, the ticket acquisition request may include the authorization information of the target user, the cancellation node identifier corresponding to the cancellation node that sends the ticket acquisition request, and other contents, which are not limited here. Among them, the authorization information may include the authorizing party identifier, the authorized party identifier, the ticket identifier corresponding to the to-be-reimbursed ticket that is allowed to be obtained, and other contents, which are not limited here. It should be understood that an authorizing party identifier can be used to uniquely mark an authorizing party, an authorized party identifier can be used to uniquely mark an authorized party, and a ticket identifier can be used to uniquely mark a ticket. Here, the authorizing party is the target user, and the authorized party is the above-mentioned verification node. Therefore, the authorizing party identifier can be the resident ID number corresponding to the target user, and the authorized party identifier can be the verification node identifier corresponding to the above-mentioned verification node, etc. For example, it can be the IP address of the verification node, etc., and there is no limitation here.

[0056] It is not difficult to understand that when the ticket service node receives the ticket acquisition request sent by the verification node, when it is determined that the authorized party identifier in the authorization information included in the ticket acquisition request is the same as the verification node identifier included in the ticket acquisition request, it can be determined that the verification node that sent the ticket acquisition request has the authority to obtain the ticket corresponding to the ticket identifier included in the authorization information. Therefore, the ticket service node can return its corresponding node public key and the ticket storage block identifier to the above verification node. Among them, the above-mentioned ticket storage block identifier can be used to uniquely mark a ticket storage block in the blockchain, and the ticket storage block includes the ticket corresponding to the ticket identifier in the authorization information. Optionally, in some feasible implementations, if the authorization information also includes an authorization time range, the ticket service node can further obtain the time of receiving the above-mentioned ticket acquisition request, that is, the first time. Among them, when it is determined that the first time is within the authorization time range, and the authorized party identifier in the authorization information is the same as the verification node identifier in the ticket acquisition request, then the corresponding node public key and the ticket storage block identifier are returned to the above verification node. It should be understood that each bill storage block identifier can be a unique identifier pre-defined for each bill storage block. For example, the identifier can be composed of numbers, letters and / or symbols according to certain arrangement rules. Alternatively, the bill storage block identifier can also be a block height. Alternatively, the bill storage block identifier can also be a timestamp. Alternatively, the bill storage block identifier can also be a 32-byte hash value obtained by performing a secondary hash calculation on the block header using the SHA256 algorithm, i.e., a block hash value. It is also commonly referred to as a block header hash value because the only data involved in the calculation is the data content encapsulated in the block header. Specifically, the calculation formula for the block hash value can be defined as:

[0057] SHA256(SHA256(version+prev_hash+merkle_root+time+bits+x)) Formula 1

[0058] Among them, version indicates the version number of the block, prev_hash is the hash value of the previous block, merkle_root is the Merkle tree root of this block, time is the timestamp, bits is the difficulty value, and x is a random number. Based on the above formula 1, a secondary hash calculation is performed on the data content encapsulated in the block header to obtain a 32-byte hash value, that is, the block hash value. Usually, the block hash value is presented in the form of 64 hexadecimal numbers.

[0059] It is not difficult to understand that a block can be composed of a block header and a block body. The block header encapsulates the block version number, the hash value of the previous block, the timestamp, the difficulty value, the random number, the Merkle tree root and other data contents, and the block body includes complete business data. For easy understanding, please refer to Figure 2b , Figure 2b Schematic diagram of the structure of blockchain and blocks provided in the embodiment of the present application. Figure 2b The blockchain shown can contain at least Figure 2b Block N, Block N+1 and Block N+2 are shown, where N can be a positive integer. It should be understood that each block can be composed of a block header and a block body. The block header encapsulates the block version number, the hash value of the previous block, the timestamp, the difficulty value, the random number, the Merkle tree root and other data contents, and the block body includes complete transaction data. For example, the block body may include transaction data 1, transaction data 2, ..., transaction data m, etc., where m is a positive integer. Further, as Figure 2b As shown, the present embodiment takes block N+1 as an example to illustrate the block structure of block N+1. Block N+1 can be composed of Figure 2b The block header and block body shown in the figure are composed of the block header and block body, where the block header can contain the version number of the block, the hash value of the previous block (i.e. Figure 2b The hash value of block N shown in the figure), timestamp, calculated difficulty value, random number set for generating block N+1, and the Merkle tree root of this block (here this block is block N+1), etc. In addition, Figure 2b The block body shown may include transaction data 1, transaction data 2, transaction data 3, and transaction data 4 obtained and packaged from the transaction pool during the period before block N+1 is generated and after block N is generated, and there is no limitation here.

[0060] S203. Obtain the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is decrypted successfully based on the node public key, obtain the bill to be cancelled corresponding to the bill identifier from the decrypted bill storage block, and perform data cancellation based on the bill to be cancelled.

[0061] In some feasible implementations, the cancellation node can obtain the bill storage block corresponding to the bill storage block identifier from the blockchain according to the received bill storage block identifier by receiving the node public key and bill storage block identifier sent by the bill service node. Then, the obtained bill storage block is decrypted based on the node public key. Among them, if the above-mentioned bill storage block can be successfully decrypted based on the above-mentioned node public key, the bill to be cancelled corresponding to the bill identifier can be obtained from the decrypted bill storage block, and then data cancellation can be performed based on the bill to be cancelled. It should be understood that if the content included in the bill storage block cannot be decrypted based on the above-mentioned node public key, the target user's data reimbursement request can be rejected, or an abnormal interruption information can be sent to the above-mentioned target user, etc., which is not limited here. Here, when data cancellation is performed based on the bill to be cancelled, the cancellation node can transfer the above-mentioned amount of data to be cancelled from its own data storage account to the data receiving account of the target user by determining the amount of data to be cancelled from the bill to be cancelled.

[0062] In an embodiment of the present application, the verification node obtains a data verification request sent by a target user, wherein the data verification request carries the first signature information of the target user for the data verification request, and the data verification request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the bill identifier. If the data verification request is determined to be a legitimate request based on the first signature information, a bill acquisition request including the authorization information is sent to the bill service node, so that when the bill service node determines that the authorized party identifier is the same as the verification node identifier included in the bill acquisition request, it obtains the node public key of the bill service node, and the bill storage block identifier corresponding to the bill identifier is returned to the verification node. The verification node obtains the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is successfully decrypted based on the node public key, the bill to be verified corresponding to the bill identifier is obtained from the decrypted bill storage block, and data verification is performed according to the bill to be verified. By adopting the embodiment of the present application, the reimbursement efficiency and bill authenticity can be improved.

[0063] See also Figure 3 , Figure 3 It is another flowchart of the data processing method based on blockchain provided by the embodiment of the present application. The method provided by the embodiment of the present application can be explained by the implementation provided by the following steps S301 to S304:

[0064] S301. Obtain a data verification request sent by a target user.

[0065] The specific implementation of step S301 can be found in Figure 2 The description of step S201 in the corresponding embodiment will not be repeated here.

[0066] S302: If the data verification request is determined to be a legitimate request based on the first signature information, and the blockchain does not include a data verification record corresponding to the ticket identifier, a ticket acquisition request including authorization information is sent to the ticket service node.

[0067] In some feasible implementations, if the data cancellation request is determined to be a legitimate request based on the first signature information, and the blockchain does not include a data cancellation record corresponding to the ticket identifier, a ticket acquisition request including authorization information may be sent to the ticket service node. The specific implementation method for determining whether the data cancellation request is legitimate based on the first signature information can be found in Figure 2 The description of step S202 in the corresponding embodiment will not be repeated here.

[0068] S303. Obtain the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is decrypted successfully based on the node public key, obtain the bill to be cancelled corresponding to the bill identifier from the decrypted bill storage block, and perform data cancellation based on the bill to be cancelled.

[0069] The specific implementation of step S303 can be found in Figure 2 The description of step S203 in the corresponding embodiment will not be repeated here.

[0070] S304, receiving the verification confirmation information sent by the target user, generating a data verification record according to the verification confirmation information, sending the data verification record and the verification confirmation information to the consensus node in the blockchain system, receiving the verification results sent by each consensus node in the blockchain system, determining the consensus result of the data verification record according to each verification result, and when it is determined that a consensus is reached on the data verification record, adding the data verification record storage block including the data verification record to the blockchain.

[0071] In some feasible implementations, when the target user determines that the amount of data to be written off is received in the data receiving account, the written-off confirmation information can be sent to the writing-off node. Here, the written-off confirmation information may include the data writing-off time, the bill identifier corresponding to the written-off bill, the written-off data volume, the data sender account (i.e., the data storage account of the writing-off node), the data receiver account (i.e., the data receiving account of the target user), etc. And the written-off confirmation information sent by the target user has been encrypted in advance according to the target user's private key. Therefore, when the writing-off node receives the written-off confirmation information sent by the target user, the written-off confirmation information can be decrypted according to the target user's public key, and after the decryption is successful, a data writing-off record is generated according to the written-off confirmation information. Among them, the data writing record may include the data writing time, the bill identifier corresponding to the written-off bill, the written-off data volume, the data sender account (i.e., the data storage account of the writing-off node), the data receiver account (i.e., the data receiving account of the target user), etc. Further, the verification node may send the data verification record and the verification confirmation information to the consensus node in the blockchain system, so that each consensus node can determine the verification result of the data verification record according to the verification confirmation information, and return the determined verification result to the above-mentioned verification node. It should be understood that the consensus node in the embodiment of the present application can be a node pre-determined from multiple nodes included in the blockchain system based on the consensus mechanism of the blockchain system. For example, the consensus mechanism includes but is not limited to the Proof of Work (PoW) consensus mechanism, the Proof of Stake (PoS) consensus mechanism, the Delegated Proof of Stake (DPoS) consensus mechanism, the Practical Byzantine Fault Tolerance (PBFT), the Proof of Importance (POI) consensus mechanism, the Proof of Participation (POP) consensus mechanism, etc., which are not limited here.

[0072] Among them, the verification node can determine the consensus result of the data verification record according to each verification result by receiving the verification results sent by each consensus node in the blockchain system. Specifically, if the verification pass ratio of the verification results returned by each consensus node is not less than the preset pass ratio, it can be determined that each consensus node has reached a consensus on the data verification record. Then, a data verification record storage block including the bill identifier and the data verification record can be added to the blockchain. Here, in the data verification record storage block, the bill identifier can be used as an index of the data verification record. Therefore, when a data verification request sent by the target user is received later, it can be checked whether the blockchain includes the data verification record corresponding to the bill identifier according to the bill identifier included in the data verification request. Among them, if there is a data verification record corresponding to the bill identifier in the blockchain, the data verification request of the target user is rejected. If the blockchain does not include the data verification record corresponding to the bill identifier, and the data verification request is determined to be a legitimate request based on the first signature information, a bill acquisition request including authorization information is sent to the bill service node.

[0073] In an embodiment of the present application, the verification node obtains a data verification request sent by a target user, wherein the data verification request carries the first signature information of the target user for the data verification request, and the data verification request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the bill identifier. If the data verification request is determined to be a legitimate request based on the first signature information, a bill acquisition request including the authorization information is sent to the bill service node, so that when the bill service node determines that the authorized party identifier is the same as the verification node identifier included in the bill acquisition request, it obtains the node public key of the bill service node, and the bill storage block identifier corresponding to the bill identifier is returned to the verification node. The verification node obtains the corresponding bill storage block from the blockchain according to the received bill storage block identifier, and if the bill storage block is successfully decrypted based on the node public key, the bill to be verified corresponding to the bill identifier is obtained from the decrypted bill storage block, and data verification is performed according to the bill to be verified. Further, the verification node receives the verification confirmation information sent by the target user, and generates a data verification record according to the verification confirmation information. Then, the data cancellation record and the cancellation confirmation information are sent to the consensus node in the blockchain system, and the verification results sent by each consensus node in the blockchain system are received. Finally, the consensus result of the data cancellation record is determined according to each verification result. When it is determined that a consensus is reached on the data cancellation record, the data cancellation record storage block including the data cancellation record is added to the blockchain. The embodiment of the present application can improve the reimbursement efficiency and the authenticity of the bill, reduce the possibility of repeated reimbursement of bills, and has high applicability.

[0074] See also Figure 4 , Figure 41 is a schematic diagram of a block chain-based data processing device provided in an embodiment of the present application. The block chain-based data processing device provided in an embodiment of the present application includes:

[0075] A cancellation request acquisition module 41 is used to acquire a data cancellation request sent by a target user, wherein the data cancellation request carries the first signature information of the target user on the data cancellation request, and the data cancellation request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the bill identifier;

[0076] The cancellation request processing module 42 is configured to send a ticket acquisition request including the authorization information to the ticket service node if the data cancellation request is determined to be a legitimate request based on the first signature information, so that when the ticket service node determines that the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request, it obtains the node public key of the ticket service node and the ticket storage block identifier corresponding to the ticket identifier and returns them to the cancellation node;

[0077] The data cancellation module 43 is used to obtain the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is decrypted successfully based on the node public key, the bill to be cancelled corresponding to the bill identifier is obtained from the decrypted bill storage block, and data cancellation is performed based on the bill to be cancelled.

[0078] Please also see Figure 5 , Figure 5 This is another structural diagram of a blockchain-based data processing device provided in an embodiment of the present application.

[0079] In some feasible implementations, the cancellation request processing module 42 includes an identity verification unit 421 and a bill acquisition unit 422. The identity verification unit 421 includes:

[0080] The public key acquisition subunit 4211 is used to acquire the target user public key corresponding to the target user from the public key storage block;

[0081] The signature decryption subunit 4212 is used to decrypt the first signature information based on the target user public key to obtain a first hash value;

[0082] The user identity determination unit 4213 is used to perform a hash operation on the data verification request to obtain a second hash value, and if the first hash value is the same as the second hash value, determine that the data verification request is a legal request.

[0083] In some feasible implementations, the identity verification unit 421 is further used to:

[0084] If the data verification request is determined to be a legitimate request based on the first signature information, and the blockchain does not include the data verification record corresponding to the ticket identifier, a ticket acquisition request including the authorization information is sent to the ticket service node.

[0085] In some feasible implementations, the data cancellation request also includes the data receiving account of the target user; the data cancellation module 43 includes a data decryption unit 431 and a data cancellation execution unit 432, and the data cancellation execution unit 432 is specifically used to:

[0086] Obtaining the amount of data to be written off included in the above-mentioned bills to be written off;

[0087] The above-mentioned amount of data to be written off is transferred from the data storage account to the above-mentioned data receiving account.

[0088] In some feasible implementation manners, the authorization information further includes an authorization time range; and the apparatus further includes:

[0089] The ticket service node obtains the first time of receiving the ticket acquisition request, and if it is determined that the first time is within the authorization time range, determines whether the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request.

[0090] In some feasible implementations, the above device further includes a verification record chain module 44, and the verification record chain module 44 includes:

[0091] The verification record generating unit 441 is used to receive the verification confirmation information sent by the target user and generate a data verification record according to the verification confirmation information;

[0092] The write-off record consensus unit 442 is used to send the data write-off record and the write-off confirmation information to the consensus nodes in the blockchain system, so that each consensus node determines the verification result of the data write-off record according to the write-off confirmation information;

[0093] The verification record processing unit 443 is used to receive the verification results sent by each consensus node in the above-mentioned blockchain system, determine the consensus result of the above-mentioned data verification record according to each verification result, and when it is determined that a consensus is reached on the above-mentioned data verification record, add the data verification record storage block including the above-mentioned data verification record to the above-mentioned blockchain.

[0094] In some feasible implementations, the above-mentioned cancellation record processing unit 443 includes a consensus result determination subunit 4431 and a cancellation record storage subunit 4432. The above-mentioned consensus result determination subunit 4431 is specifically used to:

[0095] If the proportion of verification passes in the verification results received from the above consensus nodes is not less than the preset passing proportion, it is determined that the above consensus nodes have reached a consensus on the above data verification record.

[0096] In a specific implementation, the above-mentioned blockchain-based data processing device can execute the above-mentioned Figures 2 to 3 The implementation methods provided in each step. For example, the above-mentioned cancellation request acquisition module 41 can be used to execute the implementation methods of obtaining data cancellation requests and the first signature information in the above-mentioned steps. For details, please refer to the implementation methods provided in the above-mentioned steps, which will not be repeated here. The above-mentioned cancellation request processing module 42 can be used to execute the implementation methods described in the above-mentioned steps such as determining the legitimacy of the data cancellation request based on the first signature information, sending a ticket acquisition request including authorization information to the ticket service node, etc. For details, please refer to the implementation methods provided in the above-mentioned steps, which will not be repeated here. The above-mentioned data cancellation module 43 can be used to execute the above-mentioned steps of receiving the node public key and the ticket storage block identifier, obtaining the corresponding ticket storage block from the blockchain according to the ticket storage block identifier, decrypting the ticket storage block based on the node public key, and obtaining the to-be-cancelled ticket from the decrypted ticket storage block for data cancellation. For details, please refer to the implementation methods provided in the above-mentioned steps, which will not be repeated here. The above-mentioned cancellation record chain module 44 can be used to execute the implementation methods of receiving the cancellation confirmation information, generating data cancellation records, reaching consensus on the data cancellation records, and chaining the data cancellation records in the above-mentioned steps. For details, please refer to the implementation methods provided in the above-mentioned steps, which will not be repeated here.

[0097] In an embodiment of the present application, a data processing device based on blockchain can obtain the first signature information of the target user on the data cancellation request carried by the data cancellation request by obtaining the data cancellation request sent by the target user. Among them, the data cancellation request includes the authorization information of the target user, and the authorization information includes the authorized party identifier and the bill identifier. If the data cancellation request is determined to be a legitimate request based on the first signature information, a bill acquisition request including the authorization information is sent to the bill service node, so that when the bill service node determines that the authorized party identifier is the same as the cancellation node identifier included in the bill acquisition request, it obtains the node public key of the bill service node and the bill storage block identifier corresponding to the bill identifier and returns it to the cancellation node. According to the received bill storage block identifier, the corresponding bill storage block is obtained from the blockchain. If the bill storage block is successfully decrypted based on the node public key, the bill to be cancelled corresponding to the bill identifier is obtained from the decrypted bill storage block, and data cancellation is performed according to the bill to be cancelled. Further, the cancellation confirmation information sent by the target user is received, and a data cancellation record is generated according to the cancellation confirmation information. Then, the data write-off record and the written-off confirmation information are sent to the consensus node in the blockchain system, and the verification results sent by each consensus node in the blockchain system are received. Finally, the consensus result of the data write-off record is determined according to each verification result. When it is determined that a consensus is reached on the data write-off record, the data write-off record storage block including the data write-off record is added to the blockchain. The embodiment of the present application can improve the reimbursement efficiency and the authenticity of the bill, reduce the possibility of repeated reimbursement of bills, and has high applicability.

[0098] See also Figure 6 , Figure 6 Schematic diagram of the structure of the terminal device provided in the embodiment of the present application. Figure 6 As shown, the terminal device in this embodiment may include: one or more processors 501, a memory 502 and a transceiver 503. Among them, the above-mentioned processor 501, memory 502 and transceiver 503 can be connected via a bus 504. Specifically, the transceiver 503 can be a communication module or a transceiver circuit. In the embodiment of the present application, the transceiver 503 is used to perform operations such as sending a ticket acquisition request, receiving a node public key and a ticket storage block identifier involved in the above-mentioned embodiment. The memory 502 is used to store a computer program, which includes program instructions, and the processor 501 is used to execute the program instructions stored in the memory 502.

[0099] It should be understood that in some feasible implementations, the processor 501 may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The memory 502 may include a read-only memory and a random access memory, and provide instructions and data to the processor 501. A portion of the memory 502 may also include a non-volatile random access memory. For example, the memory 502 may also store information about the device type.

[0100] In a specific implementation, the above terminal device can execute the above-mentioned functions through its built-in functional modules. Figure 2 to Figure 3 For the implementation methods provided in each step, please refer to the implementation methods provided in the above steps for details, which will not be repeated here.

[0101] The present application also provides a computer-readable storage medium storing a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, Figures 2 to 3 The data processing methods based on blockchain provided in each step can be specifically referred to the implementation methods provided in the above steps, which will not be repeated here.

[0102] The computer-readable storage medium may be a data processing device based on blockchain provided in any of the aforementioned embodiments or an internal storage unit of the terminal device, such as a hard disk or memory of an electronic device. The computer-readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the electronic device. Furthermore, the computer-readable storage medium may also include both an internal storage unit of the electronic device and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the electronic device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

[0103] The terms "first", "second", "third", "fourth", etc. in the claims, specification and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0104] Mentioning "embodiment" in this article means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. Displaying the phrase at various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments. The term "and / or" used in the specification of this application and the appended claims refers to any combination of one or more of the items listed in association and all possible combinations, and includes these combinations. It can be appreciated by those of ordinary skill in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0105] The method and related apparatus provided by the embodiment of the present application are described with reference to the method flow chart and / or structural diagram provided by the embodiment of the present application. Specifically, each process and / or box in the method flow chart and / or structural diagram, as well as the combination of the processes and / or boxes in the flow chart 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 generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the process. Figure 1 Schematic diagram of one or more processes and / or structures Figure 1These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1 Schematic diagram of one or more processes and / or structures Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the process in the process. Figure 1 A flow or multiple flows and / or structures illustrate the steps of the functions specified in one block or multiple blocks.

Claims

1. A data processing method based on blockchain, characterized in that: The method comprises: The verification node obtains a data verification request sent by a target user, wherein the data verification request carries first signature information of the target user on the data verification request, and the data verification request includes authorization information of the target user, wherein the authorization information includes an authorized party identifier and a ticket identifier; If the data cancellation request is determined to be a legitimate request based on the first signature information, a ticket acquisition request including the authorization information is sent to the ticket service node, so that when the ticket service node determines that the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request, the node public key of the ticket service node and the ticket storage block identifier corresponding to the ticket identifier are obtained and returned to the cancellation node; The cancellation node obtains the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is decrypted successfully based on the node public key, the bill to be cancelled corresponding to the bill identifier is obtained from the decrypted bill storage block, and data cancellation is performed based on the bill to be cancelled.

2. The method according to claim 1, characterized in that The method further comprises: The verification node obtains the target user public key corresponding to the target user from the public key storage block; The verification node decrypts the first signature information based on the target user public key to obtain a first hash value; The verification node performs a hash operation on the data verification request to obtain a second hash value, and if the first hash value is the same as the second hash value, determines that the data verification request is a legal request.

3. The method according to claim 1, characterized in that The method further comprises: If the data verification request is determined to be a legitimate request based on the first signature information, and the blockchain does not include a data verification record corresponding to the ticket identifier, a ticket acquisition request including the authorization information is sent to the ticket service node.

4. The method according to claim 1, characterized in that: The data cancellation request also includes the data receiving account of the target user; and performing data cancellation according to the to-be-cancelled bill includes: The cancellation node obtains the amount of data to be cancelled included in the to-be-cancelled bill; The write-off node transfers the amount of data to be written off from the data storage account to the data receiving account.

5. The method according to claim 1, characterized in that: The authorization information also includes an authorization time range; the method also includes: The ticket service node obtains the first time of receiving the ticket acquisition request, and if it is determined that the first time is within the authorization time range, determines whether the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request.

6. The method according to any one of claims 1 to 5, characterized in that: After performing data cancellation according to the to-be-cancelled bill, the method further includes: The cancellation node receives the cancellation confirmation information sent by the target user, and generates a data cancellation record according to the cancellation confirmation information; The verification node sends the data verification record and the verification confirmation information to the consensus node in the blockchain system, so that each consensus node determines the verification result of the data verification record according to the verification confirmation information; The verification node receives the verification results sent by each consensus node in the blockchain system, determines the consensus result of the data verification record based on each verification result, and when it is determined that a consensus is reached on the data verification record, adds a data verification record storage block including the data verification record to the blockchain.

7. The method according to claim 6, characterized in that Determining the consensus result of the data cancellation record according to each verification result includes: If the proportion of verification passes in the verification results received and returned by the consensus nodes is not less than a preset passing proportion, it is determined that the consensus nodes have reached a consensus on the data verification record.

8. A data processing device based on blockchain, characterized in that: The device comprises: A verification request acquisition module is used to acquire a data verification request sent by a target user, wherein the data verification request carries the first signature information of the target user on the data verification request, and the data verification request includes the authorization information of the target user, and the authorization information includes an authorized party identifier and a ticket identifier; A cancellation request processing module, configured to send a ticket acquisition request including the authorization information to a ticket service node if the data cancellation request is determined to be a legitimate request based on the first signature information, so that when the ticket service node determines that the authorized party identifier is the same as the cancellation node identifier included in the ticket acquisition request, the node public key of the ticket service node and the ticket storage block identifier corresponding to the ticket identifier are returned to the cancellation node; The data cancellation module is used to obtain the corresponding bill storage block from the blockchain according to the received bill storage block identifier. If the bill storage block is decrypted successfully based on the node public key, the bill to be cancelled corresponding to the bill identifier is obtained from the decrypted bill storage block, and data cancellation is performed based on the bill to be cancelled.

9. A terminal device, characterized in that: comprising a processor and a memory, wherein the processor and the memory are connected to each other; The memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Images