WO2020134574A1

WO2020134574A1 - Blockchain-based invoice authenticity verification method, apparatus, and electronic device

Info

Publication number: WO2020134574A1
Application number: PCT/CN2019/115357
Authority: WO
Inventors: 肖汉松; 阚文虎; 张萍; 刘勤; 林亮荣; 孙震; 张翼翔; 段金明
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2018-12-25
Filing date: 2019-11-04
Publication date: 2020-07-02
Also published as: CN110019326A; TWI714308B; TW202024954A

Abstract

Provided are a blockchain-based invoice authenticity verification method, an apparatus, and an electronic device, correspondence relationships between invoices and digital summaries of the invoices being stored in said blockchain. The method comprises: an anti-fraud verification request submitted by a client in regard to an invoice to be identified is received; in response to the anti-fraud verification request, a digital summary of the invoice to be identified is calculated, and whether a target invoice corresponding to the digital summary is stored in a blockchain is queried; and if such an invoice is stored in the blockchain, a verification result that the invoice to be identified is authentic is returned to the client.

Description

Invoice authenticity verification method, device and electronic equipment based on blockchain

Technical field

The embodiments of the present specification relate to the field of blockchain technology, and in particular to a blockchain-based invoice authenticity verification method, device, and electronic equipment.

Background technique

Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Because blockchain technology is decentralized, open and transparent, each computing device can participate in database records, and data synchronization can be quickly performed between computing devices, making blockchain technology widely implemented in many fields. application.

Summary of the invention

An embodiment of this specification provides a method, device and electronic device for authenticating invoices based on blockchain:

According to a first aspect of the embodiments of the present specification, a method for verifying the authenticity of an invoice based on a blockchain is provided. The blockchain stores the correspondence between the invoice and the digital summary of the invoice. The method includes:

Receive the anti-counterfeiting verification request for the invoice to be identified submitted by the client;

In response to the anti-counterfeiting verification request, calculate a digital digest of the invoice to be identified, and query whether the target invoice corresponding to the digital digest is stored in the blockchain;

If the target invoice corresponding to the digital digest is stored in the blockchain, a verification result that the to-be-identified invoice is true is returned to the client.

Optionally, the method further includes:

Receiving an invoice creation request submitted by a client; wherein the invoice creation request includes invoice creation information input by a user;

In response to the invoice creation request, call the invoice creation logic declared in the smart contract published on the blockchain to create an invoice based on the invoice creation information; and,

Calculate the digital summary of the invoice, and store the correspondence between the invoice and the digital summary of the invoice in the blockchain.

Optionally, in response to the anti-counterfeiting verification request, calculating a digital digest of the invoice to be identified, and querying whether a target invoice corresponding to the digital digest is stored in the blockchain includes:

In response to the anti-counterfeit verification request, call the invoice verification logic declared in the smart contract published on the blockchain, calculate the digital summary of the invoice to be identified, and query whether the digital data is stored in the blockchain The target invoice corresponding to the summary.

Optionally, the method further includes:

If the target data corresponding to the digital digest is stored in the blockchain, the target invoice is returned to the client.

Optionally, the digital summary of the invoice includes:

For the invoice content of the invoice; or a hash value calculated by hashing the unique information in the invoice content.

Optionally, the anti-counterfeiting verification request includes the invoice content of the to-be-identified invoice; or, the unique information in the invoice content;

The calculation of the digital summary of the invoice to be identified includes:

Obtaining the invoice content of the to-be-identified invoice in the anti-counterfeiting verification request; or, the unique information in the invoice content;

Regarding the acquired invoice content of the invoice to be identified; or, the uniqueness information in the invoice content is hashed to obtain a hash value.

Optionally, the blockchain is an alliance chain.

According to a second aspect of the embodiments of the present specification, there is provided an invoice authenticity verification device based on a blockchain in which the correspondence between invoices and digital summaries of invoices is stored, and the device includes:

The receiving unit receives the anti-counterfeiting verification request for the invoice to be identified submitted by the client;

The verification unit, in response to the anti-counterfeit verification request, calculates a digital digest of the invoice to be identified, and queries whether a target invoice corresponding to the digital digest is stored in the blockchain;

The return unit, if a target invoice corresponding to the digital digest is stored in the blockchain, returns a verification result that the to-be-identified invoice is true to the client.

Optionally, the device further includes:

A creation request receiving unit, receiving an invoice creation request submitted by a client; wherein the invoice creation request includes invoice creation information input by a user;

An invoice creation response unit, in response to the invoice creation request, invokes the invoice creation logic declared in the smart contract published on the blockchain, creates an invoice based on the invoice creation information; and, calculates a digital summary of the invoice, and The correspondence between the invoice and the digital summary of the invoice is stored in the blockchain.

Optionally, the verification unit specifically includes:

Optionally, the device further includes:

The query returning unit returns the target invoice to the client if the target data corresponding to the digital summary is stored in the blockchain.

Optionally, the digital summary of the invoice includes:

Optionally, the blockchain is an alliance chain.

According to a fifth aspect of the embodiments of the present specification, an electronic device is provided, including:

processor;

Memory for storing processor executable instructions;

Wherein, the processor is configured as any of the above-mentioned blockchain based invoice authenticity verification methods.

The embodiment of this specification provides a blockchain-based invoice authenticity verification scheme, which stores invoices and digital summaries of invoices in the blockchain in advance; due to the immutable characteristics of the data stored in the blockchain, and The unique feature of digital digest (that is, one digital digest corresponds to one original data); therefore, anti-counterfeiting verification can be performed based on the digital digest of the invoice stored in the blockchain. Specifically, the user only needs to upload the invoice to be identified. If the target invoice corresponding to the digital summary of the invoice to be identified stored in the blockchain can be queried, the invoice to be identified and the target invoice can be indicated to be identical 'S invoice is true, otherwise it is false.

BRIEF DESCRIPTION

FIG. 1 is a flowchart of a blockchain-based invoice authenticity verification method provided by an embodiment of this specification;

2 is a schematic diagram of an invoice on-chain provided by an embodiment of this specification;

3 is a hardware structure diagram of a blockchain-based invoice authenticity verification device provided by an embodiment of this specification;

4 is a schematic block diagram of a blockchain-based invoice authenticity verification device provided by an embodiment of the present specification.

detailed description

Exemplary embodiments will be described in detail here, examples of which are shown in the drawings. When referring to the drawings below, unless otherwise indicated, the same numerals in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.

The terminology used in this specification is for the purpose of describing particular embodiments only, and is not intended to limit this specification. The singular forms "a", "said" and "the" used in this specification and the appended claims are also intended to include most forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and encompasses 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 may also be referred to as second information, and similarly, the second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to a determination".

Invoice (Invoice) can refer to the business vouchers issued and received by all units or individuals in the purchase and sale of commodities, the provision or acceptance of services, and other business activities. Invoices are usually the original basis for accounting, and also an important basis for law enforcement inspections by auditing and tax authorities. For the company, the invoice is mainly the basis for the company to make an account, and it is also the voucher for paying taxes; for the employee, the invoice can mainly be used for reimbursement.

Since invoices involve taxes, reimbursement and other related interests, real-life situations in which false invoices are provided or received often occur. The general taxation bureau can provide the verification of the authenticity of invoices. However, due to the limitation of professional knowledge, ordinary users will not go to the taxation bureau for verification; this is easy to be used by some illegal businesses. These businesses will provide fake invoices to users for tax evasion. It can be seen that a simple and reliable invoice anti-counterfeiting verification scheme needs to be provided for users to check the authenticity of invoices at any time.

This specification provides a blockchain-based invoice authenticity verification method by storing invoices and digital summaries of invoices in the blockchain in advance; due to the immutable characteristics of the data stored in the blockchain and the digital summaries The only characteristic (that is, one digital digest corresponds to one original data); therefore, anti-counterfeiting verification can be performed based on the digital digest of the invoice stored in the blockchain. Specifically, the user only needs to upload the invoice to be identified. If the target invoice corresponding to the digital summary of the invoice to be identified stored in the blockchain can be queried, the invoice to be identified and the target invoice can be indicated to be identical 'S invoice is true, otherwise it is false.

Please refer to FIG. 1, which is a flowchart of a blockchain-based invoice authenticity verification method provided by an embodiment of the present specification. The blockchain stores the correspondence between invoices and digital summaries of invoices. The methods described include:

Step 110: Receive the anti-counterfeiting verification request for the invoice to be identified submitted by the client;

Step 120: In response to the anti-counterfeit verification request, calculate a digital digest of the invoice to be identified, and query whether the target invoice corresponding to the digital digest is stored in the blockchain;

Step 130: If the target invoice corresponding to the digital digest is stored in the blockchain, return a verification result that the to-be-identified invoice is true to the client.

The blockchain described in this specification may specifically include private chains, public chains, alliance chains, etc., and is not particularly limited in this specification.

For example, in a scenario, the above-mentioned blockchain may specifically be an alliance chain composed of headquarters organizations, branches, agencies, etc. as alliance members; the operator of the alliance chain may rely on the alliance chain to deploy the corresponding Business; and the headquarters, branches, and agencies as members of the alliance described above can be used as a business node of the above business. Each business node can publish the invoices and digital summaries generated or received by itself in the form of a transaction in the alliance chain, and after the transaction has been processed by the consensus nodes in the alliance chain, the distribution in the alliance chain The database is stored to complete the "on-chain" deposit of the above transaction information.

Among them, it should be noted that the transaction (Transaction) described in this specification refers to a piece of data that is created by 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 the transactions in the blockchain. A narrowly defined transaction refers to a value transfer issued by the user to the blockchain; for example, in the traditional Bitcoin blockchain network, the transaction can be a transfer initiated by the user in the blockchain. The generalized transaction refers to a piece of business data with business intent published by the user to the blockchain; for example, the operator can build an alliance chain based on actual business needs, relying on the alliance chain to deploy some other types not related to value transfer Online services (such as certificate storage services, anti-counterfeiting verification services, etc.), and in this type of alliance chain, a transaction can be a business message or business request issued by a user with business intent in the alliance chain.

The above client may include any type of upper-layer 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 the block. For example, operations such as storage, modification, and deletion in the blockchain all rely on smart contracts. The smart contract may be a computer protocol intended to be applied on the blockchain to propagate, verify or execute the contract in an information manner. By declaring business logic in the smart contract, the corresponding operation can be performed. Smart contracts allow trusted transactions without third parties. These transactions are traceable and irreversible. Smart contracts can provide better security than traditional contract methods and reduce other transaction costs associated with contracts. Generally, the smart contract can be deployed locally on the blockchain node. When the node needs to perform an action, it can call the corresponding smart contract and run the smart contract to execute the business logic declared in the smart contract, thereby obtaining the execution result.

The digital digest described in this specification may refer to a hash value (hash value) obtained by performing a hash (hash, also called hash) calculation on the original data.

Specifically, the digital summary of the invoice includes:

For the invoice content of the invoice; or, the unique information in the invoice content is hashed (hash value).

Wherein, the content of the invoice may contain unique information. For example, the invoice content can include the invoice number and invoice code; usually the invoice number and 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 invoice date and tax-free amount; correspondingly, the digital summary of the invoice can be recorded as hash (invoice number + invoice code + invoice date + tax-free amount).

Correspondingly, the anti-counterfeiting verification request includes the invoice content of the invoice to be identified; or, the unique information in the invoice content;

Calculating the digital summary of the invoice to be identified includes:

As mentioned above, this specification pre-chains the invoice. In an embodiment, the method further includes:

It is worth mentioning that the aforementioned calculation of the digital digest of the invoice to be identified and the calculation of the digital digest of the invoice when creating the invoice use the same hash algorithm.

The following is combined with the schematic diagram of the invoice on-chain shown in Figure 2:

In this embodiment, when a user needs to create an invoice in the blockchain, the user can initiate a transaction for creating an invoice through the client used by the client, that is, an invoice creation request is initiated through the client. Specifically, the user can input the invoice creation information of the target invoice to be created through the invoice creation page provided by the client; for example, the information such as the header and amount of the invoice. After the user completes the input of the invoice creation information, the client can generate a corresponding invoice creation request based on the invoice creation information input by the user, and send the invoice creation request to the node device in the blockchain.

After receiving the invoice creation request, the node device in the blockchain can respond to the invoice creation request, and call the invoice creation logic declared in the smart contract published on the blockchain, based on the invoice in the invoice creation request The creation information creates an invoice; and after the invoice creation is completed, the digital summary of the invoice can be further calculated, and the correspondence between the invoice and the digital summary of the invoice is stored in the blockchain.

In an embodiment, the node device that responds to the invoice creation request may first determine whether the invoice creation quota of the invoice issuer corresponding to the invoice creation request is sufficient.

For example, you can obtain the taxpayer identification number of the invoice issuer from the invoice creation information entered by the user in the invoice creation request, and determine the corresponding invoice issuer based on the taxpayer identification number. The invoice issuer is The invoice issuer corresponding to the invoice creation request. Subsequently, you can first determine whether the invoice creation quota of the invoice issuer is sufficient.

In one embodiment shown, the node device can call the quota check logic declared in the smart contract deployed on the blockchain to determine whether the invoice creation quota of the invoice issuer is sufficient.

The quota check logic may specifically be the program code (for example, some program methods or functions that can be called) that is declared in the smart contract and is related to the execution logic for checking the invoice creation quota of the invoice issuer.

Alternatively, the node device may call a third-party trusted service and send the invoice creation request to the third-party trusted service. Among them, the third-party trusted service may be a program code that is deployed on the third-party trusted service device and is related to the execution logic of checking the invoice creation quota of the invoice issuer. For example, the trusted service device of the third party 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 creation quota of the invoice issuer is sufficient, and return the determination result to the node device. The node device may determine whether the invoice creation quota of the invoice issuer is sufficient based on the determination result returned by the trusted service of the third party.

Specifically, the trusted service of the third party may return the determination result that the invoice creation quota of the invoice issuer is sufficient to the node device when it is determined that the invoice creation quota of the invoice issuer is sufficient. After receiving the determination result, the node device may determine that the invoice creation party's invoice creation quota is sufficient. Alternatively, the trusted service of the third party may return the determination result that the invoice creation quota of the invoice issuer is insufficient when it is determined that the invoice creation quota of the invoice issuer is insufficient. After receiving the determination result, the node device may determine that the invoice creation quota of the invoice issuer is insufficient.

If it is determined that the invoice creation quota of the invoice issuer is sufficient, the invoice creation logic declared in the smart contract deployed on the blockchain can be called to create the target invoice based on the invoice creation information entered by the user in the invoice creation request.

Wherein, the invoice creation logic may specifically be the program code declared in the smart contract and related to the execution logic of creating the invoice.

In another embodiment, the invoice may be provided by the organization that originally generated the invoice. For example, the national tax bureau may directly or indirectly upload the first invoice data of the invoice to the blockchain. 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 simultaneously synchronize the invoices on the chain and deposit certificates. The process of depositing certificates on the chain is the same as that in the foregoing embodiment, and details are not repeated here.

As shown in Figure 2, after invoice A, invoice B, and invoice C are chained, 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; invoice The mapping relationship between C hash and invoice C data.

The following describes the invoice anti-counterfeiting verification process in this manual:

After the user receives the invoice, if he needs to know the authenticity of the invoice, he can use the invoice as the invoice to be identified, and can submit the anti-counterfeiting verification request for the invoice to be identified to the blockchain through the client to call the deployment on the blockchain The smart contract used for invoice anti-counterfeiting verification verifies the authenticity of the invoice to be identified.

In one implementation, similar to the aforementioned invoice creation, the user can enter the invoice content of the invoice to be verified or the unique information in the invoice content on the client (hereinafter the invoice content or the unique information in the invoice content is simply referred to as Invoice data), and carry the entered invoice data in the anti-counterfeiting verification request sent by the client; send it to the node device in the blockchain to trigger the node device in the blockchain to call the deployed smart contract to verify the invoice to be identified Authenticity. In other words, the node device in the blockchain can directly receive the invoice data.

In another implementation, the user can take a picture of the invoice to be identified, collect the invoice image of the invoice to be identified, and perform image recognition on the collected invoice image on the client or a third-party identification system to identify the invoice data , And carry the invoice data obtained by image recognition in the anti-counterfeiting verification request sent by the client, and send it to the node device in the blockchain to trigger the node device in the blockchain to call the deployed smart contract to verify the invoice to be identified Authenticity.

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 by calling a third-party trusted service.

In one embodiment, invoice data in the invoice image is identified 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 identified locally at the node.

In an embodiment, 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 invoking a third-party trusted service (such as a third-party image recognition agency), which is based on the onboard image recognition algorithm , Perform image recognition on the invoice image to obtain the invoice data, and the node device can obtain the invoice data returned by the third-party image recognition organization. In this embodiment, the image recognition can be handed over to a third-party image recognition agency, thereby reducing the performance requirements of the nodes (not all nodes can have the computing resources required for image recognition).

In one embodiment, after obtaining the invoice data in the anti-counterfeiting verification request, the node device may call the invoice verification logic declared in the smart contract published on the blockchain, calculate the digital summary of the invoice to be identified, and query Whether the target invoice corresponding to the digital digest is stored in the blockchain.

If the target invoice corresponding to the digital digest is stored in the blockchain, it indicates that the invoice to be identified has been deposited in the blockchain; therefore, the verification result that the invoice to be identified is true can be returned to the client ; Further, if the target data corresponding to the digital summary is stored in the blockchain, return the target invoice to the client for the client to view.

If the target invoice corresponding to the digital abstract cannot be queried in the blockchain, it means that the invoice to be identified is not stored on the blockchain, so the verification result that the invoice to be identified is false can be returned to the customer end.

This specification proposes a blockchain-based invoice authenticity verification scheme by storing invoices and digital summaries of invoices in the blockchain in advance; due to the immutable characteristics of the data stored in the blockchain and the digital summaries The only characteristic (that is, one digital digest corresponds to one original data); therefore, anti-counterfeiting verification can be performed based on the digital digest of the invoice stored in the blockchain. Specifically, the user only needs to upload the invoice to be identified. If the target invoice corresponding to the digital summary of the invoice to be identified stored in the blockchain can be queried, the invoice to be identified and the target invoice can be indicated to be identical 'S invoice is true, otherwise it is false.

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

Please refer to FIG. 4, which is a block diagram of a blockchain-based invoice authenticity verification device provided by an embodiment of the present specification. The device corresponds to the embodiment shown in FIG. 1. The blockchain stores invoices and invoices. The corresponding relationship between the digital abstracts of the device includes:

The receiving unit 210 receives the anti-counterfeiting verification request for the to-be-identified invoice submitted by the client;

The verification unit 220, in response to the anti-counterfeiting verification request, calculates a digital digest of the invoice to be identified, and inquires whether a target invoice corresponding to the digital digest is stored in the blockchain;

The returning unit 230 returns the verification result that the invoice to be identified is true if the target invoice corresponding to the digital digest is stored in the blockchain.

Optionally, the device further includes:

Optionally, the verification unit 220 specifically includes:

Optionally, the device further includes:

Optionally, the digital summary of the invoice includes:

Optionally, the blockchain is an alliance chain.

The system, device, module or unit explained in the above embodiments may be specifically implemented by a computer chip or entity, or implemented by a product having a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.

For the implementation process of the functions and functions of each unit in the above device, please refer to the implementation process of the corresponding steps in the above 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 be referred to the description of the method embodiment. The device embodiments described above are only schematic, wherein 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, may be located in one place, or Distributed to multiple network elements. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solution in this specification. Those of ordinary skill in the art can understand and implement without paying creative labor.

The above FIG. 4 describes the internal functional modules and structural schematics of the blockchain-based invoice authenticity verification device. The actual execution subject may be an electronic device, including:

processor;

Memory for storing processor executable instructions;

Wherein, the processor is configured to:

In response to the anti-counterfeiting verification request, calculate a digital digest of the invoice to be identified, and query whether the target invoice corresponding to the digital digest is stored in the blockchain; wherein, invoices are stored in the blockchain Correspondence between the digital summary of the invoice;

Optional, also includes:

In response to the invoice creation request, call the invoice creation logic declared in the smart contract published on the blockchain, and create an invoice based on the invoice creation information; and,

Optional, also includes:

Optionally, the digital summary of the invoice includes:

Optionally, the blockchain is an alliance chain.

In the above embodiments 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 other general-purpose processors, digital signal processors (English: Digital Signal Processor) , Referred to as DSP), application specific integrated circuit (English: Application Specific Integrated Circuit, referred to as ASIC), etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc., and the aforementioned memory may be a read-only memory (English: read-only memory, abbreviation: ROM), a random access memory (English) : Random access memory (RAM for short), flash memory, hard disk or solid state drive. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly implemented and completed by a hardware processor, or may be implemented and completed by a combination of hardware and software modules in the processor.

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

After considering the description and practicing the invention disclosed herein, those skilled in the art will easily think of other embodiments of the description. This specification is intended to cover any variations, uses, or adaptations of this specification. These variations, uses, or adaptations follow the general principles of this specification and include common general knowledge or common technical means in the technical field not disclosed in this specification. . The description and examples are to be considered exemplary only, and the true scope and spirit of this description are pointed out by the following claims.

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 that various modifications and changes can be made without departing from the scope thereof. The scope of this description is limited only by the appended claims.

Claims

A blockchain-based method for verifying the authenticity of invoices. The blockchain stores the correspondence between invoices and digital summaries of invoices. The method includes:

Receive the anti-counterfeiting verification request for the invoice to be identified submitted by the client;

In response to the anti-counterfeiting verification request, calculate a digital digest of the invoice to be identified, and query whether the target invoice corresponding to the digital digest is stored in the blockchain;

If the target invoice corresponding to the digital digest is stored in the blockchain, a verification result that the to-be-identified invoice is true is returned to the client.
The method according to claim 1, further comprising:

Receiving an invoice creation request submitted by a client; wherein the invoice creation request includes invoice creation information input by a user;

In response to the invoice creation request, call the invoice creation logic declared in the smart contract published on the blockchain to create an invoice based on the invoice creation information; and,

Calculate the digital summary of the invoice, and store the correspondence between the invoice and the digital summary of the invoice in the blockchain.
According to the method of claim 1, in response to the anti-counterfeiting verification request, calculating a digital digest of the invoice to be identified and querying whether a target invoice corresponding to the digital digest is stored in the blockchain, include:

In response to the anti-counterfeit verification request, call the invoice verification logic declared in the smart contract published on the blockchain, calculate the digital summary of the invoice to be identified, and query whether the digital data is stored in the blockchain The target invoice corresponding to the summary.
The method according to claim 1, further comprising:

If the target data corresponding to the digital digest is stored in the blockchain, the target invoice is returned to the client.
According to the method of claim 2, the digital summary of the invoice includes:

The invoice content of the invoice; or a hash value obtained by hashing the unique information in the invoice content.
According to the method of claim 5, the anti-counterfeiting verification request includes the invoice content of the invoice to be identified; or, the unique information in the invoice content;

The calculation of the digital summary of the invoice to be identified includes:

Obtain the invoice content of the invoice to be identified in the anti-counterfeiting verification request; or, the unique information in the invoice content;

For the obtained invoice content of the invoice to be identified; or, the uniqueness information in the invoice content is hashed to obtain a hash value.
The method of claim 1, the blockchain is a consortium chain.
An invoice authenticity verification device based on a blockchain, where the correspondence between invoices and digital summaries of invoices is stored in the blockchain, the device includes:

The receiving unit receives the anti-counterfeiting verification request for the invoice to be identified submitted by the client;

The verification unit, in response to the anti-counterfeit verification request, calculates a digital digest of the invoice to be identified, and queries whether a target invoice corresponding to the digital digest is stored in the blockchain;

The return unit, if a target invoice corresponding to the digital digest is stored in the blockchain, returns a verification result that the to-be-identified invoice is true to the client.
The device according to claim 8, further comprising:

A creation request receiving unit, receiving an invoice creation request submitted by a client; wherein the invoice creation request includes invoice creation information input by a user;

An invoice creation response unit, in response to the invoice creation request, invokes the invoice creation logic declared in the smart contract published on the blockchain, creates an invoice based on the invoice creation information; and, calculates a digital summary of the invoice, and The correspondence between the invoice and the digital summary of the invoice is stored in the blockchain.
The apparatus according to claim 8, the verification unit specifically comprising:

In response to the anti-counterfeit verification request, call the invoice verification logic declared in the smart contract published on the blockchain, calculate the digital summary of the invoice to be identified, and query whether the digital data is stored in the blockchain The target invoice corresponding to the summary.
The device according to claim 8, further comprising:

The query returning unit returns the target invoice to the client if the target data corresponding to the digital summary is stored in the blockchain.
The apparatus of claim 9, the digital summary of the invoice includes:

The invoice content of the invoice; or a hash value obtained by hashing the unique information in the invoice content.
The device according to claim 12, wherein the anti-counterfeiting verification request includes invoice content of the invoice to be identified; or, unique information in the invoice content;

The calculation of the digital summary of the invoice to be identified includes:

Obtain the invoice content of the invoice to be identified in the anti-counterfeiting verification request; or, the unique information in the invoice content;

For the obtained invoice content of the invoice to be identified; or, the uniqueness information in the invoice content is hashed to obtain a hash value.
The device of claim 8, the blockchain is a consortium chain.
An electronic device, including:

processor;

Memory for storing processor executable instructions;

Wherein, the processor is configured as the method according to any one of claims 1-7 above.