CN108961030B

CN108961030B - Data processing method, apparatus, system, medium, and device for electronic ticket

Info

Publication number: CN108961030B
Application number: CN201810927658.5A
Authority: CN
Inventors: 蔡弋戈; 秦青; 戴传兵; 张建俊; 郑罗海; 卢吉光; 王宗友; 屠海涛; 周开班; 蓝虎
Original assignee: Shenzhen Zhishuilian Technology Co ltd
Current assignee: Shenzhen Zhishuilian Technology Co ltd
Priority date: 2018-08-15
Filing date: 2018-08-15
Publication date: 2023-01-03
Anticipated expiration: 2038-08-15
Also published as: CN108961030A

Abstract

The invention relates to a data processing method, a device, a system, a medium and equipment about electronic bills, wherein the method comprises the following steps: acquiring characteristic data of the invoicer associated with the identifier of the invoicer; setting an electronic bill making condition corresponding to the invoicer identification according to the invoicer characteristic data; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier; correspondingly uploading the electronic bill making conditions and the invoicing party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the invoicer identifications into a data block in an associated manner. The scheme provided by the application improves the electronic bill issuing efficiency.

Description

Data processing method, apparatus, system, medium, and device for electronic ticket

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, a medium, and a device for processing data regarding electronic tickets.

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.

In the traditional technology, tax staff or individuals with tax processing qualification of enterprises need to frequently go to a tax bureau and manually agree invoicing conditions with tax bureau staff, so that the time and labor are consumed, and the invoicing efficiency is greatly influenced.

Disclosure of Invention

In view of the above, it is necessary to provide a data processing method, apparatus, system, medium, and device for electronic tickets, which address the problem of relatively low invoicing efficiency.

A data processing method relating to an electronic ticket, comprising:

acquiring characteristic data of the invoicer associated with the identifier of the invoicer;

setting an electronic bill making condition corresponding to the invoicer identification according to the invoicer characteristic data; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier;

correspondingly uploading the electronic bill making conditions and the invoicing party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the invoicer identifications into a data block in an associated manner.

A data processing apparatus relating to electronic tickets, comprising:

the obtaining module is used for obtaining invoicing party characteristic data associated with the invoicing party identifier;

the setting module is used for setting an electronic bill making condition corresponding to the invoicing party identifier according to the invoicing party characteristic data; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier;

the chaining module is used for correspondingly uploading the electronic bill making conditions and the invoicing party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the corresponding uploaded invoicer identifications into a data block in an associated manner.

A data processing system related to electronic bills comprises an electronic bill management server and a block link point; wherein,

the electronic bill management server is used for acquiring characteristic data of the invoicers related to the invoicer identifications; setting an electronic bill making condition corresponding to the invoicer identification according to the invoicer characteristic data; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier; correspondingly uploading the electronic bill making conditions and the invoicing party identifier to a block chain node;

and the block chain node is used for writing the corresponding uploaded electronic bill making conditions and the invoicing party identification into a data block in an associated manner.

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of:

acquiring characteristic data of the invoicer associated with the invoicer identifier;

correspondingly uploading the electronic bill making conditions and the invoicing party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the corresponding uploaded invoicer identifications into a data block in an associated manner.

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:

setting an electronic bill making condition corresponding to the invoicer identification according to the invoicer characteristic data; the electronic bill making conditions corresponding to the invoicing party identification are used for controlling electronic bill making actions carried out through the invoicing party identification;

According to the data processing method, device, system, storage medium and equipment for the electronic bill, the characteristic data of the invoicing party associated with the invoicing party identifier is automatically acquired, the electronic bill making condition corresponding to the invoicing party identifier can be set according to the characteristic data of the invoicing party, the electronic bill making condition corresponds to the invoicing party identifier and is linked up, the electronic bill making behavior through the invoicing party identifier is controlled based on the block chain, and time consumption and labor consumption caused by the fact that the electronic bill making condition needs to be frequently and manually agreed are avoided. In addition, the block link points write the electronic bill issuing conditions into the data blocks, so that the data security and the tamper resistance of the electronic bill issuing conditions can be guaranteed.

Drawings

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

FIG. 2 is a flow diagram of a method of data processing with respect to electronic tickets in one embodiment;

FIG. 3 is a diagram of an electronic ticket issuing conditions setting interface in one embodiment;

FIG. 4 is a timing diagram of chain for electronic ticket issuing conditions in one embodiment;

FIG. 5 is a timing diagram illustrating updating of the billing conditions of an electronic ticket in one embodiment;

FIG. 6 is a schematic illustration of a consensus algorithm in one embodiment;

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

FIG. 8 is a block diagram of a data processing apparatus relating to an electronic ticket in one embodiment;

FIG. 9 is a diagram showing an internal structure of a computer device in one embodiment;

fig. 10 is an internal structural diagram of a computer device in another embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in 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 invention and do not limit the invention.

Fig. 1 is a diagram of an application environment of a data processing method for an electronic ticket in one embodiment. Referring to fig. 1, the data processing method for electronic tickets is applied to a data processing system for electronic tickets. The data processing system on electronic tickets includes an electronic ticket management terminal 110, an electronic ticket management server 120, a biller device 130, and a block link point 140. The number of the block link points 140 is plural and is located in the block chain network. And data can be transmitted between every two block chain nodes. The invoicer device 130 may be a terminal or a server. The invoicing party device can be a device owned by the invoicing party or a third party agent device authorized by the invoicing party to act for issuing the electronic bill.

Specifically, the electronic ticket management server 120 may obtain invoicer feature data associated with the invoicer identification; setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action through the invoicing party identifier. The electronic bill management server 120 then uploads the electronic bill making conditions and the invoicer identifier to the blockchain node 140 correspondingly. The block chain node 140 writes the corresponding uploaded electronic bill making conditions and the invoicer identifier into the data block in an associated manner. In this way, the invoicer device 130 can subsequently inquire the electronic ticket issuing conditions corresponding to the invoicer id from the block link point 140 to issue the electronic ticket according to the electronic ticket issuing conditions, and initiate an electronic ticket issuing condition updating request to request the electronic ticket managing server 120 to update the electronic ticket issuing conditions when the electronic ticket issuing conditions are not applicable.

In further embodiments, the electronic ticket management terminal 110 may also obtain invoicer feature data associated with the invoicer identification; setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action through the invoicing party identifier. The electronic bill management terminal 110 uploads the electronic bill making conditions corresponding to the invoicing party identifier to the electronic bill management server 120, and the electronic bill management server 120 uploads the electronic bill making conditions corresponding to the invoicing party identifier to the block chain node 140. The block chain node 140 writes the corresponding uploaded electronic bill making conditions and the invoicer identifier into the data block in an associated manner.

In a specific application scenario, the electronic bill may specifically be a block chain electronic invoice, the electronic bill management terminal 110 may specifically be a terminal operated by a staff in a tax office, the electronic bill management server 120 may specifically be a server in the tax office, and the invoicing party device 130 may specifically be a terminal or a server corresponding to an invoicing party. It can be understood that the invoicer can be used as an electronic bill invoicer to make an electronic bill and can also be used as an electronic bill reporter to reimburse the electronic bill. 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 specifically be an independent server, or may be a server cluster formed by a plurality of independent servers.

Fig. 2 is a flow chart illustrating a data processing method for an electronic ticket according to an embodiment. The present embodiment is mainly exemplified by applying the data processing method for electronic tickets to the electronic ticket management server 120 shown in fig. 1. Referring to fig. 2, the method specifically includes the following steps:

s202, acquiring invoicer characteristic data associated with the invoicer identifier.

The invoicing party identifier is used for uniquely identifying one invoicing party. The invoicing party is any user who successfully registers legal invoicing authority in the electronic bill management server. The user may specifically be an enterprise user. It can be understood that the invoicing party can be used as an invoicing party of the electronic bill to make an electronic bill and can be used as an invoicing party of the electronic bill to reimburse the electronic bill. Then, the invoicing party can also be the ticket reporting party; the invoicing party identifier can also be an invoicing party identifier. An electronic ticket is a ticket that is stored electronically, such as may be stored in a storage medium or computer device.

In one embodiment, the invoicer identification is data associated with the invoicer. 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.

In one embodiment, the identifier of the invoicing party may be a unique identifier assigned to the invoicing party by the electronic ticket management server after the invoicing party successfully registers the legal invoicing authority. In this way, the electronic bill management server can store the data related to the invoicer and the unique identifier allocated to the invoicer when the data is stored so as to indicate which data is the data related to which invoicer.

Wherein the characteristic data of the invoicer is data reflecting the characteristics of the invoicer. The invoicer characteristic data may specifically include invoicer basic data and/or invoicer behavior data. The invoicer basic data is data reflecting basic characteristics of the invoicer, such as a business name, a business type or a business operation range. The invoicing party behavior data is data reflecting the behavior characteristics of the invoicing party, such as invoicing behavior data or tax return behavior data.

It will be appreciated that whether the invoicer profile data includes invoicer behaviour data is relevant to the current time node. When the invoicer has not performed the behavior related to the electronic ticket, the invoicer feature data does not include the invoicer behavior data. Here, the invoicing party has not performed the action related to the electronic ticket, and is not limited to the action related to the electronic ticket performed after the legal invoicing authority is successfully registered in the electronic ticket management server, and may include the action related to the paper ticket performed by the invoicing party, or the action performed after the invoicing authority is successfully registered in another server by the invoicing party.

In one embodiment, the invoicer profile includes invoicer base data. S202 comprises the following steps: inquiring registration data corresponding to the invoicer identification; and extracting basic data of the invoicers from the inquired registration data.

The registration data is formed when the invoicing party successfully registers in the electronic bill management server. When the invoicer registers, the electronic bill management server acquires the basic data of the invoicer, thereby forming registration data. Therefore, after the electronic bill management server finishes registering the invoicer, the basic data of the invoicer can be automatically extracted from the registration data, and the electronic bill making conditions can be set for the invoicer subsequently according to the basic data of the invoicer so as to control the electronic bill making action performed by the invoicer.

In one embodiment, the invoicer base data is not fixed, unchanging data. Then, setting the electronic-bill issuing conditions according to the invoicer basic data is not fixed. The electronic bill management server can flexibly adjust the electronic bill making conditions when the basic data of the bill making party is changed.

It is understood that the invoicer may request the electronic ticket management server to update the registration data when the invoicer basic data is changed. The electronic bill management server can also actively update the registration data of the invoicers according to the information reported by the electronic bill management terminal. Such as the invoicer expanding the operation range or changing the operation type, etc. Therefore, the electronic bill management server can flexibly set the electronic bill making conditions suitable for the invoicer according to the changed basic data of the invoicer, thereby ensuring the normal operation of making the bill and improving the billing efficiency.

Of course, when the variation range of the basic data of the invoicing party is small, the electronic bill management server does not need to update the electronic bill making conditions corresponding to the invoicing party identification.

In one embodiment, the invoicer feature data further includes invoicer behavior data. S202 comprises the following steps: inquiring the behavior data of the invoicers corresponding to the invoicer identifications from the block chain nodes; or acquiring the invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification.

It can be understood that after the invoicing party registers on the electronic bill management server, the data related to the electronic bill related action performed by the invoicing party can be written into the blockchain node. Therefore, the electronic bill management server can inquire data corresponding to the invoicer identification in the block chain node to obtain the invoicer behavior data.

The enforcement party identifier is used to uniquely identify an enforcement party. The law enforcement party here may be a relevant law enforcement agency such as a regulatory agency. It can be understood that the related law enforcement departments can actively collect the behavior data of the invoicing party corresponding to the invoicing party identifier and transmit the collected behavior data of the invoicing party corresponding to the invoicing party identifier to the electronic bill management server; and the behavior data of the invoicing party corresponding to the invoicing party identifier reported by the user can be received, and the received behavior data of the invoicing party corresponding to the invoicing party identifier is transmitted to the electronic bill management server.

For example, the tax administration and supervision department may actively check invoicing information or tax payment information of each enterprise user, and may also receive invoicing and tax payment related information of the enterprise users reported by the masses, such as information that the invoicing enterprise reported by the masses issues a false invoice or does not pay tax due to overdue.

The data can be transmitted to the electronic bill management server after verification through law enforcement party identification, or can be directly transmitted to the electronic bill management server to request verification.

In this embodiment, the invoicer behavior data corresponding to the invoicer identifier is acquired from the block link point or the law enforcement party, so that the credibility of the behavior data source is ensured, and then the electronic bill issuing conditions corresponding to the invoicer identifier can be set according to the credible data.

S204, setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer; and the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action through the invoicing party identifier.

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 control period is a time period for controlling the electronic bill making data, such as one or more of natural days, natural weeks, natural months, natural years, and the like. 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, the electronic bill management server may set an electronic bill issuing condition corresponding to the maker identification according to the maker characteristic data. The setting here may be a first setting or a second setting.

It can be understood that the electronic bill management server can respond to the request of the invoicer or automatically set the electronic bill making conditions corresponding to the invoicer identification according to the basic data of the invoicer when the invoicer is successfully registered, namely, the electronic bill making conditions corresponding to the invoicer identification are set for the first time. After that, when the basic data of the invoicer is changed, the electronic bill management server can respond to the request of the invoicer or automatically reset the electronic bill making conditions corresponding to the identifier of the invoicer according to the updated basic data of the invoicer, namely, the electronic bill making conditions corresponding to the identifier of the invoicer are reset again. Similarly, the electronic ticket management server may reset the electronic ticket issuing conditions corresponding to the biller identification in response to a request of the biller or automatically according to the updated biller behavior data after the biller generates the behavior data, and here, the electronic ticket issuing conditions corresponding to the biller identification are also reset. That is, when the characteristic data of the invoicing party is changed, the electronic bill management server can flexibly set the electronic bill making conditions suitable for the invoicing party according to the changed characteristic data of the invoicing party.

In one embodiment, the electronic bill making conditions include an electronic bill making control period, a single-period electronic bill making amount limit, and a single electronic bill making amount limit; the electronic bill is a block chain electronic invoice.

Specifically, the electronic bill making quantity limit in a single period is the maximum electronic bill making quantity in one electronic bill making control period. The single-period electronic bill making amount is the maximum amount that can be made in one electronic bill making control period. The single electronic bill is the maximum invocable amount of an electronic bill.

In one embodiment, the electronic bill making condition further comprises a single-cycle electronic bill revocation quantity limit and a single-cycle electronic bill revocation amount limit. It will be appreciated that there may be situations where an error occurs in the invoicing party in the issuing of an electronic ticket. In this case, the invoicing party can issue an electronic ticket of the amount opposite to the wrong electronic ticket for canceling the wrong electronic ticket and additionally issue a correct electronic ticket.

In the above embodiment, the specific values of the single-cycle electronic bill making amount limit, the single-cycle electronic bill making amount limit and the single-electronic bill making amount limit can be all accurate to the minimum allowable digit.

For example, fig. 3 shows a schematic diagram of an electronic ticket issuing conditions setting interface in one embodiment. Referring to fig. 3, the electronic ticket management terminal may display an electronic ticket issuing condition setting interface as shown in fig. 3 after logging in a client or a web page provided by the electronic ticket management server through an administrator identification, and acquire an electronic ticket issuing condition set in the interface. It will be appreciated that the interface diagram shown in fig. 3 is for illustration only, and that an interface diagram particularly useful in an actual scenario may include more or less than that shown in fig. 3.

S206, correspondingly uploading the electronic bill making conditions and the bill making party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block in an associated manner.

Wherein, the block chain node is a data processing node in the block chain 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 decentralization and public transparency, so that everyone can participate in data recording. The blockchain technology is a brand new distributed infrastructure and computing approach that utilizes blockchain data structures to authenticate and store data, distributed node consensus algorithms to generate and update data, cryptography to secure data transmission and access, and intelligent contracts composed of automated script code to program and manipulate data.

Specifically, the electronic bill management server can correspondingly upload the electronic bill making conditions and the bill making party identification to the block chain node. After receiving the corresponding uploaded electronic bill making conditions and the invoice party identification, the block chain node can transmit the electronic bill making conditions and the invoice party identification to other block chain nodes in the block chain network. After the block chain nodes are identified together, the block chain node receiving the data uploaded by the electronic bill management server can associate the electronic bill making conditions with the bill making party identifier and write the electronic bill making conditions and the bill making party identifier into the data block. And associating the electronic bill issuing condition written into the data block with the invoicer identifier, wherein the electronic bill issuing action performed by the invoicer identifier is restricted by the electronic bill issuing condition.

The block chain link points of the data uploaded by the electronic bill management server can be block chain nodes corresponding to the electronic bill management server one to one. In other embodiments, the block link point where the electronic bill management server uploads data may also correspond to a device in another authority role. It can be understood that the electronic ticket management server may also be used as a node in the block chain, and the uploading of the electronic ticket issuing condition and the invoicing party identifier to the block chain node correspondingly may refer to uploading the electronic ticket issuing condition and the invoicing party identifier to another node in the block chain except the electronic ticket management server, or uploading the electronic ticket issuing condition and the invoicing party identifier to an arbitrary node in the block chain correspondingly. The invoicer device may also be a node in the block chain.

It can be understood that when the block link point where the electronic bill management server uploads the data is also the block link node corresponding to the invoicing party identifier, the invoicing party device directly queries the electronic bill making condition corresponding to the invoicing party identifier from the block link node when the electronic bill is required to be made, so as to make the electronic bill according to the electronic bill making condition.

When the block link point of the data uploaded by the electronic bill management server is not the block link node corresponding to the invoicing party identifier, the invoicing condition corresponding to the invoicing party identifier and the invoicing party identifier are associated and written into the data block after the consensus of the block link point of the invoicing party identifier is completed, and when the invoicing equipment needs to issue the electronic bill, the invoicing condition corresponding to the invoicing party identifier can be inquired from the invoicing party block link node to issue the electronic bill according to the electronic bill issuing condition.

According to the data processing method of the electronic bill, the characteristic data of the invoicing party associated with the invoicing party identifier is automatically acquired, the electronic bill making condition corresponding to the invoicing party identifier can be set according to the characteristic data of the invoicing party, the electronic bill making condition and the invoicing party identifier are correspondingly linked, the electronic bill making action performed through the invoicing party identifier is controlled based on the block chain, and time consumption and labor consumption caused by the fact that the electronic bill making condition needs to be frequently and manually agreed are avoided. In addition, the block link points write the electronic bill issuing conditions into the data blocks, so that the data security and the tamper resistance of the electronic bill issuing conditions can be guaranteed.

It should be noted that, the process of setting the electronic ticket issuing condition in the above embodiment may be a process of setting the electronic ticket issuing condition for the first time; or may be a process of setting the electronic ticket issuing condition again, that is, updating the electronic ticket issuing condition. The step of setting the electronic ticket issuing condition in the above embodiment may be a step executed by the electronic ticket management terminal; or steps performed by the electronic ticket management server.

For example, fig. 4 shows a timing diagram of the chain for electronic ticket issuing conditions in one embodiment. Referring to fig. 4, in a specific application scenario, the hardware devices involved in the timing diagram include a tax office terminal, a tax office server, and a blockchain node. The tax office terminal may receive the electronic ticket issuing condition set at the interface as shown in fig. 3, which may be specifically set according to the base data of the issuing party. The tax office terminal can upload the electronic bill making conditions to the tax office server. And the tax bureau server sends an electronic bill making condition chaining request to the block chain node, and after receiving an uploading-allowed response message fed back by the block chain node, the tax bureau server uploads the electronic bill making condition and the invoice maker identification signature which need to be uploaded correspondingly to the block chain node after using a tax bureau key. And after the block chain node completes the consensus on the uploaded data by other block chain link points in the joint block chain network, feeding back a response message of successful uplink.

Fig. 5 is a timing diagram of updating of electronic ticket issuing conditions in one embodiment. Referring to fig. 5, in a specific application scenario, the hardware devices involved in the timing diagram include a tax office terminal, a tax office server, and a blockchain node. And after the tax office terminal logs in through the tax office manager identifier, a user authority verification request can be sent to the tax office server. And after the authority verification is completed, the tax bureau server can feed back a response message passing the verification. And the tax office terminal then initiates a request for inquiring the behavior characteristic data of the invoicing party to the tax office server. The tax office server inquires the electronic bill corresponding to the invoicing party identifier from the block chain node, forms invoicing party behavior data and feeds the data back to the tax office terminal, and the tax office terminal can update the electronic bill making condition according to the invoicing party behavior data. The tax bureau terminal can upload the updated electronic bill making conditions to the tax bureau server. And the tax bureau server sends an electronic bill making condition chaining request to the block chain node, and after receiving an uploading-allowed response message fed back by the block chain node, the tax bureau server uploads the electronic bill making condition and the invoice maker identification signature which need to be uploaded correspondingly to the block chain node after using a tax bureau key. And after the block chain node completes the consensus on the uploaded data by other block chain link points in the joint block chain network, feeding back a response message of successful uplink.

It can be understood that, in the embodiment of the present invention, each authority role participating in the data processing method related to the electronic ticket corresponds to an identity key, and the identity keys are generated and issued by the electronic ticket management server. Moreover, the electronic ticket management server is only allowed to chain the electronic ticket identity. When data is transmitted, each authority role can use a private key in the identity key of the authority role to sign so as to prove the identity, and a data receiver uses a public key in the identity key of the data transmitter to verify the identity of the data transmitter.

In one embodiment, the identity key corresponding to each authority role is not fixed. The electronic bill management server can regularly generate new identity keys for all the roles again, and potential data safety hazards caused by key loss are avoided as much as possible. And each authority role can also apply for key replacement to the electronic bill management server in time after the key is lost.

In one embodiment, the setting of the electronic bill issuing condition corresponding to the invoicer identification according to the invoicer characteristic data comprises the following steps: and when the behavior data of the invoicing party comprises the information loss behavior data, updating the electronic bill making conditions corresponding to the identifier of the invoicing party according to the information loss behavior data.

Wherein the credit loss behavior data is behavior data that negatively affects credit. For example, the credit loss behavior data (behavior data for reducing credit) is as follows: "owing tax payment" or "making false electronic bill", etc.

In one embodiment, updating the electronic ticket issuing conditions corresponding to the invoicer identification according to the trust loss behavior data comprises the following steps: when the act of losing credit data is act of making out a bill and losing credit, narrowing down the electronic bill making condition corresponding to the identifier of the party making out the bill according to the act of making out a bill and losing credit data; and when the losing behavior data is tax return losing behavior data, canceling the electronic bill making condition corresponding to the invoicing party identifier according to the tax return losing behavior data.

It can be understood that when the invoicing party has the credit loss behavior data, the invoicing party has the behavior of reducing the credit and even has the illegal or illegal behavior. At the moment, the electronic bill management server can restrict the trust loss of the invoicer by updating the electronic bill issuing conditions so as to avoid the trust loss or illegal behaviors. For example, when the invoicing party has false invoicing behavior, the electronic bill issuing conditions corresponding to the invoicing party identification can be limited, so that the invoicing party cannot issue a large number of electronic bills. For another example, when the invoicer has the behavior of paying no tax due, the electronic bill making condition corresponding to the invoicer identifier is cancelled, so that the invoicer cannot make an electronic bill.

Of course, when the event of the act of losing credit of the invoicing act data is serious, the electronic bill management server can also cancel the electronic bill issuing condition corresponding to the identifier of the invoicing party.

In one embodiment, when the invoicing party loses credit, such as fraud or tax evasion, the electronic bill management server can set the state of the invoicing party corresponding to the invoicing party identifier as an abnormal state, and upload the abnormal state to the blockchain node to be written into the blockchain network so as to inform other authority roles participating in the data processing method related to the electronic bill that the invoicing party has credit problems.

In the embodiment, when the invoicing party loses credit, the electronic bill issuing condition of the invoicing party is flexibly adjusted according to the credit losing behavior of the invoicing party so as to restrict and stop the credit losing behavior of the invoicing party as much as possible and avoid illegal behaviors.

In one embodiment, uploading the electronic bill making conditions and the corresponding invoice party identification to the blockchain node comprises: correspondingly uploading the electronic bill making conditions and the bill making party identification to the block link points corresponding to the local place; the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block chain link points corresponding to the local area, transmitting the electronic bill making conditions and the invoicer identifications to other block chain nodes in the block chain, and writing the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block after consensus is completed; and the electronic bill issuing condition and the invoicer identifier which are uploaded correspondingly are used for indicating the invoicer block chain node to write the transferred electronic bill issuing condition and the invoicer identifier into the data block in a correlation way after the consensus is finished.

Specifically, the electronic ticket management server may correspond to the existence of a dedicated blockchain node. When the electronic bill management server intends to write data into the block chain network, the data can be directly transmitted to the block chain link points through the interfaces provided by the special block chain link points, and the data is written into the data block after the block chain link points are identified with other block chain link points in the block chain nodes.

Similarly, the invoicer device may also have a dedicated blockchain node. When the invoicing side equipment intends to read data from the block chain network, the inquiry request can be directly transmitted to the invoicing side block chain point through an interface provided by the special invoicing side block chain point, and the invoicing side block chain node feeds the inquiry result back to the invoicing side equipment after verifying the identity of the invoicing side.

It can be understood that the electronic bill management server uploads the data associated with the invoicing party to the corresponding block link point for the first time, the block link point cooperates with other block link nodes to achieve consensus, then the data associated with the invoicing party is written into the data block, and the block link point corresponding to the invoicing party device also writes the data associated with the invoicing party into the data block, so that the block link point corresponding to the electronic bill management server, that is, the block link point corresponding to the invoicing party device, forms a block chain. It should be noted that different block chain links are formed by the block chain link points corresponding to different invoicing side devices and the block chain link points corresponding to the electronic bill management server, and the different block chains can operate independently without mutual influence.

Specifically, the electronic bill management server correspondingly uploads the electronic bill making conditions and the invoicing party identifier to the block link point corresponding to the electronic bill management server, that is, the electronic bill making conditions and the invoicing party identifier are associated and written into the data block in the block chain network, and then the electronic bill making conditions and the invoicing party identifier are associated and written into the data block, which is an event requiring consensus. When the corresponding block chain node of the electronic bill management server is the block chain node in the leading state, the block chain node broadcasts the event needing to achieve the consensus to other block chain nodes which are not in the leading state in the block chain network.

After receiving the event needing to achieve the consensus, the blockchain nodes which are not in the leader state broadcast the received event needing to achieve the consensus to other blockchain nodes in the blockchain network. In this way, each block link point in the block chain network enters a confirmation stage when receiving the content broadcast by the preset number of other block chain nodes is consistent, so as to prevent the fraudulent behavior of the block chain node in the leading state. And feeding back the confirmation result to the block chain nodes in the leader state after the confirmation is finished, judging that the consensus is finished on the events needing to be agreed when the block chain nodes in the leader state receive the feedback confirmation of the preset number of other block chain nodes, and writing the data corresponding to the events achieving the consensus into the data block by the block chain nodes in the block chain network.

In addition, when the block link point corresponding to the electronic bill management server is not the block link point in the leader state, the event needing to achieve consensus is forwarded to the block link node in the leader state, and the block link point in the leader state is used for leading the consensus process. And the block chain nodes in the leader state are obtained by jointly electing each block chain link point in the block chain network.

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 used in other embodiments of the present invention, and the embodiments of the present invention are not limited herein.

For example, FIG. 6 shows a schematic diagram of the consensus algorithm in one embodiment. Referring to fig. 6, a Client (Client, specifically, may be a blockchain electronic invoice application platform as shown in fig. 7) initiates a consensus Request (Request) and sends the consensus Request to a blockchain link point (master node Leader a) in a Leader state; to enter the Append Entity phase; in the application Entity stage, the Leader A broadcasts the consensus content (or intermediate data obtained by processing the consensus content) corresponding to the consensus request to other blockchain nodes (following nodes, follower B, follower C and Follower D, 8230) in the blockchain network which are not in the Leader state, to continue to enter the appendix Response phase; in the application Response stage, each slave node broadcasts the received consensus content to other blockchain nodes, and when the consensus content broadcast by the other blockchain nodes with the preset number (2f + 1) is consistent, the slave node enters a Commit stage, and then feeds back the confirmation result to the master node. When the main node receives the feedback confirmation of the other block link points with the preset number (2f + 1), the result of the consensus feedback (Reply) to the Client is judged to be completed. Wherein, 3f +1 is less than or equal to N, and N is the number of block chain nodes in the block chain network. f is the number of bad blockchain nodes in the blockchain network.

In one embodiment, the using of the electronic ticket issuing condition includes: acquiring a resource transfer share by the invoicing party equipment corresponding to the invoicing party identifier; the invoicer device inquires the electronic bill making conditions corresponding to the invoicer identification from the invoicer block chain node; the invoicing party equipment acquires the electronic bill identification associated with the invoicing party identification from the invoicing party block link point according to the resource transfer share and the electronic bill making condition; and the invoicing party equipment generates bill information according to the electronic bill identification and the resource transfer share, and uploads the generated bill information to the invoicing party block chain node.

It can be understood that the electronic ticket issuing conditions corresponding to the invoicer identifier, which are set by the electronic ticket management server, are used for controlling the electronic ticket issuing behavior through the invoicer identifier. Then, when the invoicing party equipment needs to make an electronic bill through the invoicing party identifier, the invoicing condition corresponding to the invoicing party identifier needs to be acquired to make an effective electronic bill according to the electronic bill making condition. That is, electronic tickets that are not issued in accordance with the electronic ticket issuing conditions do not have legal effect.

Wherein a resource transfer is a transfer of a resource from one account to another account. For example, a consumer transfers mobile money from his or her account to the account of the service provider after consumption. The resource transfer amount is the share of the transferred resource. For example, if the transferred resource is a currency, the resource transfer share is the amount of the transferred currency, such as 100 yuan. Electronic tickets are a voucher for resource transfer.

Specifically, after completing the resource transfer, the consumer can send the resource transfer share to the invoicing side equipment through the consumer terminal; and the consumer terminal can also continue to send the resource transfer share to the invoicing side equipment according to the consumer instruction after completing the resource transfer according to the consumer instruction. And the invoicer equipment inquires the electronic bill making conditions corresponding to the invoicer identification from the invoicer block chain node. In this way, the invoicing side device can issue the electronic bill according to the resource transfer share and the electronic bill issuing condition.

In one embodiment, the invoicer device obtains an electronic ticket identity associated with the invoicer identity from an invoicer block link point according to the resource transfer share and the electronic ticket issuing conditions, comprising: when the number of the electronic bills opened by the opening party identifier does not reach the opening number limit of the electronic bills in a single cycle appointed by the electronic bill opening condition in the electronic bill opening control cycle appointed by the electronic bill opening condition, the opening party equipment determines the number of the electronic bill identifier according to the resource transfer share and the electronic bill opening condition; and the invoicer equipment acquires the electronic bill identifications associated with the invoicer identifications according to the determined quantity from the invoicer block chain nodes.

Specifically, after the invoicing side equipment inquires the electronic bill making conditions, the invoicing control period appointed by the electronic bill making conditions can be checked firstly, and the number of electronic bills made by the invoicing side identification in the electronic bill making control period can be checked continuously to determine whether the electronic bill making quantity limit of a single-period electronic bill making appointed by the electronic bill making conditions is reached.

When the invoicing party equipment judges that the number of the electronic bills issued by the invoicing party identification in the electronic bill issuing control period does not reach the single-period electronic bill issuing number limit agreed by the electronic bill issuing condition, the single-sheet electronic bill issuing limit agreed by the electronic bill issuing control period agreed by the electronic bill issuing condition is continuously checked. The invoicing side equipment can continuously determine the number of the electronic bills required to be issued according to the invoicing amount and the resource transfer share of the single electronic bill, and further obtain the electronic bill identification which is associated with the invoicing side identification and is in an unused state from the invoicing side block chain link points according to the determined number.

When the invoicing party equipment judges that the number of the electronic bills issued by the invoicing party through the identification of the number of the issued electronic bills in the electronic bill issuing control cycle reaches the single-cycle electronic bill issuing number limit agreed by the electronic bill issuing conditions, the invoicing party equipment can replenish the electronic bills in the next electronic bill issuing control cycle.

Furthermore, after the invoicing party equipment acquires the electronic bill identification, bill information is generated according to the electronic bill identification and the resource transfer share, and the bill information is uploaded to the invoicing party block chain node. Wherein the ticket information is data for generating an electronic ticket. The ticket information may also include an identifier of the biller and an identifier of the recipient. The receiver identified by the receiver identification may specifically be a personal user or an enterprise user.

In the above embodiment, when issuing an electronic ticket, the issuing party forms the ticket information strictly according to the issuing conditions of the electronic ticket, and the validity and validity of the generated ticket information are ensured.

In one embodiment, the step of using the electronic ticket issuing condition further comprises: the invoicing party block chain link point receives the invoice data information; the block chain node of the invoicing party inquires the electronic bill making condition corresponding to the identifier of the invoicing party; the link points of the invoicing party block verify the legality of the bill information according to the issuing conditions of the electronic bill; and after the bill information passes the verification, the billing party block chain node generates an electronic bill according to the bill information and writes the electronic bill into the data block.

Specifically, after receiving the ticket information uploaded by the ticket issuer device, the block chain node of the ticket issuer can inquire the electronic ticket issuing conditions corresponding to the ticket issuer identification, and verify whether the received ticket information meets the inquired electronic ticket issuing conditions. When the billing party block chain node verifies that the received bill information conforms to the queried electronic bill making conditions, the validity of the bill information can be judged, then the electronic bill is generated according to the bill information, and the electronic bill is written into the data block.

Furthermore, the invoicing party block chain link point can also generate an electronic bill invoicing query code corresponding to the received bill information, and after the electronic bill is written into the data block, the electronic bill invoicing query code is fed back to the invoicing party equipment. Therefore, after the invoicing equipment receives the electronic bill invoicing query code fed back by the block chain node point of the invoicing party, the corresponding electronic bill can be searched from the block chain node in the block chain network according to the electronic bill invoicing query code. The invoicing side equipment 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 through 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 nodes are encrypted by adopting the randomly generated bill keys, the block chain nodes can simultaneously feed back the bill keys when feeding back the electronic bill billing inquiry code to the billing party equipment, so that the billing party equipment can decrypt the electronic bills according to the bill keys to obtain the bill information. Accordingly, the invoicing party device can transmit the ticket key and the electronic ticket invoicing inquiry code to the consumer. The ticket key may be a symmetric key or an asymmetric key.

The electronic bill billing inquiry code can be regarded as an index of the electronic bill and is used for searching the corresponding electronic bill. Specifically, the hash value may be obtained by performing hash operation on the ticket information through a hash algorithm.

In the above embodiment, when the invoicing party issues the electronic bill, the electronic bill is generated only after the information of the bill issuing basis is checked to meet the issuing condition of the electronic bill through the block link point of the invoicing party, and the electronic bill is generated in combination with the invoicing party according to the issuing condition of the electronic bill, thereby ensuring that a legal and effective electronic bill is generated.

FIG. 7 is a diagram of a deployment of a data processing system for electronic tickets in a particular embodiment. In a specific block chain electronic invoice application scenario, referring to fig. 7, a block chain network at least includes 4 block chain nodes to form an alliance chain, which are a block chain link point corresponding to a tax office server, a block chain node corresponding to an invoicing enterprise, a block chain link point corresponding to a public server, and a block chain link point corresponding to a reimbursement enterprise, respectively. Typically, the devices of each authority role interact with the corresponding tile link points.

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. And on the other hand, data of the blockchain network (or data to be written after consensus) is synchronously written from the blockchain network module in the corresponding blockchain node through a synchronization tool in real time so as to inquire 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 system centric server for maintaining a mapping of enterprise identifications and public keys for each enterprise. The system center server is isolated from the tax bureau server and is mainly used for identity authentication (for example, only the tax bureau can be limited to issue invoices, and constraint conditions related to enterprises are changed). Subsequent operations requiring centralization can be uniformly executed by the system central server.

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 and develops sdk (Software Development Kit) and api (Application Programming Interface) interfaces to the outside for a third party to interact through reverse proxy service access. The blockchain network module can be specifically realized based on the Tencent underlay blockchain technology (trustSQL). The cache region can be specifically realized by a mysql database. It is to be understood that the present embodiment is for illustration and is not limited to the implementation manner adopted in the specific implementation.

In a specific application scenario, the electronic bill may specifically be a block chain electronic invoice, the electronic bill 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 bill invoicing party (electronic bill reporting party), and the electronic bill public server may specifically be a public storage service for providing an electronic bill originating from a block chain point, such as a WeChat Server. The tax office server may upload billing contracts (electronic billing conditions) set for billing enterprises to blockchain nodes in the blockchain network. Therefore, when the billing enterprise needs to issue the electronic invoice for the consumer, the billing enterprise pulls the billing contract from the block chain node in the block chain network, and issues the electronic invoice according to the billing contract.

It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence 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 part of the steps in the above embodiments may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a part of the sub-steps or the stages of other steps.

As shown in fig. 8, in one embodiment, a data processing apparatus 800 is provided in connection with an electronic ticket. Referring to fig. 8, the data processing apparatus 800 for electronic tickets includes: an acquisition module 801, a setup module 802, and an uplink module 803.

An obtaining module 801, configured to obtain invoicing party feature data associated with the invoicing party identifier.

The setting module 802 is used for setting an electronic bill making condition corresponding to the identifier of the invoicing party according to the characteristic data of the invoicing party; and the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action through the invoicing party identifier.

The chaining module 803 is configured to correspondingly upload the electronic ticket issuing conditions and the invoicing party identifier to the block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the corresponding uploaded invoicer identifications into the data block in an associated mode.

In one embodiment, the invoicer profile includes invoicer base data. The obtaining module 801 is further configured to query registration data corresponding to the invoicer identifier; and extracting basic data of the invoicers from the inquired registration data.

In one embodiment, the biller characteristic data includes biller behavior data. The obtaining module 801 is further configured to query, from the block link points, invoicing party behavior data corresponding to the invoicing party identifier; or acquiring the invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification. The setting module 802 is further configured to update the electronic billing conditions corresponding to the identifier of the invoicer according to the loss-of-credit behavior data when the invoicer behavior data includes the loss-of-credit behavior data.

In one embodiment, the setting module 802 is further configured to narrow the electronic billing conditions corresponding to the identifier of the biller according to the act of issuing a ticket and losing credit when the act of issuing a ticket is the act of issuing a ticket and losing credit; and when the losing behavior data is tax return losing behavior data, canceling the electronic bill making condition corresponding to the invoicing party identifier according to the tax return losing behavior data.

In one embodiment, the uplink module 803 is further configured to upload the electronic ticket issuing conditions and the ticket issuer identifier to the block link point corresponding to the local; the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block chain link points corresponding to the local area, transmitting the electronic bill making conditions and the invoicer identifications to other block chain nodes in the block chain, and writing the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block after consensus is completed; and the electronic bill making conditions and the invoicer identifications which are uploaded correspondingly are also used for indicating the invoicer block chain nodes to write the transferred electronic bill making conditions and the invoicer identifications into the data blocks in a correlation manner after the consensus is completed.

In one embodiment, the electronic ticket issuing condition is used for instructing the invoicing party equipment to inquire the electronic ticket issuing condition corresponding to the invoicing party identifier from the invoicing party block chain node when the invoicing party equipment corresponding to the invoicing party identifier obtains the resource transfer share; acquiring an electronic bill identifier associated with the invoicer identifier from the invoicer block link point according to the resource transfer share and the electronic bill making condition; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the billing party block chain node.

In one embodiment, the electronic ticket issuing conditions are further used for indicating the equipment of the ticket issuing party to determine the number of the electronic ticket identifications according to the resource transfer share and the electronic ticket issuing conditions when the number of the electronic tickets issued by the ticket issuing party identification in the electronic ticket issuing control period agreed by the electronic ticket issuing conditions does not reach the single-period electronic ticket issuing number limit agreed by the electronic ticket issuing conditions; and acquiring the electronic bill identification related to the invoicer identification according to the determined quantity from the invoicer block link points.

In one embodiment, the electronic bill issuing condition is also used for instructing the invoicer block chain node to inquire the electronic bill issuing condition corresponding to the invoicer identification when the invoicer block chain link node receives the bill information; verifying the legality of the bill information according to the electronic bill issuing condition; and after the bill information passes the verification, generating an electronic bill according to the bill information, and writing the electronic bill into the data block.

In one embodiment, the electronic bill making conditions include an electronic bill making control period, a single-period electronic bill making quantity credit, a single-period electronic bill making credit and a single-sheet electronic bill making credit; the electronic bill is a block chain electronic invoice.

FIG. 9 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may be specifically the electronic ticket management terminal 110 in fig. 1. As shown in fig. 9, the computer device includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. The memory comprises a nonvolatile 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 a data processing method with respect to an electronic ticket. The internal memory may also store a computer program that, when executed by the processor, causes the processor to perform a data processing method with respect to the electronic ticket. Those skilled in the art will appreciate that the architecture shown in fig. 9 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

FIG. 10 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may be specifically the electronic ticket management server 120 in fig. 1. As shown in fig. 10, 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 which, when executed by the processor, causes the processor to implement a data processing method with respect to the electronic ticket. The internal memory may also store a computer program that, when executed by the processor, causes the processor to perform a data processing method with respect to the electronic ticket. It will be appreciated by those skilled in the art that the configuration shown in fig. 10 is a block diagram of only a portion of the configuration associated with the present application, and is not intended to limit the computing device to which the present application may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the data processing apparatus related to the electronic ticket provided in the present application may be implemented in a form of a computer program, the computer program may be run on a computer device as shown in fig. 9 or 10, and the nonvolatile storage medium of the computer device may store various program modules constituting the data processing apparatus related to the electronic ticket, such as the obtaining module 801, the setting module 802, and the uplink module 803 shown in fig. 8. The computer program composed of the respective program modules causes the processor to execute the steps in the data processing method on the electronic ticket of the respective embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 9 or 10 can acquire the invoicer feature data associated with the invoicer identification by the acquisition module 801 in the data processing apparatus 800 regarding the electronic ticket as shown in fig. 8. Setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer through a setting module 802; and the electronic bill making conditions corresponding to the invoicing party identification are used for controlling the electronic bill making action through the invoicing party identification. Uploading the electronic bill issuing conditions and the invoicing party identifier to the block chain node correspondingly through the uplink module 803; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block in an associated manner.

In one embodiment, a data processing system for electronic tickets is provided that includes an electronic ticket management server and a blockchain node. The electronic bill management server is used for acquiring characteristic data of the invoicers related to the invoicer identifications; setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer; the electronic bill making conditions corresponding to the invoicing party identification are used for controlling the electronic bill making action through the invoicing party identification; correspondingly uploading the electronic bill making conditions and the invoice party identification to a block chain node; and the block chain node is used for writing the corresponding uploaded electronic bill making conditions and the invoicer identification into the data block in an associated manner.

In one embodiment, the invoicer profile includes invoicer base data. The electronic bill management server is also used for inquiring the registration data corresponding to the invoicer identifier; and extracting basic data of the invoicers from the inquired registration data.

In one embodiment, the invoicer feature data includes invoicer behavioral data. The electronic bill management server is also used for inquiring the invoicer behavior data corresponding to the invoicer identification from the block chain node; or acquiring the invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification. And when the behavior data of the invoicing party comprises the information loss behavior data, updating the electronic bill making conditions corresponding to the identifier of the invoicing party according to the information loss behavior data.

In one embodiment, the electronic bill management server is further configured to narrow the electronic bill issuing conditions corresponding to the invoicing party identifier according to the invoicing/loss behavior data when the loss behavior data is the invoicing/loss behavior data; and when the credit loss behavior data is the tax return and credit loss behavior data, canceling the electronic bill issuing condition corresponding to the invoicing party identifier according to the tax return and credit loss behavior data.

In one embodiment, the block link points include a block link point corresponding to the electronic ticket management server and a biller block chain node corresponding to the biller identification. The electronic bill management server is also used for uploading the electronic bill making conditions and the bill making party identification to the block link points corresponding to the electronic bill management server. And the block chain link point corresponding to the electronic bill management server is also used for transmitting the electronic bill making conditions and the invoicer identification to other block chain nodes in the block chain, and writing the electronic bill making conditions and the invoicer identification which are uploaded correspondingly into the data block after consensus is completed. And the invoicing party block chain node is also used for writing the transferred electronic bill making conditions and the invoicing party identification into the data block in a correlated way after the consensus is completed.

In one embodiment, the data processing system for electronic tickets further comprises a biller device corresponding to the billing identification. The invoicing side equipment is used for acquiring the resource transfer share; inquiring an electronic bill making condition corresponding to the identifier of the invoicer from the block chain node of the invoicer; acquiring an electronic bill identification associated with the invoicing party identification from the invoicing party block link point according to the resource transfer share and the electronic bill issuing condition; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the billing party block chain node.

In one embodiment, the invoicer blockchain node is further configured to receive ticket information; inquiring the electronic bill making conditions corresponding to the invoicing party identification; verifying the legality of the bill information according to the electronic bill issuing condition; and after the bill information passes the verification, generating an electronic bill according to the bill information, and writing the electronic bill into the data block.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: acquiring characteristic data of the invoicer associated with the invoicer identifier; setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier; correspondingly uploading the electronic bill making conditions and the invoice party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block in an associated manner.

In one embodiment, the invoicer profile includes invoicer base data. Obtaining invoicing party characteristic data associated with the invoicing party identifier, comprising: inquiring registration data corresponding to the invoicing party identification; and extracting basic data of the invoicers from the inquired registration data.

In one embodiment, the biller characteristic data includes biller behavior data. Obtaining invoicing party characteristic data associated with the invoicing party identifier, comprising: inquiring the behavior data of the invoicers corresponding to the invoicer identifications from the block chain nodes; or acquiring the invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification. According to the characteristic data of the invoicer, setting the electronic bill making conditions corresponding to the invoicer identification, comprising the following steps: and when the behavior data of the invoicing party comprises the information loss behavior data, updating the electronic bill making conditions corresponding to the identifier of the invoicing party according to the information loss behavior data.

In one embodiment, updating the electronic ticket issuing condition corresponding to the invoicer identifier according to the loss of credit behavior data comprises: when the credit losing behavior data is the invoicing credit losing behavior data, narrowing the electronic bill issuing conditions corresponding to the invoicing party identification according to the invoicing credit losing behavior data; and when the credit loss behavior data is the tax return and credit loss behavior data, canceling the electronic bill issuing condition corresponding to the invoicing party identifier according to the tax return and credit loss behavior data.

In one embodiment, uploading the electronic bill making conditions and the corresponding invoice party identification to the blockchain node comprises: correspondingly uploading the electronic bill making conditions and the invoice party identification to the block link points corresponding to the local; the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block chain link points corresponding to the local area, transmitting the electronic bill making conditions and the invoicer identifications to other block chain nodes in the block chain, and writing the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block after consensus is completed; and the electronic bill making conditions and the invoicer identifications which are uploaded correspondingly are also used for indicating the invoicer block chain nodes to write the transferred electronic bill making conditions and the invoicer identifications into the data blocks in a correlation manner after the consensus is completed.

In one embodiment, the electronic bill issuing condition is used for instructing the invoicer device to inquire the electronic bill issuing condition corresponding to the invoicer identification from the invoicer block chain node when the invoicer device corresponding to the invoicer identification obtains the resource transfer share; acquiring an electronic bill identifier associated with the invoicer identifier from the invoicer block link point according to the resource transfer share and the electronic bill making condition; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the billing party block chain node.

In one embodiment, the electronic ticket issuing condition is further used for indicating the equipment of the invoicing party to determine the number of the electronic ticket identifications according to the resource transfer share and the electronic ticket issuing condition when the number of the electronic tickets issued by the invoicing party identification does not reach the single-cycle electronic ticket issuing number limit agreed by the electronic ticket issuing condition in the electronic ticket issuing control cycle agreed by the electronic ticket issuing condition; and acquiring the electronic bill identification related to the invoicer identification according to the determined quantity from the invoicer block link points.

In one embodiment, the electronic ticket issuing condition is also used for indicating the block chain node of the invoker to inquire the electronic ticket issuing condition corresponding to the identifier of the invoker when the block chain node of the invoker receives the ticket information; verifying the legality of the bill information according to the electronic bill issuing condition; and after the bill information passes the verification, generating an electronic bill according to the bill information, and writing the electronic bill into the data block.

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 characteristic data of the invoicer associated with the identifier of the invoicer; setting an electronic bill making condition corresponding to the identifier of the invoicer according to the characteristic data of the invoicer; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier; correspondingly uploading the electronic bill making conditions and the invoice party identification to a block chain node; and the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the corresponding uploaded invoicer identifications into the data block in an associated mode.

In one embodiment, the invoicer profile includes invoicer base data. Obtaining invoicer characteristic data associated with the invoicer identifier, including: inquiring registration data corresponding to the invoicing party identification; and extracting basic data of the invoicers from the inquired registration data.

In one embodiment, the biller characteristic data includes biller behavior data. Obtaining invoicer characteristic data associated with the invoicer identifier, including: inquiring the behavior data of the invoicers corresponding to the invoicer identifications from the block chain nodes; or acquiring the invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification. According to the characteristic data of the invoicer, setting the electronic bill making conditions corresponding to the invoicer identification, comprising the following steps: and when the behavior data of the invoicing party comprises the information loss behavior data, updating the electronic bill making conditions corresponding to the identifier of the invoicing party according to the information loss behavior data.

In one embodiment, uploading the electronic bill making conditions and the corresponding invoice party identifier to a blockchain node comprises the following steps: correspondingly uploading the electronic bill making conditions and the bill making party identification to the block link points corresponding to the local place; the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points corresponding to the local, transmitting the electronic bill making conditions and the invoicer identifications to other block link nodes in the block chain, and writing the corresponding uploaded electronic bill making conditions and the invoicer identifications into the data block after consensus is completed; and the electronic bill making conditions and the invoicer identifications which are uploaded correspondingly are also used for indicating the invoicer block chain nodes to write the transferred electronic bill making conditions and the invoicer identifications into the data blocks in a correlation manner after the consensus is completed.

In one embodiment, the electronic ticket issuing condition is used for instructing the invoicing party device to inquire the electronic ticket issuing condition corresponding to the invoicing party identifier from the invoicing party block chain node when the invoicing party device corresponding to the invoicing party identifier obtains the resource transfer share; acquiring an electronic bill identifier associated with the invoicer identifier from the invoicer block link point according to the resource transfer share and the electronic bill making condition; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the billing party block chain node.

In one embodiment, the electronic ticket issuing condition is also used for indicating the block chain node of the invoker to inquire the electronic ticket issuing condition corresponding to the identifier of the invoker when the block chain node of the invoker receives the ticket information; verifying the legality of the bill information according to the issuing condition of the electronic bill; and after the bill information passes the verification, generating an electronic bill according to the bill information, and writing the electronic bill into the data block.

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 can include non-volatile and/or volatile memory. 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 (Rambus) direct RAM (RDRAM), direct Rambus Dynamic RAM (DRDRAM), and Rambus Dynamic RAM (RDRAM), among others.

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 examples only show some embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that various changes and modifications can be made by those skilled in the art without departing from the spirit of the invention, and these changes and modifications are all within the scope of the invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A data processing method relating to an electronic ticket, comprising:

acquiring characteristic data of the invoicer associated with the identifier of the invoicer; the characteristic data of the invoicer is used for reflecting the characteristics of the invoicer and comprises at least one of basic data of the invoicer and behavior data of the invoicer;

correspondingly uploading the electronic bill making conditions and the invoicing party identifier to a block chain node; the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the corresponding uploaded invoicer identifications into a data block in an associated mode;

wherein the block chain node comprises an invoicer block chain node; the electronic bill making conditions and the invoicing party identification written into the data block in an associated mode are used for obtaining resource transfer shares by the invoicing party equipment corresponding to the invoicing party identification, inquiring the electronic bill making conditions corresponding to the invoicing party identification at an invoicing party block chain node, determining the number of the electronic bill identifications according to the resource transfer shares and the electronic bill making conditions, and obtaining the electronic bill identifications which are associated with the invoicing party identification and are in an unused state according to the determined number from the invoicing party block chain node; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the invoicing party block chain node.

2. The method of claim 1, wherein obtaining invoicer feature data associated with an invoicer identification comprises:

inquiring registration data corresponding to the invoicing party identification;

and extracting basic data of the invoicers from the inquired registration data.

3. The method of claim 1, wherein obtaining invoicer feature data associated with an invoicer identification comprises:

inquiring the behavior data of the invoicers corresponding to the invoicer identifications from the block chain nodes; or,

acquiring invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification;

the setting of the electronic bill making conditions corresponding to the invoicer identification according to the invoicer characteristic data comprises the following steps:

and when the behavior data of the invoicing party comprises the credit loss behavior data, updating the electronic bill making conditions corresponding to the invoicing party identification according to the credit loss behavior data.

4. The method according to claim 3, wherein the updating the electronic ticket issuing conditions corresponding to the invoicer identifier according to the loss of trust behavior data comprises:

when the credit loss behavior data is the invoicing credit loss behavior data, narrowing down the electronic bill issuing conditions corresponding to the invoicing party identification according to the invoicing credit loss behavior data;

and when the information loss behavior data is tax return information loss behavior data, canceling the electronic bill making condition corresponding to the invoicing party identifier according to the tax return information loss behavior data.

5. The method according to claim 1, wherein uploading the electronic ticket issuing conditions and the invoicer identifier correspondence to a blockchain node comprises:

correspondingly uploading the electronic bill making conditions and the invoicing party identifier to a block link point corresponding to the local place; the corresponding uploaded electronic bill making conditions and the invoicing party identification are used for indicating the block chain link points corresponding to the local, transmitting the electronic bill making conditions and the invoicing party identification to other block chain nodes in the block chain, and writing the corresponding uploaded electronic bill making conditions and the invoicing party identification into a data block after consensus is completed; and the electronic bill making conditions and the invoicer identifications which are uploaded correspondingly are used for indicating the invoicer block chain nodes to write the transferred electronic bill making conditions and the invoicer identifications into the data blocks in a correlated mode after the consensus of the invoicer block chain nodes is completed.

6. The method of claim 1, wherein the invoicer device determines a number of electronic ticket identifications based on the resource transfer share and the electronic ticket issuing conditions, and obtains the electronic ticket identifications associated with the invoicer identifications and in an unused state from the invoicer blockchain node according to the determined number, comprising:

when the number of the electronic bills issued by the issuing party identifier does not reach the single-cycle electronic bill issuing quantity limit agreed by the electronic bill issuing condition in the electronic bill issuing control cycle agreed by the electronic bill issuing condition, the issuing party equipment determines the number of the electronic bill identifiers according to the resource transfer share and the electronic bill issuing condition;

and the invoicing party equipment acquires the electronic bill identification which is associated with the invoicing party identification and is in an unused state from the invoicing party block chain node according to the determined quantity.

7. The method of claim 1, further comprising:

the invoicing party block chain link point receives the bill information;

the invoicing party block chain node inquires an electronic bill issuing condition corresponding to the invoicing party identifier;

the invoicing party block link point verifies the validity of the bill information according to the electronic bill issuing condition;

and after the bill information passes verification, the invoicer block link point generates an electronic bill according to the bill information and writes the electronic bill into a data block.

8. The method according to any one of claims 1 to 7, wherein the electronic bill making conditions include an electronic bill making control period, a single-cycle electronic bill making quantity credit, a single-cycle electronic bill making credit, and a single-sheet electronic bill making credit; the electronic bill is a block chain electronic invoice.

9. A data processing apparatus relating to electronic tickets comprising:

the obtaining module is used for obtaining invoicer characteristic data associated with the invoicer identifier; the characteristic data of the invoicer is used for reflecting the characteristics of the invoicer and comprises at least one of basic data of the invoicer and behavior data of the invoicer;

the setting module is used for setting an electronic bill making condition corresponding to the invoicing party identifier according to the invoicing party characteristic data; the electronic bill making conditions corresponding to the invoicing party identification are used for controlling electronic bill making actions carried out through the invoicing party identification;

the chaining module is used for correspondingly uploading the electronic bill making conditions and the invoicing party identification to a block chain node; the corresponding uploaded electronic bill making conditions and the invoicer identifications are used for indicating the block link points to write the corresponding uploaded electronic bill making conditions and the corresponding uploaded invoicer identifications into a data block in an associated mode;

wherein the block chain node comprises an invoicing party block chain node; the electronic bill making conditions and the invoicing party identification written into the data block in an associated mode are used for obtaining resource transfer shares by the invoicing party equipment corresponding to the invoicing party identification, inquiring the electronic bill making conditions corresponding to the invoicing party identification at an invoicing party block chain node, determining the number of the electronic bill identifications according to the resource transfer shares and the electronic bill making conditions, and obtaining the electronic bill identifications which are associated with the invoicing party identification and are in an unused state according to the determined number from the invoicing party block chain node; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the invoicing party block chain node.

10. The apparatus of claim 9, wherein the obtaining module is further configured to query registration data corresponding to an invoicer identifier; and extracting basic data of the invoicers from the inquired registration data.

11. The apparatus of claim 9, wherein the obtaining module is further configured to query the biller behavior data corresponding to the biller identifier from the block link points; or acquiring invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification; the setting module is also used for updating the electronic bill making conditions corresponding to the invoicing party identification according to the credit loss behavior data when the invoicing party behavior data comprises the credit loss behavior data.

12. The apparatus according to claim 11, wherein the setting module is further configured to narrow down an electronic billing condition corresponding to the invoicer identifier according to the invoicing/loss behavior data when the loss behavior data is the invoicing/loss behavior data; and when the information loss behavior data is tax return information loss behavior data, canceling the electronic bill making condition corresponding to the invoicing party identifier according to the tax return information loss behavior data.

13. The apparatus of claim 9, wherein the uplink module is further configured to upload the electronic ticket issuing conditions corresponding to the biller identifier to a block link point corresponding to a local site; the corresponding uploaded electronic bill making conditions and the invoicing party identification are used for indicating the block chain link points corresponding to the local, transmitting the electronic bill making conditions and the invoicing party identification to other block chain nodes in the block chain, and writing the corresponding uploaded electronic bill making conditions and the invoicing party identification into a data block after consensus is completed; and the electronic bill making conditions and the invoicer identifications which are uploaded correspondingly are also used for indicating the invoicer block chain nodes to write the transferred electronic bill making conditions and the invoicer identifications into the data blocks in a correlation mode after the consensus is completed.

14. The apparatus of claim 9, wherein the electronic ticket issuing condition is further configured to instruct the invoicer device to determine the number of the electronic ticket identifications according to the resource transfer share and the electronic ticket issuing condition when the number of the electronic tickets issued by the invoicer identification does not reach the electronic ticket issuing quantity quota of the single cycle agreed by the electronic ticket issuing condition in the electronic ticket issuing control cycle agreed by the electronic ticket issuing condition; and acquiring the electronic bill identification which is associated with the invoicing party identification and is in an unused state according to the determined quantity from the invoicing party block chain link points.

15. The apparatus of claim 9, wherein the electronic ticketing conditions are further configured to instruct a ticketing authority block-chain node to query the electronic ticketing conditions corresponding to a ticketing authority identification when the ticketing authority block-link point receives ticketing information; verifying the legality of the bill information according to the issuing condition of the electronic bill; and after the bill information passes the verification, generating an electronic bill according to the bill information, and writing the electronic bill into the data block.

16. A data processing system related to electronic bills comprises an electronic bill management server, a block chain node and a invoicer device, wherein the block chain node comprises an invoicer block chain node; wherein,

the electronic bill management server is used for acquiring characteristic data of the invoicers related to the invoicer identifications; the characteristic data of the invoicer is used for reflecting the characteristics of the invoicer and comprises at least one of basic data of the invoicer and behavior data of the invoicer; setting an electronic bill making condition corresponding to the invoicer identification according to the invoicer characteristic data; the electronic bill making condition corresponding to the invoicing party identifier is used for controlling the electronic bill making action performed through the invoicing party identifier; correspondingly uploading the electronic bill making conditions and the invoicing party identification to a block chain node;

the block chain node is used for writing the corresponding uploaded electronic bill making conditions and the invoicing party identification into a data block in an associated manner;

the invoicing party equipment corresponds to the invoicing party identifier and is used for acquiring resource transfer share, inquiring an electronic bill making condition corresponding to the invoicing party identifier at an invoicing party block chain node, determining the number of the electronic bill identifiers according to the resource transfer share and the electronic bill making condition, and acquiring the electronic bill identifiers which are associated with the invoicing party identifier and are in an unused state according to the determined number from the invoicing party block chain node; and generating bill information according to the electronic bill identification and the resource transfer share, and uploading the generated bill information to the invoicing party block chain node.

17. The system of claim 16, wherein the electronic ticket management server is further configured to query registration data corresponding to an identifier of the invoicer; and extracting basic data of the invoicers from the inquired registration data.

18. The system of claim 16, wherein the electronic ticket management server is further configured to query the blockchain node for biller behavior data corresponding to the biller identification; or acquiring invoicing party behavior data corresponding to the invoicing party identification transmitted by the law enforcement party identification; and when the invoicing party behavior data comprise the lost credit behavior data, updating the electronic bill issuing conditions corresponding to the invoicing party identification according to the lost credit behavior data.

19. The system according to claim 18, wherein the electronic ticket management server is further configured to narrow the electronic ticket issuing conditions corresponding to the invoicing party identifier according to the invoicing/loss behavior data when the loss behavior data is the invoicing/loss behavior data; and when the information loss behavior data is tax return information loss behavior data, canceling the electronic bill making condition corresponding to the invoicing party identifier according to the tax return information loss behavior data.

20. The system according to claim 16, wherein the electronic bill management server is further configured to upload the electronic bill making conditions corresponding to the invoicer identifier to the block link point corresponding to the electronic bill management server;

the block link point corresponding to the electronic bill management server is also used for transmitting the electronic bill making condition and the invoicing party identifier to other block chain nodes in the block chain, and writing the corresponding uploaded electronic bill making condition and the invoicing party identifier into a data block in a correlation manner after consensus is completed;

and the invoicing party block chain node is also used for writing the transferred electronic bill making conditions and the invoicing party identification into a data block in a correlated manner after the consensus is completed.

21. The system according to claim 16, wherein the invoicing party device is configured to determine the number of electronic ticket identifications according to the resource transfer share and the electronic ticket making conditions when the number of electronic tickets issued by the invoicing party identification in the electronic ticket making control cycle agreed by the electronic ticket making conditions does not reach the electronic ticket making quantity quota agreed by the electronic ticket making conditions in a single cycle;

22. The system of claim 16, wherein the invoicer blockchain node is further configured to receive the ticket information; inquiring the electronic bill making conditions corresponding to the invoicing party identification; verifying the legality of the bill information according to the electronic bill making condition; and after the bill information passes the verification, generating an electronic bill according to the bill information, and writing the electronic bill into a data block.

23. A computer-readable storage medium, having stored thereon 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 8.

24. 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 the method according to any one of claims 1 to 8.