TWI734217B - Block chain-based invoice redemption method and device and electronic equipment - Google Patents

Abstract

The embodiment of this specification provides a method and device for redemption of invoices based on a blockchain, and electronic equipment. The blockchain stores the correspondence between invoices and digital summaries of the invoices. The method includes: receiving client submissions A redemption request for an invoice to be redeemed; in response to the redemption request, calculate a digital summary of the redemption invoice, and query whether the digital abstract is stored in the blockchain Target invoice; if it is found that the target invoice corresponding to the digital summary is stored in the blockchain, the redemption invoice issuance logic declared in the smart contract published on the blockchain is invoked, and the target invoice is issued for the target The redemption invoice of the invoice, and the corresponding relationship between the redemption invoice and the target invoice is stored in the blockchain.

Description

Block chain-based invoice redemption method and device and electronic equipment

The embodiments of the present specification relate to the field of blockchain technology, and in particular to a method and device for redemption of invoices based on a blockchain, and electronic equipment.

Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices participate in "bookkeeping" and jointly maintain a complete distributed database. Because the blockchain technology has the characteristics of decentralization, openness and transparency, each computing device can participate in database recording, and the rapid data synchronization between computing devices, the blockchain technology is widely used in many fields. To apply.

A blockchain-based invoice redemption method and device and electronic equipment provided by the embodiments of this specification: According to the first aspect of the embodiments of this specification, a blockchain-based invoice redemption method is provided. The corresponding relationship between the invoice and the digital summary of the invoice is stored, and the method includes: receiving a redemption request for an invoice to be redeemed submitted by a client; in response to the redemption request, calculating the redemption Number of invoices Summary, and query whether the target invoice corresponding to the digital summary is stored in the blockchain; if the target invoice corresponding to the digital summary is stored in the blockchain, call to publish on the blockchain The red-red invoice issuance logic stated in the smart contract on the above, issue red-red invoices for the target invoice, and store the corresponding relationship between the red-red invoice and the target invoice in the blockchain .

Optionally, the method further includes: receiving an invoice issuance request submitted by the client; wherein, the invoice issuance request includes the invoice issuance information input by the user; The invoice issuance logic declared in the smart contract on the blockchain is to issue an invoice based on the invoice issuance information; and, calculate the digital summary of the invoice, and compare the corresponding relationship between the invoice and the digital summary of the invoice Store in the blockchain.

Optionally, in response to the redemption request, calculating a digital summary of the invoice to be redeemed, and querying whether the target invoice corresponding to the digital summary is stored in the blockchain includes: responding In the redemption request, call the invoice verification logic declared in the smart contract published on the blockchain, calculate the digital summary of the redemption invoice, and query whether the blockchain is stored with the The target invoice corresponding to the digital summary.

Optionally, the digital summary of the invoice includes: invoice content for the invoice; or, in the invoice content The hash value obtained by hashing the unique information.

Optionally, the redemption request includes the invoice content of the invoice to be redeemed; or, unique information in the invoice content; and the calculation of the digital summary of the invoice to be redeemed includes: obtaining The invoice content of the invoice to be redeemed in the redemption request; or, the unique information in the invoice content; the invoice content for the obtained invoice to be redeemed; or, the invoice The unique information in the content is hashed to obtain the hash value.

Optionally, the blockchain is a consortium chain.

Optionally, the issuance of a redemption invoice for the target invoice specifically includes: issuance of a negative invoice with the same invoice value as the target invoice.

Optionally, the storing the corresponding relationship between the redemption invoice and the target invoice in the blockchain specifically includes any one of the following: establishing a relationship between the negative amount invoice and the target invoice And store the mapping relationship in the blockchain; establish the mapping relationship between the negative amount invoice and the digital summary of the target invoice, and store the mapping relationship in the Storing in the blockchain; establishing a mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice, and storing the mapping relationship in the blockchain.

According to the second aspect of the embodiments of the present specification, there is provided an invoice redemption device based on a blockchain in which invoices and invoice numbers are stored. The corresponding relationship between the bit summaries, the device includes: a receiving unit that receives a redemption request for an invoice to be redeemed submitted by a client; a query unit, in response to the redemption request, calculates the redemption The digital summary of the invoice, and query whether the target invoice corresponding to the digital summary is stored in the blockchain; the redemption unit, if it is queried that the target invoice corresponding to the digital summary is stored in the blockchain , Call the redemption invoice issuance logic declared in the smart contract published on the blockchain, issue redemption invoices for the target invoice, and set the corresponding relationship between the redemption invoice and the target invoice in all Store in the block chain.

Optionally, the device further includes: an issuance request receiving unit that receives an invoice issuance request submitted by the client; wherein the invoice issuance request includes invoice issuance information input by the user; an issuance request response unit that responds In the invoice issuance request, the invoice issuance logic declared in the smart contract published on the blockchain is invoked, and the invoice is issued based on the invoice issuance information; and, the digital summary of the invoice is calculated, and the The corresponding relationship between the invoice and the digital summary of the invoice is stored in the blockchain.

Optionally, the query unit includes: in response to the redemption request, invoking the invoice verification logic declared in the smart contract published on the blockchain, calculates the digital summary of the redemption invoice, and queries Whether the digital digest pair is stored in the blockchain The corresponding target invoice.

Optionally, the digital summary of the invoice includes: the invoice content of the invoice; or, the hash value obtained by hashing the unique information in the invoice content.

Optionally, the redemption request includes the invoice content of the invoice to be redeemed; or, unique information in the invoice content; in the query unit, a digital summary of the invoice to be redeemed is calculated , Including: obtaining the invoice content of the invoice to be redeemed in the redemption request; or, the unique information in the invoice content; the invoice content for the obtained invoice to be redeemed; or , The unique information in the invoice content is hashed to obtain the hash value.

Optionally, the blockchain is a consortium chain.

Optionally, in the redemption unit, issuing a redemption invoice for the target invoice specifically includes: issuing a negative amount invoice that is the same as the invoice amount of the target invoice.

Optionally, in the redemption unit, the corresponding relationship between the redemption invoice and the target invoice is stored in the blockchain, which specifically includes any one of the following: establishing the negative amount invoice and The mapping relationship between the target invoices, and the mapping relationship is stored in the blockchain; the mapping relationship between the negative amount invoice and the digital summary of the target invoice is established, and the The mapping relationship is stored in the blockchain; Establish a mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice, and store the mapping relationship in the blockchain.

According to a fifth aspect of the embodiments of the present specification, there is provided an electronic device, including: a processor; a memory for storing executable instructions of the processor; wherein the processor is configured as any one of the above-mentioned blockchain-based Invoice flushing method.

The embodiment of this specification provides a block chain-based invoice redemption scheme, which is certified by uploading the digital summaries of invoices and invoices to the chain; because the data stored in the block chain has the characteristics of non-tampering, and the digital summaries have The unique feature of (that is, a digital summary corresponds to one original data); therefore, when an error is found in an invoice, it can be determined based on the digital summary of the invoice stored in the blockchain that the wrong invoice (that is, the invoice to be redeemed) corresponds to The target invoice on the chain; in turn, a redemption invoice associated with the target invoice can be issued and the corresponding relationship between the redemption invoice and the target invoice can be stored in the blockchain; in this way, the redemption invoice can be offset The invoice amount of the wrong invoice.

110: Step

120: Step

130: steps

210: receiving unit

220: Query unit

230: Red unit

[Figure 1] is a flowchart of a blockchain-based invoice redemption method provided by an embodiment of this specification; [Figure 2] is a schematic diagram of an invoice redemption provided by an embodiment of this specification picture.

[Figure 3] is a hardware structure diagram of a blockchain-based invoice redemption device provided by an embodiment of this specification; [Figure 4] is a model of a blockchain-based invoice redemption device provided by an embodiment of this specification Group diagram.

The exemplary embodiments will be described in detail here, and examples thereof are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with this specification. On the contrary, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the scope of the appended application.

The terms used in this specification are only for the purpose of describing specific embodiments, and are not intended to limit the specification. The singular forms of "a", "said" and "the" used in this specification and the scope of the appended applications are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information can also be It is called the second information, and similarly, the second information can also be called the first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "in response to determination".

Invoices can refer to business vouchers issued and received by all units or individuals in purchasing and selling commodities, providing or receiving services, and engaging in other business activities. Invoices are usually the original basis for accounting and are also an important basis for law enforcement inspections by auditing agencies and taxation agencies. For the company, the invoice is mainly the basis for the company to make accounts, and it is also an expense certificate for tax payment; for the employee, the invoice is mainly used for reimbursement.

Invoice redemption is a method of re-issuing an invoice when it is found that the invoice is wrong or needs to be corrected for other reasons. When the invoice has been entered, if the invoice is incorrect, a new negative invoice with the same amount as the original invoice needs to be reissued to offset the entry.

Due to the non-tamperable characteristics of blockchain technology, the invoice can be stored on the chain to perform related invoice business based on the invoice stored in the blockchain. However, the invoice on the chain already belongs to the invoice that is entered. If the invoice on the chain is found to have errors, the invoice cannot be deleted to offset the entry; therefore, it is necessary to provide a solution for the redemption of the invoice in the blockchain.

This manual proposes a blockchain-based invoice redemption scheme, and provides a blockchain-based invoice redemption scheme. If errors are found in the invoice on the chain, you can generate a redemption invoice associated with the invoice Way to offset the invoice amount of the wrong invoice.

Please refer to Figure 1. Figure 1 is a block-based block diagram provided by an embodiment of this specification. The flow chart of the method for redemption of the invoice of the chain, the corresponding relationship between the invoice and the digital summary of the invoice is stored in the blockchain, and the method includes: Step 110: receiving the invoice submitted by the client for the redemption of the invoice Redemption request; Step 120: In response to the redemption request, calculate a digital summary of the invoice to be redeemed, and query whether the target invoice corresponding to the digital summary is stored in the blockchain; Step 130 : If it is queried that the target invoice corresponding to the digital summary is stored in the blockchain, call the red-red invoice issuance logic declared in the smart contract published on the blockchain to issue an invoice for the target invoice Flushing the red invoice, and storing the corresponding relationship between the red red invoice and the target invoice in the blockchain.

The blockchain described in this specification may specifically include a private chain, a public chain, and an alliance chain, etc., which are not particularly limited in this specification.

For example, in a scenario, the above-mentioned blockchain may specifically be a consortium chain composed of headquarters organizations, branches, agencies, etc. as alliance members; the operator of the consortium chain can rely on the consortium chain to deploy corresponding Business; and the headquarters, branches, and agencies that are members of the alliance described above can all be used as a business node of the above business. Each business node can publish the first digital summary of the invoice generated or received by itself in the consortium chain in the form of a transaction, and after the transaction is processed by the consensus node in the consortium chain, in the consortium chain Stored in the distributed database in, complete the "chain" deposit of the above transaction information.

Among them, it should be noted that the transaction described in this manual refers to a piece of data that is opened through the client of the blockchain and needs to be finally released to the distributed database of the blockchain.

There are usually narrow transactions and broad transactions in transactions in the blockchain. A transaction in a narrow sense refers to a transfer of value issued by a user to the blockchain; for example, in a traditional Bitcoin blockchain network, a transaction can be a transfer initiated by the user in the blockchain. In a broad sense, a transaction refers to a piece of business data with business intentions released by a user to the blockchain; for example, an operator can build a consortium chain based on actual business needs, and rely on the consortium chain to deploy some other types that have nothing to do with value transfer. Online business (such as deposit certificate business, authenticity verification business, invoice redemption business, etc.), and in this type of alliance chain, the transaction can be a business message or business request with business intent issued by the user in the alliance chain.

The above client may include any type of upper-level application that uses the underlying business data stored in the blockchain as data support to implement specific business functions.

In the blockchain technology, the nodes in the blockchain usually need to rely on the corresponding smart contract to operate on the block. For example, operations such as storage, modification, and deletion in the blockchain all need to rely on smart contracts. The smart contract may be a computer protocol that is designed to be deployed on the blockchain to disseminate, verify, or execute the contract in an information-based manner. The corresponding operations can be implemented by declaring business logic in the smart contract. Smart contracts allow credible transactions without a third party. These transactions are traceable and irreversible. Smart contracts can provide security that is superior to traditional contract methods. And reduce other transaction costs related to the contract. Generally, a smart contract can be deployed locally on a blockchain node. When the node needs to perform a certain action, the corresponding smart contract can be called, and the smart contract can be run to execute the business logic declared in the smart contract to obtain the execution result.

The digital abstract described in this specification may refer to a hash value obtained by hashing (also called a hash) calculation based on the original data. Specifically, the digital summary of the invoice includes: the invoice content of the invoice; or, the hash value obtained by hashing the unique information in the invoice content.

Wherein, the invoice content may include unique information. For example, the content of an invoice can include an invoice number and an invoice code; usually, both the invoice number and the invoice code are unique information; correspondingly, the digital summary of the invoice can be recorded as hash (invoice number + invoice code). Of course, the invoice content can also include non-unique information, such as the invoice date and tax excluding amount; correspondingly, the digital summary of the invoice can be recorded as a hash (invoice number + invoice code + invoice date + tax excluding amount).

Correspondingly, the redemption request includes the invoice content of the invoice to be redeemed; or, the unique information in the invoice content; and the calculation of the digital summary of the invoice to be redeemed includes: obtaining The invoice content of the invoice to be redeemed in the redemption request; or, the unique information in the invoice content; the invoice content for the obtained invoice to be redeemed; or, the invoice content The unique information in is hashed to obtain the hash value.

It’s worth mentioning that both the to-be-identified invoice and the invoice use the same hash Algorithm.

As mentioned above, this specification can pre-wind the invoice. In one embodiment, the method further includes: receiving an invoice issuance request submitted by the client; wherein, the invoice issuance request includes the invoice input by the user. Issuing information; in response to the invoice issuance request, call the invoice issuance logic declared in the smart contract published on the blockchain to issue an invoice based on the invoice issuance information; and, calculate the digits of the invoice Abstract, and store the correspondence between the invoice and the digital summary of the invoice in the blockchain.

The following is an explanation with reference to the schematic diagram of the invoice on the chain shown in Figure 2:

In this embodiment, when the user needs to open an invoice in the blockchain, he can initiate a transaction for issuing an invoice through the client terminal he uses, that is, initiate an invoice issuance request through the client terminal. Specifically, the user can enter the invoice issuance information of the target invoice to be issued through the invoice issuance page provided by the client terminal; for example, information such as the title and amount of the invoice. After the user completes the input of the invoice issuance information, the client can generate a corresponding invoice issuance request based on the invoice issuance information input by the user, and send the invoice issuance request to the node device in the blockchain .

After receiving the invoice issuance request, the node device in the blockchain can respond to the invoice issuance request. Call the invoice issuance logic declared in the smart contract published on the blockchain, and issue an invoice based on the invoice issuance information in the invoice issuance request; and after completing the invoice issuance, the invoice can be further calculated Digital summary, and combine the invoice and the The corresponding relationship of the digital summary of the invoice is stored in the blockchain.

In an embodiment, the node device responding to the invoice issuance request may also first determine whether the invoice issuance amount of the invoice issuance party corresponding to the invoice issuance request is sufficient.

For example, from the invoice issuance information entered by the user in the invoice issuance request, the taxpayer identification number of the invoice issuing party can be obtained, and the corresponding invoice issuing party can be determined based on the taxpayer identification number. It is the invoice issuing party corresponding to the invoice issuance request. Later, you can first determine whether the invoice issuer's invoice quota is sufficient.

In the illustrated embodiment, the node device may call the quota check logic declared in the smart contract deployed on the blockchain to determine whether the invoice issuance quota of the invoice issuer is sufficient.

Wherein, the quota check logic may specifically be the code (for example, some callable program methods or functions) related to the execution logic of checking the invoice issuance quota declared in the smart contract.

Alternatively, the node device may call the trusted service of the third party, and send the invoice issuance request to the trusted service of the third party. Among them, the trusted service of the third party may be a program code that is deployed on the trusted service device of the third party and is related to the execution logic of checking the invoice issuance limit of the invoice issuing party. For example, the third-party trusted service device may be a device in the intranet of the tax bureau, thereby improving data security.

The trusted service of the third party can determine whether the invoice issuance limit of the invoice issuance party is sufficient, and return the determination result to the node device. The node device can determine based on the determination result returned by the third-party trusted service Determine whether the invoice issuer's invoice quota is sufficient.

Specifically, the trusted service of the third party may return to the node device a determination result that the invoice issuance limit of the invoice issuance party is sufficient when it is determined that the invoice issuance limit of the invoice issuance party is sufficient. After receiving the determination result, the node device can determine that the invoice issuance amount of the invoice issuance party is sufficient. Alternatively, the trusted service of the third party may return to the node device a determination result that the invoice issuance limit of the invoice issuance party is insufficient when it is determined that the invoice issuance limit of the invoice issuance party is insufficient. After receiving the determination result, the node device can determine that the invoice issuance amount of the invoice issuance party is insufficient.

If it is determined that the invoice issuance limit of the invoice issuance party is sufficient, the invoice issuance logic declared in the smart contract deployed on the blockchain can be invoked, based on the invoice issuance information entered by the user in the invoice issuance request. Create a target invoice.

Among them, the invoice issuance logic may specifically be a code that is declared in the smart contract and is related to the execution logic of the invoice issuance.

In another embodiment, the invoice may be provided by the institution that originally generated the invoice. For example, the first invoice data of the invoice can be directly or indirectly uploaded to the blockchain by the State Administration of Taxation. Specifically, when an invoice is issued by an invoicing device, the invoice is also recorded on the system of the tax bureau, and the tax system of the tax bureau can synchronize the invoice on the chain for deposit. The process of uploading the evidence is the same as the previous embodiment, and will not be repeated here.

For example, after invoice A, invoice B, and invoice C are on the chain, the mapping relationship between invoice A hash and invoice A data can be recorded in the blockchain; The mapping relationship between invoice B hash and invoice B data; the mapping relationship between invoice C hash and invoice C data.

It is worth mentioning that, as shown in Figure 2, the blockchain can be divided into space for storing invoices and space for storing red invoices (that is, red invoices). The corresponding relationship between the invoice and the red note is established to realize the redemption of the invoice.

The following describes the process of redemption of invoices in this manual:

After the user finds that the invoice has an error, he needs to flush the error invoice stored in the blockchain to offset the error invoice. First, the user can use the wrong invoice as an invoice to be redeemed, and can submit a redemption request for the invoice to be redeemed to the blockchain through the client to call the invoice redemption deployed on the blockchain Smart contract for redemption for the invoice to be identified.

In one implementation method, similar to the previous invoice, the user can enter the invoice content or the unique information in the invoice content of the invoice to be redeemed on the client (the following will be the invoice content or the unique information in the invoice content (Referred to as invoice data), and carry the input invoice data in the redemption request sent by the client; send it to the node device in the block chain to trigger the node device in the block chain to call the deployed smart contract, aiming at the waiting The recognized invoice is flushed. Therefore, the node device in the blockchain can directly receive the invoice data.

In another implementation, the user can take a photo of the invoice to be redeemed, collect the invoice image of the invoice to be redeemed, and perform image recognition on the collected invoice image on the client or a third-party recognition system to identify Invoice data, and carry the invoice data obtained through image recognition In the redemption request sent by the client, it is sent to the node device in the blockchain to trigger the node device in the blockchain to call the deployed smart contract and redistribute the invoice to be recognized. Therefore, nodes in the blockchain can directly receive invoice data.

Among them, the image recognition of the collected image data of the invoice can be specifically completed by a smart contract deployed in the blockchain, or it can be completed by calling a third-party trusted service.

In one implementation, the invoice data in the invoice image is recognized according to an image recognition algorithm. In this embodiment, the smart contract itself has contract logic for image recognition, and the invoice data in the invoice image can be recognized locally at the node.

In another implementation, the method further includes: the node device can also send the invoice image in the anti-counterfeiting verification request to the third-party trusted service by calling a third-party trusted service (such as a third-party image recognition agency). The third-party trusted service performs image recognition on the invoice image based on the onboard image recognition algorithm to obtain the above-mentioned invoice data, and the node device can obtain the invoice data returned by the third-party image recognition agency. In this embodiment, image recognition can be completed by a third-party image recognition agency, thereby reducing the requirements for node performance (not all nodes may have the computing resources required for image recognition).

In one embodiment, after obtaining the invoice data in the redemption request, the node device can call the invoice verification logic declared in the smart contract published on the blockchain to calculate the digital summary of the redemption invoice. And query whether the target post corresponding to the digital summary is stored in the blockchain ticket.

In this embodiment, the calculation of the digital summary of the redemption invoice is calculated based on a smart contract. It should be noted that it may also be calculated locally based on a preset algorithm by the node device in response to the redemption request. (Does not rely on smart contracts); the specifics can be configured manually or automatically selected by the program according to business needs.

In this manual, after querying that the target invoice corresponding to the digital summary is stored in the blockchain, the node device needs to call the red invoice issuance logic declared in the smart contract published on the blockchain to issue Create a redemption invoice for the target invoice, and store the corresponding relationship between the redemption invoice and the target invoice in the blockchain.

In an embodiment, issuing a redemption invoice for the target invoice in step 130 specifically includes: issuing a negative invoice with the same invoice amount as the target invoice.

The storing the corresponding relationship between the redemption invoice and the target invoice in the blockchain specifically includes any one of the following: establishing a mapping relationship between the negative amount invoice and the target invoice , And store the mapping relationship in the blockchain; establish a mapping relationship between the negative amount invoice and the digital summary of the target invoice, and store the mapping relationship in the blockchain Storing; establishing a mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice, and storing the mapping relationship in the blockchain.

Invoices entered in the tax operation cannot be deleted, so for the incorrectly entered invoice, in practice, you can enter a negative invoice with the same amount as the incorrect invoice to offset the effect of the incorrect invoice. In the blockchain, first determine the target invoice for the red invoice, and then you can issue a negative invoice with the same invoice amount as the target invoice; at this time, the negative invoice is issued in the block The chain also needs to establish a mapping relationship between the negative amount invoice and the target invoice and/or the digital summary of the target invoice, so that the mapping relationship can be used to determine whether the erroneous invoice has been flushed.

As shown in Figure 2, after the blockchain node receives the redemption request for the redemption invoice a, it can call the preset smart contract to query whether the invoice a exists in the blockchain, that is, in this manual The target invoice; and after the existence of the invoice a is queried, a redemption invoice a for the invoice a is generated in the blockchain, and the mapping relationship between the redemption invoice a and the invoice a is established on the blockchain . The established mapping relationship may indicate that the invoice a has been flushed out. The red-red invoice a is the same negative amount as the invoice amount of the invoice a. For example, if the invoice amount of invoice a is 100 yuan, the invoice amount of red invoice a is -100 yuan.

This manual provides a blockchain-based invoice redemption solution, which is certified by uploading the digital summaries of invoices and invoices to the chain; because the data stored in the blockchain has the characteristics of non-tampering and the unique characteristics of the digital summaries (That is, a digital summary corresponds to one original data); therefore, when an error is found in an invoice, it can be determined based on the digital summary of the invoice stored in the blockchain that the wrong invoice (i.e. the invoice to be redeemed) corresponds to the on-chain Item A standard invoice; in turn, a red-red invoice associated with the target invoice can be issued and the corresponding relationship between the red-red invoice and the target invoice can be stored in the blockchain; in this way, the error of the invoice can be offset The invoice amount.

Corresponding to the foregoing embodiment of the blockchain-based invoice redemption method, this specification also provides an embodiment of the blockchain-based invoice redemption device. The device embodiments can be implemented through software, or through hardware or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer business program instructions in the non-volatile memory into the memory through the processor of the device where it is located. From the perspective of hardware, as shown in Figure 3, a hardware structure diagram of the device where the blockchain-based invoice redemption device is located in this manual, except for the processor, network interface, memory, and In addition to the non-volatile memory, the device where the device is located in the embodiment usually redistributes the actual function based on the blockchain-based invoice, and may also include other hardware, which will not be repeated here.

Please refer to FIG. 4, which is a block diagram of a block chain-based invoice redemption device provided by an embodiment of this specification. The device corresponds to the embodiment shown in FIG. 1, and the block chain stores invoices and invoices. The apparatus includes: a receiving unit 210, which receives a redemption request for a redemption invoice submitted by a client; and a query unit 220, which calculates the redemption request in response to the redemption request Redistribute the digital summary of the invoice, and query whether the target invoice corresponding to the digital summary is stored in the blockchain; the redemption unit 230, if the query finds that the blockchain stores the relevant The target invoice corresponding to the digital summary is called, the redemption invoice issuance logic declared in the smart contract published on the blockchain is called, the redemption invoice is issued for the target invoice, and the redemption invoice is combined with the redemption invoice. The corresponding relationship of the target invoice is stored in the blockchain.

Optionally, the device further includes: an issuance request receiving unit that receives an invoice issuance request submitted by the client; wherein the invoice issuance request includes invoice issuance information input by the user; an issuance request response unit that responds In the invoice issuance request, the invoice issuance logic declared in the smart contract published on the blockchain is invoked, and the invoice is issued based on the invoice issuance information; and, the digital summary of the invoice is calculated, and the The corresponding relationship between the invoice and the digital summary of the invoice is stored in the blockchain.

Optionally, the query unit 220 includes: in response to the redemption request, invoking the invoice verification logic declared in the smart contract published on the blockchain, calculates the digital summary of the redemption invoice, and Query whether the target invoice corresponding to the digital summary is stored in the blockchain.

Optionally, the digital summary of the invoice includes: the invoice content of the invoice; or, the hash value obtained by hashing the unique information in the invoice content.

Optionally, the redemption request includes the invoice content of the invoice to be redeemed; or, the unique information in the invoice content; in the query unit 220, the number of the invoice to be redeemed is calculated The summary includes: obtaining the invoice content of the invoice to be redeemed in the redemption request; or, the unique information in the invoice content; and the invoice content for the obtained invoice to be redeemed; Alternatively, the unique information in the invoice content is hashed to obtain a hash value.

Optionally, the blockchain is a consortium chain.

Optionally, in the redemption unit 230, issuing a redemption invoice for the target invoice specifically includes: issuing a negative amount invoice that is the same as the invoice amount of the target invoice.

Optionally, in the redemption unit 230, the corresponding relationship between the redemption invoice and the target invoice is stored in the blockchain, which specifically includes any one of the following: creating the negative amount invoice The mapping relationship between the target invoice and the target invoice, and the mapping relationship is stored in the blockchain; the mapping relationship between the negative amount invoice and the digital summary of the target invoice is established, and the The mapping relationship is stored in the block chain; the mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice is established, and the mapping relationship is stored in the block Store in the chain.

The systems, devices, modules, or units explained in the above embodiments may be implemented by computer chips or entities, or implemented by products with certain functions. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, and a smart phone. Phones, personal digital assistants, media players, navigation devices, email receiving and sending devices, game consoles, tablets, wearable devices, or a combination of any of these devices.

For the implementation process of the functions and roles of each unit in the above-mentioned device, please refer to the implementation process of the corresponding steps in the above-mentioned method for details, which will not be repeated here.

For the device embodiment, since it basically corresponds to the method embodiment, the relevant part can refer to the part of the description of the method embodiment. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement without creative work.

The above Figure 4 depicts the internal functional modules and structure of the blockchain-based invoice redemption device. The actual execution body can be an electronic device, including: a processor; a memory used to store executable instructions of the processor Body; wherein the processor is configured to: receive a redemption request submitted by the client for an invoice to be redeemed; in response to the redemption request, calculate a digital summary of the redemption invoice, and query Whether the target invoice corresponding to the digital summary is stored in the block chain; wherein, the block chain stores invoices and invoices Correspondence between the digital summaries; if the target invoice corresponding to the digital summaries is stored in the block chain, call the red-red invoice issuance logic declared in the smart contract published on the block chain to issue Create a redemption invoice for the target invoice, and store the corresponding relationship between the redemption invoice and the target invoice in the blockchain.

Optionally, it further includes: receiving an invoice issuance request submitted by the client; wherein, the invoice issuance request includes the invoice issuance information input by the user; in response to the invoice issuance request, calling and publishing on the blockchain The invoice issuance logic declared in the smart contract is to issue an invoice based on the invoice issuance information; and, calculate the digital summary of the invoice, and put the corresponding relationship between the invoice and the digital summary of the invoice in the Store in the blockchain.

Optionally, in response to the redemption request, calculating a digital summary of the invoice to be redeemed, and querying whether the target invoice corresponding to the digital summary is stored in the blockchain includes: responding In the redemption request, call the invoice verification logic declared in the smart contract published on the blockchain, calculate the digital summary of the redemption invoice, and query whether the blockchain is stored with the The target invoice corresponding to the digital summary.

Optionally, the digital summary of the invoice includes: the invoice content of the invoice; or, the hash value obtained by hashing the unique information in the invoice content.

Optionally, the redemption request includes the invoice content of the invoice to be redeemed; or, unique information in the invoice content; and the calculation of the digital summary of the invoice to be redeemed includes: obtaining The invoice content of the invoice to be redeemed in the redemption request; or, the unique information in the invoice content; the invoice content for the obtained invoice to be redeemed; or, the invoice The unique information in the content is hashed to obtain the hash value.

Optionally, the blockchain is a consortium chain.

Optionally, the issuance of a redemption invoice for the target invoice specifically includes: issuance of a negative invoice with the same invoice value as the target invoice.

Optionally, the storing the corresponding relationship between the redemption invoice and the target invoice in the blockchain specifically includes any one of the following: establishing a relationship between the negative amount invoice and the target invoice And store the mapping relationship in the blockchain; establish the mapping relationship between the negative amount invoice and the digital summary of the target invoice, and store the mapping relationship in the Storing in the blockchain; establishing a mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice, and storing the mapping relationship in the blockchain.

In the above embodiment of the electronic device, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, abbreviated as: CPU), or may be other general-purpose processors, digital signal processors (English: Central Processing Unit, CPU for short), Text: Digital Signal Processor, referred to as DSP), dedicated integrated circuit (English: Application Specific Integrated Circuit, referred to as ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., and the aforementioned memory can be read-only memory (English: read-only memory, abbreviation: ROM), random access memory Body (English: random access memory, abbreviated as: RAM), flash memory, hard disk or solid state drive. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

The various embodiments in this specification are described in a gradual manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the electronic device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

After considering the specification and practicing the invention disclosed herein, those skilled in the art will easily think of other embodiments of the specification. This specification is intended to cover any variations, uses, or adaptive changes of this specification. These variations, uses, or adaptive changes follow the general principles of this specification and include common knowledge or conventional technical means in the technical field that are not disclosed in this specification. . The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the specification are pointed out by the following patent application scope.

It should be understood that this specification is not limited to the precise structure that has been described above and shown in the drawings, and can be carried out without departing from its scope. Various modifications and changes. The scope of this specification is only limited by the scope of the attached patent application.

Claims (15)

A method for redemption of invoices based on a blockchain, wherein the corresponding relationship between the invoice and the digital summary of the invoice is stored in the blockchain, and the method includes: receiving redemption of the invoice submitted by the client for the redemption of the invoice Request, wherein the redemption request includes an image of the invoice collected by taking a photo of the invoice to be redacted; in response to the redemption request, the image recognition logic declared in the smart contract published on the blockchain is invoked, according to The image recognition algorithm identifies the invoice data of the invoice image; and the invoice verification logic calculates the digital summary corresponding to the invoice data, and queries whether the target invoice corresponding to the digital summary is stored in the blockchain ; If it is queried that the target invoice corresponding to the digital summary is stored in the blockchain, call the red-red invoice issuance logic declared in the smart contract published on the blockchain to issue an invoice for the target invoice Flushing the red invoice, and storing the corresponding relationship between the red red invoice and the target invoice in the blockchain. According to the method described in item 1 of the scope of patent application, the method further includes: receiving an invoice issuance request submitted by a client; wherein the invoice issuance request includes invoice issuance information input by the user; in response to the invoice Open a request and call the smart card published on the blockchain The invoice issuance logic declared in the smart contract is to issue an invoice based on the invoice issuance information; and, calculate the digital summary of the invoice, and place the correspondence between the invoice and the digital summary of the invoice in the area Store in the block chain. According to the method described in item 2 of the scope of patent application, the digital summary of the invoice includes: the invoice content of the invoice; or, the hash value obtained by hashing the unique information in the invoice content . The method according to item 3 of the scope of patent application, wherein the redemption request includes the invoice content of the invoice to be redeemed; or, the unique information in the invoice content; the calculation of the redemption The digital summary of the invoice, including: obtaining the invoice content of the invoice to be redeemed in the redemption request; or, the unique information in the invoice content; for the obtained invoice to be redeemed The content of the invoice; or, the unique information in the content of the invoice is hashed to obtain the hash value. According to the method described in item 1 of the scope of patent application, the blockchain is a consortium chain. According to the method described in item 1 of the scope of patent application, the issuance of a redemption invoice for the target invoice specifically includes: Issue a negative amount invoice that is the same as the invoice amount of the target invoice. The method according to item 6 of the scope of patent application, wherein the storing the correspondence between the redemption invoice and the target invoice in the blockchain specifically includes any one of the following: establishing the A mapping relationship between a negative amount invoice and the target invoice, and storing the mapping relationship in the blockchain; establishing a mapping relationship between the negative amount invoice and the digital summary of the target invoice, And store the mapping relationship in the blockchain; establish the mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice, and store the mapping relationship in the Store in the block chain. A block chain-based invoice redemption device, wherein the corresponding relationship between the invoice and the digital summary of the invoice is stored in the block chain, and the device includes: a receiving unit for receiving an invoice submitted by a client for redemption Redemption request, wherein the redemption request includes the invoice image collected by taking a photo of the invoice to be redeemed; the query unit, in response to the redemption request, calls the statement in the smart contract published on the blockchain The image recognition logic of, according to the image recognition algorithm, recognizes the invoice data of the invoice image; and the invoice verification logic, calculates the digital summary corresponding to the invoice data, and queries the block Whether the target invoice corresponding to the digital summary is stored in the chain; the redemption unit, if the target invoice corresponding to the digital summary is stored in the blockchain, call the smart contract published on the blockchain The redemption invoice issuance logic stated in, issues a redemption invoice for the target invoice, and stores the corresponding relationship between the redemption invoice and the target invoice in the blockchain. According to the device described in item 8 of the scope of patent application, the device further includes: an issuance request receiving unit that receives an invoice issuance request submitted by the client; wherein the invoice issuance request includes the invoice issuance information input by the user The issuance request response unit, in response to the invoice issuance request, calls the invoice issuance logic declared in the smart contract published on the blockchain, and issues an invoice based on the invoice issuance information; and, calculates the The digital summary of the invoice, and the corresponding relationship between the invoice and the digital summary of the invoice is stored in the blockchain. The device according to item 9 of the scope of patent application, wherein the digital summary of the invoice includes: the invoice content of the invoice; or, the hash value obtained by hashing the unique information in the invoice content. The device according to item 10 of the scope of patent application, wherein the flushing The request includes the invoice content of the invoice to be redeemed; or, the unique information in the invoice content; in the query unit, calculating the digital summary of the invoice to be redeemed includes: obtaining the redemption The invoice content of the invoice to be redeemed in the request; or, the unique information in the invoice content; the invoice content for the obtained invoice to be redeemed; or, the only one in the invoice content Sex information is hashed to get the hash value. The device according to item 8 of the scope of patent application, wherein the blockchain is a consortium chain. According to the device described in item 8 of the scope of patent application, in the redemption unit, issuing redemption invoices for the target invoice specifically includes: issuing a negative amount invoice with the same invoice amount as the target invoice . The device according to item 13 of the scope of patent application, wherein in the redemption unit, the corresponding relationship between the redemption invoice and the target invoice is stored in the blockchain, which specifically includes any of the following One: Establish a mapping relationship between the negative amount invoice and the target invoice, and store the mapping relationship in the blockchain; establish a digital summary of the negative amount invoice and the target invoice And store the mapping relationship in the blockchain; A mapping relationship between the negative amount invoice, the target invoice, and the digital summary of the target invoice is established, and the mapping relationship is stored in the blockchain. An electronic device comprising: a processor; a memory for storing executable instructions of the processor; wherein the processor is configured as the method described in any one of items 1-7 in the scope of the aforementioned patent application.

Images