A transaction audit method, device and equipment

Abstract

The embodiment of the present application discloses a transaction audit method, apparatus and equipment, wherein the transaction audit method includes: obtaining a target pending transaction, the target pending transaction is sent by a user device to a management node device, the target pending transaction includes a transaction request and audit information, the audit information includes the registration information of the user device, the early warning policy change notification or the early warning policy execution information, the registration information is used to verify the identity of the user device, the early warning policy change notification is used to audit the changed early warning policy, and the early warning policy execution information is used to audit the early warning policy execution event of the user device; based on the audit information, the target pending transaction is audited; if the target pending transaction is audited, the transaction request is responded to to execute the first transaction operation corresponding to the target pending transaction. By adopting the embodiment of the present application, the transaction audit process can be made open and transparent, and the reliability of the transaction audit results can be improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a transaction audit method, device and equipment. Background Art

[0002] Currently, there are many transaction review scenarios. For example, when opening a bank account, the bank reviews the credit information and identity information of the account holder; when registering a company, the Industrial and Commercial Administration Bureau reviews the company's registration information; when registering for an exam, the recruitment platform reviews the candidate's registration information.

[0003] In these transaction audit scenarios, the audit process of the auditing agency (such as banks, industrial and commercial administration bureaus, recruitment platforms, etc.) is opaque to the audited parties (such as account openers, enterprises, test takers, etc.). The audited parties cannot know the transaction audit process and can only obtain the transaction audit results, which makes the reliability of the transaction audit results low. Summary of the Invention

[0004] The embodiments of the present application provide a transaction audit method, apparatus, and device, which can make the transaction audit process open and transparent and improve the reliability of the transaction audit results.

[0005] In a first aspect, an embodiment of the present application provides a transaction audit method, which is performed by a management node device in a blockchain network. The blockchain network includes multiple blockchain node devices, and the management node device is at least one blockchain node device in the blockchain network. The transaction audit method includes:

[0006] Obtain the target pending transaction. The target pending transaction is sent by the user device to the management node device. The target pending transaction includes a transaction request and audit information. The audit information includes the registration information of the user device, the early warning policy change notification or the early warning policy execution information. The registration information is used to verify the identity of the user device, the early warning policy change notification is used to audit the changed early warning policy, and the early warning policy execution information is used to audit the early warning policy execution event of the user device; based on the audit information, the target pending transaction is audited; if the target pending transaction is audited and passed, respond to the transaction request to execute the first transaction operation corresponding to the target pending transaction.

[0007] In a second aspect, embodiments of the present application provide a transaction auditing device that implements the transaction auditing method described in the first aspect. The functionality can be implemented via hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the functionality described above.

[0008] In one implementation, the transaction auditing apparatus includes: an acquisition unit, an auditing unit, and an execution unit. The acquisition unit is configured to acquire a target pending transaction, which is sent by a user device to a management node device. The target pending transaction includes a transaction request and audit information, and the audit information includes the user device's registration information, an early warning policy change notification, or early warning policy execution information. The registration information is used to verify the identity of the user device, the early warning policy change notification is used to audit the changed early warning policy, and the early warning policy execution information is used to audit the early warning policy execution event of the user device. The auditing unit is configured to audit the target pending transaction based on the audit information. The execution unit is configured to respond to the transaction request to execute a first transaction operation corresponding to the target pending transaction if the target pending transaction passes the audit.

[0009] In a third aspect, an embodiment of the present application provides a transaction audit device, which includes a memory and a processor, wherein the memory is used to store computer programs; the processor calls the computer program stored in the memory to execute the transaction audit method described in the first aspect above.

[0010] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program used by a transaction auditing device, which includes program instructions for executing the above-mentioned first aspect.

[0011] In an embodiment of the present application, a user device sends a target pending transaction to a management node device in a blockchain network. After the management node device obtains the target pending transaction, it audits the target pending transaction based on the audit information included in the target pending transaction. If the audit of the target pending transaction is passed, the management node device responds to the transaction request included in the target pending transaction to execute the first transaction operation corresponding to the target pending transaction. The audit information includes the registration information of the user device, the early warning policy change notification, or the early warning policy execution information. The registration information of the user device is used to verify the identity of the user device, the early warning policy change notification of the user device is used to audit the changed early warning policy, and the early warning policy execution status of the user device is used to audit the early warning policy execution event of the user device. The management node device is a blockchain node device in a blockchain network. The audit process of the target pending transaction by the management node device is witnessed by each blockchain node device in the blockchain network. The audit process of the target pending transaction by the management node device is open and transparent. Therefore, the first transaction operation corresponding to the target pending transaction executed by the management node device in response to the transaction request has high reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. 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 any creative work.

[0013] Figure 1 This is a schematic diagram of the architecture of a transaction audit system provided in an embodiment of the present application;

[0014] Figure 2 This is a flowchart of an early warning strategy review solution provided by an embodiment of the present application;

[0015] Figure 3 This is a flowchart of a transaction audit method provided by an embodiment of the present application;

[0016] Figure 4 This is a flowchart of another transaction audit method provided by an embodiment of the present application;

[0017] Figure 5 This is a flowchart of another transaction audit method provided by an embodiment of the present application;

[0018] Figure 6 This is a flowchart of another transaction audit solution provided by an embodiment of the present application;

[0019] Figure 7 This is a schematic diagram of the structure of a transaction audit device provided in an embodiment of the present application;

[0020] Figure 8 This is a structural diagram of a transaction audit device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0022] The present application embodiments relate to blockchain and blockchain networks. Blockchain is a novel application model for computer technologies such as distributed data storage, peer-to-peer (P2P) transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized infrastructure with distributed storage characteristics. Specifically, it is a data structure that organizes data blocks in a chronological manner similar to a linked list. It can securely store data that has a sequential relationship and can be verified within the system, and uses cryptography to ensure that the data cannot be tampered with or forged.

[0023] A blockchain network includes multiple blockchain node devices, and the blockchain is stored in each of these devices. For example, a blockchain network may include a management node device, a first audit node device, a second audit node device, and other blockchain node devices. Blockchain node devices in a blockchain network can include clients, servers, terminals, and so on. Terminals can include mobile terminals, personal computers (PCs), or tablet personal computers (Tablet PCs).

[0024] The present application embodiment proposes a transaction audit scheme based on a blockchain network. In this transaction audit scheme, after a management node device in the blockchain network receives a target pending transaction sent by a user device, the management node device audits the target pending transaction. If the target pending transaction is audited, the management node device executes a first transaction operation corresponding to the target pending transaction. The management node device in the blockchain network audits the target pending transaction, and other blockchain node devices in the blockchain network can witness the management node device's audit process of the target pending transaction, making the transaction audit process open and transparent and improving the reliability of the transaction audit results.

[0025] Among them, the user device is a node device outside the blockchain network, and the user device can be a client, server, terminal, etc. The terminal can be a mobile terminal, personal computer (Personal Computer, PC) terminal or portable computer (Tablet Personal Computer, Tablet PC) terminal, etc.

[0026] The target pending transaction includes a transaction request and audit information. The transaction request can be used to request the management node device to audit the target pending transaction based on the audit information. Once the audit is successful, the management node device can be requested to execute the first transaction operation corresponding to the target pending transaction. The audit information can include registration information, warning policy change notifications, or warning policy execution information. Registration information can be used to verify the identity of the user device. Warning policy change notifications can be used to audit the changed warning policy. Warning policy execution information can be used to audit warning policy execution events on the user device.

[0027] Based on the above description, see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a transaction audit system provided by an embodiment of the present application. Figure 1 As shown, the transaction audit system includes a management node device 101, a first audit node device 102, a second audit node device 103, and a user device 104. Management node device 101, first audit node device 102, and second audit node device 103 are blockchain node devices in a blockchain network. The fact that the blockchain network includes management node device 101, first audit node device 102, and second audit node device 103 is merely an example. A blockchain network may include multiple management node devices 101, multiple first audit node devices 102, and multiple second audit node devices 103. User device 104 is a node device outside the blockchain network.

[0028] In a transaction audit system consisting of a management node device 101, a first audit node device 102, a second audit node device 103 and a user device 104, the user device 104 sends the target pending transaction to the management node device 101. After receiving the target pending transaction, the management node device 101 audits the target pending transaction based on the audit information included in the target pending transaction. If the target pending transaction is audited, the management node device 101 responds to the transaction request included in the target pending transaction and executes the first transaction operation corresponding to the target pending transaction.

[0029] In one implementation, the audit method used by management node device 101 to audit the target pending transaction varies depending on the audit information. If the audit information includes registration information, management node device 101 may directly audit the registration information. If the audit information includes a warning policy change notification or warning policy execution information, management node device 101 may request first audit node device 102 or second audit node device 103 to assist in auditing the target pending transaction. The audit level of second audit node device 103 is higher than that of first audit node device 102, and the audit level of first audit node device 102 is higher than that of management node device 101.

[0030] In one implementation, the audit information may include registration information. The management node device 101 may verify the legitimacy of the registration information. If the legitimacy of the registration information passes the verification, the management node device 101 determines that the target pending transaction has passed the audit. To ensure the reliability of the audit results, the management node device 101 may utilize information systems associated with the management node device 101 (e.g., industrial and commercial systems, security department systems, etc.) to assist in the verification process.

[0031] In one implementation, the audit information may include a warning policy change notification. The management node device 101 may change the original warning policy of the user device 104 according to the warning policy change notification to obtain a changed warning policy. Since the management node device 101 has not reached the audit level that can verify the changed warning policy, the management node device 101 cannot verify the changed warning policy. Therefore, the management node device 101 may send the changed warning policy to the first audit node device 102. The first audit node device 102 verifies the changed warning policy and obtains a verification result. The first audit node device 102 sends the verification result to the management node device 101. If the verification result is verification passed, the management node device 101 may update the original policy information of the user device 104 to the changed warning policy, and the changed warning policy takes effect.

[0032] In one implementation, the audit information may include early warning policy execution information. The management node device 101 may respond to the early warning policy execution event of the user device 104 indicated by the early warning policy execution information, and generate a second transaction operation to be executed on the user device 104. The early warning policy execution event may be used to indicate the early warning policy execution status of the user device 104. Since the management node device 101 has not reached the audit level that can verify the second transaction operation, the management node device 101 cannot verify the second transaction operation. Therefore, the management node device 101 may send the second transaction operation to the second audit node device 103. The second audit node device 103 verifies the second transaction operation and obtains a verification result. The second audit node device 103 sends the verification result to the management node device 101. If the verification result is verification passed, the management node device 101 may execute the second transaction operation on the user device 104.

[0033] In one implementation, in order to reduce the audit load of the second audit node device 103 and ensure that the second transaction operation to be executed on the user device 104 generated by the management node device 101 is accurate, before the management node device 101 sends the second transaction operation to the second audit node device 103, the management node device 101 can first send the second transaction operation to the first audit node device 102, and the first audit node device 102 will first verify the second transaction operation to obtain a verification result. The first audit node device 102 will send the verification result to the management node device 101. If the verification result is that the verification is passed, the management node device 101 will send the second transaction operation to the second audit node device 103, and the second audit node device 103 will verify the second transaction operation again.

[0034] It can be understood that the transaction audit system 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 by the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

[0035] Taking the tax bureau's transaction review scenario as an example, the tax bureau has three transaction review positions: general business, business review, and business approval. Each position has multiple members. The tax bureau's working network is the aforementioned blockchain network, and the tax bureau assigns each position a blockchain account that uniquely identifies that position. Management node device 101 is a blockchain node device that the general business position logs in to using its blockchain account. First review node device 102 is a blockchain node device that the business review position logs in to using its blockchain account. Second review node device 103 is a blockchain node device that the business approval position logs in to using its blockchain account. In the tax bureau's review system, the business approval position has a higher review level than the business review position, which in turn has a higher review level than the general business position. User device 104 is a node device that users requesting the tax bureau to review transactions log in to using their user accounts, which uniquely identify them.

[0036] For example, an enterprise sends a target pending transaction to the tax bureau. The target pending transaction includes a transaction request and the enterprise's registration information. The transaction request is used to request the tax bureau to review the registration information and request the issuance of an electronic invoice. The registration information may include but is not limited to the enterprise's special invoice stamp, the enterprise's taxpayer identification number, and the enterprise's registration serial number. After receiving the target pending transaction, the comprehensive business post verifies the legitimacy of the enterprise's registration information. The comprehensive business post can request the security department system to assist in verifying the special invoice stamp and request the industrial and commercial system to assist in verifying the taxpayer identification number and registration serial number. If the legitimacy of the registration information is verified, the comprehensive management post can respond to the transaction request and issue an electronic invoice to the enterprise.

[0037] For example, an enterprise sends a target pending transaction to the tax bureau. The target pending transaction includes a transaction request and a warning strategy change notification. The transaction request is used to request the tax bureau to change the warning strategy. The tax bureau's review process for the target pending transaction based on the warning strategy change notification can be found in Figure 2 , Figure 2 It is a flow chart of a warning strategy review solution provided by an embodiment of the present application. After the comprehensive business post receives the target pending transaction, it performs a change operation on the original warning strategy of the enterprise according to the warning strategy change notification to obtain the changed warning strategy. The change operation may include but is not limited to a new operation, an edit operation, and a delete operation. Since the comprehensive business post has not reached the audit level that can verify the changed warning strategy, the comprehensive business post cannot verify the changed warning strategy. Therefore, the comprehensive business post sends the changed warning strategy to the business review post, and the business review post verifies the changed warning strategy. If the business review post passes the verification, the comprehensive business post can update the original warning strategy of the enterprise to the changed warning strategy, and the changed warning strategy takes effect.

[0038] For example, an enterprise sends a target pending transaction to the tax bureau, which includes a transaction request and early warning strategy execution information. The transaction request is used to request the tax bureau to review the early warning strategy execution information. The early warning strategy execution information indicates the enterprise's early warning strategy execution status (for example, whether the enterprise declares and pays taxes within the prescribed time limit, whether the enterprise applies for tax registration, change or cancellation of registration within the prescribed time limit, whether the enterprise reports all the enterprise's bank accounts to the tax bureau in accordance with regulations, or whether the enterprise's early warning value exceeds the early warning threshold, etc.). After the comprehensive business post receives the target pending transaction, the review process of the target pending transaction based on the early warning strategy execution information is as follows: If the early warning strategy execution information indicates that the enterprise has not declared and paid taxes within the prescribed time limit, the comprehensive business post generates a stop invoicing operation for the enterprise; the comprehensive business post cannot verify the stop invoicing operation, so the comprehensive business post sends the stop invoicing operation to the business review post, and the business review post verifies the stop invoicing operation; if the business review post passes the verification, the comprehensive business post sends the stop invoicing operation to the business approval post, and the business approval post verifies the stop invoicing operation again; if the business approval post passes the verification, the comprehensive business post stops issuing electronic invoices for the enterprise, and the enterprise will not be able to continue to issue electronic invoices.

[0039] In an embodiment of the present application, each blockchain node device in the blockchain network jointly witnesses the audit process of the target pending transaction by the management node device, making the audit process of the target pending transaction by the management node device open and transparent, improving the reliability of the transaction audit results, and the transaction operations corresponding to the target pending transaction executed by the management node device also have high reliability. In addition, the audit information included in the target pending transaction is different, and the audit methods of the target pending transaction by the management node device are also different. Different audit information corresponds to different audit methods, making the audit process of the target pending transaction by the management node device flexible and diverse, and improving the reliability of the transaction audit results. The process of auditing the target pending transaction also involves multi-level audits, which can reduce the audit load of audit devices at different audit levels on the one hand, and further improve the reliability of the audit results on the other hand.

[0040] based on Figure 1 For a schematic diagram of the transaction audit system architecture, see Figure 3 , Figure 3 : This is a flowchart of a transaction audit method provided by an embodiment of the present application. The transaction audit method can be jointly executed by the management node device and the user device in the above-mentioned transaction audit system. The transaction audit method may include the following steps S301 to S303:

[0041] Step S301: The management node device receives a target transaction to be processed sent by a user equipment.

[0042] The management node device can receive pending transactions sent by multiple user devices. For example, the management node device can receive a first pending transaction sent by a first user device, a second pending transaction sent by a second user device, a third pending transaction sent by a third user device, and so on. The management node device can store the multiple pending transactions received in the transaction list of the blockchain network. The transaction list of the blockchain network stores the received pending transactions in the form of a queue. Pending transactions stored first in the transaction list can be reviewed by the management node device first, and pending transactions stored later in the transaction list can be reviewed by the management node device later. The management node device can obtain the target pending transaction sent by the user device from the transaction list. The target pending transaction is any pending transaction in the transaction list.

[0043] In one implementation, after the management node device obtains the target pending transaction sent by the user device from the transaction list, the management node device can send a transaction collection notification to other blockchain node devices in the blockchain network. The transaction collection notification can include the transaction identifier of the target pending transaction. The transaction collection notification can be used to indicate that the target pending transaction corresponding to the transaction identifier is in a processed state, and other blockchain node devices in the blockchain network will not be able to review the target pending transaction.

[0044] In one implementation, the target pending transaction may include a transaction request and audit information. The audit information may include registration information, early warning policy change notification, or early warning policy execution information.

[0045] Step S302: The management node device audits the target pending transaction based on the audit information.

[0046] In one implementation, the audit information may include registration information, and the management node device may audit the target pending transaction based on the registration information. The execution process of the management node device auditing the target pending transaction based on the registration information may be referred to in Figure 4 Detailed description of steps S402 to S403 in the illustrated embodiment.

[0047] In one implementation, the audit information may include a warning policy change notification, and the management node device may audit the target pending transaction based on the warning policy change notification. The execution process of the management node device auditing the target pending transaction based on the warning policy change notification can be found in Figure 5 Detailed description of steps S502 to S506 in the illustrated embodiment.

[0048] In one implementation, the audit information may include early warning strategy execution information, and the management node device may audit the target pending transaction according to the early warning strategy execution information. The execution process of the management node device auditing the target pending transaction according to the early warning strategy execution information can be found in Figure 6 Detailed description of steps S602 to S606 in the illustrated embodiment.

[0049] Step S303: If the target pending transaction is approved, the management node device responds to the transaction request to execute the first transaction operation corresponding to the target pending transaction.

[0050] In one implementation, the audit information may include registration information. If the management node device approves the target pending transaction according to the registration information, the management node device may respond to the transaction request and execute the first transaction operation corresponding to the target pending transaction. The execution process of the management node device executing the first transaction operation corresponding to the target pending transaction can be found in Figure 4 Detailed description of step S404 in the illustrated embodiment.

[0051] In one implementation, the audit information may include a warning policy change notification. If the management node device approves the target pending transaction according to the warning policy change notification, the management node device may respond to the transaction request and execute the first transaction operation corresponding to the target pending transaction. The execution process of the management node device executing the first transaction operation corresponding to the target pending transaction can be found in Figure 5 Detailed description of step S507 in the illustrated embodiment.

[0052] In one implementation, the audit information may include early warning strategy execution information. If the management node device approves the target pending transaction according to the early warning strategy execution information, the management node device may respond to the transaction request and execute the first transaction operation corresponding to the target pending transaction. The execution process of the management node device executing the first transaction operation corresponding to the target pending transaction can be found in Figure 6 Detailed description of step S607 in the illustrated embodiment.

[0053] In one implementation, if the target pending transaction fails to pass the audit, the management node device may send a transaction audit failure notification to the user device and delete the target pending transaction from the transaction list.

[0054] In an embodiment of the present application, after the management node device obtains the target pending transaction, it can review the target pending transaction based on the review information included in the target pending transaction. If the target pending transaction is reviewed and approved, the management node device can respond to the transaction request included in the target pending transaction and execute the first transaction operation corresponding to the target pending transaction. The management node device is a blockchain node device in the blockchain network. The review process of the target pending transaction by the management node device is witnessed by each blockchain node device in the blockchain network. The review process of the target pending transaction by the management node device is open and transparent. Therefore, the first transaction operation corresponding to the target pending transaction executed by the management node device in response to the transaction request has high reliability.

[0055] based on Figure 1 For a schematic diagram of the transaction audit system architecture, see Figure 4 , Figure 4 4 is a flow chart of another transaction audit method provided by an embodiment of the present application. The transaction audit method can be jointly executed by the management node device and the user device in the above-mentioned transaction audit system. The transaction audit method may include the following steps S401 to S404:

[0056] Step S401: The management node device receives a target transaction to be processed sent by a user equipment.

[0057] In one implementation, a management node device receives a target pending transaction sent by a user device. The target pending transaction may include a transaction request and registration information. The transaction request may be used to request review of the registration information and to request acquisition of an electronic receipt. The registration information may be used to verify the identity of the user device. The registration information may include first identification information of the user device and a user identifier of the user device. The user identifier may uniquely identify the user device.

[0058] Step S402: The management node device verifies the validity of the registration information.

[0059] In one implementation, the verification process of the management node device for verifying the legitimacy of the registration information may be: the management node device may obtain second identification information from an associated information system based on the user identification; the management node device may compare the first identification information with the second identification information; if the first identification information is the same as the second identification information, the management node device may determine that the legitimacy verification of the registration information has passed.

[0060] The information systems associated with the management node device may include but are not limited to industrial and commercial systems, security department systems, and credit reporting systems.

[0061] Step S403: If the validity check of the registration information passes, the management node device determines that the target pending transaction has passed the review.

[0062] Step S404: If the target pending transaction is approved, the management node device responds to the transaction request to execute the first transaction operation corresponding to the target pending transaction.

[0063] In one implementation, if the legitimacy of the registration information is verified, the management node device can determine that the target pending transaction is reviewed and approved. If the target pending transaction is reviewed and approved, the management node device can generate an electronic receipt corresponding to the first identification information based on the first identification information, and send the electronic receipt to the user device.

[0064] For example, in the tax bureau's electronic invoice review scenario, an enterprise sends a target pending transaction to the tax bureau's general business department. This transaction includes a transaction request and the enterprise's registration information. The transaction request requests the tax bureau to review the registration information and issue an electronic invoice based on it. The registration information includes the enterprise code and primary identification information. The enterprise code uniquely identifies the enterprise. The primary identification information may include, but is not limited to, the enterprise's invoice stamp, taxpayer identification number, and registration number. After receiving the target pending transaction, the general business department verifies the legitimacy of the enterprise's registration information.

[0065] The process of the comprehensive business post verifying the legality of the enterprise's registration information is as follows: the comprehensive business post can obtain the invoice stamp corresponding to the enterprise code from the security department system based on the enterprise code, and obtain the taxpayer identification number and registration serial number corresponding to the enterprise code from the industrial and commercial system; the management node device compares the invoice stamp in the received target pending transaction with the invoice stamp obtained from the security department system, compares the taxpayer identification number in the received target pending transaction with the taxpayer identification number obtained from the industrial and commercial system, and compares the registration serial number in the received target pending transaction with the registration serial number obtained from the industrial and commercial system; if the invoice stamp received is the same as the invoice stamp obtained from the security department system, and the taxpayer identification number received is the same as the taxpayer identification number obtained from the industrial and commercial system, and the registration serial number received is the same as the registration serial number obtained from the industrial and commercial system, the management node device determines that the legality verification of the registration information has passed.

[0066] If the legality of the registration information is verified, the comprehensive management post can generate an electronic invoice for the enterprise based on the first identification information such as the enterprise's special invoice stamp, the enterprise's taxpayer identification number, and the enterprise's registration serial number, and send the electronic invoice to the enterprise.

[0067] In an embodiment of the present application, after the management node device obtains the target pending transaction sent by the user device, it can review the target pending transaction based on the registration information included in the target pending transaction; if the legitimacy check of the registration information passes, the management node device determines that the target pending transaction has passed the review, and the management node device can respond to the transaction request included in the target pending transaction, generate an electronic receipt corresponding to the first identification information included in the registration information, and send the electronic receipt to the user device. The management node device is a blockchain node device in the blockchain network. The management node device's process of verifying the legitimacy of the registration information is witnessed by each blockchain node device in the blockchain network. The management node device's process of verifying the legitimacy of the registration information is open and transparent. As a result, the electronic receipt generated by the management node device has high reliability.

[0068] based on Figure 1 For a schematic diagram of the transaction audit system architecture, see Figure 5 , Figure 5 : This is a flowchart of another transaction audit method provided by an embodiment of the present application. The transaction audit method can be jointly performed by the management node device, the first audit node device, and the user device in the above-mentioned transaction audit system. The transaction audit method may include the following steps S501 to S507:

[0069] Step S501: The management node device receives a target transaction to be processed sent by a user equipment.

[0070] In one implementation, a management node device receives a target pending transaction sent by a user device. The target pending transaction may include a transaction request and an early warning policy change notification. The transaction request may be used to request a change to an original early warning policy, and the early warning policy change notification may be used to review the changed early warning policy. The original early warning policy may include multiple early warning sub-policies.

[0071] Step S502: The management node device changes the original warning policy of the user device according to the warning policy change notification to obtain a changed warning policy.

[0072] The management node device can modify the original warning policy of the user device according to the warning policy change notification to obtain the modified warning policy. The modification operation may include but is not limited to adding, editing, and deleting operations.

[0073] For example, the management node device can add one or more warning sub-strategies based on the original warning strategy to obtain a changed warning strategy; or, the management node device can edit any one or more warning sub-strategies in the original warning strategy to obtain a changed warning strategy; or, the management node device can delete one or more warning sub-strategies based on the original warning strategy to obtain a changed warning strategy.

[0074] Step S503: the management node device sends the changed early warning strategy to the first review node device.

[0075] The management node device may send the changed early warning policy to a first audit node device having an audit level higher than that of the management node device, so that the first audit node device verifies the changed early warning policy.

[0076] In one implementation, in order to facilitate the first audit node device to verify the identity of the management node device, the management node device can encrypt the changed early warning strategy according to the private key of the management node device to obtain a digital signature; the management node device sends the digital signature to the first audit node device; the first audit node device can use the public key of the management node device to decrypt the digital signature; if the decryption is successful, the first audit node device passes the identity authentication of the management node device, and the first audit node device obtains the changed early warning strategy.

[0077] Step S504: The first audit node device verifies the changed early warning strategy to obtain a verification result.

[0078] In one implementation, the first audit node device can verify the changed early warning policy and obtain a verification result. If the first audit node device verifies the changed early warning policy successfully, a verification result indicating verification passed is obtained; if the first audit node device fails the verification of the changed early warning policy, a verification result indicating verification failed is obtained. For example, the first audit node device can verify whether the changed early warning policy complies with national laws and regulations, or whether the first audit node device complies with national standards for establishing early warning policies, etc.

[0079] Step S505: The first audit node device sends the verification result to the management node device.

[0080] Step S506: If the verification result received from the first audit node device is that the verification is passed, the management node device determines that the target pending transaction is audited and passed.

[0081] Step S507: If the target pending transaction is approved, the management node device updates the original warning policy of the user device to the changed warning policy.

[0082] After the first audit node device obtains the verification result, it can send the verification result to the management node device; if the received verification result is verification passed, the management node device determines that the target pending transaction is audited and passed, and the management node device determines that the changed early warning strategy is effective. The management node device can update the original early warning strategy of the user device to the changed early warning strategy.

[0083] In an embodiment of the present application, after the management node device obtains the target pending transaction sent by the user device, it can change the original warning policy of the user device according to the warning policy change notification included in the target pending transaction to obtain the changed warning policy; the management node device sends the changed warning policy to the first audit node device, and the first audit node device verifies the changed warning policy; if the first audit node device verifies the changed warning policy, the management node device determines that the target pending transaction is approved, and the management node device can respond to the transaction request included in the target pending transaction and update the original warning policy of the user device to the changed warning policy. The management node device and the first audit node device are both blockchain node devices in the blockchain network. The process of the management node device changing the original warning policy and the process of the first audit node device verifying the changed warning policy are witnessed by each blockchain node device in the blockchain network. The process of the management node device changing the original warning policy is open and transparent, and the process of the first audit node device verifying the changed warning policy is open and transparent, so that the changed warning policy has higher reliability.

[0084] based on Figure 1 For a schematic diagram of the transaction audit system architecture, see Figure 6 , Figure 6 : This is a flowchart of another transaction audit solution provided by an embodiment of the present application. The transaction audit method can be jointly performed by the management node device, the second audit node device, and the user device in the above-mentioned transaction audit system. The transaction audit method may include the following steps S601 to S607:

[0085] Step S601: The management node device receives a target transaction to be processed sent by a user equipment.

[0086] In one implementation, the management node device receives a target transaction to be processed sent by the user equipment. The target transaction to be processed may include a transaction request and early warning policy execution information.

[0087] Step S602: The management node device responds to the early warning policy execution event of the user equipment indicated by the early warning policy execution information, and generates a second transaction operation to be executed on the user equipment.

[0088] In one implementation, the early warning policy execution event may be used to indicate the early warning policy execution status of the user equipment. The management node device may generate a second transaction operation to be executed on the user equipment according to the early warning policy execution status of the user equipment.

[0089] Taking the tax bureau's audit scenario as an example, if the enterprise fails to declare and pay taxes within the prescribed time limit and the enterprise is in a state where invoicing is allowed, the second transaction operation to be executed for the enterprise generated by the comprehensive business post can be to suspend invoicing, and the enterprise will not be able to continue to issue electronic invoices; if the enterprise makes a supplementary declaration and handles tax registration within the time limit specified by the tax bureau and the enterprise is in a state where invoicing is suspended, the second transaction operation to be executed for the enterprise generated by the comprehensive business post can be to resume invoicing, and the enterprise can continue to issue electronic invoices.

[0090] Step S603: The management node device sends the second transaction operation to the second review node device.

[0091] The management node device may send the second transaction operation to a second audit node device having an audit level higher than that of the management node device, so that the second audit node device verifies the second transaction operation.

[0092] In one implementation, in order to facilitate the second audit node device to verify the identity of the management node device, the management node device can encrypt the second transaction operation according to the private key of the management node device to obtain a digital signature; the management node device sends the digital signature to the second audit node device; the second audit node device can use the public key of the management node device to decrypt the digital signature; if the decryption is successful, the second audit node device passes the identity authentication of the management node device, and the second audit node device obtains the second transaction operation.

[0093] In one implementation, to reduce the audit load on the second audit node device and ensure the accuracy of the second transaction operation generated by the management node device and to be executed on the user device, before the management node device sends the second transaction operation to the second audit node device, the management node device 101 may first send the second transaction operation to a first audit node device with a lower audit level than the second audit node device. The first audit node device will perform a preliminary verification on the second transaction operation to obtain a verification result. The first audit node device will send the verification result to the management node device. If the verification result is passed, the management node device 101 will then send the second transaction operation to the second audit node device, which will then perform a further verification on the second transaction operation.

[0094] Step S604: The second audit node device verifies the second transaction operation and obtains a verification result.

[0095] In one implementation, the second audit node device may verify the second transaction operation and obtain a verification result. If the second audit node device verifies the second transaction operation successfully, a verification result indicating verification passed is obtained; if the second audit node device verifies the second transaction operation unsuccessfully, a verification result indicating verification failed is obtained.

[0096] Step S605: The second audit node device sends the verification result to the management node device.

[0097] Step S606: If the verification result received from the second audit node device is that the verification is passed, the management node device determines that the target pending transaction is audited and passed.

[0098] Step S607: If the target pending transaction is approved, the management node device performs a second transaction operation on the user device.

[0099] After the second audit node device obtains the verification result, it can send the verification result to the management node device; if the received verification result is verification passed, the management node device determines that the target pending transaction is audited and passes, and the management node device performs the second transaction operation on the user device.

[0100] In an embodiment of the present application, after the management node device obtains the target pending transaction sent by the user device, it can generate a second transaction operation to be executed on the user device based on the early warning strategy execution information included in the target pending transaction; the management node device sends the second transaction operation to the second audit node device, and the second audit node device verifies the second transaction operation; if the second audit node device passes the second transaction operation, the management node device determines that the target pending transaction has been audited, and the management node device can execute the second transaction operation on the user device. The management node device and the second audit node device are both blockchain node devices in the blockchain network. The process of the management node device generating the second transaction operation and the process of the second audit node device verifying the second transaction operation are witnessed by each blockchain node device in the blockchain network. The process of the management node device generating the second transaction operation is open and transparent, and the process of the second audit node device verifying the second transaction operation is open and transparent, which makes the second transaction operation highly reliable.

[0101] See Figure 7 , Figure 7 This is a structural diagram of a transaction audit device provided by an embodiment of the present application. The transaction audit device 70 can be a computer program (including program code) running in the transaction audit device, for example, it can be an application software in the transaction audit device. The transaction audit device 70 can be used to execute Figures 3 to 6In the steps performed by the management node device in the method embodiment shown, the transaction audit device 70 includes an acquisition unit 701, an audit unit 702, and an execution unit 703, wherein:

[0102] An acquisition unit 701 is configured to acquire a target pending transaction. The target pending transaction is sent by a user device to a management node device. The target pending transaction includes a transaction request and review information. The review information includes registration information of the user device, a warning policy change notification, or warning policy execution information. The registration information is used to verify the identity of the user device. The warning policy change notification is used to review the changed warning policy. The warning policy execution information is used to review the warning policy execution event of the user device.

[0103] An audit unit 702 is configured to audit the target pending transaction based on the audit information;

[0104] If the target pending transaction is approved, the execution unit 703 is configured to respond to the transaction request to execute the first transaction operation corresponding to the target pending transaction.

[0105] In one implementation, when auditing the target pending transaction based on the audit information, the audit unit 702 is specifically configured to:

[0106] Verify the legitimacy of registration information;

[0107] If the legitimacy of the registration information is verified, the target pending transaction is confirmed to be approved.

[0108] In one implementation, the registration information includes the first identification information of the user device and the user identification of the user device; when verifying the legitimacy of the registration information, the review unit 702 is specifically configured to:

[0109] Acquire second identification information from the associated information system according to the user identification;

[0110] comparing the first identification information with the second identification information;

[0111] If the first identification information is identical to the second identification information, it is determined that the legitimacy check of the registration information has passed.

[0112] In one implementation, when responding to a transaction request to execute the first transaction operation corresponding to the target pending transaction, the execution unit 703 is specifically configured to:

[0113] generating an electronic receipt corresponding to the first identification information according to the first identification information;

[0114] Send the electronic receipt to the user's device.

[0115] In one implementation, when auditing the target pending transaction based on the audit information, the audit unit 702 is specifically configured to:

[0116] According to the warning policy change notification, the original warning policy of the user device is changed to obtain the changed warning policy;

[0117] Sending the changed early warning strategy to a first audit node device, so that the first audit node device verifies the changed early warning strategy and obtains a verification result. The audit level of the first audit node device is higher than the audit level of the management node device. The first audit node device is at least one blockchain node device in the blockchain network.

[0118] If the verification result received from the first audit node device is that the verification is passed, it is determined that the target pending transaction is audited and passed;

[0119] When responding to the transaction request to execute the first transaction operation corresponding to the target pending transaction, the execution unit 703 is specifically configured to:

[0120] Update the original warning policy of the user device to the changed warning policy.

[0121] In one implementation, when auditing the target pending transaction based on the audit information, the audit unit 702 is specifically configured to:

[0122] In response to an early warning policy execution event of the user device indicated by the early warning policy execution information, generating a second transaction operation to be executed on the user device;

[0123] Sending the second transaction operation to a second audit node device, so that the second audit node device verifies the second transaction operation and obtains a verification result. The audit level of the second audit node device is higher than the audit level of the management node device. The second audit node device is at least one blockchain node device in the blockchain network.

[0124] If the verification result received from the second audit node device is that the verification is passed, it is determined that the target pending transaction is audited and passed;

[0125] When responding to the transaction request to execute the first transaction operation corresponding to the target pending transaction, the execution unit 703 is specifically configured to:

[0126] A second transaction operation is performed on the user equipment.

[0127] In one implementation, before sending the second transaction operation to the second audit node device, the audit unit 702 is further configured to:

[0128] Sending the second transaction operation to a first audit node device, so that the first audit node device verifies the second transaction operation and obtains a verification result, wherein the audit level of the second audit node device is higher than the audit level of the first audit node device, and the first audit node device is at least one blockchain node device in the blockchain network;

[0129] If the verification result received from the first audit node device is that the verification is passed, the step of sending the second transaction operation to the second audit node device is triggered.

[0130] In one implementation, when the audit unit 702 sends the second transaction operation to the second audit node device, it is specifically configured to:

[0131] Encrypt the second transaction operation using the private key of the management node device to obtain a digital signature;

[0132] The digital signature is sent to the second audit node device, so that the second audit node device decrypts the digital signature using the public key of the management node device to obtain a second transaction operation.

[0133] It should be noted that Figure 7 The details not mentioned in the corresponding embodiments and the specific implementation methods of the steps performed by each unit can be found in Figures 3 to 6 The illustrated embodiments and the aforementioned contents will not be described in detail here.

[0134] See Figure 8 , Figure 8 This is a structural diagram of a transaction audit device provided in an embodiment of the present application. The transaction audit device 80 includes a processor 801, a memory 802 and a communication interface 803. The processor 801, the memory 802 and the communication interface 803 are connected via one or more communication buses.

[0135] The processor 801 is configured to support the transaction audit node 80 to execute Figures 3 to 6 The method embodiment manages the corresponding functions of the node device. The processor 801 can be a central processing unit (CPU), a network processor (NP), a hardware chip or any combination thereof.

[0136] The memory 802 is used to store program code, etc. The memory 802 may include volatile memory, such as random access memory (RAM); non-volatile memory (NVM), such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); or a combination of the aforementioned types of memory.

[0137] The communication interface 803 is used to receive and send data, for example, the communication interface 803 is used to receive the target pending transaction sent by the user device, the communication interface 803 is used to receive the verification result sent by the first audit node device, the communication interface 803 is used to receive the verification result sent by the second audit node device, the communication interface 803 is used to send the electronic receipt to the user device, the communication interface 803 is used to send the changed early warning policy to the first audit node device, the communication interface 803 is used to send the second transaction operation to the first audit node device, or the communication interface 803 is used to send the second transaction operation to the second audit node device.

[0138] In an embodiment of the present application, the transaction audit device 80 includes multiple communication interfaces, wherein the communication interface for sending data and the communication interface for receiving data may not be the same communication interface.

[0139] The processor 801 may call the program code stored in the memory 802 to perform the following operations:

[0140] Obtain the target pending transaction, which is sent by the user device to the management node device. The target pending transaction includes a transaction request and review information. The review information includes the user device's registration information, warning policy change notification, or warning policy execution information. The registration information is used to verify the identity of the user device, the warning policy change notification is used to review the changed warning policy, and the warning policy execution information is used to review the warning policy execution event of the user device;

[0141] Review the target pending transactions based on the audit information;

[0142] If the target pending transaction is approved, the transaction request is responded to to execute the first transaction operation corresponding to the target pending transaction.

[0143] Furthermore, the processor 801 can also cooperate with the memory 802 and the communication interface 803 to execute Figures 3 to 6 For details on the operations corresponding to the management node device in the illustrated method embodiment, please refer to the description in the method embodiment, which will not be repeated here.

[0144] The present application also provides a computer-readable storage medium that can be used to store Figure 8 The computer program instructions called by the processor 801 in the transaction audit device 80 of the illustrated embodiment include instructions for executing the program designed for the management node device in the above embodiment.

[0145] The computer-readable storage medium includes, but is not limited to, a flash memory (Flash Memory), a hard disk drive (HDD), and a solid-state drive (SSD).

[0146] The present application also provides a computer program product. When the computer program product is run by a computer device, the computer program product can execute the above Figures 3 to 6 The embodiment provides a transaction audit method designed for a management node device.

[0147] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, computer software, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0148] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL), etc.) or wireless (e.g., infrared, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD) or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

[0149] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A transaction audit method, characterized in that: The method is performed by a management node device in a blockchain network, the blockchain network including multiple blockchain node devices, the management node device, the first audit node device, and the second audit node device being at least one blockchain node device in the blockchain network, and the method includes: Obtaining a target pending transaction, where the target pending transaction is sent by a user device to the management node device, the target pending transaction includes a transaction request and audit information, the audit information including registration information of the user device, a warning policy change notification, or warning policy execution information. The registration information is used to verify the identity of the user device, the warning policy change notification is used to audit the changed warning policy, and the warning policy execution information is used to audit the warning policy execution event of the user device; Auditing the target pending transaction based on the audit information; different audit information results in different audit methods for the management node device to audit the target pending transaction; if the audit information includes the registration information of the user device, the registration information is directly audited; if the audit information includes the early warning policy change notification or the early warning policy execution information, requesting the first audit node device or the second audit node device to assist in auditing the target pending transaction, the second audit node device having a higher audit level than the first audit node device, and the first audit node device having a higher audit level than the management node device; If the target pending transaction is approved, the transaction request is responded to to execute the first transaction operation corresponding to the target pending transaction.

2. The method according to claim 1, characterized in that The step of reviewing the target pending transaction according to the review information includes: Verify the legitimacy of the registration information; If the validity check of the registration information is passed, it is determined that the target pending transaction is approved.

3. The method according to claim 2, characterized in that The registration information includes the first identification information of the user equipment and the user identification of the user equipment; The verification of the legitimacy of the registration information includes: According to the user identifier, obtaining second identification information from an associated information system; comparing the first identification information with the second identification information; If the first identification information is the same as the second identification information, it is determined that the legitimacy check of the registration information has passed.

4. The method according to claim 3, characterized in that The responding to the transaction request to execute the first transaction operation corresponding to the target pending transaction includes: generating an electronic receipt corresponding to the first identification information according to the first identification information; The electronic ticket is sent to the user device.

5. The method according to claim 1, characterized in that The step of reviewing the target pending transaction according to the review information includes: According to the warning policy change notification, the original warning policy of the user equipment is changed to obtain the changed warning policy; Sending the changed early warning strategy to the first audit node device, so that the first audit node device verifies the changed early warning strategy and obtains a verification result; If the verification result received from the first audit node device is a passed verification, determining that the target pending transaction is passed; The responding to the transaction request to execute the first transaction operation corresponding to the target pending transaction includes: The original warning policy of the user equipment is updated to the changed warning policy.

6. The method according to claim 1, characterized in that The step of reviewing the target pending transaction according to the review information includes: In response to the early warning policy execution event of the user equipment indicated by the early warning policy execution information, generating a second transaction operation to be executed on the user equipment; sending the second transaction operation to a second audit node device, so that the second audit node device verifies the second transaction operation and obtains a verification result; If the verification result received from the second audit node device is a passed verification, determining that the target pending transaction is audited and passed; The responding to the transaction request to execute the first transaction operation corresponding to the target pending transaction includes: The second transaction operation is performed on the user equipment.

7. The method according to claim 6, characterized in that Before sending the second transaction operation to the second audit node device, the method further includes: sending the second transaction operation to the first audit node device, so that the first audit node device verifies the second transaction operation and obtains a verification result; If the verification result received from the first audit node device is that the verification is passed, the step of sending the second transaction operation to the second audit node device is triggered.

8. The method according to claim 6, characterized in that The sending the second transaction operation to the second audit node device includes: Encrypt the second transaction operation using the private key of the management node device to obtain a digital signature; The digital signature is sent to the second audit node device, so that the second audit node device decrypts the digital signature using the public key of the management node device to obtain the second transaction operation.

9. A transaction audit device, characterized in that: The transaction audit device is applied to a management node device in a blockchain network, wherein the blockchain network includes multiple blockchain node devices, and the management node device, the first audit node device, and the second audit node device are at least one blockchain node device in the blockchain network. The transaction audit device includes: an acquiring unit, configured to acquire a target pending transaction, the target pending transaction being sent by a user device to the management node device, the target pending transaction including a transaction request and audit information, the audit information including registration information of the user device, a warning policy change notification, or warning policy execution information, the registration information being used to verify the identity of the user device, the warning policy change notification being used to audit the changed warning policy, and the warning policy execution information being used to audit the warning policy execution event of the user device; an audit unit configured to audit the target pending transaction based on the audit information; the management node device auditing the target pending transaction in a different audit manner depending on the audit information; if the audit information includes registration information of the user device, the registration information is directly audited; if the audit information includes the early warning policy change notification or the early warning policy execution information, the management node device is requested to assist in auditing the target pending transaction, the second audit node device having a higher audit level than the first audit node device, and the first audit node device having a higher audit level than the management node device; The execution unit is configured to respond to the transaction request to execute a first transaction operation corresponding to the target pending transaction if the target pending transaction is approved.

10. A transaction audit device, characterized in that: The transaction audit device includes: Memory for storing computer programs; A processor is configured to call the computer program stored in the memory to execute the transaction audit method according to any one of claims 1 to 8.

Images