CN110599322A

CN110599322A - Data auditing method and device based on block chain network

Info

Publication number: CN110599322A
Application number: CN201910906437.4A
Authority: CN
Inventors: 张懿方; 戴传兵; 郭鹏; 洪晓雯
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-09-24
Filing date: 2019-09-24
Publication date: 2019-12-20
Anticipated expiration: 2039-09-24
Also published as: CN110599322B

Abstract

The application discloses a data auditing method and device based on a block chain network, wherein the method comprises the following steps: the management node acquires uplink requests corresponding to a plurality of pieces of to-be-uplink data associated with an audit object, generates a plurality of target blocks according to the uplink requests corresponding to the plurality of pieces of to-be-uplink data, and adds the plurality of target blocks to a service full-scale chain; the data to be uplink comprises service flow data; when inquiry information aiming at the service processing permission of the audit object sent by the request terminal is received, the incidence relation between the service process data in the target blocks associated with the audit object is audited through the service full-scale chain, feedback information aiming at the service processing permission of the audit object is generated according to the audit result, and the feedback information is sent to the request terminal. By the method and the device, auditing efficiency for the business process data is improved.

Description

Data auditing method and device based on block chain network

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data auditing method and apparatus based on a block chain network.

Background

With the continuous development of computer networks, each process link of the existing export tax refund can also be realized through the network. However, since the handling of an export tax refund business requires data verification among multiple parties, such as verification of enterprise-related data for applying for handling export tax refunds, verification of local tax bureau-related data where the enterprise is located, and verification of export tax bureau-related data, a higher requirement is also placed on how to handle export tax refund business quickly.

In the prior art, related voucher data, related logistics data and related production data are sent to a local tax bureau by an enterprise, the local tax bureau verifies all the received data sent by the enterprise, the logistics trader and the manufacturer, and then a related letter is generated, and the letter can prove that the enterprise has export tax refund conditions. The local tax bureau gives the generated mail to the export tax return bureau, and the export tax return bureau determines whether to handle the export tax return service for the enterprise according to the validity of the mail. Because data among multiple parties involved in handling an export tax refund rate service (including enterprises, local tax offices and export tax refunds) are isolated in order to ensure security among the parties, the handling of relevant export tax refund services can be realized through the complicated processing flow, which results in complicated service handling process and low handling efficiency.

Content of application

The application provides a data auditing method and device based on a block chain network, which can improve auditing efficiency aiming at business process data.

One aspect of the present application provides a data auditing method based on a block chain network, including:

the management node acquires uplink requests corresponding to a plurality of pieces of to-be-uplink data associated with an audit object, generates a plurality of target blocks according to the uplink requests corresponding to the plurality of pieces of to-be-uplink data, and adds the plurality of target blocks to a service full-scale chain; the uplink request carries the data to be uplink; the data to be uplink comprises service flow data; the business total chain is used for storing blocks corresponding to all business process data; the blocks corresponding to all the business process data comprise the plurality of target blocks;

when inquiry information aiming at the service processing permission of the audit object and sent by a request terminal is received, acquiring the target blocks associated with the audit object from the service full-scale chain according to the inquiry information, and acquiring association relations among the service process data respectively included in the target blocks;

auditing the incidence relation among the plurality of business process data, generating feedback information aiming at the business processing permission of the audited object according to the auditing result, and sending the feedback information to the request terminal; the feedback information comprises confirmation information that the auditing object has the service processing authority or prompt information that the auditing object does not have the service processing authority.

Wherein the obtaining the target blocks associated with the audit object from the business full-scale chain according to the query information comprises:

acquiring a logistics object and a production object which are associated with the audit object;

acquiring a target block corresponding to the auditing object, a target block corresponding to the logistics object and a target block corresponding to the production object in the business full-scale chain;

and determining the transaction voucher data in the target block corresponding to the auditing object, the logistics data in the target block corresponding to the logistics object and the production data in the target block corresponding to the production object as the business process data.

The auditing the association relation among the plurality of business process data and generating feedback information of the business processing permission aiming at the audited object according to the auditing result comprises the following steps:

when the transaction acceptance object contained in the transaction voucher data is detected to be the production object, determining that the auditing object and the production object have a transaction association relationship, and detecting an article receiving object and an article sending object contained in the logistics data;

when the article receiving object is detected to be the auditing object and the article sending object is detected to be the production object, determining that the logistics object, the production object and the auditing object have an object matching incidence relation, and comparing a transmission article attribute contained in the logistics data, a production article attribute contained in the production data and a transaction article attribute contained in the transaction voucher data;

and when the transmission article attribute, the production article attribute and the transaction article attribute are compared to be the same, determining that the logistics object, the production object and the transaction initiating object have an article matching association relationship, and generating the confirmation information.

detecting the transaction time of the transaction voucher data, the logistics time of the logistics data and the production time of the production data;

and when the transaction time, the logistics time and the generation time meet the time association relationship on a time axis, generating the confirmation information.

The management node holds a key pair of a data submitting node to which each piece of data to be uplink belongs; the key pair comprises a private key and a key of the data submission node; generating a plurality of target blocks according to the uplink requests respectively corresponding to the plurality of data to be uplink transmitted comprises:

based on a private key of a data submitting node to which each piece of data to be uplink belongs, decrypting the data to be uplink carried by each uplink request respectively to obtain a signature and business process data in each piece of data to be uplink;

decrypting the signature based on the public key to obtain a first hash value in the signature;

performing hash operation on the business process data based on a hash algorithm to obtain a second hash value corresponding to the business process data;

and when the first hash value and the second hash value are detected to be the same, verifying the signature, and generating the target blocks according to the data to be uplink.

Wherein, the generating a plurality of target blocks according to the plurality of data to be uplink and adding the plurality of target blocks to a service full-scale chain comprises:

encrypting the included business process data respectively based on a public key corresponding to a data submission node to which each piece of data to be uplink belongs to obtain encrypted data corresponding to each piece of business process data respectively;

and generating a target block corresponding to each business process data according to the encrypted data corresponding to each business process data, and adding the target block corresponding to each business process data to the business full-scale chain.

Wherein the adding the plurality of target blocks to a traffic volume chain comprises:

respectively generating an index value corresponding to each target block in the plurality of target blocks based on a block height increasing mechanism, and storing a mapping relation between each index value and the corresponding data submission node into an index mapping table;

adding the each target chunk with the index value to the traffic volume chain.

One aspect of the present application provides a data auditing device based on a block chain network, which is applied to a management node, and includes:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring uplink requests corresponding to a plurality of to-be-uplink data associated with an audit object, respectively checking and signing the to-be-uplink data based on a key pair of a data submitting node to which the to-be-uplink data belongs, if the to-be-uplink data passes the checking and signing, generating a plurality of target blocks according to the to-be-uplink data, and adding the target blocks to a service full-scale chain; the uplink request carries the data to be uplink; the data to be uplink comprises service flow data; the business total chain is used for storing blocks corresponding to all business process data; the blocks corresponding to all the business process data comprise the plurality of target blocks;

a second obtaining module, configured to, when query information for a service processing permission of the audit object sent by a request terminal is received, obtain, according to the query information, the multiple target blocks associated with the audit object from the full service chain, and obtain association relationships between the service process data included in the multiple target blocks, respectively;

the auditing module is used for auditing the incidence relation among the plurality of business process data, generating feedback information of the business processing permission aiming at the audited object according to the auditing result, and sending the feedback information to the request terminal; the feedback information comprises confirmation information that the auditing object has the service processing authority or prompt information that the auditing object does not have the service processing authority.

Wherein the second obtaining module includes:

a first acquisition unit, configured to acquire a logistics object and a production object associated with the audit object;

a block acquiring unit, configured to acquire a target block corresponding to the audit object, a target block corresponding to the logistics object, and a target block corresponding to the production object in the business full-scale chain;

and the determining unit is used for determining the transaction voucher data in the target block corresponding to the auditing object, the logistics data in the target block corresponding to the logistics object and the production data in the target block corresponding to the production object as the business process data.

Wherein, the audit module comprises:

a first detection unit configured to determine that the audit object and the production object have a transaction association relationship when it is detected that the transaction acceptance object included in the transaction voucher data is the production object, and detect an article reception object and an article issuance object included in the logistics data;

a second detecting unit, configured to determine that the logistics object, the production object, and the audit object have an object matching association relationship when it is detected that the article receiving object is the audit object and the article sending object is the production object, and compare a transmission article attribute included in the logistics data, a production article attribute included in the production data, and a transaction article attribute included in the transaction credential data;

and the first generating unit is used for determining that the logistics object, the production object and the transaction initiating object have an object matching association relation when the transmission object attribute, the production object attribute and the transaction object attribute are compared to be the same, and generating the confirmation information.

Wherein, the audit module comprises:

the third detection unit is used for detecting the transaction time of the transaction voucher data, the logistics time of the logistics data and the production time of the production data;

and the second generating unit is used for generating the confirmation information when the transaction time, the logistics time and the generating time meet the time association relation on a time axis.

The management node holds a key pair of a data submitting node to which each piece of data to be uplink belongs; the key pair comprises a private key and a key of the data submission node; the first obtaining module includes:

a first decryption unit, configured to decrypt, based on a private key of a data submitting node to which each piece of to-be-uplink data belongs, the to-be-uplink data carried by each uplink request respectively to obtain a signature and service flow data in each piece of to-be-uplink data;

the second decryption unit is used for decrypting the corresponding signatures respectively based on the public key of the data submission node to which each piece of data to be uplink belongs to obtain a first hash value in each signature;

the operation unit is used for respectively carrying out Hash operation on each business process data based on a Hash algorithm to obtain a second Hash value corresponding to each business process data;

and the fourth detection unit is used for generating the plurality of target blocks according to the plurality of data to be uplink after the verification passes when each first hash value is detected to be the same as the corresponding second hash value.

Wherein, the first obtaining module comprises:

the encryption unit is used for encrypting the included business process data respectively based on a public key corresponding to a data submission node to which each piece of data to be linked belongs to obtain encrypted data corresponding to each piece of business process data respectively;

and the first adding unit is used for generating a target block corresponding to each business process data according to the encrypted data corresponding to each business process data, and adding the target block corresponding to each business process data to the business full-scale chain.

Wherein, the first obtaining module comprises:

a mapping unit, configured to generate an index value corresponding to each of the multiple target blocks based on a block height increment mechanism, and store a mapping relationship between each index value and a corresponding data commit node in an index mapping table;

a second adding unit, configured to add the each target block with the index value to the full traffic chain.

An aspect of the application provides a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the method of the above aspect.

An aspect of the application provides a computer-readable storage medium having stored thereon a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the method of the above-mentioned aspect.

The method comprises the steps that a management node acquires uplink requests corresponding to a plurality of pieces of to-be-uplink data associated with an audit object respectively, a plurality of target blocks are generated according to the uplink requests corresponding to the plurality of pieces of to-be-uplink data respectively, and the target blocks are added to a business full-scale chain; the uplink request carries the data to be uplink; the data to be uplink comprises service flow data; when inquiry information aiming at the service processing permission of the audit object and sent by a request terminal is received, acquiring the target blocks associated with the audit object from the service full-scale chain according to the inquiry information, and acquiring association relations among the service process data respectively included in the target blocks; and auditing the incidence relation among the plurality of business process data, generating feedback information aiming at the business processing permission of the audited object according to the auditing result, and sending the feedback information to the request terminal. Therefore, the method provided by the application can obtain the business process data submitted by the data submitting nodes through the management node, and audit the obtained and correlated business process data to determine the business processing permission of the audit object corresponding to the business process data, so that the audit efficiency of the business process data is improved, and the determination efficiency of the business processing permission of the audit object is improved.

Drawings

In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of a data review scenario provided herein;

fig. 2 is a schematic flowchart of a data auditing method based on a blockchain network according to the present application;

fig. 3 is a schematic view of a scene of an acquisition block provided in the present application;

FIG. 4 is a block diagram of the present application;

fig. 5 is a schematic structural diagram of a data auditing device based on a blockchain network provided by the present application;

fig. 6 is a schematic structural diagram of a computer device provided in the present application.

Detailed Description

The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings in the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer. The Block chain comprises a series of blocks (blocks) which are mutually connected according to the generated chronological order, once a new Block is added into the Block chain, the new Block cannot be removed, and the recorded data submitted by the nodes in the Block chain system are recorded in the blocks.

Please refer to fig. 1, which is a schematic view of a data review scenario provided in the present application. As shown in fig. 1, the data submitting nodes 100a, 101a, and 102a are all 3 nodes associated with the audit object, where the number of the data submitting nodes associated with the audit object is determined according to an actual application scenario, and is not limited herein. The data submission node associated with the audit object may be understood as: when the auditing object needs to handle a certain service, the auditing object needs to handle related service data provided by the associated data submitting node. The data submitting node 100a, the data submitting node 101a, and the data submitting node 102a all send uplink requests to the management node 106a, where each uplink request carries corresponding data to be uplink, and the data to be uplink includes service flow data and a signature of the service flow data. Wherein, the uplink request sent by the data submitting node 100a to the management node 106a is an uplink request 1, the to-be-uplink data carried in the uplink request 1 includes service process data 1 and a signature 1, and the signature 1 is a signature of the service process data 1; the uplink request sent by the data submitting node 101a to the management node 106a is an uplink request 2, the data to be uplink carried in the uplink request 2 includes service flow data 2 and a signature 2, and the signature 2 is a signature of the service flow data 2; the uplink request sent by the data submitting node 102a to the management node 106a is an uplink request 3, where the to-be-uplink data carried in the uplink request 3 includes a service flow data 3 and a signature 3, and the signature 3 is a signature of the service flow data 3. The specific process of obtaining the signature of the business process data is as follows: and carrying out Hash operation on the business process data to obtain a Hash value of the business process data, and encrypting the Hash value through a private key of a data submission node to which the business process data belongs to obtain a signature of the business process data.

The data to be uplink carried in the uplink request sent by each data submitting node is encrypted by the public key of the corresponding data submitting node, and the management node 106a can check and sign the data to be uplink carried in the uplink request sent by each data submitting node by the key pair (including the public key and the private key) of each data submitting node. The label checking process specifically comprises the following steps: the management node 106a may perform the signature verification on the to-be-uplink data carried in the uplink request 1 through the key of the data submitting node 100 a: the management node 106a may decrypt the to-be-uplink data carried in the uplink request 1 by using the private key of the data submitting node 100a, so as to obtain the service flow data 1 and the signature 1 in the to-be-uplink data. Then, the management node 106a may decrypt the signature 1 by using the public key of the data submitting node 100a to obtain a hash value corresponding to the business process data 1, and the hash value may be referred to as a first hash value corresponding to the business process data 1. The management node 106a may perform hash operation on the obtained business process data 1 to obtain another hash value corresponding to the business process data 1, and the hash value may be referred to as a second hash value corresponding to the business process data 1. When the management node 106a detects that the first hash value and the second hash value corresponding to the service flow data 1 are the same, it determines that the signature of the to-be-uplink data carried in the uplink request 1 passes, and may generate a corresponding target block according to the service flow data 1 in the to-be-uplink data, where the target block includes the service flow data 1. Similarly, the management node 106a may check the to-be-uplink data carried in the uplink request 2 by using the key of the data submitting node 101 a: the management node 106a may decrypt the to-be-uplink data carried in the uplink request 2 by using the private key of the data submitting node 101a, so as to obtain the service flow data 2 and the signature 2 in the to-be-uplink data. Then, the management node 106a may decrypt the signature 2 by using the public key of the data submitting node 101a to obtain a hash value corresponding to the business process data 2, and the hash value may be referred to as a first hash value corresponding to the business process data 2. The management node 106a may perform hash operation on the obtained business process data 2 to obtain another hash value corresponding to the business process data 2, and the hash value may be referred to as a second hash value corresponding to the business process data 2. When the management node 106a detects that the first hash value corresponding to the service flow data 2 is the same as the second hash value, it determines that the signature of the to-be-uplink data carried in the uplink request 2 passes, and may generate a corresponding target block according to the service flow data 2 in the to-be-uplink data, where the target block includes the service flow data 2. Similarly, the management node 106a may check the to-be-uplink data carried in the uplink request 3 by using the key of the data submitting node 102 a: the management node 106a may decrypt the to-be-uplink data carried in the uplink request 3 by using the private key of the data submitting node 102a, so as to obtain the service flow data 3 and the signature 3 in the to-be-uplink data. Then, the management node 106a may decrypt the signature 3 by using the public key of the data submitting node 102a to obtain a hash value corresponding to the business process data 3, and the hash value may be referred to as a first hash value corresponding to the business process data 3. The management node 106a may perform hash operation on the obtained business process data 3 to obtain another hash value corresponding to the business process data 3, and the hash value may be referred to as a second hash value corresponding to the business process data 3. When the management node 106a detects that the first hash value and the second hash value corresponding to the service flow data 3 are the same, it determines that the signature of the to-be-uplink data carried in the uplink request 3 passes, and may generate a corresponding target block according to the service flow data 3 in the to-be-uplink data, where the target block includes the service flow data 3.

The management node 106a may upload the generated target block corresponding to the business process data 1, the target block corresponding to the business process data 2, and the target block corresponding to the business process data 3 to the business full-scale chain 108a, where the business full-scale chain 108a is a block chain, and the business full-scale chain 108a includes blocks corresponding to the business process data of all the data submitting nodes, that is, the business full-scale chain 108a is formed by blocks (including all the target blocks) corresponding to all the business process data (i.e., the business process data corresponding to all the data submitting nodes, including the business process data corresponding to the data submitting node 100a, the data submitting node 101a, and the data submitting node 102 a), and the management node 106a may maintain and manage all the blocks in the business full-scale chain 108 a. When the management node 106a receives the query information for the service processing permission of the audit object sent by the request terminal 112a, the management node 106a may obtain, on the service full-volume chain 108a, a target block associated with the audit object, that is, a target block corresponding to a data commit node associated with the audit object, where the target block is a target block (may be referred to as block 1) corresponding to the service flow data 1 of the data commit node 100a, a target block (may be referred to as block 2) corresponding to the service flow data 2 of the data commit node 101a, and a target block (may be referred to as block 3) corresponding to the service flow data 3 of the data commit node 102a, as shown in fig. 1, that is, block 1, block 2, and block 3 in the block set 110 a. The block 1, the block 2, and the block 3 associated with the audit object have corresponding association relationships, and the management node 106a may audit the association relationships among the block 1, the block 2, and the block 3, and generate feedback information according to the audit result. The feedback information comprises confirmation information that the checking object has the business processing authority and prompt information that the checking object does not have the business processing authority, the prompt information is generated when the association relations among the block 1, the block 2 and the block 3 are checked to be not matched, and the confirmation information is generated when the association relations among the block 1, the block 2 and the block 3 are checked to be matched. The management node 106a may send the generated feedback information to the requesting terminal 112a, and the requesting terminal 112a may perform corresponding service transaction according to the received feedback information. For example, when the request terminal 112a receives the confirmation information, the service included in the service processing authority may be handled for the object to be checked, and when the request terminal 112a receives the prompt information, the requested service may not be handled for the object to be checked.

Please refer to fig. 2, which is a schematic flowchart of a data auditing method based on a blockchain network according to the present application, and as shown in fig. 2, the method may include:

step S101, a management node acquires uplink requests corresponding to a plurality of to-be-uplink data associated with an audit object, generates a plurality of target blocks according to the uplink requests corresponding to the plurality of to-be-uplink data, and adds the plurality of target blocks to a full-service chain;

specifically, the method provided by the application can be applied to export tax refund business, the auditing object can be an enterprise applying for handling export tax refund business, the multiple data submission nodes associated with the auditing object can be nodes corresponding to objects needing to submit auditing materials when the enterprise handles export tax refund, the multiple data submission nodes can include nodes corresponding to the auditing object (namely nodes corresponding to the enterprise), nodes corresponding to manufacturers purchasing articles of the auditing object and nodes corresponding to logistics merchants entrusting delivery of the manufacturers to deliver articles, wherein the management nodes, the nodes corresponding to the enterprise, the nodes corresponding to the manufacturers and the nodes corresponding to the logistics merchants are all block chain nodes in a block chain network. The management node, the node corresponding to the enterprise, the node corresponding to the manufacturer, and the node corresponding to the logistics provider may correspond to one or more servers, respectively. The multiple pieces of to-be-uplink data associated with the audit object may be to-be-uplink data sent by a node corresponding to the enterprise to the management node, to-be-uplink data sent by a node corresponding to the manufacturer to the management node, or/and to-be-uplink data sent by a node corresponding to the logistics provider to the management node.

Each data submitting node associated with the audit object may send a uplink request to the management node, where the uplink request carries corresponding to-be-uplink data, and the to-be-uplink data may include corresponding service flow data, that is, the uplink request is used for the data submitting node to request the management node to add the service flow data in the to-be-uplink data carried by the uplink request to a service full-size chain (i.e., request uplink) held by the management node. When each piece of business process data is added to the business full-scale chain, a target block corresponding to the business process data which is linked up exists in the business full-scale chain, and the management node can maintain (including the uplink block, the maintenance authority for acquiring the uplink block, checking the uplink block and the like) all target blocks corresponding to the business process data which is linked up by all data submitting nodes in the business full-scale chain. The business total volume chain includes blocks corresponding to all business process data, specifically, there may be a plurality of audit objects, each audit object may further be associated with a plurality of data submission nodes, and a block corresponding to the business process data of the data submission node associated with the audit object may be referred to as a target block. Therefore, all the business process data refer to the business process data corresponding to all the data submission nodes associated with all the audit objects. Namely, the business total chain includes the target blocks corresponding to the business process data of all the data submitting nodes associated with all the auditing objects. When the data submitting node is a node corresponding to an enterprise, the business process data included in the to-be-linked data can be a purchase certificate when the enterprise purchases an article from a manufacturer; when the data submitting node is a node corresponding to the manufacturer, the business process data included in the to-be-linked data can be photos or videos of production workshop assembly line operation activities when the manufacturer produces articles; when the data submission node is a node corresponding to a logistics provider, the business process data included in the to-be-linked data may be logistics information (positioning information, i.e., article transportation route information) of the logistics provider when the logistics provider transports an article, i.e., an article purchased by an enterprise at a manufacturer.

The management node is configured to encrypt data to be uplink carried by the uplink request received by the management node, hold the key pair of each data submitting node, and perform signature verification on each data to be uplink respectively through the key pair (including the public key and the private key of the data submitting node) of the data submitting node to which each data to be uplink belongs: the management node can decrypt the data to be uplink by using a private key of the data submitting node to obtain the service flow data and a signature in the data to be uplink, wherein the signature is a signature corresponding to the service flow data. The process of obtaining the signature of the business process data comprises the following steps: and carrying out hash operation on the business process data through a hash algorithm to obtain a hash value of the business process data, and further encrypting the hash value through a private key of a data submission node to which the business process data belongs to obtain a signature of the business process data. Then, the management node may further decrypt the decrypted signature using the public key of the data submission node to obtain a hash value of the business process data in the signature, and the hash value may be referred to as a first hash value. The management node may perform a hash operation on the service flow data obtained by decrypting the data to be uplink, to obtain a hash value, and the hash value may be referred to as a second hash value. If the management node detects that the first hash value and the second hash value obtained from the signature are the same, it is determined that the service flow data in the received to-be-uplink data is not tampered, a target block (including the service flow data in the target block) may be generated according to the service flow data, and the generated target block is added to the full-traffic chain. Through the same signature checking process, signature checking can be performed on the data to be uplink carried by each uplink request, after the signature checking is passed, each service flow data is used as the data to be uplink, target blocks corresponding to the service flow data included in each data to be uplink can be generated, and each generated target block is added into the service full-scale chain. And the blocks stored in the service full-scale chain are target blocks corresponding to the service process data of all the data submitting nodes.

Optionally, the management node may encrypt the service flow data that needs to be uplinked, and add the target block corresponding to the encrypted service flow data to the full-service chain. The management node may encrypt the included service process data based on a public key corresponding to a data submitting node to which each piece of data to be linked belongs, to obtain encrypted data corresponding to each piece of service process data, generate a target block corresponding to each piece of service process data according to the encrypted data corresponding to each piece of service process data, and add the target block corresponding to each piece of service process data to the service full-volume chain: after the check-signing of the data to be uplink is passed, the management node can encrypt the service flow data in the data to be uplink through the public key of the data submitting node corresponding to the data to be uplink, and through the method, the encrypted data corresponding to the service flow data in each data to be uplink can be obtained. The management node may use the encrypted data corresponding to each service flow data as data that needs to be uplinked, that is, generate a corresponding target block according to each encrypted data, and add the target block corresponding to each encrypted data to the full-service chain.

When the uplink is a target block corresponding to unencrypted service flow data, the management node may obtain a block corresponding to the service flow data from the full service chain, and directly extract corresponding service flow data from the obtained block. When the uplink is the target block corresponding to the encrypted service flow data (i.e., the encrypted data), the management node may obtain the block corresponding to the encrypted data from the full service chain, and may decrypt the obtained block using the private key of the data submitting node corresponding to the encrypted data, so as to obtain the corresponding service flow data in the block.

The management node can respectively generate an index value corresponding to each target block in the plurality of target blocks based on a block height increasing mechanism, and store the mapping relation between each index value and the corresponding data submission node into an index mapping table; adding the each target chunk with the index value to the traffic volume chain: the block height increasing mechanism is understood to be that each block in the full traffic chain (i.e. all target blocks of the uplink) is assigned a number, and the numbers are sequentially higher, and the numbers added to the blocks in the full traffic chain are larger later. For example, block 1 is added to the traffic volume chain at the first time, and block 1 is the first block added to the traffic volume chain, then block 1 may be assigned a number of 001. Block 2 is added to the traffic volume chain at a second time later than the first time, block 2 may be assigned a number of 002. Block 3 is added to the full traffic chain at a third time later than the second time, block 3 may be assigned a number 003, and recursion may be performed in sequence. The number allocated to each block may also be referred to as an index value of each block, and the management node may store a mapping relationship between each index value and a corresponding data commit node in an index mapping table, for example, if the block 1 is generated according to service flow data in to-be-uplink data carried by an uplink request sent to the management node by the data commit node 1, the mapping relationship between the index value 001 corresponding to the block 1 and the data commit node 1 may be stored in the index mapping table, and the mapping relationship between the index value and a node identifier of the data commit node 1 may be stored in the index mapping table. The management node may add the target block to which the index value has been assigned to the traffic volume chain. Subsequently, the management node may find all index values having a mapping relationship with the data submitting node in the index mapping table through the node identifier of a certain data submitting node, and further find all blocks corresponding to the data submitting node in the full traffic chain through all index values having a mapping relationship with the data submitting node. For example, all blocks of the node corresponding to the enterprise are searched/obtained in the full traffic chain by searching all index values having an association relationship with the node corresponding to the enterprise in the index mapping table.

Please refer to fig. 3, which is a schematic view of a scene of an acquisition block according to the present application. As shown in fig. 3, the management node b8 stores an index mapping table b7 and a full traffic chain b 1. Here, it is illustrated that there are 3 data submitting nodes, which are respectively data submitting node 1, data submitting node 2 and data pricing node 3, and it is also illustrated that the traffic full-volume chain b1 includes 5 blocks, which are respectively block b2, block b3, block b4, block b5 and block b6, and the index value of each block is 000, 001, 002, 003 and 004 in turn. The index mapping table b7 stores a mapping relationship between the index value of each block in the service full-volume chain b1 and the corresponding data submission node, and includes: index value 000 corresponds to data commit node 1, indicating that the block indexed by 000 in the full volume chain b1 is generated by the business process data of data commit node 1, and similarly, index value 001 corresponds to data commit node 1, index value 002 corresponds to data commit node 2, index value 003 corresponds to data commit node 3, and index value 004 corresponds to data commit node 1. When management node b8 wants to search for a chunk of data commit node 1, it may obtain from index mapping table b7 that the index value corresponding to data commit node 1 includes index value 000, index value 001, and index value 004, and then management node b8 may obtain chunk b2, chunk b3, and chunk b5 in the full traffic chain by obtaining index value 000, index value 001, and index value 004. When management node b8 wants to search for the partition of data submitting node 2, it may obtain from index mapping table b7 that the index value corresponding to data submitting node 2 includes index value 002, and then management node b8 may obtain partition b4 in the full traffic chain according to the obtained index value 002. When the management node b8 wants to search for the partition of the data submitting node 3, it may obtain from the index mapping table b7 that the index value corresponding to the data submitting node 3 includes the index value 003, and then the management node b8 may obtain the partition b5 in the full traffic chain by using the obtained index value 003.

It should be noted that, if the data to be uplink is encrypted by the public key of the correct data submitting node, when the wrong private key (for example, the private key is not the private key of the corresponding data submitting node) is used to decrypt the data to be uplink, decryption failure may be caused, and the service flow data and the signature in the data to be uplink may not be obtained. On the contrary, if the to-be-uplink data is encrypted by the wrong public key (for example, the public key is not the public key of the corresponding data submitting node), when the private key of the correct data submitting node is used to decrypt the to-be-uplink data, decryption failure may also be caused, and the service flow data and the signature in the to-be-uplink data may not be obtained.

Wherein, each block in the traffic volume chain comprises a block head and a block body. If the target block of the generated business process data is the first block in the business full-scale chain, the block header included in the block stores the characteristic value (i.e., random number), the version number, the timestamp and the difficulty value of the input information, and the block body stores the input information (which may be the business process data or the first hash value corresponding to the business process data). If the target block of the generated business process data is not the first block in the business full-volume chain, the block header contained in the block stores the input information characteristic value of the current block (namely, the block of the generated business process data), the block header characteristic value, the version number, the timestamp and the difficulty value of the parent block (namely, the last block of the current block, namely, the block added latest on the business full-volume chain before the block of the business process data is added to the business full-volume chain), and so on, so that the block data stored in each block in the block chain is associated with the block data stored in the parent block, and the safety of the input information in the block is ensured. Please refer to fig. 4, which is a block diagram of the present application. As shown in fig. 4, the block c1 may be the first block in the full traffic chain, and the block c1 includes the characteristic value of the input information, the version number, the timestamp, and the difficulty value, but has no characteristic value of the block head of the parent block. Block c2 is the second block in the upper chain of the traffic volume chain, block c1 is the parent block of block c2, and block c2 includes the block header characteristic of the parent block (i.e., block c1) in addition to the input information characteristic, version number, timestamp, and difficulty value. Similarly, block c2 is the parent block of block c3, and block c3 includes the block header characteristic value of block c2 in addition to the input information characteristic value, version number, timestamp, and difficulty value.

Step S102, when receiving inquiry information aiming at the service processing permission of the audit object sent by a request terminal, acquiring the plurality of target blocks associated with the audit object from the service full-scale chain according to the inquiry information, and acquiring association relations among the service process data respectively included in the plurality of target blocks;

specifically, the request terminal may refer to an object for auditing the business process data submitted by the data submission node, for example, the request terminal may be a client corresponding to an export tax return bureau. The enterprise can apply for handling the export tax refund business to the export tax refund bureau, and the export tax refund bureau needs to check the business process data submitted to the management node by a plurality of data submitting nodes associated with the enterprise so as to judge whether the enterprise has the condition for handling the export tax refund business. When the management node obtains inquiry information, which is sent by the request terminal and is directed to the service processing permission of the audit object, the management node may obtain a data submission node associated with the audit object (which may be a node identifier of the data submission node associated with the audit object) according to the inquiry information, and obtain a plurality of blocks corresponding to the data submission node associated with the audit object from the full service chain (that is, a plurality of target blocks corresponding to the data submission node associated with the audit object may be obtained by an index value of the data submission node). The target blocks obtained here refer to a plurality of target blocks (for example, a target block corresponding to the enterprise, a block corresponding to the manufacturer, and a block corresponding to the logistics provider) corresponding to the business process data of the data submission node associated with a certain audit target (for example, the enterprise). For example, the audit object is an enterprise, and the management node may obtain a logistics object (i.e., a node identifier of a node corresponding to the logistics provider) and a production object (i.e., a node identifier of a node corresponding to the manufacturer) associated with the enterprise according to the query information, so that the management node may obtain a target block corresponding to the audit object, a target block corresponding to the logistics object, and a target block corresponding to the production object in the full traffic chain (or may obtain the target blocks according to the index value). The business process data in the target block corresponding to the audit object (i.e. the enterprise) is transaction voucher data (e.g. purchase voucher, which may be purchase order, receipt, contract and the like), the business process data in the target block corresponding to the logistics object is logistics data (e.g. the logistics information, i.e. positioning information, and article delivery route information), and the business process data in the target block corresponding to the production object is production data (e.g. photo or video of production shop pipeline operation when the producer produces the article).

The management node may obtain, according to the type of the query information, an association relationship that needs to be checked between the service flow data in the plurality of target blocks. For example, if the query information indicates whether the enterprise (i.e., the object to be checked) has conditions for handling export tax refunds, the association relationship that needs to be checked may be obtained to include a transaction association relationship, an object matching association relationship, and an article matching association relationship. The incidence relation to be audited can be set by itself, and different incidence relations to be audited can be set for different types of inquiry information. If the inquiry information is also the condition whether the enterprise (i.e. the auditing object) has the export tax return transaction, the association relationship needing to be audited, including the time association relationship, can also be acquired.

Step S103, auditing the incidence relation among a plurality of service process data, generating feedback information of the service processing permission aiming at the audited object according to the auditing result, and sending the feedback information to the request terminal;

specifically, the management node may check an association relationship between a plurality of acquired service process data (one service process data corresponds to one target block) in a plurality of target blocks. When the obtained association relation to be checked is the transaction association relation, the object matching association relation and the article matching association relation, the checking process specifically comprises the following steps: firstly, auditing a transaction association relationship, when a management node detects that a transaction acceptance object contained in the transaction voucher data is the production object, determining that the audit object and the production object have the transaction association relationship, and detecting an article receiving object and an article sending object contained in the logistics data: the management node may scan and identify the transaction credential data in the target block corresponding to the obtained audit object to obtain a transaction acceptance object in the transaction credential data, where the transaction acceptance object may be understood as an object to accept an order, that is, a seller (the audit object is a buyer). And when the acquired transaction acceptance object is the manufacturer corresponding to the audit object, indicating that the audit object and the production object have a transaction association relationship, namely that a transaction behavior exists between the two parties. After determining that the audit object and the production object have the transaction association relationship, further, the audit object may match the association relationship, and the management node may detect an article receiving object and an article sending object included in the logistics data. When the management node detects that the article receiving object is the auditing object and the article sending object is the production object, determining that the logistics object, the production object and the auditing object have an object matching association relationship, and comparing a transmission article attribute contained in the logistics data, a production article attribute contained in the production data and a transaction article attribute contained in the transaction voucher data: the management node may perform data identification (e.g., text identification) on the logistics data in the target block corresponding to the acquired logistics object, and further acquire a sender (i.e., the article sending object) and a receiver (i.e., the article receiving object) in the logistics data. And when the shipper in the logistics data is the production object corresponding to the audit object and the consignee is the audit object, indicating that the logistics object, the production object and the audit object have an object matching association relationship. Further, the item matching association relationship may be checked, and the management node may compare the attributes of the transport items included in the logistics data, the attributes of the production items included in the production data, and the attributes of the transaction items included in the transaction voucher data. When the management node compares that the transmission article attribute, the production article attribute and the transaction article attribute are the same, determining that the logistics object, the production object and the transaction initiating object have an article matching association relationship, and generating the confirmation information. The article attribute may include the number of articles, the category of the articles (for example, the category of clothes (may also be classified into clothes, trousers, shoes, skirts, etc.) or the category of jewelry), and the material of the articles (for example, cotton, linen, silver, gold, etc.). The management node may identify (e.g., text identification and image identification) the logistics data, and obtain the attribute of the transported item (i.e., the item attribute of the transported item) included in the logistics data; the management node may identify the production data (for example, image identification and video frame capture identification), and obtain the production item attributes contained in the production data (i.e., the item attributes of the items produced by the producer); the management node may identify (e.g., text recognition and image recognition) the transaction credential data, and obtain the transaction article attribute (i.e., the article attribute of the article transacted by both the audit object and the production object) included in the transaction credential data. The management node may compare the transmission article attribute, the production article attribute, and the transaction article attribute with each other for similarity (or consistency), and when the transmission article attribute, the production article attribute, and the transaction article attribute are the same, it indicates that the logistics object, the production object, and the transaction initiation object have an article matching association relationship. The feedback information comprises confirmation information and prompt information, wherein the confirmation information is generated when the management node verifies that the association relation among the verification object, the production object and the logistics object passes and confirms that the verification object has corresponding business processing authority (such as conditions for handling export tax refunds). The prompt information is generated when the management node fails to verify the association relation among the verification object, the production object and the logistics object and confirms that the verification object does not have corresponding business processing rights. When the management node verifies that the audit object, the production object and the logistics object simultaneously have the transaction association relationship, the object matching association relationship and the article matching association relationship, the management node indicates that the audit of the association relationship among the audit object, the production object and the logistics object is passed, and then the confirmation information can be generated. When the management node verifies that the audit object, the production object and the logistics object do not have at least one of the transaction association relationship, the object matching association relationship and the article matching association relationship, indicating that the audit on the association relationship among the audit object, the production object and the logistics object is not passed, the prompt information can be generated. The management node may send the generated feedback information to the request terminal, and the request terminal may determine whether to handle a corresponding service for the audit object according to the received feedback information. For example, when the request terminal receives the confirmation information sent by the management node, the corresponding export tax refund service may be handled for the audit object, and when the request terminal receives the prompt information sent by the management node, the corresponding export tax refund service may not be handled for the audit object.

Optionally, when the obtained association relationship to be checked includes the time association relationship, the management node may detect the transaction time of the transaction credential data, the logistics time of the logistics data, and the production time of the production data: that is, the management node may identify the transaction credential data, and identify a transaction time (e.g., a time to sign an order or a contract) in the transaction credential data; the management node can identify the logistics data and identify the logistics time (such as logistics order receiving time, goods delivery time, time of arriving at a certain transfer station in the delivery process, harvesting time and the like) in the logistics data; the management node may identify production data, identify production times in the production data (start time, end time, and intermediate transition times for producing the item, etc. (intermediate transition times may include production schedules for the item), etc.). And when the management node detects that the transaction time, the logistics time and the generation time meet the time association relationship on the time axis, generating the confirmation information. For example, the time correlation on the time axis includes: the transaction time and the production time must be before the logistics time (for example, before the goods delivery time), and the transaction time may be before the production time or after the production time, wherein the specific standard of the time association relationship may be specifically set according to the actual application scenario, and is not limited herein. And when the management node detects that the transaction time, the logistics time and the generation time do not meet the time association relationship on the time axis, generating the prompt message. The generation process of the feedback information for the service processing permission of the audit object described in the data processing method in fig. 2 is described by taking an audit object as an example, and when a plurality of audit objects exist, the generation process of the feedback information corresponding to each audit object is independent and the same.

By the method, the block chain network is applied to the export tax refund business, and information with basis can be searched and audited for the articles involved in the export tax refund business in the whole cycle process of production (the production process of a manufacturer), transportation (the transportation process of a logistics provider) and transaction (the transaction process of an enterprise and the manufacturer). In addition, due to the fact that the block link network is not capable of being tampered, the accuracy and the safety of auditing for the export tax refunding business are improved.

Please refer to fig. 5, which is a schematic structural diagram of a data auditing apparatus based on a blockchain network according to the present application. As shown in fig. 5, the data auditing apparatus 1 may include: a first acquisition module 11, a second acquisition module 12 and an auditing module 13;

a first obtaining module 11, configured to obtain uplink requests corresponding to multiple pieces of to-be-uplink data associated with an audit object, generate multiple target blocks according to the uplink requests corresponding to the multiple pieces of to-be-uplink data, and add the multiple target blocks to a full-service chain; the uplink request carries the data to be uplink; the data to be uplink comprises service flow data; the business total chain is used for storing blocks corresponding to all business process data; the blocks corresponding to all the business process data comprise the plurality of target blocks;

a second obtaining module 12, configured to, when query information for a service processing permission of the audit object sent by a request terminal is received, obtain, according to the query information, the multiple target blocks associated with the audit object from the full service chain, and obtain association relationships between the service process data included in the multiple target blocks respectively;

the auditing module 13 is configured to audit the association relationship among the plurality of pieces of business process data, generate feedback information of the business processing permission for the audited object according to an auditing result, and send the feedback information to the request terminal; the feedback information comprises confirmation information that the auditing object has the service processing authority or prompt information that the auditing object does not have the service processing authority.

For specific implementation of functions of the first obtaining module 11, the second obtaining module 12, and the auditing module 13, please refer to steps S101 to S103 in the embodiment corresponding to fig. 2, which is not described herein again.

The second obtaining module 12 includes a first obtaining unit 121, a block obtaining unit 122, and a determining unit 123:

a first obtaining unit 121, configured to obtain a logistics object and a production object associated with the audit object;

a block obtaining unit 122, configured to obtain, in the full service chain, a target block corresponding to the audit object, a target block corresponding to the logistics object, and a target block corresponding to the production object;

a determining unit 123, configured to determine, as the business process data, transaction credential data in a target block corresponding to the audit object, logistics data in the target block corresponding to the logistics object, and production data in the target block corresponding to the production object.

For a specific implementation manner of the functions of the first obtaining unit 121, the block obtaining unit 122, and the determining unit 123, please refer to step S102 in the corresponding embodiment of fig. 2, which is not described herein again.

The auditing module 13 includes a first detecting unit 131, a second detecting unit 132, and a first generating unit 133:

a first detecting unit 131 configured to, when it is detected that the transaction acceptance object included in the transaction voucher data is the production object, determine that the audit object and the production object have a transaction association relationship with each other, and detect an article receiving object and an article issuing object included in the logistics data;

a second detecting unit 132, configured to determine that the logistics object, the production object, and the audit object have an object matching association relationship when it is detected that the article receiving object is the audit object and the article sending object is the production object, and compare a transmission article attribute included in the logistics data, a production article attribute included in the production data, and a transaction article attribute included in the transaction credential data;

a first generating unit 133, configured to determine that the logistics object, the production object, and the transaction initiation object have an object matching association relationship when the transmission object attribute, the production object attribute, and the transaction object attribute are the same through comparison, and generate the confirmation information.

For a specific implementation manner of the functions of the first detecting unit 131, the second detecting unit 132, and the first generating unit 133, please refer to step S103 in the corresponding embodiment of fig. 2, which is not described herein again.

The auditing module 13 includes a third detecting unit 134 and a second generating unit 135:

a third detecting unit 134, configured to detect a transaction time of the transaction credential data, a logistics time of the logistics data, and a production time of the production data;

a second generating unit 135, configured to generate the confirmation information when the transaction time, the logistics time, and the generation time satisfy a time association relationship on a time axis.

For a specific implementation manner of the functions of the third detecting unit 134 and the second generating unit 135, please refer to step S103 in the corresponding embodiment of fig. 2, which is not described herein again.

The management node holds a key pair of a data submitting node to which each piece of data to be uplink belongs; the key pair comprises a private key and a key of the data submission node; the first obtaining module 11 includes a first decryption unit 111, a second decryption unit 112, an operation unit 113, and a fourth detection unit 114:

a first decryption unit 111, configured to decrypt, based on a private key of a data submitting node to which each piece of to-be-uplink data belongs, to the to-be-uplink data carried by each uplink request, respectively, so as to obtain a signature and service flow data in each piece of to-be-uplink data;

a second decryption unit 112, configured to decrypt the corresponding signatures based on the public key of the data submission node to which each piece of data to be linked belongs, to obtain a first hash value in each signature;

the operation unit 113 is configured to perform hash operation on each piece of business process data based on a hash algorithm, respectively, to obtain a second hash value corresponding to each piece of business process data;

a fourth detecting unit 114, configured to, when it is detected that each first hash value is the same as the corresponding second hash value, check that the signature passes, and generate the multiple target blocks according to the multiple data to be uplink.

For a specific implementation manner of the functions of the first decryption unit 111, the second decryption unit 112, the operation unit 113, and the fourth detection unit 114, please refer to step S101 in the corresponding embodiment of fig. 2, which is not described herein again.

The first obtaining module 11 includes an encrypting unit 115 and a first adding unit 116:

an encrypting unit 115, configured to encrypt the included service flow data based on a public key corresponding to a data submitting node to which each piece of data to be linked belongs, to obtain encrypted data corresponding to each piece of service flow data;

a first adding unit 116, configured to generate a target block corresponding to each piece of business process data according to the encrypted data corresponding to each piece of business process data, and add the target block corresponding to each piece of business process data to the business full-scale chain.

For a specific implementation manner of functions of the encryption unit 115 and the first adding unit 116, please refer to step S101 in the corresponding embodiment of fig. 2, which is not described herein again.

The first obtaining module 11 includes a mapping unit 117 and a second adding unit 118:

a mapping unit 117, configured to generate an index value corresponding to each of the multiple target blocks based on a block height incrementing mechanism, and store a mapping relationship between each index value and a corresponding data commit node in an index mapping table;

a second adding unit 118, configured to add the each target chunk with the index value to the full traffic chain.

For a specific implementation manner of functions of the mapping unit 117 and the second adding unit 118, please refer to step S101 in the corresponding embodiment of fig. 2, which is not described herein again.

Please refer to fig. 6, which is a schematic structural diagram of a computer device provided in the present application. As shown in fig. 6, the computer apparatus 1000 may include: the processor 1001, the network interface 1004, and the memory 1005, the computer apparatus 1000 may further include: a user interface 1003, and at least one communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display) and a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a standard wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 6, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.

In the computer device 1000 shown in fig. 6, the network interface 1004 may provide a network communication function; the user interface 1003 is an interface for providing a user with input; the processor 1001 may be configured to call the device control application stored in the memory 1005, so as to implement the description of the data auditing method based on the blockchain network in the embodiment corresponding to fig. 2.

It should be understood that the computer device 1000 described in this application may perform the description of the data auditing method based on the blockchain network in the embodiment corresponding to fig. 2, and may also perform the description of the data auditing apparatus 1 in the embodiment corresponding to fig. 5, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.

Further, here, it is to be noted that: the present application further provides a computer-readable storage medium, where the computer program executed by the aforementioned data auditing apparatus 1 is stored in the computer-readable storage medium, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the data auditing method based on the blockchain network in the embodiment corresponding to fig. 2 can be executed, so that details are not repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in the embodiments of the computer storage medium referred to in the present application, reference is made to the description of the embodiments of the method of the present application.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto but rather by the claims appended hereto.

Claims

1. A data auditing method based on a block chain network is characterized by comprising the following steps:

2. The method according to claim 1, wherein the obtaining the target blocks associated with the audit object from the business full volume chain according to the query information comprises:

3. The method according to claim 2, wherein the auditing the association relationship between the plurality of business process data and generating feedback information of the business processing permission for the audited object according to the auditing result includes:

4. The method according to claim 2, wherein the auditing the association relationship between the plurality of business process data and generating feedback information of the business processing permission for the audited object according to the auditing result includes:

5. The method according to claim 1, wherein the management node holds a key pair of a data submitting node to which each data to be uplink belongs; the key pair comprises a private key and a key of the data submission node; generating a plurality of target blocks according to the uplink requests respectively corresponding to the plurality of data to be uplink transmitted comprises:

respectively decrypting the corresponding signatures based on the public key of the data submission node to which each piece of data to be uplink belongs to obtain a first hash value in each signature;

performing hash operation on each service flow data based on a hash algorithm to obtain a second hash value corresponding to each service flow data;

and when each first hash value is detected to be the same as the corresponding second hash value, the signature verification is passed, and the target blocks are generated according to the data to be linked.

6. The method of claim 1, wherein the generating a plurality of target blocks according to the plurality of data to be uplink, and adding the plurality of target blocks to a traffic volume chain comprises:

7. The method of claim 1, wherein adding the plurality of target blocks to a traffic volume chain comprises:

adding the each target chunk with the index value to the traffic volume chain.

8. A data auditing device based on a block chain network is applied to a management node and is characterized by comprising:

a first obtaining module, configured to obtain uplink requests corresponding to multiple pieces of to-be-uplink data associated with an audit object, generate multiple target blocks according to the uplink requests corresponding to the multiple pieces of to-be-uplink data, and add the multiple target blocks to a full-service chain; the uplink request carries the data to be uplink; the data to be uplink comprises service flow data; the business total chain is used for storing blocks corresponding to all business process data; the blocks corresponding to all the business process data comprise the plurality of target blocks;

9. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method according to any one of claims 1-7.