A bill processing method, device and storage medium device
Through the consensus node device, the consensus mechanism of the blockchain network is solved by checking the bill information and the low bill reliability after the bill service provider is attacked, and the high reliability and immutability of bill information are achieved.
Patent Information
- Application Number
- CN201910961586.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-10-10
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-09-29
AI Technical Summary
After the bill service provider was attacked, the third party controlled the bill service provider to provide bills to other companies, resulting in the invoice issuer in the bill information being still an authorized company, resulting in the low reliability of the bill.
The bill information is verified through the consensus node device. Only when the node identifier and the terminal identifier satisfy the correspondence relationship in the associated information can the terminal be provided. The blockchain network is used to confirm and store the bill information on the chain to ensure that the bill information is guaranteed. Information reliability.
Improve the reliability of bills, prevent bill service providers from providing bills to other companies after being attacked, and ensure the authenticity and immutability of bill information.
Smart Images

Figure CN110738502B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a bill processing method, device and storage medium device. Background Art
[0002] In order to simplify the bill generation process of enterprises, many enterprises choose to transfer the bill generation operation to a third-party service provider, namely the bill service provider, which provides bills to the enterprise based on the enterprise's business activities. At present, the bill service provider authorized by the enterprise can provide bills for the enterprise. However, if the bill service provider is attacked by a third party, the third party controls the bill service provider to provide bills for other enterprises. The bill information contained in the provided bill still shows that the issuer is the enterprise, not other enterprises, resulting in low reliability of the bill. Summary of the invention
[0003] The embodiments of the present invention provide a bill processing method, device and storage medium device, which can enable a bill service provider to provide bills only to authorized enterprises, thereby improving the reliability of bills.
[0004] In a first aspect, an embodiment of the present invention provides a bill processing method, which is applied to a consensus node device, and the method includes:
[0005] Receive association information sent by a business management node device, the association information includes a node identifier of the business node device and a terminal identifier of its corresponding terminal, and the business node device is used to provide a ticket to the terminal; receive a ticket acquisition request, the ticket acquisition request includes ticket information; verify the ticket information according to the association information; if the ticket information is successfully verified, generate notification information, and send the notification information to the business node device, so that the business node device provides the ticket to the terminal according to the ticket information when it determines that the notification information indicates that the ticket information is successfully verified.
[0006] In this technical solution, the consensus node device can verify the ticket information based on the associated information sent by the business management node device. If the ticket information is verified successfully, a notification message indicating that the ticket information verification is successful is sent to the business node device, so that the business node device can provide the ticket to the terminal based on the ticket information. The ticket is provided by the business node device based on the ticket information after verification by the consensus node device. Therefore, the ticket provided by the business node device to the terminal is highly reliable.
[0007] In a second aspect, an embodiment of the present invention provides a ticket processing method, which is applied to a service management node device, and the method includes:
[0008] Receive registration request information sent by the business node device, the registration request information includes the node identifier of the business node device and the terminal identifier of its corresponding terminal; verify the node identifier; if the node identifier verification is successful, generate association information based on the registration request information, the association information includes the node identifier of the business node device and the terminal identifier of its corresponding terminal; send the association information to the consensus node device, so that the consensus node device verifies the ticket information based on the association information.
[0009] In this technical solution, the business management node device generates association information including the node identifier of the business node device and the terminal identifier of its corresponding terminal based on the registration request information sent by the business node device, and sends the association information to the consensus node device so that the consensus node device verifies the ticket information based on the association information.
[0010] In a third aspect, the present invention provides a consensus node device, which has the function of implementing the bill processing method described in the first aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.
[0011] In a fourth aspect, an embodiment of the present invention provides a consensus node device, which includes a memory, a processor and a communication interface. The memory stores a set of program codes, and the processor calls the program code stored in the memory to execute the method involved in the first aspect.
[0012] In a fifth aspect, the present invention provides a service management node device, which has the function of implementing the bill processing method described in the second aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.
[0013] In the sixth aspect, an embodiment of the present invention provides a service management node device, which includes a memory, a processor and a communication interface, the memory stores a set of program codes, and the processor calls the program code stored in the memory to execute the method involved in the second aspect.
[0014] In the seventh aspect, an embodiment of the present invention provides a computer-readable storage medium for storing computer program instructions used for a consensus node device or a business management node device, which includes a program for executing the above-mentioned first aspect or second aspect.
[0015] By implementing the example of the present invention, the business node device can provide a ticket to the terminal according to the ticket information. The ticket information is the ticket information after the consensus node device successfully verifies the associated information sent by the business management node. This ticket information satisfies the correspondence between the node identifier and the terminal identifier of the business node device in the associated information, indicating that the business node device can and can only provide a ticket for the terminal corresponding to this terminal identifier, which can improve the reliability of the ticket. After the consensus node device successfully verifies the ticket information, the ticket information can be sent to each consensus node device except the consensus node device, so that each consensus node device reaches a consensus on the ticket information. After the consensus node device determines that the ticket information has passed the consensus of each consensus node device, the ticket information is processed on the chain, so that the ticket information is distributedly stored in the form of blocks, providing traceable evidence for subsequent ticket issues. In addition, the consensus node device can receive business release information and business increase information from the business management node device, and can update the correspondence between the target node identifier and the target terminal identifier in the associated information according to the business release information or the business increase information. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background technology, the drawings required for use in the embodiments of the present invention or the background technology will be described below.
[0017] Figure 1a A type of bill provided by a bill service provider to an authorized enterprise;
[0018] Figure 1b A type of bill provided to other companies after the bill service provider is attacked;
[0019] Figure 1c A bill information provided by an embodiment of the present invention;
[0020] Figure 2 A schematic diagram of the architecture of a bill processing system provided by an embodiment of the present invention;
[0021] Figure 3 A flowchart of a bill processing method provided by an embodiment of the present invention;
[0022] Figure 4a A preset database provided by an embodiment of the present invention;
[0023] Figure 4b Another type of bill information provided by an embodiment of the present invention;
[0024] Figure 5 A schematic diagram of a flow chart of another bill processing method provided by an embodiment of the present invention;
[0025] Figure 6aAn updated preset database provided by an embodiment of the present invention;
[0026] Figure 6b Another updated preset database provided by an embodiment of the present invention;
[0027] Figure 7 A schematic diagram of a flow chart of another bill processing method provided by an embodiment of the present invention;
[0028] Figure 8a Another updated preset database provided by an embodiment of the present invention;
[0029] Figure 8b Another updated preset database provided by an embodiment of the present invention;
[0030] Fig. 9 A schematic diagram of the structure of a consensus node device provided by an embodiment of the present invention;
[0031] Fig.10 A schematic diagram of the structure of another consensus node device provided by an embodiment of the present invention;
[0032] Fig.11 A schematic diagram of the structure of a service management node device provided by an embodiment of the present invention;
[0033] Fig.12 A schematic diagram of the structure of another service management node device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0034] The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.
[0035] Currently, the bill service providers authorized by the enterprise can provide bills for the enterprise. The bill A provided is as follows: Figure 1a As shown in the figure, the issuer of the bill is enterprise A, and the recipient is enterprise C. When the bill service provider is attacked by other enterprises, other enterprises control the bill service provider to provide bills for other enterprises. The bill B provided is as follows: Figure 1b As shown, the issuer contained in the bill information is still Enterprise A, not other enterprises, such as Enterprise B, etc., and the recipient contained in the bill is Enterprise D. The bill B provided makes Enterprise A pay taxes for the business operations of other enterprises, resulting in tax evasion and tax avoidance by other enterprises, so the reliability of the provided bill is poor.
[0036] The embodiment of the present invention proposes a bill processing method, device and storage medium device. In the method, a service node device sends registration request information to a service management node device, the registration request information includes a node identifier of the service node device and a terminal identifier of its corresponding terminal; the service management node device verifies the node identifier, and if the node identifier verification is successful, generates association information including the node identifier and the terminal identifier, and then sends the association information to a consensus node device in a blockchain network; the consensus node device receives a bill acquisition request, the bill acquisition request includes bill information, and the consensus node device verifies the bill information according to the association information; if the bill information verification is successful, a notification message is generated, and the notification message is sent to the service node device, so that the service node device provides the bill to the terminal according to the bill information when it is determined that the notification information indicates that the bill information verification is successful. The consensus node device verifies the bill information, and only when the node identifier and the terminal identifier in the bill information meet the corresponding relationship in the association information, the consensus node device will notify the service node device that the bill can be provided to the terminal according to the bill information. This method enables the service node device to provide bills only for the terminal corresponding to the terminal identifier with which the corresponding relationship is established, which can improve the reliability of the bill.
[0037] In one implementation, after the terminal is authorized as a service node device, the terminal sends the node identification of the service node device to the service management node device, and the service management node device registers the service node device according to the identification of the service node device. The registered service node device can provide a ticket for the terminal.
[0038] In the process of bill processing, taking the terminal as the enterprise, the business node device as the bill service provider, and the business management node device as a business node device that manages the business node device as an example, when the enterprise authorizes the billing service to the bill service provider, the bill service provider that manages all bill service providers registers as the bill service provider for billing the terminal, and sends the registration request information to the consensus node device. The registration request information includes the registered bill service provider identifier and the terminal identifier. After the consensus node device successfully verifies the bill service provider identifier, it generates association information including the bill service provider identifier and the terminal identifier, and then sends the association information to the consensus node device in the blockchain network. The invoice acquisition request information includes the invoice information. The consensus node device verifies the invoice information according to the association information. If the invoice information is verified successfully, a notification message is generated and sent to the bill service provider, so that the bill service provider can issue an invoice for the terminal according to the invoice information when it determines that the notification information indicates that the invoice information verification is successful.
[0039] In one implementation, the service management node device is a service node device that is pre-set according to a rule. For example, according to the function of the service node device, the service node device A among all the service node devices is used as the service management node device.
[0040] In one implementation, the business management node device is a business node device elected by each business node device in the blockchain network according to a consensus algorithm. Optionally, all business node devices in the blockchain network can elect a business management node device according to a certain period, and the business management node device can be any business node device. Among them, the consensus algorithm includes but is not limited to the Proof of Work (PoW) algorithm, the Proof of Stake (PoS) algorithm, the Delegated Proof of Stake (DPoS) algorithm, the Practical Byzantine Fault Tolerance (PBFT) algorithm, etc. The business management node device can be used to receive the registration request information sent by the business node device, generate the associated information according to the registration request information, and send the associated information to the consensus node device. The business node device can be used to provide tickets for the terminal.
[0041] The consensus mechanism refers to the mathematical algorithm that enables different nodes in the blockchain network to establish trust and obtain rights and interests; the consensus mechanism is a mathematical algorithm that is recognized by all nodes in the blockchain network, which can be the above consensus algorithms. The bill processing method can use the consensus mechanism in the blockchain network to allow each consensus node device to reach a consensus on the bill information.
[0042] Blockchain is a new application model of computer technologies such as distributed data storage, consensus mechanism and encryption algorithm. It is essentially a decentralized database. Blockchain can be composed of multiple serial transaction records (also known as blocks) that are connected and protected by cryptography. The distributed ledger connected by blockchain allows multiple parties to effectively record transactions and can permanently check the transactions (cannot be tampered with).
[0043] The terminal is an enterprise that requests to obtain a ticket, and the business node device is used to provide the ticket to the terminal. The number of terminals can be one or more. Taking the number of terminals as an example, multiple terminals indicate that the enterprise has multiple branches. The terminal may include but is not limited to: smart phones (such as Android phones, iOS phones, etc.), tablet computers, portable personal computers, mobile Internet devices (Mobile Internet Devices, referred to as MID) and other devices. These terminal devices have functions such as network communication. The embodiments of the present invention are not limited.
[0044] In order to better understand the bill processing method, device and storage medium device disclosed in the embodiments of the present invention, the architecture of the system to which the embodiments of the present invention are applicable is first described below.
[0045] See also Figure 2 , Figure 2 FIG. 1 is a schematic diagram of the architecture of a bill processing system provided by an embodiment of the present invention. Figure 2 As shown, the system is composed of a terminal 201 and a blockchain network 202. The blockchain network 202 includes a business node device 2021, a business management node device 2022 and a consensus node device 2023. There can be multiple consensus node devices in the blockchain network. The consensus node device is used for consensus on bill information. The business node device and the business management node device can also be consensus node devices. The terminal is outside the blockchain network, does not participate in the consensus, and does not store information in the blockchain network. Figure 2 The system architecture shown is for example only and does not constitute a limitation to the embodiments of the present invention.
[0046] The bill can be Figure 1a As shown in the figure, it is bill A, including relevant information of the issuer and the recipient, such as the company, tax number, unit address, telephone number, etc. of the issuer and the recipient. The bill information can be Figure 1c As shown, the ticket information 1 includes the node identifier of the service node device and the terminal identifier of the terminal, such as the node identifier 1 and the terminal identifier A.
[0047] Based on the above description, the embodiment of the present invention proposes a method as follows Figure 3 The bill processing method shown may include S301-S308:
[0048] S301: The service node device sends registration request information to the service management node device.
[0049] Specifically, after the service node device is authorized by the terminal, it can provide a ticket to the terminal. Before providing the ticket to the terminal, the service node device sends a registration request message to the service management node device, and the registration request message includes the node identifier of the service node device and the terminal identifier of the corresponding terminal. The service node device is a service node device that has been authorized by the terminal, and the service node device is used to provide the ticket to the terminal.
[0050] S302: The service management node device verifies the node identifier included in the registration request information.
[0051] In one implementation, the node identifier of the service node device in the registration request information includes the identity information of the service node device, and the verification of the node identifier by the service management node device may include: verifying the identity of the sender of the node identifier, that is, verifying the identity of the service node device, thereby improving the credibility of the node identifier. Specifically, the service management node device verifies the node identifier using the public key created by the service node device. If the verification is successful, it indicates that the sender of the node identifier is the service node device that sent the node identifier, and the service management node device successfully verifies the service node identifier. In this way, it is helpful to improve the credibility of the node identifier.
[0052] In one implementation, the verification of the node identifier by the service management node device may further include: verifying the real existence of the node identifier. Once the service node device is registered, a unique node identifier is generated. If the node identifier included in the registration request information is real, it indicates that the service node device corresponding to the node identifier has been registered, and the service management node device successfully verifies the node identifier. In this way, the authenticity of the service node device corresponding to the node identifier can be improved.
[0053] In one implementation, the service management node device may also verify both the node identifier and the terminal identifier included in the registration request information. The method for verifying the node identifier is as described above and will not be described in detail.
[0054] In one implementation, the verification of the terminal identifier by the service management node device may include: verifying the identity of the sender of the terminal identifier, and the verification method is the same as the above-mentioned verification of the identity of the sender of the node identifier, which will not be repeated.
[0055] In one implementation, the verification of the terminal identification by the business management node device may include: verifying the real existence of the terminal identification. The terminal identification may include the social information code and taxpayer identification number of the terminal. If the number of terminal identifications included in the registration request information is one, the business management node device verifies whether the terminal identification really exists through the social information code and the taxpayer identification number. If the terminal identification really exists, the verification of the terminal identification is successful. This method can improve the credibility of the terminal identification. If the number of terminal identifications included in the registration request information is multiple, the business management node device verifies whether each terminal identification really exists through the social information code and the taxpayer identification number, and whether the terminals corresponding to each terminal identification belong to the same terminal class. If each terminal identification really exists and the terminals corresponding to each terminal identification belong to the same terminal class, the business management node device verifies each terminal identification successfully. For example, the registration request information includes terminal identifier A, terminal identifier B and terminal identifier C. If the business management node device verifies that the three terminal identifiers all exist, and the terminal corresponding to terminal identifier A, the terminal corresponding to terminal identifier B and the terminal corresponding to terminal identifier C are of the same terminal class M, that is, the enterprises corresponding to the three terminal identifiers are branches of enterprise M, then the business management node device successfully verifies the three terminal identifiers.
[0056] S303: If the node identification is successfully verified, the service management node device generates association information according to the registration request information.
[0057] Specifically, if the node identifier is verified successfully, the business management node device generates association information based on the registration request information. The association information includes the node identifier of the business node device and the terminal identifier of its corresponding terminal. The association information indicates that a corresponding relationship has been established between the node identifier of the business node device and the terminal identifier. It also indicates that the business node device is authorized by the terminal corresponding to the terminal identifier, that is, the business node device corresponding to the business node identifier can only provide tickets for the terminal corresponding to its corresponding terminal identifier.
[0058] S304: The consensus node device receives the associated information sent by the business management node device.
[0059] After the business management node device generates the associated information, it sends the associated information to the consensus node device so that the consensus node device can verify the ticket information according to the associated information, and the consensus node device receives the associated information sent by the business management node device.
[0060] In one implementation, after receiving the association information, the service node device stores the association information in a preset database, which is preset by the consensus node device. The association information can be stored in the preset database in the form of a document, or alternatively, in the form of a table.
[0061] S305: The consensus node device receives the ticket acquisition request.
[0062] In one implementation, when a service node device needs to provide a ticket to a terminal, the service node device cannot directly provide the ticket to the terminal based on the ticket information from the terminal, but must send a ticket acquisition request to the consensus node device. The consensus node device receives the ticket acquisition request sent by the service node device, and the ticket acquisition request includes the ticket information. Only after the consensus node device successfully verifies the ticket information can the service node device provide the ticket to the terminal based on the ticket information. This method can ensure that the ticket provided by the service node device to the terminal is provided based on the ticket information verified by the consensus node device, which can improve the reliability of the ticket.
[0063] In one implementation, when a terminal needs to obtain a ticket, the terminal can directly send a ticket acquisition request to a consensus node device. The consensus node device receives the ticket acquisition request sent by the terminal. The ticket acquisition request includes ticket information. The consensus node device verifies the ticket information. This method allows the business node device to obtain the ticket information sent by the consensus node device, which is the ticket information that has been verified by the consensus node device. This can improve the reliability of the ticket information, thereby providing the terminal with a higher reliability of the ticket.
[0064] S306: The consensus node device verifies the ticket information according to the associated information.
[0065] In one implementation, if the number of terminal identifiers included in the associated information is one, the consensus node device verifies the ticket information by: obtaining the terminal identifier corresponding to the node identifier included in the ticket information from the preset database; if the terminal identifier included in the ticket information is the same as the terminal identifier obtained from the preset database, the consensus node device verifies the ticket information successfully. Figure 1c As shown, the preset database is as follows Figure 4a As shown, the node identifier contained in the ticket information 1 is the node identifier 1, the terminal identifier contained is the terminal identifier A, the terminal identifier corresponding to the node identifier 1 obtained by the consensus node device from the preset database is the terminal identifier A, and the terminal identifier contained in the ticket information 1 is the same as the terminal identifier corresponding to the node identifier 1 obtained from the preset database, then the consensus node device successfully verifies the ticket information.
[0066] In one implementation, if the number of terminal identifiers included in the associated information is multiple, then the consensus node device verifies the ticket information by: obtaining multiple terminal identifiers corresponding to the node identifier included in the ticket information from a preset database; if the terminal identifier included in the ticket information exists among the multiple terminal identifiers obtained from the preset database, then the consensus node device verifies the ticket information successfully. Figure 4b As shown, the preset database is as follows Figure 4a As shown, the node identifier included in the ticket information is node identifier 3, and the terminal identifier included is terminal identifier F. The terminal identifiers corresponding to node identifier 3 obtained by the consensus node device from the preset database include terminal identifier D, terminal identifier E, terminal identifier F and terminal identifier M. If the terminal identifiers obtained from the preset database include terminal identifier F included in ticket information 2, then the consensus node device successfully verifies the ticket information.
[0067] The consensus node device verifies the ticket information based on the associated information. A successful verification indicates that there is a corresponding relationship between the node identifier and the terminal identifier of the business node device in the ticket information in the preset database. The business node device corresponding to the business node identifier in the ticket information can provide a ticket for the terminal corresponding to the terminal identifier, thereby improving the reliability of the ticket.
[0068] S307: If the ticket information is verified successfully, the consensus node device generates notification information.
[0069] After the service management node device successfully verifies the ticket information, it generates notification information, which is used to indicate that the ticket information has passed the verification.
[0070] S308: The consensus node device sends a notification message to the business node device.
[0071] The consensus node device generates notification information only when the ticket information is verified and sent to the business node device, which can improve the reliability of the ticket information and further improve the reliability of the tickets provided by the business node device.
[0072] In one implementation, if the ticket acquisition request information received by the consensus node device is sent by the business node device, the consensus node device sends a notification message to the business node device, indicating that the ticket information has passed the verification, so that the business node device can provide the ticket to the terminal based on the ticket information.
[0073] In one implementation, if the ticket acquisition request information received by the consensus node device is sent by the terminal, the consensus node device sends the notification information and the ticket information to the business node device, so that the business node device provides the ticket to the terminal based on the ticket information. This ticket information is the ticket information verified by the consensus node device.
[0074] S309: The service node device provides a ticket to the terminal according to the notification information.
[0075] The service node device receives the notification information from the service management node device, indicating that the ticket information has passed the verification and the ticket can be provided to the terminal according to the ticket information. The service node device provides the ticket to the terminal according to the ticket information only after receiving the notification information sent by the consensus node device, which can improve the reliability of the ticket.
[0076] By implementing the embodiments of the present invention, the business node device can provide tickets to the terminal based on the ticket information, and the ticket information is the ticket information that has been verified by the consensus node device based on the associated information generated by the business management node device. Therefore, the ticket provided by the business node device to the terminal is highly reliable.
[0077] See also Figure 5 , Figure 5 It is a flowchart of another bill processing method provided by an embodiment of the present invention, and the method includes but is not limited to S501-S513.
[0078] S501: The service node device sends registration request information to the service management node device.
[0079] S502: The service management node device verifies the node identifier included in the registration request information.
[0080] S503: If the node identifier is successfully verified, the service management node device generates association information according to the registration request information.
[0081] S504: The consensus node device receives the associated information sent by the business management node device.
[0082] S505: The consensus node device receives the ticket acquisition request.
[0083] S506: The consensus node device verifies the ticket information according to the associated information.
[0084] For details of steps S501-S506 in the embodiment of the present application, reference may be made to the execution process of steps S301-S306 in the above embodiment, which will not be described in detail in the embodiment of the present invention.
[0085] S507: If the ticket information verification is successful, the consensus node sends the ticket information to each consensus node device except the current consensus node device, so that each consensus node device reaches a consensus on the ticket information.
[0086] After the business management node device successfully verifies the bill information, it sends the bill information to each consensus node device in the blockchain network except for the current consensus node, so that each consensus node device can reach a consensus on the bill information. Only when the consensus node device successfully reaches a consensus on the bill information, the bill information is sent to each consensus node device in the blockchain network, which can improve the credibility of the bill information. Each consensus node device in the blockchain network reaches a consensus on the bill information, and sends the consensus result on the bill information in the form of a bill information consensus response to the consensus node device that receives the bill acquisition request.
[0087] Specifically, the consensus of each consensus node device on the bill information is the same as the verification method of the bill information by the above-mentioned consensus node device, which will not be repeated here. Regardless of whether the consensus result is passed or not, each consensus node device in the blockchain network can send a consensus response on the bill information to the consensus node device that receives the bill acquisition request. Among them, the consensus results for the bill information contained in the bill information consensus response from each consensus node device in the blockchain network can be independent of each other, that is, the consensus process for the bill information performed by each consensus node device can be unaffected by other consensus node devices. For example, the consensus result for the bill information contained in the bill information consensus response from one consensus node device can be a consensus passed, and the consensus result for the bill information contained in the bill information consensus response from another consensus node device can be a consensus failed.
[0088] The consensus node device that receives the bill acquisition request obtains the bill information consensus result based on the bill information consensus response, and then determines whether the bill information has passed the consensus of the blockchain network, that is, the bill information consensus result is jointly determined based on the bill information consensus response returned by each consensus node device in the blockchain network. In this way, all consensus node devices in the blockchain network can participate in the consensus process for bill information, which is conducive to improving the credibility of bill information.
[0089] In one implementation, the consensus node device receiving the bill acquisition request determines whether the bill information has passed the consensus of the blockchain network based on the consensus results of each consensus node device on the bill information. If the number of consensus results of each consensus node device on the bill information is greater than the preset threshold, the consensus node device receiving the bill acquisition request determines that the bill information has passed the consensus of the blockchain network. For example, the preset threshold is 50% of the number of consensus node devices in the blockchain network. If the blockchain network is composed of 28 consensus node devices, 18 consensus node devices have a consensus result of passing the bill information, and the number of consensus results of the consensus node devices in the blockchain network on the bill information is greater than the preset threshold, then the consensus node device determines that the bill information has passed the consensus of each consensus node device in the blockchain network.
[0090] S508: If the ticket information passes the consensus of each consensus node device, the consensus node device will process the ticket information on the chain.
[0091] If it is determined according to the above method that the bill information has passed the consensus of the blockchain network, the bill information will be processed on the chain to generate a block containing the bill information, so that the bill information is stored in a distributed data form in the form of blocks and cannot be tampered with. After the on-chain processing, each consensus node device stores the bill information and cannot be tampered with, which can provide traceable evidence for subsequent bill issues. For example, terminal A obtains a request bill from the business node device. After the bill information passes the consensus of the consensus node device, the bill information is processed on the chain and sent to the business node device. The business node device provides the bill to enterprise A based on the bill information. In the subsequent time, terminal A does not recognize the bill information on the bill and is unwilling to pay taxes and fees for the bill provided. At this time, the bill can be found in each consensus node in the blockchain network to confirm that the bill information has not been tampered with. The bill information is indeed provided by terminal A, and terminal A should pay taxes and fees for the bill.
[0092] S509: The consensus node device generates notification information.
[0093] S510: The consensus node device sends a notification message to the business node device.
[0094] S511: The service node device provides a ticket to the terminal according to the notification information.
[0095] The specific details of steps S509-S511 in the embodiment of the present application may refer to the execution process of steps S307-S309 in the above embodiment, and will not be repeated in the embodiment of the present invention.
[0096] S512: The consensus node device receives the service release information sent by the service management node device.
[0097] Specifically, the consensus node device receives the service release information sent by the service node device, the service release information includes the node identifier of the target service node device and the target terminal identifier, and the service release information is used to release the correspondence between the node identifier of the target service node device and the target terminal identifier. The node identifier of the target service node device is the node identifier of the service node device stored in the preset database, and the target terminal identifier is the terminal identifier corresponding to the node identifier of the target service node device in the preset database.
[0098] S513: The consensus node device releases the correspondence between the target node identifier and the target terminal identifier according to the service release information.
[0099] After receiving the service release information, the consensus node device releases the correspondence between the node identifier of the target service node device and the target terminal identifier by deleting the terminal identifier corresponding to the node identifier of the target service node device according to the service release information.
[0100] In one implementation, if the number of terminal identifiers corresponding to the node identifier of the target service node device in the preset database is one, the consensus node device deletes the node identifier and the target terminal identifier of the target service node device in the preset database, releases the corresponding relationship between the node identifier and the target terminal identifier of the target service node device, and obtains an updated preset database. Figure 4a As shown, the node identifier of the target service node device in the service release information is node 1, and the target terminal identifier is terminal identifier A. Then the consensus node device deletes the target node identifier 1 and the target terminal identifier A in the node identifier of the service node device, releases the corresponding relationship between the target node identifier 1 and the target terminal identifier A, and obtains an updated preset database 1 as shown in FIG. Figure 6a shown.
[0101] In one implementation, if the number of terminal identifiers corresponding to the node identifier of the target service node device in the preset database is multiple, the consensus node device deletes the target terminal identifier in the preset database, releases the correspondence between the node identifier of the target service node device and the target terminal identifier, and obtains an updated preset database. Figure 4a As shown, the node identifier of the target service node device in the service release information is node identifier 2, and the target terminal identifier is terminal identifier B. Then the consensus node device deletes the target terminal identifier B corresponding to the target node identifier 2, releases the corresponding relationship between the target node identifier 2 and the target terminal identifier B, and obtains the preset database 2 as shown in FIG. Figure 6b shown.
[0102] After releasing the correspondence between the node identifier and the target terminal identifier of the target business node device, when the consensus node device receives a ticket acquisition request, if the ticket acquisition request includes the target node identifier and the target terminal identifier, and the consensus node device cannot find the target terminal corresponding to the target node identifier in the updated preset database, the consensus node device fails to verify the ticket information, and the business node device corresponding to the target node identifier cannot provide a ticket for the terminal corresponding to the target terminal identifier. For example, the above-mentioned consensus node device releases the correspondence between the target node identifier 2 and the target terminal identifier B according to the business release information. After that, if the ticket acquisition request received by the consensus node device includes the node identifier 2 and the terminal identifier B, the consensus node device cannot find the terminal identifier B corresponding to the node identifier 2 in the updated preset data 2, the consensus node device fails to verify the ticket information, and the business node device corresponding to the node identifier 2 cannot provide a ticket for the terminal identifier B.
[0103] In the embodiment of the present invention, the consensus node device determines that the ticket information has passed the consensus of each consensus node device, and processes the ticket information on the chain, so that the ticket information can be stored in each consensus node device in the form of blocks, which can provide traceable evidence for subsequent ticket issues. At the same time, the consensus node device can release the correspondence between the target node identifier and the target terminal identifier according to the service release information sent from the service management node device, and realize the update of the correspondence between the node identifier and the terminal identifier of the service node device in the preset database.
[0104] See also Figure 7 , Figure 7 It is a flowchart of another bill processing method provided by an embodiment of the present invention, and the method includes but is not limited to S701-S713.
[0105] S701: The service node device sends registration request information to the service management node device.
[0106] S702: The service management node device verifies the node identifier in the registration request information.
[0107] S703: If the node identifier is successfully verified, the service management node device generates association information according to the registration request information.
[0108] S704: The consensus node device receives the associated information sent by the business management node device.
[0109] For details of steps S701-S704 in the embodiment of the present application, reference may be made to the execution process of steps S501-S504 in the above embodiment, which will not be described in detail in the embodiment of the present invention.
[0110] S705: The consensus node device receives the service addition information sent by the service management node device.
[0111] Specifically, the consensus node device receives the service addition information sent by the service node device, the service addition information includes the node identifier of the target service node device and the target terminal identifier, and the service addition information is used to increase the correspondence between the node identifier of the target service node device and the target terminal identifier. The node identifier of the target service node device can be a service node device that has been stored in the preset database. Optionally, the node identifier of the target service node device can also be a node identifier of a service node device that does not exist in the preset database, and the target terminal identifier is a terminal identifier that does not exist in the preset database.
[0112] S706: The consensus node device adds the corresponding relationship between the target node identifier and the target terminal identifier according to the service addition information.
[0113] After receiving the service increase information, the consensus node device increases the correspondence between the target node identifier and the target terminal identifier by adding a terminal identifier corresponding to the node identifier of the target service node device according to the service increase information, thereby obtaining an updated preset database.
[0114] In one implementation, when the node identifier of the target service node device in the service addition information is a node identifier that already exists in the preset data, the consensus node device searches for the node identifier of the target service node device in the preset database, and adds the target terminal identifier under the corresponding relationship of the target service node device, thereby increasing the corresponding relationship between the target node identifier and the target terminal identifier, and obtaining an updated preset database. For example, the target node identifier in the service addition information is node identifier 1, the target terminal identifier is terminal identifier Q, and the preset database is as follows: Figure 4a As shown, the consensus node device finds the node identifier 1 in the preset database, and adds the terminal identifier Q to the terminal identifier corresponding to the node identifier 1 to obtain an updated preset database 3, as shown in FIG. Figure 8a As shown, the correspondence between the target node identifier 1 and the target terminal identifier Q is added.
[0115] In one implementation, when the node identifier of the target service node device in the service addition information is not in the preset database, the consensus node device adds the target node identifier and the terminal identifier to the preset database, thereby increasing the correspondence between the target node identifier and the target terminal identifier, and obtaining an updated preset database. Figure 4a As shown, the target node identifier included in the service addition information is node identifier 4, and the target terminal identifier is terminal identifier I. The consensus node device searches in the preset database and finds that the node identifier 4 does not exist in the preset database. Then, the node identifier 4 and the terminal identifier I are added to the preset database to obtain an updated preset database 4, as shown in FIG. Figure 8b As shown, the correspondence between the target node identifier 4 and the target terminal identifier I is added.
[0116] S707: The consensus node device receives the ticket acquisition request.
[0117] The specific details of step S705 in the embodiment of the present application may refer to the execution process of step S505 in the above embodiment, which will not be described in detail in the embodiment of the present invention.
[0118] S708: The consensus node device verifies the ticket information based on the associated information.
[0119] After receiving the ticket acquisition request, the consensus node device verifies the ticket information according to the associated information. The associated information at this time is the associated information in the updated preset database, that is, the consensus node device verifies the ticket information according to the correspondence between the node identifier and the terminal identifier in the updated preset database. If there is a terminal identifier corresponding to the node identifier in the ticket acquisition request in the updated preset database, the consensus node device successfully verifies the ticket information. When the number of terminal identifiers included in the associated information is one or more, the consensus node device verifies the ticket information in the same way as in S306, which will not be repeated.
[0120] S709: If the ticket information verification is successful, the consensus node device sends the ticket information to each consensus node device except the current consensus node, so that each consensus node device reaches a consensus on the ticket information.
[0121] S710: If the ticket information passes the consensus of each consensus node device, the consensus node device will process the ticket information on the chain.
[0122] S711: The consensus node device generates notification information.
[0123] S712: The consensus node device sends a notification message to the business node device.
[0124] S713: The service node device provides a ticket to the terminal according to the notification information.
[0125] The specific details of steps S709-S713 in the embodiment of the present application can refer to the execution process of steps S507-S511 in the above embodiment, and will not be repeated in the embodiment of the present invention.
[0126] In an embodiment of the present invention, the consensus node device adds the correspondence between the target node identifier and the target terminal based on the received service addition information, thereby updating the correspondence between the node identifier and the terminal identifier of the service node device in the preset database. The consensus node device verifies the ticket information based on the updated preset database, thereby improving the reliability of the ticket.
[0127] See also Fig. 9 , Fig. 9 is a schematic diagram of a consensus node device provided by an embodiment of the present invention, and the consensus node device can be used for Figure 3 , Figure 5 and Figure 7 In the illustrated embodiment, the steps performed by the consensus node device, the consensus node device 90 may include:
[0128] The receiving module 901 is used to receive the association information sent by the service management node device, where the association information includes the node identifier of the service node device and the terminal identifier of the terminal corresponding to the service node device, and the service node device is used to provide the ticket to the terminal;
[0129] The receiving module 901 is further used to receive a ticket acquisition request, where the ticket acquisition request includes ticket information;
[0130] Processing module 902, used to verify the bill information according to the associated information;
[0131] The processing module 902 is also used to generate notification information after determining that the ticket information verification is successful;
[0132] The sending module 903 is used to send the notification information to the service node device, so that the service node device provides the ticket to the terminal according to the ticket information when it determines that the notification information indicates that the ticket information verification is successful.
[0133] In one implementation, after the processing module 902 verifies the ticket information according to the associated information, the processing module 902 is further configured to send the ticket information to each consensus node device in the blockchain network except the consensus node device after determining that the ticket information is successfully verified, so that each consensus node device reaches a consensus on the ticket information;
[0134] Processing module 902 is also used to determine that after the bill information consensus is passed, the bill information is put on the chain for processing.
[0135] In one implementation, the ticket acquisition request received by the receiving module 901 is sent by the terminal;
[0136] The processing module 902 is further configured to send the notification information and the ticket information to the service node device.
[0137] In one implementation, after the processing module 902 receives the association information sent by the service management node device, the processing module 902 is further configured to store the association information in a preset database;
[0138] The processing module 902 is further used to obtain the terminal identifier corresponding to the node identifier included in the ticket information in the preset database;
[0139] The processing module 902 is further configured to determine that the verification of the ticket information is successful if the terminal identifier included in the ticket information is the same as the terminal identifier obtained from the preset database.
[0140] In one implementation, the number of terminal identifiers included in the association information received by the processing module 902 and sent by the service management node device is multiple;
[0141] The processing module 902 is further used to store the associated information in a preset database;
[0142] The processing module 902 is further used to obtain multiple terminal identifiers corresponding to the node identifiers included in the ticket information in a preset database;
[0143] The processing module 902 is further configured to determine that the ticket information verification is successful if the terminal identifier included in the ticket information exists among the multiple terminal identifiers obtained from the preset database.
[0144] In one implementation, the processing module 1102 is also used to receive service release information sent by the service management node device, and the service release information includes the node identifier and the target terminal identifier of the target service node device; the processing module 902 is also used to release the correspondence between the node identifier and the target terminal identifier of the target service node device according to the service release information.
[0145] In one implementation, the processing module 902 is also used to receive service addition information sent by the service management node device, the service addition information includes the node identifier and the target terminal identifier of the target service node device; the processing module 902 is also used to add the correspondence between the node identifier and the target terminal identifier of the target service node device according to the service addition information.
[0146] See also Fig.10 , Fig.10 It is a structural diagram of a consensus node device provided in an embodiment of the present invention. The consensus node device 100 includes a processor 1001, a memory 1002, and a communication interface 1003. The processor 1001, the memory 1002, and the communication interface 1003 are connected via one or more communication buses.
[0147] Processor 1001 is configured to support consensus node device execution Figure 3 , Figure 5 and Figure 7 The corresponding functions of the consensus node device in the illustrated embodiment. The processor 1001 may be a central processing unit (CPU), a network processor (NP), a hardware chip or any combination thereof.
[0148] The memory 1002 is used to store program codes, etc. The memory 1002 may include a volatile memory, such as a random access memory (RAM); the memory 1002 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); the memory 1002 may also include a combination of the above-mentioned types of memory.
[0149] The communication interface 1003 is used to receive and send data. For example, the communication interface 1003 is used to receive association information sent by the service management node device, or the communication interface 1003 is used to send notification information to the service node device.
[0150] In an embodiment of the present invention, the consensus node device 100 includes multiple communication interfaces, wherein the communication interface for sending data and the communication interface for receiving data may not be the same communication interface.
[0151] The processor 1001 may call the program code stored in the memory 1002 to perform the following operations:
[0152] The communication interface 1003 receives the association information sent by the service management node device, the association information includes the node identifier of the service node device and the terminal identifier of the corresponding terminal, and the service node device is used to provide the ticket to the terminal;
[0153] The communication interface 1003 receives a ticket acquisition request, where the ticket acquisition request includes ticket information;
[0154] The processor 1001 verifies the bill information according to the associated information;
[0155] If the processor 1001 successfully verifies the ticket information, it generates notification information;
[0156] The processor 1001 sends the notification information to the service node device through the communication interface 1003 .
[0157] In one implementation, after the processor 1001 verifies the ticket information according to the associated information, it may further perform the following operations:
[0158] If the processor 1001 successfully verifies the bill information, it sends the bill information to each consensus node device in the blockchain network except the current consensus node device, so that each consensus node device reaches a consensus on the bill information;
[0159] If processor 1001 determines that the bill information consensus has been passed, the bill information will be uploaded to the chain for processing.
[0160] In one implementation, the ticket acquisition request received by the processor 1001 is sent by the terminal, and the processor 1001 sends notification information to the service node device, including: the processor 1001 sends the notification information and ticket information to the service node device.
[0161] In an implementation manner, after receiving the association information sent by the service management node device, the processor 1001 may further perform the following operations:
[0162] The processor 1001 stores the associated information in a preset database;
[0163] The processor 1001 obtains the terminal identifier corresponding to the node identifier included in the ticket information from a preset database;
[0164] The processor 1001 determines that the terminal identifier included in the ticket information is the same as the terminal identifier obtained from the preset database, and determines that the ticket information verification is successful.
[0165] In one implementation, the number of terminal identifiers included in the association information received by the processor 1001 is multiple; after the processor 1001 receives the association information sent by the service management node device, it may further perform the following operations:
[0166] The processor 1001 stores the associated information in a preset database;
[0167] The processor 1001 obtains multiple terminal identifiers corresponding to the node identifiers included in the ticket information from a preset database;
[0168] The processor 1001 determines that the terminal identification included in the ticket information exists among the multiple terminal identifications obtained from the preset database, and then determines that the ticket information verification is successful.
[0169] In one implementation, the processor 1001 may further perform the following operations:
[0170] The processor 1001 receives service release information sent by the service management node device, where the service release information includes a node identifier and a target terminal identifier of a target service node device;
[0171] The processor 1001 releases the correspondence between the node identifier of the target service node device and the target terminal identifier according to the service release information.
[0172] In one implementation, the processor 1001 may further perform the following operations:
[0173] The processor 1001 receives service adding information sent by the service management node device, where the service adding information includes a node identifier and a target terminal identifier of a target service node device;
[0174] The processor 1001 adds a correspondence between a node identifier of a target service node device and a target terminal identifier according to the service adding information.
[0175] See also Fig.11 , Fig.11 is a schematic diagram of a structure of a service management node device provided by an embodiment of the present invention, wherein the service management node device can be used for Figure 3 , Figure 5 and Figure 7 In the steps performed by the service management node device in the illustrated embodiment, the service management node device 110 may include:
[0176] The receiving module 1101 is used to receive registration request information sent by a service node device, where the registration request information includes a node identifier of the service node device and a terminal identifier of its corresponding terminal;
[0177] The processing module 1102 is used to verify the node identification;
[0178] The processing module 1102 is further configured to generate association information according to the registration request information if the node identifier is successfully verified, the association information including the node identifier of the service node device and the terminal identifier of its corresponding terminal;
[0179] The sending module 1103 is used to send the associated information to the consensus node device so that the consensus node device verifies the ticket information according to the associated information.
[0180] In one implementation, before the processing module 1102 generates the associated information according to the request information, the processing module 1102 is further configured to verify the terminal identifier;
[0181] The processing module 1102 is further configured to generate associated information according to the request information if the terminal identification is successfully verified.
[0182] According to another embodiment of the present application, Fig. 9 or Fig.11The various modules in the device shown can be separately or completely combined into one or several other modules to constitute, or one (some) of the modules can also be split into multiple smaller modules in function to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above modules are divided based on logical functions. In practical applications, the functions of a module can also be implemented by multiple modules, or the functions of multiple modules can be implemented by one module. In other embodiments of the present application, other modules may also be included. In practical applications, these functions can also be implemented with the assistance of other modules, and can be implemented by the collaboration of multiple modules, which is not limited in the present application.
[0183] See also Fig.12 , Fig.12 It is a structural diagram of a service management node device provided in an embodiment of the present invention. The service management node device 120 includes a processor 1201, a memory 1202, and a communication interface 1203. The processor 1201, the memory 1202, and the communication interface 1203 are connected via one or more communication buses.
[0184] Processor 1201 is configured to support client execution Figure 3 , Figure 5 and Figure 7 Corresponding functions of the service management node device in the illustrated embodiment. The processor 1201 may be a central processing unit (CPU), a network processor (NP), a hardware chip or any combination thereof.
[0185] The memory 1202 is used to store program codes, etc. The memory 1202 may include a volatile memory, such as a random access memory (RAM); the memory 1202 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); the memory 1202 may also include a combination of the above-mentioned types of memory.
[0186] In the embodiment of the present invention, the service management device 120 includes multiple communication interfaces, wherein the communication interface for sending data and the communication interface for receiving data may not be the same communication interface.
[0187] The processor 1201 may call the program code stored in the memory 1202 to perform the following operations:
[0188] The communication interface 1003 receives the registration request information sent by the service node device, where the registration request information includes the node identifier of the service node device and the terminal identifier of its corresponding terminal;
[0189] The processor 1201 verifies the node identifier;
[0190] If the processor 1201 successfully verifies the node identifier, it generates association information according to the registration request information, where the association information includes the node identifier of the service node device and the terminal identifier of its corresponding terminal;
[0191] The processor 1201 sends the associated information to the consensus node device through the communication interface 1203, so that the consensus node device verifies the ticket information according to the associated information.
[0192] In one implementation, before the processor 1201 generates the association information according to the request information, the process further includes:
[0193] The processor 1201 verifies the terminal identification;
[0194] If the processor 1201 successfully verifies the terminal identification, it generates association information according to the request information.
[0195] The embodiment of the present invention also provides a computer-readable storage medium that can be used to store Figure 3 , Figure 5 and Figure 7 The computer software instructions used by the consensus node device or the business management node device in the illustrated embodiment include the computer software instructions for executing the programs designed for the consensus node device or the business management node device in the above-mentioned embodiments.
[0196] The computer-readable storage medium includes but is not limited to a flash memory, a hard disk, and a solid-state drive.
[0197] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. A bill processing method, characterized in that: The method is applied to a consensus node device, and the method comprises: Receiving association information sent by a service management node device, the association information including a node identifier of the service node device and a terminal identifier of a corresponding terminal, the association information being used to indicate that the service node device is authorized by the terminal and the service node device is authorized to provide a ticket to the terminal; storing the associated information in a preset database; receiving a ticket acquisition request, wherein the ticket acquisition request includes ticket information; Acquire, in the preset database, a terminal identifier corresponding to the node identifier included in the ticket information; If the terminal identifier included in the ticket information is the same as the terminal identifier obtained from the preset database, the ticket information is successfully verified; Generate notification information, and send the notification information to the service node device, so that the service node device provides the ticket to the terminal according to the ticket information when determining that the notification information indicates that the ticket information is successfully verified; The method further comprises: Receiving service addition information sent by the service management node device, wherein the service addition information includes a node identifier and a target terminal identifier of a target service node device; According to the service adding information, adding a correspondence between the node identifier of the target service node device and the target terminal identifier includes: When the node identifier of the target service node device in the service adding information is a node identifier that already exists in the preset database, the consensus node device searches for the node identifier of the target service node device in the preset database, and adds the target terminal identifier under the relationship corresponding to the target service node device; When the node identifier of the target service node device in the service adding information is not in the preset database, the consensus node device adds the target node identifier and the target terminal identifier in the preset database.
2. The method according to claim 1, characterized in that If the terminal identifier included in the ticket information is the same as the terminal identifier obtained in the preset database, after the ticket information is successfully verified, the method further includes: Send the bill information to each consensus node device in the blockchain network except the current consensus node device, so that each consensus node device reaches a consensus on the bill information; If it is determined that the bill information consensus has been passed, the bill information will be uploaded to the chain for processing.
3. The method according to claim 1, characterized in that: The ticket acquisition request is sent by the terminal; The sending the notification information to the service node device includes: The notification information and the ticket information are sent to the service node device.
4. The method according to claim 1, characterized in that: The association information includes a plurality of terminal identifiers; The obtaining, in the preset database, a terminal identifier corresponding to a node identifier included in the ticket information includes: Acquire, in the preset database, a plurality of terminal identifiers corresponding to the node identifier included in the ticket information; If the terminal identifier included in the ticket information is the same as the terminal identifier obtained in the preset database, then the ticket information is successfully verified, including: If the terminal identification included in the ticket information exists among the multiple terminal identifications obtained from the preset database, the ticket information is successfully verified.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Receiving service release information sent by the service management node device, wherein the service release information includes a node identifier and a target terminal identifier of a target service node device; According to the service release information, the correspondence between the node identifier of the target service node device and the target terminal identifier is released.
6. A bill processing method, characterized in that: The method is applied to a service management node device, and the method comprises: Receiving registration request information sent by a service node device, wherein the registration request information includes a node identifier of the service node device and a terminal identifier of a corresponding terminal; Verifying the node identifier; If the node identifier is successfully verified, association information is generated according to the registration request information, the association information including the node identifier of the service node device and the terminal identifier of the corresponding terminal, the association information being used to indicate that the service node device is authorized by the terminal and the service node device is authorized to provide a ticket to the terminal; Sending the associated information to the consensus node device so that the consensus node device verifies the ticket information according to the associated information; The method further comprises: The service addition information sent to the consensus node device includes a node identifier and a target terminal identifier of the target service node device.
7. The method according to claim 6, characterized in that Before generating the associated information according to the request information, the method further includes: Verifying the terminal identification; If the terminal identification is successfully verified, the associated information is generated according to the request information.
8. A consensus node device, characterized in that: The device comprises: A receiving module, configured to receive association information sent by a service management node device, wherein the association information includes a node identifier of the service node device and a terminal identifier of a corresponding terminal, wherein the association information is used to indicate that the service node device is authorized by the terminal and the service node device is authorized to provide a ticket to the terminal; A processing module, used for storing the associated information in a preset database; The receiving module is further used to receive a ticket acquisition request, wherein the ticket acquisition request includes ticket information; The processing module is further configured to obtain, from the preset database, a terminal identifier corresponding to the node identifier included in the ticket information; if the terminal identifier included in the ticket information is the same as the terminal identifier obtained from the preset database, verifying the ticket information successfully and generating notification information; A sending module, configured to send the notification information to the service node device, so that the service node device provides the ticket to the terminal according to the ticket information when determining that the notification information indicates that the ticket information verification is successful; The processing module is also used to receive service increase information sent by the service management node device, the service increase information includes the node identifier and the target terminal identifier of the target service node device; according to the service increase information, the corresponding relationship between the node identifier of the target service node device and the target terminal identifier is added, including: when the node identifier of the target service node device in the service increase information is a node identifier that already exists in the preset database, the consensus node device searches for the node identifier of the target service node device in the preset database, and adds the target terminal identifier under the corresponding relationship of the target service node device; when the node identifier of the target service node device in the service increase information is not in the preset database, the consensus node device adds the target node identifier and the target terminal identifier in the preset database.
9. A consensus node device, characterized in that: It comprises a memory, a processor and a communication interface, the memory stores a set of program codes, and the processor calls the program codes stored in the memory to execute the method as claimed in any one of claims 1 to 5.
10. A service management node device, characterized in that: The device comprises: A receiving module, configured to receive registration request information sent by a service node device, wherein the registration request information includes a node identifier of the service node device and a terminal identifier of a corresponding terminal; a processing module, configured to verify the node identifier, and if the node identifier is successfully verified, generate association information according to the registration request information, wherein the association information includes the node identifier of the service node device and the terminal identifier of the corresponding terminal, and the association information is used to indicate that the service node device is authorized by the terminal, and the service node device is authorized to provide a ticket to the terminal; A sending module, used for sending the associated information to a consensus node device, so that the consensus node device verifies the ticket information according to the associated information; The sending module is also used to send service addition information to the consensus node device, and the service addition information includes a node identifier and a target terminal identifier of the target service node device.
11. A service management node device, characterized in that: It comprises a memory, a processor and a communication interface, the memory stores a set of program codes, and the processor calls the program codes stored in the memory to execute the method as claimed in claim 6 or 7.
12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a consensus node device, the method according to any one of claims 1 to 5 is implemented.
13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a service management node device, the method according to claim 6 or 7 is implemented.
