CN110428292B

CN110428292B - Electronic bill generating method, electronic bill generating device, storage medium and computer equipment

Info

Publication number: CN110428292B
Application number: CN201910682701.0A
Authority: CN
Inventors: 蔡弋戈; 秦青; 戴传兵; 张建俊; 郑罗海; 卢吉光; 王宗友; 屠海涛; 周开班; 蓝虎
Original assignee: Shenzhen Zhishuilian Technology Co ltd
Current assignee: Shenzhen Zhishuilian Technology Co ltd
Priority date: 2018-08-16
Filing date: 2018-08-16
Publication date: 2021-05-11
Anticipated expiration: 2038-08-16
Also published as: CN109034924A; CN110400188A; CN110428292A; CN109034924B; CN110400188B

Abstract

The application relates to an electronic bill generating method, an electronic bill generating device, a computer readable storage medium and computer equipment, wherein the method comprises the following steps: receiving a billing request; the billing request carries bill information; the bill information comprises an invoicing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share; generating an electronic bill making inquiry code corresponding to the bill information; generating an electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into a data block; responding to the billing request, and feeding back the electronic bill billing inquiry code; the electronic bill billing inquiry code is used for inquiring the electronic bill. The scheme that this application provided can greatly reduced invoice issuing's cost.

Description

Electronic bill generating method, electronic bill generating device, storage medium and computer equipment

The present application is a divisional application entitled "electronic bill generating method, apparatus, storage medium, and computer device" filed by the chinese patent office on 16/08/2018 with application number 201810936830.3, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of computer technologies, and in particular, to an electronic ticket generating method, an electronic ticket generating apparatus, a computer-readable storage medium, and a computer device.

Background

The invoice is a consumption certificate provided by a business or an individual for a consumer when selling goods, providing services or doing other business activities to the consumer. When a business or an individual sells goods, provides services or engages in other business activities to a consumer, the business or the individual should make an invoice and legally pay taxes according to the invoice.

The traditional invoicing mode is that enterprises or individuals generally purchase special tax control equipment, invoices can be made only through the special tax control equipment, and the purchase, maintenance and use of the tax control equipment generate cost and expense, so that the invoicing cost is high.

Disclosure of Invention

In view of the above, it is necessary to provide an electronic bill generating method, an electronic bill generating apparatus, a computer-readable storage medium, and a computer device, aiming at the technical problem that the traditional invoicing is expensive.

An electronic bill generation method applied to a blockchain node in a blockchain network, the method comprising:

receiving a billing request; the billing request carries bill information; the bill information comprises an invoicing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share;

generating an electronic bill making inquiry code corresponding to the bill information;

generating an electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into a data block;

responding to the billing request, and feeding back the electronic bill billing inquiry code; the electronic bill billing inquiry code is used for inquiring the electronic bill.

An electronic ticket generating apparatus comprising:

the receiving module is used for receiving an invoicing request; the billing request carries bill information; the bill information comprises an invoicing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share;

the generating module is used for generating an electronic bill billing inquiry code corresponding to the bill information;

the generating module is also used for generating an electronic bill corresponding to the electronic bill billing inquiry code according to the bill information and writing the electronic bill into a data block;

the feedback module is used for responding to the billing request and feeding back the electronic bill billing inquiry code; the electronic bill billing inquiry code is used for inquiring the electronic bill.

A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to execute the steps of the electronic ticket generating method.

A computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the electronic ticket generating method.

The electronic bill generation method, the electronic bill generation device, the computer readable storage medium and the computer equipment receive the billing request carrying the bill information through the block chain link points in the block chain network, wherein the bill information comprises a billing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share. And the block chain link points generate corresponding electronic bill billing inquiry codes according to the bill information, generate electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and write the electronic bills into the data block. And returning the electronic bill issuing inquiry code for inquiring the electronic bill so as to complete issuing the invoice on the block link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

Drawings

FIG. 1 is a diagram showing an application environment of an electronic ticket generating method according to an embodiment;

FIG. 2 is a schematic flow chart showing an electronic ticket generating method according to an embodiment;

FIG. 3 is a flowchart illustrating the steps of generating an electronic ticket billing inquiry code corresponding to the ticket information in one embodiment;

FIG. 4 is a schematic flow chart diagram illustrating the step of feeding back electronic ticket identifications in one embodiment;

FIG. 5 is a schematic diagram of the consensus algorithm in one embodiment;

FIG. 6 is a schematic flow chart showing an electronic ticket generating method in another embodiment;

FIG. 7 is a flowchart showing an electronic ticket generating method according to an embodiment;

fig. 8 is a flowchart showing an electronic ticket generating method in another embodiment;

FIG. 9 is a diagram of a deployment of a data processing system for electronic tickets in one embodiment;

FIG. 10 is a schematic diagram of a flow interface for a blockchain electronic invoice in one embodiment;

FIG. 11 is a schematic view of a flow interface for a blockchain electronic invoice in accordance with an alternative embodiment;

FIG. 12 is a schematic diagram of a flow interface for a blockchain electronic invoice in accordance with yet another embodiment;

FIG. 13 is a schematic view of a flow interface for a blockchain electronic invoice in accordance with yet another embodiment;

FIG. 14 is a block diagram showing the structure of an electronic ticket generating apparatus according to an embodiment;

fig. 15 is a block diagram showing the construction of an electronic ticket generating apparatus in another embodiment;

FIG. 16 is a block diagram showing the structure of an electronic ticket generating apparatus according to an embodiment;

fig. 17 is a block diagram showing the construction of an electronic ticket generating apparatus according to another embodiment;

FIG. 18 is a block diagram showing the construction of a computer device according to one embodiment;

fig. 19 is a block diagram showing a configuration of a computer device in another embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Fig. 1 is a diagram of an application environment of the electronic ticket generating method in one embodiment. Referring to fig. 1, the electronic ticket generating method is applied to a data processing system regarding an electronic ticket. The data processing system related to the electronic bill comprises a billing party device 110 and a block chain network, wherein the block chain network comprises a plurality of block chain nodes, specifically comprising a block chain node corresponding to a tax office server, a billing party block link point 120 corresponding to a billing enterprise, a block link point corresponding to an electronic bill public server, a block chain node corresponding to a reimbursement enterprise and the like. And data can be transmitted between every two block chain nodes. The invoicer device 110 may be a terminal or a server. The invoicer device 110 and the invoicer blockchain node 120 are connected by a network. The terminal may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The server may be implemented as a stand-alone server or as a server cluster consisting of a plurality of servers.

As shown in fig. 2, in one embodiment, an electronic ticket generating method is provided. This embodiment is illustrated primarily by the method applied to the biller block link point 120 in FIG. 1 above. Referring to fig. 2, the electronic bill generating method specifically includes the following steps:

s202, receiving an invoicing request; the billing request carries bill information; the bill information includes an invoicing party identifier, an electronic bill identifier, a receiving party identifier and a resource transfer share.

The billing request is used for issuing an electronic bill, and the billing request carries bill information. The bill information is information used to generate an electronic bill, including an invoice issuer identification, an electronic bill identification, a receiver identification, and a resource transfer share. The electronic bill identification is used for uniquely identifying an electronic bill, and specifically can comprise a bill code and a bill number of the electronic bill. An electronic ticket is a ticket that is stored electronically, such as may be stored in a storage medium or computer device.

The invoicing party identifier is an identifier corresponding to the device initiating the invoicing request and is used for uniquely identifying the invoicing party. The invoicing party may be a selling enterprise, and the invoicing party needs to provide a consumption certificate, i.e. an electronic bill, for the consumer when selling goods, providing services or engaging in other business activities. The invoicing party identification can be specifically a name of a seller, a taxpayer identification number of the seller, an account number of the seller for opening an account, and the like.

The receiver identification is used for uniquely identifying the electronic bill receiver. The recipient may in particular be a consuming individual or a consuming enterprise. After the consuming person or the consuming enterprise consumes at the selling enterprise, the selling enterprise can provide the consuming person or the consuming enterprise with the consumption certificate, namely the electronic bill. The receiver identification may be a name of the purchaser, a taxpayer identification number of the purchaser, an account number of the purchaser, or the like. The resource transfer share is the specific share of the resource consumed by the consumer.

A blockchain node is a data processing node in a blockchain network. A blockchain network is a carrier and organization of the operation blockchain technology. The block chain technology, bt (block chain technology) for short, also called distributed book technology, is an internet database technology, and is characterized by decentralized and transparent disclosure, so that everyone can participate in data recording. The blockchain technology is a brand new distributed infrastructure and computing mode that uses blockchain data structures to verify and store data, uses distributed node consensus algorithms to generate and update data, uses cryptography to secure data transmission and access, and uses intelligent contracts composed of automated script codes to program and manipulate data.

In particular, the recipient identification and resource transfer share may be provided to the invoicer device after the individual or business is finished consuming. And the invoicing party equipment generates the bill information together according to the invoicing party identifier, the electronic bill identifier which is associated with the invoicing party identifier and is in an unused state, the receiver identifier and the resource transfer share. The invoicing side equipment can send invoicing requests carrying bill information to the block chain nodes. The block link point receives the billing request.

In one embodiment, the block link point where the invoicer device uploads data may be a block link node corresponding to the invoicer device. In other embodiments, the block link point where the invoicing side device uploads data may also correspond to a computer device in another authority role. The block chain node corresponding to the invoicing party device can be a block chain link point formed by the invoicing party device, and can also be a block chain link point formed by a third party agent device authorized by the invoicing party.

In one embodiment, the invoicer device signs the ticket information with a private key corresponding to the invoicer device, resulting in an invoiced signature on the ticket information. The billing request sent by the billing party device to the block chain node carries the billing signature and the bill information related to the bill information. And after receiving the invoicing request, the block chain node verifies the invoicing signature through a public key which is locally cached in the block chain node and corresponds to the invoicing party identifier, and when the verification is passed, the subsequent steps are continuously executed.

And S204, generating an electronic bill making inquiry code corresponding to the bill information.

The electronic bill billing inquiry code is used for inquiring the electronic bill and is only corresponding to the electronic bill. The electronic bill billing inquiry code can be specifically a character string, a two-dimensional code or a bar code and the like. Specifically, the block link points can perform hash operation on the bill information through a hash algorithm to obtain the electronic bill billing inquiry code. Examples of the Hash Algorithm include MD5(Message Digest Algorithm, fifth edition), SHA1(Secure Hash Algorithm), SHA2, and the like, and the embodiment is not limited in this respect.

In one embodiment, the block link points may encrypt the ticket information using an encryption algorithm to obtain a ticket ciphertext. And generating a corresponding electronic bill billing inquiry code according to the bill ciphertext. Among them, the encryption algorithm, such as symmetric encryption algorithm and asymmetric encryption algorithm, etc. A symmetric Encryption Algorithm, such as DES (Data Encryption Standard), AES (Advanced Encryption Standard), IDEA (International Data Encryption Algorithm), and the like. Asymmetric cryptographic algorithms, such as RSA (Rivest, Shamir, Adleman, cryptographic Algorithm), DSA (Digital Signature Algorithm), or ECC (Elliptic curve cryptography), etc.

In one embodiment, the blockchain node may extract the ticket information in the billing request, and perform a hash operation on the ticket information to obtain a hash value of the ticket information. Or, the block link point can also perform hash operation on the bill ciphertext to obtain a corresponding bill hash value.

In one embodiment, the blockchain node may directly use the ticket hash value as the electronic ticket billing inquiry code. In another embodiment, the block chain node generates the electronic bill billing inquiry code according to the hash value of the bill and the signature data including the private key signature of the billing party device.

In one embodiment, the authenticity of the electronic ticket issuing inquiry code is approved for both the issuing party and the block link point. Step S204, namely, the step of generating the electronic ticket issuing inquiry code corresponding to the ticket information specifically includes the following steps:

and S302, generating a bill hash value according to the bill information.

Specifically, the block link point may perform hash operation on the ticket information through a hash algorithm to obtain a ticket hash value.

S304, sending the hash value of the bill to the invoicer equipment corresponding to the invoicer identification; and the sent bill hash value is used for indicating the invoicing side equipment to sign the bill hash value to obtain signature data.

In particular, the blockchain node may send the ticket hash value to the invoicer device corresponding to the invoicer identification. And after receiving the ticket hash value, the invoicing side equipment signs the ticket hash value by using a local private key of the invoicing side equipment to obtain signature data, and the signature data is transmitted back to the block chain node.

In one embodiment, after receiving the ticket hash value, the invoicing device can perform hash operation on the ticket information by using the same hash algorithm to verify the authenticity of the ticket hash value sent by the blockchain node. And after the verification is passed, the local private key of the invoicing side equipment is adopted to sign the hash value of the bill to obtain signature data.

And S306, receiving the signature data returned by the invoicing party device.

And S308, when the signature data passes the verification, generating an electronic bill billing inquiry code according to the hash value of the bill and the signature data.

Specifically, after receiving the signature data returned by the invoicing party device, the block chain node verifies the signature data through the public key corresponding to the invoicing party identifier locally cached at the block chain node. And after the signature data passes the verification, the block link point performs hash operation on the hash value of the bill and the signature data to generate an electronic bill billing inquiry code.

In one embodiment, after receiving the signature data returned by the invoicing side device, the block link point can transmit the signature data and the bill information to other block link nodes in the block link network, and after the block link nodes achieve consensus, the block link point generates the electronic bill invoicing query code according to the hash value of the bill and the signature data.

In the embodiment, the bill hash value is generated according to the bill information, and the bill billing inquiry code is generated through the signature data obtained by signing the bill hash value by the equipment of the billing party, so that the authenticity of the electronic bill billing inquiry code can be guaranteed to be approved by both the block chain node and the equipment of the billing party, and the authenticity of the electronic bill is further guaranteed.

And S206, generating the electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into the data block.

Wherein, the electronic bill is an electronically stored bill. A data block is a memory module in a block link point that is used to store data.

Specifically, after the block link points generate the electronic bill billing inquiry code, the bill information and the electronic bill billing inquiry code can be associated to generate the electronic bill. The block chain node may write the generated electronic ticket to the data block.

In one embodiment, the blockchain node can generate the electronic bill according to the bill information and associate the electronic bill with the electronic bill billing inquiry code, so that the electronic bill billing inquiry code can be regarded as an index of the electronic bill and used for searching the corresponding electronic bill.

In one embodiment, the blockchain node can generate the electronic bill according to the association between the bill information and the electronic bill billing inquiry code. Therefore, when the electronic bill inquiry code is used for inquiring, the bill information corresponding to the electronic bill inquiry code can be inquired.

In one embodiment, before generating the electronic bill billing inquiry code, the blockchain node sends corresponding bill information and the like to other blockchain nodes in the blockchain network, and after the blockchain nodes reach the consensus, the blockchain nodes generate the electronic bill billing inquiry code. At this point, the block chain node may write the electronic ticket directly to the data block as new blocks are generated. Therefore, after the bill information achieves consensus through the block chain network, the block chain node generates the electronic bill billing inquiry code according to the bill information, and authenticity and reliability of the electronic bill billing inquiry code can be guaranteed.

In one embodiment, the blockchain node may send the electronic ticket to other blockchain nodes in the blockchain network after generating the electronic ticket, and the blockchain nodes write the electronic ticket into the data block after reaching the consensus.

S208, responding to the billing request, and feeding back the billing inquiry code of the electronic bill; the electronic bill billing inquiry code is used for inquiring the electronic bill.

Specifically, the block link point responds to the invoicing request, and feeds back an electronic bill invoicing query code to the invoicing party equipment corresponding to the invoicing party identifier, wherein the electronic bill invoicing query code is used for querying an electronic bill. After the invoicing side equipment receives the electronic bill invoicing query code, the corresponding electronic bill invoicing query code can be fed back to the consumer.

In one embodiment, the block chain node point feeds back the electronic ticket issuing inquiry code and the feedback information indicating the success of issuing the ticket to the equipment of the corresponding issuing party of the issuing party identification in response to the issuing request. The feedback information indicating the successful invoicing may specifically be a feedback code indicating the successful invoicing, such as 0000 or 1111.

In one embodiment, after receiving the electronic bill billing query code fed back by the blockchain node, the invoicing party device can search the corresponding electronic bill from the blockchain node in the blockchain network according to the electronic bill billing query code. The invoicing side device can extract the bill information from the electronic bill and feed the bill information back to the consumer.

In one embodiment, the consumer may store the ticket information through an electronic ticket public server and log into the electronic ticket public server with the consumer identification to view the ticket information associated with the consumer identification.

In one embodiment, the electronic ticket written in the data block includes an encrypted ticket cryptogram. When the block chain link points are encrypted by the public key corresponding to the invoicing party equipment, the invoicing party equipment can correspondingly decrypt the electronic bills acquired from the block chain network according to the private key corresponding to the invoicing party equipment to acquire bill information.

In one embodiment, the electronic ticket written in the data block includes an encrypted ticket cryptogram. When the block chain node feeds back the electronic bill billing inquiry code to the billing party equipment, the corresponding decryption key can be fed back at the same time, so that the billing party equipment can decrypt the electronic bill according to the corresponding decryption key to obtain the bill information. Accordingly, the invoicing party device can transmit the corresponding decryption key and the electronic bill invoicing inquiry code to the consumer.

In one embodiment, the electronic ticket is a blockchain electronic invoice; the electronic bill identification is a block chain electronic invoice number; the invoicing party identifier is an enterprise identifier.

The block chain electronic invoice is an electronic invoice processed based on a block chain technology. The blockchain electronic invoice number may specifically include an invoice code and an invoice number. The enterprise identifier is used for uniquely identifying an enterprise, and can be a unique identifier distributed to the enterprise by a tax bureau after the enterprise is registered by the tax bureau.

Specifically, after the paper invoice is electronized, before the electronic invoice is not issued, the concept of a blank invoice can be considered to be no longer existed. Then, the billing enterprise claims the block chain electronic invoice number capable of issuing the invoice in the tax bureau, and uploads the billing party identifier, the block chain electronic invoice number, the receiver identifier and the resource transfer share to the block chain node to generate the block chain electronic invoice when the block chain electronic invoice needs to be issued.

The electronic bill generation method receives the billing request carrying the bill information through the block chain link points in the block chain network, wherein the bill information comprises a billing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share. And the block chain link points generate corresponding electronic bill billing inquiry codes according to the bill information, generate electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and write the electronic bills into the data block. And returning the electronic bill issuing inquiry code for inquiring the electronic bill so as to complete issuing the invoice on the block link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

In one embodiment, the electronic ticket generating method further includes a step of feeding back an electronic ticket identifier, and the step specifically includes:

s402, receiving an electronic bill identification receiving request; the electronic bill identification receiving request carries an identification of the invoicer.

Wherein the electronic bill identification reception request is used for obtaining available electronic bill identification. Specifically, when the invoicing party needs to make an invoice, the block chain node may obtain an electronic bill receiving request triggered by the invoicing party equipment, where the electronic bill receiving request carries an identifier of the invoicing party.

S404, determining the electronic bill identification which is associated with the invoicer identification and is in an unused state in the blockchain node.

Specifically, when the block chain node receives an electronic bill identification receiving request, the invoicing party identification can be extracted from the electronic bill identification receiving request, and the electronic bill identification which is associated with the invoicing party identification and is in an unused state is searched in the block chain network.

In one embodiment, the blockchain node may store the electronic ticket identification belonging to the invoicer in association with the invoicer identification in the data block. When the block chain node receives an electronic bill identification receiving request initiated by the invoicing side equipment, the electronic bill identification related to the requester identification is searched in the data block. The blockchain node may sift out electronic ticket identifications in an unused state from the electronic ticket identifications associated with the invoicer identifications.

In one embodiment, after the blockchain node feeds back the electronic bill identifier in the unused state to the billing enterprise, the blockchain node can mark the bill state of the electronic bill identifier as the used state.

And S406, responding to the electronic bill identification receiving request, and feeding back the determined electronic bill identification.

Specifically, the block link point feeds back the determined electronic ticket identifier associated with the invoicer identifier and in an unused state to the invoicer device in response to the electronic ticket identifier receiving request.

In one embodiment, after the invoicing party device acquires the electronic bill identifier which is associated with the invoicing party identifier and is in an unused state, the invoicing party device generates bill information according to the acquired receiver identifier and the resource transfer share. And the invoicing side equipment sends an invoicing request carrying bill information to the block chain link points.

In the above embodiment, the request for receiving the electronic ticket identifier carrying the invoicing party identifier is received, and in response to the request, the electronic ticket identifier which is associated with the invoicing party identifier and is in an unused state is fed back. The electronic bill identification which is associated with the bill making party identification and is in an unused state can be acquired from the block link point by the bill making party, so that a bill making enterprise does not need to apply a blank invoice in advance. Therefore, the invoice issuing efficiency is greatly improved, and the invoice issuing cost is reduced.

In one embodiment, the electronic ticket generating method further includes a step of verifying the issuing condition of the electronic ticket, and the step specifically includes: inquiring the electronic bill making conditions corresponding to the bill maker identification from the block chain nodes; and verifying the legality of the bill information according to the electronic bill issuing condition. Step S308, namely, after the signature data passes the verification, the step of generating the electronic bill billing inquiry code according to the hash value of the bill and the signature data comprises the following steps: and when the signature data passes the verification and the bill information passes the verification, generating an electronic bill billing inquiry code according to the hash value of the bill and the signature data.

The electronic bill issuing condition is a constraint condition for limiting the electronic bill issuing according to the electronic bill issuing control cycle. The electronic bill making condition can also be called electronic bill making intelligent contract. The electronic ticket issuing control cycle is a time length for controlling electronic ticket issuing data, such as one or more of a natural day, a natural week, a natural month, or a natural year. And controlling the billing data of the electronic bill, such as controlling the billing quantity of the electronic bill or the billing amount of a single electronic bill. For example, the electronic bill issuing conditions are specifically as follows: the amount of invoices of an enterprise A (an invoicing party) capable of opening value-added tax electronic bill in a natural month is 300, and the maximum invoicing amount of a single electronic bill is one thousand yuan.

In one embodiment, the electronic bill making conditions corresponding to the invoicer identifications are set by the electronic bill management server in a user-defined mode according to the invoicer feature data corresponding to the invoicer identifications, and are uploaded to the block chain network so that each block chain link point can be inquired and used when needed. The characteristic data of the invoicers comprises basic data of the invoicers and/or behavior data of the invoicers. The invoicer basic data is data reflecting the basic characteristics of the invoicer. The invoicer behavior data is data reflecting the invoicer behavior characteristics.

For example, when the invoicer identifies the identified invoicer as an enterprise user, the invoicer base data is such as: business name, business type or business scope, etc. Biller behavior data such as: enterprise billing data, enterprise ticketing data, enterprise tax payment data, and the like.

It is understood that the electronic ticket issuing condition set corresponding to the invoicer identification is updatable. The invoicing party can register with the real name through the electronic bill management server, and after the registration is completed, the electronic bill management server can set the electronic bill making conditions corresponding to the invoicing party identification for the first time according to the basic data of the invoicing party in the registration data. For example, the billing enterprise can issue 300 electronic invoices of value-added tax every month. And then, the electronic bill management server can automatically update the electronic bill making conditions corresponding to the invoicer identification according to the updated basic data and/or the invoicer behavior data, and can also respond to a request initiated by the invoicer identification to update the electronic bill making conditions corresponding to the invoicer identification.

In one embodiment, the block link point extracts the billing information in the billing request after receiving the billing request. The blockchain node may query the electronic ticket issuing conditions corresponding to the invoicer identification in the blockchain network. And verifying the legality of the bill information by the block chain node according to the inquired electronic bill making condition. For example, it is verified whether the number of invoices by an invoicing party in the electronic bill issuing control period conforms to the electronic bill issuing condition or not, or whether the invoicing amount of a single electronic bill conforms to the electronic bill issuing condition or not, and the like.

When the bill information conforms to the electronic bill making condition and the signature data is verified to be really sent by the bill making equipment, the block chain node can transmit the bill information and the signature data to other block chain nodes in the block chain network to finish consensus. After the block chain nodes achieve consensus, namely when the signature data passes verification and the bill information passes verification, the block chain nodes generate the electronic bill billing inquiry code according to the hash value of the bill and the signature data.

Common consensus algorithms in the blockchain network include POW (Proof of Work), POS (Proof of interest), DPOS (guaranteed Proof of interest), PBFT (Practical Byzantine Fault-tolerant algorithm), and the like.

The consensus algorithm employed in one particular embodiment is specifically a consensus algorithm (Bft-Raft) based on a consensus algorithm (e.g., Raft) and a Byzantine fault-tolerant algorithm (e.g., Bft). Of course, other consensus algorithms may be adopted in other embodiments of the present invention, and the embodiments of the present invention are not limited herein.

For example, FIG. 5 shows a schematic diagram of the consensus algorithm in one embodiment. Referring to fig. 5, a Client (Client, specifically, may be a blockchain electronic invoice application platform as shown in fig. 9) initiates a consensus Request (Request) and sends the consensus Request to a blockchain node (master node Leader a) in a Leader state. And the block chain nodes in the leader state are obtained by jointly electing each block chain link point in the block chain network. Continuing to enter an application Entity stage, broadcasting the consensus content (or intermediate data obtained after processing the consensus content) corresponding to the consensus request to other blockchain nodes (following nodes, namely, Follower B, Follower C and Follower D …) which are not in a Leader state in the blockchain network by the Leader A; and continuing to enter an application Response stage, broadcasting the received consensus content to other blockchain nodes by each slave node, entering a Commit stage when the consensus contents broadcast by the other blockchain nodes with the preset number (2f +1) are consistent, and feeding back the confirmation result to the master node by each slave node. And when the master node receives the feedback confirmation of other block link points with the preset number (2f +1), judging that the consensus is completed and feeding back (Reply) the result of the completion of the consensus to the Client. Wherein, 3f +1 is not more than N, N is the number of the block chain nodes in the block chain network. f is the number of bad blockchain nodes in the blockchain network.

In the above embodiment, the validity of the ticket information is verified through the electronic ticket issuing condition, and when the signature data passes the verification and the ticket information passes the verification, the electronic ticket issuing inquiry code is generated according to the hash value of the ticket and the signature data, so that the validity of the generated electronic ticket can be guaranteed.

In one embodiment, the electronic ticket generating method further includes a step of encrypting ticket information, and the step specifically includes: generating a bill symmetric key corresponding to the bill information; encrypting the bill information through the bill symmetric key to obtain a bill ciphertext; acquiring a public key of the invoicing party corresponding to the identifier of the invoicing party; and encrypting the bill symmetric key through the public key of the invoicing party to obtain a first bill symmetric key ciphertext. The step of producing the electronic bill corresponding to the electronic bill billing inquiry code according to the bill information specifically comprises the following steps: and generating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext and the electronic bill billing inquiry code.

The ticket symmetric key is a key of the electronic ticket and is a symmetric key. And encrypting the bill information by using the bill symmetric key to obtain a bill ciphertext, and decrypting the bill ciphertext by using the bill symmetric key to obtain the bill information.

The invoicer public key is the public key of the key pair associated with the invoicer identification. The invoicing party device can generate a key pair corresponding to the invoicing party identifier, wherein the key pair comprises an invoicing party public key and an invoicing party private key. The invoicing party device can automatically store the private key of the invoicing party and disclose the public key of the invoicing party. The blockchain node may cache the invoicer public key corresponding to the invoicer identification. It will be appreciated that the data is encrypted by the biller public key and decrypted by the corresponding biller private key. Similarly, the data is encrypted by the private key of the invoicer and can be decrypted by the corresponding public key of the invoicer.

Specifically, after acquiring the ticket information, the blockchain node may randomly generate a ticket symmetric key corresponding to the ticket information. And encrypting the bill information through the bill symmetric key to obtain a bill ciphertext. And searching the public key of the invoicing party corresponding to the identifier of the invoicing party. And the block chain node encrypts the bill symmetric key through the public key of the bill issuer to obtain a first bill symmetric key ciphertext.

Furthermore, the block chain node can correlate the bill ciphertext, the first bill symmetric key ciphertext and the electronic bill billing inquiry code to generate an electronic bill, and then write the electronic bill into the data block.

In the above implementation, when the electronic ticket stored in the blockchain network is encrypted data. When the invoicing party receives the electronic bill invoicing inquiry code fed back by the block chain point, the electronic bill corresponding to the electronic bill invoicing inquiry code can be searched from the block chain network. And decrypting the ciphertext of the bill by using the private key of the invoicing party corresponding to the identifier of the invoicing party to obtain the symmetric key of the bill, and decrypting the ciphertext of the bill by using the symmetric key of the bill to obtain the information of the bill in the plaintext.

In the above embodiment, the ticket information is encrypted in a symmetric encryption manner to obtain a ticket ciphertext, and the ticket symmetric key is encrypted by the public key of the invoker corresponding to the identifier of the invoker to obtain a first ticket symmetric key ciphertext. The electronic bill is generated according to the bill ciphertext, the first bill symmetric key ciphertext and the electronic bill billing query code, so that only the billing party with the billing party private key can obtain the plaintext data of the electronic bill, and the data security of the electronic bill is guaranteed.

In one embodiment, the electronic ticket generating method further includes a step of encrypting through a consumer public key, and the step specifically includes: acquiring a consumer identifier corresponding to the bill information; searching a consumer public key corresponding to the consumer identification; and encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext. The step of generating the electronic bill corresponding to the electronic bill billing inquiry code according to the bill information specifically comprises the following steps: and generating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code.

Wherein the consumer identification is used to uniquely identify the consumer. The consumer identification may specifically be a user name and password, a certificate number of the consumer, or a registration code of the consumer, etc. The consumer public key is the public key of the key pair associated with the consumer identification. The consumer can log in the electronic bill public server through the registered consumer identification, and a key pair corresponding to the consumer identification is generated through the electronic bill public server and comprises a consumer public key and a consumer private key. The public server of the electronic bill can help the consumer to store the private key of the consumer and disclose the public key of the consumer. The blockchain node may cache a consumer public key corresponding to the consumer identification. It will be appreciated that data encrypted by a consumer public key may be decrypted by a corresponding consumer private key. Likewise, data encrypted by a consumer private key may be decrypted by a corresponding consumer public key.

In one embodiment, the ticket information further includes a customer identification. And the block chain node can search the public key of the invoicer corresponding to the identifier of the invoicer from the locally cached secret key according to the identifier of the consumer. And the block chain node encrypts the bill symmetric key through the public key of the bill issuer to obtain a second bill symmetric key ciphertext.

Furthermore, the block chain node can correlate the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code to generate an electronic bill, and then write the electronic bill into the data block.

In one embodiment, no customer identification is included in the ticket information. The block chain node feeds back the electronic bill billing inquiry code to the billing party equipment, and the billing party equipment transmits the electronic bill billing inquiry code and the ownership of the electronic bill to the consumer. The consumer can temporarily store the delivered electronic bill to the electronic bill public server. And the electronic bill public server acquires the consumer identification and uploads the consumer identification to the block chain node. And obtaining the consumer identification by the block chain link points, searching the consumer public key corresponding to the consumer identification, and encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext. And updating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code.

In the above embodiment, the electronic ticket includes the first ticket symmetric key ciphertext encrypted by the public key of the invoicing party and the second ticket symmetric key ciphertext encrypted by the public key of the consumer, so that both the invoicing party and the consumer can decrypt the electronic ticket by their respective private keys to obtain the electronic ticket plaintext, that is, the ticket information.

In the above embodiment, the ticket symmetric key is encrypted by the consumer public key corresponding to the consumer identifier, so as to obtain the second ticket symmetric key ciphertext. The electronic bill is generated according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing query code, so that only the billing party with the private key of the billing party and the consumer with the public key of the consumer can obtain the plaintext data of the electronic bill, and the data security of the electronic bill is guaranteed.

In a specific embodiment, the electronic ticket generating method specifically includes the following steps:

s602, receiving an electronic bill identifier receiving request; the electronic bill identification receiving request carries an identification of the invoicer.

S604, determining the electronic bill identification which is associated with the invoicer identification and is in an unused state in the block chain node.

And S606, responding to the electronic bill identifier receiving request, and feeding back the determined electronic bill identifier.

S608, receiving a billing request; the billing request carries bill information; the ticket information comprises an invoicer identification, an electronic ticket identification which is associated with the invoicer identification and is in an unused state, a receiver identification and a resource transfer share.

S610, inquiring the electronic bill making condition corresponding to the invoicing party identification from the block chain node.

And S612, verifying the legality of the bill information according to the electronic bill issuing condition.

And S614, generating the bill hash value according to the bill information.

S616, sending the hash value of the bill to the invoicing party device corresponding to the invoicing party identifier; and the sent bill hash value is used for indicating the invoicing side equipment to sign the bill hash value to obtain signature data.

And S618, receiving the signature data returned by the invoicing side device.

And S620, when the signature data pass the verification and the bill information passes the verification, generating an electronic bill billing inquiry code according to the hash value of the bill and the signature data.

S622, a ticket symmetric key corresponding to the ticket information is generated.

And S624, encrypting the bill information through the bill symmetric key to obtain a bill ciphertext.

And S626, acquiring the public key of the invoicer corresponding to the identifier of the invoicer.

And S628, encrypting the bill symmetric key through the public key of the invoicing party to obtain a first bill symmetric key ciphertext.

S630, acquiring the consumer identification corresponding to the bill information.

S632, finding the public key of the consumer corresponding to the consumer identification.

And S634, encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext.

And S636, generating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code, and writing the electronic bill into the data block.

S638, responding to the billing request, feeding back the electronic bill billing inquiry code; the electronic bill billing inquiry code is used for inquiring the electronic bill.

Fig. 6 is a flowchart illustrating an electronic ticket generating method according to an embodiment. It should be understood that, although the steps in the flowchart of fig. 6 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 6 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

As shown in fig. 7, in one embodiment, an electronic ticket generating method is provided. The present embodiment is mainly illustrated by applying the method to the invoicing apparatus 110 in fig. 1. Referring to fig. 7, the electronic ticket generating method specifically includes the following steps:

s702, acquiring the receiver identification and the resource transfer share.

In one embodiment, the invoicing party device can display the bill information input interface and obtain the receiver identification and the resource transfer share input into the bill information input interface. Or the invoicing party can display the bill information input interface on the terminal, and the terminal where the invoicing party is located can send the receiver identification and the resource transfer share in the bill information input interface to the invoicing party equipment.

In one embodiment, after a consumer consumes through a payment application, a server corresponding to the payment application may upload transaction information to the blockchain network. The billing device can directly acquire the receiver identification and the resource transfer share corresponding to the consumer identification from the blockchain network. The transaction information is related information of resource transfer between the consumer (or consumer enterprise) and the sales enterprise, such as details, amount, time, location, consumer identification, sales enterprise identification, and the like of the item to be transacted.

S704, acquiring the electronic bill identification associated with the current invoicer identification.

Specifically, the billing enterprise may obtain the electronic ticket identification associated with the current biller identification from a block link point.

In one embodiment, the biller device sends an electronic ticket identification acceptance request to the block link point; the request for receiving the electronic bill identification carries an identification of a biller; the electronic bill identification receiving request is used for indicating the block chain node to inquire the electronic bill identification which is associated with the invoicing party identification and is in an unused state; and receiving the electronic bill identification fed back by the block chain node.

Specifically, when the invoicing party needs to make an invoice, an electronic bill identification receiving request carrying the invoicing party identification can be sent to the block chain nodes. And the block chain node searches the electronic bill identification which is associated with the invoicing party identification and is in an unused state in the block chain network, and feeds back the determined electronic bill identification which is associated with the invoicing party identification and is in the unused state to the invoicing party equipment.

In one embodiment, when the electronic ticket identifications associated with the invoicer identifications in the blockchain node are all marked as used states, the electronic ticket generation method further includes a step of claiming the electronic ticket identifications, which specifically includes: receiving feedback information fed back by the block chain link points, wherein the feedback information indicates that electronic bill identifications which are related to the invoicer identifications and are in an unused state are not inquired; responding to the feedback information, and initiating an electronic bill identification claiming request to an electronic bill management server; the electronic bill identification claiming request is used for indicating the electronic bill management server to distribute the electronic bill identification according to the electronic bill claiming condition and uploading the distributed electronic bill identification and the invoicing party identification to the block chain node in a correlation manner.

The electronic bill management server is a server for managing the circulation process of the electronic bill, such as a server provided by a tax bureau. The electronic bill identification claiming request is used for applying for claiming available electronic bill identifications from the electronic bill management server. Before claiming the electronic bill identification from the electronic bill management server, the invoicing party needs to register the electronic bill circulation management server successfully.

The electronic bill claim condition is a constraint condition for limiting the electronic bill claim according to the electronic bill making control period. The electronic bill billing control period is a time length for controlling the electronic bill billing data, such as one or more of natural days, natural weeks, natural months, or natural years. And controlling the billing data of the electronic bill, such as controlling the billing quantity of the electronic bill or the billing amount of a single electronic bill.

Specifically, when the invoicing side device sends an electronic bill identifier receiving request to the block link point, and the block link point does not search the electronic bill identifier which is associated with the invoicing side identifier and is in an unused state in the block link network, the block link node feeds back corresponding feedback information to the invoicing side device. And the invoicing side equipment responds to the feedback information and initiates an electronic bill identification claiming request to the electronic bill management server. And the electronic bill management server distributes unused electronic bill identification for the invoicers according to the electronic bill claim condition, and uploads the distributed electronic bill identification and the invoicer identification to the block chain node in a correlation manner.

In the above embodiment, when the block link point feeds back the feedback information of the electronic bill identifier associated with the invoicing party identifier and in an unused state, the block link point initiates an electronic bill identifier claiming request to the electronic bill management server. Therefore, unused electronic bill identification is distributed and linked up through the electronic bill management server, time consumption caused by manual application of paper bills by invoices is avoided, and bill application efficiency is improved. Moreover, the electronic bill identification and the invoicing party identification are linked up in a related mode, and the safety and reliability of the bill application data are guaranteed through the block chain.

S706, generating bill information according to the invoice party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share.

Specifically, the invoicing party device can associate an invoicing party identifier, an electronic bill identifier, a receiving party identifier and a resource transfer share, and generate bill information according to a preset bill format.

S708, uploading the bill information to a block chain node in a block chain network; and the uploaded bill information is used for indicating the block chain link points to generate electronic bill billing inquiry codes corresponding to the bill information, generating electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and writing the electronic bills into the data block.

Specifically, the billing enterprise may upload the ticket information to the blockchain node in the blockchain network. And generating an electronic bill billing inquiry code corresponding to the bill information by the block chain link points, generating an electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into the data block. The step of generating the electronic bill billing inquiry code corresponding to the bill information by the block link point, generating the electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into the data block may refer to the specific implementation manner of the above steps S204 to S206.

In one embodiment, there may be an invoicer blockchain node in the blockchain network that corresponds to the invoicer device. When the invoicing side equipment intends to write data into the block chain network, the data can be directly transmitted to the invoicing side block chain link point through an interface provided by the corresponding invoicing side block chain link point, and the invoicing side block chain link point is identified with other block chain link points in the block chain node in a cooperation manner, and then the data is written into the data block.

In one embodiment, it is understood that the electronic ticket management server first uploads the electronic ticket id assigned to the invoicer device to the corresponding block link point, and the block link point cooperates with other block link nodes to achieve consensus, and then writes the electronic ticket id assigned to the invoicer device into the data block. And after the block link points cooperate with other block link nodes to achieve consensus and write the generated electronic bill into a data block, the block link points corresponding to the electronic bill management server form a block chain with the block link points corresponding to the invoicing side equipment.

It should be noted that the block chain link points corresponding to different invoicing party devices and the block chain link points corresponding to the electronic bill management server form different block chains, and the different block chains can operate independently without mutual influence.

S710, receiving an electronic bill billing inquiry code returned by the block chain node; the electronic bill billing inquiry code is used for inquiring the electronic bill.

Specifically, the block chain node feeds back an electronic bill billing inquiry code to the billing party device corresponding to the billing party identifier, and the electronic bill billing inquiry code is used for inquiring the electronic bill. After the invoicing side equipment receives the electronic bill invoicing query code, the corresponding electronic bill invoicing query code can be fed back to the consumer. Accordingly, the step of receiving the electronic bill billing inquiry code returned by the blockchain node may refer to the specific implementation of the step S208.

The electronic bill generating method generates bill information according to the invoice party identifier, the electronic bill identifier associated with the current invoice party identifier, the receiver identifier and the resource transfer share. And uploading the bill information to block chain link points in a block chain network, generating an electronic bill making inquiry code corresponding to the bill information by the block chain link points, generating an electronic bill corresponding to the electronic bill making inquiry code according to the bill information, writing the electronic bill into a data block, and finally returning the electronic bill making inquiry code for inquiring the electronic bill so as to complete invoice making on the block chain link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bills into the data blocks, so that the safety, reliability and reliability of the electronic bills can be guaranteed, and the authenticity of the electronic bill billing inquiry codes received by enterprises or individuals is further guaranteed.

In one embodiment, step S706 specifically includes: inquiring the electronic bill making conditions corresponding to the invoicing party identification from the block chain nodes; and generating bill information according to the inquired electronic bill making conditions and according to the bill making party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share.

The electronic bill issuing condition is a constraint condition for limiting the electronic bill issuing according to the electronic bill issuing control cycle. The electronic bill making condition can also be called electronic bill making intelligent contract. When invoicing is required, the invoicing side equipment can inquire the electronic bill issuing conditions corresponding to the invoicing side identification from the corresponding block chain nodes. And generating bill information according to the inquired electronic bill making conditions and according to the bill making party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share.

For example, the electronic ticket issuing conditions include an issuing amount of a single electronic ticket, for example, an issuing amount of a single electronic ticket for an a corporation (issuing party) issuing an electronic ticket with an added-value tax is one kilo yuan at maximum. When the resource transfer share is one thousand wubai, two unused electronic bill identifiers are needed. For example, the invoicing party identifier A, the electronic bill identifier 1, the receiver identifier and the resource transfer share Jiubai are associated to generate a bill message; and generating another piece of bill information by the invoicing party identifier A, the electronic bill identifier 2, the receiver identifier and the resource transfer share continental herborist.

In the embodiment, the electronic bill making conditions corresponding to the invoicer identification are inquired from the block link points, and the bill information is generated according to the inquired electronic bill making conditions, so that the accuracy and the legality of the bill information are guaranteed.

In a specific embodiment, referring to fig. 8, the electronic ticket generating method includes:

s802, acquiring the receiver identification and the resource transfer share.

S804, sending an electronic bill identification receiving request to the block link point; the request for receiving the electronic bill identification carries an identification of a biller; the electronic bill identification receiving request is used for indicating the block chain node to inquire the electronic bill identification which is associated with the invoicer identification and is in an unused state.

And S806, receiving the electronic bill identification fed back by the block chain node.

And S808, receiving feedback information fed back by the block link points, wherein the feedback information indicates that the electronic bill identifier which is associated with the invoicing party identifier and is in an unused state is not inquired.

S810, responding to the feedback information, and initiating an electronic bill identification claiming request to the electronic bill management server; the electronic bill identification claiming request is used for indicating the electronic bill management server to distribute the electronic bill identification according to the electronic bill claiming condition and uploading the distributed electronic bill identification and the invoicing party identification to the block chain node in a correlation manner.

S812, inquiring the electronic bill making conditions corresponding to the invoicing party identification from the block chain nodes.

S814, generating bill information according to the inquired electronic bill making conditions and according to the bill making party identification, the electronic bill identification, the receiver identification and the resource transfer share.

S816, uploading the bill information to a block chain node in the block chain network; and the uploaded bill information is used for indicating the block chain link points to generate electronic bill billing inquiry codes corresponding to the bill information, generating electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and writing the electronic bills into the data block.

S818, receiving the electronic bill billing inquiry code returned by the block chain node; the electronic bill billing inquiry code is used for inquiring the electronic bill.

Fig. 8 is a flowchart illustrating an electronic ticket generating method according to an embodiment. It should be understood that, although the steps in the flowchart of fig. 8 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 8 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

Referring to FIG. 9, a diagram of a deployment of a data processing system for electronic tickets is shown in one particular embodiment. In a specific block chain electronic invoice application scenario, referring to fig. 9, a block chain network includes at least 4 block chain nodes to form a federation chain, which are respectively a block chain node corresponding to a tax office server, a block chain node corresponding to an invoicing enterprise, a block chain node corresponding to an electronic invoice utility server, and a block chain node corresponding to an reimbursement enterprise. Typically, the devices of each role interact with the corresponding tile link points. The electronic bill public server is used for storing the issued block chain electronic invoices for the consumers, and can be a WeChat server and the like.

On one hand, the tax office server provides an access interface (an internal interface for tax office terminals and an external interface for enterprise users) for the equipment of each role to access through the reverse proxy service, hosts the identity key of each role and manages the characteristic data of each role. On the other hand, data of the blockchain network (or data to be written after consensus) is synchronously written in from the blockchain network module in the corresponding blockchain node through a synchronization tool in real time so as to query and count the blockchain electronic invoice related data of each role.

On one hand, each block link point in the block chain network provides an access interface for corresponding equipment to access through reverse proxy service (for example, equipment of an invoicing enterprise accesses the block link point corresponding to the invoicing enterprise). On the other hand, the data sent by the corresponding device through the reverse proxy service is received through the blockchain electronic invoice application platform (for example, the device of the billing enterprise uploads the data to the blockchain link point corresponding to the billing enterprise, that is, the data is transmitted to the blockchain electronic invoice application platform through an interface provided by the reverse proxy service, etc.). The blockchain electronic invoice application platform then transmits the data to the blockchain network module. The block chain network modules of each block chain node jointly form a consensus network, and after consensus is achieved in the consensus network, data is written into the block chain network modules. The blockchain node also comprises a cache database used for caching various data, such as an enterprise public key obtained from a system center server.

The deployment map may further include a block chain network module system central server, which stores the mapping between the enterprise identification and the public key of each enterprise, is isolated from the tax office server, and is mainly used for identity authentication (e.g., only the tax office is restricted to issue invoices, and constraint conditions related to the enterprise are changed). Subsequent operations which need to be centralized are uniformly put into the central server of the system to be executed.

The reverse proxy service may specifically be nginx. The blockchain electronic invoice Application platform realizes the main business logic of the blockchain electronic invoice, and exposes sdk (Software Development Kit) and api (Application Programming Interface) interfaces for interaction of a third party through reverse proxy service access. The blockchain network module can be specifically realized based on the Tencent underlay blockchain technology (trustSQL). The cache region may be specifically implemented by a mysql database. It is to be understood that the present embodiments are for illustration and not intended to limit the implementations employed in specific implementations.

In a specific application scenario, the electronic ticket may specifically be a blockchain electronic invoice, the electronic ticket management server may specifically be a tax office server, the invoicing party device may specifically be a terminal or a server corresponding to an electronic ticket invoicing party (an electronic ticket submitting party), and the electronic ticket public server may specifically be a public storage service for providing an electronic ticket originating from a blockchain link point, such as a wechat server. It can be understood that the billing enterprise can be used as an electronic bill billing party to make an electronic bill and can also be used as an electronic bill reporting party to reimburse the electronic bill.

Specific steps of the electronic bill generation method are exemplified according to the specific application scenario. The consumer consumes at the billing enterprise, and the billing enterprise can issue a corresponding invoice according to the amount of money consumed by the consumer. The customer provides the invoice with a new line, i.e., the identifier of the reimburser, to the billing enterprise. The billing enterprise uploads the invoicing party identifier, the block chain electronic invoice number, the receiver identifier and the consumption amount to block chain link points in a block chain network in a correlated manner, the block chain link points generate block chain electronic invoices (also called digital invoices), and feeds back electronic bill billing inquiry codes of the block chain electronic invoices to the invoicing enterprise, so that the invoicing enterprise gives the invoicing inquiry codes to consumers, and the invoicing is completed.

It is understood that in a blockchain network, there may be blockchain link points corresponding to KA (key Account) tax enterprises, and there may also be blockchain link points corresponding to third party proxy devices. And the third-party agent equipment is used for medium and small enterprises to access the blockchain network.

The following is specifically illustrated by two specific application scenarios:

the first business scenario is a parking lot charging scenario.

For small and medium-sized enterprises, block chain electronic invoices can be issued through third-party agent equipment. If the taxpayer does not get through the parking system or receives cash and the like from the sentry box, the invoicing two-dimensional code can be printed by the receipt printer and delivered to the user, and the user submits information by scanning the invoicing two-dimensional code so as to issue the block chain electronic invoice. Referring to fig. 10, fig. 10 illustrates a flow interface diagram of a blockchain electronic invoice in one embodiment. The user can scan the billing two-dimensional code through a mobile application (such as WeChat), and the step 1 is carried out: and entering an invoicing interface through an application (such as a WeChat invoicing applet) provided by the third-party agent equipment, and enabling a user to enter related information such as invoice head-up on the invoicing interface. Entering a step 2: and applying for making an invoice, uploading corresponding information to a block chain node in a block chain network through the third-party agent equipment by the application provided by the third-party agent equipment to generate an electronic bill, and feeding back the plaintext information of the corresponding electronic bill to the user. Entering a step 3: the user can receive the 'new ticket issue reminding' prompted by WeChat. Entering step 4, the user can insert the new ticket into the WeChat card package. And the WeChat server stores the received block chain electronic invoice for the user.

For KA tax enterprises, through opening the parking system, a user can scan a code through the mobile terminal, submit the head to raise the head and then invoice. Referring to fig. 11, fig. 11 is a schematic diagram of a circulation interface of a blockchain electronic invoice according to another embodiment. Steps 1-7 in fig. 11 particularly show the complete process of the user completing payment and collecting invoices issued by the billing enterprise through the mobile application (WeChat). Firstly, step 1, the enterprise where the parking lot is located can present the payment code, and the user can enter the payment interface by scanning the payment code through the mobile application. And then step 2 is entered, the user can bind the license plate number of the user and the invoice new head in the payment interface. And then, entering a step 3, calling the parking record of the vehicle corresponding to the license plate number of the user by the billing enterprise, and generating a payment link of corresponding money. Step 3.1, the user can view the corresponding details of the order to be paid. And 4, the user pays corresponding amount to the merchant. Step 5 is entered after payment is complete and the user can view the order details. The billing enterprise can upload invoice information in order details to block chain nodes in a block chain network to generate electronic bills and feed back plaintext information of the corresponding electronic bills to users. And step 6, the user can receive a new ticket issue prompt of the WeChat prompt. Proceeding to step 7, the user may insert a new ticket into the wechat card package. And the WeChat server stores the received block chain electronic invoice for the user.

And the second business scene is a catering charging scene.

For KA tax enterprises, through a free order system, users can make invoices by scanning codes, submitting heads up. Referring to fig. 12, fig. 12 is a schematic diagram of a circulation interface of a blockchain electronic invoice according to another embodiment. Steps 1-5 in fig. 12 particularly show the complete process of the user completing payment and collecting invoices issued by the billing enterprise through the mobile application (WeChat). Firstly, step 1, the billing enterprise can show the billing two-dimensional code in the order bill generated after the user pays, and the user can scan the billing two-dimensional code through the mobile application to enter a billing interface. And then, entering the step 2, and filling the invoice head-up and receipt information in the invoicing interface by the user. And then, entering a step 3, wherein the billing enterprise can upload the invoice information to the block chain nodes in the block chain network to generate the electronic bills and feed back the plaintext information of the corresponding electronic bills to the user. And 4, entering a step 4, wherein the user can receive a new ticket issue prompt of the WeChat prompt. Entering step 5, the user can insert the new ticket into the WeChat card package. And the WeChat server stores the received block chain electronic invoice for the user.

For small and medium-sized enterprises, block chain electronic invoices can be issued through third-party agent equipment. The third party proxy device may provide standard services such as providing an application for invoicing, and the user may log in to the application to fill out invoice information. Referring to fig. 13, fig. 13 shows a flow interface diagram of a blockchain electronic invoice in a further embodiment. Entering a step 1: the user may scan the billing application two-dimensional code provided by the third party agent device via a mobile application (such as WeChat) to access the billing applet. Entering a step 2: the user may enter the amount and type of goods in an invoicing interface provided by the invoicing application. Entering a step 3: the user can input related information such as invoice head-up and the like on an invoicing interface provided by the invoicing application. Entering a step 4: and applying for billing, and sending corresponding information to the merchant for confirmation by the application provided by the third-party agent equipment. And entering the step 5 and the step 6, and the merchant reviews the information related to the block chain electronic invoice. And uploading the invoice information to a block chain node in the block chain network through third-party proxy equipment after the invoice information passes the verification so as to generate an electronic bill, and feeding back the plaintext information of the corresponding electronic bill to the user. Entering a step 7: the user can receive the 'new ticket issue reminding' prompted by WeChat. Proceeding to step 8, the user may insert a new ticket into the wechat card package. And the WeChat server stores the received block chain electronic invoice for the user.

As shown in fig. 14, in one embodiment, there is provided an electronic ticket generating apparatus 1400 including: a receiving module 1401, a generating module 1402 and a feedback module 1403.

A receiving module 1401, configured to receive an invoicing request; the billing request carries bill information; the bill information includes an invoicing party identifier, an electronic bill identifier, a receiving party identifier and a resource transfer share.

And the generating module 1402 is configured to generate an electronic billing inquiry code corresponding to the billing information.

The generating module 1402 is further configured to generate an electronic ticket corresponding to the electronic ticket billing inquiry code according to the ticket information, and write the electronic ticket into the data block.

A feedback module 1403, configured to respond to the billing request and feed back the electronic bill billing query code; the electronic bill billing inquiry code is used for inquiring the electronic bill.

In one embodiment, the electronic ticket generating apparatus 1400 further comprises a determination module 1404.

The receiving module 1401 is further configured to receive an electronic ticket identifier receiving request; the electronic bill identification receiving request carries an identification of the invoicer.

A determining module 1404, configured to determine an electronic ticket identifier associated with the invoicer identifier and in an unused state in the blockchain node.

The feedback module 1403 is further configured to feed back the determined electronic ticket identity in response to the request for receiving the electronic ticket identity.

In one embodiment, the generating module 1402 is further configured to generate a ticket hash value according to the ticket information; sending the hash value of the bill to the invoicing party equipment corresponding to the invoicing party identification; the sent bill hash value is used for indicating the invoicing party equipment to sign the bill hash value to obtain signature data; receiving signature data returned by the invoicing party equipment; and when the signature data passes the verification, generating an electronic bill billing inquiry code according to the hash value of the bill and the signature data.

In one embodiment, the electronic ticket generating apparatus 1400 further comprises a query module 1405 and a validation module 1406.

A query module 1405 for querying the electronic ticket issuing conditions corresponding to the invoicer identification from the block link points.

The verification module 1406 is used for verifying the validity of the bill information according to the electronic bill making condition.

The generating module 1402 is further configured to generate an electronic ticket issuing inquiry code according to the hash value of the ticket and the signature data after the signature data passes the verification and the ticket information passes the verification.

Referring to fig. 15, in one embodiment, the electronic ticket generating apparatus 1400 further includes an encryption module 1407 and an acquisition module 1408.

The generating module 1402 is further configured to generate a ticket symmetric key corresponding to the ticket information.

And the encrypting module 1407 is configured to encrypt the ticket information with the ticket symmetric key to obtain a ticket cryptograph.

An obtaining module 1408, configured to obtain the public key of the invoicing party corresponding to the identifier of the invoicing party.

The encrypting module 1407 is further configured to encrypt the ticket symmetric key through the public key of the invoicing party to obtain a first ticket symmetric key ciphertext.

The generating module 1402 is further configured to generate an electronic ticket according to the ticket cryptograph, the first ticket symmetric key cryptograph, and the electronic ticket billing query code.

In one embodiment, the obtaining module 1408 is further configured to obtain a consumer identification corresponding to the ticket information; the query module is also used for searching a consumer public key corresponding to the consumer identifier; the encryption module is also used for encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext; the generating module is also used for generating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code.

The electronic bill generating device receives the billing request carrying the bill information through the block chain link points in the block chain network, wherein the bill information comprises a billing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share. And the block chain link points generate corresponding electronic bill billing inquiry codes according to the bill information, generate electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and write the electronic bills into the data block. And returning the electronic bill issuing inquiry code for inquiring the electronic bill so as to complete issuing the invoice on the block link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bills into the data blocks, so that the safety, reliability and reliability of the electronic bills can be guaranteed, and the authenticity of the electronic bill billing inquiry codes received by enterprises or individuals is further guaranteed.

As shown in fig. 16, in one embodiment, there is provided an electronic ticket generating apparatus 1600 including: an acquisition module 1601, a generation module 1602, an upload module 1603, and a reception module 1604.

An obtaining module 1601 is configured to obtain a receiver identifier and a resource transfer share.

The obtaining module 1601 is further configured to obtain an electronic ticket identifier associated with the current invoicer identifier.

The generating module 1602 is configured to generate the ticket information according to the identifier of the invoicing party, the identifier of the electronic ticket, the identifier of the receiving party, and the resource transfer share.

An upload module 1603, configured to upload the ticket information to a blockchain node in a blockchain network; and the uploaded bill information is used for indicating the block chain link points to generate electronic bill billing inquiry codes corresponding to the bill information, generating electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and writing the electronic bills into the data block.

The receiving module 1604 is configured to receive the electronic bill billing query code returned by the block chain node; the electronic bill billing inquiry code is used for inquiring the electronic bill.

In one embodiment, the obtaining module 1601 is further configured to send an electronic ticket identification acceptance request to the block link point; the request for receiving the electronic bill identification carries an identification of a biller; the electronic bill identification receiving request is used for indicating the block chain node to inquire the electronic bill identification which is associated with the invoicing party identification and is in an unused state; and receiving the electronic bill identification fed back by the block chain node.

Referring to FIG. 17, in one embodiment, the electronic ticket generating apparatus 1600 further includes a request initiation module 1605.

The receiving module 1604 is further configured to receive feedback information fed back by the block link point, where the feedback information indicates that the electronic ticket id associated with the invoicing party id and in the unused state is not queried.

A request initiating module 1605, configured to initiate an electronic bill identification claiming request to the electronic bill management server in response to the feedback information; the electronic bill identification claiming request is used for indicating the electronic bill management server to distribute the electronic bill identification according to the electronic bill claiming condition and uploading the distributed electronic bill identification and the invoicing party identification to the block chain node in a correlation manner.

In one embodiment, the generating module 1602 is further configured to query the block link points for the electronic ticket issuing conditions corresponding to the invoicer identifier; and generating bill information according to the inquired electronic bill making conditions and according to the bill making party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share.

The electronic bill generating device generates bill information according to the invoicing party identification, the electronic bill identification associated with the current invoicing party identification, the receiver identification and the resource transfer share. And uploading the bill information to block chain link points in a block chain network, generating an electronic bill making inquiry code corresponding to the bill information by the block chain link points, generating an electronic bill corresponding to the electronic bill making inquiry code according to the bill information, writing the electronic bill into a data block, and finally returning the electronic bill making inquiry code for inquiring the electronic bill so as to complete invoice making on the block chain link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

FIG. 18 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the invoicer device 110 in fig. 1. As shown in fig. 18, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement the electronic ticket generating method. The internal memory may also store a computer program that, when executed by the processor, causes the processor to execute the electronic ticket generating method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

FIG. 19 is a diagram showing an internal structure of a computer device in one embodiment. The computer device may specifically be block link point 120 in fig. 1. As shown in fig. 19, the computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement the electronic ticket generating method. The internal memory may also store a computer program that, when executed by the processor, causes the processor to execute the electronic ticket generating method.

It will be appreciated by those skilled in the art that the configurations shown in fig. 18 and 19 are only block diagrams of some configurations relevant to the present disclosure, and do not constitute a limitation on the computer device to which the present disclosure may be applied, and a particular computer device may include more or less components than those shown in the figures, or may combine some components, or have a different arrangement of components.

In one embodiment, the electronic ticket generating apparatus provided in the present application may be implemented in the form of a computer program that is executable on a computer device as shown in fig. 18 or fig. 19. The memory of the computer device may store various program modules constituting the electronic ticket generating apparatus, such as the receiving module, the generating module, and the feedback module shown in fig. 14. The computer program constituted by the respective program modules causes the processor to execute the steps in the electronic ticket generating method of the respective embodiments of the present application described in the present specification. Also for example, the acquiring module, the generating module, the uploading module and the receiving module shown in fig. 16. The computer program constituted by the respective program modules causes the processor to execute the steps in the electronic ticket generating method of the respective embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 18 may execute step S202 by the receiving module in the electronic ticket generating apparatus shown in fig. 12. The computer device may perform steps S204 and S206 by the generation module. The computer device may perform step S208 through the feedback module.

For example, the computer device shown in fig. 19 may execute steps S702 and S704 by the acquiring module in the electronic ticket generating apparatus shown in fig. 16. The computer device may perform step S706 through the generation module. The computer device may perform step S708 through the upload module. The computer device may perform step S710 through the receiving module.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: receiving a billing request; the billing request carries bill information; the bill information comprises an invoicing party identifier, an electronic bill identifier, a receiving party identifier and a resource transfer share; generating an electronic bill billing inquiry code corresponding to the bill information; generating an electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into the data block; responding to the billing request, and feeding back the billing inquiry code of the electronic bill; the electronic bill billing inquiry code is used for inquiring the electronic bill.

In one embodiment, the computer program causes the processor to further perform the steps of: receiving an electronic bill identification receiving request; the request for receiving the electronic bill identification carries an identification of a biller; determining an electronic bill identifier which is associated with the invoicer identifier and is in an unused state in the block chain node; and feeding back the determined electronic bill identification in response to the electronic bill identification receiving request.

In one embodiment, the computer program causes the processor, when executing the step of generating the electronic ticket issuing inquiry code corresponding to the ticket information, to specifically execute the following steps: generating a bill hash value according to the bill information; sending the hash value of the bill to the invoicing party equipment corresponding to the invoicing party identification; the sent bill hash value is used for indicating the invoicing party equipment to sign the bill hash value to obtain signature data; receiving signature data returned by the invoicing party equipment; and when the signature data passes the verification, generating an electronic bill billing inquiry code according to the hash value of the bill and the signature data.

In one embodiment, the computer program causes the processor to further perform the steps of: inquiring the electronic bill making conditions corresponding to the bill maker identification from the block chain nodes; and verifying the legality of the bill information according to the electronic bill issuing condition. The computer program causes the processor to specifically execute the following steps when executing the step of generating the electronic bill billing inquiry code according to the bill hash value and the signature data after the signature data passes the verification: and when the signature data passes the verification and the bill information passes the verification, generating an electronic bill billing inquiry code according to the hash value of the bill and the signature data.

In one embodiment, the computer program causes the processor to further perform the steps of: generating a bill symmetric key corresponding to the bill information; encrypting the bill information through the bill symmetric key to obtain a bill ciphertext; acquiring a public key of the invoicing party corresponding to the identifier of the invoicing party; and encrypting the bill symmetric key through the public key of the invoicing party to obtain a first bill symmetric key ciphertext. The computer program causes the processor to specifically execute the following steps when executing the step of generating the electronic bill corresponding to the electronic bill billing inquiry code according to the bill information: and generating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext and the electronic bill billing inquiry code.

In one embodiment, the computer program causes the processor to further perform the steps of: acquiring a consumer identifier corresponding to the bill information; searching a consumer public key corresponding to the consumer identification; and encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext. The computer program causes the processor to specifically execute the following steps when executing the step of generating the electronic bill corresponding to the electronic bill billing inquiry code according to the bill information: and generating the electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code.

The computer equipment receives the billing request carrying the bill information through the block chain link points in the block chain network, wherein the bill information comprises a billing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share. And the block chain link points generate corresponding electronic bill billing inquiry codes according to the bill information, generate electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and write the electronic bills into the data block. And returning the electronic bill issuing inquiry code for inquiring the electronic bill so as to complete issuing the invoice on the block link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: acquiring a receiver identifier and a resource transfer share; acquiring an electronic bill identifier associated with a current invoicer identifier; generating bill information according to the invoice party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share; uploading the bill information to a block chain node in a block chain network; the uploaded bill information is used for indicating the block link points to generate electronic bill making inquiry codes corresponding to the bill information, generating electronic bills corresponding to the electronic bill making inquiry codes according to the bill information, and writing the electronic bills into the data block; receiving an electronic bill billing inquiry code returned by the block chain node; the electronic bill billing inquiry code is used for inquiring the electronic bill.

In one embodiment, the computer program causes the processor in performing the step of obtaining an electronic ticket identity associated with the current invoicer identity to perform in particular the steps of: sending an electronic bill identification receiving request to the block link points; the request for receiving the electronic bill identification carries an identification of a biller; the electronic bill identification receiving request is used for indicating the block chain node to inquire the electronic bill identification which is associated with the invoicing party identification and is in an unused state; and receiving the electronic bill identification fed back by the block chain node.

In one embodiment, the computer program causes the processor to further perform the steps of: receiving feedback information fed back by the block chain link points, wherein the feedback information indicates that electronic bill identifications which are related to the invoicer identifications and are in an unused state are not inquired; responding to the feedback information, and initiating an electronic bill identification claiming request to an electronic bill management server; the electronic bill identification claiming request is used for indicating the electronic bill management server to distribute the electronic bill identification according to the electronic bill claiming condition and uploading the distributed electronic bill identification and the invoicing party identification to the block chain node in a correlation manner.

In one embodiment, the computer program causes the processor to perform the steps of generating ticket information based on the biller identification, the electronic ticket identification, the recipient identification, and the resource transfer share, in particular by: inquiring the electronic bill making conditions corresponding to the invoicing party identification from the block chain nodes; and generating bill information according to the inquired electronic bill making conditions and according to the bill making party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share.

The computer equipment generates bill information according to the invoicing party identification, the electronic bill identification associated with the current invoicing party identification, the receiver identification and the resource transfer share. And uploading the bill information to block chain link points in a block chain network, generating an electronic bill making inquiry code corresponding to the bill information by the block chain link points, generating an electronic bill corresponding to the electronic bill making inquiry code according to the bill information, writing the electronic bill into a data block, and finally returning the electronic bill making inquiry code for inquiring the electronic bill so as to complete invoice making on the block chain link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

A computer-readable storage medium storing a computer program which, when executed by a processor, performs the steps of: receiving a billing request; the billing request carries bill information; the bill information comprises an invoicing party identifier, an electronic bill identifier, a receiving party identifier and a resource transfer share; generating an electronic bill billing inquiry code corresponding to the bill information; generating an electronic bill corresponding to the electronic bill billing inquiry code according to the bill information, and writing the electronic bill into the data block; responding to the billing request, and feeding back the billing inquiry code of the electronic bill; the electronic bill billing inquiry code is used for inquiring the electronic bill.

The computer readable storage medium receives an invoicing request carrying bill information through a block chain link point in a block chain network, wherein the bill information comprises an invoicing party identifier, an electronic bill identifier, a receiver identifier and a resource transfer share. And the block chain link points generate corresponding electronic bill billing inquiry codes according to the bill information, generate electronic bills corresponding to the electronic bill billing inquiry codes according to the bill information, and write the electronic bills into the data block. And returning the electronic bill issuing inquiry code for inquiring the electronic bill so as to complete issuing the invoice on the block link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

A computer-readable storage medium storing a computer program which, when executed by a processor, performs the steps of: acquiring a receiver identifier and a resource transfer share; acquiring an electronic bill identifier associated with a current invoicer identifier; generating bill information according to the invoice party identifier, the electronic bill identifier, the receiver identifier and the resource transfer share; uploading the bill information to a block chain node in a block chain network; the uploaded bill information is used for indicating the block link points to generate electronic bill making inquiry codes corresponding to the bill information, generating electronic bills corresponding to the electronic bill making inquiry codes according to the bill information, and writing the electronic bills into the data block; receiving an electronic bill billing inquiry code returned by the block chain node; the electronic bill billing inquiry code is used for inquiring the electronic bill.

The computer-readable storage medium generates the bill information according to the invoicer identifier, the electronic bill identifier associated with the current invoicer identifier, the receiver identifier, and the resource transfer share. And uploading the bill information to block chain link points in a block chain network, generating an electronic bill making inquiry code corresponding to the bill information by the block chain link points, generating an electronic bill corresponding to the electronic bill making inquiry code according to the bill information, writing the electronic bill into a data block, and finally returning the electronic bill making inquiry code for inquiring the electronic bill so as to complete invoice making on the block chain link points. Therefore, enterprises or individuals only need to upload bill information to the block chain nodes in the block chain network, invoicing of invoices is completed through the block chain nodes, the enterprises or the individuals do not need to purchase special tax control equipment, and paper file invoices do not need to be invoiced, the cost of invoicing is greatly reduced, and the efficiency of invoicing is improved. In addition, the block link points write the electronic bill into the data block, so that the safety and reliability of the electronic bill can be guaranteed, and the authenticity of the electronic bill billing inquiry code received by an enterprise or an individual is further guaranteed.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. An electronic bill generation method applied to a blockchain node in a blockchain network, the method comprising:

encrypting the bill information through a bill symmetric key to obtain a bill ciphertext;

encrypting the bill symmetric key through the public key of the invoicing party corresponding to the invoicing party identification to obtain a first bill symmetric key ciphertext;

acquiring a consumer identifier corresponding to the bill information, and searching a consumer public key corresponding to the consumer identifier; the consumer public key is obtained by generating a secret key pair corresponding to the registered consumer identifier through an electronic bill public server and disclosing the consumer public key in the secret key pair;

encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext;

generating a bill hash value according to the bill ciphertext, and sending the bill hash value to the invoicing party equipment corresponding to the invoicing party identifier; the sent bill hash value is used for indicating the invoicing party equipment to sign the bill hash value to obtain signature data;

receiving the signature data returned by the invoicing party equipment, and generating an electronic bill invoicing inquiry code according to the hash value of the bill and the signature data after the signature data passes verification;

generating an electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code, and writing the electronic bill into a data block;

responding to the billing request, and feeding back the electronic bill billing inquiry code; the electronic bill billing inquiry code is used for inquiring the electronic bill; when inquiring the electronic bill, the invoicing party initiating the invoicing request decrypts the electronic bill by an invoicing party private key corresponding to the invoicing party identifier to obtain the bill information; and when the terminal corresponding to the consumer identification inquires the electronic bill, decrypting the electronic bill through a consumer private key corresponding to the consumer identification to obtain the bill information.

2. The method of claim 1, further comprising:

receiving an electronic bill identification receiving request; the electronic bill identification receiving request carries an identifier of a biller;

determining an electronic bill identifier which is associated with the invoicer identifier and is in an unused state in the blockchain node;

and responding to the electronic bill identification receiving request, and feeding back the determined electronic bill identification.

3. The method according to claim 2, wherein after the feeding back the determined electronic ticket identity in response to the request for getting the electronic ticket identity, the method further comprises:

and after the electronic bill in the unused state is fed back to the invoicing party initiating the electronic bill identification receiving request, marking the bill state of the electronic bill identification as the used state.

4. The method of claim 1, wherein the billing request carries billing information and a billing signature corresponding to the billing information; the billing signature is obtained by encrypting the billing information through a private key of the billing party corresponding to the billing party identifier; after receiving the billing request, the method further comprises:

acquiring a public key of the invoicing party corresponding to the identifier of the invoicing party;

verifying the invoicing signature through the public key of the invoicing party;

and after the billing signature passes the verification, executing the bill information encrypted by the bill symmetric key to obtain a bill ciphertext.

5. The method of claim 1, further comprising:

inquiring an electronic bill making condition corresponding to the invoicing party identifier from the block chain node;

verifying the legality of the bill information according to the electronic bill making condition;

after the signature data passes verification, generating an electronic bill billing inquiry code according to the bill hash value and the signature data, wherein the method comprises the following steps:

and when the signature data passes the verification and the bill information passes the verification, generating an electronic bill billing inquiry code according to the bill hash value and the signature data.

6. The method of claim 1, further comprising:

generating a consumer private key and a consumer public key corresponding to the consumer identification through the electronic bill public server;

receiving the consumer identification and the corresponding consumer public key transmitted by the electronic bill public server;

and storing the consumer identification and the corresponding consumer public key in an associated manner.

7. The method according to any one of claims 1 to 6, wherein the electronic ticket is a blockchain electronic invoice; the electronic bill identification is a block chain electronic invoice number; the invoicing party identification is an enterprise identification.

8. An electronic ticket generating apparatus comprising:

the encryption module is used for encrypting the bill information through a bill symmetric key to obtain a bill ciphertext;

the encryption module is also used for encrypting the bill symmetric key through the public key of the invoicing party corresponding to the invoicing party identification to obtain a first bill symmetric key ciphertext;

the acquisition module is used for acquiring the consumer identification corresponding to the bill information and searching the consumer public key corresponding to the consumer identification; the consumer public key generates a secret key pair corresponding to the logged-in consumer identifier through an electronic bill public server, and the public key of the consumer in the secret key pair is obtained after being published; encrypting the bill symmetric key through the consumer public key to obtain a second bill symmetric key ciphertext;

the generating module is used for generating a bill hash value according to the bill ciphertext and sending the bill hash value to the invoicing party equipment corresponding to the invoicing party identifier; the sent bill hash value is used for indicating the invoicing party equipment to sign the bill hash value to obtain signature data; receiving the signature data returned by the invoicing party equipment, and generating an electronic bill invoicing inquiry code according to the hash value of the bill and the signature data after the signature data passes verification;

the generating module is further used for generating an electronic bill according to the bill ciphertext, the first bill symmetric key ciphertext, the second bill symmetric key ciphertext and the electronic bill billing inquiry code, and writing the electronic bill into a data block;

the feedback module is used for responding to the billing request and feeding back the electronic bill billing inquiry code; the electronic bill billing inquiry code is used for inquiring the electronic bill; when inquiring the electronic bill, the invoicing party initiating the invoicing request decrypts the electronic bill by an invoicing party private key corresponding to the invoicing party identifier to obtain the bill information; and when the terminal corresponding to the consumer identification inquires the electronic bill, decrypting the electronic bill through a consumer private key corresponding to the consumer identification to obtain the bill information.

9. The apparatus of claim 8, further comprising:

the receiving module is also used for receiving the electronic bill identification receiving request; the electronic bill identification receiving request carries an identifier of a biller;

the determining module is used for determining the electronic bill identification which is associated with the invoicing party identification and is in an unused state in the block chain node;

the feedback module is also used for responding to the electronic bill identification receiving request and feeding back the determined electronic bill identification.

10. The apparatus of claim 9, wherein the determining module is further configured to mark the ticket status of the electronic ticket identifier as used after feeding back the electronic ticket in the unused state to the invoicing party who initiated the request for accepting the electronic ticket identifier.

11. The apparatus of claim 8, wherein the billing request carries billing information and a billing signature corresponding to the billing information; the billing signature is obtained by encrypting the billing information through a private key of the billing party corresponding to the billing party identifier;

the obtaining module is further used for obtaining the public key of the invoicing party corresponding to the invoicing party identifier;

the verification module is used for verifying the invoicing signature through the public key of the invoicing party; and after the billing signature passes the verification, executing the bill information encrypted by the bill symmetric key to obtain a bill ciphertext.

12. The apparatus of claim 8, further comprising:

the query module is used for querying the electronic bill making conditions corresponding to the invoicing party identification from the block chain nodes in the block chain network;

the verification module is used for verifying the legality of the bill information according to the electronic bill making condition;

and the generation module is also used for generating an electronic bill billing inquiry code according to the bill hash value and the signature data after the signature data passes verification and the bill information passes verification.

13. The apparatus of claim 8, wherein the generating module is further configured to generate a consumer private key and a consumer public key corresponding to the consumer identifier through the electronic ticket public server;

the receiving module is further configured to receive the consumer identifier and the corresponding consumer public key transmitted by the electronic ticket public server, and store the consumer identifier and the corresponding consumer public key in an associated manner.

14. The apparatus according to any one of claims 8-13, wherein the electronic ticket is a blockchain electronic invoice; the electronic bill identification is a block chain electronic invoice number; the invoicing party identification is an enterprise identification.

15. A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 7.

16. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 7.