A method, device and medium for processing bill data
Through blockchain technology and smart contracts, the problems of data security and low efficiency of refund and change claims on traditional ticket purchase platforms have been solved, decentralized data backup and automated claims processing have been realized, and user rights and platform credibility have been protected.
Patent Information
- Application Number
- CN201911137287.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-11-19
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2039-12-15
AI Technical Summary
The bill data stored in traditional ticket purchase platforms is at risk of data tampering and loss in their own servers, resulting in complex and inefficient handling of refund and change claims, making it difficult to protect user rights and interests.
Using blockchain technology, the bill platform refund and change claims rules are stored on the blockchain through smart contracts, and the blockchain node equipment is used to receive and process transaction data to realize decentralized multi-node backup and ensure data Security and reliability allow automatic refund and change claims without the participation of third parties.
It reduces the risk of bill data being tampered with and lost, improves the efficiency of refund and change claims, enhances the protection of user rights and interests, and at the same time enhances the credibility of the bill platform.
Smart Images

Figure CN110866755B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a method, device and medium for processing bill data. Background Art
[0002] With the continuous development of Internet technology, the emergence of various Internet ticket purchasing platforms has provided great convenience for users' lives. Users can purchase various types of tickets online through ticket purchasing platforms, thus eliminating the trouble of purchasing tickets on site. The traditional ticket purchasing platform's ticket refund and change claim rules are divided into two rules. One is the information data published by the ticket platform, and the data is centrally stored in the ticket platform's own server. The other is the information data published through a third-party ticket purchasing platform. This part of the information data includes the refund and change claim rules published by the third-party platform and the official refund and change claim rules of the ticket platform, and is stored in the third-party platform's own server. The centralized storage of data has the risk of data tampering and loss. Therefore, reducing the risk of tampering and loss of ticket data on the ticket platform is an urgent problem to be solved. Summary of the invention
[0003] The embodiment of the present application proposes a method, device and medium for processing bill data, which can automatically execute refund, change and claim settlement without the involvement of a third party, thereby improving the efficiency of claim settlement and helping to improve the credibility of the bill platform.
[0004] In a first aspect, an embodiment of the present application provides a method for processing bill data, characterized in that the method is applied to a first blockchain node device, and the method includes:
[0005] Receiving first transaction data sent by the bill platform, the first transaction data is generated after the target user purchases a bill on the bill platform, the first transaction data including: bill summary data of the purchased bill, target contract information address information, bill platform identifier, and target user identifier;
[0006] Searching for the bill contract information from the blockchain according to the target contract information address information, and verifying the bill platform identifier according to the found bill contract information;
[0007] If the verification is passed, a mark is added to the bill summary data, and the mark, the bill summary data and the target user identifier are packaged to obtain second transaction data, wherein the mark is used to indicate that the bill summary data is in a valid state;
[0008] The second transaction data is processed on the chain.
[0009] In the second aspect, the embodiment of the present application provides a blockchain node device, which has the function of implementing the method for processing bill data in the first aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes:
[0010] A receiving unit, configured to receive first transaction data sent by a bill platform, wherein the first transaction data is generated after a target user purchases a bill on the bill platform, and the first transaction data includes: bill summary data of the purchased bill, target contract information address information, a bill platform identifier, and a target user identifier;
[0011] A processing unit, configured to search for the bill contract information from the blockchain according to the target contract information address information, and verify the bill platform identifier according to the found bill contract information;
[0012] The processing unit is further configured to add a mark to the bill summary data if the verification is passed, and to package the mark, the bill summary data and the target user identifier to obtain second transaction data, wherein the mark is used to indicate that the bill summary data is in a valid state;
[0013] The processing unit is also used to process the second transaction data on the chain.
[0014] In a third aspect, an embodiment of the present application provides a blockchain node device, which includes a memory and a processor, wherein the memory stores a set of program codes, and the processor calls the program codes stored in the memory to execute the operations involved in the first aspect.
[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer program instructions for a blockchain node device, which includes instructions for executing the program involved in the first aspect above.
[0016] According to the embodiment of the present application, the first blockchain node device first receives the first transaction data sent by the bill platform. The first transaction data is generated after the target user purchases the bill on the bill platform. The first transaction data includes: the bill summary data of the purchased bill, the target contract information address information, the bill platform identifier and the target user identifier. Then, the bill contract information is searched from the blockchain according to the target contract information address information, and the bill platform identifier is verified according to the found bill contract information. If the verification passes, a mark is added to the bill summary data, and the mark, the bill summary data and the target user identifier are packaged to obtain the second transaction data. The mark is used to indicate that the bill summary data is in a valid state. Finally, the second transaction data is processed on the chain. Based on the blockchain, the transaction data of the bill platform is decentralized to multiple nodes for backup data, which reduces the risk of transaction data being tampered with and lost. At the same time, the refund, change and claim settlement rules of the bill platform are stored on the blockchain through smart contracts. The refund, change and claim settlement can be automatically executed without the participation of a third party, which improves the claim settlement efficiency, is conducive to the effective protection of user rights and interests, and improves the credibility of the bill platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0018] Figure 1 This is a schematic diagram of the structure of a blockchain provided by an embodiment of the present application;
[0019] Figure 2 It is a schematic diagram of an interactive process of a method for processing bill data provided by an embodiment of the present application;
[0020] Figure 3 It is a flowchart of a method for processing bill data provided by an embodiment of the present application;
[0021] Figure 4 It is a flowchart of another method for processing bill data provided by an embodiment of the present application;
[0022] Figure 5 It is a structural schematic diagram of a blockchain node device provided in an embodiment of the present application;
[0023] Figure 6 It is a structural schematic diagram of another blockchain node device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0024] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.
[0025] The bill platform includes various types of bill purchase platforms, which can be the official bill purchase platform or the third-party bill purchase platform. The bills include transportation bills, such as airline tickets, train tickets, bus tickets, boat tickets, etc., and also include catering tickets, scenic spot tickets, commodity bills, etc., without any limitation here. The traditional bill refund and change rules include the refund and change rules issued by the official bill platform and the refund and change rules issued by the third-party bill platform, but the bill purchase information and the refund and change rules are stored in the official bill platform or the third-party platform's own server, and there is a risk of data tampering or loss. Once the data is tampered with or lost, it will have a great impact on the user's rights and interests, and the data is not open and transparent. When a dispute occurs between the user and the bill platform, it takes a long time and is difficult to resolve the dispute. This application provides a decentralized multi-node device backup information data method based on blockchain technology. In order to reduce the risk of data tampering or loss, the refund and change claims rules of the bill platform are stored on the blockchain through smart contracts, and the refund and change claims can be automatically executed without the participation of a third party, which greatly improves the efficiency of claims.
[0026] The present application provides a method for processing bill data based on blockchain, aiming to solve the risk of data tampering or loss caused by the traditional storage of bill data in the bill platform's own server, as well as the problem of complex refund, change and claim processing, low efficiency and difficulty in dispute resolution. The bill platform includes an official bill purchase platform and a third-party bill purchase platform. After the bill platform is connected to the blockchain, the bill purchase information and the bill platform's refund, change and claim rules are deployed on the blockchain in the form of smart contracts. When users purchase bills, they can use the application, webpage and other service portals provided by the bill platform to realize bill purchase, change and claim services. The bill platform's server establishes a communication connection with the first blockchain node device in the blockchain, and uploads the bill purchase information, purchase, change and claim data to the blockchain for storage through transactions, which is convenient for subsequent protection of user rights and interests, and when disputes arise between users and the bill platform, valid data can be obtained from the blockchain as evidence.
[0027] The embodiment of the present application introduces blockchain technology into the data storage of refund, change and claim settlement of the bill platform, and proposes a method for processing bill data, which is applied to the first blockchain node device. The method for processing bill data is specifically: receiving the first transaction data sent by the bill platform, the first transaction data is generated after the target user purchases the bill on the bill platform, and the first transaction data includes: the bill summary data of the purchased bill, the target contract information address information, the bill platform identifier and the target user identifier; searching the bill contract information from the blockchain according to the target contract information address information, and verifying the bill platform identifier according to the found bill contract information; if the verification passes, adding a mark to the bill summary data, and packaging the mark, the bill summary data and the target user identifier to obtain the second transaction data, the mark is used to indicate that the bill summary data is in a valid state; the second transaction data is processed on the chain.
[0028] Blockchain is a distributed ledger that combines data blocks in a sequential manner in chronological order to form a chain data structure, and uses cryptography to ensure that the data cannot be tampered with or forged. Multiple independent distributed nodes (i.e., the first blockchain node device) save the same records. Blockchain technology has achieved decentralization and has become the cornerstone of trusted digital asset storage, transfer, and transactions.
[0029] by Figure 1 Take the structural diagram of the blockchain shown in the figure as an example. Whenever new data needs to be written into the blockchain, the data will be aggregated into a block and added to the end of the existing blockchain. The consensus algorithm ensures that the newly added blocks of each node are exactly the same. Each block records the platform protocol data and / or activity announcement data, and also contains the hash value of the previous block. All blocks save the hash value in the previous block in this way, and are connected in sequence to form a blockchain. The hash value of the previous block will be stored in the block header of the next block in the blockchain. When the transaction data in the previous block changes, the hash value of this block will also change. Therefore, the transaction data uploaded to the blockchain network is difficult to be tampered with. The transaction between the client and the bill platform on the blockchain realizes the openness and transparency of the transaction process and improves the reliability of the transaction data.
[0030] In order to better understand the method for processing bill data and related equipment disclosed in the embodiment of the present application, the blockchain system applicable to the embodiment of the present application is first described below.
[0031] See also Figure 2 , Figure 2 Schematic diagram of an interactive process of a method for processing bill data disclosed in an embodiment of the present application. Figure 2 As shown, after the target user logs in to the account of the bill platform through the client, S201, he can purchase bills on the bill platform. After the purchase is completed, the target user's ticket purchase information is obtained, and the ticket purchase information includes the bill platform identifier and the target user identifier. S202 The bill platform generates bill summary data based on the ticket purchase information. S203 and sends the first transaction data to the first blockchain node device. It can be seen that the first transaction data is generated after the target user purchases the bill on the bill platform, and the first transaction data includes the bill summary data of the bill purchased by the target user, the target contract information address information, the bill platform identifier and the target user identifier. The bill summary data is the summary hash obtained by the bill platform after the bill platform performs a hash algorithm on the bill platform identifier and the target user identifier. The target contract information address information is used to indicate the storage address of the refund and change claim rules stored on the blockchain by the bill platform. The bill platform identifier is used to indicate the platform where the target user purchases the bill, and the target user identifier indicates the purchase account of the target user. S204 After receiving the first transaction data, the first blockchain node device first searches the blockchain for the bill contract information storing the bill platform refund, change and claim settlement rules according to the target contract information address information, and verifies whether the bill platform can change the bill contract information. If so, it adds a mark to the bill summary data, and packages the marked bill summary data and the target user identifier to obtain the second transaction data. S205 stores the second transaction data in the blockchain, and S206 then feeds back the user's purchase result to the bill platform. At this time, the bill summary data is in a valid state, indicating that the user has successfully completed the bill purchase.
[0032] In one implementation, the first blockchain node device may be any blockchain node device in the blockchain network. The first blockchain node device may also be the blockchain node device that is closest to the server associated with the bill platform. The first blockchain node device may also be the blockchain node device that has the best communication quality with the server associated with the bill platform. This application does not limit this.
[0033] In one implementation, the first blockchain node device is obtained by election of other consensus node devices in the blockchain network according to a consensus algorithm, wherein the consensus algorithm includes but is not limited to a Proof of Work (PoW) algorithm, a Proof of Stake (PoS) algorithm, a Delegated Proof of Stake (DPoS) algorithm, a Practical Byzantine Fault Tolerance (PBFT) algorithm, etc. The first blockchain node device 203 may also be obtained by periodic election through a consensus algorithm, and the first blockchain node devices 203 obtained by election in different periods may be the same or different.
[0034] Among them, the method for processing ticket data provided in the embodiment of the present application can be applied to any of the following scenarios: refund, change and claim settlement of transportation tickets based on smart contracts, refund, change and claim settlement of catering tickets based on smart contracts, refund, change and claim settlement of commodity tickets based on smart contracts, refund, change and claim settlement of tourist attraction tickets based on smart contracts, etc.
[0035] It can be understood that the system for processing bill data described in the embodiment of the present application is for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. A person of ordinary skill in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.
[0036] based on Figure 2 For a schematic diagram of the architecture of the bill data processing system, see Figure 3 , Figure 3 : is a flow chart of a method for processing bill data provided by an embodiment of the present application. The bill platform in the method may be an official bill sales platform and a third-party bill sales platform, etc. The method includes but is not limited to the following steps S301 to S304:
[0037] S301. The first blockchain node device receives first transaction data sent by the bill platform. The first transaction data is generated after the target user purchases a bill on the bill platform. The first transaction data includes: bill summary data of the purchased bill, target contract information address information, bill platform identifier and target user identifier.
[0038] In the specific implementation, after the target user purchases the bill through the bill purchase application, the bill platform will generate bill summary data based on the bill purchase information. The purchase information includes the bill platform identifier and the target user identifier. The summary data can be a summary hash of the purchase information after the hash algorithm is applied. The service platform can upload the summary data to the blockchain in the form of a transaction, thereby realizing the on-chain storage of relevant information such as the user's bill purchase completion. Specifically, the bill platform can send the first transaction data to the first blockchain node device, wherein the first transaction data includes summary data, target contract information address information, bill platform identifier and target user identifier.
[0039] In one implementation, the method further includes: receiving a refund, change and claim registration request sent by the bill platform, the refund, change and claim registration request including third transaction data, the third transaction data including a bill platform identifier and a first refund, change and claim rule; verifying the third transaction data, and after the verification passes, determining whether the first refund, change and claim rule of the bill platform has been uploaded to the blockchain according to the bill platform identifier; if not, generating target contract information address information, and writing the bill contract information to the first cache of the blockchain according to the target contract information address information, the bill contract information including the third transaction data; sending the third transaction data to other consensus blockchain node devices in the blockchain network; when the blockchain consensus passes, writing the first cache to the consensus ledger of the blockchain, and sending the target contract information address information to the bill platform. Before the user purchases the bill, the first blockchain node device receives the refund, change and claim registration request sent by the bill platform, mainly to store the refund, change and claim rule of the bill platform on the chain.
[0040] In the specific implementation, the third transaction data includes the bill platform identifier and the first refund, change and claim settlement rule. After the third transaction data is verified, it can be determined whether the bill platform has stored the first refund, change and claim settlement rule on the chain according to the bill platform identifier. If so, there is no need to chain it again. If not, the target contract information address information is generated, and the bill contract information is temporarily written into the first cache of the blockchain to be included. At this time, the third transaction data is sent to other consensus blockchain node devices in the blockchain. When the consensus is passed, the first cache, that is, the bill contract information, can be directly written into the consensus ledger of the blockchain, thereby completing the on-chain storage of the first refund, change and claim settlement rule, and the first refund, change and claim settlement rule can be found through the target contract information address information.
[0041] In one implementation, the method also includes: receiving a refund, change and claim update request sent by the bill platform, the refund, change and claim update request including fourth transaction data, the fourth transaction data including a bill platform identifier, a second refund, change and claim rule and the target contract information address information; verifying the fourth transaction data, and after the verification is passed, determining whether the first refund, change and claim rule is already stored in the blockchain according to the target contract information address information; if so, determining whether the first refund, change and claim rule can be updated according to the bill platform identifier; if so, writing the second refund, change and claim rule into the second cache, and marking the first refund, change and claim rule as invalid and adding a modification record; sending the fourth transaction data to other consensus blockchain node devices in the blockchain network; when the blockchain consensus is passed, writing the second cache into the consensus ledger of the blockchain, and sending the target contract information address information to the bill platform. Before the user purchases the bill, the first blockchain node device may also receive a refund, change and claim update request sent by the bill platform. When the bill platform wants to modify the first refund, change and claim rule that has been uploaded to the chain, it can send a refund, change and claim update request including the fourth transaction data to the first blockchain node device. The fourth transaction data includes the bill platform identifier, the second refund, change and claim rule and the target contract information address information.
[0042] In the specific implementation, after the fourth verification data is verified, it is determined whether the first refund, change and claim settlement rule is already stored in the blockchain according to the target contract information address information. If not, no processing is required. If so, the second refund, change and claim settlement rule can be written into the second cache, and the fourth transaction data can be sent to other consensus node devices in the blockchain. After reaching a consensus, the second cache can be written into the consensus ledger, and the target contract information address information can be sent to the bill platform. At this time, the second refund, change and claim settlement rule stored in the bill contract information address in the blockchain is valid, and the first refund, change and claim settlement rule is invalid, but it is still stored in the blockchain, and the modification record can be viewed, which is conducive to the subsequent data recovery. The second refund, change and claim settlement rule can be directly replaced with the first refund, change and claim settlement rule.
[0043] S302. The first blockchain node device searches for the bill contract information from the blockchain according to the target contract information address information, and verifies the bill platform identifier according to the found bill contract information.
[0044] In one implementation, the verification of the bill platform identifier according to the found bill contract information includes: searching for the bill platform identifier in the bill contract information; if so, determining that the bill platform has the right to modify the bill contract information. The first blockchain node device searches the blockchain for the bill contract information pre-stored on the blockchain by the bill platform according to the target contract information address information in the first transaction data, thereby verifying the bill platform identifier according to the bill contract information. The verification can determine whether the bill platform has the right to modify the bill contract information. Specifically, it can be to search for the bill platform identifier in the bill contract information. If it exists, it indicates that the bill platform has the right to modify the bill contract information.
[0045] S303. If the verification passes, the first blockchain node device adds a mark to the bill summary data, and packages the mark, the bill summary data and the target user identifier to obtain second transaction data, wherein the mark is used to indicate that the bill summary data is in a valid state.
[0046] In the specific implementation, after the verification is passed, the first blockchain node device adds a mark to the summary number. The summary data after adding the mark is in a valid state, which can indicate that the target user has successfully purchased the ticket and the ticket purchased by the target user is valid. The summary data and the target user identifier are packaged to obtain the second transaction data.
[0047] S304. The first blockchain node device processes the second transaction data on the chain.
[0048] In one implementation, the method further includes: receiving a ticket change request sent by the ticket platform, the ticket change request including fifth transaction data, the fifth transaction data including the first ticket summary data submitted by the target user to the ticket platform when purchasing the ticket, the target contract information address information, the ticket platform identifier, and the target user identifier; searching the ticket contract information according to the target contract information address information, and verifying the ticket platform identifier according to the ticket contract information; if the verification passes, searching the ticket summary data according to the target user identifier; when detecting that the first ticket summary data and the ticket summary data match, determining whether the ticket change request complies with the second refund and change claim settlement rule; if so, marking the ticket summary data as a change state, and processing the fifth transaction data on the chain. After the user successfully purchases the ticket, there may be a situation where he wants to refund or change the ticket. At this time, the user can send a ticket change request to the ticket platform through the client, and the ticket platform sends the ticket change request to the first blockchain node device, and the ticket change request carries the fifth transaction data. The first blockchain node device can process the ticket change request initiated by the target user according to the fifth transaction data and inform the user of the processing result.
[0049] In the specific implementation, the fifth transaction data includes the first bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, and the target user identifier. The bill contract information can be found in the blockchain consensus ledger based on the target contract information address information, and then it is determined whether the bill platform has the authority to modify the bill contract information based on the bill platform identifier. If so, the bill summary data is found from the bill contract information based on the target user identifier. At this time, it is only necessary to verify whether the first bill summary data submitted by the user matches the bill summary data stored in the blockchain. If it matches, it indicates that the first bill summary data submitted by the target user is accurate and the target user has not modified it privately. Therefore, it is only necessary to further verify whether the bill change request complies with the second refund and change claim rule in the bill contract information. If it does, the summary data will be marked as a changed state and the fifth transaction data will be stored in the blockchain.
[0050] In a specific implementation, the method further includes: receiving second bill summary data sent by the bill platform, the second bill summary data being summary data generated by the bill platform according to the bill platform identifier and the target user identifier; and determining whether the second bill summary data matches the first bill summary data. When the bill platform receives a bill change request submitted by a user including the fifth transaction data, it verifies the first bill summary in the fifth transaction data. The bill platform performs a hash calculation on the bill platform identifier and the target user tag according to a preset hash algorithm to obtain the second bill summary data. At this time, the bill platform sends the second bill summary data to the first blockchain node device. The first blockchain node device detects whether the first bill summary data submitted by the target user matches the second bill summary data submitted by the target user. If they match, the verification passes, and the first bill summary data submitted by the user can be considered valid.
[0051] In one implementation, the method further includes: receiving a bill claim request sent by the bill platform, the claim request including sixth transaction data, the sixth transaction data including the second bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, and the target user identifier; searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information; if the verification passes, searching for the bill summary data according to the target user identifier; when it is detected that the second bill summary data and the bill summary data match, determining whether the bill claim request complies with the second refund and change claim rule; if so, marking the bill summary data as a claim status, and processing the sixth transaction data on the chain. When the target user initiates a claim request to the bill platform, the bill platform sends the claim request submitted by the user to the first blockchain node device, and the claim request includes the sixth transaction data, so that the first blockchain node device can process the claim request initiated by the target user according to the sixth transaction data.
[0052] In the specific implementation, the sixth transaction data includes the second bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier and the target user identifier. The first blockchain node device searches the bill contract information from the blockchain according to the target contract address information, and determines whether the bill platform has the authority to modify the bill contract information according to the bill platform identifier. If so, the bill summary data is searched from the bill contract information according to the target user identifier. Thus, the second bill summary data submitted by the user and the bill summary data pre-stored on the chain are matched. After the match is successful, it is verified whether the bill claim request complies with the second refund, change and claim rules. If it does, the sixth transaction data is stored in the blockchain, and the bill summary data is marked as a claim status.
[0053] In one implementation, the method further includes: receiving the seventh transaction data sent by the bill platform, the seventh transaction data including the first bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, the target user identifier and financial claim data; searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information; if the verification passes, searching for the bill summary data according to the target user identifier; when it is detected that the second bill summary data and the bill summary data match, determining whether the bill summary data is marked as a claim status; if so, marking the bill summary data as a claim completion status, and processing the seventh transaction data on the chain. After the claim is completed, the first blockchain node device will receive the seventh transaction data sent by the bill platform, and make a claim to the target user based on the seventh transaction data.
[0054] In the specific implementation, the seventh transaction data includes the second bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, the target user identifier and the financial claim data. The first blockchain node device first searches for the bill contract information according to the target contract information address information, and then determines whether the bill platform can modify the bill contract information according to the bill platform identifier. If so, the bill summary data is found according to the target user identifier. When it is detected that the second bill summary data submitted by the target user matches the bill summary data, it is determined whether the bill summary data has been marked as a claim status. If so, the summary data is marked as a claim completion status, thereby storing the seventh transaction data in the blockchain.
[0055] The embodiment of the present application proposes a method for processing bill data, which is applied to a first blockchain node device. The first blockchain node device first receives the first transaction data sent by the bill platform. The first transaction data is generated after the target user purchases the bill on the bill platform. The first transaction data includes: the bill summary data of the purchased bill, the target contract information address information, the bill platform identifier and the target user identifier. Then, the bill contract information is searched from the blockchain according to the target contract information address information, and the bill platform identifier is verified according to the found bill contract information. If the verification passes, a mark is added to the bill summary data, and the mark, the bill summary data and the target user identifier are packaged to obtain the second transaction data. The mark is used to indicate that the bill summary data is in a valid state, and finally the second transaction data is processed on the chain. Based on the blockchain, the transaction data of the bill platform is decentralized to multi-node backup data, which reduces the risk of transaction data being tampered with and lost. At the same time, the refund, change and claim settlement rules of the bill platform are stored on the blockchain through smart contracts. The refund, change and claim settlement can be automatically executed without the participation of a third party, which improves the claim settlement efficiency, is conducive to the effective protection of user rights and interests, and improves the credibility of the bill platform.
[0056] See also Figure 4 , Figure 4 This is a flow chart of another method for processing bill data provided by an embodiment of the present application. The method is applied to a first blockchain node device, and the method includes but is not limited to the following steps S401 to S405:
[0057] S401. The first blockchain node device receives first transaction data sent by the bill platform. The first transaction data is generated after the target user purchases a bill on the bill platform. The first transaction data includes: bill summary data of the purchased bill, target contract information address information, bill platform identifier and target user identifier.
[0058] S402. The first blockchain node device searches for the bill contract information from the blockchain according to the target contract information address information, and verifies the bill platform identifier according to the found bill contract information.
[0059] S403: If the first blockchain node device passes the verification, a mark is added to the bill summary data, and the mark, the bill summary data and the target user identifier are packaged to obtain second transaction data, where the mark is used to indicate that the bill summary data is valid.
[0060] S404. The first blockchain node device sends the second transaction data to other consensus blockchain node devices in the blockchain network, so that the other consensus blockchain node devices perform blockchain consensus on the second transaction data.
[0061] The specific details of steps S401 to S404 in the embodiment of the present application may refer to the execution process of steps S301 to S304 in the above embodiment, and will not be described in detail in the embodiment of the present invention.
[0062] S405. When the blockchain consensus is passed, the first blockchain node device stores the second transaction data in the consensus ledger of the blockchain.
[0063] In the specific implementation, the first blockchain node device sends the second transaction data to other consensus blockchain node devices of the blockchain network. After other blockchain node devices reach a consensus on the second transaction data, the first blockchain node device uploads the second transaction data to the consensus ledger of the blockchain. At the same time, a notification message is fed back to the bill platform. The notification message is mainly used to inform the target user that the bill has been successfully purchased and the user's bill purchase is valid.
[0064] In one embodiment, after receiving the first transaction data, the first blockchain node device will also verify the first transaction data, specifically including: detecting whether the bill platform indicated by the bill platform identifier exists; if so, detecting whether the user account indicated by the target user identifier exists, and whether the transaction credit score of the user account is greater than a preset threshold; if so, passing the verification. If the bill platform really exists, and the user account of the target user really exists, and the target user's transaction credit score is high, the first transaction data is considered valid. If the target user is a blacklisted user of the bill platform, or a low-credit user, the first transaction data can be considered invalid. Among them, the first blockchain node device can be a server or a server cluster of the bill platform, and is connected to the blockchain.
[0065] The embodiment of the present application proposes a method for processing bill data, which is applied to a first blockchain node device. The first blockchain node device first receives the first transaction data sent by the bill platform. The first transaction data is generated after the target user purchases the bill on the bill platform. The first transaction data includes: the bill summary data of the purchased bill, the target contract information address information, the bill platform identifier and the target user identifier. Then, the bill contract information is searched from the blockchain according to the target contract information address information, and the bill platform identifier is verified according to the found bill contract information. If the verification passes, a mark is added to the bill summary data, and the mark, the bill summary data and the target user identifier are packaged to obtain the second transaction data. The mark is used to indicate that the bill summary data is in a valid state, and finally the second transaction data is processed on the chain. Based on the blockchain, the transaction data of the bill platform is decentralized to multiple nodes for backup data, which reduces the risk of transaction data being tampered with and lost. At the same time, the refund, change and claim settlement rules of the bill platform are stored on the blockchain through smart contracts, and the refund, change and claim settlement can be automatically executed without the participation of a third party, which improves the claim settlement efficiency, is conducive to the effective protection of user rights and interests, and improves the credibility of the bill platform.
[0066] In order to more clearly understand a method for processing ticket data provided by an embodiment of the present invention, a method for processing ticket data applied in a flight refund, change and claim settlement scenario is described in detail. The method for processing ticket data may include: the airline's chain-up process for storing refund, change and claim settlement rules, the airline's modification process for refund, change and claim settlement rules that have been chained, the chain-up process for ticket purchase, the chain-up process for ticket refund, the chain-up process for ticket change and the ticket claim settlement process.
[0067] The airline’s process of putting the refund and change claim rules on the blockchain is as follows:
[0068] Airlines need to deploy flight refund, change and claim rules in the form of smart contracts on the blockchain through transactions. The content includes: airline identification, flight refund, change and claim rules customized by the airline. After the blockchain receives the above transaction, it verifies the legitimacy of the transaction. After the verification, during the execution process, it checks whether the flight refund, change and claim contract has been deployed through the airline identification in the transaction. If so, the execution failure result is returned; if not, the address information is generated for the contract and the flight refund, change and claim contract is written into the blockchain cache. After other blockchain node devices in the blockchain network reach a consensus, the contract written into the blockchain cache is written into the ledger and the contract deployment result is returned. If successful, the result will contain the contract address information.
[0069] The airline’s modification process for the refund, change and claim settlement rules that have been uploaded to the blockchain is as follows:
[0070] The airline deploys the new flight refund, change and claim settlement rules in the form of smart contracts on the blockchain through transactions. The content includes the airline identification, the new flight refund, change and claim settlement rules, and the old version of the contract address information. After receiving the transaction, the blockchain verifies the legitimacy of the transaction. After the verification is passed, the virtual machine is called to execute the transaction. During the execution process, the old version address information is used to check whether there is a flight contract deployment. If not, a failure result is returned; check whether the airline identification in the transaction has the authority to modify the old version of the flight contract. If not, a failure result is returned; after the verification is passed, the new flight contract is written into the blockchain cache, and the old version of the flight contract is marked as invalid, and the modification operation is recorded. The above execution results are subjected to blockchain consensus. After consensus is reached, the above cached results are written into the ledger and the final result is returned to the airline.
[0071] The process of purchasing air tickets on the blockchain is as follows:
[0072] After the user purchases the ticket, the ticket purchase information will be uploaded to the chain. After the user successfully purchases the ticket through the APP entrance, the service platform will generate ticket information containing the digital signatures of the airline and the user. The service platform will send the summary data of the ticket information to the blockchain in the form of a transaction. The transaction content mainly includes the ticket summary data, the flight contract address information deployed above, the airline ID, the user ID, etc. After the blockchain receives the transaction data, it verifies the legality of the transaction, that is, verifies the digital signatures of the airline and the user at the same time. After the verification is passed, the virtual machine is called to execute the ticket purchase transaction. During the execution process, the contract is searched through the flight contract address information in the transaction. If it is not found, the execution failure result is returned; if it is found, then it is determined whether the airline ID has the authority to modify the contract. If not, the execution failure result is returned; if all the verifications pass, the above ticket summary data is marked as valid, and based on the user ID as the keyword, the ticket summary data and the status as the value, it is written into the contract, and the above results are subjected to blockchain consensus. After reaching a consensus, the results are written into the ledger, and the final results are returned to the user and the airline. Subsequent users can query the ticket status on the blockchain through the summary data.
[0073] The ticket refund chain process is as follows:
[0074] After the user purchases the air ticket, he can make a refund, change or claim through the above APP entrance. Taking refund as an example, when the user applies for a refund, he provides the above ticket summary data, ticket information, and user ID. After receiving the refund application, the airline server extracts the summary data of the ticket information and then sends it to the blockchain through a transaction. The transaction content includes the summary data provided by the user, the summary data extracted by the airline from the ticket information, the user ID, the airline ID, the flight contract address information deployed above, etc. After the blockchain receives the transaction, it verifies the legality of the transaction. After the verification is passed, the virtual machine is called to execute the refund transaction. During the execution process, first compare whether the ticket summary data entered by the user is the same as the ticket summary data generated by the airline. If not, the execution failure result is returned; the contract is searched through the flight contract address information in the transaction. If not found, the execution failure result is returned; if found, then determine whether the airline ID has the authority to modify the contract. If not, the execution failure result is returned; then query the user's ticket information through the user ID. If not found, the execution failure is returned; then check whether it matches the summary data entered by the user. If not, the execution failure is returned; finally, check whether the refund behavior complies with the flight contract rules. If not, the execution failure is returned. After all the above checks are passed, the ticket summary status will be marked as refunded, and the refund operation will be recorded. The above results will be subjected to blockchain consensus. After consensus is reached, the results will be written into the ledger and returned to the user and the airline.
[0075] The process of ticket change on-chain is as follows:
[0076] When a user needs to change a ticket, the user provides the purchased ticket summary data, user ID and new ticket information when applying for the change. After receiving the change application, the airline server sends it to the blockchain through a transaction. The transaction content includes the summary data provided by the user, the summary data extracted by the airline for the new ticket information, the user ID, the airline ID, the flight contract address information deployed above, etc. After receiving the transaction, the blockchain verifies the legality of the transaction. After the verification is passed, the virtual machine is called to execute the change transaction. During the execution process, first compare whether the ticket summary data entered by the user is the same as the ticket summary data generated by the airline. If the same, the execution failure result is returned; the contract is searched through the flight contract address information in the transaction. If not found, the execution failure result is returned; if found, then determine whether the airline ID has the authority to modify the contract. If not, the execution failure result is returned; then query the user's ticket information through the user ID. If not found, the execution failure is returned; then check whether it matches the summary data entered by the user. If not, the execution failure is returned; finally, check whether the ticket change behavior complies with the flight contract rules. If not, the execution failure is returned. After all the above checks are passed, the original ticket summary data is marked as changed, and the new ticket summary data is written. At the same time, the change operation is recorded, and the above results are subjected to blockchain consensus. After consensus is reached, the results are written into the ledger and returned to the user and the airline. The user can verify the ticket on the blockchain through the new ticket summary data.
[0077] The air ticket claim process is as follows:
[0078] For some reasons, users can make claims based on flight rules. In this case, when users make claims, they provide ticket summary data and user ID. After the airline server receives the claim application, it is sent to the blockchain through a transaction. The transaction content includes the summary data provided by the user, the user ID, the airline ID, the flight contract address information deployed above, etc. After the blockchain receives the transaction, it verifies the legality of the transaction. After the verification passes, the virtual machine is called to execute the claim transaction. During the execution process, the contract is searched through the flight contract address information in the transaction. If not found, the execution failure result is returned; if found, then determine whether the airline ID has the authority to modify the contract. If not, the execution failure result is returned; then query the user's ticket information through the user ID. If not found, the execution failure is returned; then check whether it matches the summary data entered by the user. If not, the execution failure is returned; finally, check whether the claim behavior complies with the flight contract rules. If not, the execution failure is returned. After all the above checks are passed, the claim result is generated according to the claim rules, and the ticket summary data is marked as the status in the claim process, the claim operation is recorded, and the above results are subjected to blockchain consensus. After consensus is reached, the results are written into the ledger. After the aviation server receives the claim result, it notifies the airline's financial system to make a claim. After the financial system completes the claim, the status of the ticket summary data on the blockchain is modified through transactions. The transaction content includes the summary data provided by the user, the financial claim data, the user ID, the airline ID, the flight contract address information deployed above, etc. After the blockchain receives the transaction, it verifies the legitimacy of the transaction. After the verification is passed, the virtual machine is called to execute the transaction. During the execution process, the flight contract address information in the transaction is used to modify the status of the ticket summary data on the blockchain. If not found, the result of execution failure is returned. If found, then determine whether the airline ID has the authority to modify the contract. If not, the result of execution failure is returned. Then query the user's ticket information through the user ID. If not found, the result of execution failure is returned. Then check whether it matches the summary data entered by the user. If not, the result of execution failure is returned. Check whether the status of the ticket summary data is in the claim process. If not, the result of execution failure is returned. After all the above checks are passed, mark the ticket summary data as the claim completion status, record the financial claim data operation, and conduct blockchain consensus on the above results. After consensus is reached, write the result into the ledger and return the claim result to the user and the airline.
[0079] See also Figure 5 , Figure 5 is a schematic diagram of a blockchain node device provided in an embodiment of the present application, wherein the blockchain node device is used to execute Figure 2~Figure 4The steps performed by the first blockchain node device in the corresponding method embodiment include: one or more processors 501; one or more input devices 502, one or more output devices 503 and a memory 504. The processor 501, input device 502, output device 503 and memory 504 are connected via a bus 505. The memory 502 is used to store a computer program, and the computer program includes program instructions. The processor 501, input device 502, and output device 503 are used to execute the program instructions stored in the memory 504, and perform the following operations:
[0080] The input device 502 receives first transaction data sent by the bill platform, the first transaction data is generated after the target user purchases a bill on the bill platform, and the first transaction data includes: bill summary data of the purchased bill, target contract information address information, bill platform identifier, and target user identifier;
[0081] The processor 501 searches for the bill contract information from the blockchain according to the target contract information address information, and verifies the bill platform identifier according to the found bill contract information;
[0082] If the verification is successful, the processor 501 adds a mark to the bill summary data, and packages the mark, the bill summary data and the target user identifier to obtain second transaction data, wherein the mark is used to indicate that the bill summary data is valid;
[0083] The processor 501 performs on-chain processing on the second transaction data.
[0084] In one implementation, the processor 501 further includes:
[0085] Receiving a refund, change, and claim settlement registration request sent by the ticket platform, wherein the refund, change, and claim settlement registration request includes third transaction data, and the third transaction data includes a ticket platform identifier and a first refund, change, and claim settlement rule;
[0086] Verifying the third transaction data, and after the verification passes, determining whether the first refund, change and claim settlement rule of the bill platform has been uploaded to the blockchain according to the bill platform identifier;
[0087] If not, generate target contract information address information, and write the bill contract information into the first cache of the blockchain according to the target contract information address information, wherein the bill contract information includes the third transaction data;
[0088] Sending the third transaction data to other consensus blockchain node devices in the blockchain network;
[0089] When the blockchain consensus is passed, the first cache is written into the consensus ledger of the blockchain, and the target contract information address information is sent to the bill platform.
[0090] In one implementation, the processor 501 further includes:
[0091] Receive a refund, change and claim settlement update request sent by the bill platform, wherein the refund, change and claim settlement update request comprises fourth transaction data, wherein the fourth transaction data comprises a bill platform identifier, a second refund, change and claim settlement rule and the target contract information address information;
[0092] Verifying the fourth transaction data, and after the verification passes, determining whether the first refund, change and claim settlement rule has been stored in the blockchain according to the target contract information address information;
[0093] If yes, determine whether the first refund, change and claim settlement rule can be updated according to the ticket platform identifier;
[0094] If yes, write the second refund, change and claim settlement rule into the second cache, mark the first refund, change and claim settlement rule as invalid and add a modification record;
[0095] Sending the fourth transaction data to other consensus blockchain node devices in the blockchain network;
[0096] When the blockchain consensus is passed, the second cache is written into the consensus ledger of the blockchain, and the target contract information address information is sent to the bill platform.
[0097] In one implementation, the processor 501 further includes:
[0098] Receiving a bill change request sent by the bill platform, the bill change request including fifth transaction data, the fifth transaction data including first bill summary data submitted by a target user to the bill platform when purchasing a bill, the target contract information address information, the bill platform identifier, and the target user identifier;
[0099] Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information;
[0100] If the verification passes, searching the bill summary data according to the target user identifier;
[0101] When detecting that the first bill summary data matches the bill summary data, determining whether the bill change request complies with the second refund, change and claim settlement rule;
[0102] If so, the bill summary data is marked as a changed state, and the fifth transaction data is processed on the chain.
[0103] In one implementation, the processor 501 further includes:
[0104] receiving second bill summary data sent by the bill platform, where the second bill summary data is summary data generated by the bill platform according to the bill platform identifier and the target user identifier;
[0105] A determination is made as to whether the second ticket summary data matches the first ticket summary data.
[0106] In one implementation, the processor 501 further includes:
[0107] Receiving a bill claim request sent by the bill platform, the claim request including sixth transaction data, the sixth transaction data including second bill summary data submitted by a target user to the bill platform when purchasing a bill, the target contract information address information, the bill platform identifier, and the target user identifier;
[0108] Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information;
[0109] If the verification passes, searching the bill summary data according to the target user identifier;
[0110] When it is detected that the second bill summary data matches the bill summary data, determining whether the bill claim request complies with the second refund, change and claim settlement rule;
[0111] If so, the bill summary data is marked as a claim status, and the sixth transaction data is processed on the chain.
[0112] In one implementation, the processor 501 further includes:
[0113] receiving seventh transaction data sent by the bill platform, wherein the seventh transaction data includes second bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, the target user identifier, and financial claim data;
[0114] Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information;
[0115] If the verification passes, searching the bill summary data according to the target user identifier;
[0116] Upon detecting that the second bill summary data matches the bill summary data, determining whether the bill summary data is marked as a claim settlement status;
[0117] If so, the bill summary data is marked as claim completion status, and the seventh transaction data is uploaded to the chain.
[0118] In one implementation, when the processor 501 verifies the bill platform identifier according to the found bill contract information, the following steps are performed:
[0119] Finding whether the bill platform identifier exists in the bill contract information;
[0120] If so, it is determined that the bill platform has the authority to modify the bill contract information.
[0121] See also Figure 6 , Figure 6 is a schematic diagram of a blockchain node device provided in an embodiment of the present application, wherein the blockchain node device is used to execute Figure 2~Figure 4 The steps performed by the first blockchain node device in the corresponding method embodiment may include:
[0122] The receiving unit 601 is used to receive first transaction data sent by the bill platform, where the first transaction data is generated after the target user purchases a bill on the bill platform, and the first transaction data includes: bill summary data of the purchased bill, target contract information address information, bill platform identifier, and target user identifier;
[0123] Processing unit 602, configured to search for bill contract information from the blockchain according to the target contract information address information, and verify the bill platform identifier according to the found bill contract information;
[0124] The processing unit 602 is further configured to, if the verification is passed, add a mark to the bill summary data, and package the mark, the bill summary data and the target user identifier to obtain second transaction data, wherein the mark is used to indicate that the bill summary data is in a valid state;
[0125] The processing unit 602 is further used to process the second transaction data on a chain.
[0126] In one implementation, the processing unit 602 further includes:
[0127] Receiving a refund, change, and claim settlement registration request sent by the ticket platform, wherein the refund, change, and claim settlement registration request includes third transaction data, and the third transaction data includes a ticket platform identifier and a first refund, change, and claim settlement rule;
[0128] Verifying the third transaction data, and after the verification passes, determining whether the first refund, change and claim settlement rule of the bill platform has been uploaded to the blockchain according to the bill platform identifier;
[0129] If not, generate target contract information address information, and write the bill contract information into the first cache of the blockchain according to the target contract information address information, wherein the bill contract information includes the third transaction data;
[0130] Sending the third transaction data to other consensus blockchain node devices in the blockchain network;
[0131] When the blockchain consensus is passed, the first cache is written into the consensus ledger of the blockchain, and the target contract information address information is sent to the bill platform.
[0132] In one implementation, the processing unit 602 further includes:
[0133] Receive a refund, change and claim settlement update request sent by the bill platform, wherein the refund, change and claim settlement update request comprises fourth transaction data, wherein the fourth transaction data comprises a bill platform identifier, a second refund, change and claim settlement rule and the target contract information address information;
[0134] Verifying the fourth transaction data, and after the verification passes, determining whether the first refund, change and claim settlement rule has been stored in the blockchain according to the target contract information address information;
[0135] If yes, determine whether the first refund, change and claim settlement rule can be updated according to the ticket platform identifier;
[0136] If yes, write the second refund, change and claim settlement rule into the second cache, mark the first refund, change and claim settlement rule as invalid and add a modification record;
[0137] Sending the fourth transaction data to other consensus blockchain node devices in the blockchain network;
[0138] When the blockchain consensus is passed, the second cache is written into the consensus ledger of the blockchain, and the target contract information address information is sent to the bill platform.
[0139] In one implementation, the processing unit 602 further includes:
[0140] Receiving a bill change request sent by the bill platform, the bill change request including fifth transaction data, the fifth transaction data including first bill summary data submitted by a target user to the bill platform when purchasing a bill, the target contract information address information, the bill platform identifier, and the target user identifier;
[0141] Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information;
[0142] If the verification passes, searching the bill summary data according to the target user identifier;
[0143] When detecting that the first bill summary data matches the bill summary data, determining whether the bill change request complies with the second refund, change and claim settlement rule;
[0144] If so, the bill summary data is marked as a changed state, and the fifth transaction data is processed on the chain.
[0145] In one implementation, the processing unit 602 further includes:
[0146] receiving second bill summary data sent by the bill platform, where the second bill summary data is summary data generated by the bill platform according to the bill platform identifier and the target user identifier;
[0147] A determination is made as to whether the second ticket summary data matches the first ticket summary data.
[0148] In one implementation, the processing unit 602 further includes:
[0149] Receiving a bill claim request sent by the bill platform, the claim request including sixth transaction data, the sixth transaction data including second bill summary data submitted by a target user to the bill platform when purchasing a bill, the target contract information address information, the bill platform identifier, and the target user identifier;
[0150] Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information;
[0151] If the verification passes, searching the bill summary data according to the target user identifier;
[0152] When it is detected that the second bill summary data matches the bill summary data, determining whether the bill claim request complies with the second refund, change and claim settlement rule;
[0153] If so, the bill summary data is marked as a claim status, and the sixth transaction data is processed on the chain.
[0154] In one implementation, the processing unit 602 further includes:
[0155] receiving seventh transaction data sent by the bill platform, wherein the seventh transaction data includes second bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, the target user identifier, and financial claim data;
[0156] Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information;
[0157] If the verification passes, searching the bill summary data according to the target user identifier;
[0158] Upon detecting that the second bill summary data matches the bill summary data, determining whether the bill summary data is marked as a claim settlement status;
[0159] If so, the bill summary data is marked as claim completion status, and the seventh transaction data is uploaded to the chain.
[0160] In one implementation, when the processing unit 602 verifies the bill platform identifier according to the found bill contract information, it further includes:
[0161] Finding whether the bill platform identifier exists in the bill contract information;
[0162] If so, it is determined that the bill platform has the authority to modify the bill contract information.
[0163] A computer-readable storage medium is also provided in an embodiment of the present application. The computer-readable storage medium stores a computer program. The computer program includes program instructions. When the program instructions are executed by a processor, the steps performed in the above embodiment can be executed.
[0164] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.
[0165] The above disclosure is only part of the embodiments of the present application, which certainly cannot be used to limit the scope of rights of the present application. Ordinary technicians in this field can understand that all or part of the processes of implementing the above embodiments and making equivalent changes according to the claims of this application are still within the scope of the invention.
Claims
1. A method for processing bill data, characterized in that: The method is applied to a first blockchain node device, and the method includes: Receiving first transaction data sent by the bill platform, the first transaction data is generated after the target user purchases a bill on the bill platform, the first transaction data including: bill summary data of the purchased bill, target contract information address information, bill platform identifier, and target user identifier; Searching the bill contract information from the blockchain according to the target contract information address information, and verifying the bill platform identifier according to the found bill contract information, wherein the bill contract information includes the refund, change and claim settlement rules that are currently in a valid state corresponding to the bill platform identifier; If the verification is passed, a mark is added to the bill summary data of the purchased bill, and the mark, the bill summary data of the purchased bill and the target user identifier are packaged to obtain second transaction data, wherein the mark is used to indicate that the bill summary data of the purchased bill is in a valid state; Processing the second transaction data on a blockchain; Receiving a bill change request sent by the bill platform, the bill change request including fifth transaction data, the fifth transaction data including first bill summary data submitted by a target user to the bill platform when purchasing a bill, the target contract information address information, the bill platform identifier, and the target user identifier; Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information; If the verification passes, searching for the bill summary data of the purchased bill according to the target user identifier; When it is detected that the first bill summary data matches the bill summary data of the purchased bill, determining whether the bill change request complies with the refund, change and claim settlement rules that are currently in effect in the bill contract information; If so, the bill summary data of the purchased bill is marked as a changed state, and the fifth transaction data is processed on the chain.
2. The method according to claim 1, characterized in that The method further comprises: Receiving a refund, change, and claim settlement registration request sent by the ticket platform, wherein the refund, change, and claim settlement registration request includes third transaction data, and the third transaction data includes a ticket platform identifier and a first refund, change, and claim settlement rule; Verifying the third transaction data, and after the verification passes, determining whether the first refund, change and claim settlement rule of the bill platform has been uploaded to the blockchain according to the bill platform identifier; If not, generate target contract information address information, and write the bill contract information into the first cache of the blockchain according to the target contract information address information, wherein the bill contract information includes the third transaction data; Sending the third transaction data to other consensus blockchain node devices in the blockchain network; When the blockchain consensus is passed, the first cache is written into the consensus ledger of the blockchain, and the target contract information address information is sent to the bill platform.
3. The method according to claim 2, characterized in that The method further comprises: Receiving a refund, change, and claim settlement update request sent by the ticket platform, wherein the refund, change, and claim settlement update request includes fourth transaction data, and the fourth transaction data includes a ticket platform identifier, a second refund, change, and claim settlement rule, and the target contract information address information; Verifying the fourth transaction data, and after the verification passes, determining whether the first refund, change and claim settlement rule has been stored in the blockchain according to the target contract information address information; If yes, determine whether the first refund, change and claim settlement rule can be updated according to the ticket platform identifier; If yes, write the second refund, change and claim settlement rule into the second cache, mark the first refund, change and claim settlement rule as invalid and add a modification record; Sending the fourth transaction data to other consensus blockchain node devices in the blockchain network; When the blockchain consensus is passed, the second cache is written into the consensus ledger of the blockchain, and the target contract information address information is sent to the bill platform.
4. The method according to any one of claims 1 to 3, characterized in that: After receiving the bill change request sent by the bill platform, the method further includes: receiving second bill summary data sent by the bill platform, where the second bill summary data is summary data generated by the bill platform according to the bill platform identifier and the target user identifier; determining whether the second bill summary data matches the first bill summary data; If they match, it is determined that the first bill summary data is valid.
5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Receiving a bill claim request sent by the bill platform, the claim request including sixth transaction data, the sixth transaction data including second bill summary data submitted by a target user to the bill platform when purchasing a bill, the target contract information address information, the bill platform identifier, and the target user identifier; Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information; If the verification passes, searching for the bill summary data of the purchased bill according to the target user identifier; When it is detected that the second bill summary data matches the bill summary data of the purchased bill, determining whether the bill claim request complies with the refund, change and ticket claim rules that are currently in effect in the bill contract information; If so, the bill summary data of the purchased bill is marked as a claim status, and the sixth transaction data is processed on the chain.
6. The method according to claim 5, characterized in that The method further comprises: receiving seventh transaction data sent by the bill platform, wherein the seventh transaction data includes second bill summary data submitted by the target user to the bill platform when purchasing the bill, the target contract information address information, the bill platform identifier, the target user identifier, and financial claim data; Searching for the bill contract information according to the target contract information address information, and verifying the bill platform identifier according to the bill contract information; If the verification passes, searching for the bill summary data of the purchased bill according to the target user identifier; Upon detecting that the second bill summary data matches the bill summary data of the purchased bill, determining whether the bill summary data of the purchased bill is marked as a claim settlement status; If so, the bill summary data of the purchased bill is marked as a claim completion status, and the seventh transaction data is processed on the chain.
7. The method according to claim 1, characterized in that The verifying the bill platform identifier according to the found bill contract information includes: Finding whether the bill platform identifier exists in the bill contract information; If so, it is determined that the bill platform has the authority to modify the bill contract information.
8. A server, characterized in that: The invention comprises a processor, an input device, an output device and a memory, wherein the processor, the input device, the output device and the memory are interconnected, wherein the memory is used to store a computer program, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the method for processing bill data as described in any one of claims 1 to 7.
9. A computer storage medium, characterized in that The computer storage medium stores computer program instructions, and the computer program instructions are suitable for being loaded by a processor and executing the method for processing bill data according to any one of claims 1 to 7.
Citation Information
Patent Citations
Electronic bill management method and device
CN106952094A
Aircraft delay compensation method and system, server and computer readable storage medium
CN109242674A
Data processing method and device for electronic tickets, storage medium and device
CN109325812A
Aviation delay risk processing method, device and apparatus based on block chain technology
CN109493236A
A claim settlement method and device based on a block chain
CN109614438A
