Block chain-based electronic bill distribution method and apparatus, and electronic device

Abstract

The invention discloses an electronic bill distribution method and device based on a block chain, and electronic equipment, and relates to the technical field of electronic bill distribution or other related fields, and the method comprises the steps: creating a block chain account book and a bill service type, configuring an intelligent contract for the bill service type, and based on the bill service type and the block chain account book, distributing the intelligent contract for the bill service type; the method comprises the following steps: creating a bill distribution application, creating a participant entity based on participant information, configuring a block chain certificate and an asymmetric encryption key for the participant entity, when a sender does not deploy an interstellar file system node locally, the sender entity sending a service request and a service file to a gateway, and the gateway encrypting the service file, and the gateway transmits the service file to the interstellar file system and uploads the service file to the interstellar file system, when a synchronization node is deployed locally at a receiver, the gateway sends the service file to the synchronization node, and the synchronization node synchronizes the service file to the local of the receiver. According to the invention, the technical problems of low security and poor concurrency capability of electronic bill distribution in the prior art are solved.

Description

Technical Field

[0001] The present invention relates to the field of electronic bill distribution technology or other related fields, and in particular, to a blockchain-based electronic bill distribution method and device, and electronic equipment. Background Art

[0002] With the development of communication networks, a large number of bills have gradually been converted from paper bills to electronic bills. Electronic bills are stored and circulated in computer systems in the form of data files, realizing paperless bills. The storage, transmission and management of electronic bills are highly dependent on the Internet. Therefore, network unreliability, hacker attacks, virus intrusions and other issues will threaten the data security of electronic bills. In addition, the backtracking of electronic bills is difficult, especially in the later stage of rights protection and dispute resolution, which often requires a lot of time and financial costs to complete the backtracking of electronic bills.

[0003] In the related technologies, the use of blockchain networks to support the application of electronic bills can ensure the security and immutability of electronic bills, making the storage and transmission of electronic bills safer and difficult to be hacked or tampered with. The decentralized nature of the blockchain network makes the management of electronic bills independent of any single node and point-to-point transactions. By removing the intermediary agencies in traditional bill management, the management cost and operational complexity of electronic bills are reduced, and at the same time, the traceability of electronic bills and the transparency of transactions are enhanced. However, due to the complexity of the blockchain network, the cost of building and maintaining the blockchain network is high, and it is very difficult to achieve the distribution of electronic bills based on blockchain. In the existing blockchain-based electronic bill distribution strategies, there are problems of small concurrency and insufficient security. In particular, when the scale of business requests is large, the concurrency in the related technologies is not enough to support all business requests to receive timely responses. At the same time, due to the chain characteristics of the blockchain, the blockchain network is not suitable for storing large-size data files, and the storage capacity is small, which leads to the inability of the existing strategies to meet the storage and transmission of large-size data files.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a blockchain-based electronic bill distribution method and device, and an electronic device to at least solve the technical problems of low security and poor concurrency capability of electronic bill distribution in related technologies.

[0006] According to one aspect of an embodiment of the present invention, a blockchain-based electronic bill distribution method is provided, comprising: creating a blockchain account book and a bill business type, configuring different smart contracts for each bill business type, wherein the blockchain account book is used to store bill business data, and the bill business types include: distribution, query, approval, and tracking; creating a bill distribution application based on the bill business type and blockchain account book selected by an external terminal, wherein each bill distribution application corresponds to one or more blockchain account books; creating a participant entity based on the participant information input by the external terminal, configuring a blockchain certificate and a pair of asymmetric encryption keys for each participant entity, wherein the participant entities include: a sender entity and a receiver entity, and each pair of asymmetric encryption keys includes: a private key and a public key; in the case where the sender has not deployed an InterPlanetary File System node locally, the sender entity sends a bill business request and a bill business file to the gateway based on the corresponding blockchain certificate and private key, and the gateway encrypts the bill business file based on the public key corresponding to the receiver entity, and uploads the encrypted bill business file to the InterPlanetary File System; in the case where the receiver has deployed a synchronization node locally, the gateway sends the bill business file to the synchronization node, and the synchronization node synchronizes the bill business file to the receiver locally.

[0007] Optionally, the blockchain-based electronic invoice distribution method also includes: pre-building a management platform for electronic invoice distribution, and establishing network connections between the management platform and the gateway and the interplanetary file system respectively.

[0008] Optionally, the smart contract includes: a basic contract and an extended contract, wherein the basic contract corresponding to each bill business type is the same, and the basic contract is used to verify whether the interaction between the management platform and the gateway meets the preset contract terms; the extended contract corresponding to each bill business type is different, and the extended contract is used to verify whether the bill business operations corresponding to different bill business types meet the preset contract terms.

[0009] Optionally, when the sender deploys the InterPlanetary File System node locally, it includes: the sender entity obtains the public key corresponding to the receiver entity; the sender entity encrypts the bill business file based on the public key, and uploads the encrypted bill business file to the InterPlanetary File System.

[0010] Optionally, after uploading the bill business file to the Interplanetary File System, it also includes: the Interplanetary File System sends the storage address of the bill business file to the blockchain account book; and the blockchain account book stores the storage address of the bill business file in the Interplanetary File System.

[0011] Optionally, in the case where the synchronization node is deployed locally on the receiving side, the step in which the gateway sends the bill business file to the synchronization node includes: in the case where the gateway monitors the bill business event, querying whether the local synchronization node of the receiving side corresponding to the bill business event has established a monitoring mechanism; in the case where the local synchronization node of the receiving side corresponding to the bill business event has established a monitoring mechanism, the gateway pushes the bill business event to the local synchronization node of the receiving side corresponding to the bill business event; in the case where the local synchronization node of the receiving side corresponding to the bill business event receives the bill business event, the local synchronization node of the receiving side corresponding to the bill business event sends a read request to the gateway; in the case where the gateway receives the read request, the gateway obtains the storage address of the bill business file corresponding to the bill business event in the interstellar file system from the bill business event; based on the storage address, the gateway obtains the bill business file corresponding to the bill business event from the interstellar file system, and sends the bill business file to the local synchronization node of the receiving side corresponding to the bill business event.

[0012] Optionally, when the synchronization node is not deployed locally on the receiving party, the method includes: deploying a blockchain node and an Interstellar File System node locally on the receiving party; when the blockchain node monitors a bill business event, the receiving party locally obtains the storage address of the bill business file corresponding to the bill business event in the Interstellar File System from the bill business event; the receiving party locally obtains the bill business file corresponding to the bill business event from the Interstellar File System based on the storage address, and the receiving party obtains the bill business file from the receiving party locally.

[0013] According to another aspect of an embodiment of the present invention, there is also provided a blockchain-based electronic bill distribution device, comprising: a first creation unit, used to create a blockchain account book and a bill business type, and configure different smart contracts for each bill business type, wherein the blockchain account book is used to store bill business data, and the bill business types include: distribution, query, approval, and tracking; a second creation unit, based on the bill business type and blockchain account book selected by an external terminal, creates a bill distribution application, wherein each bill distribution application corresponds to one or more blockchain account books; a third creation unit, based on the participant information input by the external terminal, creates a participant entity, and configures a blockchain certificate and A pair of asymmetric encryption keys, wherein the participating entities include: a sending entity and a receiving entity, and each pair of asymmetric encryption keys includes: a private key and a public key; a sending unit, used for, when the sender has not deployed an InterPlanetary File System node locally, the sending entity sends a bill business request and a bill business file to the gateway based on the corresponding blockchain certificate and private key, and the gateway encrypts the bill business file based on the public key corresponding to the receiving entity, and uploads the encrypted bill business file to the InterPlanetary File System; a receiving unit, used for, when the receiving entity has deployed a synchronization node locally, the gateway sends the bill business file to the synchronization node, and the synchronization node synchronizes the bill business file to the receiving party locally.

[0014] Optionally, the blockchain-based electronic invoice distribution device also includes: a construction unit, which is used to pre-build a management platform for electronic invoice distribution, and the management platform establishes network connections with the gateway and the interstellar file system respectively.

[0015] Optionally, the smart contract includes: a basic contract and an extended contract, wherein the basic contract corresponding to each bill business type is the same, and the basic contract is used to verify whether the interaction between the management platform and the gateway meets the preset contract terms; the extended contract corresponding to each bill business type is different, and the extended contract is used to verify whether the bill business operations corresponding to different bill business types meet the preset contract terms.

[0016] Optionally, the sending unit includes: a first acquisition module, used by the sending entity to obtain the public key corresponding to the receiving entity when the sender locally deploys the Interstellar File System node; an encryption module, used by the sending entity to encrypt the bill business file based on the public key, and upload the encrypted bill business file to the Interstellar File System.

[0017] Optionally, the sending unit also includes: a first sending module, used for the interplanetary file system to send the storage address of the bill business file to the blockchain account book; and a storage module, used for the blockchain account book to store the storage address of the bill business file in the interplanetary file system.

[0018] Optionally, the receiving unit includes: a second sending module, which is used to query whether the local synchronization node of the recipient corresponding to the bill business event has established a monitoring mechanism when the gateway monitors the bill business event when the synchronization node is deployed locally on the recipient; a push module, which is used to push the bill business event to the local synchronization node of the recipient corresponding to the bill business event when the local synchronization node of the recipient corresponding to the bill business event has established a monitoring mechanism; a third sending module, which is used to send a read request to the gateway when the local synchronization node of the recipient corresponding to the bill business event receives the bill business event; a second acquisition module, which is used to obtain the storage address of the bill business file corresponding to the bill business event in the interstellar file system from the bill business event when the gateway receives the read request; a third acquisition module, which is used for the gateway to obtain the bill business file corresponding to the bill business event from the interstellar file system based on the storage address, and send the bill business file to the local synchronization node of the recipient corresponding to the bill business event.

[0019] Optionally, the receiving unit also includes: a deployment module, which is used to deploy a blockchain node and an interplanetary file system node locally on the receiving party when no synchronization node is deployed locally on the receiving party; a fourth acquisition module, which is used to obtain the storage address of the bill business file corresponding to the bill business event in the interplanetary file system from the bill business event locally on the receiving party when the blockchain node monitors the bill business event; and a fifth acquisition module, which is used to obtain the bill business file corresponding to the bill business event from the interplanetary file system locally on the receiving party based on the storage address, and the receiving party obtains the bill business file from the receiving party locally.

[0020] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned blockchain-based electronic invoice distribution methods.

[0021] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement any one of the above-mentioned blockchain-based electronic ticket distribution methods.

[0022] According to another aspect of an embodiment of the present invention, a computer program product is also provided, including a computer program, which, when executed by a processor, implements the steps of any one of the above-mentioned blockchain-based electronic invoice distribution methods.

[0023] In the present disclosure, by creating a blockchain ledger and a bill business type, different smart contracts are configured for each bill business type, and a bill distribution application is created based on the bill business type and blockchain ledger selected by an external terminal, wherein each bill distribution application corresponds to one or more blockchain ledgers, and then a participant entity is created based on the participant information input by the external terminal, and a blockchain certificate and a pair of asymmetric encryption keys are configured for each participant entity. In the case where the sender has not deployed an InterPlanetary File System node locally, the sender entity sends a bill business request and a bill business file to the gateway based on the corresponding blockchain certificate and private key. The gateway encrypts the bill business file based on the public key corresponding to the recipient entity, and uploads the encrypted bill business file to the InterPlanetary File System. In the case where a synchronization node is deployed locally on the recipient, the gateway sends the bill business file to the synchronization node, and the synchronization node synchronizes the bill business file to the recipient locally.

[0024] The present disclosure ensures the security and non-tamperability of bill business data by accessing the blockchain network, making the storage and transmission of bill business data safer and difficult to be attacked or tampered by hackers. By using the interplanetary file system as the storage unit of the bill business file, the size of the blockchain storage data is greatly reduced, the storage requirements of the blockchain are reduced, and the characteristics and performance of the blockchain are taken into account. At the same time, by accessing the gateway, it supports binding a bill business application to multiple blockchain ledgers, solving the problem of low concurrency of the blockchain network. By using asymmetric encryption keys to encrypt and protect the bill business files, the data security of the bill business files is guaranteed, thereby solving the technical problems of low security and poor concurrency of electronic bill distribution in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0026] Figure 1 is a schematic diagram of an optional blockchain-based electronic ticket distribution system according to an embodiment of the present invention;

[0027] Figure 2 is a flow chart of an optional blockchain-based electronic bill distribution method according to an embodiment of the present invention;

[0028] Figure 3 is a schematic diagram of an optional blockchain-based electronic bill distribution device according to an embodiment of the present invention;

[0029] Figure 4This is a hardware structure block diagram of an electronic device (or mobile device) that executes a blockchain-based electronic ticket distribution method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] It should be noted that the blockchain-based electronic invoice distribution method and device in the present disclosure can be used in the field of electronic invoice distribution technology. When electronic invoices are distributed based on blockchain, they can also be used in any field except the field of electronic invoice distribution technology. When electronic invoices are distributed based on blockchain, the present disclosure does not limit the application field of the blockchain-based electronic invoice distribution method and device.

[0033] The following embodiments of the present invention can be applied to various systems / applications / devices for the distribution of electronic bills based on blockchain. The present invention ensures the security and immutability of bill business data by accessing the blockchain network, making the storage and transmission of bill business data safer and difficult to be attacked or tampered with by hackers. By using the interplanetary file system as the storage unit for bill business files, the size of blockchain storage data is greatly reduced, the storage requirements of blockchain are reduced, and the characteristics and performance of blockchain are taken into account. At the same time, by accessing the gateway, it supports binding multiple blockchain ledgers to a bill business application, solving the problem of low concurrency of the blockchain network. By using asymmetric encryption keys, the bill business files are encrypted and protected, ensuring the data security of the bill business files.

[0034] The present invention is described in detail below in conjunction with various embodiments.

[0035] Embodiment 1

[0036] According to an embodiment of the present invention, an embodiment of a blockchain-based electronic ticket distribution method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that shown here.

[0037] The electronic bill distribution method based on blockchain in the embodiment of the present invention is executed on the electronic bill distribution system based on blockchain. Figure 1 is a schematic diagram of an optional blockchain-based electronic bill distribution system according to an embodiment of the present invention, such as Figure 1 As shown, the electronic invoice distribution system based on blockchain includes: management platform, access gateway module, synchronization node module, client SDK module (client software development kit module), blockchain ledger and IPFS (Interplanetary File System). Among them, the client SDK module provides ports for connecting with the synchronization node module and the access gateway module respectively, the access gateway module is connected with the management platform, blockchain ledger and IPFS respectively, and the management platform is connected with the blockchain ledger.

[0038] The management platform is a module that provides management services for the system, which includes the following functions: account book management function, bill business type management function, bill application management function, participant management function and access function.

[0039] Among them, the ledger management function simplifies the construction, management and operation of blockchain into page operations through BaaS (Blockchain as a Service), reducing the cost of using blockchain.

[0040] The bill business type management function is used to manage and maintain bill business types and bind bill business types to smart contracts. When users create bill business applications, this function will install smart contracts accordingly and support unified upgrades of smart contracts.

[0041] The bill application management function is provided to users to create and manage bill business applications. When creating a bill business application, the smart contract corresponding to the bill business type is automatically installed on the selected blockchain ledger. Users can create multiple bill business applications, and each bill business application can be bound to multiple ledgers. By binding multiple ledgers, the problem of insufficient concurrency of a single ledger can be solved when the number of participants is too large.

[0042] The participant management function is used to manage senders and receivers. Participants can be enterprises, organizations or individuals. Each participant will be assigned a pair of asymmetric encryption keys to encrypt and decrypt bill business files to ensure the privacy of files stored in the InterPlanetary File System. At the same time, blockchain certificates are assigned to participants for them to submit and query blockchain ledgers.

[0043] The access management function allocates authentication accounts for participants to access the management platform, and controls the access flow and authority scope of the management platform.

[0044] The access gateway module is used to connect the blockchain ledger and the interstellar file system, simplifying the access mode of the blockchain ledger to the HTTP access mode, simplifying the user's docking cost, and completing the encryption and reading and writing of bill business files. The access gateway module includes the following functions: reading and writing bill files, and transaction forwarding.

[0045] Among them, the function of reading and writing bill files is used to shield the participants from the docking details of the Interplanetary File System. For users who have not deployed the Interplanetary File System node locally, they can directly read and write bill business files through the gateway. In the embodiment of the present invention, the encryption method of the bill business file is an asymmetric encryption method. When the sender uploads the bill business file to the Interplanetary File System, it is necessary to use the public key of the recipient to encrypt the bill business file before uploading it. In the embodiment of the present invention, the sender does not need to obtain the public key of the recipient. The sender sends the bill business file to the gateway in plain text. The gateway obtains the public key of the recipient and encrypts the bill business file, and then uploads it to the Interplanetary File System.

[0046] The transaction forwarding function is used to implement the file routing function. After the sender sends the bill business file to the gateway, it does not need to pay attention to the destination node for forwarding the bill business file. The gateway will route and forward the bill business file to the correct destination node.

[0047] The synchronization node module is used to automatically synchronize the bill business files to the local for the recipient, and it includes the following functions: bill synchronization function and transaction forwarding function.

[0048] Among them, the bill synchronization function is used to synchronize bill business files. The synchronization node monitors blockchain events in real time by monitoring. When it monitors that the bill business file needs to be forwarded to us, the synchronization node will automatically synchronize the bill business file to the local storage. When the user reads the bill business file, it will first be obtained from the local storage. If the corresponding bill business file does not exist in the local storage, the bill business file can be obtained by accessing the gateway.

[0049] The transaction forwarding function is used to forward bill business requests.

[0050] The client SDK module provides users with a software development kit for module docking, which simplifies the docking cost for users. The client SDK module is located locally on the sender and receiver. The client SDK module encapsulates the blockchain SDK (blockchain application) to perform transaction tasks related to the blockchain, and also encapsulates the HTTP connection pool for docking gateways and synchronization nodes. It also encapsulates the gateway bill reading and writing service to implement the reading and writing operations of bill business files in the access gateway module.

[0051] It should be noted that the embodiments of the present invention support participants to deploy blockchain nodes and InterPlanetary File System nodes by themselves. After the blockchain nodes and InterPlanetary File System nodes are deployed, users can interact with files of the blockchain and InterPlanetary File System without going through synchronization nodes and gateways.

[0052] The embodiment of the present invention greatly simplifies and reduces the difficulty and cost of blockchain implementation by building a management platform, and can build a bill business at a low cost for users who want to use blockchain to distribute electronic bills. At the same time, the embodiment of the present invention simplifies the difficulty for senders and receivers of bill business to participate in the business through the matching access gateway and client SDK. Users do not need to master blockchain knowledge and can quickly access the bill business through the client SDK.

[0053] Figure 2 is a flowchart of an optional blockchain-based electronic bill distribution method according to an embodiment of the present invention, such as Figure 2 As shown, the method comprises the following steps:

[0054] Step S201, create a blockchain ledger and a bill business type, and configure different smart contracts for each bill business type, where the blockchain ledger is used to store bill business data, and the bill business types include: distribution, query, approval, and tracking.

[0055] Optionally, the blockchain-based electronic invoice distribution method also includes: pre-building a management platform for electronic invoice distribution, and establishing network connections between the management platform and the gateway and the interplanetary file system respectively.

[0056] In an embodiment of the present invention, it is necessary to pre-build a management platform for electronic invoice distribution, and the management platform establishes network connections with the gateway and the interstellar file system respectively, so as to realize the account book management function, the invoice business type management function, the invoice application management function, the participant management function and the access function.

[0057] The management platform builds a blockchain network and creates a blockchain ledger, which is used to store bill business data and execute bill business logic. At the same time, the management platform creates bill business types and provides users with a variety of optional bill businesses, including distribution, query, approval, and tracking. Different bill businesses have different business logics. In addition, different smart contracts need to be configured for each bill business type.

[0058] Optionally, the smart contract includes: a basic contract and an extended contract, wherein the basic contract corresponding to each bill business type is the same, and the basic contract is used to verify whether the interaction between the management platform and the gateway meets the preset contract terms; the extended contract corresponding to each bill business type is different, and the extended contract is used to verify whether the bill business operations corresponding to different bill business types meet the preset contract terms.

[0059] In the embodiment of the present invention, the smart contract includes: a basic contract and an extended contract. The basic contract is used to verify whether the interaction between the management platform and the gateway meets the preset contract terms. For different bill business types, the basic contracts they configure are the same. The extended contract is used to verify whether the bill business operations corresponding to different bill business types meet the preset contract terms. For different bill business types, the extended contracts they configure are different.

[0060] Step S202: Create a bill distribution application based on the bill business type and blockchain ledger selected by the external terminal, wherein each bill distribution application corresponds to one or more blockchain ledgers.

[0061] In an embodiment of the present invention, an external terminal or user selects a bill business type and a blockchain account book in the management platform, and the management platform creates a bill distribution application based on the selected bill business type and blockchain account book. It should be noted that when an external terminal or user selects a bill business type and a blockchain account book, one bill business type can correspond to multiple blockchain account books. By selecting multiple blockchain account books, the concurrency capability of the blockchain account book can be improved. When there are many participants or many bill business applications are created, if each bill business application is bound to only one blockchain account book, the concurrency capability is insufficient, which will cause the system response speed to slow down. Binding multiple blockchain account books to each bill business application can improve the concurrency capability, thereby speeding up the response speed of the system.

[0062] Step S203, based on the participant information input by the external terminal, create a participant entity, configure a blockchain certificate and a pair of asymmetric encryption keys for each participant entity, wherein the participant entity includes: a sender entity, a receiver entity, and each pair of asymmetric encryption keys includes: a private key and a public key.

[0063] In an embodiment of the present invention, an external terminal or user inputs the participant information in the management platform, and the management platform creates a participant entity based on the input participant information, and configures a blockchain certificate and a pair of asymmetric encryption keys for each participant entity. In an embodiment of the present invention, the participant can be an enterprise, an organization or an individual, and the participant includes a sender and a receiver. The management platform creates a participant entity based on the input participant information. The participant entity refers to each node that exchanges data and transfers files in the blockchain network. The participant entity can be an enterprise entity, an organizational entity or an individual entity, and the participant entity includes a sender entity and a receiver entity.

[0064] At the same time, the embodiment of the present invention configures a blockchain certificate and a pair of asymmetric encryption keys for each participating entity. The blockchain certificate can identify the identity of the participating entity. The asymmetric encryption key is a pair of encryption keys including a private key (private key) and a public key (public key), wherein the public key is used to encrypt files and the private key is used to decrypt files.

[0065] Step S204, when the sender has not deployed the InterPlanetary File System node locally, the sender entity sends a bill business request and a bill business file to the gateway based on the corresponding blockchain certificate and private key. The gateway encrypts the bill business file based on the public key corresponding to the recipient entity and uploads the encrypted bill business file to the InterPlanetary File System.

[0066] In an embodiment of the present invention, when the sender does not deploy the InterPlanetary File System node locally, the sender sends the bill service request and bill service file through the gateway. The sender entity sends the bill service request and bill service file to the gateway based on the configured blockchain certificate and private key, and then the gateway queries the blockchain certificate and public key configured by the receiving entity, uses the public key therein to encrypt the bill service file received from the sender entity, and uploads the encrypted bill service file to the InterPlanetary File System, which is responsible for storing the encrypted bill service file.

[0067] Optionally, when the sender deploys the InterPlanetary File System node locally, it includes: the sender entity obtains the public key corresponding to the receiver entity; the sender entity encrypts the bill business file based on the public key, and uploads the encrypted bill business file to the InterPlanetary File System.

[0068] It should be noted that when the sender has deployed the InterPlanetary File System node locally, the sender does not need to send the bill business request and bill business file through the gateway. The sender entity directly obtains the public key configured by the receiver entity, encrypts the bill business file, and uploads the encrypted bill business file to the InterPlanetary File System, which is then responsible for storing the encrypted bill business file.

[0069] Optionally, after uploading the bill business file to the Interplanetary File System, it also includes: the Interplanetary File System sends the storage address of the bill business file to the blockchain account book; and the blockchain account book stores the storage address of the bill business file in the Interplanetary File System.

[0070] In the embodiment of the present invention, the bill business file is uploaded to the Interplanetary File System for storage. At this time, the bill business file will have a corresponding storage address in the Interplanetary File System. The Interplanetary File System sends the storage address of the bill business file to the blockchain account book, and the blockchain account book stores the storage address of the bill business file in the Interplanetary File System. By storing the storage address of the bill business file on the blockchain account book, the persistent traceability and tamper-proofness of the bill business file can be ensured.

[0071] Step S205: When the receiver deploys a synchronization node locally, the gateway sends the bill service file to the synchronization node, and the synchronization node synchronizes the bill service file to the receiver locally.

[0072] In an embodiment of the present invention, when the receiver has deployed a synchronization node locally, the receiver locally obtains the bill business file sent by the sender through the synchronization node. After the bill business file is stored in the interplanetary file system, the gateway determines when to send the bill business file to the receiver. When it is determined that the bill business file needs to be sent to the receiver, the gateway sends the bill business file to the synchronization node corresponding to the receiver, and the synchronization node synchronizes the bill business file to the receiver locally. The receiver obtains the desired bill business file by querying the receiver's local storage.

[0073] Optionally, in the case where the synchronization node is deployed locally on the receiving side, the step in which the gateway sends the bill business file to the synchronization node includes: in the case where the gateway monitors the bill business event, querying whether the local synchronization node of the receiving side corresponding to the bill business event has established a monitoring mechanism; in the case where the local synchronization node of the receiving side corresponding to the bill business event has established a monitoring mechanism, the gateway pushes the bill business event to the local synchronization node of the receiving side corresponding to the bill business event; in the case where the local synchronization node of the receiving side corresponding to the bill business event receives the bill business event, the local synchronization node of the receiving side corresponding to the bill business event sends a read request to the gateway; in the case where the gateway receives the read request, the gateway obtains the storage address of the bill business file corresponding to the bill business event in the interstellar file system from the bill business event; based on the storage address, the gateway obtains the bill business file corresponding to the bill business event from the interstellar file system, and sends the bill business file to the local synchronization node of the receiving side corresponding to the bill business event.

[0074] In an embodiment of the present invention, when the receiver has deployed a synchronization node locally, the gateway determines when to send the bill business file to the receiver. The gateway will continue to monitor the blockchain network. When it monitors the existence of a bill business event, the gateway will query whether the receiver's local synchronization node corresponding to the bill business event has established a monitoring mechanism. If the receiver's local synchronization node has established a monitoring mechanism, the gateway will push the bill business event to the receiver's local synchronization node. After receiving the push of the bill business event, the receiver's local synchronization node sends a read request to the gateway. After receiving the read request, the gateway obtains the storage address of the bill business file corresponding to the bill business event in the interstellar file system from the bill business event, obtains the bill business file corresponding to the bill business event from the interstellar file system according to the storage address, and sends the bill business file to the receiver's local synchronization node. Finally, the receiver's local synchronization node synchronizes the bill business file to the receiver's local.

[0075] It should be noted that the synchronization node will regularly check the synchronization of local bill business files. When it is detected that there are historical bill business files that have not been synchronized to the local, the synchronization operation of the historical bill business files will be started.

[0076] Optionally, when the synchronization node is not deployed locally on the receiving party, the method includes: deploying a blockchain node and an Interstellar File System node locally on the receiving party; when the blockchain node monitors a bill business event, the receiving party locally obtains the storage address of the bill business file corresponding to the bill business event in the Interstellar File System from the bill business event; the receiving party locally obtains the bill business file corresponding to the bill business event from the Interstellar File System based on the storage address, and the receiving party obtains the bill business file from the receiving party locally.

[0077] In the embodiment of the present invention, when the receiver has not deployed a synchronization node locally but has deployed a blockchain node and an interplanetary file system node, the receiver no longer obtains the bill business file through the synchronization node and the gateway, but obtains the bill business file through the blockchain node and the interplanetary file system node. The blockchain node continuously monitors the blockchain network, and when it monitors the existence of a bill business event related to itself, the receiver obtains the storage address of the corresponding bill business file in the interplanetary file system from the bill business event, obtains the corresponding bill business file from the interplanetary file system according to the storage address, and finally the receiver obtains the desired bill business file by querying the receiver's local storage.

[0078] The steps provided by the above-mentioned blockchain-based electronic bill distribution method are to create blockchain ledgers and bill business types, configure different smart contracts for each bill business type, create a bill distribution application based on the bill business type and blockchain ledger selected by the external terminal, wherein each bill distribution application corresponds to one or more blockchain ledgers, and then create a participant entity based on the participant information input by the external terminal, configure a blockchain certificate and a pair of asymmetric encryption keys for each participant entity, and when the sender does not deploy the InterPlanetary File System node locally, the sender entity sends a bill business request and a bill business file to the gateway based on the corresponding blockchain certificate and private key, the gateway encrypts the bill business file based on the public key corresponding to the recipient entity, and uploads the encrypted bill business file to the InterPlanetary File System, and when the recipient deploys a synchronization node locally, the gateway sends the bill business file to the synchronization node, and the synchronization node synchronizes the bill business file to the recipient locally.

[0079] The embodiment of the present invention ensures the security and non-tamperability of the bill business data by accessing the blockchain network, making the storage and transmission of the bill business data safer and difficult to be attacked or tampered by hackers. By using the interstellar file system as the storage unit of the bill business file, the size of the blockchain storage data is greatly reduced, the storage demand of the blockchain is reduced, and the characteristics and performance of the blockchain are taken into account. At the same time, by accessing the gateway, it supports binding a bill business application to multiple blockchain ledgers, solving the problem of low concurrency of the blockchain network. By using asymmetric encryption keys, the bill business files are encrypted and protected, ensuring the data security of the bill business files. The gateway realizes the judgment of the ownership of the bill business files, avoiding the illegal acquisition of the bill business files by the outside world. Even if the outside world obtains the bill business files across the gateway, the bill business files cannot be decrypted, thereby ensuring the data security of the bill business files.

[0080] The following is a detailed description in conjunction with another embodiment.

[0081] Embodiment 2

[0082] A blockchain-based electronic invoice distribution device provided in this embodiment includes multiple implementation units, each implementation unit corresponding to each implementation step in the above-mentioned embodiment one.

[0083] Figure 3 is a schematic diagram of an optional blockchain-based electronic bill distribution device according to an embodiment of the present invention, such as Figure 3 As shown, the blockchain-based electronic invoice distribution device may include: a first creation unit 30, a second creation unit 31, a third creation unit 32, a sending unit 33, and a receiving unit 34.

[0084] The first creation unit 30 is used to create a blockchain ledger and a bill business type, and configure different smart contracts for each bill business type. The blockchain ledger is used to store bill business data, and the bill business types include: distribution, query, approval, and tracking;

[0085] The second creation unit 31 creates a bill distribution application based on the bill business type and blockchain ledger selected by the external terminal, wherein each bill distribution application corresponds to one or more blockchain ledgers;

[0086] The third creation unit 32 creates a participant entity based on the participant information input by the external terminal, and configures a blockchain certificate and a pair of asymmetric encryption keys for each participant entity, wherein the participant entity includes: a sender entity and a receiver entity, and each pair of asymmetric encryption keys includes: a private key and a public key;

[0087] The sending unit 33 is used for sending a bill service request and a bill service file to the gateway based on the corresponding blockchain certificate and private key when the sender does not deploy the InterPlanetary File System node locally. The gateway encrypts the bill service file based on the public key corresponding to the receiver entity and uploads the encrypted bill service file to the InterPlanetary File System.

[0088] The receiving unit 34 is used for, when a synchronization node is deployed locally at the receiving party, the gateway sends the bill service file to the synchronization node, and the synchronization node synchronizes the bill service file to the receiving party locally.

[0089] The above-mentioned blockchain-based electronic bill distribution device can create a blockchain account book and a bill business type through the first creation unit 30, configure different smart contracts for each bill business type, and create a bill distribution application based on the bill business type and blockchain account book selected by the external terminal through the second creation unit 31, wherein each bill distribution application corresponds to one or more blockchain account books, and then create a participant entity based on the participant information input by the external terminal through the third creation unit 32, and configure a blockchain certificate and a pair of asymmetric encryption keys for each participant entity. Through the sending unit 33, when the sender does not deploy the interstellar file system node locally, the sending entity sends the bill business request and the bill business file to the gateway based on the corresponding blockchain certificate and private key. The gateway encrypts the bill business file based on the public key corresponding to the receiving entity, and uploads the encrypted bill business file to the interstellar file system. Through the receiving unit 34, when the synchronization node is deployed locally on the receiving side, the gateway sends the bill business file to the synchronization node, and the synchronization node synchronizes the bill business file to the receiving side.

[0090] The embodiments of the present invention ensure the security and non-tamperability of bill business data by accessing the blockchain network, making the storage and transmission of bill business data safer and difficult to be attacked or tampered by hackers. By using the interplanetary file system as the storage unit of the bill business file, the size of the blockchain storage data is greatly reduced, the storage requirements of the blockchain are reduced, and the characteristics and performance of the blockchain are taken into account. At the same time, by accessing the gateway, it supports binding a bill business application to multiple blockchain ledgers, solving the problem of low concurrency of the blockchain network. By using asymmetric encryption keys to encrypt and protect the bill business files, the data security of the bill business files is guaranteed, thereby solving the technical problems of low security and poor concurrency of electronic bill distribution in related technologies.

[0091] Optionally, the blockchain-based electronic invoice distribution device also includes: a construction unit 35, which is used to pre-build a management platform for electronic invoice distribution, and the management platform establishes network connections with the gateway and the interplanetary file system respectively.

[0092] Optionally, the smart contract includes: a basic contract and an extended contract, wherein the basic contract corresponding to each bill business type is the same, and the basic contract is used to verify whether the interaction between the management platform and the gateway meets the preset contract terms; the extended contract corresponding to each bill business type is different, and the extended contract is used to verify whether the bill business operations corresponding to different bill business types meet the preset contract terms.

[0093] Optionally, the sending unit 33 includes: a first acquisition module, used for the sending entity to obtain the public key corresponding to the receiving entity when the sender locally deploys the Interstellar File System node; an encryption module, used for the sending entity to encrypt the bill business file based on the public key, and upload the encrypted bill business file to the Interstellar File System.

[0094] Optionally, the sending unit 33 also includes: a first sending module, used for the interplanetary file system to send the storage address of the bill business file to the blockchain account book; and a storage module, used for the blockchain account book to store the storage address of the bill business file in the interplanetary file system.

[0095] Optionally, the receiving unit 34 includes: a second sending module, which is used to query whether the local synchronization node of the recipient corresponding to the bill business event has established a monitoring mechanism when the gateway monitors the bill business event when the synchronization node is deployed locally on the recipient; a push module, which is used to push the bill business event to the local synchronization node of the recipient corresponding to the bill business event when the local synchronization node of the recipient corresponding to the bill business event has established a monitoring mechanism; a third sending module, which is used to send a read request to the gateway when the local synchronization node of the recipient corresponding to the bill business event receives the bill business event; a second acquisition module, which is used to obtain the storage address of the bill business file corresponding to the bill business event in the interstellar file system from the bill business event when the gateway receives the read request; a third acquisition module, which is used for the gateway to obtain the bill business file corresponding to the bill business event from the interstellar file system based on the storage address, and send the bill business file to the local synchronization node of the recipient corresponding to the bill business event.

[0096] Optionally, the receiving unit 34 also includes: a deployment module, which is used to deploy a blockchain node and an interplanetary file system node locally on the receiving party when no synchronization node is deployed locally on the receiving party; a fourth acquisition module, which is used to obtain the storage address of the bill business file corresponding to the bill business event in the interplanetary file system from the bill business event locally on the receiving party when the blockchain node monitors the bill business event; and a fifth acquisition module, which is used to obtain the bill business file corresponding to the bill business event from the interplanetary file system locally on the receiving party based on the storage address, and the receiving party obtains the bill business file from the receiving party locally.

[0097] The above-mentioned blockchain-based electronic invoice distribution device may also include a processor and a memory. The above-mentioned first creation unit 30, second creation unit 31, third creation unit 32, sending unit 33, receiving unit 34, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0098] The above processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and electronic bills can be distributed based on blockchain by adjusting kernel parameters.

[0099] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (fl ash RAM), and the memory includes at least one storage chip.

[0100] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the blockchain-based electronic invoice distribution methods in the above-mentioned embodiment 1.

[0101] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement the blockchain-based electronic ticket distribution method of any one of the above-mentioned embodiments one.

[0102] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the blockchain-based electronic ticket distribution method described in each embodiment of the present application.

[0103] The present application also provides a computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the blockchain-based electronic ticket distribution method described in each embodiment of the present application are implemented.

[0104] Figure 4 1 is a hardware structure block diagram of an electronic device (or mobile device) for executing a blockchain-based electronic bill distribution method according to an embodiment of the present invention. Figure 4 As shown, the electronic device may include one or more ( Figure 4 402a, 402b, ..., 402n are used to illustrate) a processor (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 404 for storing data. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 4 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 4 More or fewer components as shown, or with Figure 4 Different configurations are shown.

[0105] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0106] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0107] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0108] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0109] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0110] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0111] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for distributing electronic bills based on blockchain, characterized in that: include: Creating a blockchain ledger and a bill business type, and configuring a different smart contract for each of the bill business types, wherein the blockchain ledger is used to store bill business data, and the bill business types include: distribution, query, approval, and tracking; Creating a bill distribution application based on the bill business type and the blockchain ledger selected by the external terminal, wherein each bill distribution application corresponds to one or more blockchain ledgers; Based on the participant information input by the external terminal, a participant entity is created, and a blockchain certificate and a pair of asymmetric encryption keys are configured for each participant entity, wherein the participant entity includes: a sender entity and a receiver entity, and each pair of asymmetric encryption keys includes: a private key and a public key; In the case that the sender does not deploy the InterPlanetary File System node locally, the sender entity sends the bill service request and the bill service file to the gateway based on the corresponding blockchain certificate and the private key, and the gateway encrypts the bill service file based on the public key corresponding to the receiver entity, and uploads the encrypted bill service file to the InterPlanetary File System; In the case where a synchronization node is deployed locally at the receiving party, the gateway sends the bill service file to the synchronization node, and the synchronization node synchronizes the bill service file to the receiving party locally.

2. The electronic ticket distribution method according to claim 1, characterized in that: Also includes: A management platform for distributing electronic receipts is pre-built, and the management platform establishes network connections with the gateway and the interplanetary file system respectively.

3. The electronic ticket distribution method according to claim 1, characterized in that: The smart contract includes: basic contract and extended contract, among which: The basic contract corresponding to each type of the bill business is the same, and the basic contract is used to verify whether the interaction between the management platform and the gateway meets the preset contract terms; The extended contract corresponding to each of the bill business types is different, and the extended contract is used to verify whether the bill business operations corresponding to the different bill business types meet the preset contract terms.

4. The electronic ticket distribution method according to claim 1, characterized in that: In the case where the sender locally deploys the InterPlanetary File System node, it includes: The sending entity obtains the public key corresponding to the receiving entity; The sending entity encrypts the bill business file based on the public key, and uploads the encrypted bill business file to the interplanetary file system.

5. The electronic ticket distribution method according to claim 1, characterized in that: After uploading the bill business file to the interstellar file system, the process also includes: The interplanetary file system sends the storage address of the bill business file to the blockchain account book; The blockchain account book stores the storage address of the bill business file in the interplanetary file system.

6. The electronic ticket distribution method according to claim 1, characterized in that: In the case where the receiver locally deploys a synchronization node, the step of the gateway sending the bill service file to the synchronization node includes: When the gateway monitors a bill service event, query whether a local synchronization node of the receiver corresponding to the bill service event has established a monitoring mechanism; In the case where a listening mechanism is established at the local synchronization node of the recipient corresponding to the bill service event, the gateway pushes the bill service event to the local synchronization node of the recipient corresponding to the bill service event; When the local synchronization node of the receiver corresponding to the bill service event receives the bill service event, the local synchronization node of the receiver corresponding to the bill service event sends a read request to the gateway; When the gateway receives the read request, the gateway obtains the storage address of the bill service file corresponding to the bill service event in the interplanetary file system from the bill service event; The gateway obtains the bill business file corresponding to the bill business event from the interplanetary file system based on the storage address, and sends the bill business file to the recipient local synchronization node corresponding to the bill business event.

7. The electronic ticket distribution method according to claim 1, characterized in that: When the receiver does not have a synchronization node deployed locally, the following situations may occur: Deploy blockchain nodes and InterPlanetary File System nodes locally on the receiving end; When the blockchain node monitors a bill business event, the receiving party locally obtains the storage address of the bill business file corresponding to the bill business event in the interplanetary file system from the bill business event; The recipient locally obtains the bill business file corresponding to the bill business event from the interplanetary file system based on the storage address, and the recipient obtains the bill business file from the recipient locally.

8. An electronic bill distribution device based on blockchain, characterized in that: include: A first creation unit is used to create a blockchain ledger and a bill business type, and configure a different smart contract for each of the bill business types, wherein the blockchain ledger is used to store bill business data, and the bill business types include: distribution, query, approval, and tracking; A second creation unit is configured to create a bill distribution application based on the bill business type and the blockchain ledger selected by the external terminal, wherein each bill distribution application corresponds to one or more blockchain ledgers; A third creation unit, based on the participant information input by the external terminal, creates a participant entity, and configures a blockchain certificate and a pair of asymmetric encryption keys for each participant entity, wherein the participant entity includes: a sender entity and a receiver entity, and each pair of asymmetric encryption keys includes: a private key and a public key; A sending unit, configured to, when no interplanetary file system node is deployed locally on the sender, the sender entity sends a bill service request and a bill service file to the gateway based on the corresponding blockchain certificate and the private key, and the gateway encrypts the bill service file based on the public key corresponding to the receiver entity, and uploads the encrypted bill service file to the interplanetary file system; The receiving unit is used for, when a synchronization node is deployed locally at the receiving party, the gateway sends the bill service file to the synchronization node, and the synchronization node synchronizes the bill service file to the receiving party locally.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the blockchain-based electronic ticket distribution method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the blockchain-based electronic ticket distribution method as described in any one of claims 1 to 7.

Images