A method for issuing invoices and a blockchain node device

Abstract

This application discloses a method for issuing invoices and a blockchain node device. The method includes: a first blockchain node device receiving an invoice issuance request from a second blockchain node device, wherein the invoice issuance request includes the digital certificate of the second blockchain node device; the first blockchain node device comparing the digital certificate included in the invoice issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device; if they match, the first blockchain node device responds to the invoice issuance request by generating an invoice and sending the invoice to the second blockchain node device. Correspondingly, the second blockchain node device signs the invoice and publishes the resulting digital signature, the invoice, and the digital certificate to the blockchain network. Using this application embodiment can establish a connection between the invoice and the issuing party, reducing the possibility of fraudulent invoice issuance.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for issuing invoices and a blockchain node device. Background Technology

[0002] With the widespread use of the internet, internet security issues have become increasingly prominent. These include information leaks and the spread of misinformation.

[0003] Currently, the practice of obtaining others' identity information for the purpose of issuing fraudulent invoices is rampant. For example, the invoice issuer may steal another person's identity information online, use this false identity to issue invoices, and then sell these invoices to other companies or individuals for personal gain. Because the invoice issuer uses false identity information, it is difficult to apprehend them based on the issued invoices, resulting in the loss of state funds. Therefore, how to prevent the fraudulent issuance of invoices has become a hot research topic. Summary of the Invention

[0004] This application provides a method for issuing invoices and a blockchain node device, which can verify the identity information of the invoice issuer and establish a relationship between the invoice and the invoice issuer, thereby avoiding the problem of fraudulent invoice issuance.

[0005] In a first aspect, embodiments of this application provide a method for issuing invoices, the method comprising: a first blockchain node device receiving an invoice issuance request sent by a second blockchain node device, wherein the invoice issuance request includes a digital certificate of the second blockchain node device; the first blockchain node device comparing the digital certificate included in the invoice issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device; if the digital certificate included in the invoice issuance request is the same as the digital certificate stored in the first blockchain node device, the first blockchain node device responds to the invoice issuance request by generating an invoice and sending the invoice to the second blockchain node device, so that the second blockchain node device signs the invoice according to its private key to obtain a digital signature of the invoice; and the second blockchain node device publishing the invoice, the digital signature, and the digital certificate of the second blockchain node device to the blockchain network.

[0006] Secondly, embodiments of this application provide a blockchain node device that has the function of issuing invoices as described in the first aspect. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned function.

[0007] In one implementation, the blockchain node device includes a receiving module, a comparison module, a generation module, and a sending module. The receiving module receives a bill issuance request from a second blockchain node device, wherein the bill issuance request includes the digital certificate of the second blockchain node device. The comparison module compares the digital certificate included in the bill issuance request with the digital certificate of the second blockchain node device stored in a first blockchain node device. The generation module generates a bill in response to the bill issuance request if the digital certificate included in the bill issuance request is the same as the digital certificate stored in the first blockchain node device. The sending module sends the bill to the second blockchain node device, enabling the second blockchain node device to sign the bill using its private key to obtain a digital signature, and to publish the bill, the digital signature, and the digital certificate of the second blockchain node device to the blockchain network.

[0008] Thirdly, embodiments of this application provide a blockchain node device, which includes a processor and a memory, coupled together. The memory stores a computer program. The processor invokes the computer program, causing the blockchain node device to execute the invoice issuance method as described in the first aspect.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium for storing a computer program used by a blockchain node device, which includes a program for executing the program described in the first aspect above.

[0010] In this embodiment, when the first blockchain node successfully verifies the digital certificate sent by the second blockchain node, it sends the generated invoice to the second blockchain node. Correspondingly, the second blockchain node signs the invoice using its private key and uploads it to the blockchain. This ensures the authenticity and reliability of the invoice issuer's identity information and establishes a link between the invoice and the issuer, facilitating tracing the issuer back to the invoice and reducing the possibility of fraudulent invoice issuance. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application will be described below.

[0012] Figure 1 This is a schematic diagram of the architecture of an invoice issuance system disclosed in an embodiment of this application;

[0013] Figure 2 This is a flowchart illustrating a method for issuing invoices disclosed in an embodiment of this application;

[0014] Figure 3This is a schematic diagram of a digital certificate disclosed in an embodiment of this application;

[0015] Figure 4 This is a schematic diagram of a type of bill disclosed in an embodiment of this application;

[0016] Figure 5 This is a flowchart illustrating another method for issuing invoices disclosed in an embodiment of this application;

[0017] Figure 6 This is a flowchart illustrating another method for issuing invoices disclosed in the embodiments of this application;

[0018] Figure 7 This is a schematic diagram of the structure of a blockchain node device disclosed in an embodiment of this application;

[0019] Figure 8 This is a schematic diagram of the structure of another blockchain node device disclosed in the embodiments of this application. Detailed Implementation

[0020] The embodiments of this application are described below with reference to the accompanying drawings.

[0021] With the rapid development of science and technology, human society has gradually entered the internet age. Internet technology accelerates the dissemination of information, facilitates modern communication, and shrinks the global reach. However, internet technology is also a double-edged sword; while bringing us convenience, it also brings hidden dangers, such as information leaks and the spread of misinformation.

[0022] Taking the issuance of false invoices as an example, the issuance of false invoices refers to the act of issuing invoices using false identity information and then reselling these invoices to other companies or individuals for personal gain. For instance, the issuer illegally obtains another person's identity information online and uses this information to register a shell company. After operating the shell company for a period of time, the issuer uses it to issue invoices and then resells these invoices to other companies or individuals for profit. It is clear that in the process of issuing invoices using false identity information, no connection is established between the invoice and the issuer. Therefore, when problems arise with the invoices later, it is impossible to trace the issuer's information back to the invoice, leading to the potential loss of state funds.

[0023] To address the aforementioned issues, this application proposes a method for issuing invoices and a blockchain node device, which are implemented based on blockchain technology.

[0024] Blockchain (BC) is a novel application model of computer technologies such as distributed data storage, consensus mechanisms, and cryptographic algorithms. Blockchain technology is characterized by decentralization, openness, independence, security, and anonymity. Generally, traditional transaction models are based on centralized thinking, meaning that the lack of trust between the transacting parties leads to the formation of a centralized third party who acts as an arbitrator, witnessing the activities of both parties during the transaction. In contrast, the decentralized nature of blockchain technology means that every node in the blockchain network stores data, achieving data redundancy through distributed storage. This enables all nodes to maintain the security of the database, making the entire transaction autonomous and simplified.

[0025] This application introduces blockchain technology into the scenario of issuing invoices. The method for issuing invoices proposed in this application includes: a first blockchain node device receiving an invoice issuance request sent by a second blockchain node device, wherein the invoice issuance request includes the digital certificate of the second blockchain node device; the first blockchain node device comparing the digital certificate included in the invoice issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device; if the digital certificate included in the invoice issuance request is the same as the digital certificate stored in the first blockchain node device, the first blockchain node device responds to the invoice issuance request, generates an invoice, and sends the invoice to the second blockchain node device, so that the second blockchain node device signs the invoice according to its private key to obtain a digital signature of the invoice; and the second blockchain node device publishes the invoice, the digital signature, and the digital certificate of the second blockchain node device to the blockchain network.

[0026] It should be noted that the first blockchain node device and the second blockchain node device belong to the same blockchain network. In the scenario of fraudulent invoicing, the first blockchain node device can be the tax bureau, and the second blockchain node device can be the client. This application embodiment does not limit the first or second blockchain node device in other scenarios.

[0027] As can be seen, the first blockchain node verifies the digital certificate in the invoice issuance request, ensuring the authenticity and reliability of the invoice issuer's identity information. The second blockchain node receives the invoice sent by the first blockchain node and signs and uploads it to the blockchain using its private key. This establishes a connection between the invoice and the invoice issuer, making the subsequent invoice traceability process more reliable and reducing the possibility of fraudulent invoice issuance.

[0028] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a bill issuance system disclosed in an embodiment of this application. Figure 1As shown, the invoice issuance system includes: a first blockchain node device and at least one second blockchain node device. The first blockchain node device and each of the second blockchain node devices form a blockchain network, and all blockchain node devices in the blockchain network share the information in the blockchain. The first blockchain node device can be a tax authority, and the second blockchain node devices can be clients.

[0029] The second blockchain node sends a bill issuance request to the first blockchain node, the request including the second blockchain node's digital certificate. The first blockchain node compares the digital certificate included in the bill issuance request with the digital certificate of the second blockchain node stored in the first blockchain node's database. If the digital certificate in the bill issuance request matches the digital certificate of the second blockchain node stored in the first blockchain node's database, the first blockchain node responds to the bill issuance request, generates a bill, and sends the bill to the second blockchain node. Accordingly, the second blockchain node signs the bill using its private key, obtaining a digital signature. The second blockchain node also publishes the bill, digital signature, and digital certificate to the blockchain network.

[0030] based on Figure 1 Please refer to the schematic diagram of the invoice issuance system shown below. Figure 2 , Figure 2 This is a flowchart illustrating a method for issuing invoices according to an embodiment of this application. The method includes, but is not limited to, the following steps:

[0031] Step S201: The first blockchain node device receives the bill issuance request sent by the second blockchain node device.

[0032] The invoice issuance request includes the digital certificate of the second blockchain node device. It should be noted that, in addition to the digital certificate of the second blockchain node device, the invoice issuance request may also include information about the issuing party, such as the company name and address.

[0033] For example, if the first blockchain node is the tax bureau and the second blockchain node is company B, then when company B needs to issue an invoice, it needs to send an invoice issuance request to the tax bureau. The invoice issuance request should include company B's digital certificate, company B's name, company B's address, company B's bank account number, company B's bank, company B's telephone number, etc.

[0034] Step S202: The first blockchain node device compares the digital certificate in the bill issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device.

[0035] A digital certificate is a relatively authoritative and impartial certificate issued by a Certificate Authority (CA). It serves as a digital authentication tool to identify a user's identity information during internet communication. Digital certificates encrypt or decrypt information and data exchanged between internet users on computer networks, ensuring the integrity and security of that information and data. Please see [link / reference]. Figure 3 , Figure 3 This is a schematic diagram of a digital certificate disclosed in an embodiment of this application, such as... Figure 3 As shown, digital certificates may include, but are not limited to: company name, company address, taxpayer identification number, account number, bank name, public key, and hash, etc.

[0036] In one implementation, the first blockchain node compares the digital certificate in the bill issuance request with the digital certificate of the second blockchain node stored on the first blockchain node. If the digital certificate in the bill issuance request is the same as the digital certificate of the second blockchain node stored on the first blockchain node, then the first blockchain node can determine that the identity of the party sending the bill issuance request through the second blockchain node is legitimate. In other words, the first blockchain node allows the party sending the bill issuance request to issue the bill.

[0037] The digital certificate in the invoice issuance request is obtained as follows: the first blockchain node device issues a digital certificate to the second blockchain node device and sends the digital certificate to the second blockchain node device. Therefore, the invoice issuance request sent by the invoice issuer to the first blockchain node device through the second blockchain node device includes the digital certificate.

[0038] It is understandable that the digital certificate stored by the first blockchain node device includes not only the digital certificate of the second blockchain node device. For example, if the first blockchain node device successfully verifies the digital certificate of the third blockchain node device in the blockchain network, the first blockchain node device will also store the digital certificate of the third blockchain node device.

[0039] As can be seen, the first blockchain node device verifies the digital certificate in the invoice issuance request. If the verification passes, the first blockchain node device responds to the invoice issuance request. This ensures that the identity of the invoice issuer is trustworthy, thereby preventing the fraudulent issuance of invoices.

[0040] Step S203: If the digital certificate in the bill issuance request is the same as the digital certificate of the second blockchain node device stored in the first blockchain node device, then the first blockchain node device responds to the bill issuance request and generates a bill.

[0041] Specifically, the first blockchain node device generates a bill based on the bill issuance request. The bill issuance request includes information about the issuing party, such as the company name and address. A bill is a security with a certain monetary value. Bills can be drafts, promissory notes, checks, invoices, etc. Please see below. Figure 4 , Figure 4 This is a schematic diagram of a ticket provided in an embodiment of this application, such as... Figure 4 As shown, a negotiable instrument may include, but is not limited to: the name of the payee, the taxpayer identification number of the payee, the address of the payee, the telephone number of the payee, the bank and account number of the payee, the name of the issuer, the taxpayer identification number of the issuer, the address of the issuer, the telephone number of the issuer, the bank and account number of the issuer, transaction information, and the total price including tax, etc.

[0042] Step S204: The first blockchain node device sends the ticket to the second blockchain node device.

[0043] Step S205: The second blockchain node device signs the ticket according to the private key to obtain the digital signature of the ticket.

[0044] Specifically, the second blockchain node device signs the bill using its private key, obtaining a digital signature for the bill. In other words, a connection is established between the bill and the issuer; thus, the issuer who issued the bill through the second blockchain node device can be identified through the bill.

[0045] Step S206: The second blockchain node device publishes the ticket, digital signature, and digital certificate to the blockchain network.

[0046] Specifically, the second blockchain node device publishes the ticket, digital signature, and digital certificate to the blockchain network. In other words, it puts the ticket, digital signature, and digital certificate on the chain. Correspondingly, the first blockchain node device in the blockchain network can obtain the ticket, digital signature, and digital certificate.

[0047] As can be seen, after the first blockchain node device successfully verifies the digital certificate in the invoice issuance request, it generates the invoice and sends it to the second blockchain node device. The second blockchain node device signs the invoice and uploads it to the blockchain. This establishes a link between the invoice and the issuing party, ensuring a more reliable traceability process and reducing the possibility of fraudulent invoice issuance.

[0048] Please see Figure 5 , Figure 5 This is a flowchart illustrating another method for issuing invoices provided in this application embodiment. The method may include:

[0049] Step S501: The first blockchain node device receives the identity information and biometric information sent by the second blockchain node device.

[0050] The identity information includes the invoice issuer's name, gender, phone number, etc. Biometric information includes the invoice issuer's fingerprint, facial, or iris scans, etc.

[0051] Step S502: The first blockchain node device compares the identity information and biometric information.

[0052] In one implementation, the method by which the first blockchain node device compares identity information and biometric information may include: the first blockchain node device searching for biometric information corresponding to the identity information; the first blockchain node device comparing the biometric information sent by the second blockchain node device with the searched biometric information. If the biometric information sent by the second blockchain node device is the same as the searched biometric information, the first blockchain node device can determine that the identity information used by the invoice issuer for invoicing is authentic and valid, and then the first blockchain node device can perform the operation of step S503.

[0053] Specifically, the first blockchain node device can obtain the biometric information corresponding to the identity information through other devices. For example, if the first blockchain node device is a tax bureau, then the tax bureau can obtain the ID card information corresponding to the identity information through the identity information storage unit that is connected to the tax bureau. The ID card information includes facial feature information (biometric information) corresponding to the identity information, etc.

[0054] Step S503: If the biometric information sent by the second blockchain node device is the same as the found biometric information, then the first blockchain node device obtains the enterprise information.

[0055] Step S504: The first blockchain node device receives the enterprise information sent by the second blockchain node device.

[0056] Enterprise information refers to the information of the enterprise represented by the invoice issuer. Enterprise information may include, but is not limited to: enterprise name, enterprise address, enterprise taxpayer identification number, enterprise bank and account, enterprise telephone number, etc.

[0057] Step S505: The first blockchain node device determines whether the enterprise corresponding to the enterprise information is a creditworthy enterprise based on the enterprise information.

[0058] In one implementation, step S505 may include: the first blockchain node device obtaining registration information corresponding to the enterprise information from the management device based on the enterprise information; and the first blockchain node device determining whether the enterprise corresponding to the enterprise information is a creditworthy enterprise based on the registration information. Optionally, the management device may also be a blockchain node device. The management device is used to store the enterprise's registration information.

[0059] For example, the first blockchain node device is the tax bureau, and the management device is the industry and commerce bureau. The industry and commerce bureau stores the registration information of at least one enterprise, and the tax bureau and the industry and commerce bureau can exchange information. After the tax bureau obtains the enterprise information, it can then obtain the corresponding registration information of the enterprise from the industry and commerce bureau.

[0060] In one implementation, the method by which the first blockchain node device determines whether the enterprise corresponding to the enterprise information is a creditworthy enterprise based on the registration information may include: the first blockchain node device obtaining the historical credit information of the enterprise corresponding to the enterprise information based on the registration information; and the first blockchain node device detecting whether the historical credit information indicates that the enterprise is a creditworthy enterprise. The historical credit information may include, but is not limited to, the enterprise's historical transaction data, risk management information, etc.

[0061] For example, if the first blockchain node device obtains historical credit information of the enterprise corresponding to the enterprise information and the enterprise has a low credit rating, then the first blockchain node device can determine that the enterprise corresponding to the enterprise information is a low-credit enterprise.

[0062] In another implementation, the method by which the first blockchain node device determines whether the enterprise corresponding to the enterprise information is a creditworthy enterprise based on the registration information may include: the first blockchain node device comparing the enterprise information with the registration information; if the enterprise information is the same as the registration information, then the first blockchain node device determines that the enterprise corresponding to the enterprise information is a creditworthy enterprise.

[0063] For example, the first blockchain node device can request the second blockchain node device to send enterprise information that includes all the information included in the registration information. Then the first blockchain node device will compare the content included in the enterprise information with the content included in the registration information. If the content included in the enterprise information is the same as the content included in the registration information, then the enterprise corresponding to the enterprise information is determined to be a credit enterprise.

[0064] As can be seen, the first blockchain node device verifies the company information provided by the invoice issuer, and executes step S506 upon successful verification. This ensures that the company information provided by the invoice issuer is authentic and reliable, thereby reducing the possibility of fraudulent invoice issuance.

[0065] Step S506: If the enterprise information corresponds to a credit enterprise, then the first blockchain node device generates a digital certificate for the second blockchain node device.

[0066] In one implementation, the first blockchain node device generates a digital certificate for the second blockchain node device based on registration information. Specifically, after receiving biometric information sent by the second blockchain node device, the first blockchain node device can generate a hash of the biometric information; the first blockchain node device then generates a digital certificate containing the hash based on the registration information. The first blockchain node device can generate the hash of the biometric information using a hash algorithm.

[0067] Step S507: The first blockchain node device sends the digital certificate to the second blockchain node device.

[0068] Step S508: The first blockchain node device receives the bill issuance request from the second blockchain node device.

[0069] Step S509: The first blockchain node device compares the digital certificate in the bill issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device.

[0070] Step S510: If they are the same, the first blockchain node device responds to the ticket issuance request and generates a ticket.

[0071] Step S511: The first blockchain node device sends the ticket to the second blockchain node device.

[0072] Step S512: The second blockchain node device signs the ticket according to the private key to obtain the digital signature of the ticket.

[0073] Step S513: The second blockchain node device publishes the ticket, digital signature, and digital certificate to the blockchain network.

[0074] It should be noted that the implementation process of steps 507 to 513 can refer to the implementation process of steps S201 to 206, and will not be repeated here.

[0075] As can be seen, the first blockchain node verifies the identity and enterprise information sent by the second blockchain node device. Only after both identity and enterprise information are successfully verified does the first blockchain node device issue a digital certificate to the second blockchain node device. This ensures the authenticity and reliability of the invoice issuer's identity information, thereby reducing the possibility of fraudulent invoice issuance.

[0076] Understandably, after the second blockchain node device publishes the bill, digital signature, and digital certificate to the blockchain network, the first blockchain node device can obtain the bill, digital signature, and digital certificate from the blockchain network, and the first blockchain node device can trace back to the issuer of the bill based on the bill, digital signature, and digital certificate.

[0077] For details on the implementation process, please refer to Figure 6 , Figure 6 A flowchart illustrating another method for issuing invoices provided in this application embodiment, the method may include:

[0078] Step S601: The first blockchain node device obtains the ticket, digital signature, and digital certificate.

[0079] Optionally, the first blockchain node device obtains the ticket, digital signature, and digital certificate from the blockchain network. Optionally, the first blockchain node device can also obtain the ticket, digital signature, and digital certificate from a device outside the blockchain network.

[0080] Step S602: The first blockchain node device compares the digital certificate obtained from the blockchain network with the digital certificate stored in the first blockchain node device.

[0081] The first blockchain node device stores at least one digital certificate. Therefore, the first blockchain node device compares the digital certificate of the second blockchain node device obtained from the blockchain network with the digital certificate of the second blockchain node device stored in the first blockchain node device.

[0082] Step S603: If the digital certificate obtained from the blockchain network is the same as the digital certificate stored in the first blockchain node device, then the first blockchain node verifies the digital signature.

[0083] In one implementation, the first blockchain node device verifies the digital signature of the second blockchain node device obtained from the blockchain network using the public key of the second blockchain node device. As mentioned above, the second blockchain node device signs the document using its private key to obtain a digital signature. Therefore, the first blockchain node device can verify the digital signature using the public key of the second blockchain node device. If the verification is successful, the first blockchain node device determines that the digital signature is trustworthy.

[0084] Step S604: If the signature verification is successful, the first blockchain node device obtains the hash from the digital certificate and determines that the identity information corresponding to the hash is the identity information associated with the ticket.

[0085] Since the hash is generated based on the issuer's biometric information, there is a correlation between the hash and the issuer's identity information. Therefore, the first blockchain node device can determine the issuer corresponding to the ticket by obtaining the hash from the digital certificate.

[0086] As can be seen, by establishing a relationship between the bill and the issuer, the first blockchain node device can trace back to the issuer of the bill based on the bill, thereby reducing the occurrence of fraudulent bill issuance.

[0087] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a blockchain node device provided in an embodiment of this application. The blockchain node device 70 is used to perform... Figure 2 , Figure 5 and Figure 6 The steps performed by the first blockchain node device in the corresponding method embodiment. The blockchain node device 70 may include a receiving module 701, a comparison module 702, a generation module 703, and a sending module 704. The receiving module 701 may include a lookup unit 7011 and a signature verification unit 7012. Each module in the blockchain node device 70 is specifically used for:

[0088] The receiving module 701 is used to receive a bill issuance request sent by the second blockchain node device, wherein the bill issuance request includes the digital certificate of the second blockchain node device, and the first blockchain node device and the second blockchain node device belong to the same blockchain network.

[0089] Comparison module 702 is used to compare the digital certificate included in the invoice issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device;

[0090] The generation module 703 is used to generate a bill in response to the bill issuance request if the digital certificate included in the bill issuance request is the same as the digital certificate stored in the first blockchain node device.

[0091] The sending module 704 is used to send the ticket to the second blockchain node device, so that the second blockchain node device signs the ticket according to the private key of the second blockchain node device to obtain the digital signature of the ticket, and the second blockchain node device publishes the ticket, the digital signature and the digital certificate of the second blockchain node device to the blockchain network.

[0092] In one implementation, before receiving the bill issuance request sent by the second blockchain node device, the receiving module 701 is further configured to: receive enterprise information sent by the second blockchain node device, and obtain the registration information of the enterprise corresponding to the enterprise information from the management device based on the enterprise information, wherein the management device is used to store the enterprise registration information;

[0093] Comparison module 702 is used to determine whether the enterprise corresponding to the enterprise information is a creditworthy enterprise;

[0094] If the enterprise information corresponds to a creditworthy enterprise, the generation module 703 generates a digital certificate based on the registration information, and the sending module 704 sends the digital certificate to the second blockchain node device.

[0095] In one implementation, when determining whether the enterprise information corresponds to a creditworthy enterprise, the comparison module 702 is specifically used to: determine the historical credit information of the enterprise information corresponding to the registration information based on the enterprise's historical credit information.

[0096] If the historical credit information only indicates that the enterprise is a creditworthy enterprise, then the generation module 703 will be executed to generate a digital certificate based on the registration information.

[0097] In one implementation, when determining whether the enterprise information corresponds to a creditworthy enterprise, the comparison module 702 is specifically used to: compare the enterprise information with the registration information.

[0098] If the company information is the same as the registration information, then the company corresponding to the company information is determined to be a creditworthy company.

[0099] In one implementation, before receiving the enterprise information sent by the second blockchain node device, the receiving module 701 is further configured to: receive the identity information and biometric information sent by the second blockchain node device;

[0100] The lookup unit 7011 searches for biometric information corresponding to the identity information;

[0101] If the comparison module 702 finds that the biometric information sent by the second blockchain node device is the same as the biometric information found, then the receiving module 701 will execute the step of receiving the enterprise information sent by the second blockchain node device.

[0102] In one implementation, when generating a digital certificate based on the registration information, the generation module 703 is specifically used to: generate a hash of biometric information;

[0103] The generation module 703 is also used to generate a digital certificate containing a hash based on the registration information.

[0104] In one implementation, after the sending module 704 sends the ticket to the second blockchain node device, the receiving module 701 is further configured to: obtain the ticket, digital signature, and digital certificate of the second blockchain node device from the blockchain network.

[0105] The signature verification unit 7012 verifies the digital signature obtained from the blockchain network based on the public key of the ticket and the second blockchain node device.

[0106] If the signature verification is successful, the receiving module 701 obtains the hash from the digital certificate of the second blockchain node device;

[0107] The identity information corresponding to the hash is determined based on the hash, which is the identity information associated with the ticket.

[0108] In one implementation, before the verification unit 7012 verifies the digital signature obtained from the blockchain network based on the ticket and the public key of the second blockchain node device, the comparison module 702 is further configured to: compare the digital certificate of the second blockchain node device obtained from the blockchain network with the digital certificate of the second blockchain node device stored in the first blockchain node device.

[0109] If the digital certificate of the second blockchain node device obtained from the blockchain network is the same as the digital certificate of the second blockchain node device stored in the first blockchain node device, then the signature verification unit 7012 performs the step of verifying the digital signature obtained from the blockchain network based on the ticket and the public key of the second blockchain node device.

[0110] It should be noted that, Figure 7 For details not mentioned in the corresponding embodiments, and the specific implementation methods of the execution steps of each module, please refer to [link to relevant documentation]. Figure 2 , Figure 5 and Figure 6 The embodiments shown and the foregoing content will not be repeated here.

[0111] Please see Figure 8 , Figure 8 This is a schematic diagram of another blockchain node device provided in an embodiment of this application. The blockchain node device 80 includes a processor 801, a memory 802, and a communication interface 803, wherein the processor 801, the memory 802, and the communication interface 803 are connected through one or more communication buses.

[0112] Processor 801 is configured to support blockchain node devices in execution. Figure 2 , Figure 5 and Figure 6 The method describes the corresponding functions of the first blockchain node device. The processor 801 can be a Central Processing Unit (CPU), a Network Processor (NP), a hardware chip, or any combination thereof.

[0113] Memory 802 is used to store program code, etc. Memory 802 may include volatile memory, such as random access memory (RAM); memory 802 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD); memory 802 may also include combinations of the above types of memory.

[0114] The communication interface 803 is used to receive and send data. For example, the communication interface 803 is used to receive a bill issuance request sent by the second blockchain node device, or the communication interface 803 is used to receive enterprise information sent by the second blockchain node device, or the communication interface 803 is used to send a bill to the second blockchain node device, etc.

[0115] In this embodiment of the invention, the blockchain node device 80 includes multiple communication interfaces, wherein the communication interface for sending data and the communication interface for receiving data may not be the same communication interface.

[0116] The processor 801 can call the program code stored in the memory 802 to perform the following operations:

[0117] Communication interface 803 is used to receive a bill issuance request sent by the second blockchain node device. The bill issuance request includes the digital certificate of the second blockchain node device. The first blockchain node device and the second blockchain node device belong to the same blockchain network.

[0118] Processor 801 is used to compare the digital certificate included in the invoice issuance request with the digital certificate of the second blockchain node device stored in the first blockchain node device;

[0119] If the digital certificate included in the bill issuance request is the same as the digital certificate stored in the first blockchain node device, then the first blockchain node device responds to the bill issuance request and generates a bill.

[0120] Communication interface 803 is used to send the ticket to the second blockchain node device, so that the second blockchain node device signs the ticket according to the private key of the second blockchain node device to obtain the digital signature of the ticket, and the second blockchain node device publishes the ticket, the digital signature and the digital certificate of the second blockchain node device to the blockchain network.

[0121] In one implementation, before receiving the bill issuance request sent by the second blockchain node device, the communication interface 803 is further configured to: receive enterprise information sent by the second blockchain node device, and obtain the registration information of the enterprise corresponding to the enterprise information from the management device based on the enterprise information, wherein the management device is used to store the enterprise registration information;

[0122] Processor 801 is used to determine whether the enterprise information corresponds to a creditworthy enterprise.

[0123] If the enterprise information corresponds to a creditworthy enterprise, the processor 801 generates a digital certificate based on the registration information, and the communication interface 803 sends the digital certificate to the second blockchain node device.

[0124] In one implementation, when determining whether the enterprise information corresponds to a creditworthy enterprise, the processor 801 specifically performs the following: based on the historical credit information of the enterprise corresponding to the registration information;

[0125] If the historical credit information only indicates that the enterprise is a creditworthy enterprise, then processor 801 executes the step of generating a digital certificate based on the registration information.

[0126] In one implementation, when determining whether the enterprise information corresponds to a creditworthy enterprise, the processor 801 specifically compares the enterprise information with the registration information.

[0127] If the company information is the same as the registration information, then the company corresponding to the company information is determined to be a creditworthy company.

[0128] In one implementation, before receiving the enterprise information sent by the second blockchain node device, the communication interface 803 is also used to: receive the identity information and biometric information sent by the second blockchain node device;

[0129] Processor 801 is used to retrieve biometric information corresponding to identity information;

[0130] If the biometric information sent by the second blockchain node device matches the found biometric information, then the step of receiving the enterprise information sent by the second blockchain node device is executed.

[0131] In one implementation, when generating a digital certificate based on registration information, the processor 801 is specifically used to: generate a hash of biometric information;

[0132] The processor 801 is also used to generate a digital certificate containing a hash based on the registration information.

[0133] In one implementation, after sending the ticket to the second blockchain node device, the communication interface 803 is also used to: obtain the ticket, digital signature, and digital certificate of the second blockchain node device from the blockchain network.

[0134] The processor 801 is used to verify the digital signature obtained from the blockchain network based on the public key of the ticket and the second blockchain node device.

[0135] If the signature verification is successful, the hash is obtained from the digital certificate of the second blockchain node device;

[0136] The identity information corresponding to the hash is determined based on the hash, which is the identity information associated with the ticket.

[0137] In one implementation, before the processor 801 verifies the digital signature obtained from the blockchain network based on the ticket and the public key of the second blockchain node device, the communication interface 803 is further used to: compare the digital certificate of the second blockchain node device obtained from the blockchain network with the digital certificate of the second blockchain node device stored in the first blockchain node device.

[0138] If the digital certificate of the second blockchain node device obtained from the blockchain network is the same as the digital certificate of the second blockchain node device stored in the first blockchain node device, then the processor 801 executes the step of verifying the digital signature obtained from the blockchain network based on the ticket and the public key of the second blockchain node device.

[0139] Furthermore, the processor 801 can also cooperate with the communication interface 803 to execute... Figure 2 , Figure 5 and Figure 6 The operations corresponding to the first blockchain node device in the method embodiment shown are detailed in the description in the method embodiment and will not be repeated here.

[0140] This application also provides a computer-readable storage medium that can be used to store... Figure 2 , Figure 5 and Figure 6 The computer program used by the blockchain node device in the illustrated embodiment includes a program designed for the first blockchain node device in the above embodiment.

[0141] The aforementioned computer-readable storage media include, but are not limited to, flash memory, hard disk, and solid-state drive.

[0142] This application also provides a computer program product that, when run by a computer device, can perform the above-described... Figure 2 , Figure 5 and Figure 6 The embodiment describes a method for issuing invoices designed for the first blockchain node device.

[0143] This application also provides a chip, including a processor and a memory, the memory for storing a computer program, and the processor for calling and running the computer program from the memory, the computer program for implementing the methods in the above method embodiments.

[0144] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0145] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0146] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method of issuing a document, characterized by, The application is applied to a bill issuing system, the bill issuing system comprises a first blockchain node device and at least one second blockchain node device, and the method comprises the following steps: The first blockchain node device receives identity information and biometric information of a bill issuer sent by the second blockchain node device; if the biometric information corresponding to the identity information is the same as the biometric information sent by the second blockchain node device, the enterprise information sent by the second blockchain node device is received, and the enterprise information comprises registration information of an enterprise; The first blockchain node device obtains historical credit information of an enterprise corresponding to the enterprise information according to the registration information; the historical credit information comprises historical transaction data and risk control information of the enterprise corresponding to the enterprise information; if the historical credit information indicates that the enterprise is a credit enterprise, a hash of biometric information is generated according to a hash algorithm, a digital certificate containing the hash is generated according to the registration information, and the digital certificate is returned to the second blockchain node device; The first blockchain node device receives a bill issuing request sent by the second blockchain node device, wherein the bill issuing request comprises a digital certificate of the second blockchain node device, and the first blockchain node device and the second blockchain node device belong to the same blockchain network; If the digital certificate included in the bill issuing request is the same as the digital certificate stored by the first blockchain node device, the first blockchain node device generates a bill in response to the bill issuing request and sends the bill to the second blockchain node device, so that the second blockchain node device signs the bill according to a private key of the second blockchain node device to obtain a digital signature of the bill, and the second blockchain node device publishes the bill, the digital signature and the digital certificate of the second blockchain node device to the blockchain network; If the digital certificate obtained by the first blockchain node device from the blockchain network is successfully compared with the digital certificate stored by the first blockchain node device, the first blockchain node device verifies the digital signature obtained from the blockchain network according to the bill obtained from the blockchain network and the public key of the second blockchain node device, and obtains a hash in the digital certificate of the second blockchain node device after the verification is successful; The first blockchain node device determines the identity information corresponding to the hash as the identity information associated with the bill according to the association relationship between the hash and the identity information of the bill issuer; the identity information comprises the name, gender and telephone of the bill issuer.

2. The method of claim 1, wherein, Before the first blockchain node device receives the bill issuing request sent by the second blockchain node device, the method further comprises the following steps: The first blockchain node device receives the enterprise information sent by the second blockchain node device and obtains the registration information of the enterprise corresponding to the enterprise information from a management device according to the enterprise information; the management device is used for storing the registration information of the enterprise; The first blockchain node device determines whether the enterprise corresponding to the enterprise information is a credit enterprise according to the registration information; If yes, the first blockchain node device generates a digital certificate according to the registration information and sends the digital certificate to the second blockchain node device.

3. The method of claim 2, wherein, The first blockchain node device determines whether the enterprise corresponding to the enterprise information is a credit enterprise according to the registration information, comprising: The first blockchain node device compares the enterprise information with the registration information; If the enterprise information is the same as the registration information, the first blockchain node device determines that the enterprise corresponding to the enterprise information is a credit enterprise.

4. The method of claim 1, wherein, Before the first blockchain node device verifies the digital signature obtained from the blockchain network according to the public key of the second blockchain node device, further comprising: The first blockchain node device compares the digital certificate of the second blockchain node device obtained from the blockchain network with the digital certificate of the second blockchain node device stored in the first blockchain node device; If the digital certificate of the second blockchain node device obtained from the blockchain network is the same as the digital certificate of the second blockchain node device stored in the first blockchain node device, the first blockchain node device verifies the digital signature obtained from the blockchain network according to the public key of the second blockchain node device. 5.A blockchain node device, characterized in that, A module for executing the method of any one of claims 1-4. 6.A blockchain node device, comprising a processor coupled with a memory, characterized in that, The memory is configured to store a computer program; The processor is configured to invoke the computer program, so that the blockchain node device executes the method of any one of claims 1-4.

7. A computer readable storage medium characterized in that, The computer readable storage medium stores a computer program for the blockchain node device, so that the blockchain node device executes the method of any one of claims 1-4.

8. A computer program product comprising a computer program, characterized in that, The computer program makes the blockchain node device execute the method of any one of claims 1-4.

Images