CN110601856B - Data interaction method and device based on block chain network - Google Patents

Data interaction method and device based on block chain network Download PDF

Info

Publication number
CN110601856B
CN110601856B CN201910907463.9A CN201910907463A CN110601856B CN 110601856 B CN110601856 B CN 110601856B CN 201910907463 A CN201910907463 A CN 201910907463A CN 110601856 B CN110601856 B CN 110601856B
Authority
CN
China
Prior art keywords
data
uplink
block
node
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910907463.9A
Other languages
Chinese (zh)
Other versions
CN110601856A (en
Inventor
张懿方
戴传兵
郭鹏
洪晓雯
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201910907463.9A priority Critical patent/CN110601856B/en
Publication of CN110601856A publication Critical patent/CN110601856A/en
Application granted granted Critical
Publication of CN110601856B publication Critical patent/CN110601856B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/10—Tax strategies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/26—Government or public services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Abstract

The application discloses a data interaction method and a data interaction device based on a block chain network, wherein the method comprises the following steps: the data submitting node sends the data to be linked to the participating node; the participating node generates a chain transmission request carrying the data to be chain transmitted, and transmits the chain transmission request to the management node; the management node checks the uplink data to be carried by the uplink request, if the check passes, a block is generated according to the uplink request, and the block is added to the business full-scale chain; when the management node receives inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by the request terminal, the management node acquires a block from the service full-scale chain and acquires the service process data through the block; and the management node audits the service flow data and generates feedback information aiming at the service processing permission corresponding to the service flow data according to the audit result. By the method and the device, interaction modes among the nodes are enriched, and auditing efficiency for the business process data is improved.

Description

Data interaction 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 interaction method and apparatus based on a blockchain network.
Background
With the continuous development of computer networks, the business transaction processes of the existing export tax refund can also be realized through the networks, but the business transaction process cannot meet the requirements of users.
In the prior art, usually, an audit object acquires a mail with an attestation property in a related authority department through an attestation material of export tax return, and then the acquired mail is sent to an audit department, and the audit department performs audit according to the validity of the received mail to determine whether to handle export tax return service for the audit object. According to the process, when the auditing object needs to handle the export tax refunding business, the relevant authoritative department needs to be reached to obtain the mail, and then the application of the export tax refunding business is carried out at the auditing department through the mail, and the business handling process is discontinuous, so that the business handling efficiency is low. In addition, the auditing department can only check and verify the checked mail of the auditing object, and cannot know the specific process of the business of the export tax refund business which needs to be handled by the auditing object, so that the auditing is not accurate enough.
Content of application
The application provides a data interaction method and device based on a block chain network, which can improve auditing efficiency and auditing accuracy for business handling.
One aspect of the present application provides a data interaction method based on a blockchain network, including:
the data submitting node sends the data to be linked to the participating node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
the participating node generates a chain loading request carrying the data to be chain loaded, and sends the chain loading request to a management node; the uplink request carries the data to be uplink;
the management node checks the uplink data to be linked carried by the uplink request, if the check passes, a block is generated according to the uplink data to be linked, and the block is added to a service full-scale chain;
when the management node receives inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, the block is obtained from the service full-scale chain according to the inquiry information, and the service process data is obtained through the block;
and the management node verifies the data authenticity and the data integrity of the business process data and generates feedback information aiming at the business processing permission corresponding to the business process data according to a verification result.
Wherein, still include:
when the participating node detects that the block exists in the business full-scale chain, acquiring the block from the business full-scale chain, extracting a block head from the block, and returning the block head to the data submitting node;
and the data submitting node adds the block head to the service subchain.
The management node also stores a mapping relation between the business process data and the first hash value in a local database;
the acquiring the business process data through the block includes:
when the data to be uplink comprises the first hash value corresponding to the business process data, the management node extracts the first hash value from the block;
the management node acquires the business process data from the local database according to the first hash value and the mapping relation between the first hash value and the business process data;
and when the data to be uplink comprises the business process data, the management node extracts the business process data from the block.
Wherein, the data submitting node sends the data to be uplink to the participating node, including:
when the data submitting node detects that the data volume of the business process data is smaller than a data volume threshold value, performing hash operation on the business process data based on a hash algorithm to obtain a first hash value corresponding to the business process data;
the data submitting node signs the first hash value based on the corresponding private key to obtain a first signature corresponding to the first hash value, and adds the business process data and the first signature to a first to-be-uplink data packet;
the data submitting node encrypts the first to-be-uplink data packet based on the corresponding public key to obtain the to-be-uplink data;
and the data submitting node submits the data to be uplink to the participating node.
Wherein, the data submitting node sends the data to be uplink to the participating node, including:
when the data submitting node detects that the data volume of the business process data is larger than or equal to a data volume threshold value, performing hash operation on the business process data based on a hash algorithm to obtain a first hash value corresponding to the business process data;
the data submission node performs hash operation on the first hash value based on the hash algorithm to obtain a second hash value corresponding to the first hash value;
the data submitting node signs the second hash value based on the corresponding private key to obtain a second signature corresponding to the second hash value, and adds the second signature and the first hash value to a second data packet to be uplinked;
the data submitting node encrypts the second data packet to be uplink based on the corresponding public key to obtain the data to be uplink;
and the data submitting node submits the data to be uplink to the participating node.
Another aspect of the present application provides a data interaction method based on a blockchain network, including:
a participating node acquires data to be uplink sent by a data submitting node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
generating a chain loading request carrying the data to be chain loaded, and sending the chain loading request to a management node, so that the management node adds the data to be chain loaded to a full service chain when the check label of the data to be chain loaded carried by the chain loading request passes, and generates feedback information through the full service chain when inquiry information aiming at the service processing permission corresponding to the service flow data is acquired; the feedback information is generated after the management node verifies the data authenticity and the data integrity of the business process data.
In another aspect, the present application provides a data interaction method based on a blockchain network, including:
the method comprises the steps that a management node obtains a uplink request carrying to-be-uplink data sent by a participating node, conducts signature verification on the to-be-uplink data carried by the uplink request, generates a block according to the to-be-uplink data if the signature verification passes, and adds the block to a business full-scale chain; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
when receiving inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, acquiring the block from the service full-scale chain according to the inquiry information, and acquiring the service process data through the block;
and auditing the data authenticity and the data integrity of the business process data, and generating feedback information aiming at the business processing permission corresponding to the business process data according to an auditing result.
One aspect of the present application provides a data interaction device based on a blockchain network, which is applied to a participating node, and includes:
the first acquisition module is used for acquiring data to be uplink sent by the data submitting node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
a generating module, configured to generate a uplink request carrying the to-be-uplink data, and send the uplink request to a management node, so that when the management node passes an identification of the to-be-uplink data carried in the uplink request, the to-be-uplink data is added to a full-service chain, and when inquiry information for a service processing permission corresponding to the service process data is acquired, feedback information is generated through the full-service chain; the feedback information is generated after the management node verifies the data authenticity and the data integrity of the business process data.
The data interaction device based on the blockchain network is further configured to:
and when the block is detected to exist in the service full-scale chain, acquiring the block from the service full-scale chain, extracting a block head from the block, and returning the block head to the data submission node.
Another aspect of the present application provides a data interaction apparatus based on a blockchain network, which is applied to a management node, and includes:
a second obtaining module, configured to obtain a uplink request carrying to-be-uplink data sent by a participating node, perform signature verification on the to-be-uplink data carried by the uplink request, generate a block according to the to-be-uplink data if the signature verification passes, and add the block to a full-service chain; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
the receiving module is used for acquiring the block from the service full-scale chain according to the inquiry information and acquiring the service process data through the block when the inquiry information aiming at the service processing authority corresponding to the service process data and sent by the request terminal is received;
and the auditing module is used for auditing the data authenticity and the data integrity of the business process data and generating feedback information aiming at the business processing permission corresponding to the business process data according to an auditing result.
The management node also stores a mapping relation between the business process data and the first hash value in a local database;
the receiving module comprises:
a first extracting unit, configured to, when the data to be uplink includes the first hash value corresponding to the service flow data, extract, by the management node, the first hash value from the block;
an obtaining unit, configured to obtain the business process data in the local database according to the first hash value and a mapping relationship between the first hash value and the business process data;
a second extracting unit, configured to extract the service flow data from the block when the to-be-uplink data includes the service flow data.
One aspect of the present application provides a computer device, comprising: a processor and a memory;
the memory stores a computer program which, when executed by the processor, causes the processor to perform the method as in one/another/further aspect of the application.
The present application provides in one aspect 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/another/further aspect.
Firstly, a data submitting node sends data to be linked to a participating node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data; the participating node generates a chain loading request carrying the data to be chain loaded, and sends the chain loading request to a management node; the uplink request carries the data to be uplink; the management node checks the uplink data to be linked carried by the uplink request, if the check passes, a block is generated according to the uplink data to be linked, and the block is added to a service full-scale chain; when the management node receives inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, the block is obtained from the service full-scale chain according to the inquiry information, and the service process data is obtained through the block; and the management node verifies the data authenticity and the data integrity of the business process data and generates feedback information aiming at the business processing permission corresponding to the business process data according to a verification result. Therefore, the method provided by the application supports the data submission node to send the business process data to the management node through the participation node, the request terminal can obtain the business process data sent by the data submission node through the management node and obtain the auditing result of the business processing permission of the business process data, and the auditing result is the feedback information, so that the auditing efficiency of the business process data uploaded by the data submission node 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 interaction scenario provided in the present application;
fig. 2 is a schematic flowchart of a data interaction method based on a blockchain network according to the present application;
FIG. 3 is a schematic flow chart of generating a signature provided herein;
FIG. 4 is a block diagram of the present application;
fig. 5 is a schematic structural diagram of a data interaction device based on a blockchain network provided in the present application;
fig. 6 is a schematic structural diagram of another data interaction device based on a blockchain network provided in the present application;
fig. 7 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 interaction scenario provided in the present application. As shown in fig. 1, the data commit node 101b, the participating node 102b, and the management node 103b are blockchain nodes under the same blockchain network. The data submitting node 101b, the participating node 102b and the managing node 103b may correspond to one or more servers, respectively. The data submitting node 101b may be a node corresponding to an object (which may include the enterprise and other enterprises associated with the enterprise) that needs to submit the audit data required by a business when the enterprise transacts the business. For example, when enterprise a needs to handle a service and enterprise a and enterprise B need to upload related service data to be checked together, the data submitting node 101B may be a node corresponding to enterprise a and a node corresponding to enterprise B. The data interaction among the data submitting nodes 101b, the participating node 102b and the management node 103b can be referred to as follows, the following processes are all described by taking the data interaction of one data submitting node as an example, and when a plurality of data submitting nodes exist, the data interaction process of each data submitting node is independent and the same. The data submitting node 101b includes the service flow data, and when the data submitting node 101b wants to upload the service flow data to the full service chain 104b, the data to be uplink may be obtained according to the service flow data. The specific process of obtaining the data to be uplink includes: in a first manner, the data submitting node 101b may detect the data size of the business process data, and when the data submitting node 101b detects that the data size of the business process data is smaller than the data size threshold, the business process data may be operated based on a hash algorithm to obtain a hash value corresponding to the business process data, and the hash value may be referred to as a first hash value. The data submitting node 101b may use its own private key to sign the first hash value, to obtain a signature corresponding to the first hash value, and the signature may be referred to as a first signature. The data submitting node 101b may package the service flow data and the first signature to obtain a to-be-uplink data packet, and may refer to the to-be-uplink data packet as a first to-be-uplink data packet. The data submitting node 101b may also encrypt the first to-be-uplink data packet by using its own public key, and may use the encrypted first to-be-uplink data packet as the to-be-uplink data. In a second manner, when the data submitting node 101b detects that the data size of the business process data is greater than the data size threshold, the business process data may be operated based on a hash algorithm to obtain the first hash value. The data submitting node 101b may perform hash operation on the first hash value again through a hash algorithm to obtain a hash value corresponding to the first hash value, which may be referred to as a second hash value. The data submitting node 101b may use its own private key to sign the second hash value, to obtain a signature corresponding to the second hash value, and the signature may be referred to as a second signature. The data submitting node 101b may package the first hash value and the second signature to obtain a to-be-uplink data packet, and may refer to the to-be-uplink data packet as a second to-be-uplink data packet. The data submitting node 101b may also encrypt the second to-be-uplink data packet by using its own public key, and may use the encrypted second to-be-uplink data packet as the to-be-uplink data.
The data submitting node 101b may send the acquired to-be-uplink data to the participating node 102b, and the participating node 102b may generate an uplink request according to the received to-be-uplink data, where the uplink request carries the to-be-uplink data. The participating node 102b may send the generated uplink request to the management node 103b, where the management node 103b performs an authentication on the to-be-uplink data in the uplink request, and after the authentication passes, the management node 103b proves that the uplink request is legal, and then the management node 103b may generate a block 107b according to the to-be-uplink data carried in the uplink request, where the block 107b includes the service flow data or the first hash value corresponding to the service flow data. If the data to be uplink includes the service flow data, the block 107b also includes the service flow data, and if the data to be uplink includes the first hash value, the block 107b also includes the first hash value. The management node 103b may add the block 107b to the full traffic chain 104 b. The management node 103b and the participating node 102b commonly hold the full-traffic chain 104b, and the management node 103b and the participating node 102b can be understood as two systems built in the full-traffic chain 104 b. The management node 103b has the authority to uplink data, view data on the link, and acquire data on the link for the full-volume service link, and the participating node 102b has the authority to view data on the link and acquire data on the link.
When the management node 103b acquires the inquiry information sent by the request terminal 106b for the service processing permission corresponding to the service flow data, the management node 103b may acquire the block corresponding to the service flow data, that is, the block 107b, from the full-service chain 104 b. The management node 103b may generate feedback information according to the block 107b, specifically, refer to the area 105 b. As shown in the area 105b, the management node 103b may obtain the service flow data according to the block 107b, specifically: if the block 107b includes the business process data, the management node 103b may directly extract the business process data from the block 107 b. If the block 107b includes the first hash value corresponding to the service flow data, the management node 103b may extract the first hash value from the block 107b, and further obtain the service flow data from the local database according to the first hash value. It should be noted that, the data submitting node sends the service flow data and the first hash value to the local database of the management node 103b in advance through a offline manner, and the local database stores a mapping relationship between the service flow data and the first hash value (it can be understood that the service flow data and the first hash value are stored in an associated manner), so that the management node 103b may correspondingly find the service flow data in the local database through the extracted first hash value.
The management node 103b may audit data authenticity and data integrity of the obtained business process data, and the management node 103b may generate feedback information according to an audit result. For example, when the management node 103b detects that the business process data does not have any one of data authenticity and data integrity, a prompt message may be generated, where the prompt message is feedback information, and the prompt message may be "no business processing authority". When the management node 103b detects that the service flow data has data authenticity and data integrity, it may generate confirmation information, that is, feedback information, and the confirmation information may be "having service processing authority". The management node may send the generated feedback information (including the confirmation information or the prompt information) to the requesting terminal 106b, and the requesting terminal 106b may perform corresponding service transaction according to the received feedback information.
Please refer to fig. 2, which is a flowchart illustrating a data interaction method based on a blockchain network according to the present application, and as shown in fig. 2, the method may include:
step S101, a data submitting node sends data to be uplinked to a participating node;
specifically, there may be multiple data submitting nodes, each of which is capable of sending data to be uplinked to a participating node. The method provided by the application can be applied to export tax refund, so that the data submission node can also be a node corresponding to an object which needs to submit the auditing materials when the export tax refund is handled. The objects to be submitted for the audit material may include enterprises applying for export tax refunds, manufacturers purchasing articles from enterprises, and logistics merchants entrusted by manufacturers to ship articles. The data to be uplinked may include service flow data sent by the data submitting node to the participating node or a hash value corresponding to the service flow data. When the data submission node is a node corresponding to the enterprise, the business process data can be a purchase voucher 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 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 the logistics provider, the business process data may be logistics information (positioning information, i.e., item transportation route information) of the logistics provider during transportation of the item.
When the data submitting node detects that the data volume of the business process data is greater than or equal to a data volume threshold, performing hash operation on the business process data based on a hash algorithm to obtain the first hash value corresponding to the business process data: the data submitting node may detect the data size of the business process data that needs to be sent to the participating node, and when the data size of the business process data is detected to be large (for example, a data size threshold is set, and if the data size of the business process data is greater than or equal to the data size threshold, it is determined that the data size of the business process data is large), the hash value of the business process data may be calculated through a hash algorithm, and the hash value may be referred to as a first hash value. The hash algorithm is to convert an input with an arbitrary length (also called a pre-mapped pre-image) into an output with a fixed length through a hash algorithm, and the output is a hash value. The conversion is a compression mapping, that is, the space of the hash value is usually much smaller than the space of the input, so when the data volume of the service flow data is large, the service flow data can be linked up corresponding to the hash value instead of the service flow data itself, so as to save the space memory of the service block chain. Stated another way, a hash algorithm is a function that compresses a message of arbitrary length to a message digest of some fixed length. The data submission node performs hash operation on the first hash value based on the hash algorithm to obtain a second hash value corresponding to the first hash value: the data submission node may recalculate the hash value corresponding to the first hash value by using a hash algorithm, and the hash value corresponding to the first hash value may be referred to as a second hash value. The data submission node signs the second hash value based on the corresponding private key to obtain a second signature corresponding to the second hash value, and adds the second signature and the first hash value to a second data packet to be uplinked: the data submitting node may encrypt the second hash value by using its own private key to generate an encrypted second hash value, and may refer to the encrypted second hash value as a signature of the first hash value, that is, the second signature, and the data submitting node may package the second signature and the first hash value to obtain a second to-be-uplink data packet. The data submitting node encrypts the second to-be-uplink data packet based on the corresponding public key to obtain the to-be-uplink data: the data submitting node may encrypt the second to-be-uplink data packet by using its own public key, and may refer to the encrypted second to-be-uplink data packet as the to-be-uplink data.
When the data submitting node detects that the data volume of the business process data is smaller than a data volume threshold, performing hash operation on the business process data based on a hash algorithm to obtain the first hash value corresponding to the business process data: when the data submitting node detects that the data volume of the business process data is small (for example, a data volume threshold is set, and if the data volume of the business process data is smaller than the data volume threshold, it is determined that the data volume of the business process data is small), the business process data may also be subjected to hash operation to obtain the first hash value. The data submitting node signs the first hash value based on the corresponding private key to obtain a first signature corresponding to the first hash value, and adds the business process data and the first signature to a first to-be-uplink data packet: the data submitting node encrypts the first hash value by using a private key of the data submitting node to obtain an encrypted first hash value, the encrypted first hash value can be called as the first signature corresponding to the business process data, and the business process data and the first signature can be packaged to obtain a first to-be-uplink data packet. The data submitting node encrypts the first to-be-uplink data packet based on the corresponding public key to obtain the to-be-uplink data: the data submitting node may encrypt the first to-be-uplink data packet by using its own public key, and may refer to the encrypted first to-be-uplink data packet as the to-be-uplink data.
Please refer to fig. 3, which is a schematic diagram illustrating a process of generating a signature according to the present application. As shown in fig. 3, when the data volume of the business process data is large (greater than or equal to the data volume threshold), the data submitting node may perform hash operation on the business process data through a hash algorithm to obtain a first hash value, perform hash operation on the first hash value again to obtain a second hash value, and then the data submitting node may obtain a second signature through the second hash value. The data submitting node may encapsulate the first hash value and the second signature to obtain the to-be-uplink data corresponding to the business process data. When the data volume of the business process data is small (smaller than the data volume threshold), the data submission node can perform hash operation on the business process data through a hash algorithm to obtain a first hash value, and then the data submission node can obtain a first signature through the first hash value. The data submitting node may encapsulate the service flow data and the first signature, and obtain the to-be-uplink data corresponding to the service flow data.
That is, when the data size of the service flow data is large, the data to be uplink transmitted by the data submitting node to the participating node includes the hash value corresponding to the service flow data (i.e., the first hash value), which indicates that the data to be uplink is the hash value corresponding to the service flow data, and the uplink service flow data itself is not needed, so as to save the block chain memory. When the data volume of the service process data is smaller, the data submitting node sends the data to be uplink-linked to the participating node, wherein the data to be uplink-linked includes the service process data, namely the data to be uplink-linked includes the service process data. The data submitting node may send the obtained data to be uplink to the participating nodes. The participating nodes can be understood as interfaces for submitting the business process data to the data submitting nodes, and a plurality of data submitting nodes can submit the respective business process data through one interface of the participating nodes.
In addition, when the data to be uplink includes a hash value (i.e., a first hash value) of the service flow data, that is, when the data to be uplink is a second data packet to be uplink after encryption, the data submitting node may send the service flow data and the first hash value to the management node through a wire-down manner, and the management node may store the first hash value and the service flow data in association in the local database, that is, the management node may store the received service flow data and the first hash value sent by the data submitting node, and may also store a mapping relationship between the service flow data and the first hash value. Subsequently, if the management node obtains the first hash value, the management node may obtain the corresponding service flow data from the local database according to the mapping relationship between the stored first hash value and the service flow data and the first hash value.
Step S102, a participating node generates a uplink request carrying the data to be uplink;
specifically, the participating node receives data to be uplink sent by the data submitting node, and the participating node may generate an uplink request according to the data to be uplink, where the uplink request is a request for the participating node to request the management node to add service flow data in the data to be uplink or a hash value corresponding to the service flow data to the service full-length chain. The uplink request carries data to be uplink transmitted. The participating node may correspond to a client, which may be understood as an interface provided for uploading data requiring uplink to the data submitting node, and when there are multiple data submitting nodes, the interface provided by the participating node may be used together to upload data.
Step S103, the participating node sends the uplink request to the management node;
step S104, the management node checks the data to be uplink carried by the uplink request, if the check passes, a block is generated according to the data to be uplink, and the block is added to a service full-scale chain;
specifically, the management node receives the uplink request and obtains the to-be-uplink data carried by the uplink request. The management node can check the labels of the data to be uplink, specifically: the management node holds a key pair of all data submitting nodes, wherein the key pair comprises a private key and a secret key of the data submitting nodes. Here, only 1 data submitting node is used for explanation, the data processing process of each data submitting node is independent and the same, the specific number of the data submitting nodes is determined according to the actual application scenario, and the method is not limited here. When the data to be uplink is the encrypted first data packet to be uplink, the management node may decrypt the encrypted first data packet to be uplink by using the private key of the data submitting node to obtain the service flow data and the first signature in the first data packet to be uplink. Then, the management node may decrypt the first signature using the public key of the data submission node to obtain the first hash value in the first signature. The management node may perform hash operation on the service flow data acquired from the first to-be-uplink data packet to obtain a hash value, and the hash value may be referred to as a third hash value. If the management node detects that the first hash value obtained from the first signature is the same as the third hash value, it is determined that the service flow data in the received first to-be-uplink data packet is not tampered, the block (including the service flow data) is generated according to the received service flow data, and the generated block is added to the full-traffic chain. When the data to be uplink is the encrypted second data packet to be uplink, the management node may decrypt the encrypted second data packet to be uplink by using the private key of the data submitting node to obtain the first hash value and the second signature in the second data packet to be uplink. Then, the management node may decrypt the second signature using the public key of the data submitting node to obtain a second hash value in the second signature. The management node may perform a hash operation on the first hash value extracted from the second to-be-uplink data packet to obtain a third hash value. If the management node detects that the second hash value and the third hash value in the second signature are the same, it is determined that the first hash value in the received second to-be-uplink data packet is not tampered, the block (including the first hash value in the block) may be generated according to the received first hash value, and the block is added to the full traffic chain. And blocks corresponding to the respectively submitted business process data of all the data submitting nodes are stored in the business full-scale chain.
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 generated block of the service flow data is the first block in the full traffic chain, the block header included in the block stores the characteristic value (i.e., the 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 service flow data or the first hash value corresponding to the service flow data). If the generated block of the business process data is not the first block in the business full-volume chain, the input information characteristic value of the current block (namely, the generated block of the business process data), the block head characteristic 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), the version number, the timestamp and the difficulty value are stored in the block head contained in the block, and the like, 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.
In addition, after the management node adds the block corresponding to the generated business process data to the business full-scale chain, the participating node can check and acquire the block in the business full-scale chain. When the participating node detects that the block exists in the full service chain, acquiring the block from the full service chain, extracting a block head from the block, and returning the block head to the data submitting node: when the participating node detects that a block (i.e., a newly added block) corresponding to the service process data exists on the full traffic chain, the participating node may obtain the block from the full traffic chain, extract a block header in the block, and send the extracted block header to a data submitting node corresponding to the block (i.e., a data submitting node that uploads the service process data in the block or uploads a first hash value of the service process data). The data commit node may add the received chunk header to its own service subchain. The management node holds the full-service chain, the management node can maintain all blocks in the full-service chain, the management node includes all feasible operation permissions (including uplink of data, acquisition and viewing of data on the chain, and the like) for the full-service chain, and sets permissions (for example, viewing of data on the chain or acquiring data on the chain) opened by the full-service chain for other nodes) for the full-service chain, and the management node can set related permissions for participating nodes, for example, the participating nodes can view data on the full-service chain and acquire data on the full-service chain, so as to implement the operation of acquiring a block on the full-service chain and returning a block header in the block to a corresponding data submitting node. Optionally, the management node and the participating node may also jointly hold the full-traffic chain, except that the management node and the participating node have different operation permissions for the full-traffic chain, for example, the management node may uplink data, and the participating node cannot uplink data. Through the above process, the management node can maintain all the blocks of the data submitting nodes on the service full-scale chain, and the management node can be called a full-scale node or a common node. In addition, if there are multiple data submitting nodes, each data submitting node corresponds to one service sub-chain, and each service sub-chain stores the block header of the corresponding data submitting node in the service full-volume chain, each data submitting node may be referred to as an spv node (light weight node), and the spv node only stores the block header of the corresponding transaction (the block header corresponding to the uplink service flow data or the block header corresponding to the first hash value), but does not store all transaction data (i.e., the service flow data or the first hash value). Each data submitting node intelligently manages and views its own service subchain, that is, only its own transaction record (including a cochain record of cochain service flow data or a cochain record of a first hash value corresponding to the cochain service flow data) can be known, but the service subchains of other data submitting nodes cannot be managed and viewed, so that the isolation between the transaction information of each data submitting node is ensured, and the security and privacy of the transaction information of each data submitting node are improved.
Step S105, the request terminal sends inquiry information aiming at the service processing authority corresponding to the service flow data to a management node;
specifically, the requesting terminal may send query information of the service processing permission for the service flow data to the management node. The request terminal may be a terminal corresponding to an export tax return bureau, and the export tax return bureau needs to determine whether to handle the export tax return service for the enterprise according to the service flow data of one or more data submission nodes (e.g., an enterprise applying for handling export tax return, a manufacturer purchasing the article by the enterprise, and a logistics provider entrusted by the manufacturer to transport the article). The query information may carry object information of an object applying for export tax refund (e.g., node information (which may include a node name, where the node name may be a business name of a business, and may also include a node identifier, etc.) of a data submission node corresponding to a business applying for export tax refund). Wherein the node identification may be an IP address (i.e., network address) of the node.
Step S106, the management node acquires the block from the service full-scale chain according to the inquiry information, and acquires the service process data through the block; verifying the data authenticity and the data integrity of the business process data, and generating feedback information aiming at the business processing permission corresponding to the business process data according to a verification result;
the management node may obtain one or more data submission nodes associated with the inquiry information, for example, the management node may obtain a data submission node corresponding to a manufacturer and a data submission node associated with a logistics provider, which are associated with node information of a data submission node corresponding to an enterprise carried in the inquiry information. The management node may obtain, in the service full-scale chain, blocks corresponding to the one (the associated data submitting node may also be a data submitting node itself corresponding to an enterprise) or the multiple data submitting nodes, respectively, and extract corresponding service flow data or the first hash value from each block. If the extracted first hash value is the first hash value, the management node may obtain the service flow data corresponding to the first hash value from the local database. The local database stores the mapping relationship between the first hash value and the business process data, and the management node can find the corresponding business process data according to the mapping relationship between the first hash value and the business process data and the first hash value. The management node may verify the data authenticity and the data integrity of the obtained business process data, for example, if the obtained business process data is a purchase certificate corresponding to an enterprise, the management node recognizes that the purchase certificate includes a purchase date, a purchase quantity, a full name of a buyer (i.e., the enterprise), a full name of a seller (i.e., a manufacturer), a stamp of the buyer, and a stamp of the seller, and considers that the purchase certificate has the data integrity. The management node stores the seal of the buyer and the seal of the seller in advance, so that the management node can identify the seal of the buyer and the seal of the seller in the purchase voucher, and if the seal of the buyer and the seal of the seller are identified to be correct, the purchase voucher is considered to have data authenticity. The management node may generate feedback information according to the result of auditing the data authenticity and the data integrity of the acquired business process data: when all the acquired business process data (one or more) are detected to have the data integrity and the data authenticity, confirmation information can be generated, wherein the confirmation information is the feedback information, and the confirmation information is information indicating that the business process authority is provided, for example, the confirmation information can be information indicating that the enterprise has the authority to handle the export tax refunds. When it is detected that at least one data submitting node does not have the data integrity and/or the data authenticity in all the acquired business process data(s), prompt information can be generated, the prompt information is the feedback information, the prompt information is information indicating that the business processing authority is not available, and for example, the prompt information can be information indicating that the enterprise does not have the authority to handle export tax refunds. The management node may send the generated feedback information to the request terminal, and the request terminal may determine whether to handle the corresponding service according to the specific content of the feedback information, for example, when the feedback information is the confirmation information, the request terminal may handle the export tax refund service for the enterprise, and when the feedback information is the prompt information, the request terminal may not handle the export tax refund service for the enterprise.
Optionally, when the management node receives query information for service processing permission of service flow data sent by the request terminal, the management node may also send one or more service flow data corresponding to the obtained one or more blocks to the request terminal, and the request terminal may automatically determine whether to handle a corresponding service (for example, an export tax refunding service) according to the obtained one or more service flow data.
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 related data of the export tax refunding business are improved.
Firstly, a data submitting node sends data to be linked to a participating node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data; the participating node generates a chain loading request carrying the data to be chain loaded, and sends the chain loading request to a management node; the uplink request carries the data to be uplink; the management node checks the uplink data to be linked carried by the uplink request, if the check passes, a block is generated according to the uplink data to be linked, and the block is added to a service full-scale chain; when the management node receives inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, the block is obtained from the service full-scale chain according to the inquiry information, and the service process data is obtained through the block; and the management node verifies the data authenticity and the data integrity of the business process data and generates feedback information aiming at the business processing permission corresponding to the business process data according to a verification result. Therefore, the method provided by the application supports the data submission node to send the business process data to the management node through the participation node, the request terminal can obtain the business process data sent by the data submission node through the management node and obtain the auditing result of the business processing permission of the business process data, and the auditing result is the feedback information, so that the auditing efficiency of the business process data uploaded by the data submission node is improved.
Please refer to fig. 5, which is a schematic structural diagram of a data interaction device based on a blockchain network according to the present application. As shown in fig. 5, the data interaction apparatus 1 is applied to a participant node, and the data interaction apparatus 1 may include: a first obtaining module 11 and a generating module 12;
a first obtaining module 11, configured to obtain data to be uplink sent by a data submitting node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
a generating module 12, configured to generate a uplink request carrying the to-be-uplink data, and send the uplink request to a management node, so that when the management node passes an identification of the to-be-uplink data carried in the uplink request, the to-be-uplink data is added to a full-service chain, and when query information for a service processing permission corresponding to the service process data is obtained, feedback information is generated through the full-service chain; the feedback information is generated after the management node verifies the data authenticity and the data integrity of the business process data.
For a specific implementation manner of the functions of the first obtaining module 11 and the generating module 12, please refer to steps S101 to S106 in the embodiment corresponding to fig. 2, which is not described herein again.
Wherein, the data interaction device 1 is further configured to:
and when the block is detected to exist in the service full-scale chain, acquiring the block from the service full-scale chain, extracting a block head from the block, and returning the block head to the data submission node.
Please refer to fig. 6, which is a schematic structural diagram of another data interaction device based on a blockchain network according to the present application. As shown in fig. 6, the data interaction apparatus 2 is applied to a management node, and the data interaction apparatus 2 may include: a second obtaining module 21, a receiving module 22 and an auditing module 23;
a second obtaining module 21, configured to obtain a uplink request carrying to-be-uplink data sent by a participating node, perform signature verification on the to-be-uplink data carried in the uplink request, and if the signature verification passes, generate a block according to the to-be-uplink data, and add the block to a full-size service chain; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
a receiving module 22, configured to, when receiving inquiry information, which is sent by a request terminal and is directed to a service processing permission corresponding to the service process data, obtain the block from the full service chain according to the inquiry information, and obtain the service process data through the block;
and the auditing module 23 is configured to audit data authenticity and data integrity of the business process data, and generate feedback information for the business processing permission corresponding to the business process data according to an auditing result.
For specific implementation of functions of the second obtaining module 21, the receiving module 22 and the auditing module 23, please refer to steps S101 to S106 in the embodiment corresponding to fig. 2, which is not described herein again.
The management node also stores a mapping relation between the business process data and the first hash value in a local database;
the receiving module 22 includes a first extracting unit 221, an obtaining unit 222, and a second extracting unit 223:
a first extracting unit 221, configured to extract the first hash value from the block when the to-be-uplink data includes the first hash value corresponding to the service flow data;
an obtaining unit 222, configured to obtain the business process data in the local database according to the first hash value and a mapping relationship between the first hash value and the business process data;
a second extracting unit 223, configured to extract the service flow data from the block when the service flow data is included in the to-be-uplink data.
For a specific implementation manner of the functions of the first extracting unit 221, the obtaining unit 222, and the second extracting unit 223, please refer to step S106 in the corresponding embodiment of fig. 2, which is not described herein again.
Firstly, a data submitting node sends data to be linked to a participating node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data; the participating node generates a chain loading request according to the data to be chain loaded, and sends the chain loading request to a management node; the uplink request carries the data to be uplink; the management node generates a block according to the data to be uplink carried by the uplink request, and adds the block to a service full-scale chain; when the management node receives inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, the block is obtained from the service full-scale chain according to the inquiry information, and the service process data is obtained through the block; and the management node verifies the data authenticity and the data integrity of the business process data and generates feedback information aiming at the business processing permission corresponding to the business process data according to a verification result. Therefore, the method provided by the application supports the data submission node to send the business process data to the management node through the participation node, the request terminal can obtain the business process data sent by the data submission node through the management node and obtain the auditing result of the business processing permission of the business process data, and the auditing result is the feedback information, so that the auditing efficiency of the business process data uploaded by the data submission node is improved.
Please refer to fig. 7, which is a schematic structural diagram of a computer device provided in the present application. As shown in fig. 7, 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. 7, 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. 7, 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 to implement the description of the data interaction 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 interaction method based on the blockchain network in the embodiment corresponding to fig. 2, and may also perform the description of the data interaction device 1 in the embodiment corresponding to fig. 5 and the description of the data interaction device 2 in the embodiment corresponding to fig. 6, which are not repeated herein. 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 interaction device 1 and data interaction device 2 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 interaction 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 (11)

1. A data interaction method based on a block chain network is characterized by comprising the following steps:
the data submitting node sends the data to be linked to the participating node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
the participating node generates a chain loading request carrying the data to be chain loaded, and sends the chain loading request to a management node;
the management node checks the uplink data to be linked carried by the uplink request, if the check passes, a block is generated according to the uplink data to be linked, and the block is added to a service full-scale chain;
when the management node receives inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, the block is obtained from the service full-scale chain according to the inquiry information, and the service process data is obtained through the block;
and the management node verifies the data authenticity and the data integrity of the business process data and generates feedback information aiming at the business processing permission corresponding to the business process data according to a verification result.
2. The method of claim 1, further comprising:
when the participating node detects that the block exists in the business full-scale chain, acquiring the block from the business full-scale chain, extracting a block head from the block, and returning the block head to the data submitting node;
and the data submitting node adds the block head to the service subchain.
3. The method according to claim 1, wherein the management node further stores a mapping relationship between the business process data and the first hash value in a local database;
the acquiring the business process data through the block includes:
when the data to be uplink comprises the first hash value corresponding to the business process data, the management node extracts the first hash value from the block;
the management node acquires the business process data from the local database according to the first hash value and the mapping relation between the first hash value and the business process data;
and when the data to be uplink comprises the business process data, the management node extracts the business process data from the block.
4. The method of claim 1, wherein the data submitting node sending data to be uplink transmitted to a participating node, comprises:
when the data submitting node detects that the data volume of the business process data is smaller than a data volume threshold value, performing hash operation on the business process data based on a hash algorithm to obtain a first hash value corresponding to the business process data;
the data submitting node signs the first hash value based on the corresponding private key to obtain a first signature corresponding to the first hash value, and adds the business process data and the first signature to a first to-be-uplink data packet;
the data submitting node encrypts the first to-be-uplink data packet based on the corresponding public key to obtain the to-be-uplink data;
and the data submitting node submits the data to be uplink to the participating node.
5. The method of claim 1, wherein the data submitting node sending data to be uplink transmitted to a participating node, comprises:
when the data submitting node detects that the data volume of the business process data is larger than or equal to a data volume threshold value, performing hash operation on the business process data based on a hash algorithm to obtain a first hash value corresponding to the business process data;
the data submission node performs hash operation on the first hash value based on the hash algorithm to obtain a second hash value corresponding to the first hash value;
the data submitting node signs the second hash value based on the corresponding private key to obtain a second signature corresponding to the second hash value, and adds the second signature and the first hash value to a second data packet to be uplinked;
the data submitting node encrypts the second data packet to be uplink based on the corresponding public key to obtain the data to be uplink;
and the data submitting node submits the data to be uplink to the participating node.
6. A data interaction method based on a block chain network is characterized by comprising the following steps:
a participating node acquires data to be uplink sent by a data submitting node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
generating a chain loading request carrying the data to be chain loaded, sending the chain loading request to a management node, so that when the management node passes the verification of the data to be chain loaded in the chain loading request, a block is generated according to the data to be chain loaded, the block is added to a full service chain, and when inquiry information aiming at the service processing permission corresponding to the service process data is acquired, the block corresponding to the service process data is acquired from the full service chain, and feedback information is generated through the block; the feedback information is generated after the management node verifies the data authenticity and the data integrity of the business process data.
7. A data interaction method based on a block chain network is characterized by comprising the following steps:
the method comprises the steps that a management node obtains a uplink request carrying to-be-uplink data sent by a participating node, conducts signature verification on the to-be-uplink data carried by the uplink request, generates a block according to the to-be-uplink data if the signature verification passes, and adds the block to a business full-scale chain; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data; the data to be uplink comes from a data submitting node;
when receiving inquiry information aiming at the service processing authority corresponding to the service process data, which is sent by a request terminal, acquiring the block from the service full-scale chain according to the inquiry information, and acquiring the service process data through the block;
and auditing the data authenticity and the data integrity of the business process data, and generating feedback information aiming at the business processing permission corresponding to the business process data according to an auditing result.
8. A data interaction device based on a block chain network is applied to a participating node, and is characterized by comprising:
the first acquisition module is used for acquiring data to be uplink sent by the data submitting node; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data;
a generating module, configured to generate a uplink request carrying the to-be-uplink data, send the uplink request to a management node, so that when the management node passes an identification of the to-be-uplink data carried in the uplink request, a block is generated according to the to-be-uplink data, the block is added to a full-service chain, and when inquiry information for a service processing permission corresponding to the service process data is obtained, a block corresponding to the service process data is obtained from the full-service chain, and feedback information is generated through the block; the feedback information is generated after the management node verifies the data authenticity and the data integrity of the business process data.
9. A data interaction device based on a block chain network is applied to a management node and is characterized by comprising the following components:
a second obtaining module, configured to obtain a uplink request carrying to-be-uplink data sent by a participating node, perform signature verification on the to-be-uplink data carried by the uplink request, generate a block according to the to-be-uplink data if the signature verification passes, and add the block to a full-service chain; the data to be uplink comprises service flow data or a first hash value corresponding to the service flow data; the data to be uplink comes from a data submitting node;
the receiving module is used for acquiring the block from the service full-scale chain according to the inquiry information and acquiring the service process data through the block when the inquiry information aiming at the service processing authority corresponding to the service process data and sent by the request terminal is received;
and the auditing module is used for auditing the data authenticity and the data integrity of the business process data and generating feedback information aiming at the business processing permission corresponding to the business process data according to an auditing result.
10. 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.
11. 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.
CN201910907463.9A 2019-09-24 2019-09-24 Data interaction method and device based on block chain network Active CN110601856B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910907463.9A CN110601856B (en) 2019-09-24 2019-09-24 Data interaction method and device based on block chain network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910907463.9A CN110601856B (en) 2019-09-24 2019-09-24 Data interaction method and device based on block chain network

Publications (2)

Publication Number Publication Date
CN110601856A CN110601856A (en) 2019-12-20
CN110601856B true CN110601856B (en) 2022-04-29

Family

ID=68862829

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910907463.9A Active CN110601856B (en) 2019-09-24 2019-09-24 Data interaction method and device based on block chain network

Country Status (1)

Country Link
CN (1) CN110601856B (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111130806A (en) * 2019-12-30 2020-05-08 论客科技（广州）有限公司 E-mail filing and evidence saving method and device based on block chain technology
CN111339086B (en) * 2020-02-18 2021-04-20 腾讯科技（深圳）有限公司 Block processing method, and data query method and device based on block chain
CN111416808B (en) * 2020-03-13 2021-04-13 财付通支付科技有限公司 Cross-block-chain data mutual storage method, device, equipment and storage medium
CN111600896A (en) * 2020-05-21 2020-08-28 昆明大棒客科技有限公司 Data chaining method, device, equipment and system based on AWS cloud platform
CN111813853B (en) * 2020-05-29 2022-07-22 深圳平安医疗健康科技服务有限公司 Data acquisition method and device based on block chain system and computer equipment
CN111967875A (en) * 2020-08-19 2020-11-20 上海网班教育科技股份有限公司 Block chain-based file uplink evidence storing method and device
CN112364371B (en) * 2020-10-16 2024-04-16 杭州甘道智能科技有限公司 Vaccine transfer monitoring device and method based on block chain
CN113094427B (en) * 2021-03-10 2023-12-19 贾晓丰 Data management method and device based on block chain
CN116596197A (en) * 2023-07-18 2023-08-15 青岛博什兰物联技术有限公司 Standard public service platform based on block chain technology
CN117057889B (en) * 2023-10-11 2023-12-12 北京天润基业科技发展股份有限公司 Transaction method and system based on data isolation

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107341702A (en) * 2017-03-08 2017-11-10 阿里巴巴集团控股有限公司 A kind of method and device of business processing
CN108133008A (en) * 2017-12-22 2018-06-08 平安养老保险股份有限公司 The processing method of business datum, device, equipment and storage medium in database
CN109102246A (en) * 2018-07-25 2018-12-28 珠海宏桥高科技有限公司 A kind of trade Synergistic method and trade cooperative system based on block chain
CN109154885A (en) * 2016-03-21 2019-01-04 澳大利亚国家Ict有限公司 Business processing on block platform chain executes
CN109981750A (en) * 2019-03-06 2019-07-05 北京百度网讯科技有限公司 Business process system, business data processing method and device
WO2019143593A1 (en) * 2018-01-19 2019-07-25 Vpt Gp Data collection with a blockchain recording
CN110245186A (en) * 2019-05-21 2019-09-17 深圳壹账通智能科技有限公司 A kind of method for processing business and relevant device based on block chain

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109154885A (en) * 2016-03-21 2019-01-04 澳大利亚国家Ict有限公司 Business processing on block platform chain executes
CN107341702A (en) * 2017-03-08 2017-11-10 阿里巴巴集团控股有限公司 A kind of method and device of business processing
CN108133008A (en) * 2017-12-22 2018-06-08 平安养老保险股份有限公司 The processing method of business datum, device, equipment and storage medium in database
WO2019143593A1 (en) * 2018-01-19 2019-07-25 Vpt Gp Data collection with a blockchain recording
CN109102246A (en) * 2018-07-25 2018-12-28 珠海宏桥高科技有限公司 A kind of trade Synergistic method and trade cooperative system based on block chain
CN109981750A (en) * 2019-03-06 2019-07-05 北京百度网讯科技有限公司 Business process system, business data processing method and device
CN110245186A (en) * 2019-05-21 2019-09-17 深圳壹账通智能科技有限公司 A kind of method for processing business and relevant device based on block chain

Also Published As

Publication number Publication date
CN110601856A (en) 2019-12-20

Similar Documents

Publication Publication Date Title
CN110601856B (en) Data interaction method and device based on block chain network
CN109255084B (en) Electronic bill query method, device, storage medium and computer equipment
US20200043001A1 (en) Pet Food Traceability System and Method Therefor
CN110493268B (en) Data processing method, device and equipment based on block chain network and storage medium
CN111292041B (en) Electronic contract generation method, device, equipment and storage medium
US11223482B2 (en) Secure data exchange
US20200387859A1 (en) Methods, Application Server, Block Chain Node and Media For Logistics Tracking and Source Tracing
US20080263645A1 (en) Privacy identifier remediation
CN110598456B (en) Data storage method and device, electronic equipment and storage medium
CN110599107B (en) Logistics data processing method and device based on block chain
AU2020279093A1 (en) Method and system for generalized provenance solution for blockchain supply chain applications
US20070174196A1 (en) System and method for verifying authenticity
CN109905351B (en) Method, device, server and computer readable storage medium for storing data
CN113128950B (en) Enterprise chain code service platform
CN110599322B (en) Data auditing method and device based on blockchain network
US11516001B2 (en) Method and system for generalized provenance solution for blockchain supply chain applications
CN110599270A (en) Electronic bill generation method and device and computer equipment
CN114500093A (en) Safe interaction method and system for message information
CN112819675A (en) Banking affair flow control method and device
CN110689348B (en) Revenue verification method, device, terminal and medium based on alliance chain
WO2018210097A1 (en) Method and device for execution transaction mode by classification
CN113129008B (en) Data processing method, device, computer readable medium and electronic equipment
KR102358511B1 (en) Menagement system of product safety information based on blockchain
CN114298698A (en) Transaction settlement method and device
CN111131227B (en) Data processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant