WO2020233087A1 - 票据数据回退方法和系统 - Google Patents

票据数据回退方法和系统 Download PDF

Info

Publication number
WO2020233087A1
WO2020233087A1 PCT/CN2019/122719 CN2019122719W WO2020233087A1 WO 2020233087 A1 WO2020233087 A1 WO 2020233087A1 CN 2019122719 W CN2019122719 W CN 2019122719W WO 2020233087 A1 WO2020233087 A1 WO 2020233087A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
bill
review
recipient
blockchain node
Prior art date
Application number
PCT/CN2019/122719
Other languages
English (en)
French (fr)
Inventor
范诗怡
宦鹏飞
Original Assignee
深圳壹账通智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2020233087A1 publication Critical patent/WO2020233087A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2471—Distributed queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing

Definitions

  • This application relates to a method and system for rolling back bill data.
  • the billing party obtains the bill data to be modified from the blockchain, and after modifying the bill data to be modified, after obtaining the revised bill data, it will write the revised bill data into the blockchain as the one to be reviewed by the recipient Bill data.
  • the receiver receives the review request sent by the issuer, it will obtain the bill data to be reviewed from the blockchain, and review the bill data to be reviewed to obtain the review opinion data.
  • the recipient device will perform blockchain in-chain operations and database backup operations on the approved bill data.
  • the receiver device pushes the bill data that has not passed the review to the billing party device to instruct the billing party device to modify the bill data again. If the billing party device receives the bill data that has not passed the review and the billing party cancels the modification in advance, the bill data on the blockchain needs to be returned to the bill data before this modification, that is, the bill before this modification
  • the data is rewritten into the blockchain, and the rewritten bill data is reviewed by the recipient.
  • the inventor realizes that in the process of returning the receipt data, the operation process of both the issuing party and the receiving party is complicated, which causes the problem of low efficiency of returning the receipt data.
  • a method and system for rolling back bill data with rolling back efficiency are provided.
  • a method for rolling back bill data includes:
  • the receiving device receives the ticket data review request carrying the ticket identifier sent by the issuing device;
  • the receiver device searches the blockchain node for the current latest version of the bill data corresponding to the bill identifier
  • the recipient device displays the receipt data to the recipient auditor through the recipient audit interface, and obtains the audit opinion data triggered by the recipient auditor on the receipt data;
  • the recipient device queries the recipient backup bill data corresponding to the bill identifier, and sends the recipient backup bill data and the review opinion data to the area Block chain node;
  • the recipient's backup receipt data is the audit opinion data triggered by the recipient's auditor indicating the receipt data backed up when the audit is passed;
  • the sent recipient backup receipt data and the audit opinion data are used to instruct the blockchain node to write the recipient backup receipt data and the audit opinion data into a data block.
  • a bill data rollback system includes: receiver device, bill issuer device and blockchain node;
  • the bill-issuing party device is configured to send a bill data review request carrying a bill identifier to the recipient device;
  • the recipient device is configured to search for the current latest version of the bill data corresponding to the bill identifier from the blockchain node according to the bill data review request; display the bill data through the recipient review interface To the recipient auditor, and obtain the audit opinion data triggered by the recipient auditor on the receipt data; and
  • the receiver device is also configured to, when the review opinion data indicates that the review has not passed, query the receiver backup ticket data corresponding to the ticket identifier, and send the receiver backup ticket data and the review opinion data To the blockchain node;
  • the recipient's backup receipt data is the audit opinion data triggered by the recipient's auditor indicating the receipt data backed up when the audit is passed;
  • the blockchain node is used to write the recipient's backup receipt data and the audit opinion data into a data block.
  • Fig. 1 is an application scenario diagram of a method for rolling back bill data according to one or more embodiments.
  • FIG. 2 is a schematic flowchart of a method for rolling back bill data according to one or more embodiments
  • Fig. 3 is a schematic flowchart of a method for rolling back bill data in another embodiment.
  • Figure 4 is a block diagram of a computer device according to one or more embodiments.
  • the bill data rollback method provided in this application can be applied to the application environment as shown in FIG. 1.
  • the recipient device 102, the issuer device 104, and the blockchain node 106 communicate with each other through a network.
  • the receiver device 102 receives the ticket data review request carrying the ticket identifier sent by the issuer device 104, and searches the blockchain node 106 for the current latest version of the ticket data corresponding to the ticket identifier according to the ticket data review request
  • the review interface displays the receipt data to the recipient auditor, and obtains the audit opinion data triggered by the recipient auditor; when the audit opinion data indicates that the audit has not passed, the recipient device 102 queries the recipient corresponding to the receipt identifier
  • the receipt data is backed up, and the recipient's backup receipt data is written into the data block by means of the blockchain node 106.
  • the recipient device 102 and the billing device 104 may be terminals or servers.
  • the blockchain node corresponds to the server, and the blockchain node can be a server.
  • the terminal can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
  • the server can be implemented by an independent server or a server cluster composed of multiple servers.
  • the block chain node 106 corresponds to a block chain network, and the block chain network includes a plurality of block chain nodes, and each block chain node can transmit data to each other.
  • the corresponding blockchain nodes of the receiver device 102 and the billing device 104 may be the same or different.
  • a method for rolling back bill data includes the following steps:
  • the receiver device receives the bill data review request carrying the bill identifier sent by the bill issuer device.
  • the bill identifier is used to uniquely identify the bill, and may be a character string composed of at least one of characters such as numbers, letters, and symbols, and specifically may be a bill code or serial number.
  • a bill refers to an electronic bill, which is a voucher/consumption voucher provided by the billing party to the recipient when it provides services, sells products (or commodities) or engages in other business activities.
  • the issuing party can be a selling company or individual, and the receiving party can be a consumer company or individual.
  • the ticket data review request is a request for triggering the ticket data review operation.
  • the bill issuer device when the bill issuer device obtains the bill modification data corresponding to the bill identifier, it triggers the generation of a bill data review request carrying the bill identifier, and sends the generated bill data review request to the receiver device.
  • the receiver device searches the blockchain node for the current latest version of the bill data corresponding to the bill identifier according to the bill data review request.
  • the bill data refers to the data corresponding to the bill, including the billing party identification, the recipient identification, the bill identification and the amount of resource transfer, and can also include the product identification or business item identification, and the billing timestamp.
  • the identity of the issuing party can be the name of the issuing party (seller), taxpayer identification number and/or account number, etc.
  • the identity of the recipient can be the name of the recipient (consumer), taxpayer identification number and/or account number of the account. Wait.
  • the amount of resource transfer refers to the amount of resources consumed by the recipient.
  • the receiver device determines the bill identification according to the bill data review request, generates the first bill data acquisition request according to the bill identification, and sends the generated first bill data acquisition request to the blockchain node.
  • the blockchain node determines the ticket identifier according to the first ticket data acquisition request, searches the blockchain for the latest version of the ticket data corresponding to the ticket identifier according to the ticket identifier, and feeds back the found ticket data to the receiver device.
  • the current latest version of the ticket data is the ticket data to be reviewed by the receiver’s auditor, and it is also the ticket data newly modified by the operator of the issuing party, that is, the latest version of the ticket data acquired by the issuing party’s device and written into the data block. Note modification data.
  • the blockchain includes a plurality of data blocks, the bill data is stored in the data block, and the bill data stored in the data block corresponds to a version number.
  • the version number of the ticket data can be determined by the time stamp when the ticket data is written into the data block or the block number of the data block, and can also be determined by the current latest version number corresponding to the ticket ID, for example, the current latest version number is 1. , Then the version number of the confirmed receipt data is 2. Random numbers can also be included in the version number.
  • the blockchain node obtains the ticket identifier in the request according to the first ticket data, searches for one or more ticket data corresponding to the ticket identifier in the blockchain, and finds the ticket identifier according to the version number corresponding to each ticket data The bill data with the latest version number is filtered out as the bill data of the current latest version found.
  • the first receipt data acquisition request carries the recipient identification (or recipient auditor identification) and the receipt identification.
  • the blockchain node verifies the authority of the receiver (or receiver auditor) according to the receiver identifier (or receiver auditor identifier), and when the verification passes, finds the current latest version of the bill data corresponding to the bill identifier .
  • the recipient device displays the receipt data to the recipient auditor through the recipient review interface, and obtains review opinion data triggered by the recipient auditor on the receipt data.
  • the review opinion data is used to characterize the review opinions of the receiving party’s auditor on the receipt data currently displayed on the receiving party’s review interface, which can specifically include the review passed and the review failed. According to the review opinion data, it can be determined whether the recipient auditor agrees with the bill data created or modified by the operator of the billing party. When the review opinion data indicates that the review is passed, it indicates that the recipient auditor agrees with the invoice data created or modified by the issuing operator; when the review opinion data indicates that the review is not passed, it indicates that the recipient auditor does not agree (ie reject) the issuer's operation The invoice data created or modified by the administrator.
  • the recipient terminal displays the receipt data found according to the receipt identification to the recipient auditor through the recipient review interface, and detects the receipt data currently displayed by the recipient auditor in real time
  • the preset audit operation is triggered, and the corresponding audit opinion data is obtained according to the detected preset audit operation.
  • the recipient terminal obtains the review opinion data pre-selected or pre-entered by the recipient's auditor according to the preset review operation.
  • the recipient server sends the found bill data to the recipient terminal to display the bill data to the recipient auditor through the recipient review interface with the help of the recipient terminal, and receive the The receiving terminal corresponds to the review opinion data obtained and fed back.
  • the receiver device queries the recipient's backup ticket data corresponding to the ticket identifier, and sends the recipient's backup ticket data and the audit opinion data to the blockchain node;
  • the receiver's backup ticket data is The audit opinion data triggered by the receiver auditor represents the bill data that was backed up when the audit passed;
  • the sent recipient backup bill data and audit opinion data are used to instruct the blockchain node to write the recipient's backup bill data and audit opinion data Data block.
  • Recipient's backup receipt data refers to the receipt data that is backed up when the audit opinion data triggered by the recipient's auditor indicates that the audit is passed.
  • the recipient's backup bill data includes bill data, and may also include the recipient's auditor identification and/or audit opinion data triggered by the recipient's auditor.
  • the recipient device queries the corresponding recipient backup bill data locally or other computer equipment according to the bill identification, and the inquired recipient backs up the bill data and the corresponding review opinion data Send to the blockchain node.
  • the blockchain node performs a blockchain in-chain operation on the received recipient's backup ticket data and audit opinion data to write the recipient's backup ticket data and audit opinion data into the data block.
  • Other computer equipment such as blockchain nodes, or data backup servers for storing backup bill data.
  • the recipient device queries the corresponding recipient's backup bill data from a local or other computer device based on the bill identification and the recipient auditor identification.
  • the receiver device queries the corresponding backup ticket data from the local or other computer equipment according to the ticket identifier, and filters out the backup ticket data of the receiver that matches the receiver's auditor identifier from the inquired backup ticket data.
  • the receiver's auditor ID is used to uniquely identify the receiver's auditor, which can be specifically the receiver's name, ID number, or registered user name.
  • the recipient device when the review opinion data indicates that the review is not passed, the recipient device queries the local database for the recipient backup bill data corresponding to the bill identification. In one of the embodiments, when the review opinion data indicates that the review is not passed, the receiver device generates a corresponding backup data acquisition request according to the ticket identifier, and sends the generated backup data acquisition request to the data backup server. The data backup server queries the corresponding receiver backup ticket data in the local database according to the ticket identifier in the backup data acquisition request, and feeds back the inquired receiver backup ticket data to the receiver device.
  • the recipient device querying the recipient's backup bill data corresponding to the bill identifier includes: the recipient device generates a backup data acquisition request according to the bill identifier, and sends the backup data acquisition request to the blockchain node; the recipient device The device receives the current latest version of the recipient's backup receipt data that is queried and fed back by the blockchain node according to the backup data acquisition request and corresponds to the receipt identifier.
  • the receiver device sends the backup data acquisition request generated according to the ticket identifier to the blockchain node.
  • the blockchain node queries the corresponding receiver backup ticket data in the blockchain according to the ticket identifier in the backup data acquisition request, and filters the current latest version of the receiver backup ticket data from the queried receiver backup ticket data, and The filtered backup bill data of the receiver is fed back to the receiver device.
  • the blockchain node queries the backup ticket data carrying the backup data identifier in the blockchain according to the backup data acquisition request, and filters out the backup ticket data of the recipient corresponding to the ticket identifier from the backup ticket data found Data, and further filter the current latest version of the receiver’s backup ticket data from the filtered receiver’s backup ticket data.
  • the approved receipt data is backed up to the blockchain, and the backup receipt data is distinguished from other receipt data by the backup data identifier, so that the receipt data can be quickly located when the receipt data is rolled back, and the receipt data can be improved. Return efficiency.
  • the above-mentioned bill data rollback method further includes: when the review opinion data indicates that the review is passed, the recipient device sends the bill data and the review opinion data to the blockchain node; the sent bill data And audit opinion data, used to instruct the blockchain node to write bill data and audit opinion data into the data block.
  • the receiver device sends the corresponding bill data and review opinion data to the blockchain node.
  • the blockchain node performs a blockchain in-chain operation on the received bill data and review opinion data to write the bill data and review opinion data into the data block.
  • the blockchain node when the blockchain node writes the bill data and the review opinion data into the data block, it generates a version number corresponding to the bill data as the current latest version number of the corresponding bill identifier.
  • the recipient device updates the bill identification current corresponding recipient backup bill data according to the verified bill data.
  • the specific update method depends on the storage location of the recipient’s backup receipt data. For example, the recipient’s device locally queries the receipt identifier for the current recipient’s backup receipt data, and updates the queried recipient’s backup receipt data to pass the review.
  • the bill data is written into the data block with the help of the blockchain node, so that the operator of the billing party can modify the bill from the blockchain. Quickly find the bill data to be modified, while ensuring the authenticity, traceability and non-tampering of the bill data.
  • the above-mentioned bill data rollback method further includes: the billing party device searches for the initial bill data corresponding to the bill identifier from the blockchain node; the billing party device transfers the initial bill data through the billing party operation interface Show it to the operator of the issuing party, and obtain the ticket modification data triggered by the issuing party operator for the initial ticket data; the issuing party device sends the ticket modification data to the blockchain node, and the ticket modification data is used to instruct the blockchain node to modify the ticket The data is written into the data block, and the bill modification data written in the data block is used as the current latest version of the bill data; the billing party device triggers the generation of a bill data review request carrying the bill identifier.
  • the initial bill data refers to the bill data to be modified in the current bill data modification and review process, and the bill data to be modified is the initial bill data relative to the revised bill data.
  • the initial bill data is the bill data that has been reviewed by the recipient auditor and written into the data block by the recipient device with the aid of the blockchain node in the bill data modification and review process performed last time.
  • the bill modification data refers to the revised bill data corresponding to the bill identification.
  • the billing party device when it obtains the bill modification instruction triggered by the billing party operator for the bill identification, it generates a second bill data acquisition request according to the bill identification, and sends the generated second bill data acquisition request to the blockchain node .
  • the blockchain node obtains the ticket identifier in the request from the second ticket data, searches the blockchain for the current latest version of the ticket data corresponding to the ticket identifier as the initial ticket data, and feeds the initial ticket data back to the issuing party device .
  • the billing party device displays the found initial bill data to the billing party operator through the billing party operation interface, and obtains the bill modification data triggered by the billing party operator for the displayed initial bill data.
  • the bill issuer device sends the obtained bill modification data to the blockchain node, and triggers the generation of a bill data review request carrying the bill identifier, and then sends the generated bill data review request to the receiver device.
  • the blockchain node performs the blockchain in-chain operation on the received ticket modification data to write the ticket modification data into the data block, and generates the version number corresponding to the ticket modification data, which is the current latest corresponding to the ticket identifier The current version number of the current latest version corresponding to the ticket identifier to use the ticket modification data as the ticket identifier.
  • the receiver device can query the current latest version of the bill data corresponding to the bill identifier from the blockchain node.
  • the billing party terminal displays the initial bill data to the billing party operator through the billing party operation interface, and when it is detected that the billing party operator responds to the initial bill data
  • the preset modification operation is triggered, the invoice modification data pre-entered by the operator of the issuing party is obtained.
  • the issuer device is an issuer server
  • the issuer server obtains the note modification data corresponding to the initial note data by means of the corresponding issuer terminal.
  • the bill-issuing device encrypts the bill modification data based on its own private key to obtain a digital signature, and sends the digital signature and its own public key to the blockchain node.
  • the blockchain node verifies the digital signature based on the public key, and writes the verified digital signature into the data block.
  • the bill-issuing party device writes the bill modification data corresponding to the initial bill data into the data block with the help of the blockchain node, so that the recipient can quickly query the pending bill from the blockchain based on the bill identifier.
  • the audited bill data can ensure the traceability and authenticity of the bill data, so as to prevent the bill data from being tampered with intentionally or unintentionally.
  • the ticket issuer device sends the ticket modification data to the blockchain node, and the ticket modification data is used to instruct the blockchain node to write the ticket modification data into the data block, and write the ticket to the data block
  • the modification data includes: the billing party device triggers the generation of the bill data preliminary verification request corresponding to the bill identification, and sends the bill modification data to the blockchain node.
  • the bill modification data is used to instruct the blockchain node to
  • the bill modification data is written into the data block;
  • the billing party device searches for the bill modification data corresponding to the bill identification from the blockchain node according to the bill data preliminary verification request, and displays the found bill modification data to the billing party through the billing party review interface
  • the auditor obtains the initial review opinion data triggered by the billing party auditor for the displayed bill modification data; when the initial verification opinion data indicates that the review has not passed, the billing party's equipment queries the billing party's backup bill data corresponding to the bill identification by means of the block
  • the chain node writes the billing party's backup bill data and preliminary review opinion data into the data block, and uses the billing party's backup bill data written in the data block as the current latest version of the bill data.
  • the billing party device when the billing party device obtains the bill modification data triggered by the billing party operator for the initial bill data, it triggers the generation of a bill data preliminary verification request carrying the corresponding bill identifier, and sends the obtained bill modification data to the block Chain node.
  • the blockchain node performs a blockchain in-chain operation on the received ticket modification data to write the ticket modification data into the data block.
  • the billing party device queries the bill modification data corresponding to the corresponding bill identification from the blockchain node according to the bill data preliminary verification request generated by the trigger, as the bill modification data to be reviewed.
  • the bill-issuing party device displays the to-be-reviewed bill modification data to the bill-issuing party auditor through the bill-issuing party review interface, and obtains the initial review opinion data triggered by the bill-issuing party auditor for the displayed bill modification data.
  • the billing party's device queries the corresponding billing party's backup bill data in the local or other computer equipment according to the bill identifier, and sends the inquired billing party's backup bill data and the corresponding initial verification opinion data to Blockchain node.
  • the blockchain node performs the blockchain in-chain operation on the issuer's backup bill data and preliminary review opinion data to write the issuer's backup bill data and initial review opinion data into the data block, and write it into the data block
  • the billing party backed up bill data as the bill data of the current latest version corresponding to the bill identifier.
  • the steps for the issuer's device to query the issuer's backed-up bill data are similar to the steps for the receiver's device to query the issuer's backed-up bill data provided in one or more embodiments above, and will not be repeated here.
  • the billing party device when the initial review opinion data indicates that the review is approved, sends the initial review review data and the approved bill modification data to the blockchain node to use the blockchain node to perform the initial verification.
  • the opinion data and the bill modification data are written into the data block, and the bill modification data written in the data block is used as the current latest version of the bill data corresponding to the bill identifier.
  • the billing party device updates the current billing party backup bill data corresponding to the bill identifier according to the bill modification data that has passed the verification, so as to back up the bill modification data that has passed the verification to the local or other computer device.
  • the procedure for the issuer device to update the issuer's backup bill data according to the bill modification data is similar to the procedure for the receiver device to update the issuer's backup bill data according to the bill data provided in one or more embodiments, and will not be repeated here.
  • the billing party's device can also obtain the preliminary opinion data corresponding to the bill data according to the above processing flow, and trigger the corresponding blockchain based on the preliminary verification opinion data Into the chain operation.
  • the billing party device when the original review opinion data indicates that the review failed, the billing party device triggers a bill data modification request corresponding to the bill identification, and the bill data modification request is used to instruct the billing party operator to address the bill corresponding to the bill identification The data is modified again.
  • the device of the issuer may obtain the preset modification operation triggered again by the operator of the issuer, and obtain the corresponding preset modification operation according to the preset modification operation triggered again. Modify the data of the target bill, and perform the blockchain in-chain operation and review operation according to the processing flow provided in one or more of the above embodiments for the obtained target bill modification data.
  • the issuer's device queries whether the review operation performed by the issuer's device on the bill modification data last modified by the operator of the issuer has been completed, and if it has not been completed, the review operation is stopped so that the issuer
  • the auditor and the recipient auditor in turn perform the audit operation on the modified data of the target bill. Therefore, in the case that the recipient auditor has not reviewed and confirmed the previous modification data of the invoice that the invoice-issuing party operator has previously modified, the invoice-issuing party operator can initiate the modification again (for example, when the invoice-issuing party operator finds that the previously modified invoice modification data is incorrect Initiate the modification again), which saves time in the processing flow.
  • the invoice-issuing party operator can initiate the modification again (for example, when the invoice-issuing party operator finds that the previously modified invoice modification data is incorrect Initiate the modification again), which saves time in the processing flow.
  • the recipient’s device continues to perform the review operation for the bill modification data previously modified by the billing operator, and obtains the corresponding review opinion data; Opinion data indicates that when the review is passed, the receiving device writes the previously modified bill data into the data block with the help of the blockchain node; when the review opinion data indicates that the review is not passed, if it is determined that the previous modified bill is
  • the receiver device continues to perform the review operation on the latest ticket modification data in the above-mentioned manner, otherwise it queries the current latest version of the receiver backup ticket data corresponding to the ticket identifier , And write the recipient’s backup bill data and corresponding review opinion data into the data block with the help of the blockchain node.
  • the multi-version rollback of bill data can be realized, and the correctness and version of the bill data can be guaranteed during the multi-version rollback process The consistency of the number.
  • the billing party device includes a first billing party device corresponding to the billing party operator, and a second billing party device corresponding to the billing party auditor.
  • the first billing party device displays the initial bill data to the billing party operator.
  • the bill modification data triggered by the billing party operator is obtained, it triggers the generation of a bill data preliminary verification request, and sends the bill data preliminary verification request to the second billing party.
  • the bill-issuing party device writes the bill modification data into the data block with the help of the blockchain node.
  • the second billing party device searches for the bill modification data to be reviewed from the blockchain node according to the received bill data preliminary verification request, displays the found bill modification data to the billing party auditor, and obtains the corresponding trigger of the billing party auditor According to the preliminary audit opinion data, the preliminary audit opinion data, as well as the backup bill data or bill modification data of the issuing party, are written into the data block with the aid of the blockchain node.
  • the bill-issuing auditor performs a preliminary review of the bill modification data triggered by the bill-issuing operator, and when the bill-issuing auditor disagrees with the bill modification data, the bill is identified in the blockchain with the bill data corresponding to the bill
  • the invoice data is automatically returned to the invoice-issuing party that passed the previous review by the invoice-issuing party auditor and backed up the invoice data, which can effectively avoid the issue of the receiving-party auditor's auditing operation for modifying errors or non-compliant invoice modification data, saving Unnecessary operation process improves the efficiency of rollback of receipt data.
  • the recipient auditor continues to review the backed-up bill data of the billing party that is automatically rolled back to avoid the case that both the billing party auditor and the recipient auditor disagree with the currently reviewed bill data and both trigger the bill data rollback operation
  • the issue of inconsistency of the returned bill data ensures the consistency of the bill data while saving processing procedures.
  • the receiving party review interface includes the receiving party preliminary review interface and the receiving party review interface;
  • the receiving party auditor includes the receiving party preliminary reviewer and the receiving party reviewer;
  • step S206 includes: The bill data is displayed to the receiving party's first reviewer, and the receiving party's first reviewer obtains the initial review opinion data triggered by the bill data, triggers the generation of a bill data review request corresponding to the bill identifier, and writes the first review opinion data and bill data with the help of blockchain nodes Data block; according to the bill data review request, the receiver's device searches the blockchain node for the initial review opinion data and bill data corresponding to the bill identification, and displays the searched initial review opinion data and bill data to the recipient through the recipient review interface Reviewer: The receiving device obtains the review opinion data triggered by the receiving reviewer for the displayed preliminary review opinion data and bill data, and obtains the review opinion data corresponding to the bill data based on the review opinion data and the preliminary review opinion data.
  • the receiving device determines that the review opinion data corresponding to the bill mark has passed the review; the initial review opinion data indicates that the review failed , And when the review opinion data indicates that it agrees with the preliminary review opinion data, the receiving device determines that the corresponding review opinion data indicates that the review failed.
  • the receiving device when the initial review opinion data triggered by the initial reviewer of the receiving party is obtained, regardless of whether the initial review opinion data indicates that the review has passed or failed the review, the receiving device directly uses the initial review opinion data and corresponding bill data with the aid of the district.
  • Block chain nodes write data blocks.
  • the receiving device When the audit opinion data determined based on the preliminary review opinion data and the review opinion data indicates that the review is passed, the receiving device will write the approved bill data, preliminary review opinion data, and review opinion data into the data block with the help of blockchain nodes, and According to the approved bill data, the bill identifier is updated to the current recipient backup bill data.
  • the receiving device can back up the audit opinion data corresponding to the bill data (which may include the initial review opinion data and the review opinion data) and/or the receiving party’s auditor identification (which may include the receiving party’s primary auditor and the receiving party reviewer) until the update The recipient backs up the receipt data.
  • the bill data which may include the initial review opinion data and the review opinion data
  • the receiving party’s auditor identification which may include the receiving party’s primary auditor and the receiving party reviewer
  • the receiver device can query the corresponding receiver's backup bill data according to the ticket identifier, or query the corresponding data according to the ticket identifier, the receiver's initial reviewer identifier, and the receiver reviewer identifier. The recipient backs up the receipt data.
  • the receiver device includes a first receiver device corresponding to the receiver preliminary examiner, and a second receiver device corresponding to the receiver reviewer.
  • the first receiver device and the second receiver device respectively perform the aforementioned related operations performed by the receiver device.
  • the final audit opinion data is determined based on the preliminary review opinion data of the receiving party’s first examiner and the receiving party reviewer’s review opinion data, so as to avoid errors in the receipt data due to audit errors or operational errors of the receiving party’s primary examiner.
  • the rollback ensures the accuracy of the bill data rollback. Moreover, through double review, the accuracy of the bill modification data can be effectively guaranteed.
  • the method further includes: when the review opinion data indicates that the initial review opinion data is not agreed with, the receiver device triggers the generation of the corresponding bill identification
  • the bill data review request, and the initial review opinion data, the review opinion data, and the bill data are written into the data block with the help of the blockchain node; the receiving device searches the blockchain node for the corresponding bill identification according to the bill data review request Note data, and return to the step of displaying the note data to the receiver’s preliminary reviewer through the receiver’s preliminary review interface to continue execution.
  • the bill data review request is used to instruct the receiver device to display the bill data to the receiver's preliminary reviewer for review. Specifically, when the review opinion data indicates that it does not agree with the initial review opinion data, regardless of whether the initial review opinion data indicates that the review passed or failed, the receiving device triggers the generation of a bill data re-examination request carrying the bill identification, and combines the reviewed bill data, The preliminary review opinion data and the review opinion data are sent to the blockchain node.
  • the blockchain node performs blockchain in-chain operations on the received bill data, preliminary review opinion data, and review opinion data to write the bill data, preliminary review opinion data, and review opinion data into the data block.
  • the recipient device searches for the bill data corresponding to the bill identifier from the blockchain node according to the bill data reexamination request generated by the trigger, and returns to the recipient's preliminary review interface to display the queried bill data to the recipient preliminary reviewer Continue to execute the steps until the iteration stop condition is reviewed, and the above iteration process is stopped.
  • the conditions for stopping iterations are, for example, that the review opinion data indicates agreement to the initial review opinion data, or the number of iterations reaches a preset number.
  • the receiver’s device can trigger the generation of a prompt message indicating offline negotiation, and display it to the receiver’s preliminary reviewer and/or receiver reviewer to instruct the receiver’s first reviewer and The reviewer of the receiving party determines the review opinion data of the bill data through offline negotiation.
  • the bill data review process is triggered, which can improve the reliability and authenticity of the bill data.
  • a method for rolling back bill data includes:
  • the bill-issuing party device searches the blockchain node for initial bill data corresponding to the bill identifier.
  • S304 The device of the issuer displays the initial bill data to the operator of the issuer through the operation interface of the issuer, and obtains the bill modification data triggered by the operator of the issuer for the initial bill data.
  • the bill-issuing party device triggers the generation of a bill data preliminary verification request corresponding to the bill identifier, and sends the bill modification data to the blockchain node.
  • the bill modification data is used to instruct the blockchain node to write the bill modification data into the data block.
  • the billing party device searches for the bill modification data corresponding to the bill identifier from the blockchain node according to the bill data preliminary verification request, and displays the searched bill modification data to the billing party auditor through the billing party review interface, and obtains the billing party's review The initial review opinion data triggered by the modification data of the displayed bill.
  • the billing party device queries the billing party's backup bill data corresponding to the bill identifier, and writes the billing party's backup bill data and the initial verification opinion data into the data block by means of the blockchain node. And take the backed-up bill data of the billing party written into the data block as the bill data of the current latest version.
  • the bill-issuing party device triggers the generation of a bill data review request carrying the bill identifier.
  • the receiver device receives the bill data review request carrying the bill identifier sent by the bill issuer device.
  • the receiver device searches the blockchain node for the current latest version of the bill data corresponding to the bill identifier.
  • the receiving device displays the bill data to the receiving preliminary reviewer through the receiving preliminary review interface, obtains the preliminary review opinion data triggered by the receiving preliminary reviewer for the bill data, triggers the generation of a bill data review request corresponding to the bill identification, and uses the block
  • the chain node writes the preliminary review opinion data and bill data into the data block.
  • the receiving party device searches the blockchain node for the initial review opinion data and bill data corresponding to the bill identifier according to the bill data review request, and displays the searched initial review opinion data and bill data to the recipient reviewer through the recipient review interface .
  • the receiver device obtains the review opinion data triggered by the receiver reviewer for the displayed preliminary review opinion data and bill data, and obtains the review opinion data corresponding to the bill data based on the review opinion data and the preliminary review opinion data.
  • the receiver device queries the recipient's backup ticket data corresponding to the ticket identifier, and sends the recipient's backup ticket data and the audit opinion data to the blockchain node; the receiver's backup ticket data is The audit opinion data triggered by the receiver auditor represents the bill data that was backed up when the audit passed; the sent recipient backup bill data and audit opinion data are used to instruct the blockchain node to write the recipient's backup bill data and audit opinion data Data block.
  • the receiver device sends the bill data and review opinion data to the blockchain node; the sent bill data and review opinion data are used to instruct the blockchain node to combine the bill data and the review opinion Data is written into the data block.
  • the receiver device When the review opinion data indicates that it disagrees with the initial review opinion data, the receiver device triggers the generation of a bill data review request corresponding to the bill identification, and writes the initial review opinion data, review opinion data, and bill data into the data area with the help of the blockchain node Piece.
  • the recipient device searches for the bill data corresponding to the bill identifier from the blockchain node according to the bill data review request, and returns to step S318 to continue execution.
  • the blockchain entry operation performed by the blockchain node includes the following steps: the blockchain node performs a consensus operation on the data to be entered into the chain based on the consensus mechanism, and when the consensus is passed, the entry chain is generated The data corresponding to the data block, and write the generated data block into the blockchain. It is understandable that when the blockchain generates a data block corresponding to the data to be entered into the chain, the version number corresponding to the ticket identifier is correspondingly updated as the current latest version number of the ticket identifier, and the version number is written into the data area Block.
  • the recipient device and the billing party device may be the same computer device, such as a terminal or a server.
  • Operators of the issuing party, auditors of the issuing party, preliminary auditors of the receiving party and reviewers of the receiving party can log in to the computer equipment based on their respective account numbers and passwords and perform corresponding operations.
  • a bill data rollback system including: a receiver device 102, an issuer device 104, and a blockchain node 106;
  • the bill issuer device 104 is configured to send a bill data review request carrying a bill identifier to the recipient device 102;
  • the recipient device 102 is used to search the blockchain node 106 for the latest version of the bill data corresponding to the bill identifier according to the bill data review request; display the bill data to the recipient reviewer through the recipient review interface, and obtain Audit opinion data triggered by the receiving auditor for the receipt data;
  • the receiver device 102 is also used to query the receiver's backup bill data corresponding to the bill identifier when the review opinion data indicates that the review fails, and send the recipient's backup bill data and review opinion data to the blockchain node 106; the recipient
  • the backed-up bill data is the audit opinion data triggered by the receiver's auditor, which means the backed up bill data when the audit is passed;
  • the blockchain node 106 is used to write the recipient's backup bill data and review opinion data into the data block.
  • the receiver device 102 is also used to generate a backup data acquisition request according to the ticket identifier, and send the backup data acquisition request to the blockchain node 106; the blockchain node 106 is also used to acquire the backup data Request to query the current latest version of the recipient's backup bill data corresponding to the bill identifier, and feed back the inquired recipient's backup bill data to the recipient device 102.
  • the receiver device 102 is also used to send the bill data and the review opinion data to the blockchain node 106 when the review opinion data indicates that the review is passed; the blockchain node 106 is also used to send the bill Data and audit opinion data are written into the data block.
  • the billing party device 104 is also used to find the initial bill data corresponding to the bill identifier from the blockchain node; the initial bill data is displayed to the billing party operator through the billing party operation interface, and the billing party is obtained
  • the operator modifies the data triggered by the initial ticket data; sends the modified data to the blockchain node 106; triggers the generation of a ticket data review request carrying the ticket identifier; the blockchain node 106 is also used to write the ticket modified data Enter the data block, and use the note modification data written in the data block as the current latest version of the note data.
  • the billing party device 104 is also used to trigger the generation of a bill data preliminary verification request corresponding to the bill identification, and to send the bill modification data to the blockchain node; the blockchain node 106 is also used to send the bill The modification data is written into the data block; the billing party device 104 is also used to find the bill modification data corresponding to the bill identification from the blockchain node 106 according to the bill data preliminary verification request, and pass the bill modification data searched through the billing party review
  • the interface is displayed to the auditor of the invoice issuing party to obtain the initial review opinion data triggered by the auditor of the invoice issuer on the displayed note modification data; when the initial audit opinion data indicates that the review has not passed, query the issuer’s backup note data corresponding to the invoice identification, with the help of
  • the blockchain node 106 writes the issuer's backup note data and the preliminary review opinion data into the data block, and uses the issuer's backup note data written in the data block as the current latest version of the note data.
  • the receiving party review interface includes the receiving party preliminary review interface and the receiving party review interface;
  • the receiving party auditor includes the receiving party preliminary reviewer and the receiving party reviewer;
  • the receiving party device 102 is also used to pass the receiving party's preliminary review interface Show the bill data to the receiving party's first reviewer, obtain the initial review opinion data triggered by the recipient's first reviewer for the bill data, trigger the generation of a bill data review request corresponding to the bill identifier, and use the blockchain node 106 to transfer the initial review opinion data and bill data Write the data block;
  • the recipient device 102 is also used to find the initial review opinion data and bill data corresponding to the bill identifier from the blockchain node 106 according to the bill data review request, and the first review opinion found through the recipient review interface
  • Data and bill data are displayed to the receiving party reviewer;
  • the receiving party reviewer obtains the review opinion data triggered by the displayed preliminary review opinion data and bill data, and obtains the review opinion data corresponding to the bill data based on the review opinion data and the
  • the receiver device 102 is also used to trigger the generation of a bill data re-examination request corresponding to the bill identifier when the review opinion data indicates that it does not agree with the initial review opinion data, and use the blockchain node 106 to transfer the initial review opinion data ,
  • the review opinion data and bill data are written into the data block;
  • the recipient device 102 is also used to find the bill data corresponding to the bill identifier from the blockchain node 106 according to the bill data review request, and return it to the recipient through the initial review
  • the interface displays the bill data to the first reviewer of the receiving party to continue.
  • a computer device is provided.
  • the computer device may be a receiver device, an issuer device or a blockchain node, and its internal structure diagram may be as shown in FIG. 4.
  • the computer equipment includes a processor, a memory, a network interface and a database connected through a system bus.
  • the processor of the computer device is used to provide calculation and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium stores an operating system, a computer-readable storage medium, a computer-readable storage medium, and a database.
  • the internal memory provides an environment for the operation of the operating system and the computer-readable storage medium in the non-volatile storage medium.
  • the database of the computer equipment is used to store bill data.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable storage medium is executed by the processor, the computer-readable storage medium realizes a method for rollback of bill data.
  • FIG. 4 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied.
  • the specific computer device may Including more or fewer parts than shown in the figure, or combining some parts, or having a different arrangement of parts.
  • Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Marketing (AREA)
  • Mathematical Physics (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Accounting & Taxation (AREA)
  • Fuzzy Systems (AREA)
  • Strategic Management (AREA)
  • Probability & Statistics with Applications (AREA)
  • Software Systems (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种票据数据回退方法，包括：接收方设备接收开票方设备发送的携带有票据标识的票据数据审核请求；接收方设备根据票据数据审核请求，从区块链节点中查找与票据标识对应的当前最新版本的票据数据；接收方设备通过接收方审核界面将票据数据展示给接收方审核员，获取接收方审核员针对票据数据触发的审核意见数据；当审核意见数据表示审核未通过时，接收方设备查询与票据标识对应的接收方备份票据数据，将接收方备份票据数据和审核意见数据发送至区块链节点；发送的接收方备份票据数据和审核意见数据，用于指示区块链节点将接收方备份票据数据和审核意见数据写入数据区块。

Description

票据数据回退方法和系统
本申请要求于2019年05月20日提交中国专利局，申请号为2019104193769，申请名称为“票据数据回退方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种票据数据回退方法和系统。
背景技术
开票方从区块链中获取待修改的票据数据，并对待修改的票据数据进行修改得到修改后的票据数据后，会将修改后的票据数据写入区块链中，作为待接收方审核的票据数据。接收方接收到开票方发送的审核请求时，会从区块链中获取待审核的票据数据，并对待审核的票据数据进行审核得到审核意见数据。
目前，当审核意见数据表示审核通过时，接收方设备会对审核通过的票据数据执行区块链入链操作和数据库备份操作。当审核意见数据表示审核未通过时，接收方设备将审核未通过的票据数据推送至开票方设备，以指示开票方设备重新修改票据数据。若开票方设备接收到审核未通过的票据数据时，开票方预撤销本次修改，则需将区块链上的票据数据回退至本次修改之前的票据数据，即将本次修改之前的票据数据重新写入区块链，并由接收方对重新写入的票据数据进行审核。然而，发明人意识到，在票据数据的回退过程中，开票方和接收方双方的操作流程复杂，从而存在票据数据的回退效率低的问题。
发明内容
根据本申请公开的各种实施例，提供一种回退效率的票据数据回退方法和系统。
一种票据数据回退方法包括：
接收方设备接收开票方设备发送的携带有票据标识的票据数据审核请求；
所述接收方设备根据所述票据数据审核请求，从区块链节点中查找与所述票据标识对应的当前最新版本的票据数据；
所述接收方设备通过接收方审核界面将所述票据数据展示给接收方审核员，并获取所述接收方审核员针对所述票据数据触发的审核意见数据；及
当所述审核意见数据表示审核未通过时，所述接收方设备查询与所述票据标识对应的接收方备份票据数据，将所述接收方备份票据数据和所述审核意见数据发送至所述区块链节点；所述接收方备份票据数据是在所述接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；
发送的所述接收方备份票据数据和所述审核意见数据，用于指示所述区块链节点将所 述接收方备份票据数据和所述审核意见数据写入数据区块。
一种票据数据回退系统包括：接收方设备、开票方设备和区块链节点；
所述开票方设备，用于向所述接收方设备发送携带有票据标识的票据数据审核请求；
所述接收方设备，用于根据所述票据数据审核请求，从所述区块链节点中查找与所述票据标识对应的当前最新版本的票据数据；通过接收方审核界面将所述票据数据展示给接收方审核员，并获取所述接收方审核员针对所述票据数据触发的审核意见数据；及
所述接收方设备，还用于当所述审核意见数据表示审核未通过时，查询与所述票据标识对应的接收方备份票据数据，将所述接收方备份票据数据和所述审核意见数据发送至所述区块链节点；所述接收方备份票据数据是在所述接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；
所述区块链节点，用于将所述接收方备份票据数据和所述审核意见数据写入数据区块。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中票据数据回退方法的应用场景图。
图2为根据一个或多个实施例中票据数据回退方法的流程示意图；
图3为另一个实施例中票据数据回退方法的流程示意图。
图4为根据一个或多个实施例中计算机设备的框图。
具体实施方式
为了使本申请的技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供的票据数据回退方法，可以应用于如图1所示的应用环境中。接收方设备102、开票方设备104和区块链节点106相互之间通过网络进行通信。接收方设备102接收开票方设备104发送的携带有票据标识的票据数据审核请求，根据该票据数据审核请求从区块链节点106中查找与票据标识对应的当前最新版本的票据数据，通过接收方审核界面将该票据数据展示给接收方审核员，并获取该接收方审核员对应触发的审核意见数据； 当审核意见数据表示审核未通过时，接收方设备102查询与该票据标识对应的接收方备份票据数据，并借助于区块链节点106将该接收方备份票据数据写入数据区块。接收方设备102和开票方设备104可以是终端也可以是服务器。区块链节点与服务器相对应，区块链节点具体可以是服务器。终端可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备，服务器可以用独立的服务器或者是多个服务器组成的服务器集群来实现。区块链节点106与区块链网络相对应，该区块链网络中包括多个区块链节点，各区块链节点相互之间可以进行数据传递。在该区块链网络中，接收方设备102和开票方设备104各自对应的区块链节点可以相同也可以不同。
在其中一个实施例中，如图2所示，提供了一种票据数据回退方法，该方法包括以下步骤：
S202，接收方设备接收开票方设备发送的携带有票据标识的票据数据审核请求。
票据标识用于唯一标识票据，可以是由数字、字母和符号等字符中的至少一种字符组成的字符串，具体可以是票据代码或编号。票据是指电子票据，是开票方在向接收方提供服务、出售产品(或商品)或从事其他经营活动时为接收方提供的凭证/消费凭证。开票方可以是销售企业或个人，接收方可以是消费企业或个人。票据数据审核请求是用于触发票据数据审核操作的请求。
具体地，开票方设备在获取到与票据标识对应的票据修改数据时，触发生成携带该票据标识的票据数据审核请求，并将生成的票据数据审核请求发送至接收方设备。
S204，接收方设备根据票据数据审核请求，从区块链节点中查找与票据标识对应的当前最新版本的票据数据。
票据数据是指票据所对应的数据，包括开票方标识、接收方标识、票据标识和资源转移数额，还可包括产品标识或经营项目标识，以及开票时间戳。开票方标识具体可以是开票方(销售方)的名称、纳税人识别号和/或开户账号等，接收方标识具体可以是接收方(消费方)的名称、纳税人识别号和/或开户账号等。资源转移数额是指接收方的消费资源数额。
具体地，接收方设备根据票据数据审核请求确定票据标识，根据该票据标识生成第一票据数据获取请求，并将生成的第一票据数据获取请求发送至区块链节点。区块链节点根据第一票据数据获取请求确定票据标识，根据票据标识在区块链中查找与该票据标识对应的当前最新版本的票据数据，并将查找到的票据数据反馈至接收方设备。
在其中一个实施例中，该当前最新版本的票据数据是待接收方审核员审核的票据数据，也是开票方操作员最新修改后的票据数据，即开票方设备最新获取并写入数据区块的票据修改数据。
在其中一个实施例中，区块链包括多个数据区块，票据数据存储于数据区块中，存储于数据区块中的票据数据对应有版本号。票据数据的版本号可由将该票据数据写入数据区块的时间戳或该数据区块的区块编号确定，还可由票据标识对应的当前最新的版本号确 定，比如当前最新的版本号为1时，则对应确定的票据数据的版本号为2。版本号中还可包括随机数。区块链节点根据第一票据数据获取请求中的票据标识，在区块链中查找与该票据标识对应的一个或多个票据数据，根据各票据数据对应的版本号从查找到的票据标识中筛选出版本号最新的票据数据，作为查找的当前最新版本的票据数据。
在其中一个实施例中，第一票据数据获取请求中携带有接收方标识(或接收方审核员标识)和票据标识。区块链节点根据接收方标识(或接收方审核员标识)对接收方(或接收方审核员)的权限进行校验，当校验通过时，查找与票据标识对应的当前最新版本的票据数据。
S206，接收方设备通过接收方审核界面将票据数据展示给接收方审核员，并获取接收方审核员针对票据数据触发的审核意见数据。
审核意见数据用于表征接收方审核员对接收方审核界面当前展示的票据数据的审核意见，具体可包括审核通过和审核未通过。根据审核意见数据可确定接收方审核员是否同意开票方操作员创建或修改的票据数据。当审核意见数据表示审核通过时，表明接收方审核员同意开票方操作员创建或修改的票据数据；当审核意见数据表示审核未通过时，表明接收方审核员不同意(即拒绝)开票方操作员创建或修改的票据数据。
具体地，当接收方设备为接收方终端时，该接收方终端通过接收方审核界面将根据票据标识查找到的票据数据展示给接收方审核员，实时检测接收方审核员针对当前展示的票据数据触发的预设审核操作，并根据检测到的预设审核操作获取相应的审核意见数据。当检测到预设审核操作时，接收方终端根据该预设审核操作获取接收方审核员预选取或预录入的审核意见数据。当接收方设备为接收方服务器时，接收方服务器将查找到的票据数据发送至接收方终端，以借助于接收方终端通过接收方审核界面将该票据数据展示给接收方审核员，并接收该接收方终端对应获取并反馈的审核意见数据。
S208，当审核意见数据表示审核未通过时，接收方设备查询与票据标识对应的接收方备份票据数据，将接收方备份票据数据和审核意见数据发送至区块链节点；接收方备份票据数据是在接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；发送的接收方备份票据数据和审核意见数据，用于指示区块链节点将接收方备份票据数据和审核意见数据写入数据区块。
接收方备份票据数据是指在接收方审核员触发的审核意见数据表示审核通过时备份的票据数据。接收方备份票据数据包括票据数据，还可包括接收方审核员标识和/或由接收方审核员触发的审核意见数据。
具体地，当审核意见数据表示审核未通过时，接收方设备根据票据标识在本地或其他计算机设备查询相应的接收方备份票据数据，并将查询到的接收方备份票据数据和相应的审核意见数据发送至区块链节点。区块链节点对接收到的接收方备份票据数据和审核意见数据执行区块链入链操作，以将该接收方备份票据数据和审核意见数据写入数据区块。其他计算机设备比如区块链节点，或者用于存储备份票据数据的数据备份服务器。
在其中一个实施例中，接收方设备根据票据标识和接收方审核员标识从本地或其他计算机设备查询相应的接收方备份票据数据。接收方设备根据票据标识从本地或其他计算机设备查询相应的备份票据数据，并从查询到的备份票据数据中筛选出与接收方审核员标识相匹配的接收方备份票据数据。接收方审核员标识用于唯一标识接收方审核员，具体可以是接收方审核员的姓名、身份证号或注册的用户名等。
在其中一个实施例中，当审核意见数据表示审核未通过时，接收方设备从本地数据库中查询与票据标识对应的接收方备份票据数据。在其中一个实施例中，当审核意见数据表示审核未通过时，接收方设备根据票据标识生成相应的备份数据获取请求，将生成的备份数据获取请求发送至数据备份服务器。数据备份服务器根据该备份数据获取请求中的票据标识，在本地数据库中查询相应的接收方备份票据数据，并将查询到的接收方备份票据数据反馈至接收方设备。
在其中一个实施例中，接收方设备查询与票据标识对应的接收方备份票据数据，包括：接收方设备根据票据标识生成备份数据获取请求，将备份数据获取请求发送至区块链节点；接收方设备接收区块链节点根据备份数据获取请求查询并反馈的、且与票据标识对应的当前最新版本的接收方备份票据数据。
具体地，接收方设备将根据票据标识生成的备份数据获取请求发送至区块链节点。区块链节点根据备份数据获取请求中的票据标识在区块链中查询相应的接收方备份票据数据，从查询到的接收方备份票据数据筛选出当前最新版本的接收方备份票据数据，并将筛选出的接收方备份票据数据反馈至接收方设备。
在其中一个实施例中，区块链节点根据备份数据获取请求在区块链中查询携带有备份数据标识的备份票据数据，从查询到的备份票据数据筛选出与票据标识对应的接收方备份票据数据，并从筛选出的接收方备份票据数据进一步筛选出当前最新版本的接收方备份票据数据。由此，将审核通过的票据数据备份至区块链，通过备份数据标识区分备份票据数据和其他票据数据，以便于在进行票据数据回退时能够根据快速定位备份票据数据，能够提高票据数据的回退效率。
在其中一个实施例中，步骤S206之后，上述票据数据回退方法还包括：当审核意见数据表示审核通过时，接收方设备将票据数据和审核意见数据发送至区块链节点；发送的票据数据和审核意见数据，用于指示区块链节点将票据数据和审核意见数据写入数据区块。
具体地，当审核意见数据表示审核通过时，接收方设备将相应的票据数据和审核意见数据发送至区块链节点。区块链节点对接收到的票据数据和审核意见数据执行区块链入链操作，以将该票据数据和审核意见数据写入数据区块。
在其中一个实施例中，区块链节点在将票据数据和审核意见数据写入数据区块时，生成与该票据数据对应的版本号，作为相应票据标识当前最新的版本号。
在其中一个实施例中，当审核意见数据表示审核通过时，接收方设备根据审核通过的 票据数据更新票据标识当前对应的接收方备份票据数据。具体的更新方式依据接收方备份票据数据的存储位置而定，比如，接收方设备在本地查询票据标识当前对应的接收方备份票据数据，并将查询到的接收方备份票据数据更新为该审核通过的票据数据；接收方设备借助于备份数据服务器更新该票据标识当前对应的接收方备份票据数据；接收方设备借助于区块链节点将该审核通过的票据数据备份至区块链，作为该票据标识对应的当前最新版本的接收方备份票据数据。可以理解的是，接收方设备可将票据数据对应的审核意见数据和/或接收方审核员标识，对应备份至更新后的接收方备份票据数据。
上述实施例中，接收方审核员同意创建或修改票据数据时，将该票据数据借助于区块链节点写入数据区块，以便于开票方操作员对票据发起修改时能够从区块链中快速查找待修改的票据数据，同时保证了票据数据的真实性、可追溯性和不可篡改性。
在其中一个实施例中，步骤S202之前，上述票据数据回退方法还包括：开票方设备从区块链节点中查找票据标识对应的初始票据数据；开票方设备通过开票方操作界面将初始票据数据展示给开票方操作员，并获取开票方操作员针对初始票据数据触发的票据修改数据；开票方设备将票据修改数据发送至区块链节点，票据修改数据用于指示区块链节点将票据修改数据写入数据区块，并将写入数据区块的票据修改数据作为当前最新版本的票据数据；开票方设备触发生成携带有票据标识的票据数据审核请求。
初始票据数据是指在当次执行的票据数据修改和审核流程中待修改的票据数据，该待修改的票据数据相对于修改后的票据数据而言是初始票据数据。初始票据数据是在前次执行的票据数据修改和审核流程中，由接收方审核员审核过、且由接收方设备借助于区块链节点写入数据区块的票据数据。票据修改数据是指票据标识对应的修改后的票据数据。
具体地，开票方设备在获取到开票方操作员针对票据标识触发的票据修改指令时，根据票据标识生成第二票据数据获取请求，并将生成的第二票据数据获取请求发送至区块链节点。区块链节点根据第二票据数据获取请求中的票据标识，从区块链中查找该票据标识对应的当前最新版本的票据数据，作为初始票据数据，并将该初始票据数据反馈至开票方设备。开票方设备通过开票方操作界面将查找到的初始票据数据展示给开票方操作员，并获取开票方操作员针对展示的初始票据数据触发的票据修改数据。
进一步地，开票方设备将获取到的票据修改数据发送至区块链节点，并触发生成携带有票据标识的票据数据审核请求，进而将生成的票据数据审核请求发送至接收方设备。区块链节点对接收到的票据修改数据执行区块链入链操作，以将该票据修改数据写入数据区块，并生成与该票据修改数据对应的版本号，作为票据标识对应的当前最新的版本号，以将该票据修改数据作为票据标识对应的当前最新版本的票据数据。接收方设备根据接收到的票据数据审核请求，即可从区块链节点中查询到该票据标识对应的当前最新版本的票据数据。
在其中一个实施例中，当开票方设备为开票方终端时，该开票方终端通过开票方操作界面将初始票据数据展示给开票方操作员，并在检测到开票方操作员针对该初始票据数据 触发的预设修改操作时，获取该开票方操作员预录入的票据修改数据。当开票方设备为开票方服务器时，该开票方服务器借助于相应开票方终端获取与初始票据数据对应的票据修改数据。
在其中一个实施例中，开票方设备基于自身的私钥对票据修改数据进行加密，得到数字签名，并将该数字签名和自身的公钥发送至区块链节点。区块链节点基于公钥对数字签名进行校验，并将校验通过的数字签名写入数据区块。
上述实施例中，开票方设备将对应于初始票据数据获取到的票据修改数据，借助于区块链节点写入数据区块，以便于接收方根据票据标识即可快速从区块链中查询待审核的票据数据，同时，可以确保票据数据的可追溯性和真实性，以免票据数据被有意或无意篡改。
在其中一个实施例中，开票方设备将票据修改数据发送至区块链节点，票据修改数据用于指示区块链节点将票据修改数据写入数据区块，并将写入数据区块的票据修改数据作为当前最新版本的票据数据，包括：开票方设备触发生成票据标识对应的票据数据初核请求，并将票据修改数据发送至区块链节点，票据修改数据用于指示区块链节点将票据修改数据写入数据区块；开票方设备根据票据数据初核请求，从区块链节点中查找与票据标识对应的票据修改数据，将查找的票据修改数据通过开票方审核界面展示给开票方审核员，获取开票方审核员针对展示的票据修改数据触发的初核意见数据；当初核意见数据表示审核未通过时，开票方设备查询与票据标识对应的开票方备份票据数据，借助于区块链节点将开票方备份票据数据和初核意见数据写入数据区块，并将写入数据区块的开票方备份票据数据作为当前最新版本的票据数据。
具体地，开票方设备在获取到开票方操作员针对初始票据数据触发的票据修改数据时，触发生成携带有相应票据标识的票据数据初核请求，并将获取到的票据修改数据发送至区块链节点。区块链节点对接收到的票据修改数据执行区块链入链操作，以将该票据修改数据写入数据区块。进一步地，开票方设备根据触发生成的票据数据初核请求，从区块链节点中查询与相应票据标识对应的票据修改数据，作为待审核的票据修改数据。开票方设备将该待审核的票据修改数据通过开票方审核界面展示给开票方审核员，并获取开票方审核员针对展示的该票据修改数据触发的初核意见数据。
当初核意见数据表示审核未通过时，开票方设备根据票据标识在本地或其他计算机设备中查询相应的开票方备份票据数据，并将查询到的开票方备份票据数据和相应初核意见数据发送至区块链节点。区块链节点对该开票方备份票据数据和初核意见数据执行区块链入链操作，以将该开票方备份票据数据和初核意见数据写入数据区块，并将写入数据区块的该开票方备份票据数据作为票据标识对应的当前最新版本的票据数据。开票方设备查询开票方备份票据数据的步骤，类似于上述一个或多个实施例中提供的接收方设备查询开票方备份票据数据的步骤，在此不再赘述。
在其中一个实施例中，当初核意见数据表示审核通过时，开票方设备将该初核意见数据和审核通过的票据修改数据发送至区块链节点，以借助于区块链节点将该初核意见数据 和票据修改数据写入数据区块，并将写入数据区块的该票据修改数据作为票据标识对应的当前最新版本的票据数据。相应地，开票方设备根据审核通过的票据修改数据更新相应票据标识当前对应的开票方备份票据数据，以将该审核通过的票据修改数据备份至本地或其他计算机设备中。开票方设备根据票据修改数据更新开票方备份票据数据的步骤，类似于上述一个或多个实施例中提供的接收方设备根据票据数据更新开票方备份票据数据的步骤，在此不再赘述。
在其中一个实施例中，对于开票方操作员首次创建的票据数据，开票方设备也可按照上述处理流程获取该票据数据对应的初核意见数据，并根据初核意见数据触发相应的区块链入链操作。在其中一个实施例中，当初核意见数据表示审核未通过时，开票方设备触发与票据标识对应的票据数据修改请求，该票据数据修改请求用于指示开票方操作员针对该票据标识对应的票据数据重新发起修改。
在其中一个实施例中，当获取到开票方审核员触发的初核意见数据时，开票方设备可获取开票方操作员再次触发的预设修改操作，根据该再次触发的预设修改操作获取相应的目标票据修改数据，并针对获取的目标票据修改数据，按照上述一个或多个实施例中提供的处理流程执行区块链入链操作和审核操作。相应地，开票方设备借助于管理服务器，查询开票方设备针对开票方操作员前次修改的票据修改数据执行的审核操作是否执行完毕，若尚未执行完毕，则停止该审核操作，以使得开票方审核员和接收方审核员依次针对该目标票据修改数据执行审核操作。由此，在接收方审核员尚未审核确认开票方操作员前次修改的票据修改数据的情况下，开票方操作员可再次发起修改(比如开票方操作员发现前次修改的票据修改数据错误时再次发起修改)，节省了处理流程中耗费的时间。而且，基于上述处理流程，能够避免因同一票据标识在同一时间对应多个处理流程而导致的票据数据错误或版本号不一致的问题。
值得说明的是，当接收方审核员不同意该目标票据修改数据时，接收方设备针对开票方操作员前次修改的票据修改数据继续执行的审核操作，得到相应的审核意见数据；当该审核意见数据表示审核通过时，接收方设备借助于区块链节点将该前次修改的票据数据写入数据区块；当该审核意见数据表示审核未通过时，若判定针对该前次修改的票据修改数据之前的最新票据修改数据执行的审核操作尚未执行完毕时，接收方设备按照上述方式对该最新票据修改数据继续执行审核操作，否则查询票据标识所对应的当前最新版本的接收方备份票据数据，并借助于区块链节点将该接收方备份票据数据和相应审核意见数据写入数据区块。由此，当开票方审核员和/或接收方审核员拒绝修改的票据修改数据时，能够实现票据数据的多版本回退，且在多版本回退过程中能够保证票据数据的正确性和版本号的一直性。
在其中一个实施例中，开票方设备包括开票方操作员所对应的第一开票方设备，以及开票方审核员所对应的第二开票方设备。第一开票方设备将初始票据数据展示给开票方操作员，当获取到开票方操作员对应触发的票据修改数据时，触发生成票据数据初核请求， 将该票据数据初核请求发送至第二开票方设备，并借助于区块链节点将票据修改数据写入数据区块。第二开票方设备根据接收到的票据数据初核请求从区块链节点中查找待审核的票据修改数据，将查找到的票据修改数据展示给开票方审核员，获取该开票方审核员对应触发的初核意见数据，并根据初核意见数据借助于区块链节点将该初核意见数据，以及开票方备份票据数据或票据修改数据写入数据区块。
上述实施例中，由开票方审核员对开票方操作员触发的票据修改数据进行初步审核，并在开票方审核员不同意该票据修改数据时，在区块链中将票据标识对应的票据数据自动回退至开票方审核员前次审核通过、且备份的开票方备份票据数据，由此能够有效避免接收方审核员针对修改错误或不符合要求的票据修改数据执行审核操作的问题，节省了不必要的操作流程，提高了票据数据的回退效率。此外，接收方审核员继续审核该自动回退的开票方备份票据数据，以避免因开票方审核员和接收方审核员均不同意当前审核的票据数据、且均触发票据数据回退操作时导致回退的票据数据不一致的问题，在节省处理流程的情况下，保证了票据数据的一致性。
在其中一个实施例中，接收方审核界面包括接收方初审界面和接收方复核界面；接收方审核员包括接收方初审员和接收方复核员；步骤S206包括：接收方设备通过接收方初审界面将票据数据展示给接收方初审员，获取接收方初审员针对票据数据触发的初审意见数据，触发生成票据标识对应的票据数据复核请求，并借助于区块链节点将初审意见数据和票据数据写入数据区块；接收方设备根据票据数据复核请求，从区块链节点中查找与票据标识对应的初审意见数据和票据数据，通过接收方复核界面将查找的初审意见数据和票据数据展示给接收方复核员；接收方设备获取接收方复核员针对展示的初审意见数据和票据数据触发的复核意见数据，并根据复核意见数据和初审意见数据得到票据数据对应的审核意见数据。
在其中一个实施例中，当初审意见数据表示审核通过、且复核意见数据表示同意初审意见数据时，接收方设备则判定票据标识对应的审核意见数据标识审核通过；当初审意见数据表示审核未通过、且复核意见数据表示同意初审意见数据时，接收方设备则判定相应审核意见数据表示审核未通过。
在其中一个实施例中，当获取到接收方初审员触发的初审意见数据时，不论该初审意见数据表示审核通过还是审核未通过，接收方设备直接将该初审意见数据和相应票据数据借助于区块链节点写入数据区块。当根据初审意见数据和复核意见数据确定的审核意见数据表示审核通过时，接收方设备将审核通过的票据数据、初审意见数据和复核意见数据，借助于区块链节点写入数据区块，并根据该审核通过的票据数据更新票据标识当前对应的接收方备份票据数据。接收方设备可将票据数据对应的审核意见数据(可包括初审意见数据和复核意见数据)和/或接收方审核员标识(可包括接收方初审员和接收方复核员)，对应备份至更新后的接收方备份票据数据。
进一步地，当所确定的审核意见数据表示审核通过时，接收方设备可根据票据标识查 询相应的接收方备份票据数据，也可根据票据标识、接收方初审员标识和接收方复核员标识查询相应的接收方备份票据数据。
在其中一个实施例中，接收方设备包括接收方初审员对应的第一接收方设备，以及接收方复核员对应的第二接收方设备。第一接收方设备和第二接收方设备分别执行上述由接收方设备执行的相关操作。
上述实施例中，根据接收方初审员的初审意见数据和接收方复核员的复核意见数据，确定最终的审核意见数据，以免因接收方初审员审核错误或操作失误等原因而导致票据数据的错误回退，保证了票据数据回退的准确性。而且，通过双重审核能够有效保证票据修改数据的准确性。
在其中一个实施例中，根据复核意见数据和初审意见数据得到票据数据对应的审核意见数据之后，方法还包括：当复核意见数据表示不同意初审意见数据时，接收方设备触发生成票据标识对应的票据数据重审请求，并借助于区块链节点将初审意见数据、复核意见数据和票据数据写入数据区块；接收方设备根据票据数据重审请求，从区块链节点中查找与票据标识对应的票据数据，并返回至通过接收方初审界面将票据数据展示给接收方初审员的步骤继续执行。
票据数据重审请求用于指示接收方设备将票据数据展示给接收方初审员进行重新审核。具体地，当复核意见数据表示不同意初审意见数据时，不论初审意见数据表示审核通过还是审核未通过，接收方设备均触发生成携带有票据标识的票据数据重审请求，并将审核的票据数据、初审意见数据和复核意见数据发送至区块链节点。区块链节点对接收到的票据数据、初审意见数据和复核意见数据执行区块链入链操作，以将该票据数据、初审意见数据和复核意见数据写入数据区块。进一步地，接收方设备根据触发生成的票据数据重审请求，从区块链节点中查找与票据标识对应的票据数据，并返回至通过接收方初审界面将查询到的票据数据展示给接收方初审员的步骤继续执行，直至复核迭代停止条件时，停止上述迭代过程。迭代停止条件比如复核意见数据标识同意初审意见数据，或者，迭代次数达到预设次数。
可以理解的是，当迭代次数达到预设次数时，接收方设备可触发生成表示线下协商的提示信息，并展示给接收方初审员和/或接收方复核员，以指示接收方初审员与接收方复核员通过线下协商的方式确定票据数据的审核意见数据。
上述实施例中，当接收方初审员与接收方复核员对票据数据的审核意见不一致时，触发票据数据重审流程，可以提高票据数据的可靠性和真实性。
如图3所示，在其中一个实施例中，提供了一种票据数据回退方法，方法包括：
S302，开票方设备从区块链节点中查找票据标识对应的初始票据数据。
S304，开票方设备通过开票方操作界面将初始票据数据展示给开票方操作员，并获取开票方操作员针对初始票据数据触发的票据修改数据。
S306，开票方设备触发生成票据标识对应的票据数据初核请求，并将票据修改数据发 送至区块链节点，票据修改数据用于指示区块链节点将票据修改数据写入数据区块。
S308，开票方设备根据票据数据初核请求，从区块链节点中查找与票据标识对应的票据修改数据，将查找的票据修改数据通过开票方审核界面展示给开票方审核员，获取开票方审核员针对展示的票据修改数据触发的初核意见数据。
S310，当初核意见数据表示审核未通过时，开票方设备查询与票据标识对应的开票方备份票据数据，借助于区块链节点将开票方备份票据数据和初核意见数据写入数据区块，并将写入数据区块的开票方备份票据数据作为当前最新版本的票据数据。
S312，开票方设备触发生成携带有票据标识的票据数据审核请求。
S314，接收方设备接收开票方设备发送的携带有票据标识的票据数据审核请求。
S316，接收方设备根据票据数据审核请求，从区块链节点中查找与票据标识对应的当前最新版本的票据数据。
S318，接收方设备通过接收方初审界面将票据数据展示给接收方初审员，获取接收方初审员针对票据数据触发的初审意见数据，触发生成票据标识对应的票据数据复核请求，并借助于区块链节点将初审意见数据和票据数据写入数据区块。
S320，接收方设备根据票据数据复核请求，从区块链节点中查找与票据标识对应的初审意见数据和票据数据，通过接收方复核界面将查找的初审意见数据和票据数据展示给接收方复核员。
S322，接收方设备获取接收方复核员针对展示的初审意见数据和票据数据触发的复核意见数据，并根据复核意见数据和初审意见数据得到票据数据对应的审核意见数据。
S324，当审核意见数据表示审核未通过时，接收方设备查询与票据标识对应的接收方备份票据数据，将接收方备份票据数据和审核意见数据发送至区块链节点；接收方备份票据数据是在接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；发送的接收方备份票据数据和审核意见数据，用于指示区块链节点将接收方备份票据数据和审核意见数据写入数据区块。
S326，当审核意见数据表示审核通过时，接收方设备将票据数据和审核意见数据发送至区块链节点；发送的票据数据和审核意见数据，用于指示区块链节点将票据数据和审核意见数据写入数据区块。
S328，当复核意见数据表示不同意初审意见数据时，接收方设备触发生成票据标识对应的票据数据重审请求，并借助于区块链节点将初审意见数据、复核意见数据和票据数据写入数据区块。
S330，接收方设备根据票据数据重审请求，从区块链节点中查找与票据标识对应的票据数据，并返回至步骤S318继续执行。
在其中一个实施例中，区块链节点执行的区块链入链操作包括以下步骤：区块链节点基于共识机制对待入链的数据进行共识运算，当共识通过时，生成与该待入链的数据对应的数据区块，并将生成的数据区块写入区块链中。可以理解的是，当区块链生成与待入链 的数据对应的数据区块时，对应更新票据标识对应的版本号，作为票据标识当前最新的版本号，并将该版本号写入数据区块中。
在其中一个实施例中，接收方设备和开票方设备可以是同一个计算机设备，比如终端或服务器。开票方操作员、开票方审核员、接收方初审员和接收方复核员可基于各自对应的账号和密码登录该计算机设备，并执行相应的操作。
应该理解的是，虽然图2-3的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2-3中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
在其中一个实施例中，如图1所示，提供了一种票据数据回退系统，包括：接收方设备102、开票方设备104和区块链节点106；
开票方设备104，用于向接收方设备102发送携带有票据标识的票据数据审核请求；
接收方设备102，用于根据票据数据审核请求，从区块链节点106中查找与票据标识对应的当前最新版本的票据数据；通过接收方审核界面将票据数据展示给接收方审核员，并获取接收方审核员针对票据数据触发的审核意见数据；
接收方设备102，还用于当审核意见数据表示审核未通过时，查询与票据标识对应的接收方备份票据数据，将接收方备份票据数据和审核意见数据发送至区块链节点106；接收方备份票据数据是在接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；
区块链节点106，用于将接收方备份票据数据和审核意见数据写入数据区块。
在其中一个实施例中，接收方设备102，还用于根据票据标识生成备份数据获取请求，将备份数据获取请求发送至区块链节点106；区块链节点106，还用于根据备份数据获取请求查询与票据标识对应的当前最新版本的接收方备份票据数据，并将查询到的接收方备份票据数据反馈至接收方设备102。
在其中一个实施例中，接收方设备102，还用于当审核意见数据表示审核通过时，将票据数据和审核意见数据发送至区块链节点106；区块链节点106，还用于将票据数据和审核意见数据写入数据区块。
在其中一个实施例中，开票方设备104，还用于从区块链节点中查找票据标识对应的初始票据数据；通过开票方操作界面将初始票据数据展示给开票方操作员，并获取开票方操作员针对初始票据数据触发的票据修改数据；将票据修改数据发送至区块链节点106；触发生成携带有票据标识的票据数据审核请求；区块链节点106，还用于将票据修改数据 写入数据区块，并将写入数据区块的票据修改数据作为当前最新版本的票据数据。
在其中一个实施例中，开票方设备104，还用于触发生成票据标识对应的票据数据初核请求，并将票据修改数据发送至区块链节点；区块链节点106，还用于将票据修改数据写入数据区块；开票方设备104，还用于根据票据数据初核请求，从区块链节点106中查找与票据标识对应的票据修改数据，将查找的票据修改数据通过开票方审核界面展示给开票方审核员，获取开票方审核员针对展示的票据修改数据触发的初核意见数据；当初核意见数据表示审核未通过时，查询与票据标识对应的开票方备份票据数据，借助于区块链节点106将开票方备份票据数据和初核意见数据写入数据区块，并将写入数据区块的开票方备份票据数据作为当前最新版本的票据数据。
在其中一个实施例中，接收方审核界面包括接收方初审界面和接收方复核界面；接收方审核员包括接收方初审员和接收方复核员；接收方设备102，还用于通过接收方初审界面将票据数据展示给接收方初审员，获取接收方初审员针对票据数据触发的初审意见数据，触发生成票据标识对应的票据数据复核请求，并借助于区块链节点106将初审意见数据和票据数据写入数据区块；接收方设备102，还用于根据票据数据复核请求，从区块链节点106中查找与票据标识对应的初审意见数据和票据数据，通过接收方复核界面将查找的初审意见数据和票据数据展示给接收方复核员；获取接收方复核员针对展示的初审意见数据和票据数据触发的复核意见数据，并根据复核意见数据和初审意见数据得到票据数据对应的审核意见数据。
在其中一个实施例中，接收方设备102，还用于当复核意见数据表示不同意初审意见数据时，触发生成票据标识对应的票据数据重审请求，并借助于区块链节点106将初审意见数据、复核意见数据和票据数据写入数据区块；接收方设备102，还用于根据票据数据重审请求，从区块链节点106中查找与票据标识对应的票据数据，并返回至通过接收方初审界面将票据数据展示给接收方初审员的步骤继续执行。
关于票据数据回退系统的具体限定可以参见上文中对于票据数据回退方法的限定，在此不再赘述。
在其中一个实施例中，提供了一种计算机设备，该计算机设备可以是接收方设备、开票方设备或区块链节点，其内部结构图可以如图4所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机可读存储介质计算机可读存储介质和数据库。该内存储器为非易失性存储介质中的操作系统和计算机可读存储介质计算机可读存储介质的运行提供环境。该计算机设备的数据库用于存储票据数据。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读存储介质计算机可读存储介质被处理器执行时以实现一种票据数据回退方法。
本领域技术人员可以理解，图4中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读存储介质计算机可读存储介质来指令相关的硬件来完成，的计算机可读存储介质计算机可读存储介质可存储于一非易失性计算机可读取存储介质中，该计算机可读存储介质计算机可读存储介质在执行时，可包括如上述各方法的实施例的流程。本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种票据数据回退方法，包括：
    接收方设备接收开票方设备发送的携带有票据标识的票据数据审核请求；
    所述接收方设备根据所述票据数据审核请求，从区块链节点中查找与所述票据标识对应的当前最新版本的票据数据；
    所述接收方设备通过接收方审核界面将所述票据数据展示给接收方审核员，并获取所述接收方审核员针对所述票据数据触发的审核意见数据；及
    当所述审核意见数据表示审核未通过时，所述接收方设备查询与所述票据标识对应的接收方备份票据数据，将所述接收方备份票据数据和所述审核意见数据发送至所述区块链节点；所述接收方备份票据数据是在所述接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；
    发送的所述接收方备份票据数据和所述审核意见数据，用于指示所述区块链节点将所述接收方备份票据数据和所述审核意见数据写入数据区块。
  2. 根据权利要求1所述的方法，其特征在于，所述接收方设备查询与所述票据标识对应的接收方备份票据数据，包括：
    所述接收方设备根据所述票据标识生成备份数据获取请求，将所述备份数据获取请求发送至所述区块链节点；及
    所述接收方设备接收所述区块链节点根据所述备份数据获取请求查询并反馈的、且与所述票据标识对应的当前最新版本的接收方备份票据数据。
  3. 根据权利要求1所述的方法，其特征在于，所述获取所述接收方审核员针对所述票据数据触发的审核意见数据之后，所述方法还包括：
    当所述审核意见数据表示审核通过时，所述接收方设备将所述票据数据和所述审核意见数据发送至所述区块链节点；及
    发送的所述票据数据和所述审核意见数据，用于指示所述区块链节点将所述票据数据和所述审核意见数据写入数据区块。
  4. 根据权利要求1所述的方法，其特征在于，所述接收方设备接收开票方设备发送的携带有票据标识的票据数据审核请求之前，所述方法还包括：
    所述开票方设备从区块链节点中查找所述票据标识对应的初始票据数据；
    所述开票方设备通过开票方操作界面将所述初始票据数据展示给开票方操作员，并获取所述开票方操作员针对所述初始票据数据触发的票据修改数据；
    所述开票方设备将所述票据修改数据发送至所述区块链节点，所述票据修改数据用于指示所述区块链节点将所述票据修改数据写入数据区块，并将写入数据区块的所述票据修改数据作为当前最新版本的票据数据；及
    所述开票方设备触发生成携带有所述票据标识的票据数据审核请求。
  5. 根据权利要求4所述的方法，其特征在于，所述开票方设备将所述票据修改数据 发送至所述区块链节点，所述票据修改数据用于指示所述区块链节点将所述票据修改数据写入数据区块，并将写入数据区块的所述票据修改数据作为当前最新版本的票据数据，包括：
    所述开票方设备触发生成所述票据标识对应的票据数据初核请求，并将所述票据修改数据发送至所述区块链节点，所述票据修改数据用于指示所述区块链节点将所述票据修改数据写入数据区块；
    所述开票方设备根据所述票据数据初核请求，从所述区块链节点中查找与所述票据标识对应的所述票据修改数据，将查找的所述票据修改数据通过开票方审核界面展示给开票方审核员，获取所述开票方审核员针对展示的所述票据修改数据触发的初核意见数据；及
    当所述初核意见数据表示审核未通过时，所述开票方设备查询与所述票据标识对应的开票方备份票据数据，借助于所述区块链节点将所述开票方备份票据数据和所述初核意见数据写入数据区块，并将写入数据区块的所述开票方备份票据数据作为当前最新版本的票据数据。
  6. 根据权利要求5所述的方法，其特征在于，所述开票方设备将所述票据修改数据发送至所述区块链节点，所述票据修改数据用于指示所述区块链节点将所述票据修改数据写入数据区块，并将写入数据区块的所述票据修改数据作为当前最新版本的票据数据，还包括：
    当所述初核意见数据表示审核通过时，所述开票方设备将所述初核意见数据与审核通过的票据修改数据发送至所述区块链节点，以指示所述区块链节点将所述初核意见数据与所述审核通过的票据修改数据写入数据区块，并将审核通过且写入数据区块的票据修改数据作为当前最新版本的票据数据。
  7. 根据权利要求1所述的方法，其特征在于，所述接收方审核界面包括接收方初审界面和接收方复核界面；所述接收方审核员包括接收方初审员和接收方复核员；所述接收方设备通过接收方审核界面将所述票据数据展示给接收方审核员，并获取所述接收方审核员针对所述票据数据触发的审核意见数据包括：
    所述接收方设备通过接收方初审界面将所述票据数据展示给接收方初审员，获取所述接收方初审员针对所述票据数据触发的初审意见数据，触发生成所述票据标识对应的票据数据复核请求，并借助于所述区块链节点将所述初审意见数据和所述票据数据写入数据区块；
    所述接收方设备根据所述票据数据复核请求，从所述区块链节点中查找与所述票据标识对应的所述初审意见数据和所述票据数据，通过接收方复核界面将查找的所述初审意见数据和所述票据数据展示给接收方复核员；及
    所述接收方设备获取所述接收方复核员针对展示的所述初审意见数据和所述票据数据触发的复核意见数据，并根据所述复核意见数据和所述初审意见数据得到所述票据数据对应的审核意见数据。
  8. 根据权利要求7所述的方法，其特征在于，所述根据所述复核意见数据和所述初审意见数据得到所述票据数据对应的审核意见数据之后，所述方法还包括：
    当所述复核意见数据表示不同意初审意见数据时，所述接收方设备触发生成所述票据标识对应的票据数据重审请求，并借助于所述区块链节点将所述初审意见数据、所述复核意见数据和所述票据数据写入数据区块；及
    所述接收方设备根据所述票据数据重审请求，从所述区块链节点中查找与所述票据标识对应的票据数据，并返回至所述通过接收方初审界面将所述票据数据展示给接收方初审员的步骤继续执行。
  9. 根据权利要求1所述的方法，其特征在于，所述接收方设备根据所述票据数据审核请求，从区块链节点中查找与所述票据标识对应的当前最新版本的票据数据，包括：
    所述接收方设备根据所述票据数据审核请求确定所述票据标识，将携带所述票据标识和接收方标识的第一票据数据获取请求发送至区块链节点；
    所述第一票据数据获取请求，用于指示所述区块链节点根据所述接收方标识对接收方的权限进行校验，并在校验通过时，查找与所述票据标识对应的当前最新版本的票据数据；及
    接收所述区块链节点反馈的所述当前最新版本的票据数据。
  10. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述审核意见数据表示审核通过时，所述接收方设备根据所述票据标识当前对应的接收方备份票据数据的存储位置确定更新方式；
    根据审核通过的所述票据数据按照所述更新方式，更新所述票据标识当前对应的接收方备份票据数据。
  11. 一种票据数据回退系统，包括：接收方设备、开票方设备和区块链节点；
    所述开票方设备，用于向所述接收方设备发送携带有票据标识的票据数据审核请求；
    所述接收方设备，用于根据所述票据数据审核请求，从所述区块链节点中查找与所述票据标识对应的当前最新版本的票据数据；通过接收方审核界面将所述票据数据展示给接收方审核员，并获取所述接收方审核员针对所述票据数据触发的审核意见数据；
    所述接收方设备，还用于当所述审核意见数据表示审核未通过时，查询与所述票据标识对应的接收方备份票据数据，将所述接收方备份票据数据和所述审核意见数据发送至所述区块链节点；所述接收方备份票据数据是在所述接收方审核员触发的审核意见数据表示审核通过时备份的票据数据；及
    所述区块链节点，用于将所述接收方备份票据数据和所述审核意见数据写入数据区块。
  12. 根据权利要求11所述的系统，其特征在于，所述接收方设备，还用于根据所述票据标识生成备份数据获取请求，将所述备份数据获取请求发送至所述区块链节点；及
    所述区块链节点，还用于根据所述备份数据获取请求查询与所述票据标识对应的当前最新版本的接收方备份票据数据，并将查询到的接收方备份票据数据反馈至所述接收方设备。
  13. 根据权利要求11所述的系统，其特征在于，所述接收方设备，还用于当所述审核意见数据表示审核通过时，将所述票据数据和所述审核意见数据发送至所述区块链节点；及
    所述区块链节点，还用于将所述票据数据和所述审核意见数据写入数据区块。
  14. 根据权利要求11所述的系统，其特征在于，所述开票方设备，还用于从区块链节点中查找所述票据标识对应的初始票据数据；通过开票方操作界面将所述初始票据数据展示给开票方操作员，并获取所述开票方操作员针对所述初始票据数据触发的票据修改数据；将所述票据修改数据发送至所述区块链节点；触发生成携带有所述票据标识的票据数据审核请求；及
    所述区块链节点，还用于将所述票据修改数据写入数据区块，并将写入数据区块的所述票据修改数据作为当前最新版本的票据数据。
  15. 根据权利要求14所述的系统，其特征在于，所述开票方设备，还用于触发所述生成票据标识对应的票据数据初核请求，并将所述票据修改数据发送至所述区块链节点；
    所述区块链节点，还用于将所述票据修改数据写入数据区块；及
    所述开票方设备，还用于根据所述票据数据初核请求，从所述区块链节点中查找与所述票据标识对应的所述票据修改数据，将查找的所述票据修改数据通过开票方审核界面展示给开票方审核员，获取所述开票方审核员针对展示的所述票据修改数据触发的初核意见数据；当所述初核意见数据表示审核未通过时，查询与所述票据标识对应的开票方备份票据数据，借助于所述区块链节点将所述开票方备份票据数据和所述初核意见数据写入数据区块，并将写入数据区块的所述开票方备份票据数据作为当前最新版本的票据数据。
  16. 根据权利要求15所述的系统，其特征在于，所述开票方设备，还用于当所述初核意见数据表示审核通过时，将所述初核意见数据与审核通过的票据修改数据发送至所述区块链节点；
    所述区块链节点，还用于将所述初核意见数据与所述审核通过的票据修改数据写入数据区块，并将审核通过且写入数据区块的票据修改数据作为当前最新版本的票据数据。
  17. 根据权利要求11所述的系统，其特征在于，所述接收方审核界面包括接收方初审界面和接收方复核界面；所述接收方审核员包括接收方初审员和接收方复核员；所述接收方设备，还用于通过接收方初审界面将所述票据数据展示给接收方初审员，获取所述接收方初审员针对所述票据数据触发的初审意见数据，触发生成所述票据标识对应的票据数据复核请求，并借助于所述区块链节点将所述初审意见数据和所述票据数据写入数据区块；及
    所述接收方设备，还用于根据所述票据数据复核请求，从所述区块链节点中查找与所 述票据标识对应的所述初审意见数据和所述票据数据，通过接收方复核界面将查找的所述初审意见数据和所述票据数据展示给接收方复核员；获取所述接收方复核员针对展示的所述初审意见数据和所述票据数据触发的复核意见数据，并根据所述复核意见数据和所述初审意见数据得到所述票据数据对应的审核意见数据。
  18. 根据权利要求17所述的系统，其特征在于，所述接收方设备，还用于当所述复核意见数据表示不同意初审意见数据时，触发生成所述票据标识对应的票据数据重审请求，并借助于所述区块链节点将所述初审意见数据、所述复核意见数据和所述票据数据写入数据区块；及
    所述接收方设备，还用于根据所述票据数据重审请求，从所述区块链节点中查找与所述票据标识对应的票据数据，并返回至所述通过接收方初审界面将所述票据数据展示给接收方初审员的步骤继续执行。
  19. 根据权利要求11所述的系统，其特征在于，所述接收方设备，还用于根据所述票据数据审核请求确定所述票据标识，将携带所述票据标识和接收方标识的第一票据数据获取请求发送至区块链节点；
    所述区块链节点，还用于根据所述接收方标识对接收方的权限进行校验，并在校验通过时，查找与所述票据标识对应的当前最新版本的票据数据；及
    所述接收方设备，还用于接收所述区块链节点反馈的所述当前最新版本的票据数据。
  20. 根据权利要求11所述的系统，其特征在于，所述接收方设备，还用于当所述审核意见数据表示审核通过时，根据所述票据标识当前对应的接收方备份票据数据的存储位置确定更新方式；根据审核通过的所述票据数据按照所述更新方式，更新所述票据标识当前对应的接收方备份票据数据。
PCT/CN2019/122719 2019-05-20 2019-12-03 票据数据回退方法和系统 WO2020233087A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910419376.9 2019-05-20
CN201910419376.9A CN110223127A (zh) 2019-05-20 2019-05-20 票据数据回退方法和系统

Publications (1)

Publication Number Publication Date
WO2020233087A1 true WO2020233087A1 (zh) 2020-11-26

Family

ID=67821689

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/122719 WO2020233087A1 (zh) 2019-05-20 2019-12-03 票据数据回退方法和系统

Country Status (2)

Country Link
CN (1) CN110223127A (zh)
WO (1) WO2020233087A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4307058A1 (de) 2022-07-15 2024-01-17 Turck Holding GmbH Station zum einsatz in einem feldnetz zwischen einem oder mehreren feldgeräten und einer zentraleinheit sowie in einen modulträger auswechselbar einsteckbares switch-modul

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110223127A (zh) * 2019-05-20 2019-09-10 深圳壹账通智能科技有限公司 票据数据回退方法和系统
CN110213357B (zh) * 2019-05-22 2022-04-22 深圳壹账通智能科技有限公司 业务数据回退方法、装置、计算机设备和存储介质
CN110599270B (zh) * 2019-09-16 2024-05-10 腾讯科技（深圳）有限公司 电子票据生成方法、装置和计算机设备
CN110853216B (zh) * 2019-10-18 2022-06-17 深圳壹账通智能科技有限公司 信息存储方法、装置、存储介质和计算机设备
CN111210288A (zh) * 2019-12-26 2020-05-29 大象慧云信息技术有限公司 基于税控服务器的发票批量开具作业优化调度方法及系统
CN113205346A (zh) * 2021-04-24 2021-08-03 上海赛可出行科技服务有限公司 一种票据可撤销的去中心化的加密认证和鉴权方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040054910A1 (en) * 2002-09-13 2004-03-18 Nec Corporation Computer network system including an information collector computer
CN109067541A (zh) * 2018-06-29 2018-12-21 阿里巴巴集团控股有限公司 基于区块链的数据验证方法及装置、电子设备
CN109191272A (zh) * 2018-08-17 2019-01-11 腾讯科技（深圳）有限公司 关于电子票据的数据处理方法、装置、存储介质和设备
CN109325812A (zh) * 2018-08-24 2019-02-12 深圳市智税链科技有限公司 关于电子票据的数据处理方法、装置、存储介质和设备
CN110223127A (zh) * 2019-05-20 2019-09-10 深圳壹账通智能科技有限公司 票据数据回退方法和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109165943B (zh) * 2018-08-20 2023-01-03 深圳市智税链科技有限公司 关于电子票据的数据处理方法、装置、存储介质和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040054910A1 (en) * 2002-09-13 2004-03-18 Nec Corporation Computer network system including an information collector computer
CN109067541A (zh) * 2018-06-29 2018-12-21 阿里巴巴集团控股有限公司 基于区块链的数据验证方法及装置、电子设备
CN109191272A (zh) * 2018-08-17 2019-01-11 腾讯科技（深圳）有限公司 关于电子票据的数据处理方法、装置、存储介质和设备
CN109325812A (zh) * 2018-08-24 2019-02-12 深圳市智税链科技有限公司 关于电子票据的数据处理方法、装置、存储介质和设备
CN110223127A (zh) * 2019-05-20 2019-09-10 深圳壹账通智能科技有限公司 票据数据回退方法和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4307058A1 (de) 2022-07-15 2024-01-17 Turck Holding GmbH Station zum einsatz in einem feldnetz zwischen einem oder mehreren feldgeräten und einer zentraleinheit sowie in einen modulträger auswechselbar einsteckbares switch-modul
DE102022117693A1 (de) 2022-07-15 2024-01-18 Turck Holding Gmbh Station zum Einsatz in einem Feldnetz zwischen einem oder mehreren Feldgeräten und einer Zentraleinheit sowie in einen Modulträger auswechselbar einsteckbares Switch-Modul

Also Published As

Publication number Publication date
CN110223127A (zh) 2019-09-10

Similar Documents

Publication Publication Date Title
WO2020233087A1 (zh) 票据数据回退方法和系统
US11562375B2 (en) Blockchain-based data verification method, apparatus, and electronic device
WO2020233091A1 (zh) 业务数据回退方法、装置、计算机设备和存储介质
CN109474578A (zh) 报文消息校验方法、装置、计算机设备和存储介质
US20210049715A1 (en) Blockchain-based data procesing method, apparatus, and electronic device
CN110378755B (zh) 电子发票生成方法、装置、计算机设备和存储介质
CN109493048B (zh) 基于区块链的财务记账方法、装置、设备及存储介质
CN111464499A (zh) 电子仓单溯源方法、装置、计算机设备及存储介质
CN107861991B (zh) 单据数据处理方法、装置、计算机设备和存储介质
CN110633963A (zh) 电子票据处理方法、装置、计算机可读存储介质和设备
CN110941630A (zh) 一种数据库运维方法、装置及系统
US10795882B2 (en) Blockchain-based data compression and searching
CN110599357A (zh) 基于区块链的保险业务数据处理方法、装置和存储介质
WO2019153598A1 (zh) 客户风险等级管理方法、服务器及计算机可读存储介质
CN110866289B (zh) 基于区块链的数据处理方法、装置、服务器及存储介质
WO2021012572A1 (zh) 区块链交易数据处理方法、装置、计算机设备和存储介质
WO2019033741A1 (zh) 投资产品的资源处理方法、装置、存储介质和计算机设备
CN112307049A (zh) 数据库的读写分离方法、装置、设备及可读存储介质
CN110599270A (zh) 电子票据生成方法、装置和计算机设备
US10956408B2 (en) Data transformation tool
CN112214456B (zh) 一种房产数据处理方法、装置和电子设备
CN110942314A (zh) 异常账户监管方法及装置
CN111522881A (zh) 业务数据处理方法、装置、服务器及存储介质
EP3779755B1 (en) A computer-implemented method for cross-chain-interoperability
CN110765131A (zh) 货源数据的数据压缩方法、装置、计算机设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19929837

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19929837

Country of ref document: EP

Kind code of ref document: A1